|
| 1 | +# autoware_vehicle_msgs |
| 2 | + |
| 3 | +## ActuationCommand.msg |
| 4 | + |
| 5 | +Defines an actuator-level command for the vehicle. |
| 6 | + |
| 7 | +This message sits **below** `autoware_control_msgs/Control.msg` in the control stack. |
| 8 | + |
| 9 | +- `Control.msg` expresses the _desired physical state_ of the vehicle (target steering tire angle, target velocity / acceleration). It is vehicle-independent. |
| 10 | +- `ActuationCommand.msg` expresses _commands to the actuators themselves_ (throttle pedal, brake pedal, steering input). Its meaning depends on how the vehicle interface is configured. |
| 11 | + |
| 12 | +The typical producer is `autoware_raw_vehicle_cmd_converter`, which converts a `Control` command into actuator-level signals using the vehicle's accel / brake / steer maps. The typical consumer is the vehicle interface that forwards these signals to the vehicle CAN bus or to a simulator. |
| 13 | + |
| 14 | +Fields: |
| 15 | + |
| 16 | +| Field | Meaning | Range | Sign | Units | |
| 17 | +| ----------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------- | ------------------------- | ------------- | |
| 18 | +| `accel_cmd` | Throttle pedal command (vehicle-defined scale) | Vehicle-dependent (defined by actuation maps and vehicle interface) | n/a | Dimensionless | |
| 19 | +| `brake_cmd` | Brake pedal command (vehicle-defined scale) | Vehicle-dependent (defined by actuation maps and vehicle interface) | n/a | Dimensionless | |
| 20 | +| `steer_cmd` | Steering actuation signal. Semantics depend on `convert_steer_cmd_method`, see below | Vehicle-dependent (defined by actuation maps and vehicle interface) | Left positive (Ackermann) | See below | |
| 21 | + |
| 22 | +Note that for `brake_cmd`, the command itself is positive while the resulting deceleration is negative. |
| 23 | + |
| 24 | +`steer_cmd` modes: |
| 25 | + |
| 26 | +| `convert_steer_cmd_method` | `steer_cmd` meaning | Units | |
| 27 | +| -------------------------- | ----------------------------------------------------------------------------------------- | --------------- | |
| 28 | +| Unset (vanilla) | Steering tire angle | radians | |
| 29 | +| `"vgr"` | Steering wheel angle, derived from the tire angle via a velocity-dependent gear ratio | radians | |
| 30 | +| `"steer_map"` | Vehicle-specific actuation signal (for example an EPS voltage), produced from a steer map | vehicle-defined | |
| 31 | + |
| 32 | +For all three fields, the canonical contract is _whatever the vehicle's actuation maps and parameters define_. A different vehicle interface (CARLA, AWSIM, a real CAN driver) can use different ranges or scaling. |
| 33 | + |
| 34 | +## ActuationCommandStamped.msg |
| 35 | + |
| 36 | +Wraps `ActuationCommand` with a `std_msgs/Header`, typically containing the time at which the command was issued. The `frame_id` is not used. |
| 37 | + |
| 38 | +## ActuationReport.msg |
| 39 | + |
| 40 | +Defines the _actual_ actuator state reported back by the vehicle, mirroring `ActuationCommand`. |
| 41 | + |
| 42 | +Producers: the vehicle interface (real or simulated). Consumers: tools that need to know what the vehicle is actually doing at the actuator level, such as `autoware_accel_brake_map_calibrator`. |
| 43 | + |
| 44 | +Fields use the same units, sign conventions, and modes as `ActuationCommand`: |
| 45 | + |
| 46 | +- `accel_report`: Throttle pedal command the vehicle is currently applying (vehicle-defined scale). |
| 47 | +- `brake_report`: Brake pedal command the vehicle is currently applying (vehicle-defined scale). |
| 48 | +- `steer_report`: Steering actuation signal the vehicle is currently applying. Same mode-dependent semantics as `steer_cmd`. |
| 49 | + |
| 50 | +## ActuationReportStamped.msg |
| 51 | + |
| 52 | +Wraps `ActuationReport` with a `std_msgs/Header` carrying the report's timestamp. |
0 commit comments