by PedroR » Thu Oct 18, 2012 7:13 pm
by PedroR
Thu Oct 18, 2012 7:13 pm
Hi Gort
I would actually love to see the results you're getting with the 3D Printed frames.
From the experiments we've made, it seems it is possible to 3D print the frames but you need to do see work on the CAD file to reinforce key structural zones. (see for example the post about the Robot Limor's designing).
Regarding the Metal vs Plastic it is possible a "Darwinized" bioloid GP was overweight.
From our experience, we've built a Bioloid GP with 18 servos (torso rotation and head rotation) and we found it was the weight of the extra servos that created some difficulties. (a stock GP has only 16 servos; a Darwin has 20)
From what we've seen the most sensitive part is the Ankle joint and the knee. (this is inline with what you said).
I guess you can work around these issues by putting an MX-28 on the lower body (it uses the same AX bus but the commands have higher resolution; there are work arounds for this).
Regarding the raspberry PI, the DArwin framework comes as source code.
Therefore, as long as you have a Linux OS, you should be able to compile the framework to run on any host.
The gait generator uses a lot of FPU but I trust a Raspberry PI would be able to handle that.
Going back to iBot's project he used a Beaglebone which I think is also ARM (I just don't know how the Bone and the PI compare).
There is an intermediate step which i-Bot did but I don't remember how he achieved it, where I think he has communication flowing from the PC to the servos though an intermediate board (like the CM-730 does).
Using the intermediate board is a very nice idea because you can rewrite the commands if need to.
(for example if the Darwin framework is sending commands with 4096 resolution, the intermediate board can rewrite them to 1024 of the AX (or let it pass through for any MX servos you may have in the mix).
Finally, if you're looking to use a PI, I assume you'd be looking to replace the CM-730. I recommend you have a look at iBot's project.
he's used an Arduino (a Pro mini I think), added the same IMu chips (he got them from Pololu I think) and program it to emulate the same memory mapping of the CM-730 et voilá.
(there's a lot of work before the voilá
but he's been able to prove the concept really well!)
Anyway, I apologise for the long reply.
I wrote a lot more than a reply to your question. I guess I'm just excited about the idea and getting carried away
Your approach of going with the DARwIn electronics kit is probably the most clever t this stage as you can now focus on fabricating the mechanics.
We get a lot of inquiries from people looking to get the CM-730 only (probably for custom projects where they want to run the DARwIn framework), but Robotis won't sell it separately. Yet interestingly no one has achieved a drop in CM-730 clone/replacement afaik.
Regards
Pedro
Hi Gort
I would actually love to see the results you're getting with the 3D Printed frames.
From the experiments we've made, it seems it is possible to 3D print the frames but you need to do see work on the CAD file to reinforce key structural zones. (see for example the post about the Robot Limor's designing).
Regarding the Metal vs Plastic it is possible a "Darwinized" bioloid GP was overweight.
From our experience, we've built a Bioloid GP with 18 servos (torso rotation and head rotation) and we found it was the weight of the extra servos that created some difficulties. (a stock GP has only 16 servos; a Darwin has 20)
From what we've seen the most sensitive part is the Ankle joint and the knee. (this is inline with what you said).
I guess you can work around these issues by putting an MX-28 on the lower body (it uses the same AX bus but the commands have higher resolution; there are work arounds for this).
Regarding the raspberry PI, the DArwin framework comes as source code.
Therefore, as long as you have a Linux OS, you should be able to compile the framework to run on any host.
The gait generator uses a lot of FPU but I trust a Raspberry PI would be able to handle that.
Going back to iBot's project he used a Beaglebone which I think is also ARM (I just don't know how the Bone and the PI compare).
There is an intermediate step which i-Bot did but I don't remember how he achieved it, where I think he has communication flowing from the PC to the servos though an intermediate board (like the CM-730 does).
Using the intermediate board is a very nice idea because you can rewrite the commands if need to.
(for example if the Darwin framework is sending commands with 4096 resolution, the intermediate board can rewrite them to 1024 of the AX (or let it pass through for any MX servos you may have in the mix).
Finally, if you're looking to use a PI, I assume you'd be looking to replace the CM-730. I recommend you have a look at iBot's project.
he's used an Arduino (a Pro mini I think), added the same IMu chips (he got them from Pololu I think) and program it to emulate the same memory mapping of the CM-730 et voilá.
(there's a lot of work before the voilá
but he's been able to prove the concept really well!)
Anyway, I apologise for the long reply.
I wrote a lot more than a reply to your question. I guess I'm just excited about the idea and getting carried away
Your approach of going with the DARwIn electronics kit is probably the most clever t this stage as you can now focus on fabricating the mechanics.
We get a lot of inquiries from people looking to get the CM-730 only (probably for custom projects where they want to run the DARwIn framework), but Robotis won't sell it separately. Yet interestingly no one has achieved a drop in CM-730 clone/replacement afaik.
Regards
Pedro