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

move_base constantly replanning ("got new plan")

asked 2019-10-23 12:37:44 -0500

pitosalas gravatar image

I'm not sure if this is normal but I never noticed it before. Here's my scenario:

Ros Melodic, Turtlbot3, physical robot, not simulation. All nodes appear to be launching correctly. I provide an initial pose in Rviz and that seems to work fine. But, when I set a navigation goal in Rviz, the robot does not move. Instead in the log I see a fast steady stream of "got new plan" logs. What does that mean? What might be wrong? Thanks!

edit retag flag offensive close merge delete


Are you running on all default params? If not, try doing that for the TB3 params file and work back from there if it works.

stevemacenski gravatar image stevemacenski  ( 2019-10-23 12:48:16 -0500 )edit

Thanks... Sounds like a good theory! What file exactly are we talking about?

pitosalas gravatar image pitosalas  ( 2019-10-23 13:49:12 -0500 )edit

All of the configurations

stevemacenski gravatar image stevemacenski  ( 2019-10-23 15:16:21 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2019-10-23 21:52:15 -0500

fergs gravatar image

If you're using the default turlebot3_navigation package, then that appears to be expected behavior. The developers of this package have chosen to set "planner_frequency" to 5.0 (see This means the planner will replan at 5.0hz - which might be OK, or might cause side effects. You could try setting the parameter to 0.0 in order to stop the replanning if it is causing issues (for instance, a major side effect is large-scale oscillation where the planner is oscillating between two vastly different solutions).

edit flag offensive delete link more

Question Tools



Asked: 2019-10-23 12:37:44 -0500

Seen: 1,177 times

Last updated: Oct 23 '19