Skip to main content
iNav adds GPS navigation, waypoint missions, safehomes, geozones and a programming framework to a Betaflight-class flight controller. Mission Control speaks MSP to iNav 7.0 and later and shows the iNav panels when it detects iNav. Mission Control’s iNav support is tested against the bundled demo protocol. It has not been verified against a physical iNav flight controller.

When to use iNav

Choose iNav for waypoint missions, GPS-assisted modes (position hold, return to home, cruise) or fixed-wing autolaunch and autoland on a small flight controller. For manual FPV racing or freestyle, Betaflight is leaner. See Firmware comparison.

Connect

1

Plug in the flight controller

Power the flight controller and connect it to your computer over USB.
2

Open the Connect dialog

Click + at the top of the Fleet sidebar, or press Ctrl+K (⌘K on macOS) and choose Connect Drone.
3

Pick the port

Choose USB Serial, click Request Port and select the flight controller in the browser picker.
4

Let Mission Control detect iNav

iNav answers the MSP FC_VARIANT request with INAV. The node opens with the iNav panels in its Setup tab.
USB serial needs Web Serial: Chrome or Edge on desktop, or the desktop app. Safari and Firefox do not support it. See Connect a drone for Bluetooth and other links.

Flight modes

iNav modes include ACRO, ANGLE, HORIZON, NAV ALTHOLD, NAV POSHOLD, NAV RTH, NAV WP, NAV CRUISE, NAV COURSE HOLD, NAV LAUNCH and NAV LAND. Assign each to an AUX channel range in Aux Modes (Setup → FLIGHT) and switch it from the transmitter.

Mission planning

Plan iNav missions in the Plan tab. Mission Control translates the plan into iNav waypoint actions and uploads it over MSP (MSP_SET_WP). An iNav mission holds at most 60 waypoints. Upload refuses any other attached action. The iNav Mission panel (Setup → FLIGHT) shows the missions stored on the flight controller, which can hold several.

Safehomes

Safehomes are alternate return points for when the launch point is not reachable. The Safehome panel (Setup → SAFETY) edits all 8 slots. Each slot has an enabled flag, latitude and longitude. iNav uses the nearest enabled safehome within safehome_max_distance.

Geozones

Geozones are iNav’s fences. Edit them in the Geozones panel (Setup → SAFETY). Each zone has:
  • Type: exclusive (keep out) or inclusive (stay inside)
  • Shape: circle or polygon, up to 10 vertices per polygon
  • Altitude bounds: minimum and maximum
  • Fence action: None, Avoid, Position hold or RTH
Draw a polygon zone on the panel’s map, or enter the coordinates. Navigation Config (Setup → FLIGHT) edits these iNav settings: Nav PID (Setup → TUNING) edits the navigation PID gains. All iNav settings use iNav’s name-based settings protocol, and Mission Control converts each value to its declared type.

Profiles

iNav keeps several profile sets. Each has its own panel, and switching a profile takes effect on the flight controller at once.
  • Control Profiles (Setup → TUNING): three profiles of PIDs, rates and RC tuning.
  • Battery Profiles (Setup → SENSORS): capacity, cell count, voltage thresholds and current scale.
  • Mixer Profiles (Setup → FLIGHT): platform type, motor and servo counts, and mixer rules.

Programming

The PROGRAMMING section holds iNav’s programming framework.
  • Logic Conditions: up to 64 rules. Each has an operation, two operands (for example an RC channel, flight mode, global variable or constant) and an activator. The panel shows each condition’s live state.
  • Global Variables: live values of the 8 global variables, set by logic conditions or overridden in the panel.
  • Programming PIDs: up to 4 PID controllers that run outside the main flight loop.

Programming (JS)

Programming (JS) compiles a small JavaScript-like language into logic conditions.
  1. Write one statement per line: assign a global variable or write a bare boolean. Operands are numbers, gvar[N] and rc[N]. Operators are + - * / %, > < >= <= ==, && || and !.
  2. Preview the generated logic condition slots.
  3. Load them into Logic Conditions, review them there, then write to the flight controller.

EZ Tune

EZ Tune (Setup → TUNING) sets PIDs from a few sliders: response, damping, stability, aggressiveness, snappiness, axis ratio, rate and expo.

Fixed-wing approach

FW Approach (Setup → FLIGHT) edits the landing approach slots the flight controller reports: landing coordinates, approach and land altitudes, approach direction, two landing headings and a sea-level reference flag. It appears on airplane and tricopter platforms.

OSD

iNav OSD and Custom OSD configure the OSD elements and custom text. OSD Preview shows a live view of the character grid the flight controller sends over MSP DisplayPort, so you can check an HD goggle layout without goggles.

What Mission Control does not do on iNav

  • Firmware flashing. Mission Control does not flash iNav. Use iNav Configurator.
  • Telemetry over the RC link (SmartPort, CRSF, LTM). Mission Control talks MSP over USB, Bluetooth or a network bridge. Use the transmitter’s telemetry screen or the OSD in flight.
  • Phones. For a phone, use the Android GCS.

Next steps

Firmware comparison

iNav next to ArduPilot, PX4 and Betaflight.

Mission planning

Plan and upload a mission.
Last modified on October 11, 2026