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

44 lines
991 B
Plaintext
Raw Permalink Normal View History

px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
uint64 timestamp # time since system start (microseconds)
uint16 free_memory_bytes
float32 voltage_v # Servo rail voltage in volts
float32 rssi_v # RSSI pin voltage in volts
# PX4IO status flags (PX4IO_P_STATUS_FLAGS)
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool status_arm_sync
bool status_failsafe
bool status_fmu_initialized
bool status_fmu_ok
bool status_init_ok
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
bool status_outputs_armed
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool status_raw_pwm
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
bool status_rc_ok
bool status_rc_dsm
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool status_rc_ppm
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
bool status_rc_sbus
bool status_rc_st24
bool status_rc_sumd
px4io: replace safety_off state with safety button event (#19558) internal PX4IO safety_off state is removed and replaced with a normal safety button event. From this 'commit' commander is taking care of the PX4IO safety.
2022-05-30 09:44:13 -03:00
bool status_safety_button_event # px4io safety button was pressed for longer than 1 second
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
# PX4IO alarms (PX4IO_P_STATUS_ALARMS)
bool alarm_pwm_error
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool alarm_rc_lost
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
# PX4IO arming (PX4IO_P_SETUP_ARMING)
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool arming_failsafe_custom
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
bool arming_fmu_armed
bool arming_fmu_prearmed
bool arming_force_failsafe
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
bool arming_io_arm_ok
bool arming_lockdown
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
bool arming_termination_failsafe
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
uint16[8] pwm
uint16[8] pwm_disarmed
uint16[8] pwm_failsafe
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
px4io: moving mixing to FMU side Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>
2021-08-16 14:10:52 -03:00
uint16[8] pwm_rate_hz
px4io: servorail_status -> px4io_status and log all flags
2020-07-16 15:39:13 -03:00
uint16[18] raw_inputs