Extrapolation Error looking up robot pose ... when looking up transform from frame [base_footprint] to frame [map]

edit

Hi All,

This is one of my first posts, please go easy on me.. To start: Working with the navigation stack in ROS Indigo, on Turtlebot with Xbox Kinect Camera. The Turtlebot is using an NVIDIA TK1 board, roscore is running on a HP Elitebook laptop. Viewing rviz on the HP Elitebook and running all the code locally on the TK1

The launch file looks like this:

<include file="$(find turtlebot_bringup)/launch/minimal.launch"/>
<include file="$(find kobuki_auto_docking)/launch/minimal.launch"/>
<include file="$(find turtlebot_navigation)/launch/amcl_demo.launch"/>
<node pkg="robot_pose_publisher" name="robot_pose_publisher" type="robot_pose_publisher"/>

Pretty simple, right?

Then i'm opening up rviz like this:

roslaunch turtlebot_rviz_launchers view_navigation.launch

I'm then choosing the 2D nav_goal in rviz and moving my robot around the map. The robot will move generally well, but when it gets stuck in tight places, I keep getting this error message:

Extrapolation Error looking up robot pose: Lookup would require extrapolation into the past.  Requested time 1486427903.748853431 but the earliest data is at time 1486427905.883079467, when looking up transform from frame [base_footprint] to frame [map]

When this error message comes up, the command rosrun tf tf_echo /map /base_footprint implies that it cannot find the transformation, which is what the error message is showing

I've looked at some other ROS questions and answers regarding this error message like this. I took the recommendation and set the transform tolerance lower and also set the frequency for local and global cost map lower, all with the intent of trying not to overload the CPU.

One thing I noticed was in rviz I kept noticing was my /scan topic timing out, with the error message:

For frame [/camera_depth_frame]: No transform to fixed frame [map]. TF error: [Lookup would require extrapolation into the future. Requested time is xxxxx but the latest data is at time xxxx, when looking up transform from frame [camera_depth_frame] to frame [map]

Okay! Looks like a /tf problem on two fronts, then I ran rosrun tf tf_monitor and saw this: RESULTS: for all Frames

Frames:
Frame: base_footprint published by unknown_publisher Average Delay: -0.0257666 Max Delay: 0
Frame: base_link published by unknown_publisher Average Delay: -0.52515 Max Delay: 0
Frame: camera_depth_frame published by unknown_publisher Average Delay: -0.525171 Max Delay: 0
Frame: camera_depth_optical_frame published by unknown_publisher Average Delay: -0.525185 Max Delay: 0
Frame: camera_link published by unknown_publisher Average Delay: -0.525198 Max Delay: 0
Frame: camera_rgb_frame published by unknown_publisher Average Delay: -0.525206 Max Delay: 0
Frame: camera_rgb_optical_frame published by unknown_publisher Average Delay: -0.525241 Max Delay: 0
Frame: caster_back_link published by unknown_publisher Average Delay: -0.525249 Max Delay: 0
Frame: caster_front_link published by unknown_publisher Average Delay: -0.525257 Max Delay: 0
Frame: cliff_sensor_front_link published by unknown_publisher Average Delay: -0.525262 Max Delay: 0
Frame: cliff_sensor_left_link published by unknown_publisher Average Delay: -0.52528 Max Delay: 0
Frame: cliff_sensor_right_link published by unknown_publisher Average Delay: -0.525287 Max Delay: 0
Frame: gyro_link published by unknown_publisher Average Delay: -0.525295 Max Delay: 0
Frame: odom ...