Skip to content
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

Control Error & Reflex Recovery #50

Open
jcarpinelli-bdai opened this issue Mar 12, 2024 · 3 comments
Open

Control Error & Reflex Recovery #50

jcarpinelli-bdai opened this issue Mar 12, 2024 · 3 comments
Assignees

Comments

@jcarpinelli-bdai
Copy link

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.

@BarisYazici
Copy link
Collaborator

Good point. It's not yet available in Franka_ros2. We will prepare it for the coming releases.

@BarisYazici BarisYazici self-assigned this Mar 26, 2024
@jcarpinelli-bdai
Copy link
Author

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.

@jcarpinelli-bdai
Copy link
Author

@BarisYazici do you all have an ETA on this? I may have limited availability to help add error recovery to these hardware_interface classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants