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

Negative frame latency. #431

Closed
pavloblindnology opened this issue Aug 2, 2018 · 4 comments
Closed

Negative frame latency. #431

pavloblindnology opened this issue Aug 2, 2018 · 4 comments

Comments

@pavloblindnology
Copy link
Contributor

Using D435 camera (firmware 5.9.14, librealsense 2.14.0) with ROS Kinetic (realsense2_camera 2.0.3)
I often get negative latency with command
rostopic delay /camera/infra1/image_rect_raw.

@pavloblindnology
Copy link
Contributor Author

It seems to be related to #419.
According to the latter, we get ~0 latency for the 1st frame and, if there is no time drift between camera and host clocks, for the next ones. And this obviously can not be true, because real latency = up to 1/FPS ms + OS pipe latency.
And the solution is the same as in #419 - to have a function to get current camera time. Then we could synchronize camera and host clocks - of course, up to the function latency.

@shuntaraw
Copy link

I think this is related to #461. The reason for this is that on-device clock is inaccurate and almost always gains.

@pavloblindnology
Copy link
Contributor Author

@shuntaraw Yes, for sure. And also because current synchronization is done stupidly, giving 0 latency for the 1st frame, that leads to later latencies fluctuating around 0 even if there were no drift.

@RealSenseCustomerSupport
Copy link
Collaborator

[Please Ignore - RealSense system 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

3 participants