Skip to content

ADOS Mission Control

  • Software
  • Drones and boats
  • Tool

A browser-based ground control station for drones that connects to ArduPilot, PX4, Betaflight and iNav flight controllers over USB or WebSocket, with mission planning, flying and 3D simulation.

Made by altnautica.

Source on GitHub: github.com/altnautica/ADOSMissionControl (opens in a new tab). Facts read at commit fc8961b (opens in a new tab).

Licenses

Code
GPL-3.0-only (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (GPL-3.0-only) at commit fc8961b (opens in a new tab), on 22 Oct 2026.

Commercial use
Yes

Copyleft: Modified source must be published.

What it does

  • Connects to MAVLink and MSP flight controllers via WebSerial, WebSocket, or a paired ADOS agent on the LAN, with no driver install.
  • Offers more than 80 panels for flight controller setup, covering calibration, PID tuning, receivers, failsafe, OSD and firmware flashing.
  • Plans missions on a map with survey, orbit, corridor and search pattern generators, terrain following, geofences and validation before upload.
  • Flies with a gamepad, HOTAS, RC transmitter or keyboard at 50 Hz, with arm/disarm, mode switching and a kill switch.
  • Simulates and replays missions on a CesiumJS 3D globe with real terrain before flight.
  • Analyzes flight data with FFT-driven noise and motor-health checks to suggest filter and PID settings.

Written by Robotheca from the project's README (opens in a new tab) at commit fc8961b.

Getting started

Difficulty
Intermediate
Hardware it needs, as the project states it
A browser; Chrome 89+ or Edge 89+ is recommended for WebSerial and WebUSB, and a desktop build is available for macOS, Windows and Linux. 3D features benefit from a dedicated GPU but work without one at lower frame rates. Paired ADOS Drone Agent runs on a drone's companion computer.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
22 Oct 2026 on main
Latest release
0.61.0 (22 Oct 2026)

Checked on GitHub on 22 Oct 2026.

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.