
ESC firmware: BLHeli_32 vs AM32
ESC firmware is the boring layer until bidirectional DShot and the RPM filter need telemetry; then BLHeli_32 vs AM32 matters. Many pilots fly whatever shipped from the factory and never open a flash tool. That is fine until one ESC desyncs, one channel runs different timing, or you enable bidirectional DShot and the quad misbehaves. Firmware choice isn’t tribal. It comes down to hardware support, flash procedure, and whether you can recover if something bricks.
The short version for 2026: BLHeli_32’s developer stopped development and licensing in 2024 (Hackaday, ArduPilot docs). Existing BLHeli_32 ESCs keep working but get no new updates, and newer 32-bit ESCs increasingly ship with AM32. Note that many 1S whoop AIOs use 8-bit ESCs running BLHeli_S or Bluejay, which is a different family again; check your board’s listing.
When NOT to flash

| Situation | Better move |
|---|---|
| Quad flies perfectly, no bidir plans | Leave factory firmware alone |
| One desync, never flashed before | Check caps, protocol, props first |
| Rushing before a field meet | Flash the week before, not morning of |
| Unknown ESC clone, no target listed | Ask the seller or replace it; don’t guess |
| Channels on different versions | Match firmware across all four channels |
Flashing is maintenance, not entertainment. Have a smoke stopper or current-limited bench supply ready; see smoke stopper vs multimeter.
BLHeli_32
BLHeli_32 was the standard on 32-bit hobby ESCs for years, and a huge number of 4-in-1s still run it.
| Aspect | Notes |
|---|---|
| Tool | BLHeliSuite32 (Windows); official downloads and support ended with the project |
| Features | DShot, bidirectional DShot on supported ESCs, timing and demag settings |
| Community | Lots of existing tuning advice |
| Status | Closed source; development and licensing ended in 2024 |
Strengths: proven on name-brand ESCs, and most older tutorials assume it.
Weaknesses: no further updates; flashing the wrong target bricks a channel; some clones misreport compatibility.
If your BLHeli_32 ESC flies well, there is no urgency to change it. Just don’t expect new fixes.
Typical workflow:
1. Identify exact ESC model and revision
2. Connect via FC passthrough or direct USB (per ESC docs)
3. Read settings, screenshot motor direction and timing
4. Flash correct target only, verify twice
5. Set motor direction, protocol, timing defaults
6. Test bidir in Betaflight only after clean motor spinAM32
AM32 is open-source firmware for 32-bit ESCs, actively developed and now the main successor to BLHeli_32.
| Aspect | Notes |
|---|---|
| Tool | AM32 configurator (web or desktop); follow the current project docs |
| Features | DShot, bidirectional DShot, active community fixes |
| Hardware | Not every BLHeli_32 ESC can run AM32; check the supported list for your exact board |
| Recovery | Moving from BLHeli_32 usually needs the AM32 bootloader flashed first; procedures vary by target |
Strengths: open and actively maintained; ships preloaded on a growing number of new ESCs; the obvious path when you need updates.
Weaknesses: a wrong flash still bricks; not every board is supported; documentation varies by target.
Don’t flash AM32 just because a forum post said "AM32 is better" without confirming your exact ESC board is supported.
Timing and demag (shared vocabulary)
Both expose timing and demag (demagnetisation compensation) settings that affect punch-outs. Aggressive timing can feel snappy until a weak battery or hot motor triggers a desync.
| Setting | Too aggressive | Too soft |
|---|---|---|
| Setting | Notes | |
| ------- | ----- | |
| Timing | Too aggressive: desyncs on punch, one motor hot. Too soft: sluggish | |
| Demag | Higher compensation helps prevent desyncs, at a small cost in punch | |
| Motor direction | Fix before fitting props | |
| Protocol | Must match the DShot setting in Betaflight |
Screenshot the defaults before flashing. Restoring known settings beats guessing what changed.
Choosing between them
| Question | Lean |
|---|---|
| ESC shipped with BLHeli_32 and flies fine | Leave it |
| Manufacturer officially supports AM32 for your board | AM32 is reasonable |
| Need bidirectional DShot + RPM filter | Either works once telemetry is verified (see RPM filter) |
| Buying a new ESC | Prefer one that ships with AM32 or has documented AM32 support |
| Want ongoing updates | AM32 on confirmed hardware |
Firmware doesn’t fix an undersized ESC or an overloaded motor.
Shared pitfalls
| Pitfall | Result |
|---|---|
| Wrong target flashed | Dead ESC channel; recover via bootloader or replace |
| Mixed firmware on one quad | Desyncs, uneven timing, mystery heat |
| Aggressive timing on a weak ESC | Desyncs on punch; back off timing |
| Motor direction wrong after a flash | Reverse it in the ESC tool; check before props |
| Ignoring a damaged capacitor | Telemetry dropouts, noise, brownouts |
| Enabling bidirectional DShot before a spin test | Props off first, always |
Pair firmware work with RPM filter testing, one motor at a time on the bench, props off.
Telemetry and tuning link

Bidirectional DShot depends on ESC firmware and a clean power path. After flashing:
- Betaflight: correct DShot rate, bidirectional DShot on, correct motor poles
- Motors tab: RPM readings show and error rates stay near zero
- Hover: no desyncs
- Blackbox: stable RPM traces (reading Blackbox)
- Then rely on the RPM filter
Bad telemetry feeds the RPM filter wrong numbers, which is worse than no RPM filter.
Symptom → action map
| Symptom | Check firmware side |
|---|---|
| Desync on one motor only | Check that channel’s firmware matches the others |
| Worked until the flash | Restore timing and demag defaults |
| Problems as soon as bidirectional DShot is on | Firmware support, DShot rate |
| Motors run hot at cruise | Timing too aggressive; soften it |
| Intermittent telemetry | Solder joints, capacitor, power connector |
India practical notes
If you are learning to flash, keep a spare 4-in-1 on the shelf; a domestic replacement arrives faster than you will find the courage for a bootloader recovery. Same idea as the field repair kit: one known-good ESC beats debugging a clone at 40 °C in a car park.
Summer heat exposes marginal settings: a desync you never saw in winter may appear once motors heat-soak. Test in the conditions you actually fly in.
Voltage spikes from long battery leads are real, so fit a low-ESR capacitor at the ESC power pads on 4-in-1 builds.
Recovery mindset
If a channel bricks:
- Check the manufacturer’s bootloader recovery procedure before reaching for the iron
- Note exactly what you flashed; support forums need the target name
- Fly a spare quad or ESC at the field; debug at home
After crash repair, inspect the ESC for damaged components before reflashing; damaged hardware won’t behave, however perfect the firmware.
Flash day checklist
□ Exact ESC model and revision written down
□ Screenshot of current settings (all four motors)
□ Correct target checked twice in the flash tool
□ Props off for the first motor spin test
□ Smoke stopper or current limit on the bench
□ Betaflight backup saved before enabling bidirectional DShot
□ One hover pack before freestyle
□ Blackbox RPM traces checked if using the RPM filterFlash the week before a meet, not in the car park.
Common mistakes
- Flashing the "closest" target name
- Updating one channel of a 4-in-1 and leaving three on the old version
- Wrong motor pole count in Betaflight, so RPM readings are off
- Skipping the smoke stopper on the first power-up after a flash
- Blaming Betaflight PIDs for ESC desyncs
BLHeli_32 and AM32 are both tools; only one is still being developed. Use what your hardware supports, flash carefully, verify telemetry, then tune. The best ESC firmware session ends boring: four matching motors, clean logs, no smoke.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.