dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/msg/VtolVehicleStatus.msg

13 lines
505 B
Plaintext
Raw Normal View History

vehicle_status: move vtol_vehicle_status enum It makes more sense to have the VTOL status in its own message.
2016-02-24 06:27:00 -04:00
# VEHICLE_VTOL_STATE, should match 1:1 MAVLinks's MAV_VTOL_STATE
uint8 VEHICLE_VTOL_STATE_UNDEFINED = 0
uint8 VEHICLE_VTOL_STATE_TRANSITION_TO_FW = 1
uint8 VEHICLE_VTOL_STATE_TRANSITION_TO_MC = 2
uint8 VEHICLE_VTOL_STATE_MC = 3
uint8 VEHICLE_VTOL_STATE_FW = 4
beautify some identation
2018-08-07 10:42:32 -03:00
uint64 timestamp # time since system start (microseconds)
add timestamp field to uORB msgs; sync timestamp whenever possible
2018-08-06 21:30:05 -03:00
VTOL: remove some unsued variables Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
2022-01-25 12:29:54 -04:00
uint8 vehicle_vtol_state # current state of the vtol, see VEHICLE_VTOL_STATE
vtol_vehicle_status: replace several status bools by single vehicle_vtol_state Replace vtol_in_rw_mode, vtol_in_trans_mode, in_transition_to_fw by vehicle_vtol_state. Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
2022-01-20 07:55:06 -04:00
VTOL/Commander: rename transition_failsafe to vtol_fixed_wing_system_failure Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
2023-01-12 04:56:58 -04:00
bool fixed_wing_system_failure # vehicle in fixed-wing system failure failsafe mode (after quad-chute)