BLDC Controller PWM Frequency: Noise, Loss and EMI Trade-Offs

Engineering note. This guide is published by the Sankey engineering content team for OEM planning. It explains the design decisions and evidence a project team should review; component datasheets, the intended end product, target-market requirements, and controlled laboratory testing remain the source of truth for a released design.

PWM frequency is a cross-functional design setting. A frequency that improves one acoustic or control objective can increase switching loss, change current ripple, tighten timing requirements, or move emissions into a more difficult test condition.

What this decision changes

The selected frequency influences MOSFET and gate-driver stress, audible tones, current-sense timing, controller CPU load, thermal behavior, filter design, and the repeatability of production software. It must be chosen with the motor and load, not in isolation.

Start with measurable inputs

Define motor inductance and resistance, bus voltage range, target speed range, acoustic target, current limit, switching devices, control loop timing, enclosure temperature, and cable configuration. Identify the operating points most likely to produce audible beat tones or difficult emissions.

Engineering review method

Evaluate a small set of feasible frequencies in hardware. Compare phase-current ripple, device temperature, gate and drain waveforms, speed stability, audible response, and pre-compliance emissions under the same load. Check that ADC sampling and current reconstruction remain valid at duty-cycle extremes.

Evidence to keep with the design

Keep frequency comparison plots, microphone or controlled acoustic observations where available, thermal data, current ripple captures, emissions setup details, firmware version, and the motor/load configuration used for each run.

Failure paths to challenge early

Teams often move frequency above the audible range without checking switching loss, or lower it for efficiency without checking torque ripple and audible artifacts. Another frequent miss is using a bench motor that does not represent the installed blade, housing, cable, or supply.

Before prototype release

Document the approved frequency range, any speed-dependent scheduling, the test conditions supporting it, and the configuration control for firmware. Revalidate when a MOSFET, driver, motor, layout, or cable changes.

Questions an OEM team should close

What measurable acoustic and thermal criteria determine the acceptable frequency range?
Does current sensing remain accurate at low and high duty cycles?
Which system changes require the PWM decision to be reviewed again?