Feature matrix
Stick control streams only while it is switched on, the aircraft is armed and the flight mode gives the pilot stick authority. On MSP links it overrides every RC channel. See Cockpit and Skills.
The demo fleet includes aircraft on every firmware. See Dashboard and fleet.
Shared panels
The Setup tab uses one set of panels across firmwares and adapts each panel to the connected firmware. For example, Receiver reads RC settings from parameters on ArduPilot and PX4 and fromMSP_RX_CONFIG on Betaflight and iNav. Panels gate on firmware capability, vehicle class and firmware type. The full list is on Flight controller setup.
Firmware-specific panels
Choosing a firmware
- Survey, mapping or delivery aircraft: ArduPilot offers the widest feature set. iNav on a small F7 or H7 board covers many autonomous missions at lower weight.
- FPV with position hold or return to home: iNav.
- FPV racing or freestyle: Betaflight.
- MAVLink ecosystem integration: PX4 or ArduPilot, depending on the airframe and mission.
Outside Mission Control
- Telemetry on the RC transmitter (SmartPort, CRSF, LTM) is handled by the RC system.
- Goggle OSD rendering happens on the aircraft. Mission Control configures what the OSD shows, not how goggles render it.
- Dense mapping, terrain meshes and multi-drone aggregation live in the Drone Agent, not in Mission Control.
- Phones: Mission Control targets desktops, laptops and landscape tablets. For a phone, use the Android GCS.
Next steps
iNav guide
iNav-specific workflows.
Connect a drone
USB, WebSocket, UDP, TCP and Bluetooth links.
Flight controller setup
Every Setup tab panel.