Skip to content

C
C-Astral dialect C library
Commit 6b84c348 authored by PX4BuildBot's avatar PX4BuildBot
Browse files
Options

autogenerated headers for rev... 

autogenerated headers for rev https://github.com/mavlink/mavlink/tree/ac515aedf895dda46828389682e486e2d507ce38
parent 360879fc
Hide whitespace changes
Inline Side-by-side
Showing with 16 additions and 16 deletions
message_definitions/ardupilotmega.xml
View file @ 6b84c348
...@@ -1082,7 +1082,7 @@ ...@@ -1082,7 +1082,7 @@
<!-- Path planned landings are still in the future, but we want these fields ready: --> <!-- Path planned landings are still in the future, but we want these fields ready: -->
<field name="break_alt" type="int16_t">Break altitude in meters relative to home</field> <field name="break_alt" type="int16_t">Break altitude in meters relative to home</field>
<field name="land_dir" type="uint16_t">Heading to aim for when landing. In centi-degrees.</field> <field name="land_dir" type="uint16_t">Heading to aim for when landing. In centi-degrees.</field>
<field name="flags" type="uint8_t" enum="RALLY_FLAGS">See RALLY_FLAGS enum for definition of the bitmask.</field> <field name="flags" type="uint8_t" enum="RALLY_FLAGS" display="bitmask">See RALLY_FLAGS enum for definition of the bitmask.</field>
</message> </message>
<message id="176" name="RALLY_FETCH_POINT"> <message id="176" name="RALLY_FETCH_POINT">
<description>Request a current rally point from MAV. MAV should respond with a RALLY_POINT message. MAV should not respond if the request is invalid.</description> <description>Request a current rally point from MAV. MAV should respond with a RALLY_POINT message. MAV should not respond if the request is invalid.</description>
...@@ -1285,7 +1285,7 @@ ...@@ -1285,7 +1285,7 @@
<description>Heartbeat from a HeroBus attached GoPro</description> <description>Heartbeat from a HeroBus attached GoPro</description>
<field enum="GOPRO_HEARTBEAT_STATUS" name="status" type="uint8_t">Status</field> <field enum="GOPRO_HEARTBEAT_STATUS" name="status" type="uint8_t">Status</field>
<field enum="GOPRO_CAPTURE_MODE" name="capture_mode" type="uint8_t">Current capture mode</field> <field enum="GOPRO_CAPTURE_MODE" name="capture_mode" type="uint8_t">Current capture mode</field>
<field name="flags" type="uint8_t" enum="GOPRO_HEARTBEAT_FLAGS">additional status bits</field> <field name="flags" type="uint8_t" enum="GOPRO_HEARTBEAT_FLAGS" display="bitmask">additional status bits</field>
<!-- see GOPRO_HEARTBEAT_FLAGS --> <!-- see GOPRO_HEARTBEAT_FLAGS -->
</message> </message>
<message id="216" name="GOPRO_GET_REQUEST"> <message id="216" name="GOPRO_GET_REQUEST">
......
message_definitions/common.xml
View file @ 6b84c348
...@@ -2430,16 +2430,16 @@ ...@@ -2430,16 +2430,16 @@
<description>The heartbeat message shows that a system is present and responding. The type of the MAV and Autopilot hardware allow the receiving system to treat further messages from this system appropriate (e.g. by laying out the user interface based on the autopilot).</description> <description>The heartbeat message shows that a system is present and responding. The type of the MAV and Autopilot hardware allow the receiving system to treat further messages from this system appropriate (e.g. by laying out the user interface based on the autopilot).</description>
<field type="uint8_t" name="type" enum="MAV_TYPE">Type of the MAV (quadrotor, helicopter, etc., up to 15 types, defined in MAV_TYPE ENUM)</field> <field type="uint8_t" name="type" enum="MAV_TYPE">Type of the MAV (quadrotor, helicopter, etc., up to 15 types, defined in MAV_TYPE ENUM)</field>
<field type="uint8_t" name="autopilot" enum="MAV_AUTOPILOT">Autopilot type / class. defined in MAV_AUTOPILOT ENUM</field> <field type="uint8_t" name="autopilot" enum="MAV_AUTOPILOT">Autopilot type / class. defined in MAV_AUTOPILOT ENUM</field>
<field type="uint8_t" name="base_mode" enum="MAV_MODE_FLAG">System mode bitfield, see MAV_MODE_FLAG ENUM in mavlink/include/mavlink_types.h</field> <field type="uint8_t" name="base_mode" enum="MAV_MODE_FLAG" display="bitmask">System mode bitfield, see MAV_MODE_FLAG ENUM in mavlink/include/mavlink_types.h</field>
<field type="uint32_t" name="custom_mode">A bitfield for use for autopilot-specific flags.</field> <field type="uint32_t" name="custom_mode">A bitfield for use for autopilot-specific flags.</field>
<field type="uint8_t" name="system_status" enum="MAV_STATE">System status flag, see MAV_STATE ENUM</field> <field type="uint8_t" name="system_status" enum="MAV_STATE">System status flag, see MAV_STATE ENUM</field>
<field type="uint8_t_mavlink_version" name="mavlink_version">MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version</field> <field type="uint8_t_mavlink_version" name="mavlink_version">MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version</field>
</message> </message>
<message id="1" name="SYS_STATUS"> <message id="1" name="SYS_STATUS">
<description>The general system state. If the system is following the MAVLink standard, the system state is mainly defined by three orthogonal states/modes: The system mode, which is either LOCKED (motors shut down and locked), MANUAL (system under RC control), GUIDED (system with autonomous position control, position setpoint controlled manually) or AUTO (system guided by path/waypoint planner). The NAV_MODE defined the current flight state: LIFTOFF (often an open-loop maneuver), LANDING, WAYPOINTS or VECTOR. This represents the internal navigation state machine. The system status shows wether the system is currently active or not and if an emergency occured. During the CRITICAL and EMERGENCY states the MAV is still considered to be active, but should start emergency procedures autonomously. After a failure occured it should first move from active to critical to allow manual intervention and then move to emergency after a certain timeout.</description> <description>The general system state. If the system is following the MAVLink standard, the system state is mainly defined by three orthogonal states/modes: The system mode, which is either LOCKED (motors shut down and locked), MANUAL (system under RC control), GUIDED (system with autonomous position control, position setpoint controlled manually) or AUTO (system guided by path/waypoint planner). The NAV_MODE defined the current flight state: LIFTOFF (often an open-loop maneuver), LANDING, WAYPOINTS or VECTOR. This represents the internal navigation state machine. The system status shows wether the system is currently active or not and if an emergency occured. During the CRITICAL and EMERGENCY states the MAV is still considered to be active, but should start emergency procedures autonomously. After a failure occured it should first move from active to critical to allow manual intervention and then move to emergency after a certain timeout.</description>
<field type="uint32_t" name="onboard_control_sensors_present" enum="MAV_SYS_STATUS_SENSOR" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are present. Value of 0: not present. Value of 1: present. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field> <field type="uint32_t" name="onboard_control_sensors_present" enum="MAV_SYS_STATUS_SENSOR" display="bitmask" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are present. Value of 0: not present. Value of 1: present. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field>
<field type="uint32_t" name="onboard_control_sensors_enabled" enum="MAV_SYS_STATUS_SENSOR" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are enabled: Value of 0: not enabled. Value of 1: enabled. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field> <field type="uint32_t" name="onboard_control_sensors_enabled" enum="MAV_SYS_STATUS_SENSOR" display="bitmask" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are enabled: Value of 0: not enabled. Value of 1: enabled. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field>
<field type="uint32_t" name="onboard_control_sensors_health" enum="MAV_SYS_STATUS_SENSOR" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are operational or have an error: Value of 0: not enabled. Value of 1: enabled. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field> <field type="uint32_t" name="onboard_control_sensors_health" enum="MAV_SYS_STATUS_SENSOR" display="bitmask" print_format="0x%04x">Bitmask showing which onboard controllers and sensors are operational or have an error: Value of 0: not enabled. Value of 1: enabled. Indices defined by ENUM MAV_SYS_STATUS_SENSOR</field>
<field type="uint16_t" name="load">Maximum usage in percent of the mainloop time, (0%: 0, 100%: 1000) should be always below 1000</field> <field type="uint16_t" name="load">Maximum usage in percent of the mainloop time, (0%: 0, 100%: 1000) should be always below 1000</field>
<field type="uint16_t" name="voltage_battery">Battery voltage, in millivolts (1 = 1 millivolt)</field> <field type="uint16_t" name="voltage_battery">Battery voltage, in millivolts (1 = 1 millivolt)</field>
<field type="int16_t" name="current_battery">Battery current, in 10*milliamperes (1 = 10 milliampere), -1: autopilot does not measure the current</field> <field type="int16_t" name="current_battery">Battery current, in 10*milliamperes (1 = 10 milliampere), -1: autopilot does not measure the current</field>
...@@ -3441,12 +3441,12 @@ ...@@ -3441,12 +3441,12 @@
<description>Power supply status</description> <description>Power supply status</description>
<field type="uint16_t" name="Vcc">5V rail voltage in millivolts</field> <field type="uint16_t" name="Vcc">5V rail voltage in millivolts</field>
<field type="uint16_t" name="Vservo">servo rail voltage in millivolts</field> <field type="uint16_t" name="Vservo">servo rail voltage in millivolts</field>
<field type="uint16_t" name="flags" enum="MAV_POWER_STATUS">power supply status flags (see MAV_POWER_STATUS enum)</field> <field type="uint16_t" name="flags" enum="MAV_POWER_STATUS" display="bitmask">power supply status flags (see MAV_POWER_STATUS enum)</field>
</message> </message>
<message name="SERIAL_CONTROL" id="126"> <message name="SERIAL_CONTROL" id="126">
<description>Control a serial port. This can be used for raw access to an onboard serial peripheral such as a GPS or telemetry radio. It is designed to make it possible to update the devices firmware via MAVLink messages or change the devices settings. A message with zero bytes can be used to change just the baudrate.</description> <description>Control a serial port. This can be used for raw access to an onboard serial peripheral such as a GPS or telemetry radio. It is designed to make it possible to update the devices firmware via MAVLink messages or change the devices settings. A message with zero bytes can be used to change just the baudrate.</description>
<field type="uint8_t" name="device" enum="SERIAL_CONTROL_DEV">See SERIAL_CONTROL_DEV enum</field> <field type="uint8_t" name="device" enum="SERIAL_CONTROL_DEV">See SERIAL_CONTROL_DEV enum</field>
<field type="uint8_t" name="flags" enum="SERIAL_CONTROL_FLAG">See SERIAL_CONTROL_FLAG enum</field> <field type="uint8_t" name="flags" enum="SERIAL_CONTROL_FLAG" display="bitmask">See SERIAL_CONTROL_FLAG enum</field>
<field type="uint16_t" name="timeout">Timeout for reply data in milliseconds</field> <field type="uint16_t" name="timeout">Timeout for reply data in milliseconds</field>
<field type="uint32_t" name="baudrate">Baudrate of transfer. Zero means no change.</field> <field type="uint32_t" name="baudrate">Baudrate of transfer. Zero means no change.</field>
<field type="uint8_t" name="count">how many bytes in this transfer</field> <field type="uint8_t" name="count">how many bytes in this transfer</field>
...@@ -3652,7 +3652,7 @@ ...@@ -3652,7 +3652,7 @@
</message> </message>
<message id="148" name="AUTOPILOT_VERSION"> <message id="148" name="AUTOPILOT_VERSION">
<description>Version and capability of autopilot software</description> <description>Version and capability of autopilot software</description>
<field type="uint64_t" name="capabilities" enum="MAV_PROTOCOL_CAPABILITY">bitmask of capabilities (see MAV_PROTOCOL_CAPABILITY enum)</field> <field type="uint64_t" name="capabilities" enum="MAV_PROTOCOL_CAPABILITY" display="bitmask">bitmask of capabilities (see MAV_PROTOCOL_CAPABILITY enum)</field>
<field type="uint32_t" name="flight_sw_version">Firmware version number</field> <field type="uint32_t" name="flight_sw_version">Firmware version number</field>
<field type="uint32_t" name="middleware_sw_version">Middleware version number</field> <field type="uint32_t" name="middleware_sw_version">Middleware version number</field>
<field type="uint32_t" name="os_sw_version">Operating system version number</field> <field type="uint32_t" name="os_sw_version">Operating system version number</field>
...@@ -3679,7 +3679,7 @@ ...@@ -3679,7 +3679,7 @@
<message id="230" name="ESTIMATOR_STATUS"> <message id="230" name="ESTIMATOR_STATUS">
<description>Estimator status message including flags, innovation test ratios and estimated accuracies. The flags message is an integer bitmask containing information on which EKF outputs are valid. See the ESTIMATOR_STATUS_FLAGS enum definition for further information. The innovaton test ratios show the magnitude of the sensor innovation divided by the innovation check threshold. Under normal operation the innovaton test ratios should be below 0.5 with occasional values up to 1.0. Values greater than 1.0 should be rare under normal operation and indicate that a measurement has been rejected by the filter. The user should be notified if an innovation test ratio greater than 1.0 is recorded. Notifications for values in the range between 0.5 and 1.0 should be optional and controllable by the user.</description> <description>Estimator status message including flags, innovation test ratios and estimated accuracies. The flags message is an integer bitmask containing information on which EKF outputs are valid. See the ESTIMATOR_STATUS_FLAGS enum definition for further information. The innovaton test ratios show the magnitude of the sensor innovation divided by the innovation check threshold. Under normal operation the innovaton test ratios should be below 0.5 with occasional values up to 1.0. Values greater than 1.0 should be rare under normal operation and indicate that a measurement has been rejected by the filter. The user should be notified if an innovation test ratio greater than 1.0 is recorded. Notifications for values in the range between 0.5 and 1.0 should be optional and controllable by the user.</description>
<field type="uint64_t" name="time_usec">Timestamp (micros since boot or Unix epoch)</field> <field type="uint64_t" name="time_usec">Timestamp (micros since boot or Unix epoch)</field>
<field name="flags" type="uint16_t" enum="ESTIMATOR_STATUS_FLAGS">Integer bitmask indicating which EKF outputs are valid. See definition for ESTIMATOR_STATUS_FLAGS.</field> <field name="flags" type="uint16_t" enum="ESTIMATOR_STATUS_FLAGS" display="bitmask">Integer bitmask indicating which EKF outputs are valid. See definition for ESTIMATOR_STATUS_FLAGS.</field>
<field name="vel_ratio" type="float">Velocity innovation test ratio</field> <field name="vel_ratio" type="float">Velocity innovation test ratio</field>
<field name="pos_horiz_ratio" type="float">Horizontal position innovation test ratio</field> <field name="pos_horiz_ratio" type="float">Horizontal position innovation test ratio</field>
<field name="pos_vert_ratio" type="float">Vertical position innovation test ratio</field> <field name="pos_vert_ratio" type="float">Vertical position innovation test ratio</field>
...@@ -3704,7 +3704,7 @@ ...@@ -3704,7 +3704,7 @@
<description>GPS sensor input message. This is a raw sensor value sent by the GPS. This is NOT the global position estimate of the sytem.</description> <description>GPS sensor input message. This is a raw sensor value sent by the GPS. This is NOT the global position estimate of the sytem.</description>
<field type="uint64_t" name="time_usec">Timestamp (micros since boot or Unix epoch)</field> <field type="uint64_t" name="time_usec">Timestamp (micros since boot or Unix epoch)</field>
<field type="uint8_t" name="gps_id">ID of the GPS for multiple GPS inputs</field> <field type="uint8_t" name="gps_id">ID of the GPS for multiple GPS inputs</field>
<field type="uint16_t" name="ignore_flags" enum="GPS_INPUT_IGNORE_FLAGS">Flags indicating which fields to ignore (see GPS_INPUT_IGNORE_FLAGS enum). All other fields must be provided.</field> <field type="uint16_t" name="ignore_flags" enum="GPS_INPUT_IGNORE_FLAGS" display="bitmask">Flags indicating which fields to ignore (see GPS_INPUT_IGNORE_FLAGS enum). All other fields must be provided.</field>
<field type="uint32_t" name="time_week_ms">GPS time (milliseconds from start of GPS week)</field> <field type="uint32_t" name="time_week_ms">GPS time (milliseconds from start of GPS week)</field>
<field type="uint16_t" name="time_week">GPS week number</field> <field type="uint16_t" name="time_week">GPS week number</field>
<field type="uint8_t" name="fix_type">0-1: no fix, 2: 2D fix, 3: 3D fix. 4: 3D with DGPS. 5: 3D with RTK</field> <field type="uint8_t" name="fix_type">0-1: no fix, 2: 2D fix, 3: 3D fix. 4: 3D with DGPS. 5: 3D with RTK</field>
...@@ -3729,7 +3729,7 @@ ...@@ -3729,7 +3729,7 @@
</message> </message>
<message id="234" name="HIGH_LATENCY"> <message id="234" name="HIGH_LATENCY">
<description>Message appropriate for high latency connections like Iridium</description> <description>Message appropriate for high latency connections like Iridium</description>
<field name="base_mode" type="uint8_t" enum="MAV_MODE_FLAG">System mode bitfield, see MAV_MODE_FLAG ENUM in mavlink/include/mavlink_types.h</field> <field name="base_mode" type="uint8_t" enum="MAV_MODE_FLAG" display="bitmask">System mode bitfield, see MAV_MODE_FLAG ENUM in mavlink/include/mavlink_types.h</field>
<field name="custom_mode" type="uint32_t">A bitfield for use for autopilot-specific flags.</field> <field name="custom_mode" type="uint32_t">A bitfield for use for autopilot-specific flags.</field>
<field name="landed_state" type="uint8_t" enum="MAV_LANDED_STATE">The landed state. Is set to MAV_LANDED_STATE_UNDEFINED if landed state is unknown.</field> <field name="landed_state" type="uint8_t" enum="MAV_LANDED_STATE">The landed state. Is set to MAV_LANDED_STATE_UNDEFINED if landed state is unknown.</field>
<field name="roll" type="int16_t">roll (centidegrees)</field> <field name="roll" type="int16_t">roll (centidegrees)</field>
...@@ -3814,7 +3814,7 @@ ...@@ -3814,7 +3814,7 @@
<field type="char[9]" name="callsign">The callsign, 8+null</field> <field type="char[9]" name="callsign">The callsign, 8+null</field>
<field type="uint8_t" name="emitter_type" enum="ADSB_EMITTER_TYPE">Type from ADSB_EMITTER_TYPE enum</field> <field type="uint8_t" name="emitter_type" enum="ADSB_EMITTER_TYPE">Type from ADSB_EMITTER_TYPE enum</field>
<field type="uint8_t" name="tslc">Time since last communication in seconds</field> <field type="uint8_t" name="tslc">Time since last communication in seconds</field>
<field type="uint16_t" name="flags" enum="ADSB_FLAGS">Flags to indicate various statuses including valid data fields</field> <field type="uint16_t" name="flags" enum="ADSB_FLAGS" display="bitmask">Flags to indicate various statuses including valid data fields</field>
<field type="uint16_t" name="squawk">Squawk code</field> <field type="uint16_t" name="squawk">Squawk code</field>
</message> </message>
<message id="247" name="COLLISION"> <message id="247" name="COLLISION">
......
message_definitions/uAvionix.xml
View file @ 6b84c348
...@@ -92,7 +92,7 @@ ...@@ -92,7 +92,7 @@
<field type="uint8_t" name="gpsOffsetLat" enum="UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LAT">GPS antenna lateral offset (table 2-36 of DO-282B)</field> <field type="uint8_t" name="gpsOffsetLat" enum="UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LAT">GPS antenna lateral offset (table 2-36 of DO-282B)</field>
<field type="uint8_t" name="gpsOffsetLon" enum="UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LON">GPS antenna longitudinal offset from nose [if non-zero, take position (in meters) divide by 2 and add one] (table 2-37 DO-282B)</field> <field type="uint8_t" name="gpsOffsetLon" enum="UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LON">GPS antenna longitudinal offset from nose [if non-zero, take position (in meters) divide by 2 and add one] (table 2-37 DO-282B)</field>
<field type="uint16_t" name="stallSpeed">Aircraft stall speed in cm/s</field> <field type="uint16_t" name="stallSpeed">Aircraft stall speed in cm/s</field>
<field type="uint8_t" name="rfSelect" enum="UAVIONIX_ADSB_OUT_RF_SELECT">ADS-B transponder reciever and transmit enable flags</field> <field type="uint8_t" name="rfSelect" enum="UAVIONIX_ADSB_OUT_RF_SELECT" display="bitmask">ADS-B transponder reciever and transmit enable flags</field>
</message> </message>
<message id="10002" name="UAVIONIX_ADSB_OUT_DYNAMIC"> <message id="10002" name="UAVIONIX_ADSB_OUT_DYNAMIC">
<description>Dynamic data used to generate ADS-B out transponder data (send at 5Hz)</description> <description>Dynamic data used to generate ADS-B out transponder data (send at 5Hz)</description>
...@@ -110,12 +110,12 @@ ...@@ -110,12 +110,12 @@
<field type="int16_t" name="velNS">North-South velocity over ground in cm/s North +ve. If unknown set to INT16_MAX</field> <field type="int16_t" name="velNS">North-South velocity over ground in cm/s North +ve. If unknown set to INT16_MAX</field>
<field type="int16_t" name="VelEW">East-West velocity over ground in cm/s East +ve. If unknown set to INT16_MAX</field> <field type="int16_t" name="VelEW">East-West velocity over ground in cm/s East +ve. If unknown set to INT16_MAX</field>
<field type="uint8_t" name="emergencyStatus" enum="UAVIONIX_ADSB_EMERGENCY_STATUS">Emergency status</field> <field type="uint8_t" name="emergencyStatus" enum="UAVIONIX_ADSB_EMERGENCY_STATUS">Emergency status</field>
<field type="uint16_t" name="state" enum="UAVIONIX_ADSB_OUT_DYNAMIC_STATE">ADS-B transponder dynamic input state flags</field> <field type="uint16_t" name="state" enum="UAVIONIX_ADSB_OUT_DYNAMIC_STATE" display="bitmask">ADS-B transponder dynamic input state flags</field>
<field type="uint16_t" name="squawk">Mode A code (typically 1200 [0x04B0] for VFR)</field> <field type="uint16_t" name="squawk">Mode A code (typically 1200 [0x04B0] for VFR)</field>
</message> </message>
<message id="10003" name="UAVIONIX_ADSB_TRANSCEIVER_HEALTH_REPORT"> <message id="10003" name="UAVIONIX_ADSB_TRANSCEIVER_HEALTH_REPORT">
<description>Transceiver heartbeat with health report (updated every 10s)</description> <description>Transceiver heartbeat with health report (updated every 10s)</description>
<field type="uint8_t" name="rfHealth" enum="UAVIONIX_ADSB_RF_HEALTH">ADS-B transponder messages</field> <field type="uint8_t" name="rfHealth" enum="UAVIONIX_ADSB_RF_HEALTH" display="bitmask">ADS-B transponder messages</field>
</message> </message>
</messages> </messages>
</mavlink> </mavlink>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7