ESCs

ESC Beep Codes: What the Beeps Mean and How to Calibrate an ESC

ESC beep codes are the tones an ESC plays through the motors. Three rising tones at plug-in mean it has power; a final ready beep means it has found a throttle signal at zero; a beep that keeps repeating usually means no signal, or throttle not at zero. Once you know the sequence, most “my drone just beeps” problems take a minute to diagnose. This guide covers BLHeli_S, BLHeli_32, AM32 and the older SimonK and Hobbywing-style ESCs.

Updated 26 September 2026 · by the Fioparts team, Gurugram

An ESC has no speaker. When it beeps it pulses current through the motor windings so the motor itself makes the tone — which is why a motor that is unplugged or has a broken wire stays silent while the other three sing. The sequences below are the common ones; exact melodies vary by firmware and manufacturer, so treat the pattern, not the pitch, as the message.

The normal power-up sequence

  1. Three rising tones (♪ 1-2-3) the moment the battery goes in. The ESC has power, has found the motor and passed its self-test. On a 4-in-1 you hear all four motors do this together.
  2. Cell-count beeps — on SimonK, Hobbywing and many budget single ESCs, a number of short beeps equal to the number of cells detected: three beeps for 3S, four for 4S. BLHeli_S, BLHeli_32 and AM32 generally skip this step.
  3. The ready tone — one long beep on SimonK and Hobbywing-style ESCs, a low-then-high pair on BLHeli_S and BLHeli_32. A valid throttle signal was found and it is at zero; the ESC is armed and waiting. Only now will the motors respond.

On a Betaflight quad you will normally hear the rising tones, then a short pause, then the ready beep once the flight controller boots and starts sending DShot. That whole sequence takes a second or two.

Beeps that mean something is wrong

What you hearWhat it meansWhat to check
Rising tones, then a single beep every 1–2 s, foreverNo throttle signal. The ESC never saw a valid signal from the flight controller.FC not powered or not booting; ESC signal wire / ribbon cable not seated; wrong ESC protocol in Betaflight (DShot vs PWM); a 4-in-1 wired to the wrong FC pads.
Rapid short beeps right after power-upThrottle not at minimum — the ESC sees a signal but it isn’t “zero”.Throttle stick down; radio trims; a PWM ESC that needs calibration (see below); Betaflight motor tab left with a slider up.
Beep-beep pairs repeating at power-up, no ready toneBattery voltage outside the ESC’s accepted range (Hobbywing-style and many DIY-class ESCs).A flat or wrong-cell-count pack; an ESC rated for fewer cells than the battery; a bad cell dragging the pack down.
Nothing at all from one motorThat ESC channel has no power or no motor.Motor plug or solder joint; a broken phase wire; on a 4-in-1, a dead channel (test by swapping motors).
Nothing from any motorThe ESC has no power.Battery connector, XT60 solder joint, blown fuse or a burnt board — smell the ESC before plugging in again.
Continuous tone that doesn’t stopA motor that can’t turn (stalled or blocked), a shorted phase, or a failing ESC channel.Unplug immediately. Spin each motor by hand for grit or a rubbing bell; check phase wires for shorts to the frame; if the hardware is fine, reflash with BLHeli Suite / AM32 configurator.
Motors twitch and beep on arming, don’t spinThe FC is sending a signal the ESC can’t read.Match the ESC protocol (DShot300 or DShot600 — DShot1200 is deprecated); check motor pads for solder bridges and cold joints; a motor that stutters on its own points to a bad phase joint or desync.

ESC beeps vs flight-controller beeps

Modern Betaflight builds make a lot of noise that is not ESC beep codes. The DShot beacon uses the motors as a lost-model beeper when you flip the beeper switch or the receiver hits failsafe; the FC’s own buzzer plays patterns for arming, battery warnings and GPS. If the beeping starts only after the FC boots or responds to a switch, it is the flight controller talking. Betaflight’s beeper conditions list, in the Configuration tab, decodes those.

ESC calibration: when you need it and how

DShot ESCs (every modern 4-in-1 and most singles) never need throttle calibration — the signal is digital, so the ESC knows exactly where zero and full are. Calibration is for PWM ESCs (SimonK, BLHeli in PWM mode, most 30 A DIY-class ESCs) where the ESC has to learn your radio’s pulse range.

Do it with props off, one ESC at a time or with all signal wires on a parallel harness:

  1. Radio on, throttle stick to maximum.
  2. Connect the battery. The ESC plays its power-up tones, then two beeps to confirm it recorded the top of the range.
  3. Move the throttle to minimum within a couple of seconds.
  4. The ESC beeps the cell count, then a long beep: bottom of the range stored, calibration done.
  5. Disconnect and reconnect the battery; check every motor starts at the same stick position.

On a Pixhawk or ArduPilot build the same routine runs through the ground station (Mission Planner → Initial Setup → Mandatory Hardware → ESC Calibration) so all four ESCs learn the FC’s output range together. Redo it whenever you change the radio, receiver or flight controller.

Choosing an ESC that behaves

The quiet, predictable ones are current BLHeli_32 and AM32 boards with a real amp rating margin — a 45–65 A 4-in-1 for a 5″ quad, 20–30 A singles for a 450-class DIY build. 4-in-1 ESCs · Single ESCs · FC + ESC stacks · Made in India ESCs. If a board keeps beeping after all of the above, message us with a short video of the beeps and a photo of the wiring — it is usually a one-line answer.

Sources & manuals