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
The franka_ros documentation specifies an ErrorRecoveryAction which can be used to restart controller nodes after an error or reflex. Is there a similar mechanism in franka_ros2? I do not see any mention of error recovery in the ROS2 documentation.
The text was updated successfully, but these errors were encountered:
Good point. It's not yet available in Franka_ros2. We will prepare it for the coming releases.
Thank you! For what it's worth... I think it would be really valuable to have an allow-list of errors that we want franka_hardware to ignore. In ROS1, these errors delay the control loop because they are thrown, then caught. We see the robot "hiccup" as the error is caught on the user side. It would be helpful if we could prevent franka_hardware from throwing some errors in the first place. In addition, it would be helpful to have more control over the thresholds for some errors. The 20ms UDP timeout in particular would be great to have the option to increase.
The
franka_ros
documentation specifies anErrorRecoveryAction
which can be used to restart controller nodes after an error or reflex. Is there a similar mechanism infranka_ros2
? I do not see any mention of error recovery in the ROS2 documentation.The text was updated successfully, but these errors were encountered: