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

Add a service for rebooting camera #140

Open
2 tasks done
scheideman opened this issue Mar 21, 2023 · 1 comment
Open
2 tasks done

Add a service for rebooting camera #140

scheideman opened this issue Mar 21, 2023 · 1 comment
Labels
feature_request New feature or request

Comments

@scheideman
Copy link

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal

Add a service to the ROS 2 node that allows you to reboot the device. Optionally, reboot the camera if it cannot grab images or connect to the camera after a timeout.

Note: this sort of behaviour could be implemented using the LifecycleNode interface. But I see that the ROS 2 wrapper switched away from using LifecycleNode in patch 3.3.1

Use-Case

Because USB cameras can be unreliable and disconnect due to vibration or other random occurrences I need to periodically restart the ROS 2 node and sometimes call the reboot function using another script.

If the wrapper had a service that allowed me to reboot the camera then I could call it if the publishing rate dropped below some threshold. Also, if the wrapper tried to reboot on startup when a camera is unreachable this would save me needing to run another script to reboot the cameras or manually unplugging and re-plugging the cameras.

Anything else?

No response

@scheideman scheideman added the feature_request New feature or request label Mar 21, 2023
@peredwardsson
Copy link

I second the need for this. The camera node doesn't warn when its publishing rate decreases, i just notice other reliant nodes performing worse and worse. Any type of semiautomatic reboot would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature_request New feature or request
Development

No branches or pull requests

2 participants