Your quad won’t arm because the mode switch range is off by 25 points on the slider. Or it arms in Angle mode when you wanted Acro. The Modes tab is where these problems live and die. Here’s exactly how to configure every useful mode, what each actually does to your flight controller, and how to avoid the mistakes that put quads into trees.
Understanding What Each Mode Does
Before touching the sliders, you need to know what you’re asking the flight controller to do. Too many pilots flip switches without understanding the flight logic underneath.
ARM — The master enable. When ARM is active, the ESCs receive power and the motors respond to throttle input. When disarmed, motors either stop or spin at idle (if MOTOR_STOP is disabled). Never configure ARM on the same switch position as any flight mode — you want a dedicated two-position switch. The ARM flag is the single most safety-critical setting on your quad.
ANGLE — Self-leveling mode. The flight controller limits the maximum tilt angle (default 45 degrees, adjustable via angle_limit CLI variable) and auto-levels when you center the right stick. Stick deflection controls the angle of the quad, not the rotation rate. This is training-wheels mode — useful for line-of-sight hover testing and indoor whoop flying, but it fights you when you try to fly aggressively.
HORIZON — Hybrid mode. Behaves like ANGLE near center stick (self-leveling) but transitions to ACRO at full stick deflection (allowing flips and rolls). Sounds great in theory. In practice, the transition zone around 60-70% stick creates unpredictable handling — the quad snaps from self-leveling to full-rate rotation with no warning. Most experienced pilots skip HORIZON entirely and go straight from ANGLE to ACRO.
ACRO TRAINER — Angle-limited rate mode. The quad responds to stick input with rotation rate (like ACRO) but caps the maximum angle. Default cap is 20 degrees. This is the bridge mode between ANGLE and true ACRO — you learn rate control without the risk of flipping upside-down. Bump the acro_trainer_angle_limit to 45 or 60 degrees as you gain confidence, then disable it entirely.
BEEPER — Activates the buzzer for lost-model location. You want this on a momentary switch (spring-loaded 2-position) or as a secondary function. The DShot beacon alternative (motor beeping) is useful if you don’t have a physical buzzer installed, but it’s much quieter and only works while the battery is connected.
Mapping Modes to AUX Channels
Connect your radio, open Betaflight Configurator, and navigate to the Modes tab. The horizontal bars represent AUX channel values from your radio — you’ll see colored indicators moving as you flip switches.
Step 1 — Identify Your Switches
Go to the Receiver tab first. Flip every switch on your radio and note which AUX channel each switch controls. A typical 3-position switch maps to AUX1 (channel 5), a 2-position to AUX2 (channel 6). Write these down — you’ll reference them constantly.
Step 2 — Add an ARM Range
Click “Add Range” under ARM. Select your dedicated 2-position switch’s AUX channel. Drag the yellow slider bar to cover the switch’s high position (typically 1800-2100 on the channel value scale). The slider range should be generous — 1750-2100 is safer than 1950-2050, which can drop in and out if your radio’s potentiometer drifts.
Step 3 — Configure Flight Modes on a 3-Position Switch
Map ANGLE to position 1 (low: 988-1300), ACRO TRAINER to position 2 (mid: 1300-1700), and leave position 3 (high: 1700-2100) unassigned for true ACRO. This progression makes sense: start in ANGLE, move to ACRO TRAINER, then to full ACRO.
Step 4 — Set BEEPER
Map to the momentary switch. Cover the full range of that switch’s active position. Test it: flip the switch, and your buzzer should sound. If it doesn’t, check that beeper -RX_SET isn’t disabled in the CLI (run beeper list to see the current configuration).
Verification: Test Before You Fly
Remove your props. Always.
- Connect battery and USB. Open the Modes tab.
- Flip each switch. Confirm the mode name turns yellow highlighted when active. If it flickers or doesn’t highlight, adjust the slider range.
- Arm the quad (props off). The motors should spin. Disarm — they should stop immediately.
- Switch through ANGLE → ACRO TRAINER → ACRO. Tilt the quad by hand — in ANGLE, the motors on the low side should spin faster (self-leveling correction). In ACRO/Acro Trainer, the motors should only respond to stick input.
- For ARM specifically: try arming with the throttle above zero. Betaflight should refuse (THROTTLE arming prevention flag). Good. Now lower throttle to zero and arm. It should arm cleanly.
If ARM won’t engage, go to the CLI and type status. The Arming disable flags line tells you exactly why. Common culprits: CLI MSP, RX_FAILSAFE (radio not connected), THROTTLE (throttle too high), or ANGLE (accelerometer not calibrated if angle mode is the default).
Parameter Comparison: Mode Characteristics
| Mode | Stick Controls | Self-Leveling | Max Angle Limit | Best Use |
|---|---|---|---|---|
| ACRO (no mode) | Rotation rate | No | None | Freestyle, racing, experienced flight |
| ANGLE | Angle | Yes | 45° (default) | Indoor whoops, LOS hover testing |
| HORIZON | Angle near center, rate at edge | Partial | 45° then unlimited | Rarely recommended — unpredictable |
| ACRO TRAINER | Rotation rate | No | 20° (default) | Transitioning from ANGLE to ACRO |
| ARM | N/A | N/A | N/A | Master power enable — dedicated switch |
Common Mistakes & How to Avoid Them
Mistake 1: ARM on the same switch as a flight mode.
The consequence: you arm in a mode you didn’t intend, or the overlapping ranges cause intermittent disarms mid-flight. The fix: use a dedicated 2-position switch for ARM. Never share an AUX channel between ARM and ANGLE/HORIZON/BEEPER.
Mistake 2: Slider ranges too narrow.
A 1950-2050 range on a switch that outputs 1930-2070 will flicker. The consequence: your quad randomly disarms at the edge of the range. The fix: always add 50-100 points of margin on both ends. 1800-2100 is standard and safe.
Mistake 3: Skipping the ANGLE mode accelerometer calibration.
If you plan to use ANGLE or HORIZON, the accelerometer must be calibrated on a level surface. The consequence: self-leveling drifts, and the quad “thinks” tilted is level. The fix: place the quad on a known-flat surface, go to the Setup tab, click “Calibrate Accelerometer,” and don’t touch it until the process completes.
Mistake 4: Not testing the beeper before hiding the quad in tall grass.
A buzzer that doesn’t work is worse than no buzzer — you’ll waste 20 minutes searching and assume it just failed. The fix: toggle the beeper switch before every session. If using DShot beacon instead of a physical buzzer, set beacon_strength to at least 100 in the CLI and test with beacon RX_SET.
Mistake 5: Leaving ACRO TRAINER enabled indefinitely.
The angle cap creates a false sense of control. The consequence: when you finally disable it and go full ACRO, you’ll overshoot every roll and flip because you’ve been training with a 20-degree ceiling. The fix: increase the limit by 10-15 degrees every 5-10 packs until you’re at 180 (effectively unlimited), then disable the mode entirely.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
As we covered in our Betaflight OSD configuration guide, displaying the current flight mode in your OSD gives you a real-time sanity check on what mode you’re actually flying — especially helpful during those first ACRO sessions when muscle memory hasn’t locked in yet. Combine this with our Betaflight rates setup to match your rates to your mode progression.
The JHEMCU GHF722 flight controller includes a dedicated buzzer pad and supports all Betaflight mode configurations out of the box, with a built-in barometer that adds altitude data to your OSD — useful when you’re testing ANGLE mode hover stability and want hard numbers instead of eyeballing it.