MAVLink messages update Wed Oct 29 03:34:09 UTC 2025

Author: PX4BuildBot

en/messages/common.md

@@ -37,7 +37,7 @@ span.warning {
 
 Type | Defined | Included
 --- | --- | ---
-[Messages](#messages) | 227 | 4
+[Messages](#messages) | 228 | 3
 [Enums](#enumerated-types) | 143 | 9
 [Commands](#mav_commands) | 165 | 0
 
@@ -3034,9 +3034,7 @@ password | `char[64]` | | Password. Blank for an open AP. MD5 hash when message
 <span class='ext'>response</span> <a href='#mav2_extension_field'>++</a> | `int8_t` | [WIFI_CONFIG_AP_RESPONSE](#WIFI_CONFIG_AP_RESPONSE) | Message acceptance response (sent back to GS). 
 
 
-### PROTOCOL_VERSION (300) — \[from: [minimal](../messages/minimal.md#PROTOCOL_VERSION)\] [WIP] {#PROTOCOL_VERSION}
-
-<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
+### PROTOCOL_VERSION (300) {#PROTOCOL_VERSION}
 
 Version and capability of protocol version. This message can be requested with [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) and is used as part of the handshaking to establish which MAVLink version should be used on the network. Every node should respond to a request for [PROTOCOL_VERSION](#PROTOCOL_VERSION) to enable the handshaking. Library implementers should consider adding this into the default decoding state machine to allow the protocol core to respond directly.
 

en/messages/loweheiser.md

@@ -34,7 +34,7 @@ span.warning {
 
 Type | Defined | Included
 --- | --- | ---
-[Messages](#messages) | 1 | 2
+[Messages](#messages) | 1 | 1
 [Enums](#enumerated-types) | 0 | 6
 [Commands](#mav_commands) | 1 | 0
 

en/messages/minimal.md

@@ -38,7 +38,7 @@ span.warning {
 
 Type | Defined | Included
 --- | --- | ---
-[Messages](#messages) | 2 | 0
+[Messages](#messages) | 1 | 0
 [Enums](#enumerated-types) | 6 | 0
 Commands | 0 | 0
 
@@ -60,21 +60,6 @@ system_status | `uint8_t` | [MAV_STATE](#MAV_STATE) | System status flag.
 mavlink_version | `uint8_t_mavlink_version` | | MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version 
 
 
-### PROTOCOL_VERSION (300) — [WIP] {#PROTOCOL_VERSION}
-
-<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
-
-Version and capability of protocol version. This message can be requested with [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) and is used as part of the handshaking to establish which MAVLink version should be used on the network. Every node should respond to a request for [PROTOCOL_VERSION](#PROTOCOL_VERSION) to enable the handshaking. Library implementers should consider adding this into the default decoding state machine to allow the protocol core to respond directly.
-
-Field Name | Type | Description
---- | --- | ---
-version | `uint16_t` | Currently active MAVLink version number * 100: v1.0 is 100, v2.0 is 200, etc. 
-min_version | `uint16_t` | Minimum MAVLink version supported 
-max_version | `uint16_t` | Maximum MAVLink version supported (set to the same value as version by default) 
-spec_version_hash | `uint8_t[8]` | The first 8 bytes (not characters printed in hex!) of the git hash. 
-library_version_hash | `uint8_t[8]` | The first 8 bytes (not characters printed in hex!) of the git hash. 
-
-
 ## Enumerated Types
 
 ### MAV_AUTOPILOT {#MAV_AUTOPILOT}

en/messages/standard.md

@@ -34,7 +34,7 @@ span.warning {
 
 Type | Defined | Included
 --- | --- | ---
-[Messages](#messages) | 2 | 2
+[Messages](#messages) | 2 | 1
 [Enums](#enumerated-types) | 3 | 6
 Commands | 0 | 0