Why Your Betaflight Drone Received’t Arm? Let’s Troubleshoot and Repair it.

July 30, 2026

1

32K

One of the crucial widespread issues inexperienced persons encounter is when a Betaflight drone refuses to arm. You flip the arm swap… and nothing occurs. That is normally not a {hardware} failure. Betaflight consists of many security checks that deliberately forestall arming if one thing isn’t configured appropriately. On this information, I’ll present you learn how to shortly establish the issue and repair it.

A few of the hyperlinks on this web page are affiliate hyperlinks. I obtain a fee (at no additional value to you) should you make a purchase order after clicking on one in all these affiliate hyperlinks. This helps assist the free content material for the group on this web site. Please learn our Affiliate Hyperlink Coverage for extra data.

New to Betaflight? No worries—right here’s a tutorial to get you began on setting it up for the primary time: https://oscarliang.com/betaflight-firmware-setup/

Frequent Points

Alright, listed here are the most typical causes why your drone isn’t arming.

Unplugging USB Cable

Betaflight has a security function the place your drone gained’t arm if the flight controller is linked to the configurator (you’re going to get a MSP warning flag within the OSD and CLI if you try and arm). So, be sure USB cable is unplugged and provides it one other go.

Transferring Throttle Stick Down

The throttle stick must be lowered all the best way down so as to arm. Betaflight doesn’t arm if it’s above the minimal throttle (increased than the min_check worth). It is a security function in order that the quad doesn’t all of a sudden spin up the motors and damage you when it’s armed.

You have to make sure that your throttle is decrease than min_check when it’s within the lowest stick place. The default min_check worth is 1050, which ought to work high-quality for most individuals. Which means if you decrease your throttle stick all the best way down, the throttle worth ought to be decrease than 1050, any worth increased than that may forestall your drone from arming.

Drone on an Uneven Floor

By default, Most Arm Angle within the Configuration tab is about to 25°. It is a security function to stop the drone from arming if it’s tilted past that angle.

To repair this, you possibly can:

Place the drone on a flat floor, or
Enhance the Most Arm Angle to a better worth, corresponding to 45° or 60°, or
Disable the function totally by setting the angle to 180°.

Some pilots choose disabling this function as a result of it permits them to arm the quad when it’s caught in bushes, which can assist shake it unfastened. Nonetheless, it’s best to fastidiously contemplate the dangers earlier than disabling a security function.

One other doable trigger is a defective accelerometer. If disabling the arm angle doesn’t clear up the issue, attempt disabling the accelerometer within the Configuration tab.

Needless to say disabling the accelerometer will even disable Angle mode, Horizon mode, GPS Rescue, and Place Maintain, since these options depend on accelerometer knowledge.

Radio Receiver Test

Guarantee your radio receiver is certain and dealing appropriately in Betaflight. bind ExpressLRS radio/receivers: https://oscarliang.com/bind-expresslrs-receivers/

Then head over to the receiver tab to see if the channel responses match your stick actions appropriately. If the channels are flawed, it’s doable that you’re utilizing the flawed channel map, choose a distinct channel and see if resolves the problem. To study extra about channel map see this information: https://oscarliang.com/channel-map/

Arm Mode Project

Did you setup an ARM swap appropriately? When you don’t know learn how to do it, right here’s the tutorial: https://oscarliang.com/betaflight-modes/#How-to-Setup-Arm-Swap

Mainly. go to the Modes tab, and assign an auxiliary swap to “ARM”, sometimes AUX 1 for ExpressLRS.

AUX 1 = Channel 5
AUX 2 = Channel 6
AUX 3 = Channel 7
and so forth

ARM mode ought to flip pink when activated on the bench, signalling it’s responding to your radio swap, and it’s been set appropriately.

If that’s working, however the drone nonetheless gained’t arm, let’s troubleshoot a bit deeper.

Test the Arming Disable Flags in Betaflight

OSD

To show Arming Disabled Flags in OSD:

Go to the OSD tab in Betaflight Configurator
Allow “Warnings” ingredient
Underneath the Warning part, allow “Arming Disabled”

When one thing is stopping your drone from arming, it would let you know the rationale on display screen. As an example, my throttle isn’t all the best way down at 0, and it says “Throttle” on display screen:

Betaflight Configurator

When you don’t have OSD, you possibly can verify the “Arming Disable Flag” within the Setup Tab within the Betaflight configurator. However they’re normally numbers and you might want to look it up within the desk under.

CLI

Alternatively, you may as well verify “Arming disable flags” within the CLI by coming into the command:

standing

The final line exhibits you the arming prevention flags.

Additional Studying: use CLI in Betaflight?

Buzzer Beeping

When you don’t have OSD, and don’t have entry to Betaflight Configurator, you possibly can hearken to the beeps from the buzzer – the variety of beeps signifies the disarm flags. Right here’s learn how to decipher the beeping sample:

5 quick beeps for simply consideration, which might be ignored
Various lengthy beeps
Various quick beeps with lengthy intervals

Every lengthy beep represents 5, whereas every quick beep represents 1. The ultimate flag quantity might be calculated as 5 x <the variety of lengthy beeps> + <the variety of quick beeps>.

For instance:

0 lengthy beep and a couple of quick beeps = 2
1 lengthy beep and three quick beeps = 8
2 lengthy beeps + 0 quick beeps = 10

Sure, that is barely extra complicated. That’s why it’s simpler to simply have a look at your OSD, or verify within the configurator.

Arming Prevention Flags Lookup Desk

When you’ve discovered the arming disabled flag codes or errors, look it up on this desk for the precise concern and resolution. This desk is from the Betaflight wiki.

Error Names	Problem Description	Code	Resolution
`NOGYRO`	A gyro was not detected	1	You could have a {hardware} failure, if a earlier firmware model works then it could be a firmware concern. Otherwise you may need flashed a flawed goal.
`FAILSAFE`	Failsafe is energetic	2	Rectify the failure situation and check out once more.
`RXLOSS` ⁽¹⁾ or `RX_FAILSAFE`	No legitimate receiver sign is detected	3	Your receiver is both defective or has no hyperlink to the transmitter.
`BADRX` ⁽¹⁾ or `NOT_DISARMED`	Your receiver has simply recovered from failsafe however the arm swap is on	4	Deactivate the arm swap first.
`BOXFAILSAFE`	The ‘FAILSAFE’ swap was activated	5	See `FAILSAFE`
`RUNAWAY`	Runaway Takeoff Prevention has been triggered	6	Disarm to clear this situation.
`CRASH`	Crash Restoration has been triggered	7	Disarm to clear this situation.
`THROTTLE`	Throttle channel is just too excessive	8	Decrease throttle under `min_check`.
`ANGLE`	Craft will not be stage (sufficient)	9	Stage craft to inside `small_angle` levels (default 25).
`BOOTGRACE`	Arming too quickly after energy on	10	Wait till `pwr_on_arm_grace` seconds (default 5) have elapsed.
`NOPREARM`	Prearm swap will not be activated or prearm has not been toggled after disarm	11	Toggle the prearm swap.
`LOAD`	System load is just too excessive for secure flight	12	Revisit configuration and disable options.
`CALIB`	Sensor calibration remains to be ongoing	13	Look forward to sensor calibration to finish.
`CLI`	CLI is energetic	14	Exit the CLI.
`CMS`	CMS (config menu) is energetic – it might be OSD or different show menu	15	Exit the config menu (or OSD menu).
`BST`	A Black Sheep Telemetry machine (TBS Core Professional for instance) disarmed and is stopping arming	16	Discuss with the handbook to your {hardware}.
`MSP`	MSP connection is energetic, in all probability by way of Betaflight Configurator	17	Terminate the Betaflight Configurator connection (click on disconnect button or unplug USB cable).
`PARALYZE`	Paralyze mode has been activated	18	Energy cycle/reset FC board.
`GPS`	GPS rescue mode is configured however required variety of satellites has not been mounted	19	Look forward to GPS repair, allow arming with out GPS repair, or disable GPS rescue mode.
`RESCUE_SW`	GPS Rescue swap is turned on	20	Deactivate the GPS Rescue swap earlier than arming.
`RPMFILTER` ⁽²⁾ or `DSHOT_TELEM`	Motor RPM-based filtering will not be functioning	21	A number of ESC’s will not be supplying legitimate RPM telemetry.
`REBOOT_REQD`	Reboot required	22	Reboot the flight controller for settings modifications to take impact.
`DSHOT_BBANG`	DSHOT Bitbang will not be working	23	Bitbang DSHOT will not be working correctly and the motors can’t be managed. Doubtless attributable to a timer battle with different options enabled on the flight controller.
`NO_ACC_CAL`	Accelerometer calibration required	24	Calibrate the accelerometer or disable options that use it
`MOTOR_PROTO`	ESC/Motor Protocol not configured	25	Choose the ESC/Motor protocol to make use of on the Configuration tab.
`ARMSWITCH`	Arm swap is in an unsafe place	26	Toggle the arm swap to arm.

(1) – This will seem on the Betaflight OSD throughout flight, take it as an indication that your radio system is both defective or you might be flying on the fringe of your vary. Deal with it the identical you’d an “RSSI critically low” warning.

(2) – RPM-based filtering is enabled however a number of ESC’s will not be supplying legitimate DSHOT telemetry. Test that the ESC’s are able to and have the required firmware put in to assist bidirectional DSHOT telemetry.

Different Frequent Points

If Betaflight exhibits no arming disabled flags, and you continue to can’t arm the drone, the issue is perhaps unrelated to Betaflight. Listed here are a number of extra issues to verify.

Are ESC and Motors Truly Working?

Did you plug within the battery? Motors ought to beep a number of occasions to point ESC initialization. If nothing, it’d point out an influence concern, connection concern between ESC and FC, or defective FC, ESC or motors.
Be sure DShot300 or DShot600 are chosen as ESC protocol.
Attempt to spin the motors utilizing the sliders within the motors tab (take away propellers earlier than doing so)

Is CPU Utilization Too Excessive?

When CPU load is just too excessive, Betaflight could refuse to arm. Yow will discover out the CPU load on the backside of Betaflight Configurator.

CPU load ought to keep under 75% (per BF4.5 suggestion). To decrease CPU load, you possibly can regulate settings, corresponding to

reducing PID loop frequency from 8KHz to 4KHz
disabling pointless options within the Configuration tab, corresponding to LED_Strip, tender serial.

Throttle Finish Factors

Guarantee your radio gimbals are appropriately calibrated, and that they attain the right finish factors.

When your throttle’s lowest worth is increased than it ought to be, Betaflight will refuse to arm. Ideally the vary of the channels ought to be 1000 to 2000. Barely exterior of this vary is normally high-quality and doesn’t do any hurt, e.g. 988/990 – 2010-2012 is ok. Nonetheless, in case your finish factors are inside this vary, that’s not perfect. Not solely you aren’t utilizing the complete vary, it may also cease you from arming. To repair that, it’s best to calibrate your stick endpoints correctly by following this information: https://oscarliang.com/adjust-tx-channel-mid-end-point/

Moron threshold

Some FC could have extra delicate gyro’s and the drone would refuse to calibrate and initialize after energy up, and also you gained’t be capable of arm it.

By improve “gyro_calib_noise_limit” (beforehand generally known as Moron Threshold) in CLI reduces gyro sensitivity throughout initialization. You may attempt setting it to 100 and even 120.

Conclusion

When a Betaflight drone refuses to arm, it’s normally as a result of failure of security checks. When you learn to learn the arming disable flags, diagnosing the issue turns into a lot simpler. In fact, there are different widespread causes too corresponding to radio and receiver setup, stick endpoints and so on.

If you’re nonetheless having issues arming your quad after following this information, be at liberty to publish your query on our discussion board, our group is all the time right here to assist and study collectively. Completely satisfied flying!

Edit Historical past

Jun 2018 – Tutorial created.
Feb 2024 – Up to date.
July 2026 – Up to date information and added some screenshots.