iFlight Europe logo
iFlight Europe logo
All articles

FPV drone won’t armUpdated 2 months ago

If your FPV drone does not arm, this usually does not mean the drone is defective. Betaflight includes safety checks that intentionally prevent arming when something is not configured correctly or when the drone is not in a safe state.

Always remove all propellers before troubleshooting.

Common symptoms

You may experience:

  • Nothing happens when using the arm switch
  • Motors do not spin after arming
  • “Arming Disabled” appears in Betaflight
  • OSD shows warnings such as RXLOSS, THROTTLE, MSP, ANGLE, GPS, or FAILSAFE
  • Radio is bound, but the drone still will not arm
  • Drone works in Betaflight but not when disconnected from USB

Step 1 — Check the arming disable flag

The fastest way to find the problem is to check the arming disable reason.

In Betaflight:

  1. Connect the flight controller by USB
  2. Open Betaflight Configurator
  3. Check the Setup tab for “Arming Disabled”
  4. Open the CLI and type:
1status

The result will show the active arming disable flags.

Do not guess randomly. The arming flag usually tells you exactly what is preventing arming.

Step 2 — Common arming flags and what they mean

RXLOSS

Betaflight is not receiving a valid receiver signal.

Check:

  • Receiver is bound
  • Radio is on
  • Correct model selected on the radio
  • Correct UART has Serial RX enabled
  • Correct receiver protocol selected
  • ELRS / Crossfire / DJI system is configured correctly

If you see RXLOSS, the receiver system should be checked before anything else.

THROTTLE

Throttle is too high for arming.

Check:

  • Throttle stick is fully down
  • No throttle trim is added
  • Receiver tab shows throttle around 1000 µs at minimum
  • Channel endpoints are calibrated correctly

Betaflight prevents arming if throttle is above the safe arming threshold.

MSP

The flight controller is connected to Betaflight Configurator or another MSP device.

This is normal while USB is connected. Disconnect from Betaflight before trying to arm normally.

ANGLE

The drone is tilted too much to arm.

Place the drone on a flat surface and try again. If needed, calibrate the accelerometer in the Setup tab.

FAILSAFE

Betaflight detects a receiver or failsafe condition.

Check receiver connection, radio link, failsafe settings, and signal quality.

GPS

If GPS Rescue is enabled, Betaflight may prevent arming until a GPS fix and the required minimum number of satellites are available. Betaflight documentation warns that allowing arming without a GPS fix is not recommended when GPS Rescue is used, because rescue may not work correctly if failsafe occurs before a valid fix is available.

RUNAWAY

Betaflight detected a runaway takeoff condition during a previous arm attempt.

This can happen with incorrect motor direction, wrong propeller installation, wrong motor order, incorrect board orientation, or serious configuration problems. Betaflight can automatically disarm in this situation to prevent uncontrolled takeoff.

Do not keep trying to take off. Check motor direction, motor order, propeller orientation, and flight controller orientation first.

Step 3 — Check battery and power

Make sure:

  • Battery is charged
  • Battery is connected properly
  • Battery voltage is within the correct range
  • Connector is not damaged
  • No wires are loose

Some systems may appear normal over USB, but receivers, GPS modules, DJI Air Units, or other peripherals may require main battery power.

Important: Always remove propellers before connecting a battery on the bench.

Step 4 — Check receiver input

Open the Receiver tab in Betaflight.

Move the sticks and check whether channels move correctly.

You should see movement for:

  • Roll
  • Pitch
  • Yaw
  • Throttle

If there is no movement, check your receiver setup first. Common causes include:

  • ELRS not bound
  • Wrong ELRS frequency or region
  • DJI video works but control is not linked
  • Wrong UART
  • Wrong receiver protocol
  • Receiver not powered
  • Incorrect wiring

Step 5 — Check throttle endpoints

In the Receiver tab, check the throttle value.

Typical values should be close to:

  • Minimum: around 1000
  • Center: around 1500
  • Maximum: around 2000

If throttle minimum is too high, Betaflight may block arming with THROTTLE.

Adjust endpoints, subtrim, or radio calibration if necessary.

Step 6 — Motor Stop may make it look like the drone is not armed

If Motor Stop is enabled, the drone may be armed even though motors do not spin at idle.

Betaflight notes that motors normally spin slowly when armed, unless Motor Stop is enabled; for safety reasons, disabling motor spin at arm is generally not recommended.

Check:

  • OSD arm status
  • Beeper behavior
  • Betaflight status
  • Motor Stop setting

Do not assume the drone is not armed just because the motors are not spinning.

Step 7 — Do not flash firmware as a first step

Do not update or reflash Betaflight unless you know exactly why it is required.

Flashing the wrong target or losing the factory configuration can cause:

  • No receiver input
  • Wrong motor order
  • Missing OSD
  • Missing gyro
  • Incorrect UART setup
  • DJI / ELRS configuration loss

Firmware flashing should only be done when necessary and with the correct target, presets, and backup.

Step 8 — Check GPS if GPS Rescue is enabled

If your drone uses GPS Rescue, wait until GPS has a valid fix and the required satellite count.

Check:

  • GPS icon in Betaflight
  • Satellite count
  • GPS Rescue settings
  • Outdoor sky visibility
  • Correct UART and baud rate

Do not rely on GPS Rescue as a guaranteed safety system. It must be configured and tested carefully.

Step 9 — Check for physical or crash damage

If the drone stopped arming after a crash or modification, inspect:

  • Receiver wiring
  • Antennas
  • Flight controller
  • ESC
  • Motor wires
  • Battery connector
  • Solder joints
  • USB port
  • Burn marks or smell

Damage caused by crashes, incorrect wiring, soldering, water, reverse polarity, or misuse is generally not covered under warranty.

Before contacting support

Please collect:

  • Order number
  • Drone model
  • Radio model
  • Receiver type
  • Betaflight screenshot of the Setup tab
  • CLI status output
  • Screenshot of the Receiver tab
  • Photos of the drone and wiring
  • Short video showing the arming attempt
  • Any OSD warning message

Contact our support team at:

[email protected]

Was this article helpful?
Yes
No
Powered by