ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

TopicDiagnostic: "Timestamps too far in future seen" but timestamps are correct.

asked 2017-07-26 09:37:18 -0600

vmlane gravatar image

I'm using a diagnostic_updater::TopicDiagnostic for a NavSatFix topic with the following parameters.

diagnostic_updater::FrequencyStatusParam freq_param(1.0, 1.0, 0.15, 10);
diagnostic_updater::TimeStampStatusParam time_param(0, 0.275);

And I frequently receive "Timestamps too far in future seen" messages in the rqt_runtime_monitor diagnostics. When the error occurs the earliest time stamp delay is always approximately -4.25 seconds. However, when I display the timestamp of the NavSatFix message in the terminal, it's the same as the UTC time for my computer, and there's no messages with future timestamps. What could be causing this?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2021-04-22 09:02:41 -0600

kosmastsk gravatar image

I had exactly the same issue and finally the problem was that the GPS antenna was not tightly mounted, even though the GPS messages that arrived on ROS seemed to have normal timestamps, small covariance and correct lat/lon measurements.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2017-07-26 09:37:18 -0600

Seen: 229 times

Last updated: Apr 22 '21