Fan Temperature Map: Control Logic and Validation

A fan temperature map is part of the logic that requests radiator-fan operation. Depending on the system, the request may select relay stages, a variable-speed command or a message to another controller. Correct calibration starts with the wiring and control architecture, not a universal temperature or PWM frequency.

Fan temperature map: identify the control architecture

Establish which controller requests fan operation, which device supplies motor power and which inputs influence the request. A temperature threshold in the engine ECU may be only one of several contributors. Air-conditioning demand, pressure, vehicle speed, fault responses and post-shutdown cooling can also matter.

Relay-driven fans, motors controlled by external power electronics and fans with integrated electronics require different output arrangements. Wire count alone does not determine whether variable-speed operation is supported. Never assume an ECU signal output can directly carry motor current.

Use the wiring diagram and component specifications to establish polarity, current handling, control-signal format and failure behavior. A PWM setting cannot turn an incompatible relay circuit into a supported variable-speed controller.

Verify temperature measurement before changing thresholds

Compare the logged coolant temperature with the diagnostic procedure for the installed sensor and circuit. Check wiring, connector condition and plausibility across operating states. A calibration table does not physically drift; sensor or circuit behavior may change, or an incorrect conversion may have been entered.

Use the correct temperature units and map definition. If an editor exposes a raw value, confirm its conversion rather than assuming that it directly represents sensor voltage. Changing the sensor transfer function to make the fan start earlier also changes the temperature understood by other ECU functions.

Assess coolant level, circulation, thermostat operation, radiator condition and airflow when temperature is abnormal. Earlier fan engagement cannot repair a restriction, circulation fault or inadequate heat rejection.

Understand thresholds, hysteresis and other requests

Hysteresis separates the conditions for switching on and off, reducing repeated transitions near a threshold. Its representation and interaction with delays differ between strategies. Multiple stages may be independent, mutually exclusive or permitted together.

MaxxECU’s radiator-fan documentation gives a concrete example with start temperatures, hysteresis, vehicle-speed conditions and AC requests. Its example settings apply to that implementation; they are not standard values for every engine.

If a fan remains on, inspect all active requests before changing the main threshold. A fault response, AC demand or after-run function may explain the command. If the command is off but the motor continues to run, investigate the output stage or wiring.

Use the controller specification for PWM

On a supported variable-speed system, verify frequency, polarity, duty limits, start requirements and the response to a lost signal. Some controllers interpret the signal as a requested speed rather than direct motor-power duty. A higher frequency is not automatically better.

The Analog Devices article linked below discusses cooling electronic equipment. Its circuit examples should not be transferred into an automotive fan controller without matching specifications. MaxxECU likewise exposes configurable frequency and duty behavior rather than one universal automotive setting.

Keep power PWM and a low-current command signal distinct when testing. Confirm the relevant electrical behavior with the component’s diagnostic procedure; do not use an AC-signal emulator as a generic repair for a fan fault.

Verify thermal behavior and commanded response

Define the intended operating range from the engine and cooling-system specifications. Log coolant temperature, fan request, available actual fan response, engine speed, vehicle speed and relevant AC or fault states. Include warm-up, hot idle and representative load where appropriate.

Check that the command changes under the documented conditions.
Confirm the physical fan response and correct airflow direction.
Review transitions for excessive cycling or unexpected overrides.
Check supported shutdown behavior and electrical demand.

Choose test duration and acceptance criteria for the installation. There is no universal safe low/high temperature pair or hysteresis width. A satisfactory idle test does not validate sustained-load cooling, and changing the fan map alone does not establish total system capacity.

Perguntas frequentes

Should every fan use PWM above 20 kHz?

No. Frequency and signal type must match the fan controller or power stage. Guidance for electronics-cooling fans is not a universal automotive specification.

Does a two-wire motor rule out variable-speed control?

Not necessarily. A compatible external power controller may regulate it. The complete hardware arrangement determines what is supported.

Why can the fan stay on below its temperature threshold?

Another request, a fault response or after-run logic may be active. Compare the requested state with the physical response before changing calibration.

References and further reading

Manufacturer documentation applies to the named product, firmware and application. General articles and forum discussions are background reading, not universal settings or proof of compatibility.