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

July 31, 2026

2

32K

One of the vital frequent issues learners 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 contains many security checks that deliberately forestall arming if one thing isn’t configured accurately. On this information, I’ll present you the right way to shortly determine the issue and repair it.

A number of the hyperlinks on this web page are affiliate hyperlinks. I obtain a fee (at no additional value to you) if you happen to make a purchase order after clicking on one among these affiliate hyperlinks. This helps help the free content material for the neighborhood 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/

Widespread Points

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

Unplugging USB Cable

Betaflight has a security characteristic the place your drone gained’t arm if the flight controller is linked to the configurator (you’ll get a MSP warning flag within the OSD and CLI while you try to arm). So, make sure that 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 in an effort to arm. Betaflight doesn’t arm if it’s above the minimal throttle (greater than the min_check worth). It is a security characteristic in order that the quad doesn’t immediately spin up the motors and damage you when it’s armed.

You will need to be certain 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 while you decrease your throttle stick all the best way down, the throttle worth must be decrease than 1050, any worth greater 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 characteristic to stop the drone from arming if it’s tilted past that angle.

To repair this, you may:

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

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

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

Take into account that disabling the accelerometer can even disable Angle mode, Horizon mode, GPS Rescue, and Place Maintain, since these options depend on accelerometer information.

Radio Receiver Test

Guarantee your radio receiver is sure and dealing accurately in Betaflight. The right way to 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 accurately. If the channels are unsuitable, it’s potential that you’re utilizing the unsuitable channel map, choose a distinct channel and see if resolves the problem. To be taught extra about channel map see this information: https://oscarliang.com/channel-map/

Arm Mode Project

Did you setup an ARM swap accurately? In case you don’t know the right way to do it, right here’s the tutorial: https://oscarliang.com/betaflight-modes/#How-to-Setup-Arm-Change

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

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

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

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” component
Below the Warning part, allow “Arming Disabled”

When one thing is stopping your drone from arming, it can inform you 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

In case you don’t have OSD, you may verify the “Arming Disable Flag” within the Setup Tab within the Betaflight configurator. However they’re normally numbers and it’s worthwhile to look it up within the desk beneath.

CLI

Alternatively, it’s also possible to verify “Arming disable flags” within the CLI by getting into the command:

standing

The final line exhibits you the arming prevention flags.

Additional Studying: The right way to use CLI in Betaflight?

Buzzer Beeping

In case you don’t have OSD, and don’t have entry to Betaflight Configurator, you may take heed to the beeps from the buzzer – the variety of beeps signifies the disarm flags. Right here’s the right way to decipher the beeping sample:

5 brief beeps for simply consideration, which will be ignored
A variety of lengthy beeps
A variety of brief beeps with lengthy intervals

Every lengthy beep represents 5, whereas every brief beep represents 1. The ultimate flag quantity will be calculated as 5 x + .

For instance:

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

Sure, that is barely extra complicated. That’s why it’s simpler to simply take 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 situation and resolution. This desk is from the Betaflight wiki.

Error Names	Subject Description	Code	Answer
`NOGYRO`	A gyro was not detected	1	You’ll have a {hardware} failure, if a earlier firmware model works then it could be a firmware situation. Otherwise you might need flashed a unsuitable goal.
`FAILSAFE`	Failsafe is lively	2	Rectify the failure situation and take a look at 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 simply too excessive	8	Decrease throttle beneath `min_check`.
`ANGLE`	Craft isn’t degree (sufficient)	9	Degree 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 isn’t activated or prearm has not been toggled after disarm	11	Toggle the prearm swap.
`LOAD`	System load is simply too excessive for secure flight	12	Revisit configuration and disable options.
`CALIB`	Sensor calibration remains to be ongoing	13	Watch for sensor calibration to finish.
`CLI`	CLI is lively	14	Exit the CLI.
`CMS`	CMS (config menu) is lively – it could possibly be OSD or different show menu	15	Exit the config menu (or OSD menu).
`BST`	A Black Sheep Telemetry system (TBS Core Professional for instance) disarmed and is stopping arming	16	Seek advice from the handbook in your {hardware}.
`MSP`	MSP connection is lively, 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 fastened	19	Watch for 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 isn’t 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 adjustments to take impact.
`DSHOT_BBANG`	DSHOT Bitbang isn’t working	23	Bitbang DSHOT isn’t working correctly and the motors can’t be managed. Probably 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 may occasionally seem on the Betaflight OSD throughout flight, take it as an indication that your radio system is both defective or you’re flying on the fringe of your vary. Deal with it the identical you’ll 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 help bidirectional DSHOT telemetry.

Different Widespread 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 below are a couple of extra issues to verify.

Are ESC and Motors Really Working?

Did you plug within the battery? Motors ought to beep a couple of occasions to point ESC initialization. If nothing, it’d point out an influence situation, connection situation between ESC and FC, or defective FC, ESC or motors.
Be certain 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 simply too excessive, Betaflight might refuse to arm. You’ll find out the CPU load on the backside of Betaflight Configurator.

CPU load ought to keep beneath 75% (per BF4.5 advice). To decrease CPU load, you may regulate settings, equivalent to

decreasing PID loop frequency from 8KHz to 4KHz
disabling pointless options within the Configuration tab, equivalent to LED_Strip, gentle serial.

Throttle Finish Factors

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

When your throttle’s lowest worth is greater than it must be, Betaflight will refuse to arm. Ideally the vary of the channels must 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 okay. Nonetheless, in case your finish factors are inside this vary, that’s not ultimate. Not solely you aren’t utilizing the total 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 might 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 enhance “gyro_calib_noise_limit” (beforehand referred to 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 attributable to failure of security checks. When you discover ways to learn the arming disable flags, diagnosing the issue turns into a lot simpler. In fact, there are different frequent causes too equivalent to radio and receiver setup, stick endpoints and so on.

In case you are nonetheless having issues arming your quad after following this information, be at liberty to publish your query on our discussion board, our neighborhood is all the time right here to help and be taught collectively. Joyful flying!

Edit Historical past

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