Dialect: all

This dialect is intended to include all other dialects in the mavlink/mavlink repository (including external dialects).

Dialects that are in all.xml are guaranteed to not have clashes in messages, enums, enum ids, and MAV_CMDs. This ensure that:

  • Systems based on these dialects can co-exist on the same MAVLink network.
  • A Ground Station might (optionally) use libraries generated from all.xml to communicate using any of the dialects.

New dialect files in the official repository must be added to all.xml and restrict themselves to using ids in their own allocated range. A few older dialects are not included because these operate in completely closed networks or because they are only used for tests.

This topic is a human-readable form of the XML definition file: all.xml.

MAVLink 2 messages have an ID > 255 and are marked up using (MAVLink 2) in their description.

MAVLink 2 extension fields that have been added to MAVLink 1 messages are displayed in blue.

MAVLink Include Files: ardupilotmega.xml

MAVLink Include Files: ASLUAV.xml

MAVLink Include Files: common.xml

MAVLink Include Files: development.xml

MAVLink Include Files: icarous.xml

MAVLink Include Files: minimal.xml

MAVLink Include Files: python_array_test.xml

MAVLink Include Files: standard.xml

MAVLink Include Files: test.xml

MAVLink Include Files: ualberta.xml

MAVLink Include Files: uAvionix.xml

MAVLink Include Files: storm32.xml

MAVLink Include Files: AVSSUAS.xml

MAVLink Include Files: cubepilot.xml

MAVLink Include Files: csAirLink.xml

MAVLink Messages

results matching ""

    No results matching ""