MAVLink

Problem

Understanding and working with the MAVLink wire protocol that connects autopilots, ground stations, SDKs and companion computers.

Topic reviewed 2026-08-16 · Membership is an editorial index, not a compatibility or performance claim.

Engineering questions

• Which MAVLink dialect and version does each component in the stack implement?
• How do message definitions stay compatible across autopilot and GCS releases?
• When is MAVLink 1 versus MAVLink 2 behaviour a practical concern?
• What tooling exists for generating bindings and debugging traffic?

Topic map

Stack layers: communication_gcs · flight_control · edge_ai

Engineering scope and evidence boundary

MAVLink is treated here as a protocol and ecosystem boundary, not as a synonym for every communication or telemetry tag. The topic links the release records whose descriptions or recorded topics explicitly connect them to MAVLink, then preserves each record's own resource type and evidence status. That distinction matters when a reader is tracing a message library, an SDK, a ground-control application, or a flight stack: the page provides a navigable evidence set, while the individual resource detail remains authoritative for repository URLs, retrieved fields, Unknown values, and maintenance signals. The related guide and collections provide an editorial path for source tracing and system-level review.

Topic membership is an editorial index, not a compatibility or performance claim. Verify each resource through its SourceRef, retrieval date, and verification status.