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

Revision history [back]

click to hide/show revision 1
initial version

Receiving transform from [..] that differed from ROS time by 86.129054226s

With "multiple machines" and issues with TF / subscribers the first thing to check would be time synchronisation across all machines involved. Can you confirm you've done that?

Receiving transform from [..] that differed from ROS time by 86.129054226s

With "multiple machines" and issues with TF / subscribers the first thing to check would be time synchronisation across all machines involved. Can you confirm you've done that?


Edit:

I had no idea synchronization was something to take into account.

It is pretty logical though, if you think about it: how would we be able to temporally correlate sensor data (or more generally: publications) coming from different machines without a common/shared/synchronised clock?

I quickly forced synchronisation by taking the desyncrhonized data and publishing it to a new topic without the old time info and this works (as a temp solution).

You probably already figured it out, but republishing like that is certainly not a real solution.

Take a look at wiki/ROS/NetworkSetup - Timing issues, TF complaining about extrapolation into the future? for a solution.