Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a Dynamixel motor detects some dangerous situations, the motor goes torque off:
https://emanual.robotis.com/docs/en/dxl/mx/mx-28/#shutdown
However, we sometimes want the motor to ignore the error and continue working.
For example, when we use the motor in robotic fingers and these fingers grasp an object, these fingers should continue exerting strong force not to drop the object.
In that situation, the motor continues detecting a big load, easily goes into
Overload Error
, and torque off.To avoid this problem, we can remove errors from
Shutdown
(andAlarm LED
) register of the motor to prevent torque off due to these errors.However, even when we do that, these errors are included in every response from the motor.
dynamixel_motor detects them and prints many error messages (especially when
Overload Error
):dynamixel_motor/dynamixel_driver/src/dynamixel_driver/dynamixel_io.py
Lines 985 to 1005 in 3d84232
dynamixel_motor/dynamixel_driver/src/dynamixel_driver/dynamixel_serial_proxy.py
Lines 228 to 238 in 3d84232
This PR enables to suppress that phenomenon by setting rosparam.