by i-Bot » Mon Jan 07, 2013 12:13 pm
by i-Bot
Mon Jan 07, 2013 12:13 pm
The OP code is easy to use on the Bioloid and is of significant value if you want to develop using a linux processor. It is all written in C/C++, so you see a complete implementation without using external applications for video processing etc. C/C++ is an advantage on processors like the raspi because Python is pretty slow on the pi.
The DARwin motion manager takes a while to understand, but is ok when you get into it. Because the DARwin framework integrates the same motion engine as Bioloid and talks to Roboplus, you can quickly download all your existing motions from Roboplus to the DARwin framework on the bioloid(not tasks though).
Running AX instead of MX is not a problem, because the current DARwin code does not actually depend on MX specific commands.
The greater challenges are finding suitable small, light low cost linux boards which can handle the video and dynamixel load. Fit-PC is rather big and heavy for the Bioloid, but smaller Raspi and MK802 come with performance challenges. This said, porting to smaller linux processors does work with some special hardware considerations, and a rather slower video frame rate. It builds and runs fine under Raspbian(Debian), and Ubuntu.
I have also run the DARwin framework on the Robobuilder, but the modifications were very large, and of less value. Though once done, the video integration is very useful.
Let me know if you have any specific questions and when you have a hardware configuration decided, I can help you build the DARwin framework for it.
The OP code is easy to use on the Bioloid and is of significant value if you want to develop using a linux processor. It is all written in C/C++, so you see a complete implementation without using external applications for video processing etc. C/C++ is an advantage on processors like the raspi because Python is pretty slow on the pi.
The DARwin motion manager takes a while to understand, but is ok when you get into it. Because the DARwin framework integrates the same motion engine as Bioloid and talks to Roboplus, you can quickly download all your existing motions from Roboplus to the DARwin framework on the bioloid(not tasks though).
Running AX instead of MX is not a problem, because the current DARwin code does not actually depend on MX specific commands.
The greater challenges are finding suitable small, light low cost linux boards which can handle the video and dynamixel load. Fit-PC is rather big and heavy for the Bioloid, but smaller Raspi and MK802 come with performance challenges. This said, porting to smaller linux processors does work with some special hardware considerations, and a rather slower video frame rate. It builds and runs fine under Raspbian(Debian), and Ubuntu.
I have also run the DARwin framework on the Robobuilder, but the modifications were very large, and of less value. Though once done, the video integration is very useful.
Let me know if you have any specific questions and when you have a hardware configuration decided, I can help you build the DARwin framework for it.