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
Fix: Default disable auto recovery on motor loss comm (#62)
* feat(dm_driver): make motor auto-recovery opt-in, fail-fast by default
- i2rt/motor_drivers/dm_driver.py: added enable_auto_recovery constructor flag (default False, read live each control-loop iteration); gated both control-loop recovery paths (the RuntimeError "Motor error detected" catch and the feedback error_code check) behind it, so a loss-comm error (0xD) now sets running=False and re-raises instead of silently clearing and re-enabling the motor
- i2rt/robots/get_robot.py: threaded enable_auto_recovery through get_yam_robot and _get_gripper_only_robot into the DMChainCanInterface constructor (default False)
- i2rt/robots/motor_chain_robot.py: added enable_auto_recovery override on MotorChainRobot (None = inherit the chain's setting) and exposed the effective value in the robot info dict
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(flow_base): explicitly disable motor auto-recovery on the mobile base
- i2rt/flow_base/flow_base_controller.py: pass enable_auto_recovery=False at the
holonomic_base and unified_motor_chain DMChainCanInterface constructions so the
base's fail-fast intent is explicit at the call sites (ROB-1449); functional no-op
since the constructor default is already False.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments