FPV Drone ESC Selection Guide 2026: AM32 vs BLHeli_32 Protocol Deep Dive
The Electronic Speed Controller (ESC) is the bridge between your flight controller’s commands and the physical rotation of your motors. Choosing the right ESC and firmware protocol directly affects throttle response, efficiency, braking performance, and reliability. As of 2026, the FPV market has largely consolidated around two open-source firmware ecosystems: AM32 and BLHeli_32. This guide provides a technical deep dive into both protocols to help you make informed hardware decisions.
How BLDC Motor Control Works in FPV
Before comparing protocols, it is essential to understand what an ESC does at the electrical level. A brushless DC motor in an FPV drone uses three-phase trapezoidal or sinusoidal commutation. The ESC contains six MOSFETs arranged in three half-bridges, one per motor phase. By switching these MOSFETs in a precise sequence, the ESC creates a rotating magnetic field that the permanent-magnet rotor follows. The switching timing must be synchronized with the rotor position, which is detected either by back-EMF sensing (sensorless, used in all FPV ESCs) or Hall effect sensors (rare in our application).
The microcontroller on the ESC runs firmware that implements this commutation logic. The flight controller sends a throttle signal — typically over DShot600 or DShot1200 — and the ESC translates that signal into MOSFET switching events at frequencies measured in tens of kilohertz.
BLHeli_32: The Incumbent
BLHeli_32 has been the dominant ESC firmware since 2017. Originally developed as closed-source commercial firmware for 32-bit ARM MCUs, its development effectively ceased after the BLHeli_32 developer disappeared from the community in 2023. However, a vast installed base of BLHeli_32 ESCs remains in service, and the firmware continues to perform reliably for most applications.
Key characteristics of BLHeli_32:
- MCU requirement: STM32F0 or AT32F4 series, minimum 24MHz clock
- PWM frequency: Selectable 24kHz, 48kHz, or 96kHz output to motors
- DShot protocol support: DShot150 through DShot1200, plus bidirectional DShot for RPM filtering
- Telemetry: ESC temperature, voltage, current, and RPM data per-motor
- Current limiting: Hardware-based current sensing with configurable thresholds
- Music/beacon: Motor beacon for lost model location, plus startup tones
- Adaptive timing: Automatic advance adjustment based on measured motor characteristics
The firmware freeze means no new features, no bug fixes, and no support for newer MCUs. ESCs shipped with BLHeli_32 are effectively frozen at their factory firmware version. For most pilots, this is not an immediate problem — BLHeli_32 revision 32.9 is mature and stable — but it represents a dead end for future development.
AM32: The Open-Source Successor
AM32 (short for “AlkaMotors 32-bit”) emerged as the community’s answer to the BLHeli_32 void. It is fully open-source under the GPLv3 license, actively maintained by a team of contributors, and supports a growing range of MCUs including STM32F0, STM32F3, STM32G0, AT32F4, and GD32 series. AM32 has rapidly matured and in 2026 is the recommended firmware for new ESC purchases.
Technical advantages of AM32 over BLHeli_32:
- Variable PWM frequency: AM32 supports dynamic PWM frequency adjustment from 24kHz to 128kHz, allowing pilots to tune for efficiency (lower frequency) or smoothness (higher frequency) on a per-build basis
- Dead time compensation: Advanced dead time insertion algorithms that minimize cross-conduction losses while maintaining fast switching transitions. AM32 detects and compensates for gate driver propagation delays
- Sinusoidal commutation: Beyond trapezoidal drive, AM32 supports sine-wave modulation with field-oriented control (FOC) on supported hardware. This produces smoother motor operation and can improve efficiency by 3-8% at partial throttle
- RPM filtering integration: Bidirectional DShot at up to DShot1200 with configurable telemetry rates optimized for the RPM filter in Betaflight 4.5+
- Extended telemetry: Per-motor current sensing, power calculation (watts), and energy consumption tracking (milliamp-hours) that exceeds BLHeli_32’s data set
Dead Time and PWM Frequency: The Technical Tradeoffs
Dead time is the deliberate delay inserted between turning off one MOSFET in a half-bridge and turning on its complementary partner. Without dead time, both MOSFETs could conduct simultaneously, creating a direct short across the battery known as “shoot-through” that destroys the ESC instantly. However, dead time also represents wasted energy — during the dead band, current flows through the MOSFET body diodes, which have a forward voltage drop 5-10 times higher than the MOSFET’s Rds(on) channel resistance.
The optimal dead time depends on the specific MOSFET gate capacitance, the gate driver’s current capability, and the operating temperature. Typical values range from 50 to 200 nanoseconds. AM32’s hardware-aware dead time compensation measures the actual switching behavior and adjusts dynamically, while BLHeli_32 uses a fixed dead time setting configured in the firmware that may not match the actual hardware characteristics.
PWM frequency selection involves a parallel tradeoff. Higher PWM frequencies (48-96kHz) produce smoother motor operation with reduced audible noise but increase switching losses in the MOSFETs. Each switching event dissipates a small amount of energy as heat in the gate driver and MOSFET. At 96kHz PWM, a 6S quad cruising at 30% throttle produces MOSFET switching events at roughly twice the rate of 48kHz. The efficiency penalty is typically 1-3%, which reduces flight time by 15-30 seconds. For racing where efficiency matters, 24kHz PWM is optimal; for cinematic flying where motor smoothness and low noise are prioritized, 48-96kHz is preferred.
Current Ratings: Decoding ESC Specifications
ESC current ratings are among the most confusing specifications in FPV. A “55A ESC” does not mean the ESC can handle 55 amps continuously. The rating conventions differ between manufacturers and are not standardized. Here is how to interpret the numbers:
| Rating Type | Meaning | Example (55A ESC) |
|---|---|---|
| Burst Current | Maximum current for 10-30 seconds with adequate cooling | 55A |
| Continuous Current | Maximum sustained current without overheating (typically 60-70% of burst rating) | 35-40A |
| Peak Current | Absolute maximum for less than 1 second — hitting this repeatedly will degrade MOSFETs | 60-65A |
For a 5-inch freestyle quad spinning 2207 or 2306 motors on 6S with aggressive props, each motor can draw 40-50 amps in full-throttle punchouts. A 4-in-1 ESC rated at 55A burst is adequate. For 7-inch long-range builds with 2807 motors and 7-inch props, step up to 65A-rated ESCs to handle the sustained current demands of heavy cruising.
4-in-1 vs. Individual ESCs
The 4-in-1 ESC has largely won the market for 3-inch and larger builds. A single PCB integrates all four ESCs with a shared power distribution network, reducing wiring complexity and weight. The total weight of a typical 55A 4-in-1 30×30 ESC is 12-18 grams, compared to 25-35 grams for four individual ESCs plus a PDB. For most builds, the weight and simplicity advantages are decisive.
Individual ESCs retain advantages in specific scenarios:
- Repairability: A single damaged ESC can be replaced without discarding the entire unit
- Thermal isolation: Each ESC has its own heat sink and airflow path, reducing thermal coupling between channels
- X-class and large builds: For 9-inch and larger props drawing 80A+ per motor, individual ESCs allow more flexible layout and superior heat dissipation
- Arm-mounted ESCs: Placing the ESC directly on the arm under the motor shortens phase wires and reduces electrical noise
Firmware Flashing and Configuration
Configuring AM32 ESCs uses the AM32 Configurator (web-based or standalone), which provides a similar interface to BLHeliSuite32. Both allow adjusting motor direction, startup power, timing advance, demag compensation, and PWM frequency. Critical settings to verify:
- Motor direction: Set all motors to the same direction in the ESC configurator. Use Betaflight’s “Motor direction is reversed” slider to handle prop rotation direction at the FC level
- Startup power: Increase from default 0.50 to 0.75-1.00 for larger motors (2207+) that need more starting torque
- Timing: Auto timing works well for most builds. Manually set 15-20 degrees for high-KV racing motors, 23-25 degrees for lower-KV long-range setups
- Demag compensation: Set to high for high-KV motors on 6S to prevent sync loss during rapid throttle changes
Conclusion
For new builds in 2026, AM32 is the clear recommendation. Its open-source development model ensures ongoing improvements, broader MCU support, and features that BLHeli_32 will never receive. Existing BLHeli_32 ESCs continue to perform well and do not need to be replaced — the firmware is stable and thoroughly tested. When purchasing new hardware, verify that the ESC explicitly supports AM32 and has an accessible bootloader for firmware updates. The extra minutes spent configuring AM32’s advanced settings pay off in a quad that runs smoother, responds faster, and communicates more diagnostic data back to your flight controller and OSD.