A 4-pin PWM fan looks simple. Four wires. One connector. One speed command.
But that simplicity is misleading. In my experience, this is where the confusion usually starts. A 4-pin desktop fan header, a 4-wire industrial EC fan, and a cabinet controller output can all look compatible on paper while behaving very differently in the field.
Key Takeaway
A 4-pin connector does not guarantee one universal control standard. In industrial wiring, the useful questions are whether the PWM input type is correct, whether the tachometer signal is referenced properly, and whether power and signal routing are clean enough for stable control.
This guide explains what each pin actually does, how the PWM signal works, why tachometer wiring is often misunderstood, and how to wire a 4-pin PWM fan correctly in an industrial cabinet. It also sits inside the broader Cooling Fan Fundamentals, where control logic, signal integrity, and real-duty behavior matter as much as basic airflow selection. The pinout and signal logic here apply the same way whether you’re wiring an axial fan or a centrifugal fan — the wiring doesn’t change, only the duty and pressure requirements do.
What the Four Pins Actually Do
Every 4-pin PWM fan has the same basic idea: two wires keep the fan alive, one wire reports speed, and one wire tells the fan how hard to run. That is the concept. The implementation can still vary by application.
| Pin | Function | Direction | Signal type |
|---|---|---|---|
| 1 | Ground (GND) | – | Power reference |
| 2 | Power (VCC) | Input | DC supply, typically 12 V or 24 V |
| 3 | Tachometer | Output | Open-collector pulse |
| 4 | PWM control | Input | Open-drain or logic pulse |
4-pin PWM fan pinout and wire colors
The 4-pin PWM fan connector follows Intel’s 4-Wire PWM Fan Specification. Standard Intel-compatible wire colors are:
| Pin | Signal | Function | Wire color (Intel) |
|---|---|---|---|
| 1 | GND | Ground / 0 V reference | Black |
| 2 | +12V | Power (12 V; 24 V on some industrial fans) | Yellow |
| 3 | Sense (TACH) | Speed feedback, 2 pulses/rev, open-collector | Green |
| 4 | Control (PWM) | Speed-control input, 25 kHz, open-drain | Blue |
Note: some AMD-branded fans use red for the +12 V wire and yellow for the tachometer (Sense); pin positions and electrical behavior are identical.
Pin 1 (Ground) and Pin 2 (Power) – the baseline every fan shares
Pin 1 is the electrical reference. Pin 2 is the supply input. Without a stable ground and the correct supply voltage, nothing else in the connector matters. This part is common to almost every electronically controlled fan system, whether the fan is used in a PC, a server tray, or an industrial cabinet.
The problem is that many installers stop there. They verify voltage, see the fan spin, and assume the wiring is correct. It may not be. A powered fan is not the same as a controllable fan.
Pin 3 (Tachometer) – how the fan reports its speed back to the controller
The tachometer wire is the feedback channel. It does not control the fan. It reports fan speed back to the controller, usually as a pulse signal that can be counted and translated into RPM. In many applications, that feedback is just as important as the PWM command itself.
This is especially true in cabinets and fan trays where the controller needs proof that the fan is actually responding, not just receiving power. The signal may exist. The control may not.
Pin 4 (PWM signal) – the control wire that changes everything
Pin 4 carries the speed command. In a standard 4-wire PWM concept, the fan receives a pulsed control signal and interprets duty cycle as a requested speed level. That extra wire is what separates PWM-based control from simpler voltage-drop control on a 3-pin fan.
I would not assume that a 4-pin connector means a shared control standard. The connector may look familiar, but the PWM input logic behind it may not.
Pin numbering and connector orientation – why wiring errors often start here
A surprising number of field mistakes begin before the wire is landed. Numbering may be shown from the cable side in one document and from the mating-header side in another. A technician may identify the right four functions and still reverse them because the orientation was read from the wrong viewpoint.
This is not a minor detail. If the PWM and tach positions are swapped, the controller may show a dead fan, a locked-speed fan, or an unstable signal pattern that looks like a control fault. Always verify orientation from the actual datasheet before treating the pin order as settled.
The PWM Signal Itself – Frequency, Duty Cycle, Startup, and Minimum Control Limits
The PWM line is not just an on-off wire. It is a signal specification. Frequency, duty cycle, startup behavior, and minimum controllable range all affect what the fan actually does once the signal reaches the input.
Why 25 kHz became the standard and what happens below that frequency
In the desktop 4-wire PWM world, 25 kHz is the familiar reference point because it keeps the switching above the audible range for many applications while still being practical for fan electronics. That makes sense in the Intel-style 4-wire specification context.
The Intel 4-wire PWM fan specification is still the clearest historical anchor for the desktop-standard interpretation of this topic, which is why many engineers still start there before comparing any industrial implementation against the actual fan datasheet.
Industrial reality is broader. Some industrial EC control systems still expect open-collector PWM, but acceptable frequency range may differ by fan family or controller design. Some manufacturer-side documentation supports a much wider operating band, which is exactly why desktop assumptions can become misleading once you leave the motherboard header world.
How duty cycle translates to fan speed from startup to full load
Duty cycle defines how long the PWM signal stays high within one switching cycle. Higher duty usually means a higher commanded speed. Lower duty usually means a lower commanded speed. That is the basic relationship.
But the field behavior is rarely perfectly linear. Some fans follow duty closely across most of the range. Others compress the low end, jump at startup, or hold a minimum internal floor. A valid waveform is not the same as a predictable speed curve.
Startup floor, restart threshold, and why run duty is not always restart duty
A fan may keep running at a lower duty than it needs to start from rest. This is one of the most common misunderstandings in PWM control. The motor may spin smoothly once already moving, yet refuse to start reliably from the same command if the fan is stationary.
That is why startup floor and restart threshold deserve separate attention. In practical commissioning, the fan should be tested both from stopped condition and from stable running condition. Do not assume they match.
Minimum duty cycle and stall protection – what the Intel spec actually requires
The Intel-style 4-wire PWM framework includes expectations around minimum behavior, startup assurance, and low-duty response. Those details matter because they set the reference many people still carry into industrial work.
But here’s the thing. Industrial EC fan control often adds another layer of interpretation. Some systems handle low duty by holding a defined minimum speed, some treat very low duty as stop, and some require application-specific validation because the internal profile is not identical to the desktop expectation. This is why PWM fan control vs voltage control is a useful companion read before treating all PWM-controlled fans as one shared class.
Intel 4-Wire PWM Specification: Key Parameters
The 4-pin PWM standard originated from Intel’s 4-Wire Pulse Width Modulation (PWM) Controlled Fans specification, first published in 2003 and updated to Revision 1.3 in 2005. Most desktop motherboards and many industrial controllers follow this spec. Industrial EC fans sometimes deviate — which is where wiring problems start.
| Parameter | Intel Spec (Rev 1.3) | Industrial EC fans |
|---|---|---|
| PWM frequency | 25 kHz (±6.25 kHz) | 1–25 kHz (check datasheet) |
| PWM signal level | 5V logic, open-drain | Usually 5V; some accept 3.3V |
| Duty cycle range | 0–100% | 0–100% |
| 0% duty cycle behavior | Fan runs at minimum speed | Fan may stop or hold minimum RPM |
| Tach output type | Open-collector | Open-collector |
| Tach pull-up voltage | 5V | 3.3V or 5V |
| Pull-up resistor | 1–10 kΩ | 1–10 kΩ |
| Tach pulses per revolution | 2 | 1, 2, or 4 (fan-specific) |
| Power supply voltage | 12V DC | 12V or 24V |
| Minimum startup duty cycle | Fan-specific, typically 20–30% | Fan-specific — test before assuming |
One detail that causes repeated trouble: 0% duty cycle does not guarantee the fan stops. The spec allows fans to hold a minimum speed at 0% duty. If your application needs the fan fully off, check the manufacturer datasheet for a dedicated enable pin or use a power-side switch.
Source:
4-Pin vs 3-Pin Fans – When the Extra Wire Matters
The extra wire matters whenever stable speed control, repeatable startup behavior, or real feedback is important. It matters less when the application only needs a powered fan with simple run/stop behavior.
| Feature | 3-pin fan | 4-pin PWM fan |
|---|---|---|
| Speed control method | Voltage variation | PWM duty cycle |
| Feedback signal | Tach on some models | Tach standard in typical 4-wire control setups |
| Minimum controllable speed | Limited by startup voltage | Lower, defined by duty-cycle behavior |
| Industrial continuous-duty use | Basic on/off acceptable | Recommended for modulating control |
| BMS or PLC integration | Limited | Better suited for alarm and feedback loops |
For a broader overview of all three connector types, 2-pin, 3-pin, and 4-pin, including compatibility and application fit, see 2-Pin, 3-Pin & 4-Pin Cooling Fan Connectors.
What a 3-pin fan does when you connect it to a 4-pin header
A 3-pin fan connected to a 4-pin header still uses power, ground, and tach if the arrangement supports it. What it does not use is the dedicated PWM control input, because that input wire is not present. In many systems, the fan then runs either at fixed speed or under a separate voltage-based control behavior.
This is where many people think they are doing PWM control when they are really doing supply-voltage control. The fan spins. The speed changes. The control method is still different.
Can you plug a 4-pin fan into a 3-pin header – and what you lose when you do
Yes, mechanically and electrically, a 4-pin fan can often be connected to a 3-pin header arrangement. But the dedicated PWM control line is then not being used in the intended way. In practice, that means the fan may run at full speed, at a board-defined fallback, or under a reduced control scheme that does not reflect the real 4-wire logic.
Do not assume compatibility means full functionality. It usually does not.
Speed control accuracy: voltage-drop method vs PWM signal method
Voltage-drop control changes the supply level to influence motor speed. PWM signal control keeps the supply stable and changes only the control input waveform. That difference affects startup reliability, low-speed behavior, efficiency, and signal integration.
For industrial continuous-duty operation, a stable supply plus separate control signal is usually easier to manage than trying to shape speed by starving the fan electrically. This is one reason PWM and EC control have become more common in systems that run long hours or need tighter temperature response.
Which to specify for industrial continuous-duty vs simple on/off applications
If the application only needs basic airflow with limited control sophistication, a simpler 3-pin or non-feedback fan may still be enough. If the application needs speed modulation, alarm logic, RPM confirmation, or adaptive thermal response, the extra wire matters a lot.
I would specify 4-wire PWM whenever the installation needs predictable response rather than just powered airflow. That threshold comes earlier than many people think. For a full method comparison, including voltage control, 0-10V, and BMS integration, see PWM Fan Control vs Voltage Control.
Industrial EC Fan PWM vs PC Motherboard PWM – Not the Same Standard
This is where many wiring assumptions fail.
How EC fan PWM input differs from the Intel 4-pin desktop spec
The Intel desktop 4-wire specification is the best-known reference for PWM fan behavior, but industrial EC fans often sit in a different control ecosystem. The fan may still use four wires. The control expectations may still include PWM and tach. The actual electrical behavior can still differ in important ways.
Industrial EC fans may accept open-collector PWM, may expect different signal conditioning, may use a wider acceptable frequency range, or may define stop/start behavior differently from the desktop assumption. The control concept is similar. The integration standard is not always the same.
Input impedance, voltage levels, and signal isolation in industrial fans
Industrial installations add issues that PC headers usually hide: controller output type, input impedance expectations, pull-up requirements, longer cable runs, noisier grounds, and mixed power environments. That is why a signal that looks correct at the controller may still misbehave at the fan input.
In my experience, the biggest mistake is treating the PWM line as if it were just another logic wire with universal behavior. It is not. Some industrial systems need external pull-up handling. Some rely on cleaner reference routing than the installer expects. Some behave badly when power and signal are bundled together near noisy drive outputs.
Why a PC fan controller will not reliably drive an industrial EC fan
A desktop controller is built around the desktop control expectation. An industrial EC fan may need different signal assumptions, different grounding discipline, different connector practices, and different alarm integration. Even if the fan responds, that does not mean the control is reliable.
This is why I do not treat a PC fan controller as a safe commissioning tool for an industrial EC fan unless the actual fan documentation explicitly supports that pairing. For broader motor and application differences, EC fan vs AC fan helps frame why the control behavior can diverge so much once the fan is part of a real industrial system.
The Tachometer Signal – Reading Fan Speed in Industrial Systems
The tachometer line is where “fan seems okay” turns into measurable reality. If wired correctly, it tells the controller whether the fan is actually doing what the PWM command requested.
Open-collector output – what it is and how to wire it correctly
Many tachometer outputs are open-collector style outputs. That means the signal line does not generate a complete high-level voltage on its own in the way some installers assume. Instead, it switches relative to an external pull-up path and reference.
That detail matters. A tach line can look dead, noisy, or incomplete simply because the surrounding wiring logic is wrong. The fan may be fine.
Pull-up voltage, reference ground, and why tach wiring often fails in practice
Tachometer wiring often fails for the same reason PWM wiring fails: the signal is treated like a simple conductor instead of a signal path with reference requirements. If the pull-up arrangement is missing or mismatched, or if the ground reference is noisy, the pulse train can become unstable or unreadable.
I treat tach wiring as a signal-integrity issue first, not only a pinout issue. That mindset solves problems faster.
Pulses per revolution and how to calculate actual RPM from the signal
The controller does not infer RPM by magic. It counts pulses. To turn pulse frequency into actual fan speed, the controller needs the pulses-per-revolution value from the fan documentation. Two pulses per revolution is common, but not universal.
This is another point where industrial systems differ. Some controllers allow configurable pulses per revolution, including alarm-only or non-standard profiles. If that value is wrong, the RPM reading can be consistently wrong even when the wiring is correct.
A fan’s tachometer (tach) output reports speed as a number of pulses per revolution (PPR). To convert a measured tach frequency into fan speed, use:
RPM = (tach frequency in Hz × 60) ÷ pulses per revolution.
Most brushless DC and PWM fans output 2 pulses per revolution, so a 100 Hz tach signal equals (100 × 60) ÷ 2 = 3,000 RPM. Always confirm the pulses-per-revolution value on the fan datasheet, as some fans use 1 or 4.
Integrating tachometer feedback into BMS, PLC, or SCADA
In industrial systems, tach feedback is not only for display. It feeds alarm logic, trend records, redundancy decisions, and maintenance planning. A BMS may use it to confirm server tray health. A telecom cabinet controller may use it to raise a pre-alarm before enclosure temperature drifts too far. A BESS controller may use tach loss as a trigger for backup fan activation.
That is why the tach wire deserves the same design attention as the PWM line. It is a control-system signal, not just an accessory output.
Wiring a 4-Pin PWM Fan in an Industrial Cabinet – Step by Step
This is the most practical part of the guide. A correct 4-wire fan can still behave incorrectly if the wiring is handled like ordinary low-voltage power instead of a mixed power-and-signal connection.
Connector types used in industrial fans vs PC fans
Industrial fans often use terminal blocks, fixed industrial plugs, cabinet harnesses, or controller-side screw terminals rather than the small friction-fit motherboard connector seen in PC hardware. The signal logic may be related. The physical connection standard often is not.
That matters because connector style affects shielding, cable retention, field service, and how easy it is to misread pin orientation.
Wiring Reference: 4-Pin PWM Fan to Controller
| Fan connector | Controller | |
|---|---|---|
| Pin 1 — GND | ──── | GND |
| Pin 2 — VCC | ──── | +12V (or +24V for industrial) |
| Pin 3 — Tach | ──── | Tach input + 4.7 kΩ pull-up to +5V |
| Pin 4 — PWM | ──── | PWM output (5V, 25 kHz) |
Three things that go wrong most often:
Pull-up resistor missing on tach. The tach pin is open-collector. Without a pull-up resistor to 5V, the signal floats and the controller reads garbage RPM or zero. Add a 4.7 kΩ resistor between the tach line and 5V.
Signal cable running next to power cable. PWM and tach lines are low-voltage signals. Running them alongside 12V or 24V power lines, or near VFD output cables, picks up noise. Route signal wires separately. Even 10 cm of separation helps.
Assuming 0% duty = fan off. It doesn’t. Test the actual minimum speed at 0% duty before finalizing your control logic. If the fan needs to stop completely, use a relay or mosfet on the power line.
A six-step wiring sequence from power to signal verification
The safest sequence is simple:
- 1 Confirm voltage and pinout Verify fan supply voltage, rated current, and connector orientation from the datasheet.
- 2 Land power first Land power and ground first, then verify stable supply at the fan terminals.
- 3 Confirm controller output type Confirm the controller output type before wiring the PWM line.
- 4 Wire tach correctly Wire the tach output with the correct pull-up and reference logic.
- 5 Separate signal routing Route PWM and tach away from motor power and VFD output cabling.
- 6 Test real operating behavior Test startup duty, restart duty, full-speed response, and tach stability under real cabinet conditions.
This sequence catches more installation faults than trying to debug all four wires at once.
Signal wire routing – keeping PWM away from power and motor lines
PWM and tach lines do not belong in the same routing path as noisy motor power conductors when cleaner routing is available. Parallel runs next to VFD output cables, bundled low-voltage and high-power conductors, and shared noisy return paths can all distort the control or feedback signal.
A single cabinet can show all three routing mistakes at once.
Picture a 24 VDC external-rotor EC axial fan cooling a VFD and PLC control cabinet that stays locked at high speed, ignores commands below 40% duty, and shows intermittent tach loss. The fan itself is not the problem. The PWM input has no external pull-up, the signal wiring runs parallel with noisy VFD output cabling over about 1.8 m, and the grounding path is shared with high-noise drive components.
How to correct the three faults
The corrections are simple but critical: add a 10 kOhm pull-up resistor on the PWM input, separate signal and power routing, clean up the signal reference path relative to the power circuit, and re-make all 4-pin terminations. With those fixed, a fan like this should control smoothly across its rated duty range, give stable tach feedback, and soft-start reliably at low command levels.
Typical technical data show why this topic matters: 25 kHz PWM frequency, 15% startup duty, and 2 pulses per revolution. The connector can be correct and the fan can be correct while the wiring architecture is not.
PWM Fan Control in Real Applications
The control idea is the same across many use cases: power the fan, command the speed, read the feedback. The integration rules are not the same.
Server rack and data centre fan trays – why PWM is the default choice
In server rack and data centre fan trays, PWM is often the default because thermal load can move fast and cooling response needs to follow without wasting power at all times. Typical control logic may tie rack inlet temperature to fan duty, with something like 28 C calling for moderate duty and 35 C pushing the tray to full speed.
Tach feedback is just as important here. Real RPM is uploaded to the management layer so the system can detect degraded fan trays before total failure. For a wider application view, see server rack cooling.
Telecom cabinet cooling – duty-cycle profiles for day/night ambient swings
Outdoor telecom cabinets are a different control problem. The thermal load is not only electronic. It also follows ambient swing, solar gain, and enclosure behavior. Night conditions may allow low-duty quiet running. Daytime heat may demand much higher duty even before the internal electronics themselves change much.
In a semi-sealed IP-rated cabinet, tach feedback can be tied to pre-alarm logic so falling RPM is noticed before the internal enclosure temperature climbs into a dangerous zone. That is one reason telecom cabinet cooling benefits from PWM control and feedback rather than fixed-speed operation alone.
BESS and industrial enclosures – when to add tachometer alarm to the loop
In BESS and industrial enclosure cooling, PWM is often part of staged thermal control. Low-speed standby may be enough below one temperature band, medium continuous speed may be used in the middle band, and full-speed plus system notice may be triggered above a higher limit.
Here the tach alarm should usually be part of the loop, not an optional extra. In high-value enclosures with 24/7 duty, PWM signal loss may trigger forced high-speed fallback, while missing tach pulses may confirm fan fault and switch a redundant fan group into operation.
Same control concept, different integration rules by application
This is the last point worth stressing. Server trays, telecom cabinets, and BESS enclosures may all use PWM and tach. They do not all use them with the same assumptions.
The connector is not the standard. The waveform is not the whole story. The application decides what the signal has to mean.
Conclusion
A 4-pin fan connector does not guarantee one universal control standard. It only tells you that power, feedback, and command are likely separated into different wires.
That distinction matters because PWM and tach signals have to be treated as signal paths, not just as extra conductors in the harness. Pull-up logic, reference grounding, cable routing, startup threshold, and pulses per revolution all affect whether the fan actually behaves the way the controller expects.
The desktop 4-wire PWM specification is still the most familiar reference point, but industrial EC fan control often works inside a different electrical and integration context. That is why a fan can be powered correctly and still be wired badly.
If I had to reduce this guide to one rule, it would be this: do not assume compatibility from connector shape alone. Verify the pinout, confirm the signal type, separate power from control wiring, and test both PWM response and tach stability under real operating conditions.
FAQ
Q: What are the 4 pins on a PWM fan?
A: They are typically ground, power, tachometer output, and PWM control input. Two wires keep the fan powered, one reports speed, and one carries the speed command.
Q: What is the PWM pin on a fan?
A: It is the dedicated control wire that carries the pulsed command signal telling the fan how hard to run. It is different from simply changing the fan supply voltage.
Q: What frequency is PWM fan control?
A: In the classic desktop 4-wire PWM context, 25 kHz is the common reference. Industrial EC fans may accept different frequency ranges depending on the manufacturer and control design.
Q: What is the difference between 3-pin and 4-pin fans?
A: A 3-pin fan typically uses power, ground, and tach only. A 4-pin fan adds a dedicated PWM control input, which allows speed control without changing supply voltage.
Q: Can I plug a 4-pin fan into a 3-pin header?
A: Often yes mechanically, but you usually lose the intended PWM control behavior. The fan may run at full speed or under a simplified fallback mode rather than true 4-wire control.
Q: How does PWM fan speed control work?
A: The controller sends a pulsed signal with a defined duty cycle. The fan electronics interpret that duty cycle as a speed command and adjust motor operation accordingly.
Q: What is a tachometer signal on a fan?
A: It is the feedback output that reports fan rotational behavior back to the controller, usually as pulses that can be converted into RPM.
Q: What is the minimum PWM duty cycle for a fan?
A: There is no single universal number. Some fans may hold speed at very low duty, while others need a higher startup floor. That is why startup duty and running duty should be checked separately in the real application.
References
-
Intel Support, Industry Specifications for Intel NUC. Intel support material identifying the desktop 4-Wire Pulse Width Modulation (PWM) Controlled Fans Specification, Revision 1.3, September 2005. Read more
-
ebm-papst, FAQ. Useful for dedicated PWM control input guidance and fan-specific frequency notes. Read more
-
ebm-papst, TMS GUI Interface 210-OMI13962. Useful for PWM frequency range, stationary PWM, and pulses-per-revolution settings. Read more
-
ebm-papst, TMS Development Kit 210-OMI13191. Useful for four-wire industrial fan examples, open-collector control type, and tachometer compatibility. Read more
-
Delta Electronics, Pulse Width Modulation – PWM. Useful as a manufacturer-side example of broader PWM implementation beyond desktop fan control. Read more
Disclosure
This article is provided for general informational purposes and is based on field experience, publicly available technical references, and representative application data. Signal behavior, wiring compatibility, and control performance should always be verified against the actual fan datasheet, controller logic, and site wiring environment.
About The Author
Krystal K is a Technical Marketing Engineer at Proventofan, where she writes about industrial cooling, airflow engineering, fan control, and application-driven wiring guidance for cabinets, telecom systems, server racks, and other high-duty equipment.
