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

Use case: Support for initialization of robot hardware #27

Open
destogl opened this issue Jun 2, 2020 · 1 comment
Open

Use case: Support for initialization of robot hardware #27

destogl opened this issue Jun 2, 2020 · 1 comment

Comments

@destogl
Copy link
Member

destogl commented Jun 2, 2020

Many robotic components need initialization (e.g. homing) procedures to be ready to use.
Also, the components need to be able to recover themselves after an unexpected event, e.g. an emergency stop.

In ROS1, services are often used for this, and they are calling methods directly in hardware_interface. This is actually something which could be managed by the controller manager or at least the top-level robot interface to make it transparent throughout whole control chain.

@destogl
Copy link
Member Author

destogl commented Feb 2, 2023

This is still very fun!!!

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

1 participant