Running a fan at full speed all the time is the simplest thermal strategy and the loudest one. Almost every modern product modulates fan speed, but the method matters: PWM and voltage regulation behave very differently at low speeds, and choosing the wrong one produces stalled fans, audible ticking or premature bearing wear.

Voltage control: simple and lossy

Voltage control lowers the supply voltage to reduce speed. It requires only two wires and a variable regulator, which is why it appears in cheap designs. The drawbacks are significant. Below roughly 40–50% of rated voltage, most brushless fans cannot start reliably, and some will stall and then restart in a loop, drawing locked-rotor current each time. The fan’s P-Q curve also shifts unpredictably, so the airflow you calculated at 12 V is not proportional at 7 V.

There is also an efficiency cost: a linear regulator dissipates the voltage difference as heat, which in a hot enclosure is exactly what you do not need.

PWM control: efficient and precise

Pulse-width modulation switches the fan’s power stage on and off rapidly, leaving the supply voltage intact. A 4-wire fan accepts a 25 kHz PWM signal on a dedicated control wire while power stays constant, so the fan can run smoothly from about 20% to 100% speed without stalling. The motor’s internal commutation electronics do the work, which is why 4-wire fans are the standard in servers, medical devices and automotive electronics.

Because the control signal is separate from the power path, PWM also allows accurate speed reporting (tach output) and fault detection (locked-rotor alarm). That combination is what makes closed-loop thermal control possible: the controller reads temperature, sets a duty cycle, verifies the fan actually reached the requested speed, and raises an alarm if it did not.

The audible difference

A well-implemented PWM signal is inaudible because the switching frequency sits above the audible band relative to the motor’s response. A poorly implemented one — low frequency, slow edges, or long wires — can produce a faint ticking at the fan, caused by magnetostriction in the stator. If you hear ticking at low duty cycles, the fix is usually a higher PWM frequency or a small RC filter, not a different fan.

Voltage control, by contrast, tends to produce a smoother acoustic transition at mid speeds but becomes unstable at the bottom of its range. In products where silence at idle matters — monitors, audio equipment, bedroom appliances — the ideal is a 4-wire fan with a minimum duty cycle set high enough to avoid the acoustic “dead zone” near start-up.

Temperature-based control in practice

The most common control law is a simple ramp: below 40 °C run at 30%, above 70 °C run at 100%, linear in between. Two refinements make a real difference. First, add hysteresis so the fan does not oscillate audibly around the threshold. Second, add a startup kick: run at 100% for one second at power-on, then drop to the computed duty cycle, which clears dust and guarantees rotation from rest.

Failure modes to design against

Which to specify

If the fan is inside a device with a microcontroller, specify a 4-wire PWM fan with tach and alarm. If the product has no control electronics and simply needs to run, a 2-wire fan is cheaper and more robust. Voltage control is defensible only for low-cost products with a narrow speed range and no acoustic requirements — and even then, verify start-up at the lowest voltage the regulator can produce.

A closed-loop example that works

A 300 W charger uses two 80 mm 4-wire fans. The controller reads an NTC on the heatsink and maps 35–75 °C to 25–100% duty cycle, with a 1-second full-speed kick at power-on. Below 40 °C the fans idle at 25%, which is inaudible in a garage. Above 70 °C they ramp smoothly, and if the tach signal disappears the controller drops charging current by 50% and raises a fault flag.

This design costs a few dollars more than a fixed-speed fan but delivers three benefits at once: quieter operation most of the time, longer bearing life because average speed is lower, and a diagnosable failure mode instead of silent overheating. For any product with a microcontroller already on board, the incremental cost is mostly firmware.

What to write in the specification

State the control type (4-wire PWM, 25 kHz, 3.3/5 V logic), the minimum and maximum duty cycle, the expected speed at 50% duty, the tach specification (pulses per revolution), the alarm logic (open collector, active low) and the default behaviour if the control signal is lost. Ambiguity here produces fans that behave differently batch to batch — a problem that only shows up when a customer notices their unit is louder than the review sample.

Testing the control loop before release

Control behaviour is easy to get wrong in a way that only appears in the field. Before release, test these scenarios: cold start at −10 °C, a step change from 20% to 100% duty, loss of the tach wire, a blocked impeller, and a supply brown-out. In each case, confirm the fan behaves as specified and the system reports the condition rather than hiding it. A fan controller that silently ignores a stopped fan is worse than no controller at all, because it creates false confidence in a thermal design that has already failed.

Keep it simple where you can

Not every product needs a control loop. If the thermal load is constant and the acoustic environment is industrial, a well-chosen fixed-speed fan is more reliable and cheaper than any controller. Add modulation only where it buys something the user can perceive — quieter nights, lower energy bills, longer service intervals. Complexity should earn its place.

Need help selecting the right fan?

Send your size, voltage and airflow requirements — our engineers reply within 24 hours.

Get a Quote →
← Back to all news