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

Revision history [back]

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).