Problems with the firmware of Premium Bioloid robots

Technical Support
, , , , ,
1

Hello, I hope you can help me. I am working on a project with Bioloid Premium robots (humanoid type C and king spider). But I ran into software limitations, especially 3.

1. The humanoid does connect to my computer with the RoboPlus and R+ Motion 2.0 programs, but with programs like R+ Task 2.0 or newer software, it does not detect the CM-510. So I’ve been working with those two programs without issues, but when I record the default program, the following errors appear in the console:

{[ERROR:8100:0007:02]}

{[ERROR:8100:0008:02]}

{[ERROR:8100:0007:02]}

{[ERROR:8100:0008:02]}

{[ERROR:8100:0007:02]}

{[ERROR:8100:0008:02]}

{[ERROR:8100:0007:02]}

I read the manual and found that:

8100 → is the error ID

0007 or 0008 → is the servo motor ID, but there is no information on 02. I would like to ask for your help to verify what type of error this is.

2. When trying to use the physical remote control, the robot does not respond, do you think the receiver might be damaged?

3. When trying to use the spider king controller (CM-5), no program detects it at all.

2

  1. Dynamixels ID7 and ID8 are not recognized. The exact meaning of the last number, 02, is unknown.
    R+ Task 1.0
    The cable is likely damaged. Try replacing the cable connected to the unrecognized joint.

  2. Are you using an infrared receiver? Check for cable damage. Even if the robot isn’t moving, check to see if the RX and TX LEDs on the controller (CM510) blink when you press the remote control. If the controller LED responds when you press the remote control, communication is established.

  3. The CM5 is a long-discontinued product, but it uses the same communication method as the CM510. Check if the COM port is recognized in Device Manager. This could be a driver issue or an incorrect COM port setting.

3

Hello.

  1. I’m still having the problem, but I’m going to put it aside for now because I don’t see any impact on its other functionality.
  2. Fortunately, I was able to establish a connection thanks to a firmware update with the Robo Plus, updated the necessary drivers, and was able to download the robot’s default software. I felt very satisfied because I’d been stuck with this problem for days, haha.
  3. You were right. The receiver cable was acting up, and when I moved it, the controller’s LED would turn on. I fixed it, and it’s now receiving a signal.

Thanks for your help.

1 Like