mirror/mavlink
1
0
Fork 0
mirror of https://github.com/mavlink/mavlink.git synced 2026-06-19 07:35:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

PROTOCOL_VERSION - move to common and remove WIP (#2318)

Browse Source 
* minimal.xml - PROTOCOL_VERSION is not WIP

* move PROTOCOL_VERSION to common.xml
This commit is contained in:
Hamish Willee
2025-10-29 14:33:40 +11:00
committed by GitHub
parent ff0432a640
commit 8ec715d4a6
2 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
message_definitions/v1.0/common.xml
+8
View File
@@ -7434,6 +7434,14 @@
<field type="int8_t" name="mode" enum="WIFI_CONFIG_AP_MODE">WiFi Mode.</field>
<field type="int8_t" name="response" enum="WIFI_CONFIG_AP_RESPONSE">Message acceptance response (sent back to GS).</field>
</message>
<message id="300" name="PROTOCOL_VERSION">
<description>Version and capability of protocol version. This message can be requested with 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 to enable the handshaking. Library implementers should consider adding this into the default decoding state machine to allow the protocol core to respond directly.</description>
<field type="uint16_t" name="version">Currently active MAVLink version number * 100: v1.0 is 100, v2.0 is 200, etc.</field>
<field type="uint16_t" name="min_version">Minimum MAVLink version supported</field>
<field type="uint16_t" name="max_version">Maximum MAVLink version supported (set to the same value as version by default)</field>
<field type="uint8_t[8]" name="spec_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
<field type="uint8_t[8]" name="library_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
</message>
<message id="301" name="AIS_VESSEL">
<description>The location and information of an AIS vessel</description>
<field type="uint32_t" name="MMSI">Mobile Marine Service Identifier, 9 decimal digits</field>
message_definitions/v1.0/minimal.xml
-10
View File
@@ -750,15 +750,5 @@
<field type="uint8_t" name="system_status" enum="MAV_STATE">System status flag.</field>
<field type="uint8_t_mavlink_version" name="mavlink_version">MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version</field>
</message>
<message id="300" name="PROTOCOL_VERSION">
<wip/>
<!-- This message is work-in-progress and it can therefore change. It should NOT be used in stable production environments. -->
<description>Version and capability of protocol version. This message can be requested with 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 to enable the handshaking. Library implementers should consider adding this into the default decoding state machine to allow the protocol core to respond directly.</description>
<field type="uint16_t" name="version">Currently active MAVLink version number * 100: v1.0 is 100, v2.0 is 200, etc.</field>
<field type="uint16_t" name="min_version">Minimum MAVLink version supported</field>
<field type="uint16_t" name="max_version">Maximum MAVLink version supported (set to the same value as version by default)</field>
<field type="uint8_t[8]" name="spec_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
<field type="uint8_t[8]" name="library_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
</message>
</messages>
</mavlink>