ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
In my case, the issue was that the clocks between the machine acting as ros master and the subscriber were not in sync. After syncing them back up, the warning went away and move_base accepted the point cloud data being sent.
Since there was no warning to the effect of the clock-sync issue anywhere where I could find it, I thought it useful to share this issue and resolution here.