Exclusive Deals & New Industry-Leading Products for Wholesalers
ELECDURA NETWORK

Leading Automotive Parts 

Supply Chain Solution Provider

 WhatsApp
+86 18915027366
 Phone
+86 18915027366
You are here: Home » Blog » Technical Guides » PWM Radiator Fan Command vs Actual Speed: Scope-Based Diagnosis

PWM Radiator Fan Command vs Actual Speed: Scope-Based Diagnosis

Views: 0     Author: Site Editor     Publish Time: 2026-08-24      Origin: Elecdura

A PWM radiator fan can receive a valid speed request and still run too slowly, run at maximum speed, surge, or remain stopped. The missing step in many diagnoses is a time-aligned comparison between the command waveform and the fan's physical response. Scan data shows what a controller intends, but it does not prove that the signal reaches the fan, that the fan electronics interpret it correctly, or that the motor and blade create useful airflow.

Pulse-width modulation also has no universal pinout or logic convention. Some assemblies receive constant battery power and ground plus a low-current PWM command. Others use a module that switches the high-current feed, a ground-side command, or network communication. A percentage displayed by a scan tool may represent requested cooling, electrical duty, or an inverted value. Identify the exact radiator fan assembly architecture before connecting jumpers or interpreting percentages.

Quick Answer: What Must Be Compared?

Evidence

What it establishes

What it cannot establish alone

Scan-tool fan request

The controller's reported intent

The waveform present at the fan connector

Measured PWM duty and frequency

Electrical command quality at the test point

Correct interpretation by the fan module

Power and ground voltage drop

Whether high-current supply remains available under load

Motor torque or blade airflow

Fan current waveform

Electrical loading, startup, switching, and intermittent behavior

Correct rotation or shroud performance

Independent fan RPM

The physical speed response

Whether that speed moves the required air

Feedback or tach signal

What the fan reports to the controller

Accuracy unless compared with independent RPM

Airflow and temperature/pressure change

Whether the response solves the heat-rejection demand

Which electrical component caused a poor response

Classify the Fan Control System Before Testing

Separate resistor, relay, module, and smart-motor designs

A discrete two-speed fan may use relays and a resistor rather than PWM. Another assembly can contain a separate fan control module, while a brushless fan may integrate power electronics with the motor. Count terminals, trace heavy-gauge conductors, locate external modules, and read the wiring diagram. The guide to brushless versus brushed radiator fan motors explains why direct-power tests that suit a two-wire brushed motor may damage a smart fan.

Identify every pin by function

Label constant power, switched power, ground, PWM command, feedback, ignition wake-up, and network terminals as applicable. Do not assign function from wire color across different models. Confirm whether the control line has an ECU pull-up, a module pull-up, or an internally generated voltage. This determines the correct scope connection and prevents a test lamp from overloading a low-current circuit.

Confirm the specified command frequency

A module may reject a duty cycle delivered at the wrong frequency even when a multimeter displays the expected average voltage. Use service information or capture a known-good signal. Record frequency, duty cycle, high and low voltage, polarity, and waveform stability. A function generator should be used only with a protected interface and a confirmed pinout.

Determine whether the duty convention is inverted

On one application, greater high-time can request faster operation. On another, the active-low portion carries the command, making the apparent relationship opposite. Some controllers also reserve duty ranges for fault states. Compare measured waveform with scan command at several points instead of assuming that 80% always means high fan speed.

Verify That Cooling Demand Is Real

Review all inputs that can request fan speed

Coolant temperature, A/C refrigerant pressure, ambient temperature, transmission temperature, charge-air temperature, battery or inverter cooling, and engine protection modes may contribute to the request. A fan running at maximum can be responding correctly to a biased sensor or missing network message. Preserve codes and freeze-frame data before clearing anything.

Compare requested and commanded values

Some scan tools show a calculated desired speed and a separate electrical command. They are not interchangeable. A controller may limit the output because of battery voltage, engine speed, communication loss, or a detected fan fault. Identify the parameter definition and update rate. If only a generic percentage is available, corroborate it with the scope.

Use an actuator test carefully

A bidirectional test can create controlled steps without overheating the engine, but the function may be disabled by temperature, engine speed, or active faults. Command several stable levels and allow the fan to settle. Do not hold maximum speed longer than the service procedure permits, and keep all tools and leads outside the rotating zone.

Measure the PWM Signal at Both Ends of the Circuit

Start at the fan connector under load

Back-probe without spreading or damaging sealed terminals. A correct command at the controller is insufficient if an open conductor, short, corrosion, or poor terminal changes it before the fan. Capture the signal while the connector is installed and the fan is commanded, because an unplugged open-collector line can assume a different voltage.

Check amplitude as well as duty

A waveform can have the requested duty cycle but insufficient high level, a ground that never falls low enough, rounded edges, or electrical noise. Compare high and low voltages with specification. Repeat while moving the harness at known stress points. If the waveform changes with vibration, inspect terminal tension and conductor strands.

Compare the controller output when necessary

If the connector signal is invalid, measure at the controller or intermediate module using approved access. A valid source waveform and invalid fan-end waveform isolate the harness. An invalid source requires power, ground, input-data, driver, and protection-state checks before the controller is condemned.

Do not confuse communication with PWM

LIN or another serial signal can look like a changing square wave but carries framed data rather than duty-based speed instruction. A duty measurement on that line is meaningless. The existing PWM and LIN fan-control diagnosis provides the signal-family distinction.

Test Power and Ground While the Fan Accelerates

Measure at the high-current terminals

A smart fan can receive a perfect command yet fail because battery feed collapses under load. Record voltage at the assembly and voltage drop across the positive and ground paths during low, medium, and high requests. Inspect fuses, relay or power-stage contacts, connectors, splices, and grounds. Static battery voltage at an unplugged connector proves very little.

Correlate voltage drop with current

A high drop at modest current points to connection resistance. A modest drop at excessive current may reflect motor or mechanical overload. Local heating and plastic discoloration help locate the loss, but a loaded voltage measurement is stronger evidence. Use the radiator fan relay load test where a separate relay feeds the assembly.

Check wake-up and ignition circuits

Some modules require a separate ignition or wake input in addition to constant power. A missing wake signal can create a no-response condition even when the heavy terminals are correct. Other designs wake from the PWM or network line. Confirm the sequence and timing from the diagram rather than supplying power to an unknown terminal.

Compare Command With Independent Fan RPM

Measure speed without relying on feedback

Use an approved optical, magnetic, or diagnostic method to measure the physical fan speed. Record RPM after each command has stabilized. If scan data supplies fan feedback, compare it with independent RPM. A fan that physically changes speed while scan feedback stays fixed has a different fault from a fan that never responds.

Build a command-response curve

Plot command on one axis and stabilized fan RPM on the other. The curve may not be linear; modules can use dead bands, minimum speeds, soft starts, and temperature protection. Compare with service data or a verified unit of the same part number. Do not import RPM limits from a different blade, voltage, or vehicle.

Watch response time and stability

A slow rise can indicate current limiting, low supply voltage, bearing drag, motor damage, an underspecified assembly, or deliberate soft start. Hunting around a steady command can indicate unstable power, noisy signal, thermal protection, feedback error, or control-loop problems. Capture several seconds of command, current, voltage, and RPM together.

Distinguish feedback failure from motor failure

If independent RPM is correct but the feedback pulse is missing or incorrectly scaled, inspect the sensor, target, signal terminal, pull-up, and controller interpretation. Replacing a mechanically healthy radiator fan motor without checking the feedback circuit may repeat the code.

Use Current Waveforms to Find Mechanical and Electronic Faults

Record startup and stabilized current

Brushed motors show a startup surge followed by current that depends on speed and load. Brushless assemblies can shape the startup electronically, so clamp-meter inrush features may not describe internal phase current. Compare battery-side current at repeatable commands and temperatures. The fan motor current-draw guide explains how sustained overload differs from a brief normal peak.

Relate current to RPM

High current with low speed suggests mechanical drag, blade contact, winding damage, or an internal power-stage problem. Low current with low speed can indicate supply interruption, command limiting, open winding, or module shutdown. Normal current and RPM with poor cooling directs attention away from electronics and toward airflow geometry or the heat exchanger.

Repeat after hot soak

Bearings, winding insulation, semiconductor protection, and connector resistance can change when hot. Reproduce the original thermal condition and command the same steps. A fan that works cold but stops or limits speed hot needs its temperature, current, and supply history preserved before replacement.

Prove Useful Airflow After Speed Responds

Check rotation, blade pitch, and shroud position

A replacement motor can turn at the commanded RPM but move air in the wrong direction or at inadequate volume. Verify pusher or puller orientation, fan rotation, blade geometry, diameter, tip clearance, and shroud overlap. The motor versus complete fan assembly decision matters when blade and shroud matching cannot be separated from the motor.

Observe the protected system's response

At controlled fan steps, record radiator discharge temperature, coolant trend, and A/C pressure where relevant. Increased RPM without a meaningful airflow or temperature response points to blockage, recirculation, wrong blade load, or heat-transfer problems. Inspect the complete engine cooling system rather than raising command until the motor reaches a protection limit.

Do not judge airflow by sound

Blade noise rises with speed but is affected by geometry, turbulence, nearby panels, and damaged edges. Use airflow direction, pressure or velocity measurement where specified, and system temperature response. A loud but poorly shrouded fan can still recirculate hot air.

Fault Patterns and Replacement Scope

Distinguish an intentional after-run from a control fault

Some PWM fan systems continue operating after key-off to remove stored heat from the engine, turbocharger, refrigerant circuit, battery, or power electronics. Others should stop once the command and wake circuits are removed. Record command waveform, wake voltage, power-module state, temperatures, and the time until shutdown. The dedicated analysis of a radiator fan running after shutdown helps separate programmed after-run from a stuck relay or module.

Check for backfeed without disconnecting evidence too early

An aftermarket accessory, damaged diode, shared ignition feed, wet connector, or incorrect relay can keep a wake circuit alive. Measure voltage relative to the correct ground and determine whether the line can supply current, not just whether a high-impedance meter detects a ghost voltage. Removing fuses one at a time without a diagram can reset modules and erase the condition; isolate branches according to the circuit plan.

Account for module thermal derating

Integrated electronics may reduce motor current when the power stage becomes hot. A command can remain high while RPM falls gradually and recovers after cooling. Inspect airflow around the module, heat-sink contact, contamination, fan mechanical load, and supply voltage. Record module or housing temperature where a valid method exists. Thermal derating caused by excessive blade load should not be treated as proof of a defective control board.

Repeat the final test with covers and seals installed

A fan can pass with the hood open, splash panels removed, or an external workshop fan blowing across its electronics, then fail in normal packaging. Reassemble the airflow path and reproduce the original load safely. Compare command, supply, current, RPM, feedback, and protected-system response one final time before closing a warranty case.

Command and response pattern

Priority checks

Likely scope

No PWM at fan; valid output at controller

Harness continuity under load, short, terminals, ground reference

Circuit repair

Valid PWM; power or ground collapses

Fuse, relay, splice, connector, ground

Power-path repair before fan decision

Valid command and supply; no current

Wake circuit, module input, internal open, protection state

Fan/module after pinout proof

High current and low RPM

Blade contact, bearing, winding, wrong assembly

Motor or complete assembly

Correct RPM; incorrect feedback

Tach circuit, pull-up, sensor target, scaling

Feedback repair or integrated assembly

Correct command and RPM; poor cooling

Rotation, blade, shroud, stack, coolant flow

Airflow or heat-transfer repair

Fitment and Wholesale Matching

Collect electrical identity before comparing housings

Provide the OE number, vehicle, engine, build range, system voltage, connector face and wire-side photographs, terminal count and keying, PWM frequency and duty convention if available, feedback type, fan diameter, blade count, rotation, shroud dimensions, mounting points, current evidence, and quantity. An assembly that bolts in can still reject the vehicle's command or report the wrong feedback.

Clarify whether electronics are integrated

State whether the quotation includes motor only, motor and module, blade, shroud, wiring, or the complete unit. When electronics are integrated, replacing only the visible motor may not be possible or may leave the failed driver in service. A separate fan control unit must be matched by its own pinout and protocol.

Define sample checks that represent the real application

Receiving inspection should confirm connector keying, terminals, mounting geometry, blade and shroud condition, rotation, labels, and traceability. Functional approval should use the specified voltage, command frequency and polarity, multiple duty steps, current, independent RPM, feedback, hot operation, and airflow direction. A direct 12-volt spin test cannot validate PWM control.

Review Elecdura's aftermarket parts program, wholesale cooling fan range, and wholesale supply terms. Send the OE reference, application, connector photos, waveform and speed evidence, assembly scope, quantity, packaging needs, and destination through the contact page.

FAQ

Can I test a PWM fan by applying battery voltage?

Only if the exact design has an approved direct-power procedure

Many smart fans require constant power plus a separate command, and direct power on the wrong terminal can damage electronics. Confirm pinout, wake-up, signal type, and current limits first.

Why does the fan run at full speed when the PWM wire is disconnected?

The assembly may use a fail-safe default

Some fans select high speed when the control signal is missing; others stop. Verify the application strategy. A full-speed default can show that power electronics work, but it does not prove the command circuit or feedback is correct.

Does a 50% duty cycle mean half fan speed?

Not necessarily

Control polarity, reserved ranges, minimum speed, non-linear mapping, and soft-start logic affect the result. Build a measured command-to-RPM curve for the exact part number.

Why does scan data show fan speed when the fan is stopped?

Check feedback scaling, electrical noise, pull-up, and parameter definition

Compare with independent RPM and scope the feedback line. A frozen or calculated scan value is not proof that the motor turns.

Should I replace the motor or the full PWM fan assembly?

Follow serviceability and the location of the proven fault

If the module, feedback sensor, blade, or shroud is integrated or mismatched, the complete assembly may be the reliable scope. A motor-only replacement is appropriate only when it is serviceable and its electrical and mechanical specifications are confirmed.

Contact us
Wholesale Sourcing Enquiry
+86 18915027366
 Creative Industry Park , ChangZhou, China 213022

SYSTEM

MARKET

ABOUT US

SOCIAL MEDIA

COPYRIGHT © 2025 CHANGZHOU SKYFOUND ALL RIGHTS RESERVED.