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

nav2: go exactly to this point, not approximately

asked 2023-03-14 04:24:08 -0500

Per Edwardsson gravatar image

updated 2023-03-14 04:24:35 -0500

When I provide a goal pose to the nav2 system on my robot, it tries it best to get within the goal tolerance of the goal, then stops. I find this behavior to be unintuitive: i should expect that the robot tries its best to get to the actual goal, then accept any result within the tolerance, but instead, it goes to the edge of the tolerance and is happy with that result. This means that if I give an xy tolerance of 1.0, it will always stop 1.0 meters from the goal. But then, if I set the xy goal tolerance too small, it oscillates around the target. Is this the intended behavior? How do I tell the nav2 system to generate a path to EXACTLY the goal, not just to any point within the tolerance? Using the pure pursuit controller if it makes a difference.

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2023-03-14 12:02:59 -0500

Sounds like a very reasonable potential contribution to change the behavior. However, its hard to then define when "done" is "done" without causing the exact same oscillation issues as you describe for setting very low tolerances. Basically: we would need a proposal for a metric for how to say, after we're within the tolerance, when we're completed to a satisfactory refined level.

edit flag offensive delete link more

Question Tools



Asked: 2023-03-14 04:24:08 -0500

Seen: 350 times

Last updated: Mar 14 '23