How Do You Drive a Brushless DC (BLDC) Motor with a Three-Phase Driver?
Last updated 6 July 2026 · 7 min read
Direct Answer
A brushless DC (BLDC) motor has three windings arranged 120 degrees apart, driven by a three-phase bridge — six switches (three half-bridges) instead of the four switches an H-bridge uses for a brushed DC motor or the eight switches two H-bridges use for a stepper motor. The driver's job is commutation: energising the correct pair of windings at the correct moment as the rotor turns, which requires knowing rotor position — either directly, from Hall-effect sensors embedded in the motor, or indirectly, from the back-EMF voltage the un-driven third winding generates as the rotor spins (sensorless commutation). Commutation itself is implemented as either simple six-step trapezoidal switching (energise two of three windings at a time, in six 60-degree steps per electrical revolution) or smoother, more efficient sinusoidal Field-Oriented Control (FOC), which continuously modulates all three phases based on the rotor's precise angle rather than switching between discrete states. Dedicated three-phase gate driver ICs (or fully integrated BLDC driver+controller parts) handle the high-side/low-side gate drive, bootstrap supplies, and often the commutation logic itself, the same way single-phase gate driver ICs and stepper driver ICs simplify their respective motor types.
Detailed Explanation
A BLDC motor inverts the brushed DC motor's mechanical commutation (the brushes and commutator that physically switch winding current as the rotor turns) into an electronic one — the permanent magnets are on the rotor, the windings are fixed on the stator, and a driver circuit switches current through the windings in the correct sequence based on rotor position. This is more complex to drive than a brushed motor but eliminates brush wear, gives higher achievable efficiency and power density, and enables much more precise torque and speed control — which is why BLDC motors dominate applications from drone propulsion to appliance motors to electric vehicle traction where brushed motors previously served.
The Three-Phase Bridge
Where an H-bridge uses four switches to drive one brushed-motor winding in either direction, and a stepper driver uses eight switches (two H-bridges) for two windings, a BLDC three-phase bridge uses six switches — three half-bridges, one per winding (commonly labelled U, V, and W phases). At any commutation step, exactly two windings are actively driven (one sourcing current, one sinking it) while the third is either floating (trapezoidal commutation) or also actively driven at an intermediate voltage (sinusoidal/FOC commutation).
Commutation: Knowing When to Switch
The fundamental problem a BLDC driver solves is timing: switching the wrong windings, or switching at the wrong moment, produces reduced torque, increased current draw, or a stalled/reversed motor. Two approaches to knowing rotor position dominate:
Sensored (Hall-effect) commutation. Three Hall-effect sensors, positioned 120 electrical degrees apart inside the motor, each output a digital high/low signal indicating which magnetic pole is currently passing. The combination of all three sensor states directly maps to one of six commutation sectors — simple, reliable at any speed including standstill, but requires the extra sensor wiring (typically 5 wires beyond the 3 motor phases: sensor supply, ground, and three Hall outputs) and adds a component that can fail.
Sensorless (back-EMF) commutation. As covered in the FAQ above, the undriven phase's back-EMF zero-crossing substitutes for a Hall sensor, eliminating the extra wiring and sensor cost — the majority of small drone, RC, and appliance BLDC drivers use this approach — but it cannot detect rotor position reliably at zero or very low speed, requiring an open-loop startup ramp before closed-loop commutation can begin. This startup phase is a common source of failed starts under load, since the motor is being driven blind without any confirmation it's actually following the commanded ramp.
Trapezoidal vs Sinusoidal (FOC) Control
Beyond knowing rotor position, the driver chooses how to shape the phase currents:
- Trapezoidal (six-step) commutation switches between six discrete states per electrical revolution, matching the Hall-sensor sector boundaries directly — simple to implement in firmware or dedicated hardware, but produces torque ripple at each 60-degree commutation step (felt as vibration or heard as acoustic noise, particularly at low speed).
- Field-Oriented Control (FOC) treats the motor's three-phase currents as a rotating vector in a rotor-aligned reference frame, using the Clarke and Park transforms to convert measured phase currents into direct (torque-producing) and quadrature (flux) components that PI control loops regulate independently — producing smooth, continuously-varying phase currents rather than six discrete steps. FOC needs accurate continuous rotor angle (not just sector information), current sensing on at least two phases, and meaningfully more computation per control loop iteration, but delivers smoother torque, lower audible noise, and better efficiency, especially at low speed — the reason FOC has become the default for higher-performance BLDC applications (e-bikes, drones, robotics) despite its added complexity.
Driver ICs and Integration Level
Three-phase BLDC driver ICs span a range of integration levels, mirroring the choice already covered for H-bridge motor drivers and stepper driver ICs:
- Three-phase gate driver ICs (TI DRV8323-class, similar parts from onsemi and Infineon) provide just the high-side/low-side gate drive with bootstrap supplies and shoot-through protection for six external MOSFETs — see MOSFET gate driver IC and bootstrap design for the bootstrap-capacitor mechanics this extends to three phases. All commutation logic, sensing, and control algorithm run in the host MCU or a dedicated motor-control peripheral.
- Integrated BLDC controller/driver ICs combine the gate drivers with an onboard commutation state machine (sensored or sensorless), reducing firmware complexity at the cost of less control over the exact commutation algorithm — a reasonable trade for products that need a motor spinning at a commanded speed without custom torque-control requirements.
- Complete driver modules (including hobbyist/drone ESCs) package the full power stage, gate drivers, and commutation firmware behind a simple speed-command interface (commonly a PWM or digital protocol input) — the fastest path to a working motor, at the cost of firmware/algorithm flexibility.
Many modern MCUs also include dedicated motor-control peripherals (timers with complementary PWM outputs and dead-time insertion, ADC triggering synchronised to PWM edges for current sensing) specifically to support driving the discrete-MOSFET approach without dedicating the CPU to bit-perfect PWM timing.
Zeus Design designs BLDC motor-control hardware and firmware — from driver IC selection through FOC or trapezoidal control implementation — as part of complete product electronics development.
Design Considerations
- Plan the sensorless startup ramp deliberately if going sensorless. A fixed open-loop ramp profile that works for an unloaded motor on the bench can fail to start the same motor under its actual working load — validate startup under worst-case load and inertia, not just a free-spinning bench test.
- Verify Hall sensor phase alignment against the winding phase order for sensored designs. A Hall sensor sequence that doesn't match the actual winding commutation order causes the motor to run backwards, stall, or run with severely reduced torque — this is a wiring/configuration check to make during bring-up, not something firmware can fully compensate for after the fact.
- Size the bridge and driver for stall current the same way as any other motor drive. BLDC motors, like brushed and stepper motors, draw their highest current at low speed under load — apply the same stall-current sizing discipline covered in the H-bridge motor drive page rather than sizing only for the nameplate running current.
- Budget the control loop's computational load honestly before committing to FOC. FOC's Clarke/Park transforms, PI loops, and space-vector modulation calculation must complete within each PWM period — verify the target MCU's available cycles at the intended PWM frequency before committing to FOC over the simpler trapezoidal approach, particularly on lower-end Cortex-M0/M0+ parts without hardware floating-point or DSP instructions.
Common Mistakes
- Assuming sensorless commutation works identically to sensored at all speeds. The zero-speed/low-speed blind spot is a fundamental limitation of back-EMF sensing, not a tuning problem — a design that genuinely needs reliable starts under load at unpredictable initial positions should reconsider Hall sensors rather than trying to perfect a sensorless startup ramp indefinitely.
- Under-provisioning bootstrap capacitor refresh time in low-speed or stalled operation. The same high-side bootstrap-capacitor refresh problem covered for single-phase gate drivers applies across all three high-side switches in a BLDC bridge — a commutation pattern that holds one high-side switch on for too long at low PWM frequency or low speed can starve its bootstrap capacitor.
- Neglecting EMI from the fast-switching three-phase bridge. A BLDC bridge switches at least as aggressively as a single-phase H-bridge, across three phases simultaneously — apply the same switching-loop and layout discipline used for any high-current switching stage, and budget EMC pre-compliance testing time rather than discovering the problem at formal certification.
- Confusing electrical degrees with mechanical degrees on a multi-pole-pair motor. A BLDC motor with more than one magnetic pole pair completes multiple electrical commutation cycles per single mechanical revolution — commutation timing, Hall sensor spacing, and back-EMF zero-crossing intervals are all specified in electrical degrees, and conflating the two produces commutation timing errors that scale with the motor's pole-pair count.
Frequently Asked Questions
- What's the difference between trapezoidal (six-step) and sinusoidal (FOC) commutation?
- Trapezoidal (six-step) commutation energises exactly two of the three windings at a time in a fixed sequence of six states per electrical revolution, leaving the third winding floating — simple to implement, requiring only knowledge of which 60-degree sector the rotor is in, but producing torque ripple at each commutation step and some acoustic noise. Field-Oriented Control (FOC) instead treats the three-phase currents as a rotating vector, continuously commanding all three phases with sinusoidal (or space-vector-modulated) waveforms that track the rotor's precise angle rather than discrete sectors — this gives smoother torque, lower acoustic noise, and higher efficiency, particularly at low speed, at the cost of needing accurate rotor angle information (rather than just sector information) and considerably more computation (current sensing on at least two phases, and the Clarke/Park coordinate transforms every control loop iteration).
- How does sensorless BLDC commutation work without Hall sensors?
- A three-phase BLDC motor's undriven winding (the one not currently part of the active commutation pair) generates a back-EMF voltage proportional to rotor speed as the rotor's permanent magnets sweep past it. Sensorless commutation monitors this back-EMF and detects the zero-crossing point — where it crosses the motor's electrical centre voltage — which reliably indicates the correct moment for the next commutation step. The core limitation is that back-EMF is proportional to speed, so it's too small to detect reliably at very low speed or standstill — sensorless designs typically start with an open-loop forced-commutation ramp (driving the motor blind at a slowly increasing frequency, hoping the rotor follows) before switching over to back-EMF-based closed-loop commutation once speed is high enough for a reliable zero-crossing signal.
- Do I need a dedicated BLDC driver IC, or can I build one from a generic three-phase gate driver and discrete MOSFETs?
- Both are legitimate approaches, and the right choice depends on how much of the commutation logic you want to own. A three-phase gate driver IC (TI DRV8323-class parts) handles only the high-side/low-side gate drive, bootstrap supplies, and shoot-through protection — the host MCU still runs all commutation logic, Hall/back-EMF sensing, and PWM generation in firmware or a dedicated motor-control peripheral. A fully integrated BLDC driver (parts that combine the gate drivers with onboard commutation state machines, or complete ESC-style modules) offloads much of that logic to the IC itself, at the cost of less flexibility over the control algorithm. For a design already committed to FOC with custom torque/speed control behaviour, the discrete gate-driver approach is usually necessary; for a design that just needs a motor spinning at a commanded speed, an integrated part is often faster to bring up.
References
Related Questions
How Do You Drive a DC Motor with an H-Bridge?
How an H-bridge drives a brushed DC motor in both directions — topology, shoot-through and dead time, PWM decay modes, driver ICs, and current sensing.
How Do You Drive a Stepper Motor with a Driver IC?
Drive a stepper motor with a dedicated driver IC: step/direction interface, microstepping, current-limit sizing, and A4988 vs DRV8825 vs TMC2209 trade-offs.
How Do MOSFET Gate Driver ICs and Bootstrap Circuits Work?
How MOSFET/IGBT gate driver ICs work, how to size a bootstrap capacitor and diode for high-side drive, and when a GPIO alone isn't enough.
PWM Explained: Frequency, Duty Cycle, Dead-Time, and Hardware Timers
Learn how PWM works: duty cycle, frequency, resolution, dead-time for H-bridge drives, and when to use hardware timers versus software PWM on microcontrollers.
How Do You Interface a Rotary Encoder to a Microcontroller?
Interface an incremental rotary encoder to a microcontroller: quadrature A/B decoding, hardware timer/PCNT counting vs software ISR decoding, and debounce.
How Do You Limit Inrush Current When a Board Is Hot-Plugged or Powered On?
Limit inrush current at power-on or hot-plug with a hot-swap controller or load switch IC — soft-start ramp, current limiting, and fault protection.