* feat(msg): rename rover throttle setpoint to surface_vehicle_* The throttle setpoint was the last rover topic shared by rovers and boats without the surface_vehicle_* prefix decided in #29524. Rename RoverThrottleSetpoint to SurfaceVehicleThrottleSetpoint and the TYPE_ROVER_THROTTLE_* setpoint types to TYPE_SURFACE_VEHICLE_THROTTLE_*. The type values are unchanged. The topic rename breaks ROS 2 users anyway, so also shorten the fields of the throttle and speed setpoints to x and y: the message name already says what the value is and [@frame Body] states the frame. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> * fix(zenoh): bring surface_vehicle rename to the zenoh dds topics * fix(concept): rename rover throttle setpoint to surface_vehicle_* in navigation terminology * fix(tools): update px4-ros2-interface-lib pin * docs(msg): describe sideways fields as omnidirectional, not mecanum The surface vehicle messages are shared by rovers and boats, and the lateral axis applies to any vehicle that can move sideways, not only mecanum rovers. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> * docs(ros2): use the surface vehicle setpoint type names of the interface lib The pinned px4-ros2-interface-lib names the rover setpoint types SurfaceVehicle*SetpointType. The table and the example reference still used the old Rover*SetpointType class names, which do not exist in that version. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> * feat(msg)!: rename surface vehicle throttle setpoint to thrust setpoint The setpoint is a normalized force command along the body x and y axes, which is a thrust, not a throttle. Throttle stays the name for the motor command the actuator control derives from it. surface_vehicle_throttle_setpoint is now surface_vehicle_thrust_setpoint (SurfaceVehicleThrustSetpoint), and SetpointConfig TYPE_SURFACE_VEHICLE_THROTTLE_* are now TYPE_SURFACE_VEHICLE_THRUST_* (same values). The px4-ros2-interface-lib pin follows the matching rename there. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> * fix(tools): update px4-ros2-interface-lib pin * fix(commander): do not enable velocity control for surface vehicle thrust setpoints The SurfaceVehicleThrust* setpoint types enabled the velocity flag, taken over from the original interface lib configuration. Nothing in these types uses velocity, and offboard mode maps the same combinations without it. The flag kept the rover speed controller running: switching from a SurfaceVehicleSpeed* to a SurfaceVehicleThrust* type sets the same flags, so the controllers were not reset and a stale speed setpoint kept overriding the commanded thrust. It also made external modes that only command thrust require a local position estimate. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> * docs(msg): apply review suggestions for the surface vehicle setpoints Add long descriptions to the thrust and speed setpoints and the speed status, name modules instead of C++ classes, and use single spaces before field comments. Rename the speed status PID integrals from pid_throttle_* to pid_thrust_*, since the speed controller drives the thrust setpoint. Update the docs and the rover control structure diagram for the thrust setpoint and omnidirectional vehicles, note the Rover*SetpointType names of PX4 v1.17 and v1.18, and add the ROS 2 release note. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Michael Fritsche <frimi999@gmail.com> --------- Signed-off-by: Michael Fritsche <frimi999@gmail.com>
4.3 KiB
pageClass
| pageClass |
|---|
| is-wide-page |
SurfaceVehiclePositionSetpoint (UORB message)
Surface Vehicle Position Setpoint.
Position setpoint consumed by the position controllers of rover_ackermann, rover_differential and rover_mecanum, which turn it into surface_vehicle_speed_setpoint and surface_vehicle_attitude_setpoint. Published by the manual (position), auto and offboard drive modes of rover_ackermann, rover_differential and rover_mecanum, and can be sent from ROS 2 over uXRCE-DDS (/fmu/in/surface_vehicle_position_setpoint). The rover follows the desired track from start_ned to target_ned. To control the course over ground instead, publish surface_vehicle_course_setpoint; the position controller follows whichever of the two was published most recently.
TOPICS: surface_vehicle_position_setpoint
Fields
Source Message
::: details Click here to see original file
# Surface Vehicle Position Setpoint
#
# Position setpoint consumed by the position controllers of rover_ackermann, rover_differential
# and rover_mecanum, which turn it into surface_vehicle_speed_setpoint and
# surface_vehicle_attitude_setpoint.
# Published by the manual (position), auto and offboard drive modes of rover_ackermann,
# rover_differential and rover_mecanum, and can be sent from ROS 2 over uXRCE-DDS
# (/fmu/in/surface_vehicle_position_setpoint).
# The rover follows the desired track from start_ned to target_ned. To control the course over ground
# instead, publish surface_vehicle_course_setpoint; the position controller follows whichever
# of the two was published most recently.
uint64 timestamp # [us] Time since system start
float32[2] target_ned # [m] [@range -inf, inf] [@frame NED] [@invalid NaN No target; the position controller stays idle] Target position
float32[2] start_ned # [m] [@range -inf, inf] [@frame NED] [@invalid NaN Defaults to the vehicle position when the setpoint is received] Start position of the desired track towards target_ned
float32 cruising_speed # [m/s] [@range -inf, inf] [@invalid NaN Defaults to maximum speed] Cruising speed; a negative value drives the rover in reverse (rear first) towards target_ned
float32 arrival_speed # [m/s] [@range 0, inf] [@invalid NaN Defaults to 0] Speed magnitude to arrive at the target with, independent of the direction of travel
float32 yaw # [rad] [@range -pi, pi] [@frame NED] [@invalid NaN Not considered] Currently unused. Only for omnidirectional vehicles: vehicle yaw during travel.
:::