Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Odometry data delay

I'm trying to implement the navigation stack but am having trouble with my odometry data. It seems to be delayed, judging by RVIZ: Once I tell the robot to move, it starts moving physically, but still takes a couple of seconds to start moving in RVIZ. The same happens when I tell it to stop. The robot stops immediately, but it's RVIZ model continues to move a couple of seconds more.

This is causing issues with my laser scan data, which does seem to work properly, so that when the robot starts or stops, it gets "dragged" across the map.

What could be a cause for this kind of behaviour?

Thank you!

Odometry data delay

I'm trying to implement the navigation stack but am having trouble with my odometry data. It seems to be delayed, judging by RVIZ: Once I tell the robot to move, it starts moving physically, but still takes a couple of seconds to start moving in RVIZ. The same happens when I tell it to stop. The robot stops immediately, but it's RVIZ model continues to move a couple of seconds more.

This is causing issues with my laser scan data, which does seem to work properly, so that when the robot starts or stops, it gets "dragged" across the map.

What could be a cause for this kind of behaviour?

Thank you!