mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-11-22 22:50:49 +08:00
* 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>
34 lines
2.0 KiB
Plaintext
34 lines
2.0 KiB
Plaintext
# Setpoint configuration message
|
|
#
|
|
# Published by external modes and PX4 will respond with SetpointConfigReply.
|
|
|
|
uint32 MESSAGE_VERSION = 0
|
|
|
|
uint64 timestamp # [us] Time since system start
|
|
|
|
uint16 TYPE_INVALID = 0
|
|
uint16 TYPE_DIRECT_ACTUATORS = 1 # ActuatorMotors and ActuatorServos
|
|
uint16 TYPE_MULTICOPTER_GOTO = 2 # GotoSetpoint
|
|
uint16 TYPE_FIXEDWING_LATERAL_LONGITUDINAL = 3 # FixedWingLateralSetpoint and FixedWingLongitudinalSetpoint
|
|
uint16 TYPE_TRAJECTORY = 4 # TrajectorySetpoint
|
|
uint16 TYPE_RATES = 5 # VehicleRatesSetpoint
|
|
uint16 TYPE_ATTITUDE = 6 # VehicleAttitudeSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_POSITION = 7 # SurfaceVehiclePositionSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_SPEED_ATTITUDE = 8 # SurfaceVehicleSpeedSetpoint and SurfaceVehicleAttitudeSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_SPEED_RATE = 9 # SurfaceVehicleSpeedSetpoint and SurfaceVehicleRateSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_SPEED_STEERING = 10 # SurfaceVehicleSpeedSetpoint and SurfaceVehicleSteeringSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_THRUST_ATTITUDE = 11 # SurfaceVehicleThrustSetpoint and SurfaceVehicleAttitudeSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_THRUST_RATE = 12 # SurfaceVehicleThrustSetpoint and SurfaceVehicleRateSetpoint
|
|
uint16 TYPE_SURFACE_VEHICLE_THRUST_STEERING = 13 # SurfaceVehicleThrustSetpoint and SurfaceVehicleSteeringSetpoint
|
|
uint16 TYPE_TRAJECTORY_6DOF = 14 # TrajectorySetpoint6dof
|
|
uint16 TYPE_THRUST_AND_TORQUE = 15 # VehicleThrustSetpoint and VehicleTorqueSetpoint
|
|
uint16 TYPE_POSITION_TRIPLET = 16 # PositionSetpointTriplet
|
|
|
|
uint16 type # [@enum TYPE] setpoint type (corresponding to one or more setpoint messages)
|
|
|
|
uint8 source_id # nav_state of the mode
|
|
|
|
bool should_apply # if true: apply as current setpoint configuration (mode should be active). If false: setpoint configuration is not changed (can be used to check if a setpoint can be used with the current vehicle configuration).
|
|
|
|
uint16 timeout_ms # Configure setpoint timeout. If no setpoint received for this time, PX4 triggers a failsafe. 0 disables the timeout (unresponsive modes still trigger a timeout through arming checks).
|