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

Navigation stack velocity setpoint

asked 2019-11-24 19:24:48 -0500

sritee gravatar image

Reading through the document of the ROS Local Planner, a common one being DWA (, It seems like they all provide a setpoint velocity which is then provided to the robot base driver.

Am I correct in my understanding that all of these assume that the robot can accelerate near instantaneously to the set velocity, as none of them seem to take into account that it takes some amount of time to reach a setpoint.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2019-11-24 19:35:11 -0500

jordan gravatar image

updated 2019-11-24 23:40:28 -0500

gvdhoorn gravatar image

Look a little more more closely at:

~<name>/acc_lim_x (double, default: 2.5)

    The x acceleration limit of the robot in meters/sec^2 

~<name>/acc_lim_y (double, default: 2.5)

    The y acceleration limit of the robot in meters/sec^2 

~<name>/acc_lim_theta (double, default: 3.2)

    The rotational acceleration limit of the robot in radians/sec^2

I believe these parameters affect the trajectories that are evaluated by the controller.

edit flag offensive delete link more


These parameters affect the search for the next velocity, but when we forward simulate from the current point, it looks like we assume that the next velocity is reached instantaneously, that is my question

sritee gravatar image sritee  ( 2019-11-24 21:32:33 -0500 )edit

Question Tools

1 follower


Asked: 2019-11-24 19:24:48 -0500

Seen: 233 times

Last updated: Nov 24 '19