Your FPV Drone Won't Arm. Read the Flag Before Buying Parts

Quick Answer

If your FPV drone will not arm, remove the props, disconnect USB, power the receiver from a battery and run status in Betaflight’s CLI. The active arming-disable flag tells you what is blocking the motors. Fix that flag rather than changing random settings: RXLOSS means no valid receiver signal, THROTTLE means the input is above min_check, and MSP means the configurator connection is still active.

Use the Flag, Not Guesswork

A red “arming disabled” message is a safety status, not the diagnosis. Betaflight can show the reason in the OSD warnings, the Setup page or the final line of the CLI status output. If several flags appear, clear the obvious connection flags first, then run status again.

Start with the aircraft level and still. Disconnect the USB cable, lower throttle, switch ARM off, connect the flight battery and wait five seconds. USB often produces MSP or CLI because an active configurator session intentionally blocks arming. Never troubleshoot arming with props fitted.

Betaflight Arming Disable Flags: What to Fix

Flag	What it means	Next check
RXLOSS / FAILSAFE	No valid receiver link, or failsafe is active	Confirm the receiver is bound and all channels move in the Receiver tab
THROTTLE	Throttle is above min_check	Lower the stick; verify its low endpoint sits below min_check
ANGLE	The craft exceeds small_angle, 25° by default	Place it level; do not disable this protection merely to hide a bad accelerometer setup
MSP / CLI	An MSP connection or CLI session is active	Close the configurator connection and unplug USB
BOOTGRACE / CALIB	Start-up grace period or sensor calibration is not complete	Keep the craft still and wait; BOOTGRACE defaults to five seconds
NOPREARM	The configured PREARM switch has not been toggled	Activate PREARM before ARM
NOT_DISARMED / ARM_SWITCH	The arm switch was on during recovery or is in an unsafe position	Switch ARM off, then on after every other flag clears
GPS / RESCUE_SW	GPS Rescue lacks its required fix, or its switch is active	Wait for a fix, review Rescue settings and switch Rescue off before arming
DSHOT_TELEM	Bidirectional DShot is not returning valid RPM telemetry	Check ESC firmware, motor protocol and bidirectional DShot support
NOGYRO / MOTOR_PROTO	No gyro is detected, or no motor protocol is configured	Verify the exact firmware target before considering hardware replacement

Receiver and ARM Switch Checks

In the Receiver tab, roll, pitch, yaw and throttle should move correctly, while the ARM switch should move its assigned AUX channel. In Modes, place the ARM range over that channel’s switched value. ExpressLRS commonly uses AUX 1, channel 5, for ARM, but the assignment is not automatic.

If RXLOSS remains, confirm the RadioMaster AX12 or your own transmitter is bound, the receiver protocol matches the flight-controller configuration and the receiver is powered from the correct pad. Our Betaflight flashing and configuration guide covers the setup path.

Do Not Replace the Flight Controller Too Soon

We would not buy a board for RXLOSS, THROTTLE, ANGLE, MSP or ARM_SWITCH: those flags point to configuration, connection or radio state. Replacement becomes reasonable when NOGYRO survives a power cycle and a verified reflash of the correct target, or when physical damage is visible.

If hardware is genuinely at fault, compare the integrated SpeedyBee F405 AIO V2 with the separate MicoAir405v2 F405 stack. A complete Axisflying Manta 5 SE V2 is a different decision, not a troubleshooting shortcut.

See our flight controller explainer, browse flight controllers and electronics, or view our Betaflight-compatible range.

iNav Is Not Always Waiting for GPS

It is too broad to say every GPS-equipped iNav aircraft needs a fix before arming. Current iNav behaviour depends on nav_extra_arming_safety and whether a navigation mode such as RTH or POSHOLD is configured. Read the iNav arming flags before altering the GPS requirement; do not disable a safety check simply to make the warning disappear.

FAQ

Why is ARM disabled in red in Betaflight?

It means at least one safety condition is active. Run status in the CLI or read Arming Disable Flags on the Setup page; the named flag is the useful part.

What do the arming beep codes mean?

After five short attention beeps, Betaflight encodes the most important flag as five times the number of long beeps, plus the later short beeps. One long and two short therefore means code 7. Flag numbers vary by firmware version, so match the code to that version’s documentation.

Why will my FPV drone not arm after the receiver reconnects?

NOT_DISARMED or ARM_SWITCH can remain when the link recovers while ARM is already on. Switch ARM off, clear the other flags, then switch it on again.