| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hello there, I use the nav2d package and works fine, but I'm not satisfied by the path planner. That's because it does not use simple rotation relative to robot's own frame and this leads the robot stucked in corners etc.
Is there a way to cooperate move_base with nav2d_navigator? Or maybe another path planner?
Hello, what kind of robot platform do you use? This is currently not easily done, as the Operator and Navigator communicate via a non-standard topic. Of course you can always replace both nodes with any other navigation solution (e.g. move_base).
However, if your robot platform is able to turn in place, the Operator should make use of this motion. If your robot gets stuck in corners, this is possible due to wrong parameter settings of robot_radius in Operator and Navigator. The Navigator should have a slightly larger value than the Operator.
In costmap.yaml (Operator uses it) I added: "footprint: [ [0.25, 0.17], [-0.25, 0.17], [-0.25, -0.17], [0.25, -0.17] ]". Should I also add robot_radius parameter?
I tried robot_radius=0.25 for Operator and robot_radius=0.3 for Navigator but it still has the same behaviour.
Now the robot can turn in place but it does not choose this motion often, resulting in collisions. I posted a new question here if you could help me :) http://answers.ros.org/question/23369...
Asked: 2016-04-29 09:17:43 -0500
Seen: 296 times
Last updated: May 04 '16
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.
