HARDWARE

What it runs on.

ADOS is software. It does not sell you a board, it adopts the one you already chose. Nineteen board profiles ship in the agent's hardware abstraction layer, plus generic ARM64 and x86_64 fallbacks, each declaring its SoC, its accelerator and what the agent may switch on. Board identity is detected from the device tree at boot, not configured by hand.
19
Companion boards, plus 2 fallbacks
2
Injection chipsets
4
Autopilot firmwares

Flight controller, companion computer and radio, one stack.

Flight controller, companion computer and radio, one stack.

COMPANION BOARDS

Nineteen boards, two fallbacks

The tier is a RAM class the agent reports and Mission Control displays. The accelerator note is what the profile declares. The agent only counts it toward local detection when its vision engine has a backend that can actually drive that silicon.

Raspberry Pi 5BCM2712 · tier 4 · CPU ONNX
Raspberry Pi CM5BCM2712 · tier 4 · CPU ONNX
Raspberry Pi 4BBCM2711 · tier 3
Raspberry Pi CM4BCM2711 · tier 3
Raspberry Pi 3BCM2837 · tier 2
Raspberry Pi CM3BCM2837 · tier 2
Raspberry Pi Zero 2 WBCM2710A1 · tier 2 · experimental
Radxa ROCK 5C LiteRK3582 · tier 4 · 6 TOPS NPU
Radxa CM4 (RK3588S2)RK3588S2 · tier 4 · 6 TOPS NPU
Orange Pi 5RK3588S · tier 4
Rockchip RK3576 referenceRK3576 · tier 3 · 6 TOPS NPU
Radxa CM3 (RK3566)RK3566 · tier 3 · 0.8 TOPS NPU
Rockchip RV1126BRV1126B · armv7l · tier 3 · 2 TOPS NPU
Radxa Cubie A7SAllwinner A733 · tier 3 · 3 TOPS NPU · CPU ONNX · experimental
Radxa Cubie A7ZAllwinner A733 · tier 2 · 3 TOPS NPU · experimental
NVIDIA Jetson Orin NanoTegra Orin · tier 4
NVIDIA Jetson NanoTegra X1 · tier 3
BeagleY-AITI AM67A · tier 3 · experimental
D-Robotics RDK X3Sunrise X3 · tier 3 · experimental
Generic ARM64 and x86_64fallback profiles · tier from measured RAM

A few entries deserve a footnote. The RDK X3 and the BeagleY-AI both carry real accelerators that only their vendor toolchains can drive, so their profiles declare zero and detection runs on a paired compute node instead of pretending. The A733 NPU on the two Cubie boards is declared as hardware only; the vision engine has no backend for it, so the A7S runs detection on its CPU through ONNX. The Jetsons and the Orange Pi 5 have silicon the profiles have not characterised yet, so they read as no accelerator until they do. A board that is not in this list still runs the agent through a generic fallback, just without the profile-specific display, camera and radio bindings.

TIERS

What a tier means

The agent classifies a board by RAM and publishes the result on its status surface. Mission Control shows it next to the node, and an extension that needs a bigger board is refused at install instead of failing at run time.

Board tier by memory
Tier 1, under 512 MB
no compute
Tier 2, 512 MB to 2 GB
basic compute
Tier 3, 2 GB to 4 GB
full agent
Tier 4, over 4 GB
swarm capable

Perception is tiered separately. A board with a usable NPU, or one whose profile declares CPU ONNX, runs detection locally. A board with neither offloads detection to a paired compute node when an extension holds a live, reachable offload link, and otherwise runs odometry only, with no detection or tracking.

RADIO

Two chipsets for the long-range link

The video and telemetry link injects raw 802.11 frames, which only a handful of USB WiFi chipsets do reliably. The compat table is generated once and consumed by both the Python and the Rust adapter selectors, so the two can never disagree about what is supported.

RTL8812EUthe validated injection radio
RTL8812AUsupported, ranked below EU
Link parameters
Channel width
20 MHz
Driver install
DKMS, or prebuilt module
Mesh carrier
any 802.11s or IBSS adapter
Onboard management WiFi
excluded from injection

Eight USB vendor and product id pairs map onto those two families, including the common TP-Link rebadges. One id ships on both AU and EU hardware, so the agent disambiguates from the bound kernel driver rather than the id alone. Channel width is pinned at 20 MHz because the vendored driver has no narrowband symbol and 40 MHz has open upstream defects. A mesh relay needs a second dongle, and that one is not restricted to Realtek.

Five board families get a prebuilt kernel module so the install does not compile on the drone: the Pi v8 and 2712 kernels, the Radxa A733 and RK356x kernels, and the Armbian RK35xx kernel. Every other board builds the module on device. A new board profile cannot merge until it declares which of the two it is.

FLIGHT CONTROLLERS

Four firmware families, detected not configured

Betaflight and iNav are identified from the product and manufacturer strings of the USB descriptor when the agent opens the port. ArduPilot and PX4 are identified from the autopilot field of a live heartbeat, so a stale guess cannot survive a disconnect.

ArduPilotMAVLink · autopilot id 3
PX4MAVLink · autopilot id 12
BetaflightMSP · named in the USB descriptor
iNavMSP · named in the USB descriptor

Mission Control mirrors the same decision when it talks to a board directly over USB with no agent in the path: it tries a MAVLink heartbeat first, then an MSP handshake, and picks the adapter from the answer. Descriptor-based MSP identification on the agent is Linux-only; on any other host the agent reports no variant and Mission Control does the handshake itself.

PAYLOADS

Cameras, gimbals and pods come from extensions

Payload hardware is not compiled into the agent. It arrives as a signed extension that declares the capabilities it needs, and the host grants them one at a time.

Hardware reached by first-party extensions
SIYI optical pods
A2 mini, A8 mini, ZR10, ZR30, ZT6, ZT30
MAVLink gimbals
gimbal-manager component 154
Downward nav camera
USB UVC or CSI, via V4L2
Optional rangefinder
TF-Luna, LIDAR-Lite, VL53L1X
Thermal camera
FLIR Lepton 3.5 on a PureThermal 2 USB dongle

The SIYI extension fails closed on a pod it cannot identify rather than guessing a protocol. The gimbal extension speaks the MAVLink gimbal-manager protocol and nothing else, so it works with any autopilot that forwards those messages and with no serial-only gimbal. The downward camera path is optical flow with a scale ladder, not visual-inertial odometry.

NEW BOARD

Bringing up something not on the list

Two paths. Force an existing profile at run time, or add a profile and let CI hold you to it.

shell
$# Force a known profile on an unrecognised box:
echo "rpi4b" | sudo tee /etc/ados/board_override
sudo reboot

# What the agent thinks it is running on:
ados hardware show

A real profile is a YAML file in the agent's board directory, validated against a typed schema at load. Three CI gates then apply: the profile must declare whether its radio driver is prebuilt or compiled on device, no two profiles may match the same device-tree string, and every profile must carry a valid display section. That is deliberately more friction than a config file, because a board profile is what decides which GPIO the agent is allowed to drive.

Get Early Access