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

AVAILABLE_MODES_MONITOR message - attempt to reduce ambiguityu (#2447)

Browse Source
This commit is contained in:
Hamish Willee
2026-03-26 14:50:34 +11:00
committed by GitHub
parent 2abff2cb58
commit 2bb03f5eb2
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
message_definitions/v1.0/common.xml
+5 -3
View File
@@ -8091,9 +8091,11 @@
<field type="uint32_t" name="intended_custom_mode" invalid="0">The custom_mode of the mode that was last commanded by the user (for example, with MAV_CMD_DO_SET_STANDARD_MODE, MAV_CMD_DO_SET_MODE or via RC). This should usually be the same as custom_mode. It will be different if the vehicle is unable to enter the intended mode, or has left that mode due to a failsafe condition. 0 indicates the intended custom mode is unknown/not supplied</field>
</message>
<message id="437" name="AVAILABLE_MODES_MONITOR">
<description>A change to the sequence number indicates that the set of AVAILABLE_MODES has changed.
A receiver must re-request all available modes whenever the sequence number changes.
This is only emitted after the first change and should then be broadcast at low rate (nominally 0.3 Hz) and on change.
<description>A change to the sequence number indicates that the set of AVAILABLE_MODES has changed, and that the receiver should re-request all available modes.
The message is optional, and is only needed when the set of modes can change dynamically after boot.
It should be emitted whenever the set of modes change.
It should be streamed at low rate (nominally 0.3 Hz).
See https://mavlink.io/en/services/standard_modes.html
</description>
<field type="uint8_t" name="seq">Sequence number. The value iterates sequentially whenever AVAILABLE_MODES changes (e.g. support for a new mode is added/removed dynamically).</field>