move_base constantly replanning ("got new plan")

melodic

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

pitosalas
628 ●116 ●149 ●169

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

Comments

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 ( 2019-10-23 12:48:16 -0500 )edit

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

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

All of the configurations

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

add a comment

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

fergs

13902 ●59 ●157 ●196 http://www.robotandchisel.com

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 https://github.com/ROBOTIS-GIT/turtle...). 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

add a comment

move_base constantly replanning ("got new plan")

Comments

1 Answer

Question Tools

Stats

Related questions

move_base constantly replanning ("got new plan") edit

Comments

1 Answer

Question Tools

Stats

Related questions

move_base constantly replanning ("got new plan")