Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

The [topicname] observation buffer has not been updated for [X] seconds, and it should be updated every [Y] seconds.

asked 2020-04-23 15:35:40 -0600

chfritz

553 ●2 ●48 ●18 https://luminrobotics.com

updated 2020-04-23 15:36:07 -0600

Similar to https://answers.ros.org/question/1720... I got this warning from move_base:

When checking the the topic in question though, it was arriving at high frequency. I've solved the issue now, and will post my answer, and since it is different from the above, I think it is useful to capture it here.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-04-23 15:38:09 -0600

chfritz

553 ●2 ●48 ●18 https://luminrobotics.com

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.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2020-04-23 15:35:40 -0600

Seen: 146 times

Last updated: Apr 23 '20

The [topicname] observation buffer has not been updated for [X] seconds, and it should be updated every [Y] seconds. edit

1 Answer

Question Tools

Stats

Related questions

The [topicname] observation buffer has not been updated for [X] seconds, and it should be updated every [Y] seconds.