Ask Your Question
0

Navigation stack velocity setpoint

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

sritee gravatar image

Reading through the document of the ROS Local Planner, a common one being DWA (http://wiki.ros.org/base_local_planner), 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
0

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

jordan gravatar image

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

gvdhoorn gravatar image

Look a little more more closely at:

http://wiki.ros.org/base_local_planne...

~<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

Comments

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 imagesritee ( 2019-11-24 21:32:33 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

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

Seen: 23 times

Last updated: Nov 24