We spell out exactly which batteries we recommend. We say which batteries not to use. That sounds pretty cookbook to me.
github.com/ArcBotics/Hexy/wiki/Powering-Hexy
Perhaps I’m missing something, but short of actually including a set of batteries and a charger (which would be redundant for many people, and increase the costs for everyone), I’m not sure what more you’re looking for. If you let me know, I’ll be sure to include it in the documentation.
As I explained in your post for your bluetooth, you got one of the very few 6 pin devices we ever got, and I apologize the for the inconvenience of that, and we are including that in the documentation as per your suggestion in case someone else fall into that problem. However, out of 1500 units shipped, that probably accounts for about 10 of them.
Bluetooth is rarely a simple thing, and rightfully the most often then people have trouble with. We thus have a step-by-step tutorial covering it, for both OSX and windows:
github.com/ArcBotics/Hexy/wiki/Bluetooth
We think we have identified most of the issues people have, and are including that in our new batch of documents. If you have any suggestions as to more we could include, I am more than happy to do so.
While I do agree that better and clearer documentation is needed (and should be ready to go in a week, as I’ve been working on it for a while now), Hexy is a research platform. Its purpose is to get people spending time discovering what it can be. It is not a toy ready to play with, the reason we made it a kit. While we may release a version of Hexy which is sold as ready-to-go in the future (in a year or two), we do bill Hexy v1 as an introduction to advanced robotics. We have actively discouraged people who want to use it as such for their first robot, or in a classroom setting. Hexy is currently to hexapods what linux is to operating systems. Its going to take some work. However, it also comes at linux prices. If you want an apple, you can pay apple prices and get a Bioloid kit. Just be prepared to spend $$$$$$$$$$$$$$$$$ instead of $$$. This choice comes up often. UPrint vs Makerbot is another good example. Just like makerbot, however, we hope to improve over time to be fairly comparable (although we plan on keeping open source
.
That said, people like Michael and Rob have been able to do amazing things with Hexy, so much so we now link to their work right on the Hexy product page. I’m really happy with what this community has been able to do, and hope that I can include more of it into the mainline documentation and code. Such also is the spirit of open source.
The role of ready-to-go product lies with the release version of Sparki, which we are indeed putting a ton of effort into documenting before it goes out the door.
If you have any specific changes you’d recommend, please let us know and we’ll be happy to implement them.