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

Tutorial 3 and map frame problems

asked 2018-10-09 05:00:15 -0500

FraBgn gravatar image

Hi,

After the last update of Ubuntu, I'm having a lot of problems with nav2d. I have downloaded nav2d and the other needed packages (rviz, stage_ros, joy, p2os) but, when I start tutorial 3 (without changing anything) with the command

roslaunch nav2d_tutorials tutorial3.launch

I get some problems. Everything seems fine (both stage and rviz are correctly opened and I can start the exploration without problems) until, in Rviz, the robot seems to start blocking and making little jumps after a couple of seconds. Then the exploration goes fine for a little time, but it then does the same behaviour again. This often leads to bad maps in Rviz, for example creating walls where there should be none, and eventually failing the exploration. Every time the robot begins blocking, both the Desired and Corrected operator topics in Rviz show this error message:

Transform [sender=unknown_publisher] For frame [odom]: No transform to fixed frame [map]. TF error: [Lookup would require extrapolation into the future. Requested time 169.800000000 but the latest data is at time 168.600000000, when looking up transform from frame [odom] to frame [map]]

While the topic LaserScan in Rviz shows this message:

Transform [sender=unknown_publisher] For frame [base_laser_link]: No transform to fixed frame [map]. TF error: [Lookup would require extrapolation into the future. Requested time 169.800000000 but the latest data is at time 168.600000000, when looking up transform from frame [base_laser_link] to frame [map]]

Sometimes after one of these blocks has gone on for some time, an error pops up in the command line:

[ERROR] [1539077791.154842789, 221.600000000]: Could not get robot position: Lookup would require extrapolation into the past. Requested time 211.400000000 but the earliest data is at time 211.600000000, when looking up transform from frame [base_link] to frame [map]

Here is an image of the screen in Rviz, hoping it can help in identifying the problem: Rviz Screen

I tried looking at some other topics, but I haven't found a solution. I first had these problems when doing the same with my map and my exploration plugins, but after I created another catkin workspace and installing a fresh copy of all the packages, included nav2d, I found out that the problems remain the same. I also noticed these problems before the last package update, but they now happen every time, while before they only happened not very often and with little real effect. I'm using Kinetic on an Acer Aspire E15 with 4GB RAM. If you need any other information, please ask me and I'll try to do anything I can.

Thanks in advance for your help!

edit retag flag offensive close merge delete

Comments

What is shown in the PDF generated by rosrun tf view_frames? That might be useful here.

allenh1 gravatar image allenh1  ( 2018-10-09 12:34:10 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2018-10-16 04:51:35 -0500

Sebastian Kasperski gravatar image

These might be some timing related issue. From what you write it looks a bit like the mapper is not able to provide the "map"->"odom" transformation in time. Please have a look at the system load (e.g. via the "System Monitor" or "top") to check if the mapper is unable to keep up. Also make sure that you use the "kinetic" branch of nav2d and that you build with -DCMAKE_BUILD_TYPE=Release.

If nothing of this helps, you could install the binary version of nav2d to see if it produces the same issues.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2018-10-09 05:00:15 -0500

Seen: 329 times

Last updated: Oct 16 '18