ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

costmap does not get /scan data

asked 2013-06-16 17:34:36 -0600

pmolina gravatar image

updated 2014-01-28 17:16:55 -0600

ngrennan gravatar image


I am having a problem with basic nav_stack that I am hoping someone can provide basic guidance. I am sorry if it is a silly question, but I have been stuck on this for a while now.

I have started following the example in the tutorial in "navigation_stage" and changing the parameters to suit my sensors (I am trying to replace what is provided by stage with my own sensors) (I also read the navigation tunning page)

My problem is that although my TF, sensors topics, etc seems to be correct, both slam_gmapping and move_base_node only receive data from my laser scanner during startup and are unable to receive further data later (the blue "inflated_obstacles" is never updated in RVIZ neither is the red obstacles). Move_base often goes into "recovery mode" and starts spinning on the spot indefinitely. The main slam_gmapping map also does not update.

System: ROS fuerte - Ubuntu 12.04 Hokuyo urg-04lx-ug01 - hokuyo node

My configuration is: tf: (image description)

RXgraph: (image description)

move_base_node during startup:


-maxUrange 16 -maxUrange 5.59 -sigma 0.05 -kernelSize 1 -lstep 0.05 -lobsGain 3 -astep 0.05 -srr 0.01 -srt 0.02 -str 0.01 -stt 0.02 -linearUpdate 0.5 -angularUpdate 0.436 -resampleThreshold 0.5 -xmin -50 -xmax 50 -ymin -50 -ymax 50 -delta 0.05 -particles 80 update frame 0 update ld=0 ad=0 Laser Pose= 0 0 0 m_count 0 Registering First Scan


My config for the costmap is:


observation_sources: base_scan

base_scan: { sensor_frame: /base_laser_link, topic: /scan, data_type: LaserScan, expected_update_rate: 0.1, observation_persistence: 0.0, marking: true, clearing: true, max_obstacle_height: 0.4, min_obstacle_height: 0.08}


I wrote my own EKF based on MRPT EKF.(this might be cause of the problem, but I do not see how it affects it)

I should maybe mention that the packages seem to operate well since in simulation everything runs smoothly. (when using stage, everything works) I have checked the DEBUG messages for the move_base and slam_gmapping and there is nothing that stands out as being completely wrong. (just the standard message filter)

Hector mapping is working OK using the same transforms. However, gmapping or move_base_node are not.

Thank you for your time and help.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2013-06-17 09:03:51 -0600

pmolina gravatar image

I figured it out

Basically, the cost_map settings do not change every time the move_base system is launched.

I will change the name of the topic of the laser in the cost_map.xml file, but it would not be updated in param_server for some reason. Hence, once I launched move_base it will still use the old topic name (this is how I found out...)

If I restarted ROS core (that restarts param_server), then it will start working.

Is this expected behaviour? do I have to close ROS Core every time?


edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2013-06-16 17:34:36 -0600

Seen: 533 times

Last updated: Jun 17 '13