Legacy Forum: Preserving Nearly 20 Years of Community History - A Time Capsule of Discussions, Memories, and Shared Experiences.

AX-12A not recognized and not turning

Bioloid robot kit from Korean company Robotis; CM5 controller block, AX12 servos..
6 postsPage 1 of 1
6 postsPage 1 of 1

AX-12A not recognized and not turning

Post by coasterman » Thu Jan 05, 2012 4:49 am

Post by coasterman
Thu Jan 05, 2012 4:49 am

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. :?:

Is there any way I can reset the motor, or is it toast?
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. :?:

Is there any way I can reset the motor, or is it toast?
coasterman
Newbie
Newbie
Posts: 4
Joined: Thu Jan 05, 2012 4:38 am

Post by Fritzoid » Thu Jan 05, 2012 8:02 pm

Post by Fritzoid
Thu Jan 05, 2012 8:02 pm

coasterman,

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.

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.
coasterman,

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.

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.
Fritzoid
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 331
Joined: Mon Dec 18, 2006 1:00 am

Post by coasterman » Fri Jan 06, 2012 4:05 am

Post by coasterman
Fri Jan 06, 2012 4:05 am

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.

I think it's toast. Any possible ways to recover it?
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.

I think it's toast. Any possible ways to recover it?
coasterman
Newbie
Newbie
Posts: 4
Joined: Thu Jan 05, 2012 4:38 am

Post by Fritzoid » Fri Jan 06, 2012 1:44 pm

Post by Fritzoid
Fri Jan 06, 2012 1:44 pm

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.

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.

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.
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.

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.

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.
Fritzoid
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 331
Joined: Mon Dec 18, 2006 1:00 am

Post by coasterman » Fri Jan 06, 2012 8:02 pm

Post by coasterman
Fri Jan 06, 2012 8:02 pm

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.
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.
coasterman
Newbie
Newbie
Posts: 4
Joined: Thu Jan 05, 2012 4:38 am

Post by coasterman » Sat Jan 07, 2012 1:37 am

Post by coasterman
Sat Jan 07, 2012 1:37 am

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.
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.
coasterman
Newbie
Newbie
Posts: 4
Joined: Thu Jan 05, 2012 4:38 am


6 postsPage 1 of 1
6 postsPage 1 of 1