<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="http://forum.robosavvy.com/feed.php?f=5&amp;t=7687" />

<title>RoboSavvy Forum</title>
<subtitle>Robosavvy Forum: The largest online community of Humanoid Robot Builders</subtitle>
<link href="http://forum.robosavvy.com/index.php" />
<updated>2012-01-07T01:37:15+01:00</updated>

<author><name><![CDATA[RoboSavvy Forum]]></name></author>
<id>http://forum.robosavvy.com/feed.php?f=5&amp;t=7687</id>
<entry>
<author><name><![CDATA[coasterman]]></name></author>
<updated>2012-01-07T01:37:15+01:00</updated>
<published>2012-01-07T01:37:15+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33387#p33387</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33387#p33387"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33387#p33387"><![CDATA[
Well, now I have another problem - in RoboPlus Motion, all the motors are reading either 0 or 1023, and when a program is run, the robot acts very strange.<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=3097">coasterman</a> — Sat Jan 07, 2012 1:37 am</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[coasterman]]></name></author>
<updated>2012-01-06T20:02:41+01:00</updated>
<published>2012-01-06T20:02:41+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33386#p33386</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33386#p33386"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33386#p33386"><![CDATA[
I finally figured out how to correctly use the dynamixel wizard, and recovered the firmware on the bad motor. After resetting its ID it is up and running again.<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=3097">coasterman</a> — Fri Jan 06, 2012 8:02 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Fritzoid]]></name></author>
<updated>2012-01-06T13:44:33+01:00</updated>
<published>2012-01-06T13:44:33+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33381#p33381</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33381#p33381"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33381#p33381"><![CDATA[
At this point it sounds like your only hope is the firmware recovery function in Dynamixel Wizard.  This function can re-flash the servo firmware IF it can communicate with the boot loader software.  <br /><br />A dynamixel servo is similar to a CM-5(10) controller in that each has a built-in boot loader segment in protected storage.  You communicate with the boot loader at 56Kbs (not 1Mbs) but only at power-on time.  The Dynamixel Wizard does this for you or you can try getting to the boot loader using Terminal mode and the USB2Dynamixel.<br /><br />If you can get into the boot loader, then the servo can be recovered.  It not then the servo is beyond repair.  Judging from your original post it sounds like it's a nearly new and should still be under warranty if that's the case.<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=438">Fritzoid</a> — Fri Jan 06, 2012 1:44 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[coasterman]]></name></author>
<updated>2012-01-06T04:05:03+01:00</updated>
<published>2012-01-06T04:05:03+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33379#p33379</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33379#p33379"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33379#p33379"><![CDATA[
I connected the motors to the adapter that came with the kit. I did a quick search in the dynamixel wizard and it found all the daisy-chained motors but #2. I then singled out the motor, connected it, and ran a full search. Nothing came up.<br /><br />I think it's toast. Any possible ways to recover it?<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=3097">coasterman</a> — Fri Jan 06, 2012 4:05 am</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Fritzoid]]></name></author>
<updated>2012-01-05T20:02:30+01:00</updated>
<published>2012-01-05T20:02:30+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33376#p33376</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33376#p33376"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33376#p33376"><![CDATA[
coasterman,<br /><br />If you have a USB2Dynamixel then you can use the dynamixel wizard to further diagnose the problem.  Could be that the CMOS based settings like BAUD rate or ID are hosed so that the servo responds at the wrong rate or address.  You can use the SEARCH command to check for this.  Or it could be that the RAM based program is corrupted and a firmware refresh will fix the problem.  If the boot loader or the hardware is damaged then the problem is much worse.<br /><br />But before you start, be sure to disconnect all the other servos and only power up the one you are interested in fixing.  It's all too easy to mess up other servos if you are not careful here.<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=438">Fritzoid</a> — Thu Jan 05, 2012 8:02 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[coasterman]]></name></author>
<updated>2012-01-05T04:49:02+01:00</updated>
<published>2012-01-05T04:49:02+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33371#p33371</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33371#p33371"/>
<title type="html"><![CDATA[AX-12A not recognized and not turning]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7687&amp;p=33371#p33371"><![CDATA[
I recently built a Bioloid GP and started using it. After a few days, the left arm shoulder stopped turning. I looked inside and found that ID 2 had a red LED lit solid on it. The motor did not seem hot at all and the joint seems to be smooth. Motors 4 and 6 farther down the arm work fine. The Dynamixel utility does not show motor 2 in the list of motors. <img src="http://forum.robosavvy.com/images/smilies/icon_question.gif" alt=":?:" title="Question" /> <br /><br />Is there any way I can reset the motor, or is it toast?<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=3097">coasterman</a> — Thu Jan 05, 2012 4:49 am</p><hr />
]]></content>
</entry>
</feed>