forked from mavlink/mavlink
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create development.xml and seed with MISSION_CHECKSUM (mavlink#1611)
- Loading branch information
1 parent
26ac90c
commit 09f8c9e
Showing
2 changed files
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
<?xml version="1.0"?> | ||
<mavlink> | ||
<!-- XML file for prototyping definitions for standard.xml --> | ||
<include>standard.xml</include> | ||
<version>0</version> | ||
<dialect>0</dialect> | ||
<enums> | ||
<!-- none defined (yet) --> | ||
</enums> | ||
<messages> | ||
<message id="53" name="MISSION_CHECKSUM"> | ||
<wip/> | ||
<!-- This message is work-in-progress and it can therefore change. It should NOT be used in stable production environments. --> | ||
<description>Checksum for the current mission, rally points or geofence plan (a GCS can use this checksum to determine if it has a matching plan definition). | ||
This message must be broadcast following any change to a plan (immediately after the MISSION_ACK that completes the plan upload sequence). | ||
It may also be requested using MAV_CMD_REQUEST_MESSAGE, where param 2 indicates the plan type for which the hash is required. | ||
The checksum must be calculated on the autopilot, but may also be calculated by the GCS. | ||
The checksum uses the same CRC32 algorithm as MAVLink FTP (https://mavlink.io/en/services/ftp.html#crc32-implementation). | ||
It is run over each item in the plan in seq order (excluding the home location if present in the plan), and covers the following fields (in order): | ||
frame, command, autocontinue, param1, param2, param3, param4, param5, param6, param7. | ||
</description> | ||
<field type="uint8_t" name="mission_type" enum="MAV_MISSION_TYPE">Mission type.</field> | ||
<field type="uint32_t" name="checksum">CRC32 checksum of current plan for specified type.</field> | ||
</message> | ||
</messages> | ||
</mavlink> |