Cooling fan PWM control uses a pulse-width modulation signal to request fan speed. A buyer should identify the exact fan, the matching controller and the documented response before approving a cooling assembly. Keep the command signal, measured speed and thermal acceptance as separate items in the review.
This guide focuses on supplier proposals for fan-assisted aluminum heat sinks or equipment enclosures. It helps organize the interface evidence. It does not provide a wiring procedure, choose a replacement fan or approve a cooling capacity for an illustrated profile.
On this page
Cooling fan PWM control: read the signal terms
Noctua’s PWM specification white paper addresses its 4-pin PWM fan families. It distinguishes the control input from the tachometer speed output. For its stated interface, the target control frequency is 25 kHz, with 21–28 kHz accepted.
Frequency describes signal cycles per second. Duty cycle describes the fraction of a cycle in the high state. The paper’s model-specific speed example also shows why a duty percentage should not simply be read as the same percentage of maximum RPM.
These facts concern the documented Noctua interface. They are not universal specifications for every industrial fan or evidence that a JiurunCut machine uses that product family. Obtain the exact proposed fan’s own documentation.
Keep three quantities separately named
| Quantity | What the comparison should identify |
|---|---|
| Control frequency | The stated signal frequency and accepted range for the selected interface. |
| Duty cycle | The controller’s command setting and the fan’s documented response. |
| Fan speed | The reported RPM, feedback source and condition behind the reading. |
A quotation saying “50% fan” leaves the intended quantity unclear. Ask whether it means a command setting, a recorded speed or another stated control mode. Preserve the supplier’s actual definition.
1. Identify the complete fan and controller interface
Record the fan manufacturer and full model, supply requirement, connection documentation and control-interface specification. Request the controller’s complete identification and the information supporting its use with that fan.
Have the responsible electrical designer review the proposed interface. Matching connector appearance does not complete that review. The supplier package should make the relevant signal requirements and the approved connection documentation visible.
Keep supply information beside the fan identity and control information beside the interface description. If the two appear in one unlabeled voltage column, ask the issuer to separate them. The reviewer needs to know which statement applies to which function.
Also record the offered cable and connector arrangement, installed location and any agreed environmental requirements. Request the actual assembly drawing rather than assuming that a catalog illustration represents the proposed equipment.
For a replacement order, retain the original approved part and list the offered alternative separately. Ask the owner to review every affected interface and assembly requirement before the purchase line changes.
2. Review the command and the response together
Request the selected product’s speed-response information and its behavior at the command conditions relevant to the application. Have the control owner identify what the controller requests during normal operation and which recorded feedback answers the review.
The Noctua paper describes differing low-duty behavior among its named models. That is a reason to retain the exact product identity when discussing minimum speed or stopping behavior. Do not approve an unspecified fan from a generic PWM label.
Ask the provider to identify what happens when control information is missing and how the proposed system reports an abnormal condition. Keep the documented response and the application’s required response separately identified. The responsible system designer should decide whether they meet the project requirement.
A fictional proposal review
Imagine cooling request F-63 for an enclosure assembly. Proposal A identifies its fan and controller but supplies no speed-response information. Proposal B includes a speed table but does not identify the represented controller revision. These are invented document gaps, with no test results or actual supplier ratings.
For Proposal A, request the missing response information for the named fan. For Proposal B, request the controller identity and the conditions behind the table. Both offers should connect their evidence to the same released assembly requirement before comparison.
A reviewer may ask for a demonstration or reported result at agreed command conditions. State the fan identity, controller setup, measurement source and acceptance question in that request. Keep any test report attached to the represented configuration.
Do not convert a command percentage into a guaranteed airflow or component temperature. The fan airflow and static-pressure guide addresses the separate air-path evaluation. Retain both the control response and the installed condition when reviewing the complete proposal.
3. Retain evidence for the complete cooling arrangement
Identify the assembly drawing and the operating conditions covered by its thermal review. Include the aluminum heat sink, fan arrangement, enclosure and relevant acceptance requirements. Ask the technical owner to define the evaluation and release decision.
The heat sink thermal-resistance guide helps organize thermal evidence. A visible RPM reading and an accepted device temperature are different review items. Give each its own result and supporting conditions.
Keep responsibility clear when several suppliers contribute parts. One may supply the cut aluminum section, another the fan and another the controller. The assembly owner needs their identified components and evidence together.
If the proposed controller, fan or enclosure layout changes, state the change and request the appropriate review. Do not silently attach an earlier acceptance record to a new configuration. Track the revision represented by each response and result.
Prepare a concise supplier handoff
A useful inquiry asks for the exact fan and controller, their interface documentation, response information and the scope of assembly acceptance. Identify any item that the supplier excludes from its quotation.
Quote the fan-assisted assembly against the attached drawing revision. Identify the fan, controller and connection documents. State the evidence supplied for command response, speed feedback and the agreed thermal requirement. List unresolved assumptions before order release.
For the aluminum parts, add the section drawing, finished lengths, quantity, mounting features and protected surfaces. If the project is still selecting the cooling approach, use the passive and active heat sink comparison to organize that earlier decision.
Send JiurunCut the aluminum profile and cutting requirements. Describe the delivered condition needed for the next assembly stage. Keep fan-control integration and thermal acceptance connected to their responsible technical owners.
Buyer questions
Does a matching plug approve a replacement?
Request the exact product and interface documents. Have the responsible reviewer evaluate the offered part against the complete requirement.
Does a commanded setting prove the fan reached its intended speed?
Ask which feedback or measurement records the response. Keep the command and observed result separately labeled.
Does an accepted speed reading approve the whole heat sink?
Retain the applicable assembly-level thermal evidence and acceptance decision. A speed record answers only its stated measurement question.