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

dynamic obstacle problems with short range sensor

asked 2015-10-28 09:59:50 -0500 gravatar image

updated 2015-10-29 02:38:19 -0500

Hi all,

I got some problem in using move_base with short LaserScan sensor.

Here is my condition:

  • With short distance range sensor (xv11 sensor, max range is 6M)
  • With a static map and the map contains lots of open space
  • Now I put an obstacle in front of the robot. Yes, I saw the obstacle shown in costmap.
  • Then, I removed the above obstacle from gazebo.
  • I found the obstacle is still there in costmap. I think it's because the range sensor can not reach the edge of the map, so it got unknown readings for this area which I put an obstacle in previous step.

Any suggestion will be appreciated. Thanks!

Kevin Kuei

edit retag flag offensive close merge delete


what is your raytrace_range parameter set to in the costmap?

miguel gravatar image miguel  ( 2015-10-28 11:20:30 -0500 )edit

raytrace_range=2.5 and obstacle_range=2.0, I put the obstacle at 1.5m in front and I saw the obstacle in costmap. Then, I removed the obstacle from gazebo. But the result is, the obstacle is still in costmap. gravatar image  ( 2015-10-28 19:23:29 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-11-01 20:32:13 -0500 gravatar image

Again, I will answer my own question.

I wrote a custom range filter, and this can be applied in obstacle observation sources in costmap_common_params.yaml The logic is simple, if the laser range is large enough or Inf or Nan, then rewrite it to be another value which is slightly larger than your "obstacle_range" value.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2015-10-28 09:59:50 -0500

Seen: 1,558 times

Last updated: Nov 01 '15