Vehicle data & robotics · 35 of 40

ArduPilot, ArduSub, and MAVLink: know the pieces

Separate vehicle-control software from the messaging protocol and from the downstream systems that use selected telemetry.

Why this matters

ArduPilot, ArduSub, and MAVLink are related, but they are not interchangeable. Understanding the boundary between them prevents a data platform from accidentally being described as the vehicle controller.

Learn it

ArduPilot is an open-source autopilot platform supporting multiple vehicle types. ArduSub is the ArduPilot vehicle stack for submersible ROVs. MAVLink is a lightweight messaging protocol used by autopilots, ground-control software, companion computers, cameras, and other components to exchange telemetry, state, commands, mission information, and more. Ground-control and autopilot software remain responsible for vehicle operation; Atlasemoji can work with selected data, observations, spatial context, rules, and downstream workflows.

Work through an example

A submersible can run ArduSub on its autopilot, exchange MAVLink messages with a surface or companion computer, and have a gateway forward selected observations into AtlasEvo.

Keep control and data workflow separate

vehicle
  ↓ controlled by
autopilot running ArduPilot/ArduSub
  ↕ MAVLink
ground control / companion / gateway
  ↓ selected data
GIS + observation workflow

Practice

1Draw vehicle → autopilot → MAVLink → gateway/companion → destination.
2Label which component controls the vehicle and which components only receive or transform data.
3List the specific data you want downstream instead of writing 'all telemetry'.

What to watch for

MAVLink is not the autopilot. ArduSub is not the transport link. Atlasemoji should not be described as replacing the ground-control or autopilot system.

Where this takes you

This is the preparation for research vehicles, student robotics, underwater observation, drone/rover data, and any workflow that turns vehicle data into spatial records.