Skip to main content
Mission Control supports four firmware families. Pick the one that matches your flight controller and your mission profile. This page shows what works where.

​
Quick matrix

​
Shared panels

All four firmwares share the same Configure-tab base: Flight Modes, Failsafe, PID Tuning, Power, Receiver, Ports, Sensors, GPS, LED, OSD, CLI, Calibration, Firmware Flasher, Blackbox. Mission Control adapts each shared panel to the connected firmware. For example, the Receiver panel reads RC configuration via MAVLink parameters on ArduPilot / PX4 and via MSP_RX_CONFIG on Betaflight / iNav. Operators see a single panel, the protocol layer handles the dispatch.

​
iNav-specific panels

13 panels only appear when iNav is connected:
  • Safehome (16 alternate RTH points)
  • Geozones (polygon and circular fences)
  • Nav Config (waypoint speed, RTH altitude, landing slowdown)
  • INav Failsafe (FAILSAFE_PROCEDURE: DROP, LAND, RTH)
  • Battery Profiles (4)
  • Control Profiles (3)
  • Mixer Profiles (3)
  • Output Mapping (timer-to-output with mode override)
  • Servos (fixed-wing and tricopter)
  • Temp Sensors (8)
  • MC Braking (multirotor)
  • Rate Dynamics
  • iNav Mission (read-only mission summary with planner link)
Plus the Tier B panels: Logic Conditions, Global Variables, Programming PID, EZ Tune, FW Approach, iNav OSD, Custom OSD Elements.

​
Betaflight-specific panels

Aux Modes, Betaflight Config, Betaflight Motors, VTX, Rate Profile, Adjustments, Blackbox config, OSD editor.

​
PX4-specific panels

Airframe selector (SYS_AUTOSTART), Actuator configuration, MAVLink Shell.

​
ArduPilot-specific panels

Frame class selector, Gimbal Manager, Camera, Rally Points, MAVLink Signing.

​
Choosing a firmware

Some quick rules of thumb:
  • Building a survey, mapping, or delivery drone? ArduPilot on a larger flight controller gives the widest feature surface. iNav on a smaller F7 / H7 board gives enough for most civilian autonomous missions at lower weight and cost.
  • Flying FPV with occasional position hold or RTH? iNav is the sweet spot.
  • Pure FPV racing or freestyle? Betaflight stays the leanest and lowest-latency.
  • Research or defense requiring MAVLink ecosystem integration? PX4 or ArduPilot, depending on the mission profile.
All four firmwares are fully configurable, flashable, and flyable through Mission Control.

​
What is not covered by the GCS

This is where the GCS draws scope lines regardless of which firmware you use:
  • Telemetry-over-RC-link displays (SmartPort, CRSF, LTM). Mission Control connects over USB WebSerial or TCP. Telemetry that flows up a radio link to the transmitter screen is handled by the RC system itself.
  • FPV OSD rendering on goggles. DJI, Walksnail, and analog OSD are rendered on the drone by the flight controller or VTX chip. The GCS configures what appears, not how it renders in-flight.
  • Real-time dense SLAM, terrain mesh, or multi-drone aggregation. These live in the separate drone agent + ADOS MeshNet track, not in the Mission Control GCS.
  • Mobile phone-first UI. Mission Control is desktop and laptop first. Tablet landscape works. Phones are not specifically targeted.

​
Cross-references