controller_manager fails to find motors.

[blakelyc]

I have 8 XM430-350R motors connected through a U2D2 module. I am able to access each motor using the Dynamixel Workbench Single Manager. Verified that there are no baud or id conflicts.

started roslaunch server http://brain:34311/

SUMMARY

PARAMETERS

• /dynamixel_manager/namespace: locomotion
• /dynamixel_manager/serial_ports/motors/baud_rate: 1000000
• /dynamixel_manager/serial_ports/motors/max_motor_id: 8
• /dynamixel_manager/serial_ports/motors/min_motor_id: 1
• /dynamixel_manager/serial_ports/motors/port_name: /dev/ttyUSB0
• /dynamixel_manager/serial_ports/motors/update_rate: 20
• /rosdistro: kinetic
• /rosversion: 1.12.7

NODES
/
dynamixel_manager (dynamixel_controllers/controller_manager.py)

auto-starting new master
process[master]: started with pid [26359]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to be5abadc-b46f-11e8-a7d0-3052cbe70273
process[rosout-1]: started with pid [26416]
started core service [/rosout]
process[dynamixel_manager-2]: started with pid [26420]
[INFO] [1536525267.550451]: motors: Pinging motor IDs 1 through 8...
[FATAL] [1536525268.212288]: motors: No motors found.
================================================================================REQUIRED process [dynamixel_manager-2] has died!
process has died [pid 26420, exit code 1, cmd /opt/ros/kinetic/lib/dynamixel_controllers/controller_manager.py __name:=dynamixel_manager __log:=/home/charles/.ros/log/be5abadc-b46f-11e8-a7d0-3052cbe70273/dynamixel_manager-2.log].
log file: /home/charles/.ros/log/be5abadc-b46f-11e8-a7d0-3052cbe70273/dynamixel_manager-2*.log
Initiating shutdown!

[dynamixel_manager-2] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

[RosMasters]

Dear Sir,
I have got the same problem as you Sir. I don't know how to fix it, please help.
Thank you

[ycho80]

Have you guys found any solution for this issue?

[arebgun]

The XM430-350R wasn't produced when I developed the driver. It's not on the supported motors list, so it doesn't currently work. If it has the same API as other motors, you should be able to add the model number to the list to make it work.

…

On Sat, Aug 24, 2019 at 1:52 PM ycho80 ***@***.***> wrote: Have you guys found any solution for this issue? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#86?email_source=notifications&email_token=AALPNU46P6KZUOGAZUSDKCLQGF7PTA5CNFSM4FUBYYJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CFSJQ#issuecomment-524572966>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALPNUZMPUWBDCLL6DBQBVTQGF7PTANCNFSM4FUBYYJA> .