| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi! I am facing a problem that when I am using nav stack and dwa local planner to navigate the PR2 in gazebo. I have the map for navigation, but if I set the goal to close to some obstacles, the robot will start turning around and lose its goal. Is there any solution to this problem?
If the obstacle is not in the robot's global map, and the goal is too close to the obstacle (within the radius of the robot), the global planner will produce a valid path, but the local planner will not be able to execute it because it would put the robot in collision with the obstacle.
If the goal is too close to the obstacle, the robot will behave OK until it gets within sensor range of the obstacle, at which point the local planner will start issuing warnings about the goal point being in collision. It will also start executing the recovery behaviors in an attempt to clear out sensor noise. The recovery behaviors are probably causing the rotating that you're seeing.
If you aren't already, it's probably worth watching the console output or rosout from navigation while the robot is navigating.
Asked: 2013-07-16 12:00:23 -0600
Seen: 235 times
Last updated: Jul 17 '13
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
How close are you setting the goal to the obstacles? Is it closer than the radius of the robot?
Maybe it is smaller than the radius of the robot. But the planner still generate a valid global plan. And the robot begins to circle over 2 meters ahead of the goal. Is there any way that we can do to force the robot to follow its global plan?