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

Leading Automotive Parts 

Supply Chain Solution Provider

 WhatsApp
+86 18915027366
 Phone
+86 18915027366
Language
You are here: Home » Blog » Technical Guides » Condenser Fan Runs Continuously: Sensor, Relay, Module, or Failsafe Logic

Condenser Fan Runs Continuously: Sensor, Relay, Module, or Failsafe Logic

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

A condenser fan that runs continuously is not automatically caused by a stuck relay. The fan may be responding correctly to high refrigerant pressure, high coolant temperature, battery charging demand, an electric-vehicle thermal request, or a control-module failsafe strategy. It may also be powered by welded relay contacts, a shorted control wire, a failed module, or incorrect replacement wiring.

The diagnosis should separate command from power. First determine whether the control system wants the fan on; then prove whether the electrical output follows that command. Elecdura's condenser fan product range includes relay-controlled, module-controlled, single-speed, multi-speed, and integrated assemblies, so the correct test depends on the actual architecture.

Define Exactly When the Fan Keeps Running

Record whether the fan starts with key on, only after A/C request, during engine warm-up, after shutdown, or as soon as the battery is connected. Note fan speed, ambient temperature, coolant temperature, refrigerant pressure, A/C request, engine state, battery voltage, and stored faults.

Behavior

Possible normal or commanded cause

Possible electrical fault

First check

Runs only with A/C active

Condenser airflow request

Pressure input biased high

Gauge pressure versus scan data

Runs at maximum from key on

Failsafe for missing sensor data

Relay/module/control-wire fault

Codes and commanded fan percentage

Runs with key removed

After-run thermal strategy

Welded relay or powered module

Specified after-run time and relay output

Runs after engine starts cold

Defrost/A-C request or battery strategy

False temperature or pressure input

Inputs and HVAC request

Never changes speed

Single-speed design or failsafe

Failed control stage or feedback

Command sweep and motor response

“Continuous” should be timed. A manufacturer may intentionally run a fan for several minutes after shutdown to control underhood or battery temperature. A fault is suspected when operation exceeds the defined strategy or conflicts with commanded state.

Map the Fan-Control Architecture

Relay-controlled single-speed fan

A module energizes a relay coil; the relay contacts deliver battery power to the motor. Some circuits switch power, others switch ground. A stuck contact can power the motor with the coil inactive.

Separate coil control from contact output

Measure relay-coil command and motor-side output simultaneously. If the coil is off but output remains powered, inspect welded contacts, socket bridging, or a power-side short. If the coil remains commanded, trace the input logic.

Series-parallel or resistor-based multi-speed fan

Multiple relays may place two motors in series for low speed and parallel for high speed, or route current through a resistor. A stuck relay can create an unexpected speed rather than simple full-time operation. Use the exact relay-state table.

Electronic module or integrated fan

A fan control module may receive PWM, LIN, or another command and regulate motor current internally. Constant operation can result from a commanded failsafe, a shorted command line, lost communication, internal output failure, or incorrect module calibration.

Some vehicles use one radiator cooling fan assembly for both engine coolant and condenser airflow. Do not assume an A/C symptom means the fan is controlled only by refrigerant pressure.

Determine Whether the Module Is Commanding the Fan

Read requested and actual fan data

Use a capable scan tool to record fan request, desired speed, actual speed or feedback, A/C pressure, coolant temperature, intake or ambient temperature, vehicle speed, A/C request, battery-system status, and relevant inhibit or failsafe parameters.

A scan command is not the same as motor voltage

A displayed zero-percent command with a running fan points toward an output-stage, relay, wiring, or interpretation problem. A high command with a running fan may be correct even if the driver considers the operation excessive.

Use bidirectional control as an output test

Where supported, command several fan speeds and observe command signal, motor voltage or current, actual speed, and airflow. A fan that follows commands proves significant parts of the output path but does not prove that automatic inputs are accurate.

Elecdura's automotive technical guides emphasize comparing requested state, delivered electrical output, and physical result. This prevents a valid high command from being misdiagnosed as a stuck relay.

Check for Valid Refrigerant-Pressure Demand

Compare physical pressure with electronic pressure

Connect approved refrigerant equipment and follow safety procedures. Compare high-side gauge pressure with scan data or pressure-switch state at several operating points. If both show genuinely high pressure, the fan request may be correct.

Find the reason for real high pressure

Inspect condenser airflow, fin blockage, fan direction, shroud sealing, refrigerant charge, non-condensable gas, line or metering restriction, and heat load. Visible rotation does not prove adequate airflow.

Fan airflow should influence pressure

At low road speed, a correct increase in fan output should normally stabilize or reduce high-side pressure under comparable conditions. If pressure remains high, verify airflow direction, speed, and heat-exchanger condition before condemning the pressure input.

The A/C pressure switch or sensor can request fan operation directly or through software. Use the switch-versus-sensor test guide to select contact-state or signal testing.

Check for Failsafe Operation

Missing pressure data can command maximum fan

Many control strategies choose high fan speed when refrigerant pressure is missing or implausible. This protects the system when the module cannot determine heat-rejection demand. Look for pressure-sensor circuit codes, substituted values, and a fan request labeled failsafe or default.

Coolant and communication faults can do the same

A missing coolant-temperature signal, lost communication between modules, or a controller power/ground fault may command the fan as a protective response. Compare all thermal inputs, not only the A/C pressure parameter.

Default values may look plausible

A scan tool may display a substituted pressure or temperature rather than an obvious error. Unplugging a sensor and seeing the value remain stable can reveal substitution, but use the service procedure and interpret codes and parameter status.

An intermittent input can create intermittent failsafe operation. The intermittent pressure-device diagnosis shows how to capture reference, ground, signal, physical pressure, and module command on one timeline.

Test Relay-Controlled Circuits

Inspect command at the relay coil

Identify whether the module switches power or ground. Measure both coil terminals with the relay installed. A voltage reading on one side alone does not show whether current flows through the coil.

Remove or substitute the relay only as specified

If fan operation stops when the correct relay is removed, the power path runs through that relay, but the fault can still be coil command or welded contacts. Inspect contact output while the coil is unpowered. Use only a relay with verified terminal layout and rating for substitution.

Socket heat can bridge or distort terminals

Look for discoloration, spread terminals, melted plastic, corrosion, or previous bypass wiring. A replacement relay cannot repair a loose socket terminal. Measure loaded voltage drop and terminal grip.

The electrical method in Elecdura's radiator fan voltage-drop guide helps identify power and ground loss, while a continuously powered motor requires the same circuit to be evaluated for unintended voltage.

Test Electronic Fan Commands

Identify PWM, LIN, or other control

Use the wiring diagram and module information. PWM command requires duty-cycle, frequency, and voltage interpretation. LIN or another digital line requires protocol-aware equipment. A multimeter average can be misleading.

Capture command at both ends

Measure at the controller output and fan-module input when accessible. If the command is correct at the controller but corrupted at the fan, inspect the harness. If command is low but fan remains at high speed, investigate module failsafe behavior, communication, power, ground, and internal failure.

Do not ground or power an unknown command wire

A direct jumper can damage a module or communication transceiver. Use the approved simulator, breakout harness, or scan-tool command.

Separate Motor Operation from Adequate Airflow

Measure current and actual speed

A motor can run continuously at an incorrect speed because of a module fault, voltage loss, mechanical drag, or wrong replacement. Measure system voltage, motor current, actual speed where possible, and command.

Use the principles in the fan motor current-draw test. High current with low speed suggests drag or winding trouble; low current with low speed may reflect supply or control loss.

Inspect fan direction and shroud recirculation

Wrong polarity, incorrect blade, missing seals, or a distorted shroud can recirculate hot air. The controller may keep commanding the fan because pressure or coolant temperature never falls.

Continuous operation may be the consequence, not the cause

If measured temperature or pressure remains high despite correct command, solve heat rejection. Replacing a relay to stop the fan would remove protection and worsen the underlying condition.

Diagnose Key-Off Fan Operation

Compare run time with the specified after-run strategy

Some vehicles continue cooling after shutdown based on temperature, A/C pressure, turbocharger heat, battery condition, or charging events. Time operation and read module status. Do not disconnect the battery before preserving codes and commands.

Check retained power and wake-up causes

A module can remain awake because of network activity, a door or charging event, a stuck wake line, or an internal fault. Measure module power, ground, communication, and sleep current according to procedure.

Prove welded contacts

If a relay output remains connected with its coil unpowered and removed from control, the contacts may be welded. Inspect motor current and socket condition because overcurrent or heat can repeat the failure.

Use a Decision Table

Fan command

Fan power/output

Physical inputs

Diagnosis direction

High

Fan follows

Pressure/temperature genuinely high

Valid demand; diagnose heat rejection or system load

High/failsafe

Fan follows

Input missing or implausible

Sensor, reference, wiring, or communication

Zero

Fan powered

Inputs normal

Welded relay, shorted control, or module output

Variable

Fan fixed high

Inputs follow demand

Command line, module failsafe, calibration, or feedback

High

Fan slow or airflow weak

Pressure remains high

Voltage loss, motor, blade, direction, or shroud

Replacement Matching

Motor and assembly data

  • Vehicle, model year, market, engine or powertrain, and HVAC option

  • OE number from motor, shroud, module, and complete assembly

  • System voltage, motor count, speed architecture, and control protocol

  • Connector pinout, terminal size, keying, latch, and wire gauge

  • Blade diameter, count, pitch, rotation, motor position, and shroud dimensions

  • Mounting holes, seals, brackets, sensors, and included hardware

Control data

  • Relay logic, series-parallel arrangement, resistor, PWM, or digital control

  • Command frequency, duty interpretation, feedback, and failsafe behavior

  • Measured current, speed, voltage, airflow, and fault condition

  • Whether module calibration is separate or integrated with the motor

Elecdura's aftermarket replacement program compares the complete fan and control configuration. A motor that bolts into the shroud can still be wrong if rotation, blade, connector, current, or command strategy differs.

Wholesale Quality Validation

Test commanded response across the range

For single-speed assemblies, verify start, current, speed, airflow, and relay-contact temperature. For variable-speed products, sweep the command, record actual speed and current, verify feedback, and test loss-of-signal behavior. Failsafe operation should match the approved specification.

Validate mechanical airflow

Check blade rotation, balance, clearance, shroud sealing, mounting, connector temperature, and airflow direction. A powered spin test without the intended shroud cannot confirm heat-exchanger airflow.

Packaging protects alignment and electronics

Support rigid shroud features, isolate blade tips and motor shaft, protect module connectors, and prevent loose hardware from striking the assembly. Control electrostatic and moisture exposure where required.

For wholesale cooling fan orders, approve a golden sample with electrical, control, airflow, and dimensional records. On-highway vehicles and off-highway applications can require different duty, sealing, dust, vibration, and after-run validation.

Common Diagnostic Errors

Replacing the relay without checking command

A continuously energized coil can make a healthy relay appear stuck. Measure coil control and contact output separately.

Assuming maximum fan speed means a failed module

High speed may be an intentional failsafe for missing pressure, temperature, or communication data. Check inputs and codes.

Trusting scan pressure without a gauge

A biased sensor can create a valid-looking high value. Compare electronic data with physical pressure at multiple points.

Ignoring real heat load

Blocked fins, recirculation, wrong blade direction, overcharge, or restriction can demand continuous fan operation. Verify physical response.

Installing a universal fan controller

Different command frequency, polarity, feedback, current, and failsafe logic can make a visually compatible controller operate incorrectly.

FAQ

Is it normal for the condenser fan to run whenever A/C is on?

Many systems request fan operation with A/C, but speed and timing vary with pressure, temperature, vehicle speed, and strategy. Compare operation with service information and live command.

Why does the fan run at full speed when the engine is cold?

A defrost A/C request or failsafe for missing pressure, coolant-temperature, or communication data can command high speed. Check codes and inputs.

Can a bad AC pressure sensor make the fan run continuously?

Yes. A high-biased, missing, or implausible signal may request airflow or trigger failsafe. Confirm with gauge pressure, reference, ground, and signal.

How can I tell if the relay is welded?

Verify the relay coil is unpowered, then check whether the contact output remains connected or powered. Inspect socket heat and motor current before replacement.

Why does the fan keep running after key-off?

It may be a timed after-run strategy or a retained-power, wake-up, relay, wiring, or module fault. Time the event and read command and sleep-state data.

What should a buyer submit?

Send the OE number, application, fan and shroud photos, connector and pinout, control type, command data, voltage, current, rotation, blade and mounting dimensions, required quantity, and validation needs through Elecdura's technical matching contact page.

Post-Repair Verification Sequence

Begin with a true cold start

Allow coolant, refrigerant, modules, and underhood components to return to the condition associated with the original complaint. Record key-on fan command before starting the engine. Confirm that default or failsafe operation is absent and that pressure and temperature inputs are physically plausible.

Apply A/C demand in controlled steps

Engage the system at idle, then observe pressure, fan request, delivered fan speed, motor current, and airflow as heat load develops. If the vehicle uses staged or variable speed, verify each accessible region rather than checking only maximum output.

Confirm that the replacement motor matches the command

A substitute radiator or condenser fan motor may rotate yet draw the wrong current, use the wrong direction, or deliver the wrong speed. Compare actual response with the approved assembly and control specification.

Verify recovery and key-off behavior

Remove A/C demand and observe whether pressure and fan command fall in the expected sequence. Shut down the vehicle and time any after-run operation. Confirm that the fan stops when the strategy ends and that module sleep current returns to specification.

Repeat the condition that originally produced continuous operation, including heat soak, ambient load, or harness movement. A repair is proven only when the command, electrical output, and physical temperature or pressure response agree throughout the entire cycle.

Prove Command Before Replacing the Output

A condenser fan that runs continuously must be separated into input demand, controller decision, electrical output, and physical airflow. If the module is commanding the fan because pressure or temperature is truly high, the fan is performing a necessary function. If command is absent but power remains, the output circuit becomes the focus.

Capture pressure, temperature, command, voltage, current, speed, and airflow on one timeline. After repair, repeat cold start, A/C demand, fan-speed sweep, heat soak, and key-off operation so the original condition is proven absent without disabling protective control.

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.