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
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
The text was updated successfully, but these errors were encountered:
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.
Preliminary Checks
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
The text was updated successfully, but these errors were encountered: