gmapping Detected jump back in time of. Clearing TF buffer.

asked 2020-03-10 12:37:15 -0500

sinsinsinsin
28 ●12 ●13 ●16

updated 2020-03-10 16:53:36 -0500

Hi everyone

I am running gmapping with my own bag (in which I drive turtlebot with turtlebot_telop node, drive the robot go around the simulation environment.)

Then I start roscore, set use_sim_time true, run gmapping, play the bag file.

The gmapping works, but terminal sometimes outputs

[ WARN] [1583861539.918718206, 587.563370629]: Detected jump back in time of 0.000629371s. Clearing TF buffer.

It seems like there was a jump in the timestamp? It is the problem with my bag file of the gamapping settings?

Thank you!

------updates-----

I set the /use_sim_time to 0.1, now it works fine without warning.

edit retag flag offensive close merge delete

Comments

Are you running rosbag play with the --clock option?

gvdhoorn ( 2020-03-10 16:20:06 -0500 )edit

yes I did. I guess the problem is /use_sim_true. I set it to 0.1 then warning disappeared.

sinsinsinsin ( 2020-03-10 16:52:41 -0500 )edit

0.1 is not a legal value for use_sim_time. It's supposed to be a boolean. Not a float.

gvdhoorn ( 2020-03-10 16:59:30 -0500 )edit

Yes, I understand it is a boolean. I can't remember in which slam system, I get the /use_sim_time, got a result of 0.1. But you are right, it is a boolean.

sinsinsinsin ( 2020-04-02 15:10:15 -0500 )edit

add a comment

Comments

Hi, Thank you for answering. Is that right if the message jumps out during playing a bag file. If i understand is correct, The clock shouldn't frequently switching during the system running. for example, I run roscore, set the sim time true, roslaunch SLAM, play --clock bag. At the beginning, there will be some clock jump message. Okay, maybe the system need few seconds to adjust the clock. But what if the message frequently shows up?

sinsinsinsin ( 2020-04-02 15:16:50 -0500 )edit

That is correct. It should not show up frequently or else you have something else also resetting the clock or not all your nodes are using the same clock.

stevemacenski ( 2020-04-02 15:51:20 -0500 )edit

Oh, sounds not good. I just roscore, set /use_sim_time true, roslaunch turtlebot3_slam turtlebot3_slam slam_methods:=gmapping, rosbag play --clock mybag. the bag was recorded by record all.

I guess this will cost a lot of time to find out.

sinsinsinsin ( 2020-04-02 15:55:24 -0500 )edit

add a comment

gmapping Detected jump back in time of. Clearing TF buffer.

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

gmapping Detected jump back in time of. Clearing TF buffer. edit

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

gmapping Detected jump back in time of. Clearing TF buffer.