-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newer Dynamixel models not properly supported in ROS2 branches #376
Comments
Similarly, the selection of the current conversion factor in Lines 1363 to 1395 in 67a1631
Lines 1367 to 1406 in 140ddf6
|
any update on this? |
1. How to setup? (ex, U2D2, OpenCR,...)
Connected to the Dynamixels via RS485 over a USB->RS485 converter (Waveshare), then RS485 to TTL via Dynamixel Communication Bridge.
2. Which Dynamixel have you used? and how many? (Please describe below format to all connected Dynamixels)
3. Write down the commands you used in order
I'm using the workbench as a library, calling
Where
joint.dxl_id
is my Dynamixel's ID, of course.5. Please, describe detailedly what difficulty you are in
I'm on branch
ros2
(using it in Humble). When I want to switch to Current Control Mode, nothing happens (no comms on the bus). Replacing the call tosetCurrentControlMode()
with a call tosetExtendedPositionControlMode()
in the same place, it successfully changes to the Extended Position Control Mode. So I went into the workbench's code and saw that the checks don't include the XC330 models and probably just need to be added as in 99f377b :dynamixel-workbench/dynamixel_workbench_toolbox/src/dynamixel_workbench_toolbox/dynamixel_workbench.cpp
Lines 627 to 637 in 140ddf6
It looks like commit c9e4c75 adds some support to the ROS2 branches but misses the above mentioned checks/
The
master
branch has commit 99f377b which seems to add full support for them -> can it possibly be cherry-picked onto the ROS2 branches?The issue #278 (more than 3 years old by now) could be sort of related and would possibly be resolved when resolving this issue.
The text was updated successfully, but these errors were encountered: