You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to setup? (ex, U2D2, OpenCR,...)
We have a setup with 24 motors connected to a Trossen Robotics 6 port hub which is then connected to a U2D2 that is plugged into our host that is running ROS2 Foxy. dynamixel-workbench branch ros2 dynamixel-control branch main dynamixel-workbench-msgs branch ros2
Image of our setup
That is we have 4 separate chains that are each connected to the 6 port hub. Each chain has the motors connected in serial (hub->motor1->motor2->motor3->motor4->motor5->motor6)
Please, describe detailedly what difficulty you are in
The system is working amazing right out of the box but we have seen issues where one chain of motors can become disconnected (the wire between the 6 port hub and the first motor in the chain falls out) while executing motion which causes the motors on the other 3 chains to move out of control.
Our question is why would removing one chain cause the others to move out of control? It looks as though the protocol supports CRC checking but it doesn't seem to be helping or enabled. Is there an easy way to check if the CRC is being utilized? Is there anything else we can do to help make our communication more robust?
The text was updated successfully, but these errors were encountered:
Hi @MarqRazz
I'm sorry about the delayed response.
DYNAMIXEL should never intercept packets for other IDs unless its Secondary ID happens to be configured with the same ID number of other DYNAMIXEL.
Let me take a look at the workbench and see if there's any bug that may send unintended packets to irrelevant DYNAMIXEL.
@ROBOTIS-Will no worries I know how busy things can get!
Thanks for pointing me to the Secondary ID I will have our customer check what that have it set to. I went over their wire routing and made it much more robust which has helped suppress the issue. If we continue to have problems I will post more updates here.
ISSUE TEMPLATE ver. 1.0.0
We have a setup with 24 motors connected to a Trossen Robotics 6 port hub which is then connected to a U2D2 that is plugged into our host that is running ROS2 Foxy.
dynamixel-workbench branch
ros2
dynamixel-control branch
main
dynamixel-workbench-msgs branch
ros2
Image of our setup
That is we have 4 separate chains that are each connected to the 6 port hub. Each chain has the motors connected in serial (hub->motor1->motor2->motor3->motor4->motor5->motor6)
Here is a copy of our ros2_control xacro:
The system is working amazing right out of the box but we have seen issues where one chain of motors can become disconnected (the wire between the 6 port hub and the first motor in the chain falls out) while executing motion which causes the motors on the other 3 chains to move out of control.
Our question is why would removing one chain cause the others to move out of control? It looks as though the protocol supports CRC checking but it doesn't seem to be helping or enabled. Is there an easy way to check if the CRC is being utilized? Is there anything else we can do to help make our communication more robust?
The text was updated successfully, but these errors were encountered: