-
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
itemRead function does not work after Motor Error... #307
Comments
Any update on this? |
Hi @swiz23 DYNAMIXEL Workbench has been updated with a limitation such as adding a new DYNAMIXEL, but without fixing bugs or adding new features. Thank you. |
Got it. Thanks! Will the changes be merged into master eventually? |
I think these changes are pretty safe to be merged as it only allows to "read" from DYNAMIXEL. |
Hi @ROBOTIS-Will, |
@swiz23 |
@ROBOTIS-Will We were able to verify that the patch does work. You can feel free to close this. Thanks! |
@LSinterbotix |
How to setup? U2D2
Which Dynamixel have you used? and how many? (Please describe below format to all connected Dynamixels)
Model Name: Combination of XL430 and XM430 servos (7 in total)
ID: 1 - 7
Baud Rate of Dynamixels: 1 Mbps
Protocol Version: 2.0
Write down the commands you used in order:
[RxPacketError] Hardware error occurred. Check the error at Control Table (Hardware Error Status)!
I'm purposely putting the motor with ID 7 into an error state (by overloading it), and then trying to read the Hardware_Error_Status register using the 'itemRead' function in the dynamixel_workbench_toolbox. Unfortunately, I always recieve the above error message - no matter what register I try to read from. Note that before putting the motor in an 'overloaded' state, the itemRead function works just fine. Is there a reason this function breaks after a motor error occurs? I'm not trying to enable the torque or even write to a register - just trying to read the register so I can know in software if the motor is in an error state or not.
Thanks
The text was updated successfully, but these errors were encountered: