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
I propose that the 'uptime' of the camera is computed and published so that the user can know how long the camera driver has been running. We already have the code available for this and it is available upon request.
The text was updated successfully, but these errors were encountered:
Sure, I'd take a look at a PR but I'm curious about a couple things -- why is 'uptime' useful to you? When do you publish uptime values (per frame? fixed interval?)?
Currently we publish uptime as part of a combined message, and uptime refers to the duration of time that the driver has been running. We use this because sometimes the driver loses connection to the camera and we are forced to restart the driver. We have a status screen that monitors all TOF cameras on our network and displays their uptimes as a type of health monitor.
I propose that the 'uptime' of the camera is computed and published so that the user can know how long the camera driver has been running. We already have the code available for this and it is available upon request.
The text was updated successfully, but these errors were encountered: