MAVLink dialects are XML files that define protocol- and vendor-specific messages, enums and commands.
Dialects may include other MAVLink XML files, which may in turn contain other XML files. A typical pattern is for a dialect to include common.xml (containing the MAVLink standard definitions), extending it with vendor or protocol specific messages. At time of writing up to 5 levels of XML file nesting are allowed (see
MAXIMUM_INCLUDE_FILE_NESTING in mavgen.py).
Vendor forks of MAVLink may contain dialect messages that are not yet merged, and hence will not appear in this documentation.
The dialect files are stored alongside in separate XML files in mavlink/message definitions.
The human-readable forms of the XML dialect files are linked below: