minimal.xml 0 Enum used to indicate true or false (also: success or failure, enabled or disabled, active or inactive). False. True. Bitmask of (optional) autopilot capabilities (64 bit). If a bit is set, the autopilot supports this capability. Autopilot supports the MISSION_ITEM float message type. Note that MISSION_ITEM is deprecated, and autopilots should use MISSION_ITEM_INT instead. Autopilot supports the new param float message type. Autopilot supports MISSION_ITEM_INT scaled integer message type. Note that this flag must always be set if missions are supported, because missions must always use MISSION_ITEM_INT (rather than MISSION_ITEM, which is deprecated). Autopilot supports COMMAND_INT scaled integer message type. Parameter protocol uses byte-wise encoding of parameter values into param_value (float) fields: https://mavlink.io/en/services/parameter.html#parameter-encoding. Note that either this flag or MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_C_CAST should be set if the parameter protocol is supported. Autopilot supports the File Transfer Protocol v1: https://mavlink.io/en/services/ftp.html. Autopilot supports the SET_ATTITUDE_TARGET message (for commanding attitude from an offboard controller). Autopilot supports the SET_POSITION_TARGET_LOCAL_NED message (for commanding position and velocity targets in local NED frame). Autopilot supports the SET_POSITION_TARGET_GLOBAL_INT message (for commanding position and velocity targets in global scaled integers). Autopilot supports terrain protocol / data handling. Reserved for future use. Autopilot supports the MAV_CMD_DO_FLIGHTTERMINATION command (flight termination). Autopilot supports onboard compass calibration. Autopilot supports MAVLink version 2. Autopilot supports mission fence protocol. Autopilot supports mission rally point protocol. Reserved for future use. Parameter protocol uses C-cast of parameter values to set the param_value (float) fields: https://mavlink.io/en/services/parameter.html#parameter-encoding. Note that either this flag or MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_BYTEWISE should be set if the parameter protocol is supported. This component implements/is a gimbal manager. This means the GIMBAL_MANAGER_INFORMATION, and other messages can be requested. Component supports locking control to a particular GCS independent of its system (via MAV_CMD_REQUEST_OPERATOR_CONTROL). Autopilot has a connected gripper. MAVLink Grippers would set MAV_TYPE_GRIPPER instead. These values define the type of firmware release. These values indicate the first version or release of this type. For example the first alpha release would be 64, the second would be 65. development release alpha release beta release release candidate official stable release The filtered global position (e.g. fused GPS and accelerometers). The position is in GPS-frame (right-handed, Z-up). It is designed as scaled integer message since the resolution of float is not sufficient. Timestamp (time since system boot). Latitude, expressed Longitude, expressed Altitude (MSL). Note that virtually all GPS modules provide both WGS84 and MSL. Altitude above home Ground X Speed (Latitude, positive north) Ground Y Speed (Longitude, positive east) Ground Z Speed (Altitude, positive down) Vehicle heading (yaw angle), 0.0..359.99 degrees. If unknown, set to: UINT16_MAX Version and capability of autopilot software. This should be emitted in response to a request with MAV_CMD_REQUEST_MESSAGE. Bitmap of capabilities Firmware version number. 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). Middleware version number Operating system version number HW / board version (last 8 bits should be silicon ID, if any). The first 16 bits of this field specify a board type from an enumeration stored at https://github.com/PX4/PX4-Bootloader/blob/master/board_types.txt and with extensive additions at https://github.com/ArduPilot/ardupilot/blob/master/Tools/AP_Bootloader/board_types.txt 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. 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. 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. ID of the board vendor ID of the product UID if provided by hardware (see uid2) UID if provided by hardware (supersedes the uid field. If this is non-zero, use this field, otherwise use uid)