Your motors stutter on arming, one ESC comes down scorching hot, and you can’t figure out why. The defaults in BLHeli_32 Suite are generic starting points — not optimal settings for a 5-inch quad pulling 45A per motor. Here’s how to configure BLHeli_32 ESCs for clean starts, cool operation, and zero desyncs.
BLHeli_32 Configuration: Parameter-by-Parameter Setup
Step 1: Flashing and Connecting
Before changing any settings, check your ESC firmware version. Connect via BLHeliSuite32 (Windows) or the BLHeli_32 Configurator web app. Read the current setup first — write down every value before touching anything. This is your “known good” baseline.
To flash: select the correct ESC target (check the label on your ESC or the manufacturer’s product page). Flashing the wrong target can brick the ESC. Most modern BLHeli_32 ESCs ship with version 32.7 or 32.8. If you’re running version 32.5 or older, update — version 32.7 introduced significant improvements to bidirectional DShot timing accuracy.
Step 2: PWM Frequency and Motor Timing
- PWM Frequency: 48 kHz for most 5-inch builds. Lower frequencies (24 kHz) reduce FET switching losses and run cooler but produce audible motor whine. Higher frequencies (96 kHz) run quieter but increase ESC temperature by 8-12°C under load. 48 kHz is the sweet spot.
- Motor Timing: “Auto” works for 90% of builds. If you’re running high-KV motors (2400KV+) on 6S, try “23°” — this advances commutation timing to prevent desyncs at high RPM. Fixed timing values trade top-end RPM for smoother low-end startup. Too advanced: motors run rough and ESCs run hot. Too retarded: motors lose top-end speed and may desync on rapid throttle changes.
Step 3: Demag Compensation
Demag compensation prevents the ESC from losing sync with the motor when it decelerates rapidly — think full-throttle punch-out followed by zero throttle. The motor’s back-EMF confuses the ESC’s zero-crossing detection, causing the classic “desync screech” and a tumble to the ground.
Settings:
– Off: only use on very low-power builds (whoops, 2-inch). Risky on 5-inch.
– Low: sufficient for most freestyle and racing builds with quality motors.
– High: necessary for high-KV 6S setups, heavy builds (700g+), or when using aggressive motor timing. The tradeoff is slightly reduced efficiency — the ESC applies more braking force to maintain sync.
What happens without demag: you punch out, cut throttle, and the quad death-rolls. One motor stopped spinning while the other three kept going. The fix: bump demag from Low to High, test with aggressive throttle cuts.
Step 4: Startup Power and Rampup Power
Motor startup power controls the initial kick the ESC gives to overcome motor cogging and get the bell spinning. Issues this fixes:
- Too low (0.125-0.25): motors cog or stutter on arming. The ESC can’t overcome the magnetic detent torque. This is common on larger motors (2207, 2306, 2506) and tight-gap designs.
- Too high (0.75-1.00): motors “chirp” loudly on arm and may overshoot idle speed momentarily. Annoying, but not dangerous.
Recommended: 0.50 for 5-inch 2207/2306 motors on 4S or 6S. If motors stutter on arming, bump to 0.75. If they chirp loudly, back down to 0.375.
Rampup power controls how aggressively the ESC accelerates the motor from startup to commanded speed. Low values cause sluggish throttle response; high values cause overshoot and possible desync. The default (50%) is fine for most builds.
Step 5: Brake on Stop and Damped Light
Brake on Stop: this is the “active braking” feature that makes modern FPV quads feel responsive. Without it, motors freewheel when you cut throttle — they feel floaty and imprecise. Enable it. Always.
The only reason to disable Brake on Stop is for fixed-wing builds where you want the prop to windmill for glide efficiency. On any multirotor, it should be ON.
Damped Light mode (formerly “COMP_PWM”) is the underlying mechanism for active braking. It recirculates current through the FETs during the off-cycle, creating a braking force proportional to motor speed. This is automatically enabled when you set PWM Frequency to 48 kHz and Brake on Stop to ON.
Step 6: Motor Direction and Reverse Rotation
Use the BLHeli_32 Configurator to set motor direction — don’t swap motor wires unless you absolutely have to. Digital direction reversal is cleaner and lets you use the “Motor Direction is Reversed” checkbox in Betaflight’s Motors tab to keep the configuration consistent.
For a typical “props out” configuration (recommended for freestyle to avoid debris on the camera lens): motors 1 and 3 are reversed, motors 2 and 4 are normal. Set this in BLHeli_32, then check “Motor Direction is Reversed” in Betaflight for the reversed motors.
BLHeli_32 Parameter Reference Table
| Setting | Recommended Value (5-inch) | Effect if Too High | Effect if Too Low |
|---|---|---|---|
| PWM Frequency | 48 kHz | Quieter operation, higher ESC temp (+8-12°C) | Audible whine, lower ESC temp, slightly less smooth |
| Motor Timing | Auto / 23° (high-KV 6S) | Rough running, hot ESCs, possible desync | Reduced top-end RPM, desync on rapid throttle |
| Demag Compensation | Low (freestyle) / High (high-KV 6S) | Reduced efficiency, minor power loss | Death roll on throttle cut, desync at high RPM |
| Startup Power | 0.50 | Chirping/overshoot on arm, hot motors at idle | Stuttering on arm, motors won’t spin |
| Rampup Power | 50% | Overshoot, possible desync on punch | Sluggish throttle response, feels loose |
| Brake on Stop | ON | (no downside for multirotors) | Floaty throttle feel, prop freewheeling |
| Current Limit | Disabled | Protection for ESCs, limits max power output | (recommended disabled for performance builds) |
| Temperature Protection | 120°C | Prevents ESC burnout | (none — should always be enabled) |
Common BLHeli_32 Configuration Mistakes
Mistake 1: Flashing wrong ESC target. Each ESC variant (BLHeli_32 G-H-30, G-H-40, etc.) uses a specific firmware binary. Flashing the wrong one can brick the ESC, requiring a C2 interface programmer to recover. Always verify the ESC model in BLHeliSuite32 before flashing. The target is printed on the “Flash BLHeli” tab.
Mistake 2: Ignoring motor temperature after changing timing. When you advance motor timing, the ESC fires the commutation step earlier in the electrical cycle. This increases top-end RPM at the cost of efficiency — more energy becomes heat in the motor windings. After adjusting timing from Auto to 23°, check motor temperature after a 30-second hover. If motors hit 70°C+, back off to Auto.
Mistake 3: Setting current limit too low. Some builders enable current limiting at 35A for “safety.” On a 5-inch pulling 40A+ on punch-outs, this causes the ESC to pulse-limit current — you feel it as a “sag” or “hesitation” at full throttle. Disable current limiting and use motor output limits in Betaflight instead, which is smoother.
Mistake 4: Forgetting to reverse motor direction in both BLHeli_32 AND Betaflight. If you reverse a motor in BLHeli_32 but don’t set the corresponding flag in Betaflight’s Motors tab, the flight controller’s RPM filter uses the wrong direction data. This corrupts the notch filter placement and introduces mid-throttle oscillations that are nearly impossible to diagnose.
Mistake 5: Running PWM frequency at 24 kHz on modern ESCs. 24 kHz was the standard on BLHeli_S hardware, but BLHeli_32 ESCs use faster gate drivers designed for 48 kHz operation. Running at 24 kHz on BLHeli_32 actually produces a louder motor because the FETs switch at a frequency inside the human hearing range. 48 kHz pushes switching noise above 20 kHz — out of audible range.
⚠️ 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.
BLHeli_32 settings directly affect motor performance. For motor KV selection and prop matching, see our FPV Motor Kv Selection guide. For ESC protocol configuration, our DShot ESC Protocol Deep Dive covers bidirectional DShot and RPM filtering setup. If motors are desyncing despite correct BLHeli_32 settings, check the Motor Desync Causes and Fixes guide.
Modern BLHeli_32 ESCs like the T-Motor F55A Pro II handle 55A continuous with 48 kHz PWM, bidirectional DShot, and full telemetry — ideal for 6S builds pushing 2306 or 2506 motors. The current-sensing telemetry feeds directly into Betaflight’s Power tab for accurate mAh-used tracking. Available at uavmodel.com in the ESC section.