Revision history [back]

I've found that turtlebot_navigation requires a bit of tuning. It's not bad if the turtlebot is already facing in the general direction of a nav goal, but if the little guy has to do a 180, it's Spin City (extreme overshoot when coming about). Here are the settings I use (from my launch file):

  <!-- move_base -->
  <include file="$(find turtlebot_navigation)/launch/includes/move_base.launch.xml"/>
  <!-- default turtlebot is poorly-tuned-->
  <param name="move_base/DWAPlannerROS/max_rot_vel" value="1.0"/>
  <param name="move_base/DWAPlannerROS/acc_lim_theta" value="10.0"/>

This (mostly) damps the overshoot in my setup.

I've found that turtlebot_navigation requires a bit of tuning. It's not bad if the (simulated) turtlebot is already facing in the general direction of a nav goal, but if the little guy has to do a 180, it's Spin City (extreme overshoot when coming about). Here are the settings I use (from my launch file):

  <!-- move_base -->
  <include file="$(find turtlebot_navigation)/launch/includes/move_base.launch.xml"/>
  <!-- default turtlebot is poorly-tuned-->
  <param name="move_base/DWAPlannerROS/max_rot_vel" value="1.0"/>
  <param name="move_base/DWAPlannerROS/acc_lim_theta" value="10.0"/>

This (mostly) damps the overshoot in my setup.