ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

There are possibly three reasons due to which this can occur

Either the id is more than the set range
Or the baud rate is different
the motor's firmware is not working properly

try this :

check the id of motor using single manager gui package from dynamixel workbench and confirm it is not set to be more than 25.
check the communication baud rate it should match 57600
- if both of the above are fine then do a firmware recovery using R+ manager

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2