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

L515: frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically #2127

Closed
alexart13 opened this issue Oct 20, 2021 · 2 comments

Comments

@alexart13
Copy link

I have L515 connected to my desktop with Ubuntu 20.04. Every time I start Realsense ROS node I get a message about HARDWARE_CLOCK:
[ INFO] [1634724771.144913009]: RealSense Node Is Up!
[ WARN] [1634724771.294350412]:
[ WARN] [1634724771.294478292]: frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically.

What does it mean? Is it possible to solve it? How often the timestamps could reset?

To launch the node I use the following command: roslaunch realsense2_camera rs_camera.launch

@alexart13
Copy link
Author

The timestamps seem to reset indeed periodically. I use realsense ROS node with rtabmap node. And in rtabmap logs after a few minutes from the start I noticed a message about timestamps:
[ WARN] [1634729045.501166339]: Odometry: Detected not valid consecutive stamps (previous=1634728996.176391s new=1634724749.179497s). New stamp should be always greater than previous stamp. This new data is ignored.

@alexart13
Copy link
Author

The reason is that 'global_timestamp' is off by default (which is not the case for D4xx). I don't know why. It is confusing.
#1607 (comment)

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