What the FC-to-ESC Signal Chain Actually Does
When a flight controller decides how fast a motor should spin, it does not send power to the motor directly. It sends a small digital or analog signal to an electronic speed controller, and the ESC translates that signal into the three-phase power that drives a brushless motor. The wire between the two is thin, and the signal on it is easy to overlook. But the protocol on that wire is what determines how quickly the drone reacts to stick input, how smoothly it holds a hover, and whether the ESC can report its own temperature and current back to the pilot.
For buyers comparing ESC regulators and flight controllers, the practical question is not "which brand is best" but "which protocol do the two devices on my stack speak, and what do I lose or gain by choosing one over another." This page explains the three protocol families a builder will encounter — PWM, Oneshot and DShot — in plain terms, and what each one means for a build.
Analog PWM: The Legacy Protocol
Pulse-width modulation is the oldest of the three. In PWM, the flight controller sends a train of pulses, and the width of each pulse encodes the throttle value. A narrow pulse means idle, a wider pulse means more throttle, and the ESC reads the pulse width to set motor speed.
PWM has two properties that shaped its reputation. First, it is analog in the sense that the ESC measures a time interval, not a number. Small timing errors in the signal, or noise on the wire, can shift the perceived throttle. Second, the update rate is slow: the classic refresh period is long enough that the flight controller cannot correct motor speed as often as modern gyro loops would like.
For large, slow multirotors and fixed-wing aircraft, PWM is still perfectly adequate. It is simple, well understood, and supported by nearly every ESC ever made. For FPV racing and acro flying, however, the slow refresh and analog measurement became the bottleneck, which is why the hobby moved on.
Oneshot: Faster Analog Refresh
Oneshot was the first attempt to close the gap. It keeps the same pulse-width idea as PWM but shortens the pulse durations and the refresh interval, so the flight controller can update the motors much more often. The result is noticeably more responsive control, especially on quadcopters where the gyro loop runs fast and expects the motors to follow quickly.
Oneshot is still analog. The ESC is still measuring a pulse width, so it still inherits the noise and resolution limits of that approach. But it was a meaningful step forward, and it is the protocol many older FPV stacks still use. A single or multi-ESC regulator from that era typically supports Oneshot alongside PWM.
Oneshot is largely a transitional technology today. It survives on older hardware and in retrofit builds, but new designs usually skip straight to DShot.
DShot: Digital Protocol for Digital ESCs
DShot replaced the analog pulse-width idea with a simple digital frame. The flight controller sends a short packet of bits that encodes the throttle value as a number, along with a checksum. The ESC reads the packet, validates it, and sets the motor. There is no pulse width to measure, so timing noise on the wire no longer directly corrupts the throttle command.
DShot comes in several bitrates, named for the approximate transfer speed: DShot150, DShot300, DShot600 and DShot1200. Higher bitrates let the flight controller update the motors more often, which matters most on fast FPV builds where the gyro loop runs at high frequency. On a larger, slower airframe, the difference between DShot300 and DShot1200 is rarely noticeable.
The other important DShot feature is telemetry. A DShot ESC can, over the same wire or a companion telemetry line, report back its temperature, current draw and voltage. That data feeds the flight controller's battery and motor monitoring, and it is what lets a modern stack warn the pilot before an ESC overheats. A 4-in-1 ESC board built around a 32-bit MCU is the kind of hardware that expects DShot and can make use of telemetry.
Comparing the Three Families
There is no single "best" protocol; the right choice depends on what the ESC and flight controller both support, and what the airframe actually does.
PWM
Oneshot
DShot
Firmware Matters as Much as the Protocol
The protocol on the wire is only half the story. The ESC's onboard firmware determines which protocols it speaks, how it handles telemetry, and how configurable the motor timing and startup behavior are. The BLHeli family is the most widely used open firmware lineage: the 8-bit BLHeli ran on older ESCs, and the 32-bit BLHeli_32 generation runs on modern, higher-current boards and supports DShot at higher bitrates.
A higher-current ESC regulator or a multi-rotor ESC paired with a 32-bit flight controller is the kind of combination where firmware choice is worth checking: confirm the ESC accepts a maintained firmware build, and that the configurator tool you plan to use (typically the open BLHeli configurator) supports the exact MCU on the board you are buying.
Backwards Compatibility: What Pairs With What
A common practical question is whether a modern DShot ESC works with an older flight controller, or vice versa. The short answer is that the pair must share a protocol both sides support.
Always confirm the supported protocol list on both the flight controller and the ESC before ordering a stack. The pairing is not always obvious from product marketing.
What Buyers Should Check on a Stack
When comparing an ESC and flight controller pair, the following items do more than the brand name.
A motor such as a brushless motor for multirotor use paired with the right ESC class is the normal way these builds come together; the protocol decision is usually settled by the ESC firmware rather than the motor.
Common mistakes to avoid
Frequently Asked Questions
Is DShot1200 better than DShot300 for every drone?
No. The higher bitrate helps when the gyro loop runs very fast, which is typical of small, agile FPV quadcopters. On larger, slower multirotors and fixed-wing aircraft, the difference is rarely perceptible, and the lower bitrate is simpler to wire and more tolerant of long signal leads.
Can a DShot ESC work with an old PWM flight controller?
Only if the ESC firmware supports a fallback to PWM or Oneshot. Many modern ESCs do, but you lose digital telemetry and the higher update rate. Confirm the supported modes on both devices before relying on a fallback.
Does DShot telemetry require extra wires?
It depends on the ESC and flight controller. Some implementations use the same signal wire for bidirectional communication; others use a dedicated telemetry pad. Check the wiring diagram for the exact board rather than assuming.
What is BLHeli_32?
BLHeli_32 is the 32-bit generation of the open BLHeli ESC firmware. It supports higher-current ESCs, DShot at higher bitrates and configurable telemetry, and it is configured through the open BLHeli configurator.
Do I need to reflash my ESC?
Not if the ESC ships with a firmware you are happy with. Reflashing becomes relevant when you want a newer protocol, telemetry behavior or a bug fix, and when the board supports the open configurator.


