by StuartL » Wed Jun 20, 2007 3:36 pm
by StuartL
Wed Jun 20, 2007 3:36 pm
Yesterday my Bioloids turned up (yes, two of them). I wasted no time at all in assembling the humanoid straight away (anyone say "Steep learning curve"?).
This post is intended for new users to learn from my mistakes.
I had some minor wiring problems in the build as I didn't initially realise that there were both 18cm and 20cm data bus cables and put the 18cm in the ankles, requiring a rebuild of the ankles when I ran out of 18cm cables later in the build.
This frustration aside and taking half the day putting those damn nuts in place (please Robotis: Preinstall those nuts. Glue them in. Don't make me put any more in!) I had a humanoid built in about 2.5 hours.
Obviously I couldn't wait to try it and installed the software, updated the Bioloid firmware, loaded the test routine, couldn't figure out why the LEDs weren't lighting, couldn't figure out why it wasn't assuming the test position but thought "Hell, I'll just put the demo code on it and see what happens".
Of course I know NOW why the test code didn't work. I put the demo code on and pressed the start button. I blew a fuse. I had been warned about the blowing fuses problem by Royce at RoboGames so I fortunately didn't spend the next 3 hours trying to figure out what was wrong. Instead I popped the top off and put the supplied spare fuse in. The console had reported loads of "Invalid page" errors which confused me for a minute.
I guessed what was up and scanned the manual. The manual says loading the motion data is optional. Of course what it means (in hindsight) is that the motion data isn't overwritten by the BCP but plain doesn't exist on a new configuration. I uploaded the motion data and while the test program still didn't attain the crucifix position the LEDs were now lighting.
I loaded the motion editor and verified that the motor positions were being read correctly.
I then gritted my teeth and reloaded the BCP and ran it. It assumed the standing position! The clap test worked and so finally, at 12:30am, I went to bed.
Summary:
- Make sure you measure all your cables before plugging them in!
- Make sure you verify all motor positions before tightening those screws (this one didn't catch me but would be a BIG problem if you didn't get it right).
- Make sure you load the motion program before you run your BCP. If you don't BAD things will happen.
- Buy lots of fuses. 20x5mm 250v 5A. Buy loads, they're cheap.
Things I didn't like:
- The absence of pre-installed/glued nuts. This seriously extends build time.
- The absence of automatic torque overload control preventing fuse overloads.
- The size of the holes for the screwdriver to fit the CM-5 into the case. None of the screwdrivers I have with me in SF fit in these holes and still reach the screw heads. You need a screwdriver with a very long shaft.
- The zig-100 module is solder on, not plug in. I will have another look at this later next week and see if I can solder on a socket for it to fit in.
Things I did like:
- The flexibility of the kit.
- Torque feedback capability.
- The clarity of the instruction manual build instructions.
- Future build possibilities (e.g. double knees, grippers etc).
Yesterday my Bioloids turned up (yes, two of them). I wasted no time at all in assembling the humanoid straight away (anyone say "Steep learning curve"?).
This post is intended for new users to learn from my mistakes.
I had some minor wiring problems in the build as I didn't initially realise that there were both 18cm and 20cm data bus cables and put the 18cm in the ankles, requiring a rebuild of the ankles when I ran out of 18cm cables later in the build.
This frustration aside and taking half the day putting those damn nuts in place (please Robotis: Preinstall those nuts. Glue them in. Don't make me put any more in!) I had a humanoid built in about 2.5 hours.
Obviously I couldn't wait to try it and installed the software, updated the Bioloid firmware, loaded the test routine, couldn't figure out why the LEDs weren't lighting, couldn't figure out why it wasn't assuming the test position but thought "Hell, I'll just put the demo code on it and see what happens".
Of course I know NOW why the test code didn't work. I put the demo code on and pressed the start button. I blew a fuse. I had been warned about the blowing fuses problem by Royce at RoboGames so I fortunately didn't spend the next 3 hours trying to figure out what was wrong. Instead I popped the top off and put the supplied spare fuse in. The console had reported loads of "Invalid page" errors which confused me for a minute.
I guessed what was up and scanned the manual. The manual says loading the motion data is optional. Of course what it means (in hindsight) is that the motion data isn't overwritten by the BCP but plain doesn't exist on a new configuration. I uploaded the motion data and while the test program still didn't attain the crucifix position the LEDs were now lighting.
I loaded the motion editor and verified that the motor positions were being read correctly.
I then gritted my teeth and reloaded the BCP and ran it. It assumed the standing position! The clap test worked and so finally, at 12:30am, I went to bed.
Summary:
- Make sure you measure all your cables before plugging them in!
- Make sure you verify all motor positions before tightening those screws (this one didn't catch me but would be a BIG problem if you didn't get it right).
- Make sure you load the motion program before you run your BCP. If you don't BAD things will happen.
- Buy lots of fuses. 20x5mm 250v 5A. Buy loads, they're cheap.
Things I didn't like:
- The absence of pre-installed/glued nuts. This seriously extends build time.
- The absence of automatic torque overload control preventing fuse overloads.
- The size of the holes for the screwdriver to fit the CM-5 into the case. None of the screwdrivers I have with me in SF fit in these holes and still reach the screw heads. You need a screwdriver with a very long shaft.
- The zig-100 module is solder on, not plug in. I will have another look at this later next week and see if I can solder on a socket for it to fit in.
Things I did like:
- The flexibility of the kit.
- Torque feedback capability.
- The clarity of the instruction manual build instructions.
- Future build possibilities (e.g. double knees, grippers etc).