Why is my ESC beeping?
An ESC beeps by playing tones through the motor windings. Once you know that, the sound tells you which of half a dozen things is wrong — starting with whether it is the ESC beeping at all.
The symptom
You plug in the battery and the aircraft makes a noise it should not be making. Or it will not stop making it. Or one corner of it is making a noise the other three are not.
Before anything else, understand where the noise comes from, because it explains everything that follows: an ESC has no speaker. It makes sound by energising the motor windings. It drives the coils at an audible frequency and the motor becomes a crude loudspeaker. That is why ESC tones are musical — clean pitched notes, coming physically out of the motor bells.
This gives you the single most useful diagnostic in the whole article, and it costs you nothing.
Check this in 60 seconds
Put your ear next to the aircraft and answer one question: is the sound coming out of the motors, or out of a small black cylinder somewhere on the frame?
- A pitched tone from a motor is an ESC talking to you. It is a low-level, pre-flight-controller-level statement about power and signal.
- A harsh piezo squeal from a buzzer is the flight controller talking to you. Betaflight, iNAV and ArduPilot all drive a buzzer to report their own state — low battery, failsafe, arming refused, "here I am."
People confuse these two constantly, and then spend an evening resoldering an ESC that was perfectly healthy while their FC was patiently telling them the battery was flat. Sort this out first. Everything below assumes you have confirmed the sound is coming from the motors.
Then note two more things: which motors (all four, or one?) and when (at power-up only, or continuously?). Those three facts — source, count, timing — narrow it to one cause almost every time.
What the beeping means
An honest warning before the table: exact beep codes are specific to your ESC firmware and manufacturer. BLHeli_S, BLHeli_32, AM32 and the various vendor forks all differ in the details, and a manufacturer can change the tones between hardware revisions. There is no universal beep dictionary and anyone who gives you one is guessing. Look up your ESC's own documentation for the precise patterns.
What is universal is the category. The sound tells you which bucket you are in, and the bucket is what you act on.
| What you hear | When | What it means |
|---|---|---|
| A short ascending set of tones, then silence or a steady tone | Immediately at power-up | Normal. Most BLHeli-family ESCs play a startup sequence when they get power and see a valid signal. Not a fault |
| Startup tones, then a tone that will not stop | After power-up | Check your ESC's documentation before assuming this is normal. On some firmware a persistent tone means "ready and idling"; on others it is a fault indication. This is exactly the case where the universal beep tables on the internet will mislead you |
| Slow, continuous beeping that never stops | From power-up onwards | Power but no valid signal. The most common fault by a wide margin — see below |
| Slow, continuous beeping from one motor only | From power-up onwards | Wiring or a dead output on that channel. The other three prove the battery and the FC are fine |
| Rapid, urgent beeping | During or after a flight | A protection has tripped — usually low-voltage cutoff (if the ESC's battery alarm is enabled), or over-temperature / over-current |
| Repeating beeps long after a crash | While disarmed, on the ground | Almost certainly the beacon you configured. Betaflight can drive the ESCs as a find-my-quad buzzer (the DShot beacon). It is doing what you asked |
| A piezo squeal from a black cylinder | Any time | Not an ESC at all. That is the FC's buzzer. Go and read the FC's status instead |
The big one: continuous slow beeping
This is the fault you are most likely to have, and it has exactly one meaning: "I have power, but I am not receiving a valid signal from the flight controller." The ESC is powered up, initialised, and waiting for something it has not been given.
Work through these in order:
- Has the FC actually booted? If the FC is dead, unpowered, or stuck, all four ESCs will complain. Check that the board has a light on it.
- Is a motor protocol configured? An ESC that expects DShot and receives nothing, or expects a signal the FC is not producing, will sit there beeping. In Betaflight this also shows up as the
MOTOR_PROTOarming disable flag — read the flags, not the noise. - Is the signal wire physically connected? On the ESC side and the FC side. A cold joint on a motor signal pad is the classic: it looks fine, it passes a tug, and it conducts nothing. Reflow it rather than staring at it.
- Is the FC output mapped to that ESC? A 4-in-1 with a resource remapped, a motor output assigned to something else, or a target that never enabled that timer will leave one ESC signal-less.
- Does the ESC need a protocol it is not getting? Some ESCs will not accept a signal type they have not been told about. Check the ESC firmware, not just the FC.
One motor beeping, three motors quiet
The three silent ESCs have already done your diagnosis for you. They prove the battery is fine, the FC booted, and the motor protocol is being produced. Whatever is wrong is on the path between the FC and that one ESC — a signal pad, a wire, a solder joint, a resource assignment, or a blown output on that channel.
Go straight to that path. Do not re-flash the FC.
How to know you actually fixed it
Not "the beeping stopped once." Power-cycle the aircraft from cold, props off, and look for the positive signal rather than the absence of a negative one:
- All four ESCs play the same startup sequence, at the same time.
- The aircraft then goes quiet, or settles to a steady armed tone.
- Every motor spins from the Configurator's motor test, in the order you expect.
- It survives a second cold power-up. Intermittent signal faults — a joint that only conducts when the board is warm — are the ones that hand you a dead motor in the air.
The honest closing
Most ESC beeping is not an ESC fault. It is the ESC correctly reporting that something upstream of it — a wire, a solder joint, a protocol setting, an output mapping — is not doing its job. The ESC is the messenger, and it is a fairly reliable one.
So resist the urge to replace it. Confirm the sound is coming from the motors, count how many are complaining, and follow that back up the signal path. Nine times out of ten, the fix costs you a soldering iron and four minutes.