The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Your step (2) is missing important information: move_base hands off the global plan to the local-planner, then the local-planner executes whatever algorithm it is programmed with. In theory, the local-planner might be designed to completely ignore the global plan.
Some local-planners publish info about their internal state as they do their calculations, maybe including the next internally-selected short-term goal, but I don't think there's any common/shared way this is done. Whether you can get the info depends on which local-planner you are using, or on you enhancing the local-planner with custom code.
So, in the completely general case, I think the only info you can get is the robot's current pose.
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.
