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

TF_OLD_DATA ignoring data from the past for frame odom

asked 2015-01-28 08:19:57 -0600

Diego gravatar image

updated 2015-01-28 10:48:42 -0600

Thomas D gravatar image

Hello everyone

I was using ROS hydro, however I updated Ubuntu and installed ROS indigo in my computer. I am writing to you because I am currently trying to make a robot which goes from an estimated point to an aim point, for this I need to use tf (to find the robots estimated position), but when I execute my program the following warnings appear

warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:43 : property [interval_real] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:40 : property [gui_movemask] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:44 : property [laser_return] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:25 : property [laser_return] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:42 : property [range_max] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
warn: worldfile /home/diego/MobileRobots/src/AIS_worlds/LBH_floor_1.world:44 : property [resolution] is defined but not used (/tmp/buildd/ros-indigo-stage-4.1.1-2trusty-20141229-2215/libstage/worldfile.cc WarnUnused)
[ INFO] [1422453286.760958942]: found 1 position and laser(1)/camera(0) pair in the file
Warning: TF_OLD_DATA ignoring data from the past for frame odom at time 0.5 according to authority unknown_publisher
Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained
     at line 260 in /tmp/buildd/ros-indigo-tf2-0.5.7-0trusty-20141230-0040/src/buffer_core.cpp

I can cope with this if this it's just a simple problem or something with no importance (the map is loading perfectly), however the warning of TF_OLD_DATA is appearing at every 0.1s, Additionally I suspect that the robot is not receiving estimated position correctly:

[ INFO] [1422454423.865170946, 13.100000000]: POS estimated_x = 33.027127, aim_X= 33.800000, estimated_y =7.292175, aim_Y= -40.000000, dist = 47.298490
[ INFO] [1422454423.865415347, 13.100000000]: POS estimated_x = 33.027127, aim_X= 33.800000, estimated_y =7.292175, aim_Y= -40.000000, dist = 47.298490
Warning: TF_OLD_DATA ignoring data from the past for frame odom at time 13.3 according to authority unknown_publisher
Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained
     at line 260 in /tmp/buildd/ros-indigo-tf2-0.5.7-0trusty-20141230-0040/src/buffer_core.cpp
[ INFO] [1422454423.968773001, 13.200000000]: POS estimated_x = 33.027127, aim_X= 33.800000, estimated_y =7.292175, aim_Y= -40.000000, dist = 47.298490
[ INFO] [1422454423.969095065, 13.200000000]: POS estimated_x = 33.079496, aim_X= 33.800000, estimated_y =7.323241, aim_Y= -40.000000, dist = 47.328725
Warning: TF_OLD_DATA ignoring data from the past for frame odom at time 13.4 according to authority unknown_publisher
Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained
     at line 260 in /tmp/buildd/ros-indigo-tf2-0.5.7-0trusty-20141230-0040/src/buffer_core.cpp
[ INFO] [1422454424.062837413, 13.300000000]: POS estimated_x = 33 ...
(more)
edit retag flag offensive close merge delete

Comments

is this all running on the same computer, or are some nodes running on different machines running on your network? (I'm wondering if it's a networking problem rather than a ROS-specific problem.)

Morgan gravatar image Morgan  ( 2015-01-28 13:50:30 -0600 )edit

They are running on the same computer. Actually it's just one .cpp file. I can put it here if you want. Also I can upload the .launch file in case there is something missing

Diego gravatar image Diego  ( 2015-01-28 16:16:03 -0600 )edit

If you can provide a way for us to reproduce the problem, then we can really help you. Otherwise it's mostly guessing.

tfoote gravatar image tfoote  ( 2015-01-28 16:36:53 -0600 )edit

Hello,

I have the same issue. I tried first rosparam set use_sim_time true before replaying bag file.

I also tried setting <param name ="/use_sim_time" value="true"/> to launch file, but I am still getting the same error.

I am running SLAM toolbox within the docker so not sure if that is making a problem.

Any suggestions?

Regards

nedo99 gravatar image nedo99  ( 2021-02-15 10:36:39 -0600 )edit
1

Make sure you don't have anything running on the background that produces the same data -you can inspect all running processes with htop-. As I mentioned in my answer below, my problem was both the actual camera and Gazebo plugin was publishing the same topic with the same frame as I did not realize the camera wrapper node was running on background. For example, imagine in your SLAM toolbox, there is a laser scanner and publishes /laser topic on laser_frame. On the other hand, you have a robot equipped with a laser plugin and you spawned it into Gazebo, where /laser topic is been published on laser_frame. In this case, because of this same topic and frame name, tf might produce this error.

asaglam gravatar image asaglam  ( 2021-02-19 13:41:08 -0600 )edit
1

@nedo99 Please don't use an answer to ask a question, this isn't a forum. You'll get more visibility (and help!) by creating your own question and referencing this one

jayess gravatar image jayess  ( 2021-02-19 23:23:17 -0600 )edit

2 Answers

Sort by ยป oldest newest most voted
7

answered 2015-01-28 14:12:43 -0600

tfoote gravatar image

The error messages suggest you're running with simulated time. Make sure that you've set the flag to make sure the whole system is using simulated time by setting the parameter "use_sim_time" before you start any nodes.

http://wiki.ros.org/Clock

edit flag offensive delete link more

Comments

Thank you so much. I just put it before the node started in the .launch file and that's it.

Diego gravatar image Diego  ( 2015-01-28 16:37:52 -0600 )edit

Glad to hear it worked. Please accept the answer using the checkmark button at the left so others know it's resolved.

tfoote gravatar image tfoote  ( 2015-01-28 17:29:14 -0600 )edit

thank u so much for the help.it worked

npa gravatar image npa  ( 2015-12-17 00:37:07 -0600 )edit

Hi, I met with the same problem, but can you tell me how I can set the use_sim_time parameter? Thanks

Chunting gravatar image Chunting  ( 2017-03-19 04:29:06 -0600 )edit

@Chunting: in the launch file, write <param name="/use_sime_time" value="false"/>

gavran gravatar image gavran  ( 2017-03-20 02:27:55 -0600 )edit
2

@gavran that should be value="true"

tfoote gravatar image tfoote  ( 2017-03-20 12:42:38 -0600 )edit

yes, you are right!

gavran gravatar image gavran  ( 2017-03-24 11:23:39 -0600 )edit
3

@Chunting small misspelling. Should be: <param name ="/use_sim_time" value="true"/>

surfertas gravatar image surfertas  ( 2017-03-29 06:15:17 -0600 )edit
0

answered 2021-02-12 11:39:41 -0600

asaglam gravatar image

updated 2021-02-19 13:26:10 -0600

I know @tfoote has already answered the question but today I encountered the same error even though I was using use_sim_time = true.

I was running Mynteye (a depth camera) ROS-wrapper on my computer. Then, I wanted to do some tests in Gazebo. So, I shutdown the Mynteye wrapper node and then started Gazebo with my robot which includes the depth plugin. Then, I received the error.

The problem for me was that the Mynteye ROS-wrapper node was still running in the background. I thought the process was dead with a shutdown signal (Ctrl+c) but it wasn't. When I was looking at htop, I realized the wrapper node was there. After killing the wrapper node, my problem was solved.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2015-01-28 08:19:57 -0600

Seen: 21,589 times

Last updated: Feb 19 '21