mirror of
https://github.com/mavlink/mavlink-devguide.git
synced 2026-06-19 07:36:26 +00:00
New Crowdin updates (#597)
* New translations development.md (Korean) * New translations common.md (Korean) * New translations development.md (Chinese Simplified) * New translations common.md (Chinese Simplified) * New translations cubepilot.md (Korean) * New translations cubepilot.md (Chinese Simplified) * New translations matrixpilot.md (Korean) * New translations paparazzi.md (Korean) * New translations python_array_test.md (Korean) * New translations storm32.md (Korean) * New translations uavionix.md (Korean) * New translations all.md (Korean) * New translations ardupilotmega.md (Korean) * New translations asluav.md (Korean) * New translations avssuas.md (Korean) * New translations matrixpilot.md (Chinese Simplified) * New translations paparazzi.md (Chinese Simplified) * New translations python_array_test.md (Chinese Simplified) * New translations storm32.md (Chinese Simplified) * New translations uavionix.md (Chinese Simplified) * New translations all.md (Chinese Simplified) * New translations ardupilotmega.md (Chinese Simplified) * New translations asluav.md (Chinese Simplified) * New translations avssuas.md (Chinese Simplified) * New translations ualberta.md (Korean) * New translations ualberta.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations development.md (Korean) * New translations common.md (Korean) * New translations development.md (Chinese Simplified) * New translations common.md (Chinese Simplified) * New translations cubepilot.md (Korean) * New translations cubepilot.md (Chinese Simplified) * New translations matrixpilot.md (Korean) * New translations paparazzi.md (Korean) * New translations python_array_test.md (Korean) * New translations storm32.md (Korean) * New translations uavionix.md (Korean) * New translations all.md (Korean) * New translations ardupilotmega.md (Korean) * New translations asluav.md (Korean) * New translations avssuas.md (Korean) * New translations matrixpilot.md (Chinese Simplified) * New translations paparazzi.md (Chinese Simplified) * New translations python_array_test.md (Chinese Simplified) * New translations storm32.md (Chinese Simplified) * New translations uavionix.md (Chinese Simplified) * New translations all.md (Chinese Simplified) * New translations ardupilotmega.md (Chinese Simplified) * New translations asluav.md (Chinese Simplified) * New translations avssuas.md (Chinese Simplified) * New translations ualberta.md (Korean) * New translations ualberta.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations development.md (Korean) * New translations common.md (Korean) * New translations development.md (Chinese Simplified) * New translations common.md (Chinese Simplified) * New translations all.md (Korean) * New translations all.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations development.md (Korean) * New translations development.md (Chinese Simplified) * New translations summary.md (Chinese Simplified) * New translations faq.md (Chinese Simplified) * New translations index.md (Chinese Simplified) * New translations summary.md (Chinese Simplified) * New translations heartbeat.md (Chinese Simplified)
This commit is contained in:
+1
-1
@@ -62,7 +62,7 @@ span.warning {
|
||||
| -------------------------- | ------- | -------- |
|
||||
| [Messages](#messages) | 0 | 372 |
|
||||
| [Enums](#enumerated-types) | 0 | 235 |
|
||||
| [Commands](#mav_commands) | 217 | 0 |
|
||||
| [Commands](#mav_commands) | 218 | 0 |
|
||||
|
||||
The following sections list all entities in the dialect (both included and defined in this file).
|
||||
|
||||
|
||||
+61
-63
@@ -582,7 +582,9 @@ Acknowledgment message during waypoint handling. The type field states if this m
|
||||
| <span class='ext'>mission_type</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | [MAV_MISSION_TYPE](#MAV_MISSION_TYPE) | Mission type. |
|
||||
| <span class='ext'>opaque_id</span> <a href='#mav2_extension_field'>++</a> | `uint32_t` | invalid:0 | Id of new on-vehicle mission, fence, or rally point plan (on upload to vehicle).<br>The id is calculated and returned by a vehicle when a new plan is uploaded by a GCS.<br>The only requirement on the id is that it must change when there is any change to the on-vehicle plan type (there is no requirement that the id be globally unique).<br>0 on download from the vehicle to the GCS (on download the ID is set in [MISSION_COUNT](#MISSION_COUNT)).<br>0 if plan ids are not supported.<br>The current on-vehicle plan ids are streamed in `[MISSION_CURRENT](#MISSION_CURRENT)`, allowing a GCS to determine if any part of the plan has changed and needs to be re-uploaded. |
|
||||
|
||||
### SET_GPS_GLOBAL_ORIGIN (48) {#SET_GPS_GLOBAL_ORIGIN}
|
||||
### SET_GPS_GLOBAL_ORIGIN (48) — [DEP] {#SET_GPS_GLOBAL_ORIGIN}
|
||||
|
||||
<span class="warning">**DEPRECATED:** Replaced By [MAV_CMD_SET_GLOBAL_ORIGIN](#MAV_CMD_SET_GLOBAL_ORIGIN) (2025-04)</span>
|
||||
|
||||
Sets the GPS coordinates of the vehicle local origin (0,0,0) position. Vehicle should emit [GPS_GLOBAL_ORIGIN](#GPS_GLOBAL_ORIGIN) irrespective of whether the origin is changed. This enables transform between the local coordinate frame and the global (GPS) coordinate frame, which may be necessary when (for example) indoor and outdoor settings are connected and the MAV should move from in- to outdoor.
|
||||
|
||||
@@ -1145,12 +1147,12 @@ Sent from simulation to autopilot. The RAW values of the RC channels received. T
|
||||
|
||||
Sent from autopilot to simulation. Hardware in the loop control outputs. Alternative to [HIL_CONTROLS](#HIL_CONTROLS).
|
||||
|
||||
| Field Name | Type | Units | Values | Description |
|
||||
| ------------------------------ | ----------- | ----- | ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 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. |
|
||||
| controls | `float[16]` | | | Control outputs -1 .. 1. Channel assignment depends on the simulated hardware. |
|
||||
| mode | `uint8_t` | | [MAV_MODE_FLAG](#MAV_MODE_FLAG) | System mode. Includes arming state. |
|
||||
| flags | `uint64_t` | | | Flags as bitfield, 1: indicate simulation using lockstep. |
|
||||
| Field Name | Type | Units | Values | Description |
|
||||
| ------------------------------ | ----------- | ----- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 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. |
|
||||
| controls | `float[16]` | | | Control outputs -1 .. 1. Channel assignment depends on the simulated hardware. |
|
||||
| mode | `uint8_t` | | [MAV_MODE_FLAG](#MAV_MODE_FLAG) | System mode. Includes arming state. |
|
||||
| flags | `uint64_t` | | [HIL_ACTUATOR_CONTROLS_FLAGS](#HIL_ACTUATOR_CONTROLS_FLAGS) | Flags bitmask. |
|
||||
|
||||
### OPTICAL_FLOW (100) {#OPTICAL_FLOW}
|
||||
|
||||
@@ -1886,20 +1888,20 @@ Battery information. Updates GCS with flight controller battery status. Smart ba
|
||||
|
||||
Version and capability of autopilot software. This should be emitted in response to a request with [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE).
|
||||
|
||||
| Field Name | Type | Values | Description |
|
||||
| -------------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| capabilities | `uint64_t` | [MAV_PROTOCOL_CAPABILITY](#MAV_PROTOCOL_CAPABILITY) | Bitmap of capabilities |
|
||||
| flight_sw_version | `uint32_t` | | Firmware version number |
|
||||
| middleware_sw_version | `uint32_t` | | Middleware version number |
|
||||
| os_sw_version | `uint32_t` | | Operating system version number |
|
||||
| board_version | `uint32_t` | | HW / board version (last 8 bits should be silicon ID, if any). The first 16 bits of this field specify https://github.com/PX4/PX4-Bootloader/blob/master/board_types.txt |
|
||||
| flight_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| middleware_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| os_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| vendor_id | `uint16_t` | | ID of the board vendor |
|
||||
| product_id | `uint16_t` | | ID of the product |
|
||||
| uid | `uint64_t` | | UID if provided by hardware (see uid2) |
|
||||
| <span class='ext'>uid2</span> <a href='#mav2_extension_field'>++</a> | `uint8_t[18]` | | UID if provided by hardware (supersedes the uid field. If this is non-zero, use this field, otherwise use uid) |
|
||||
| Field Name | Type | Values | Description |
|
||||
| -------------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| capabilities | `uint64_t` | [MAV_PROTOCOL_CAPABILITY](#MAV_PROTOCOL_CAPABILITY) | Bitmap of capabilities |
|
||||
| flight_sw_version | `uint32_t` | | Firmware version number.<br>The field must be encoded as 4 bytes, where each byte (shown from MSB to LSB) is part of a semantic version: (major) (minor) (patch) ([FIRMWARE_VERSION_TYPE](#FIRMWARE_VERSION_TYPE)). |
|
||||
| middleware_sw_version | `uint32_t` | | Middleware version number |
|
||||
| os_sw_version | `uint32_t` | | Operating system version number |
|
||||
| board_version | `uint32_t` | | HW / board version (last 8 bits should be silicon ID, if any). The first 16 bits of this field specify https://github.com/PX4/PX4-Bootloader/blob/master/board_types.txt |
|
||||
| flight_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| middleware_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| os_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| vendor_id | `uint16_t` | | ID of the board vendor |
|
||||
| product_id | `uint16_t` | | ID of the product |
|
||||
| uid | `uint64_t` | | UID if provided by hardware (see uid2) |
|
||||
| <span class='ext'>uid2</span> <a href='#mav2_extension_field'>++</a> | `uint8_t[18]` | | UID if provided by hardware (supersedes the uid field. If this is non-zero, use this field, otherwise use uid) |
|
||||
|
||||
### LANDING_TARGET (149) {#LANDING_TARGET}
|
||||
|
||||
@@ -3883,21 +3885,6 @@ Some deprecated frames do not follow these conventions (e.g. [MAV_FRAME_BODY_NED
|
||||
| <a id='MAVLINK_DATA_STREAM_IMG_PGM'></a>4 | [MAVLINK_DATA_STREAM_IMG_PGM](#MAVLINK_DATA_STREAM_IMG_PGM) | |
|
||||
| <a id='MAVLINK_DATA_STREAM_IMG_PNG'></a>5 | [MAVLINK_DATA_STREAM_IMG_PNG](#MAVLINK_DATA_STREAM_IMG_PNG) | |
|
||||
|
||||
### FENCE_ACTION {#FENCE_ACTION}
|
||||
|
||||
Actions following geofence breach.
|
||||
|
||||
| Value | Name | Description |
|
||||
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id='FENCE_ACTION_NONE'></a>0 | [FENCE_ACTION_NONE](#FENCE_ACTION_NONE) | Disable fenced mode. If used in a plan this would mean the next fence is disabled. |
|
||||
| <a id='FENCE_ACTION_GUIDED'></a>1 | [FENCE_ACTION_GUIDED](#FENCE_ACTION_GUIDED) | Fly to geofence [MAV_CMD_NAV_FENCE_RETURN_POINT](#MAV_CMD_NAV_FENCE_RETURN_POINT) in GUIDED mode. Note: This action is only supported by ArduPlane, and may not be supported in all versions. |
|
||||
| <a id='FENCE_ACTION_REPORT'></a>2 | [FENCE_ACTION_REPORT](#FENCE_ACTION_REPORT) | Report fence breach, but don't take action |
|
||||
| <a id='FENCE_ACTION_GUIDED_THR_PASS'></a>3 | [FENCE_ACTION_GUIDED_THR_PASS](#FENCE_ACTION_GUIDED_THR_PASS) | Fly to geofence [MAV_CMD_NAV_FENCE_RETURN_POINT](#MAV_CMD_NAV_FENCE_RETURN_POINT) with manual throttle control in GUIDED mode. Note: This action is only supported by ArduPlane, and may not be supported in all versions. |
|
||||
| <a id='FENCE_ACTION_RTL'></a>4 | [FENCE_ACTION_RTL](#FENCE_ACTION_RTL) | Return/RTL mode. |
|
||||
| <a id='FENCE_ACTION_HOLD'></a>5 | [FENCE_ACTION_HOLD](#FENCE_ACTION_HOLD) | Hold at current location. |
|
||||
| <a id='FENCE_ACTION_TERMINATE'></a>6 | [FENCE_ACTION_TERMINATE](#FENCE_ACTION_TERMINATE) | Termination failsafe. Motors are shut down (some flight stacks may trigger other failsafe actions). |
|
||||
| <a id='FENCE_ACTION_LAND'></a>7 | [FENCE_ACTION_LAND](#FENCE_ACTION_LAND) | Land at current location. |
|
||||
|
||||
### FENCE_BREACH {#FENCE_BREACH}
|
||||
|
||||
| Value | Name | Description |
|
||||
@@ -3919,11 +3906,13 @@ Actions being taken to mitigate/prevent fence breach
|
||||
|
||||
### FENCE_TYPE {#FENCE_TYPE}
|
||||
|
||||
(Bitmask)
|
||||
(Bitmask) Fence types to enable or disable when using [MAV_CMD_DO_FENCE_ENABLE](#MAV_CMD_DO_FENCE_ENABLE).
|
||||
|
||||
Note that at least one of these flags must be set in [MAV_CMD_DO_FENCE_ENABLE](#MAV_CMD_DO_FENCE_ENABLE).param2.
|
||||
If none are set, the flight stack will ignore the field and enable/disable its default set of fences (usually all of them).
|
||||
|
||||
| Value | Name | Description |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------- | ---------------------- |
|
||||
| <a id='FENCE_TYPE_ALL'></a>0 | [FENCE_TYPE_ALL](#FENCE_TYPE_ALL) | All fence types |
|
||||
| <a id='FENCE_TYPE_ALT_MAX'></a>1 | [FENCE_TYPE_ALT_MAX](#FENCE_TYPE_ALT_MAX) | Maximum altitude fence |
|
||||
| <a id='FENCE_TYPE_CIRCLE'></a>2 | [FENCE_TYPE_CIRCLE](#FENCE_TYPE_CIRCLE) | Circle fence |
|
||||
| <a id='FENCE_TYPE_POLYGON'></a>4 | [FENCE_TYPE_POLYGON](#FENCE_TYPE_POLYGON) | Polygon fence |
|
||||
@@ -4271,14 +4260,15 @@ Actuator output function. Values greater or equal to 1000 are autopilot-specific
|
||||
|
||||
### AUTOTUNE_AXIS {#AUTOTUNE_AXIS}
|
||||
|
||||
(Bitmask) Enable axes that will be tuned via autotuning. Used in [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).
|
||||
(Bitmask) Axes that will be autotuned by [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).
|
||||
|
||||
| Value | Name | Description |
|
||||
| ----------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
|
||||
| <a id='AUTOTUNE_AXIS_DEFAULT'></a>0 | [AUTOTUNE_AXIS_DEFAULT](#AUTOTUNE_AXIS_DEFAULT) | Flight stack tunes axis according to its default settings. |
|
||||
| <a id='AUTOTUNE_AXIS_ROLL'></a>1 | [AUTOTUNE_AXIS_ROLL](#AUTOTUNE_AXIS_ROLL) | Autotune roll axis. |
|
||||
| <a id='AUTOTUNE_AXIS_PITCH'></a>2 | [AUTOTUNE_AXIS_PITCH](#AUTOTUNE_AXIS_PITCH) | Autotune pitch axis. |
|
||||
| <a id='AUTOTUNE_AXIS_YAW'></a>4 | [AUTOTUNE_AXIS_YAW](#AUTOTUNE_AXIS_YAW) | Autotune yaw axis. |
|
||||
Note that at least one flag must be set in [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).param2: if none are set, the flight stack will tune its default set of axes.
|
||||
|
||||
| Value | Name | Description |
|
||||
| --------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------ |
|
||||
| <a id='AUTOTUNE_AXIS_ROLL'></a>1 | [AUTOTUNE_AXIS_ROLL](#AUTOTUNE_AXIS_ROLL) | Autotune roll axis. |
|
||||
| <a id='AUTOTUNE_AXIS_PITCH'></a>2 | [AUTOTUNE_AXIS_PITCH](#AUTOTUNE_AXIS_PITCH) | Autotune pitch axis. |
|
||||
| <a id='AUTOTUNE_AXIS_YAW'></a>4 | [AUTOTUNE_AXIS_YAW](#AUTOTUNE_AXIS_YAW) | Autotune yaw axis. |
|
||||
|
||||
### PREFLIGHT_STORAGE_PARAMETER_ACTION {#PREFLIGHT_STORAGE_PARAMETER_ACTION}
|
||||
|
||||
@@ -5840,6 +5830,14 @@ See https://mavlink.io/en/services/standard_modes.html
|
||||
| <a id='MAV_MODE_PROPERTY_NOT_USER_SELECTABLE'></a>2 | [MAV_MODE_PROPERTY_NOT_USER_SELECTABLE](#MAV_MODE_PROPERTY_NOT_USER_SELECTABLE) | If set, this mode should not be added to the list of selectable modes.<br>The mode might still be selected by the FC directly (for example as part of a failsafe). |
|
||||
| <a id='MAV_MODE_PROPERTY_AUTO_MODE'></a>4 | [MAV_MODE_PROPERTY_AUTO_MODE](#MAV_MODE_PROPERTY_AUTO_MODE) | If set, this mode is automatically controlled (it may use but does not require a manual controller).<br>If unset the mode is a assumed to require user input (be a manual mode). |
|
||||
|
||||
### HIL_ACTUATOR_CONTROLS_FLAGS {#HIL_ACTUATOR_CONTROLS_FLAGS}
|
||||
|
||||
(Bitmask) Flags used in [HIL_ACTUATOR_CONTROLS](#HIL_ACTUATOR_CONTROLS) message.
|
||||
|
||||
| Value | Name | Description |
|
||||
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
|
||||
| <a id='HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP'></a>1 | [HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP](#HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP) | Simulation is using lockstep |
|
||||
|
||||
### MAV_AUTOPILOT — \[from: [minimal](../messages/minimal.md#MAV_AUTOPILOT)\] {#MAV_AUTOPILOT}
|
||||
|
||||
Micro air vehicle / autopilot classes. This identifies the individual model.
|
||||
@@ -6982,15 +6980,15 @@ The persistence/lifetime of the setting is undefined.
|
||||
Depending on flight stack implementation it may persist until superseded, or it may revert to a system default at the end of a mission.
|
||||
Flight stacks typically reset the setting to system defaults on reboot.
|
||||
|
||||
| Param (Label) | Description | Values |
|
||||
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | enable? (0=disable, 1=enable, 2=disable_floor_only) | min: 0 max: 2 inc: 1 |
|
||||
| 2 (Types) | Fence types to enable or disable as a bitmask. A value of 0 indicates that all fences should be enabled or disabled. This parameter is ignored if param 1 has the value 2 | [FENCE_TYPE](#FENCE_TYPE) |
|
||||
| 3 | Empty | |
|
||||
| 4 | Empty | |
|
||||
| 5 | Empty | |
|
||||
| 6 | Empty | |
|
||||
| 7 | Empty | |
|
||||
| Param (Label) | Description | Values |
|
||||
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | enable? (0=disable, 1=enable, 2=disable_floor_only) | min: 0 max: 2 inc: 1 |
|
||||
| 2 (Types) | Fence types to enable or disable as a bitmask. 0: field is unused/all fences should be enabled or disabled (for compatiblity reasons). Parameter is ignored if param1=2. | [FENCE_TYPE](#FENCE_TYPE) |
|
||||
| 3 | Empty | |
|
||||
| 4 | Empty | |
|
||||
| 5 | Empty | |
|
||||
| 6 | Empty | |
|
||||
| 7 | Empty | |
|
||||
|
||||
### MAV_CMD_DO_PARACHUTE (208) {#MAV_CMD_DO_PARACHUTE}
|
||||
|
||||
@@ -7052,15 +7050,15 @@ Mission command to operate a gripper.
|
||||
|
||||
Enable/disable autotune.
|
||||
|
||||
| Param (Label) | Description | Values |
|
||||
| -------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | Enable (1: enable, 0:disable). | min: 0 max: 1 inc: 1 |
|
||||
| 2 (Axis) | Specify which axis are autotuned. 0 indicates autopilot default settings. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS) |
|
||||
| 3 | Empty. | |
|
||||
| 4 | Empty. | |
|
||||
| 5 | Empty. | |
|
||||
| 6 | Empty. | |
|
||||
| 7 | Empty. | |
|
||||
| Param (Label) | Description | Values |
|
||||
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | Enable (1: enable, 0:disable). | min: 0 max: 1 inc: 1 |
|
||||
| 2 (Axis) | Specify axes for which autotuning is enabled/disabled. 0 indicates the field is unused (for compatiblity reasons). If 0 the autopilot will follow its default behaviour, which is usually to tune all axes. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS) |
|
||||
| 3 | Empty. | |
|
||||
| 4 | Empty. | |
|
||||
| 5 | Empty. | |
|
||||
| 6 | Empty. | |
|
||||
| 7 | Empty. | |
|
||||
|
||||
### MAV_CMD_NAV_SET_YAW_SPEED (213) {#MAV_CMD_NAV_SET_YAW_SPEED}
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ span.warning {
|
||||
| -------------------------- | ------- | -------- |
|
||||
| [Messages](#messages) | 12 | 229 |
|
||||
| [Enums](#enumerated-types) | 11 | 146 |
|
||||
| [Commands](#mav_commands) | 172 | 0 |
|
||||
| [Commands](#mav_commands) | 173 | 0 |
|
||||
|
||||
The following sections list all entities in the dialect (both included and defined in this file).
|
||||
|
||||
@@ -487,6 +487,27 @@ Recipients must reject command addressed to broadcast system ID.
|
||||
| 3 (Reboot) | Reboot components after ID change. Any non-zero value triggers the reboot. | |
|
||||
| 4 | | |
|
||||
|
||||
### MAV_CMD_DO_SET_GLOBAL_ORIGIN (611) — [WIP] {#MAV_CMD_DO_SET_GLOBAL_ORIGIN}
|
||||
|
||||
<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
|
||||
|
||||
Sets the GNSS coordinates of the vehicle local origin (0,0,0) position.
|
||||
|
||||
Vehicle should emit [GPS_GLOBAL_ORIGIN](#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](#SET_GPS_GLOBAL_ORIGIN).
|
||||
Should be sent in a [COMMAND_INT](#COMMAND_INT) (Expected frame is [MAV_FRAME_GLOBAL](#MAV_FRAME_GLOBAL), and this should be assumed when sent in [COMMAND_LONG](#COMMAND_LONG)).
|
||||
|
||||
| Param (Label) | Description | Units |
|
||||
| -------------------------------- | ----------- | ----- |
|
||||
| 1 | Empty | |
|
||||
| 2 | Empty | |
|
||||
| 3 | Empty | |
|
||||
| 4 | Empty | |
|
||||
| 5 (Latitude) | Latitude | |
|
||||
| 6 (Longitude) | Longitude | |
|
||||
| 7 (Altitude) | Altitude | m |
|
||||
|
||||
### MAV_CMD_ODID_SET_EMERGENCY (12900) — [WIP] {#MAV_CMD_ODID_SET_EMERGENCY}
|
||||
|
||||
<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
|
||||
|
||||
@@ -116,3 +116,4 @@ Mode currently commanded by pilot
|
||||
| <a id='PILOT_ROTO'></a>3 | [PILOT_ROTO](#PILOT_ROTO) | Rotomotion mode |
|
||||
|
||||
## Commands (MAV_CMD) {#mav_commands}
|
||||
|
||||
|
||||
+2
-2
@@ -37,8 +37,8 @@
|
||||
- [standard.xml](messages/standard.md)
|
||||
- [minimal.xml](messages/minimal.md)
|
||||
- [development.xml](messages/development.md)
|
||||
- [Microservices](services/index.md)
|
||||
- [Heartbeat/Connection Protocol](services/heartbeat.md)
|
||||
- [](services/index.md)
|
||||
- [心跳/连接协议](services/heartbeat.md)
|
||||
- [Mission Protocol](services/mission.md)
|
||||
- [Parameter Protocol](services/parameter.md)
|
||||
- [Extended Parameter Protocol](services/parameter_ext.md)
|
||||
|
||||
+2
-3
@@ -29,9 +29,8 @@
|
||||
<dd>
|
||||
|
||||
<ul>
|
||||
<li>The underlying over-the-wire format is rarely updated (we're only up to <em>MAVLink 2</em>, which was introduced in 2017).
|
||||
</li>
|
||||
<li>New <a href="../messages/common.md">messages</a>/<a href="../services/index.md">microservices</a> are frequently added. 这些更新是后向兼容,用户可定期更新其使用的库以支持新的消息。</li>
|
||||
<li>底层的序列化方式很少更新(只在2017年引入 <em>MAVLink 2</em>时进行了更新)。</li>
|
||||
<li>经常添加新的<a href="../messages/common.md">信息</a>/<a href="../services/index.md">微服务</a>。 这些更新是后向兼容,用户可定期更新其使用的库以支持新的消息。</li>
|
||||
<li>消息很少被修改(或删除),以防止它们变得不兼容。 如果需要更新,项目将通过更新MAVLink次要版本号,并通过 <a href="https://groups.google.com/forum/#!forum/mavlink">邮件列表</a> 通知用户(用户也可以在代码中查询版本)。</li>
|
||||
</ul>
|
||||
</dd>
|
||||
|
||||
+1
-1
@@ -62,7 +62,7 @@ span.warning {
|
||||
| -------------------------- | ------- | -------- |
|
||||
| [Messages](#messages) | 0 | 372 |
|
||||
| [Enums](#enumerated-types) | 0 | 235 |
|
||||
| [Commands](#mav_commands) | 217 | 0 |
|
||||
| [Commands](#mav_commands) | 218 | 0 |
|
||||
|
||||
The following sections list all entities in the dialect (both included and defined in this file).
|
||||
|
||||
|
||||
+61
-63
@@ -582,7 +582,9 @@ Acknowledgment message during waypoint handling. The type field states if this m
|
||||
| <span class='ext'>mission_type</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | [MAV_MISSION_TYPE](#MAV_MISSION_TYPE) | Mission type. |
|
||||
| <span class='ext'>opaque_id</span> <a href='#mav2_extension_field'>++</a> | `uint32_t` | invalid:0 | Id of new on-vehicle mission, fence, or rally point plan (on upload to vehicle).<br>The id is calculated and returned by a vehicle when a new plan is uploaded by a GCS.<br>The only requirement on the id is that it must change when there is any change to the on-vehicle plan type (there is no requirement that the id be globally unique).<br>0 on download from the vehicle to the GCS (on download the ID is set in [MISSION_COUNT](#MISSION_COUNT)).<br>0 if plan ids are not supported.<br>The current on-vehicle plan ids are streamed in `[MISSION_CURRENT](#MISSION_CURRENT)`, allowing a GCS to determine if any part of the plan has changed and needs to be re-uploaded. |
|
||||
|
||||
### SET_GPS_GLOBAL_ORIGIN (48) {#SET_GPS_GLOBAL_ORIGIN}
|
||||
### SET_GPS_GLOBAL_ORIGIN (48) — [DEP] {#SET_GPS_GLOBAL_ORIGIN}
|
||||
|
||||
<span class="warning">**DEPRECATED:** Replaced By [MAV_CMD_SET_GLOBAL_ORIGIN](#MAV_CMD_SET_GLOBAL_ORIGIN) (2025-04)</span>
|
||||
|
||||
Sets the GPS coordinates of the vehicle local origin (0,0,0) position. Vehicle should emit [GPS_GLOBAL_ORIGIN](#GPS_GLOBAL_ORIGIN) irrespective of whether the origin is changed. This enables transform between the local coordinate frame and the global (GPS) coordinate frame, which may be necessary when (for example) indoor and outdoor settings are connected and the MAV should move from in- to outdoor.
|
||||
|
||||
@@ -1145,12 +1147,12 @@ Sent from simulation to autopilot. The RAW values of the RC channels received. T
|
||||
|
||||
Sent from autopilot to simulation. Hardware in the loop control outputs. Alternative to [HIL_CONTROLS](#HIL_CONTROLS).
|
||||
|
||||
| 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. |
|
||||
| controls | `float[16]` | | | Control outputs -1 .. 1. Channel assignment depends on the simulated hardware. |
|
||||
| 模式 | `uint8_t` | | [MAV_MODE_FLAG](#MAV_MODE_FLAG) | System mode. Includes arming state. |
|
||||
| flags | `uint64_t` | | | Flags as bitfield, 1: indicate simulation using lockstep. |
|
||||
| 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. |
|
||||
| controls | `float[16]` | | | Control outputs -1 .. 1. Channel assignment depends on the simulated hardware. |
|
||||
| 模式 | `uint8_t` | | [MAV_MODE_FLAG](#MAV_MODE_FLAG) | System mode. Includes arming state. |
|
||||
| flags | `uint64_t` | | [HIL_ACTUATOR_CONTROLS_FLAGS](#HIL_ACTUATOR_CONTROLS_FLAGS) | Flags bitmask. |
|
||||
|
||||
### OPTICAL_FLOW (100) {#OPTICAL_FLOW}
|
||||
|
||||
@@ -1886,20 +1888,20 @@ Battery information. Updates GCS with flight controller battery status. Smart ba
|
||||
|
||||
Version and capability of autopilot software. This should be emitted in response to a request with [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE).
|
||||
|
||||
| Field Name | Type | 值 | 描述 |
|
||||
| -------------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| capabilities | `uint64_t` | [MAV_PROTOCOL_CAPABILITY](#MAV_PROTOCOL_CAPABILITY) | Bitmap of capabilities |
|
||||
| flight_sw_version | `uint32_t` | | Firmware version number |
|
||||
| middleware_sw_version | `uint32_t` | | Middleware version number |
|
||||
| os_sw_version | `uint32_t` | | Operating system version number |
|
||||
| board_version | `uint32_t` | | HW / board version (last 8 bits should be silicon ID, if any). The first 16 bits of this field specify https://github.com/PX4/PX4-Bootloader/blob/master/board_types.txt |
|
||||
| flight_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| middleware_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| os_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| vendor_id | `uint16_t` | | ID of the board vendor |
|
||||
| product_id | `uint16_t` | | ID of the product |
|
||||
| uid | `uint64_t` | | UID if provided by hardware (see uid2) |
|
||||
| <span class='ext'>uid2</span> <a href='#mav2_extension_field'>++</a> | `uint8_t[18]` | | UID if provided by hardware (supersedes the uid field. If this is non-zero, use this field, otherwise use uid) |
|
||||
| Field Name | Type | 值 | 描述 |
|
||||
| -------------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| capabilities | `uint64_t` | [MAV_PROTOCOL_CAPABILITY](#MAV_PROTOCOL_CAPABILITY) | Bitmap of capabilities |
|
||||
| flight_sw_version | `uint32_t` | | Firmware version number.<br>The field must be encoded as 4 bytes, where each byte (shown from MSB to LSB) is part of a semantic version: (major) (minor) (patch) ([FIRMWARE_VERSION_TYPE](#FIRMWARE_VERSION_TYPE)). |
|
||||
| middleware_sw_version | `uint32_t` | | Middleware version number |
|
||||
| os_sw_version | `uint32_t` | | Operating system version number |
|
||||
| board_version | `uint32_t` | | HW / board version (last 8 bits should be silicon ID, if any). The first 16 bits of this field specify https://github.com/PX4/PX4-Bootloader/blob/master/board_types.txt |
|
||||
| flight_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| middleware_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| os_custom_version | `uint8_t[8]` | | Custom version field, commonly the first 8 bytes of the git hash. This is not an unique identifier, but should allow to identify the commit using the main version number even for very large code bases. |
|
||||
| vendor_id | `uint16_t` | | ID of the board vendor |
|
||||
| product_id | `uint16_t` | | ID of the product |
|
||||
| uid | `uint64_t` | | UID if provided by hardware (see uid2) |
|
||||
| <span class='ext'>uid2</span> <a href='#mav2_extension_field'>++</a> | `uint8_t[18]` | | UID if provided by hardware (supersedes the uid field. If this is non-zero, use this field, otherwise use uid) |
|
||||
|
||||
### LANDING_TARGET (149) {#LANDING_TARGET}
|
||||
|
||||
@@ -3883,21 +3885,6 @@ Some deprecated frames do not follow these conventions (e.g. [MAV_FRAME_BODY_NED
|
||||
| <a id='MAVLINK_DATA_STREAM_IMG_PGM'></a>4 | [MAVLINK_DATA_STREAM_IMG_PGM](#MAVLINK_DATA_STREAM_IMG_PGM) | |
|
||||
| <a id='MAVLINK_DATA_STREAM_IMG_PNG'></a>5 | [MAVLINK_DATA_STREAM_IMG_PNG](#MAVLINK_DATA_STREAM_IMG_PNG) | |
|
||||
|
||||
### FENCE_ACTION {#FENCE_ACTION}
|
||||
|
||||
Actions following geofence breach.
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id='FENCE_ACTION_NONE'></a>0 | [FENCE_ACTION_NONE](#FENCE_ACTION_NONE) | Disable fenced mode. If used in a plan this would mean the next fence is disabled. |
|
||||
| <a id='FENCE_ACTION_GUIDED'></a>1 | [FENCE_ACTION_GUIDED](#FENCE_ACTION_GUIDED) | Fly to geofence [MAV_CMD_NAV_FENCE_RETURN_POINT](#MAV_CMD_NAV_FENCE_RETURN_POINT) in GUIDED mode. Note: This action is only supported by ArduPlane, and may not be supported in all versions. |
|
||||
| <a id='FENCE_ACTION_REPORT'></a>2 | [FENCE_ACTION_REPORT](#FENCE_ACTION_REPORT) | Report fence breach, but don't take action |
|
||||
| <a id='FENCE_ACTION_GUIDED_THR_PASS'></a>3 | [FENCE_ACTION_GUIDED_THR_PASS](#FENCE_ACTION_GUIDED_THR_PASS) | Fly to geofence [MAV_CMD_NAV_FENCE_RETURN_POINT](#MAV_CMD_NAV_FENCE_RETURN_POINT) with manual throttle control in GUIDED mode. Note: This action is only supported by ArduPlane, and may not be supported in all versions. |
|
||||
| <a id='FENCE_ACTION_RTL'></a>4 | [FENCE_ACTION_RTL](#FENCE_ACTION_RTL) | Return/RTL mode. |
|
||||
| <a id='FENCE_ACTION_HOLD'></a>5 | [FENCE_ACTION_HOLD](#FENCE_ACTION_HOLD) | Hold at current location. |
|
||||
| <a id='FENCE_ACTION_TERMINATE'></a>6 | [FENCE_ACTION_TERMINATE](#FENCE_ACTION_TERMINATE) | Termination failsafe. Motors are shut down (some flight stacks may trigger other failsafe actions). |
|
||||
| <a id='FENCE_ACTION_LAND'></a>7 | [FENCE_ACTION_LAND](#FENCE_ACTION_LAND) | Land at current location. |
|
||||
|
||||
### FENCE_BREACH {#FENCE_BREACH}
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
@@ -3919,11 +3906,13 @@ Actions being taken to mitigate/prevent fence breach
|
||||
|
||||
### FENCE_TYPE {#FENCE_TYPE}
|
||||
|
||||
(Bitmask)
|
||||
(Bitmask) Fence types to enable or disable when using [MAV_CMD_DO_FENCE_ENABLE](#MAV_CMD_DO_FENCE_ENABLE).
|
||||
|
||||
Note that at least one of these flags must be set in [MAV_CMD_DO_FENCE_ENABLE](#MAV_CMD_DO_FENCE_ENABLE).param2.
|
||||
If none are set, the flight stack will ignore the field and enable/disable its default set of fences (usually all of them).
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------- | ---------------------- |
|
||||
| <a id='FENCE_TYPE_ALL'></a>0 | [FENCE_TYPE_ALL](#FENCE_TYPE_ALL) | All fence types |
|
||||
| <a id='FENCE_TYPE_ALT_MAX'></a>1 | [FENCE_TYPE_ALT_MAX](#FENCE_TYPE_ALT_MAX) | Maximum altitude fence |
|
||||
| <a id='FENCE_TYPE_CIRCLE'></a>2 | [FENCE_TYPE_CIRCLE](#FENCE_TYPE_CIRCLE) | Circle fence |
|
||||
| <a id='FENCE_TYPE_POLYGON'></a>4 | [FENCE_TYPE_POLYGON](#FENCE_TYPE_POLYGON) | Polygon fence |
|
||||
@@ -4271,14 +4260,15 @@ Actuator output function. Values greater or equal to 1000 are autopilot-specific
|
||||
|
||||
### AUTOTUNE_AXIS {#AUTOTUNE_AXIS}
|
||||
|
||||
(Bitmask) Enable axes that will be tuned via autotuning. Used in [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).
|
||||
(Bitmask) Axes that will be autotuned by [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
| ----------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
|
||||
| <a id='AUTOTUNE_AXIS_DEFAULT'></a>0 | [AUTOTUNE_AXIS_DEFAULT](#AUTOTUNE_AXIS_DEFAULT) | Flight stack tunes axis according to its default settings. |
|
||||
| <a id='AUTOTUNE_AXIS_ROLL'></a>1 | [AUTOTUNE_AXIS_ROLL](#AUTOTUNE_AXIS_ROLL) | Autotune roll axis. |
|
||||
| <a id='AUTOTUNE_AXIS_PITCH'></a>2 | [AUTOTUNE_AXIS_PITCH](#AUTOTUNE_AXIS_PITCH) | Autotune pitch axis. |
|
||||
| <a id='AUTOTUNE_AXIS_YAW'></a>4 | [AUTOTUNE_AXIS_YAW](#AUTOTUNE_AXIS_YAW) | Autotune yaw axis. |
|
||||
Note that at least one flag must be set in [MAV_CMD_DO_AUTOTUNE_ENABLE](#MAV_CMD_DO_AUTOTUNE_ENABLE).param2: if none are set, the flight stack will tune its default set of axes.
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
| --------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------ |
|
||||
| <a id='AUTOTUNE_AXIS_ROLL'></a>1 | [AUTOTUNE_AXIS_ROLL](#AUTOTUNE_AXIS_ROLL) | Autotune roll axis. |
|
||||
| <a id='AUTOTUNE_AXIS_PITCH'></a>2 | [AUTOTUNE_AXIS_PITCH](#AUTOTUNE_AXIS_PITCH) | Autotune pitch axis. |
|
||||
| <a id='AUTOTUNE_AXIS_YAW'></a>4 | [AUTOTUNE_AXIS_YAW](#AUTOTUNE_AXIS_YAW) | Autotune yaw axis. |
|
||||
|
||||
### PREFLIGHT_STORAGE_PARAMETER_ACTION {#PREFLIGHT_STORAGE_PARAMETER_ACTION}
|
||||
|
||||
@@ -5840,6 +5830,14 @@ See https://mavlink.io/en/services/standard_modes.html
|
||||
| <a id='MAV_MODE_PROPERTY_NOT_USER_SELECTABLE'></a>2 | [MAV_MODE_PROPERTY_NOT_USER_SELECTABLE](#MAV_MODE_PROPERTY_NOT_USER_SELECTABLE) | If set, this mode should not be added to the list of selectable modes.<br>The mode might still be selected by the FC directly (for example as part of a failsafe). |
|
||||
| <a id='MAV_MODE_PROPERTY_AUTO_MODE'></a>4 | [MAV_MODE_PROPERTY_AUTO_MODE](#MAV_MODE_PROPERTY_AUTO_MODE) | If set, this mode is automatically controlled (it may use but does not require a manual controller).<br>If unset the mode is a assumed to require user input (be a manual mode). |
|
||||
|
||||
### HIL_ACTUATOR_CONTROLS_FLAGS {#HIL_ACTUATOR_CONTROLS_FLAGS}
|
||||
|
||||
(Bitmask) Flags used in [HIL_ACTUATOR_CONTROLS](#HIL_ACTUATOR_CONTROLS) message.
|
||||
|
||||
| 值 | Name | 描述 |
|
||||
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
|
||||
| <a id='HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP'></a>1 | [HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP](#HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP) | Simulation is using lockstep |
|
||||
|
||||
### MAV_AUTOPILOT — \[from: [minimal](../messages/minimal.md#MAV_AUTOPILOT)\] {#MAV_AUTOPILOT}
|
||||
|
||||
Micro air vehicle / autopilot classes. 这里标明了每个单个模型。
|
||||
@@ -6982,15 +6980,15 @@ The persistence/lifetime of the setting is undefined.
|
||||
Depending on flight stack implementation it may persist until superseded, or it may revert to a system default at the end of a mission.
|
||||
Flight stacks typically reset the setting to system defaults on reboot.
|
||||
|
||||
| Param (Label) | 描述 | 值 |
|
||||
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | enable? (0=disable, 1=enable, 2=disable_floor_only) | min: 0 max: 2 inc: 1 |
|
||||
| 2 (Types) | Fence types to enable or disable as a bitmask. A value of 0 indicates that all fences should be enabled or disabled. This parameter is ignored if param 1 has the value 2 | [FENCE_TYPE](#FENCE_TYPE) |
|
||||
| 3 | Empty | |
|
||||
| 4 | Empty | |
|
||||
| 5 | Empty | |
|
||||
| 6 | Empty | |
|
||||
| 7 | Empty | |
|
||||
| Param (Label) | 描述 | 值 |
|
||||
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | enable? (0=disable, 1=enable, 2=disable_floor_only) | min: 0 max: 2 inc: 1 |
|
||||
| 2 (Types) | Fence types to enable or disable as a bitmask. 0: field is unused/all fences should be enabled or disabled (for compatiblity reasons). Parameter is ignored if param1=2. | [FENCE_TYPE](#FENCE_TYPE) |
|
||||
| 3 | Empty | |
|
||||
| 4 | Empty | |
|
||||
| 5 | Empty | |
|
||||
| 6 | Empty | |
|
||||
| 7 | Empty | |
|
||||
|
||||
### MAV_CMD_DO_PARACHUTE (208) {#MAV_CMD_DO_PARACHUTE}
|
||||
|
||||
@@ -7052,15 +7050,15 @@ Mission command to operate a gripper.
|
||||
|
||||
Enable/disable autotune.
|
||||
|
||||
| Param (Label) | 描述 | 值 |
|
||||
| -------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | Enable (1: enable, 0:disable). | min: 0 max: 1 inc: 1 |
|
||||
| 2 (Axis) | Specify which axis are autotuned. 0 indicates autopilot default settings. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS) |
|
||||
| 3 | Empty. | |
|
||||
| 4 | Empty. | |
|
||||
| 5 | Empty. | |
|
||||
| 6 | Empty. | |
|
||||
| 7 | Empty. | |
|
||||
| Param (Label) | 描述 | 值 |
|
||||
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- |
|
||||
| 1 (Enable) | Enable (1: enable, 0:disable). | min: 0 max: 1 inc: 1 |
|
||||
| 2 (Axis) | Specify axes for which autotuning is enabled/disabled. 0 indicates the field is unused (for compatiblity reasons). If 0 the autopilot will follow its default behaviour, which is usually to tune all axes. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS) |
|
||||
| 3 | Empty. | |
|
||||
| 4 | Empty. | |
|
||||
| 5 | Empty. | |
|
||||
| 6 | Empty. | |
|
||||
| 7 | Empty. | |
|
||||
|
||||
### MAV_CMD_NAV_SET_YAW_SPEED (213) {#MAV_CMD_NAV_SET_YAW_SPEED}
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ span.warning {
|
||||
| -------------------------- | ------- | -------- |
|
||||
| [Messages](#messages) | 12 | 229 |
|
||||
| [Enums](#enumerated-types) | 11 | 146 |
|
||||
| [Commands](#mav_commands) | 172 | 0 |
|
||||
| [Commands](#mav_commands) | 173 | 0 |
|
||||
|
||||
The following sections list all entities in the dialect (both included and defined in this file).
|
||||
|
||||
@@ -487,6 +487,27 @@ Recipients must reject command addressed to broadcast system ID.
|
||||
| 3 (Reboot) | Reboot components after ID change. Any non-zero value triggers the reboot. | |
|
||||
| 4 | | |
|
||||
|
||||
### MAV_CMD_DO_SET_GLOBAL_ORIGIN (611) — [WIP] {#MAV_CMD_DO_SET_GLOBAL_ORIGIN}
|
||||
|
||||
<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
|
||||
|
||||
Sets the GNSS coordinates of the vehicle local origin (0,0,0) position.
|
||||
|
||||
Vehicle should emit [GPS_GLOBAL_ORIGIN](#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](#SET_GPS_GLOBAL_ORIGIN).
|
||||
Should be sent in a [COMMAND_INT](#COMMAND_INT) (Expected frame is [MAV_FRAME_GLOBAL](#MAV_FRAME_GLOBAL), and this should be assumed when sent in [COMMAND_LONG](#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_ODID_SET_EMERGENCY (12900) — [WIP] {#MAV_CMD_ODID_SET_EMERGENCY}
|
||||
|
||||
<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
|
||||
|
||||
@@ -116,3 +116,4 @@ Mode currently commanded by pilot
|
||||
| <a id='PILOT_ROTO'></a>3 | [PILOT_ROTO](#PILOT_ROTO) | 旋转模式 |
|
||||
|
||||
## Commands (MAV_CMD) {#mav_commands}
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Heartbeat/Connection Protocol
|
||||
# 心跳/连接协议
|
||||
|
||||
The heartbeat protocol is used to advertise the existence of a system on the MAVLink network, along with its system and component id, vehicle type, flight stack, component type, and flight mode.
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Microservices
|
||||
#
|
||||
|
||||
The MAVLink "microservices" define higher-level protocols that MAVLink systems can adopt in order to better inter-operate.
|
||||
For example, _QGroundControl_, ArduPilot and PX4 autopilots all share a common [Command Protocol](../services/command.md) for sending point-to-point messages that require an acknowledgment.
|
||||
|
||||
Reference in New Issue
Block a user