One ground station, every flight controller
Firmware
Four flight stacks, two protocols
ArduPilot and PX4 over MAVLink v2. Betaflight and iNav over MSP. All from one ground station.
Parity
What each firmware supports
The ground station gates features by what the connected firmware can do. Here is how the four line up.
| ArduPilot | PX4 | Betaflight | iNav | |
|---|---|---|---|---|
| Transport | MAVLink v2 | MAVLink v2 | MSP v1/v2 | MSP v1/v2 |
| Live parameter editing | ✓ | ✓ | ✓ | ✓ |
| Parameter metadata registry | ✓ | ✓ | ✓ | ✓ |
| Mission planning | ✓ | ✓ | — | ✓ |
| Flight modes + arming | ✓ | ✓ | ✓ | ✓ |
| Calibration wizards | ✓ | ✓ | ✓ | ✓ |
| Geofence + safehomes | ✓ | ✓ | — | ✓ |
| OSD, ports + blackbox | — | — | ✓ | ✓ |
Transport
Live parameter editing
Parameter metadata registry
Mission planning
Flight modes + arming
Calibration wizards
Geofence + safehomes
OSD, ports + blackbox
Parameter registry
Complete metadata, offline
Every parameter carries its enum values, bitmask flags, ranges, units, and defaults, bundled so the editors work with no network.
A first-party parameter registry ships metadata for all four firmwares, so a bitmask field renders as labeled checkboxes and an enum renders as a named dropdown instead of a raw number. Undocumented bits are preserved on write, so an editor never silently zeroes a value it does not recognize. The registry loads from a bundled floor first, then overlays anything the firmware reports at runtime.
Architecture
One adapter per firmware
Every protocol adapter implements one unified interface, so the UI queries capabilities instead of hard-coding a firmware.
Connection lifecycle, heartbeat, identification, parameter get and set, mission upload and download, RC override, mode switching, and arm and disarm all sit behind one adapter contract. Panels read a capability type and show or hide themselves accordingly. Adding a new protocol means writing one adapter file that implements the interface, not rewriting the app.
Configure
A panel for every subsystem
A representative selection across the four firmwares. The panels you see depend on what the connected firmware supports.
Connect your flight controller
Plug in over USB or connect over the air, and configure any of the four firmwares in your browser.
Launch Mission Control