-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow speed limits for slotcar robots #56
Conversation
Signed-off-by: ddengster <ed.fan@osrfoundation.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this feature, @luca-della-vedova! I've taken a quick look, other than the comments, I also feel that we should revisit functions like calculate_control_signals
and calculate_joint_control_signals
in the future and remove the use of default arguments in the next major versions release, as those arguments are used wholly by our downstream packages so far.
Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Added checks for speed limit being greater than 0 02dc918.
This can be done, so the idea is that all the arguments must be specified at all times instead of relying on default arguments? In that case I think some refactoring is also in order to reduce the number of input arguments to these functions, maybe by packing more motion parameters in |
Closed via #71 |
New feature implementation
Implemented feature
This PR allows simulated robots to respect speed limits specified in path requests, requires open-rmf/rmf_internal_msgs#28 and open-rmf/rmf_ros2#132
Implementation description
A new
std::optional<double> max_speed
is added toUpdateResult
inslotcar_common
, if a speed limit was specified in the message (specifically if it was > 0.0) the minimum between vehicle nominal speed and speed limit will be the navigation speed of the vehicle, before it was fixed at being the maximum robot speed at all times.Since we need to store more information than a simple pose for differential drive robots' trajectories (i.e. speed limit), a new struct
DiffDriveTrajectory
was added and a minor refactoring took place to use it throughout the code.