PX4 Build Bot
138 KiB
Dialect: development
This dialect contains messages that are proposed for inclusion in the common set, in order to ease development of prototype implementations. They should be considered a 'work in progress' and not included in production builds.
This topic is a human-readable form of the XML definition file: development.xml.
::: info
- MAVLink 2 extension fields are displayed in blue.
- Entities from dialects are displayed only as headings (with link to original)
:::
<style> span.ext { color: blue; } span.warning { color: red; } </style>Protocol dialect: 0
Protocol version: 0
MAVLink Include Files
概览
| Type | Defined | Included |
|---|---|---|
| Messages | 14 | 234 |
| Enums | 15 | 158 |
| Commands | 178 | 0 |
The following sections list all entities in the dialect (both included and defined in this file).
消息
ESC_EEPROM (292) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
ESC EEPROM data message for reading and writing ESC configuration.
Supports multiple ESC firmware types including AM32, Bluejay, and BLHeli32.
ESC data is read by sending the MAV_CMD_REQUEST_MESSAGE with param1=292 and param2=esc_index, where esc_index is the zero-indexed ESC number for the corresponding motor, and 255 is used to request data for all ESC.
The message can be sent to set the ESC value.
For write requests, a bitmask allows selective writing of specific bytes to avoid corrupting unchanged values.
The data format is opaque to the autopilot. A GCS is required to understand the format in order to create an appropriate UI for display and setting configuration values, and to inform users when the ESC uses an unsupported data format. Note that for AM32 EEPROMs the data layout is defined in: https://github.com/am32-firmware/AM32/blob/main/Inc/eeprom.h (the second byte in the structure is the eeprom_version). The firmware field indicates which ESC firmware is in use, allowing the GCS to interpret the data correctly.
| Field Name | Type | 值 | 描述 |
|---|---|---|---|
| target_system | uint8_t |
System ID (ID of target system, normally flight controller). | |
| target_component | uint8_t |
Component ID (normally 0 for broadcast). | |
| firmware | uint8_t |
ESC_FIRMWARE | ESC firmware type. |
| msg_index | uint8_t |
Zero-indexed sequence number of this message when multiple messages are required to transfer the complete EEPROM data. The first message has index 0. For single-message transfers, set to 0. | |
| msg_count | uint8_t |
Total number of messages required to transfer the complete EEPROM data. For single-message transfers, set to 1. Receivers should collect all messages from index 0 to msg_count-1 before reconstructing the complete data. | |
| esc_index | uint8_t |
max:254 | Index of the ESC (0 = ESC1, 1 = ESC2, etc.). |
| write_mask | uint32_t[6] |
Bitmask indicating which bytes in the data array should be written. Each bit corresponds to a byte index in the data array (bit 0 of write_mask[0] = data[0], bit 31 of write_mask[0] = data[31], bit 0 of write_mask[1] = data[32], etc.). Set bits indicate bytes to write, cleared bits indicate bytes to skip. This allows precise updates of individual parameters without overwriting the entire EEPROM. | |
| length | uint8_t |
max:222 | Number of valid bytes in data array. |
| data | uint8_t[192] |
Raw ESC EEPROM data. Unused bytes should be set to zero. |
SET_VELOCITY_LIMITS (354) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Set temporary maximum limits for horizontal speed, vertical speed and yaw rate.
The consumer must stream the current limits in VELOCITY_LIMITS at 1 Hz or more (when limits are being set). The consumer should latch the limits until a new limit is received or the mode is changed.
| Field Name | Type | Units | 描述 |
|---|---|---|---|
| target_system | uint8_t |
System ID (0 for broadcast). | |
| target_component | uint8_t |
Component ID (0 for broadcast). | |
| horizontal_speed_limit | float |
m/s | Limit for horizontal movement in MAV_FRAME_LOCAL_NED. NaN: Field not used (ignore) |
| vertical_speed_limit | float |
m/s | Limit for vertical movement in MAV_FRAME_LOCAL_NED. NaN: Field not used (ignore) |
| yaw_rate_limit | float |
rad/s | Limit for vehicle turn rate around its yaw axis. NaN: Field not used (ignore) |
VELOCITY_LIMITS (355) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Current limits for horizontal speed, vertical speed and yaw rate, as set by SET_VELOCITY_LIMITS.
| Field Name | Type | Units | 描述 |
|---|---|---|---|
| horizontal_speed_limit | float |
m/s | Limit for horizontal movement in MAV_FRAME_LOCAL_NED. NaN: No limit applied |
| vertical_speed_limit | float |
m/s | Limit for vertical movement in MAV_FRAME_LOCAL_NED. NaN: No limit applied |
| yaw_rate_limit | float |
rad/s | Limit for vehicle turn rate around its yaw axis. NaN: No limit applied |
BATTERY_STATUS_V2 (369) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Battery dynamic information.
This should be streamed (nominally at 1Hz). Static/invariant battery information is sent in BATTERY_INFO. Note that smart batteries should set the MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL bit to indicate that supplied capacity values are relative to a battery that is known to be full. Power monitors would not set this bit, indicating that capacity_consumed is relative to drone power-on, and that other values are estimated based on the assumption that the battery was full on power-on.
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| id | uint8_t |
Battery ID [Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
||
| temperature | int16_t |
cdegC | invalid:INT16_MAX | Temperature of the whole battery pack (not internal electronics). INT16_MAX field not provided. |
| voltage | float |
V | invalid:NaN | Battery voltage (total). NaN: field not provided. |
| current | float |
A | invalid:NaN | Battery current (through all cells/loads). Positive value when discharging and negative if charging. NaN: field not provided. |
| capacity_consumed | float |
Ah | invalid:NaN | Consumed charge. NaN: field not provided. This is either the consumption since power-on or since the battery was full, depending on the value of MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL. |
| capacity_remaining | float |
Ah | invalid:NaN | Remaining charge (until empty). NaN: field not provided. Note: If MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL is unset, this value is based on the assumption the battery was full when the system was powered. |
| percent_remaining | uint8_t |
% | invalid:UINT8_MAX | Remaining battery energy. Values: [0-100], UINT8_MAX: field not provided. |
| status_flags | uint32_t |
MAV_BATTERY_STATUS_FLAGS | Fault, health, readiness, and other status indications. |
GROUP_START (414) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Emitted during mission execution when control reaches MAV_CMD_GROUP_START.
| Field Name | Type | Units | 描述 |
|---|---|---|---|
| group_id | uint32_t |
Mission-unique group id (from MAV_CMD_GROUP_START). | |
| mission_checksum | uint32_t |
CRC32 checksum of current plan for MAV_MISSION_TYPE_ALL. As defined in MISSION_CHECKSUM message. | |
| time_usec | uint64_t |
us | Timestamp (UNIX Epoch time or time since system boot). The receiving end can infer timestamp format (since 1.1.1970 or since system boot) by checking for the magnitude of the number. |
GROUP_END (415) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Emitted during mission execution when control reaches MAV_CMD_GROUP_END.
| Field Name | Type | Units | 描述 |
|---|---|---|---|
| group_id | uint32_t |
Mission-unique group id (from MAV_CMD_GROUP_END). | |
| mission_checksum | uint32_t |
CRC32 checksum of current plan for MAV_MISSION_TYPE_ALL. As defined in MISSION_CHECKSUM message. | |
| time_usec | uint64_t |
us | Timestamp (UNIX Epoch time or time since system boot). The receiving end can infer timestamp format (since 1.1.1970 or since system boot) by checking for the magnitude of the number. |
RADIO_RC_CHANNELS (420) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
RC channel outputs from a MAVLink RC receiver for input to a flight controller or other components (allows an RC receiver to connect via MAVLink instead of some other protocol such as PPM-Sum or S.BUS).
Note that this is not intended to be an over-the-air format, and does not replace RC_CHANNELS and similar messages reported by the flight controller. The target_system field should normally be set to the system id of the system to control, typically the flight controller. The target_component field can normally be set to 0, so that all components of the system can receive the message. The channels array field can publish up to 32 channels; the number of channel items used in the array is specified in the count field. The time_last_update_ms field contains the timestamp of the last received valid channels data in the receiver's time domain. The count field indicates the first index of the channel array that is not used for channel data (this and later indexes are zero-filled). The RADIO_RC_CHANNELS_FLAGS_OUTDATED flag is set by the receiver if the channels data is not up-to-date (for example, if new data from the transmitter could not be validated so the last valid data is resent). The RADIO_RC_CHANNELS_FLAGS_FAILSAFE failsafe flag is set by the receiver if the receiver's failsafe condition is met (implementation dependent, e.g., connection to the RC radio is lost). In this case time_last_update_ms still contains the timestamp of the last valid channels data, but the content of the channels data is not defined by the protocol (it is up to the implementation of the receiver). For instance, the channels data could contain failsafe values configured in the receiver; the default is to carry the last valid data. Note: The RC channels fields are extensions to ensure that they are located at the end of the serialized payload and subject to MAVLink's trailing-zero trimming.
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| target_system | uint8_t |
System ID (ID of target system, normally flight controller). | ||
| target_component | uint8_t |
Component ID (normally 0 for broadcast). | ||
| time_last_update_ms | uint32_t |
ms | Time when the data in the channels field were last updated (time since boot in the receiver's time domain). | |
| flags | uint16_t |
RADIO_RC_CHANNELS_FLAGS | Radio RC channels status flags. | |
| count | uint8_t |
Total number of RC channels being received. This can be larger than 32, indicating that more channels are available but not given in this message. | ||
| channels ++ | int16_t[32] |
min:-4096 max:4096 | RC channels. Channel values are in centered 13 bit format. Range is -4096 to 4096, center is 0. Conversion to PWM is x * 5/32 + 1500. Channels with indexes equal or above count should be set to 0, to benefit from MAVLink's trailing-zero trimming. |
RC_CHANNELS_OVERRIDE_V2 (421) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Highly bandwidth-efficient RC override message for professional networked operations (LTE, Zigbee, GCP). Supersedes RC_CHANNELS_OVERRIDE by adding 32-channel support and a bitmask for multi-master conflict avoidance. Uses centered-at-zero values and extension-field placement to maximize MAVLink 2 trailing-zero truncation.
| Field Name | Type | 描述 |
|---|---|---|
| target_system | uint8_t |
System ID. |
| target_component | uint8_t |
Component ID. |
| active_mask | uint32_t |
Bitmap of included channels (bit 0 = CH1). 1: Valid/Override, 0: Ignore. |
| channels ++ | int16_t[32] |
RC channels in centered 13-bit format. Range: -4096 to 4096, Center: 0. Conversion to PWM: (x * 5/32) + 1500. Unused channels must be set to 0 to enable MAVLink 2 trailing-zero trimming. |
GNSS_INTEGRITY (441) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Information about key components of GNSS receivers, like signal authentication, interference and system errors.
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| id | uint8_t |
GNSS receiver id. Must match instance ids of other messages from same receiver. [Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
||
| system_errors | uint32_t |
GPS_SYSTEM_ERROR_FLAGS | Errors in the GPS system. | |
| authentication_state | uint8_t |
GPS_AUTHENTICATION_STATE | Signal authentication state of the GPS system. | |
| jamming_state | uint8_t |
GPS_JAMMING_STATE | Signal jamming state of the GPS system. | |
| spoofing_state | uint8_t |
GPS_SPOOFING_STATE | Signal spoofing state of the GPS system. | |
| raim_state | uint8_t |
GPS_RAIM_STATE | The state of the RAIM processing. | |
| raim_hfom | uint16_t |
厘米 | invalid:UINT16_MAX | Horizontal expected accuracy using satellites successfully validated using RAIM. |
| raim_vfom | uint16_t |
厘米 | invalid:UINT16_MAX | Vertical expected accuracy using satellites successfully validated using RAIM. |
| corrections_quality | uint8_t |
invalid:UINT8_MAX min:0 max:10 | An abstract value representing the estimated quality of incoming corrections, or 255 if not available. | |
| system_status_summary | uint8_t |
invalid:UINT8_MAX min:0 max:10 | An abstract value representing the overall status of the receiver, or 255 if not available. | |
| gnss_signal_quality | uint8_t |
invalid:UINT8_MAX min:0 max:10 | An abstract value representing the quality of incoming GNSS signals, or 255 if not available. | |
| post_processing_quality | uint8_t |
invalid:UINT8_MAX min:0 max:10 | An abstract value representing the estimated PPK quality, or 255 if not available. |
TARGET_ABSOLUTE (510) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Current motion information from sensors on a target
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| timestamp | uint64_t |
us | Timestamp (UNIX epoch time). | |
| id | uint8_t |
The ID of the target if multiple targets are present | ||
| sensor_capabilities | uint8_t |
TARGET_ABSOLUTE_SENSOR_CAPABILITY_FLAGS | Bitmap to indicate the sensor's reporting capabilities | |
| lat | int32_t |
degE7 | Target's latitude (WGS84) | |
| lon | int32_t |
degE7 | Target's longitude (WGS84) | |
| alt | float |
m | Target's altitude (AMSL) | |
| vel | float[3] |
m/s | invalid:[0] | Target's velocity in its body frame |
| acc | float[3] |
m/s/s | invalid:[0] | Linear target's acceleration in its body frame |
| q_target | float[4] |
invalid:[0] | Quaternion of the target's orientation from its body frame to the vehicle's NED frame. | |
| rates | float[3] |
rad/s | invalid:[0] | Target's roll, pitch and yaw rates |
| position_std | float[2] |
m | Standard deviation of horizontal (eph) and vertical (epv) position errors | |
| vel_std | float[3] |
m/s | Standard deviation of the target's velocity in its body frame | |
| acc_std | float[3] |
m/s/s | Standard deviation of the target's acceleration in its body frame |
TARGET_RELATIVE (511) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
The location of a target measured by MAV's onboard sensors.
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| timestamp | uint64_t |
us | Timestamp (UNIX epoch time) | |
| id | uint8_t |
The ID of the target if multiple targets are present [Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
||
| frame | uint8_t |
TARGET_OBS_FRAME | Coordinate frame used for following fields. | |
| x | float |
m | X Position of the target in TARGET_OBS_FRAME | |
| y | float |
m | Y Position of the target in TARGET_OBS_FRAME | |
| z | float |
m | Z Position of the target in TARGET_OBS_FRAME | |
| pos_std | float[3] |
m | Standard deviation of the target's position in TARGET_OBS_FRAME | |
| yaw_std | float |
rad | Standard deviation of the target's orientation in TARGET_OBS_FRAME | |
| q_target | float[4] |
Quaternion of the target's orientation from the target's frame to the TARGET_OBS_FRAME (w, x, y, z order, zero-rotation is 1, 0, 0, 0) | ||
| q_sensor | float[4] |
Quaternion of the sensor's orientation from TARGET_OBS_FRAME to vehicle-carried NED. (Ignored if set to (0,0,0,0)) (w, x, y, z order, zero-rotation is 1, 0, 0, 0) | ||
| type | uint8_t |
LANDING_TARGET_TYPE | Type of target |
CONTROL_STATUS (512) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Information about GCS(s) in control of this MAV.
This should be broadcast at low rate (nominally 1 Hz) and emitted when ownership or takeover status change.
Components in the system should only accept "state changing commands/messages" from any system id in gcs_main or gcs_secondary.
- In single-owner mode there is a single GCS that can send "state changing commands/messages" listed in
gcs_main(gcs_secondarymust be set to all-zero). - In multi-owner mode, all GCS with ids in
gcs_mainandgcs_secondarycan send "state changing commands/messages". Howevergcs_mainis the only GCS that can perform "special controlled operations" such as manual control. - Control over ownership of the
gcs_mainrole is requested using MAV_CMD_REQUEST_OPERATOR_CONTROL. - GCS in
gcs_secondaryare set by the flight stack (cannot be set by this mechanism). It should only include IDs for connected GCS. If more than 11 GCS are in control and visible, the flight stack will at most be able to publish 11.
| Field Name | Type | 值 | 描述 |
|---|---|---|---|
| flags | uint8_t |
GCS_CONTROL_STATUS_FLAGS | Control status. For example, whether takeover of the gcs_main role is allowed, and whether this CONTROL_STATUS instance defines the default controlling GCS for the whole system. |
| gcs_main | uint8_t |
invalid:0 | System ID of GCS in control. 0: no GCS in control. |
| gcs_secondary | uint8_t[10] |
invalid:[0,] | System IDs from which the system can recieve state-changing commands/messages in multi-control mode. All values should be zero for single-ower mode. |
RANGING_BEACON (513) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Range information from a radio beacon for trilateration-based positioning.
This message is telemetry intended for consumption by an autopilot (MAVLink does not define the mechanism used to determine the range).
| Field Name | Type | Units | 值 | 描述 |
|---|---|---|---|---|
| time_usec | uint64_t |
us | Timestamp (UNIX Epoch time or time since system boot). The receiving end can infer timestamp format (since 1.1.1970 or since system boot) by checking for the magnitude of the number. | |
| target_system | uint8_t |
System ID. | ||
| target_component | uint8_t |
Component ID. | ||
| beacon_id | uint16_t |
ID of the ranging beacon/station. [Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
||
| range | uint32_t |
毫米 | invalid:UINT32_MAX | Range measurement between a beacon and a vehicle. |
| lat | int32_t |
degE7 | invalid:INT32_MAX | Beacon latitude (WGS84). |
| lon | int32_t |
degE7 | invalid:INT32_MAX | Beacon longitude (WGS84). |
| alt | float |
m | invalid:NaN | Beacon altitude (frame defined in alt_type). |
| alt_type | uint8_t |
RANGING_BEACON_ALT_TYPE | Altitude frame for alt field. RANGING_BEACON_ALT_TYPE_WGS84 (0) preferred. | |
| hacc_est | uint32_t |
毫米 | invalid:UINT32_MAX | Beacon 1-sigma horizontal accuracy estimate. |
| vacc_est | uint32_t |
毫米 | invalid:UINT32_MAX | Beacon 1-sigma vertical accuracy estimate. |
| carrier_freq | uint16_t |
MHz | invalid:UINT16_MIN | Ranging carrier frequency |
| range_accuracy | uint32_t |
毫米 | invalid:UINT32_MAX | Estimated 1-sigma range measurement accuracy. |
| sequence | uint8_t |
Measurement sequence number. | ||
| status | uint8_t |
RANGING_BEACON_STATUS_FLAG | Ranging beacon status. |
ESTIMATOR_SENSOR_FUSION_STATUS (514) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Status of estimator sensor fusion sources. Each array is indexed by ESTIMATOR_SENSOR_FUSION_SOURCE - 1. Each element is a per-instance bitmask (bit 0 = instance 0, etc.). For single-instance sources only bit 0 is used. For multi-instance sources like AGP, multiple bits may be set.
| Field Name | Type | 描述 |
|---|---|---|
| intended | uint8_t[9] |
Per-source instance bitmask of sensors the estimator intends to fuse (reflects CTRL params with runtime overrides via MAV_CMD_ESTIMATOR_SENSOR_ENABLE). |
| active | uint8_t[9] |
Per-source instance bitmask of sensors the estimator is actively fusing. |
| test_ratio | float[9] |
Per-source normalized innovation test ratio. NaN if not available. |
Enumerated Types
MAV_BATTERY_STATUS_FLAGS — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) Battery status flags for fault, health and state indication.
| 值 | Name | 描述 |
|---|---|---|
| 1 | MAV_BATTERY_STATUS_FLAGS_NOT_READY_TO_USE | The battery is not ready to use (fly). Set if the battery has faults or other conditions that make it unsafe to fly with. Note: It will be the logical OR of other status bits (chosen by the manufacturer/integrator). |
| 2 | MAV_BATTERY_STATUS_FLAGS_CHARGING | Battery is charging. |
| 4 | MAV_BATTERY_STATUS_FLAGS_CELL_BALANCING | Battery is cell balancing (during charging). Not ready to use (MAV_BATTERY_STATUS_FLAGS_NOT_READY_TO_USE may be set). |
| 8 | MAV_BATTERY_STATUS_FLAGS_FAULT_CELL_IMBALANCE | Battery cells are not balanced. Not ready to use. |
| 16 | MAV_BATTERY_STATUS_FLAGS_AUTO_DISCHARGING | Battery is auto discharging (towards storage level). Not ready to use (MAV_BATTERY_STATUS_FLAGS_NOT_READY_TO_USE would be set). |
| 32 | MAV_BATTERY_STATUS_FLAGS_REQUIRES_SERVICE | Battery requires service (not safe to fly). This is set at vendor discretion. It is likely to be set for most faults, and may also be set according to a maintenance schedule (such as age, or number of recharge cycles, etc.). |
| 64 | MAV_BATTERY_STATUS_FLAGS_BAD_BATTERY | Battery is faulty and cannot be repaired (not safe to fly). This is set at vendor discretion. The battery should be disposed of safely. |
| 128 | MAV_BATTERY_STATUS_FLAGS_PROTECTIONS_ENABLED | Automatic battery protection monitoring is enabled. When enabled, the system will monitor for certain kinds of faults, such as cells being over-voltage. If a fault is triggered then and protections are enabled then a safety fault (MAV_BATTERY_STATUS_FLAGS_FAULT_PROTECTION_SYSTEM) will be set and power from the battery will be stopped. Note that battery protection monitoring should only be enabled when the vehicle is landed. Once the vehicle is armed, or starts moving, the protections should be disabled to prevent false positives from disabling the output. |
| 256 | MAV_BATTERY_STATUS_FLAGS_FAULT_PROTECTION_SYSTEM | The battery fault protection system had detected a fault and cut all power from the battery. This will only trigger if MAV_BATTERY_STATUS_FLAGS_PROTECTIONS_ENABLED is set. Other faults like MAV_BATTERY_STATUS_FLAGS_FAULT_OVER_VOLT may also be set, indicating the cause of the protection fault. |
| 512 | MAV_BATTERY_STATUS_FLAGS_FAULT_OVER_VOLT | One or more cells are above their maximum voltage rating. |
| 1024 | MAV_BATTERY_STATUS_FLAGS_FAULT_UNDER_VOLT | One or more cells are below their minimum voltage rating. A battery that had deep-discharged might be irrepairably damaged, and set both MAV_BATTERY_STATUS_FLAGS_FAULT_UNDER_VOLT and MAV_BATTERY_STATUS_FLAGS_BAD_BATTERY. |
| 2048 | MAV_BATTERY_STATUS_FLAGS_FAULT_OVER_TEMPERATURE | Over-temperature fault. |
| 4096 | MAV_BATTERY_STATUS_FLAGS_FAULT_UNDER_TEMPERATURE | Under-temperature fault. |
| 8192 | MAV_BATTERY_STATUS_FLAGS_FAULT_OVER_CURRENT | Over-current fault. |
| 16384 | MAV_BATTERY_STATUS_FLAGS_FAULT_SHORT_CIRCUIT | Short circuit event detected. The battery may or may not be safe to use (check other flags). |
| 32768 | MAV_BATTERY_STATUS_FLAGS_FAULT_INCOMPATIBLE_VOLTAGE | Voltage not compatible with power rail voltage (batteries on same power rail should have similar voltage). |
| 65536 | MAV_BATTERY_STATUS_FLAGS_FAULT_INCOMPATIBLE_FIRMWARE | Battery firmware is not compatible with current autopilot firmware. |
| 131072 | MAV_BATTERY_STATUS_FLAGS_FAULT_INCOMPATIBLE_CELLS_CONFIGURATION | Battery is not compatible due to cell configuration (e.g. 5s1p when vehicle requires 6s). |
| 262144 | MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL | Battery capacity_consumed and capacity_remaining values are relative to a full battery (they sum to the total capacity of the battery). This flag would be set for a smart battery that can accurately determine its remaining charge across vehicle reboots and discharge/recharge cycles. If unset the capacity_consumed indicates the consumption since vehicle power-on, as measured using a power monitor. The capacity_remaining, if provided, indicates the estimated remaining capacity on the assumption that the battery was full on vehicle boot. If unset a GCS is recommended to advise that users fully charge the battery on power on. |
| 2147483648 | MAV_BATTERY_STATUS_FLAGS_EXTENDED | Reserved (not used). If set, this will indicate that an additional status field exists for higher status values. |
GCS_CONTROL_STATUS_FLAGS — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) CONTROL_STATUS flags.
| 值 | Name | 描述 |
|---|---|---|
| 1 | GCS_CONTROL_STATUS_FLAGS_SYSTEM_MANAGER | If set, this CONTROL_STATUS publishes the controlling GCS(s) of the whole system. If unset, the CONTROL_STATUS indicates the controlling GCS(s) for just the component emitting the message. Note that to request control of the system a GCS should send MAV_CMD_REQUEST_OPERATOR_CONTROL to the component emitting CONTROL_STATUS with this flag set. |
| 2 | GCS_CONTROL_STATUS_FLAGS_TAKEOVER_ALLOWED | Takeover allowed (requests for control will be granted). If not set requests for control will be rejected, but the controlling GCS will be notified (and may release control or allow takeover). |
TARGET_ABSOLUTE_SENSOR_CAPABILITY_FLAGS — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) These flags indicate the sensor reporting capabilities for TARGET_ABSOLUTE.
TARGET_OBS_FRAME — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
The frame of a target observation from an onboard sensor.
| 值 | Name | 描述 |
|---|---|---|
| 0 | TARGET_OBS_FRAME_LOCAL_NED | NED local tangent frame (x: North, y: East, z: Down) with origin fixed relative to earth. |
| 1 | TARGET_OBS_FRAME_BODY_FRD | FRD local frame aligned to the vehicle's attitude (x: Forward, y: Right, z: Down) with an origin that travels with vehicle. |
| 2 | TARGET_OBS_FRAME_LOCAL_OFFSET_NED | NED local tangent frame (x: North, y: East, z: Down) with an origin that travels with vehicle. |
| 3 | TARGET_OBS_FRAME_OTHER | Other sensor frame for target observations neither in local NED nor in body FRD. |
RADIO_RC_CHANNELS_FLAGS — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) RADIO_RC_CHANNELS flags (bitmask).
| 值 | Name | 描述 |
|---|---|---|
| 1 | RADIO_RC_CHANNELS_FLAGS_FAILSAFE | Failsafe is active. The content of the RC channels data in the RADIO_RC_CHANNELS message is implementation dependent. |
| 2 | RADIO_RC_CHANNELS_FLAGS_OUTDATED | Channel data may be out of date. This is set when the receiver is unable to validate incoming data from the transmitter and has therefore resent the last valid data it received. |
GPS_SYSTEM_ERROR_FLAGS — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) Flags indicating errors in a GPS receiver.
| 值 | Name | 描述 |
|---|---|---|
| 1 | GPS_SYSTEM_ERROR_INCOMING_CORRECTIONS | There are problems with incoming correction streams. |
| 2 | GPS_SYSTEM_ERROR_CONFIGURATION | There are problems with the configuration. |
| 4 | GPS_SYSTEM_ERROR_SOFTWARE | There are problems with the software on the GPS receiver. |
| 8 | GPS_SYSTEM_ERROR_ANTENNA | There are problems with an antenna connected to the GPS receiver. |
| 16 | GPS_SYSTEM_ERROR_EVENT_CONGESTION | There are problems handling all incoming events. |
| 32 | GPS_SYSTEM_ERROR_CPU_OVERLOAD | The GPS receiver CPU is overloaded. |
| 64 | GPS_SYSTEM_ERROR_OUTPUT_CONGESTION | The GPS receiver is experiencing output congestion. |
GPS_AUTHENTICATION_STATE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Signal authentication state in a GPS receiver.
| 值 | Name | 描述 |
|---|---|---|
| 0 | GPS_AUTHENTICATION_STATE_UNKNOWN | The GPS receiver does not provide GPS signal authentication info. |
| 1 | GPS_AUTHENTICATION_STATE_INITIALIZING | The GPS receiver is initializing signal authentication. |
| 2 | GPS_AUTHENTICATION_STATE_ERROR | The GPS receiver encountered an error while initializing signal authentication. |
| 3 | GPS_AUTHENTICATION_STATE_OK | The GPS receiver has correctly authenticated all signals. |
| 4 | GPS_AUTHENTICATION_STATE_DISABLED | GPS signal authentication is disabled on the receiver. |
GPS_JAMMING_STATE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Signal jamming state in a GPS receiver.
| 值 | Name | 描述 |
|---|---|---|
| 0 | GPS_JAMMING_STATE_UNKNOWN | The GPS receiver does not provide GPS signal jamming info. |
| 1 | GPS_JAMMING_STATE_NOT_JAMMED | The GPS receiver detected no signal jamming. |
| 2 | GPS_JAMMING_STATE_MITIGATED | The GPS receiver detected and mitigated signal jamming. |
| 3 | GPS_JAMMING_STATE_DETECTED | The GPS receiver detected signal jamming. |
GPS_SPOOFING_STATE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Signal spoofing state in a GPS receiver.
| 值 | Name | 描述 |
|---|---|---|
| 0 | GPS_SPOOFING_STATE_UNKNOWN | The GPS receiver does not provide GPS signal spoofing info. |
| 1 | GPS_SPOOFING_STATE_NOT_SPOOFED | The GPS receiver detected no signal spoofing. |
| 2 | GPS_SPOOFING_STATE_MITIGATED | The GPS receiver detected and mitigated signal spoofing. |
| 3 | GPS_SPOOFING_STATE_DETECTED | The GPS receiver detected signal spoofing but still has a fix. |
GPS_RAIM_STATE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
State of RAIM processing.
| 值 | Name | 描述 |
|---|---|---|
| 0 | GPS_RAIM_STATE_UNKNOWN | RAIM capability is unknown. |
| 1 | GPS_RAIM_STATE_DISABLED | RAIM is disabled. |
| 2 | GPS_RAIM_STATE_OK | RAIM integrity check was successful. |
| 3 | GPS_RAIM_STATE_FAILED | RAIM integrity check failed. |
ACTUATOR_TEST_GROUP — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Actuator groups to test in MAV_CMD_ACTUATOR_GROUP_TEST.
| 值 | Name | 描述 |
|---|---|---|
| 0 | ACTUATOR_TEST_GROUP_ROLL_TORQUE | Actuators that contribute to roll torque. |
| 1 | ACTUATOR_TEST_GROUP_PITCH_TORQUE | Actuators that contribute to pitch torque. |
| 2 | ACTUATOR_TEST_GROUP_YAW_TORQUE | Actuators that contribute to yaw torque. |
| 3 | ACTUATOR_TEST_GROUP_COLLECTIVE_TILT | Actuators that affect collective tilt. |
| 4 | ACTUATOR_TEST_GROUP_X_THRUST | Actuators that contribute to x (longitudinal, positive = forward) thrust. |
| 5 | ACTUATOR_TEST_GROUP_Y_THRUST | Actuators that contribute to y (lateral, positive = right) thrust. |
| 6 | ACTUATOR_TEST_GROUP_Z_THRUST | Actuators that contribute to z (vertical, positive = down) thrust. |
ESC_FIRMWARE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
ESC firmware type identifier.
| 值 | Name | 描述 |
|---|---|---|
| 0 | ESC_FIRMWARE_UNKNOWN | Unknown firmware. |
| 1 | ESC_FIRMWARE_AM32 | AM32 open source ESC firmware. |
| 2 | ESC_FIRMWARE_BLUEJAY | Bluejay open source ESC firmware. |
| 3 | ESC_FIRMWARE_BLHELI32 | BLHeli32 ESC firmware. |
RANGING_BEACON_ALT_TYPE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Altitude reference for RANGING_BEACON alt field.
| 值 | Name | 描述 |
|---|---|---|
| 0 | RANGING_BEACON_ALT_TYPE_WGS84 | Altitude above WGS84 ellipsoid. |
| 1 | RANGING_BEACON_ALT_TYPE_MSL | Altitude above Mean Sea Level (AMSL). |
RANGING_BEACON_STATUS_FLAG — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
(Bitmask) Status flags for a RANGING_BEACON.
| 值 | Name | 描述 |
|---|---|---|
| 1 | RANGING_BEACON_STATUS_FLAG_STATION_SIGNAL_POOR | Station signal is poor. This might indicate channel fading, interference, or other signal quality issues. |
ESTIMATOR_SENSOR_FUSION_SOURCE — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Estimator sensor fusion source types. Used in MAV_CMD_ESTIMATOR_SENSOR_ENABLE and as array index in ESTIMATOR_SENSOR_FUSION_STATUS.
| 值 | Name | 描述 |
|---|---|---|
| 0 | ESTIMATOR_SENSOR_FUSION_SOURCE_GPS | GNSS |
| 1 | ESTIMATOR_SENSOR_FUSION_SOURCE_OF | Optical Flow |
| 2 | ESTIMATOR_SENSOR_FUSION_SOURCE_EV | External Vision |
| 3 | ESTIMATOR_SENSOR_FUSION_SOURCE_AGP | Auxiliary Global Position |
| 4 | ESTIMATOR_SENSOR_FUSION_SOURCE_BARO | Barometer |
| 5 | ESTIMATOR_SENSOR_FUSION_SOURCE_RNG | Range Finder |
| 6 | ESTIMATOR_SENSOR_FUSION_SOURCE_MAG | Magnetometer |
| 7 | ESTIMATOR_SENSOR_FUSION_SOURCE_ASPD | Airspeed |
| 8 | ESTIMATOR_SENSOR_FUSION_SOURCE_RANGING_BEACON | Ranging Beacon |
Commands (MAV_CMD)
MAV_CMD_ACTUATOR_GROUP_TEST (309) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Command to test groups of related actuators together.
This might include groups such as the actuators that contribute to roll, pitch, or yaw torque, actuators that contribute to thrust in x, y, z axis, tilt mechanisms, flaps and spoilers, and so on. This is similar to MAV_CMD_ACTUATOR_TEST, except that multiple actuators may be affected. Different groups may also affect the same actuators (as in the case of controls that affect torque in different axes). Autopilots must NACK this command with MAV_RESULT_TEMPORARILY_REJECTED while armed.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (Group) | Actuator group to check, such as actuators related to roll torque. | ACTUATOR_TEST_GROUP |
| 2 (Value) | Value to set. This is a normalized value across the full range of the tested group [-1,1]. | min: -1 max: 1 |
MAV_CMD_DO_SET_SYS_CMP_ID (610) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Set system and component id. This allows moving of a system and all its components to a new system id, or moving a particular component to a new system/component id. Recipients must reject command addressed to broadcast system ID.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (System ID) | New system ID for target component(s). 0: ignore and reject command (broadcast system ID not allowed). | min: 1 max: 255 inc: 1 |
| 2 (Component ID) | New component ID for target component(s). 0: ignore (component IDs don't change). | min: 0 max: 255 inc: 1 |
| 3 (Reboot) | Reboot components after ID change. Any non-zero value triggers the reboot. | |
| 4 |
MAV_CMD_DO_SET_GLOBAL_ORIGIN (611) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Sets the GNSS coordinates of the vehicle local origin (0,0,0) position.
Vehicle should emit GPS_GLOBAL_ORIGIN irrespective of whether the origin is changed. This enables transform between the local coordinate frame and the global (GNSS) coordinate frame, which may be necessary when (for example) indoor and outdoor settings are connected and the MAV should move from in- to outdoor. This command supersedes SET_GPS_GLOBAL_ORIGIN. Should be sent in a COMMAND_INT (Expected frame is MAV_FRAME_GLOBAL, and this should be assumed when sent in COMMAND_LONG).
| Param (Label) | 描述 | Units |
|---|---|---|
| 1 | Empty | |
| 2 | Empty | |
| 3 | Empty | |
| 4 | Empty | |
| 5 (Latitude) | Latitude | |
| 6 (Longitude) | Longitude | |
| 7 (Altitude) | Altitude | m |
MAV_CMD_EXTERNAL_ATTITUDE_ESTIMATE (620) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Set an external estimate of vehicle attitude.
This might be used to provide an initial attitude (especially heading) estimate to the estimator (EKF). Angles are defined in a 3-2-1 (yaw-pitch-roll) intrinsic Tait-Bryan sequence.
| Param (Label) | 描述 | 值 | Units |
|---|---|---|---|
| 1 (Roll) | Roll angle. Set to NaN if unknown. | min: 0 max: 360 | 度 |
| 2 (Pitch) | Pitch angle. Set to NaN if unknown. | min: 0 max: 360 | 度 |
| 3 (Yaw) | Yaw/heading (relative to true north) angle. Set to NaN if unknown. | min: 0 max: 360 | 度 |
| 4 (Tilt accuracy) | Estimated 1 sigma accuracy of roll and pitch angles. Set to NaN if unknown. | 度 | |
| 5 | Empty | ||
| 6 | Empty | ||
| 7 (Yaw accuracy) | Estimated 1 sigma accuracy of yaw angle. Set to NaN if unknown. | 度 |
MAV_CMD_CAMERA_START_MTI (2020) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Enable Moving Target Indicators (MTI) on streamed video.
Support for feature can be checked with CAMERA_CAP_FLAGS_HAS_MTI, and disabled with MAV_CMD_CAMERA_STOP_MTI.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (Target Camera ID) | Target camera ID. 7 to 255: MAVLink camera component id. 1 to 6 for cameras attached to the autopilot, which don't have a distinct component id. 0: all cameras. This is used to target specific autopilot-connected cameras. It is also used to target specific cameras when the MAV_CMD is used in a mission. | min: 0 max: 255 inc: 1 |
MAV_CMD_CAMERA_STOP_MTI (2021) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Disable Moving Target Indicators (MTI) on streamed video.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (Target Camera ID) | Target camera ID. 7 to 255: MAVLink camera component id. 1 to 6 for cameras attached to the autopilot, which don't have a distinct component id. 0: all cameras. This is used to target specific autopilot-connected cameras. It is also used to target specific cameras when the MAV_CMD is used in a mission. | min: 0 max: 255 inc: 1 |
MAV_CMD_NAV_FENCE_HOME_CIRCLE_INCLUSION (5005) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Circular fence area centered on home. The vehicle must stay inside this area. If home is moved, the fence moves.
| Param (Label) | 描述 | 值 | Units |
|---|---|---|---|
| 1 (Radius) | Radius. | m | |
| 2 (Inclusion Group) | Vehicle must be inside ALL inclusion zones in a single group, vehicle must be inside at least one group. Ignored when sent as a command. | min: 0 inc: 1 |
MAV_CMD_ODID_SET_EMERGENCY (12900) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Used to manually set/unset emergency status for remote id.
This is for compliance with MOC ASTM docs, specifically F358 section 7.7: "Emergency Status Indicator". The requirement can also be satisfied by automatic setting of the emergency status by flight stack, and that approach is preferred. See https://mavlink.io/en/services/opendroneid.html for more information.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (Number) | Set/unset emergency 0: unset, 1: set | min: 0 inc: 1 |
| 2 | ||
| 3 | ||
| 4 | Empty | |
| 5 | Empty | |
| 5 | Empty | |
| 6 | Empty | |
| 7 | Empty |
MAV_CMD_REQUEST_OPERATOR_CONTROL (32100) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Request exclusive control of a system or special system feature by a GCS.
The operator control protocol supports two modes:
- In single-owner mode there is a single GCS "owner" that can send state changing operations to the whole system, and this command can be used to request takeover of that ownership role.
- In multi-owner mode the flight stack allows multiple GCS to be "owners" and send (most) state changing operations (which GCS those are is implementation-dependent, and not controlled by this protocol). However only one GCS owner can control manual input of the vehicle: this command can be used to request takeover of that ownership role.
A controlled system should only accept MAVLink operations that change the state of the vehicle, such as commands and command-like messages, which are sent by its controlling GCS(s) (or from other components in its own system/with the same system id, such as a companion computer). Commands to control the vehicle from other systems should be rejected with MAV_RESULT_NOT_IN_CONTROL (except for this command, which may be acknowledged with MAV_RESULT_ACCEPTED if control is granted). Messages and commands that don't control or change vehicle movement or functionality, such as telemetry requests, may still be send from (and to) a controlled system.
GCS control of the whole system is managed via a single component that we will refer to here as the "system manager component". This component streams the CONTROL_STATUS message and sets the GCS_CONTROL_STATUS_FLAGS_SYSTEM_MANAGER flag. Other components in the system should monitor for the CONTROL_STATUS message with this flag, and set their controlling GCS(s) to match its published system id(s). A GCS that wants to control the system should also monitor for the same message and flag, and address the MAV_CMD_REQUEST_OPERATOR_CONTROL to its component id. Note that integrators are required to ensure that there is only one system manager component in the system (i.e. one component emitting the message with GCS_CONTROL_STATUS_FLAGS_SYSTEM_MANAGER set).
The MAV_CMD_REQUEST_OPERATOR_CONTROL command is sent by a GCS to the system manager component to request or release control of a system, specifying whether subsequent takeover requests from another GCS are automatically granted, or require permission. The command may request control for a single GCS system ID or a range of GCS system IDs: the sender of the command must have a system id that is in the requested range.
The system manager component should grant control to the requested GCS(s) if the system does not require takeover permission (or is uncontrolled) and ACK the request with MAV_RESULT_ACCEPTED. The system manager component should then stream CONTROL_STATUS indicating its controlling system(s): all other components in the system (with the same system id) should monitor this message and set their own controlling GCS(s) to match that of the system manager component.
If the system manager component cannot grant control because takeover requires permission, the request should be rejected with MAV_RESULT_FAILED. The system manager component should then send this same command to the owning GCS with the lowest system ID that has a heartbeat, in order to notify of the request. That owning GCS must ACK with MAV_RESULT_ACCEPTED, and may choose to release control of the vehicle, or re-request control with the takeover bit set to allow permission. In case it choses to re-request control with takeover bit set to allow permission, the requester GCS will only have 10 seconds to get control, otherwise owning GCS will re-request control with takeover bit set to disallow permission, and requester GCS will need repeat the request if still interested in getting control. Note that the pilots of both GCS should coordinate safe handover offline.
While any owning GCS are connected the system should consider itself connected to a GCS, and still owned by all GCS (even those that are not connected). If all owning GCS are disconnected the vehicle should GCS loss failsafe, and broadcast a CONTROL_STATUS indicating that it has no owner(s). In simultaneous-owner scenarios this allows an owner to disconnect and reconnect without the vehicle failsafing, provided at least one owner is connected.
Note that in most systems the only controlled component will be the "system manager component", and that will be the autopilot (although it could be a companion computer). However separate GCS control of a particular component is also permitted, if supported by the component. In this case the GCS will address MAV_CMD_REQUEST_OPERATOR_CONTROL to the specific component it wants to control. The component will then stream CONTROL_STATUS for its controlling GCS (it must not set GCS_CONTROL_STATUS_FLAGS_SYSTEM_MANAGER). The component should fall back to the system GCS (if any) when it is not directly controlled, and may stop emitting CONTROL_STATUS. The flow is otherwise the same as for requesting control over the whole system.
| Param (Label) | 描述 | 值 | Units |
|---|---|---|---|
| 1 (Action) | 0: Release control, 1: Request control. | ||
| 2 (Allow takeover) | Enable automatic granting of ownership on request (by default reject request and notify current owner). 0: Ask current owner and reject request, 1: Allow automatic takeover. | ||
| 3 (Request timeout) | Timeout in seconds before a request to a GCS to allow takeover is assumed to be rejected. This is used to display the timeout graphically on requester and GCS in control. | min: 3 max: 60 | s |
| 4 (GCS Sysid) | System ID of GCS requesting control. For a range of GCS in control, this the minimum id (and the sender system ID may be anywhere in the range). | ||
| 5 (GCS Sysid (upper range)) | Upper range of controlling GCS system IDs. 0 for single-GCS control. If non-zero the sender system ID may be anywhere in the range). | ||
| 6 | Empty | ||
| 7 | Empty |
MAV_CMD_EXTERNAL_WIND_ESTIMATE (43004) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Set an external estimate of wind direction and speed.
This might be used to provide an initial wind estimate to the estimator (EKF) in the case where the vehicle is wind dead-reckoning, extending the time when operating without GPS before before position drift builds to an unsafe level. For this use case the command might reasonably be sent every few minutes when operating at altitude, and the value is cleared if the estimator resets itself.
| Param (Label) | 描述 | 值 | Units |
|---|---|---|---|
| 1 (Wind speed) | Horizontal wind speed. | min: 0 | m/s |
| 2 (Wind speed accuracy) | Estimated 1 sigma accuracy of wind speed. Set to NaN if unknown. | m/s | |
| 3 (Direction) | Azimuth (relative to true north) from where the wind is blowing. | min: 0 max: 360 | 度 |
| 4 (Direction accuracy) | Estimated 1 sigma accuracy of wind direction. Set to NaN if unknown. | 度 | |
| 5 | Empty | ||
| 6 | Empty | ||
| 7 | Empty |
MAV_CMD_ESTIMATOR_SENSOR_ENABLE (43006) — [WIP]
WORK IN PROGRESS: Do not use in stable production environments (it may change).
Enable or disable a specific estimator sensor fusion source at runtime.
This allows a GCS or companion computer to dynamically control which sensors the estimator fuses without changing parameters.
| Param (Label) | 描述 | 值 |
|---|---|---|
| 1 (Source) | Sensor fusion source type. | ESTIMATOR_SENSOR_FUSION_SOURCE |
| 2 (Instance) | Sensor instance (0-based, for multi-instance). | min: 0 inc: 1 |
| 3 (Enable) | Enable (1) or Disable (0) the source. | MAV_BOOL |
| 4 (Estimator Instance) | Estimator instance (0-based, for systems with multiple estimators). | min: 0 inc: 1 |
| 5 | Empty | |
| 6 | Empty | |
| 7 | Empty |