Why Is My Aircon Fan Speed Not Changing?

The remote control sends an IR signal to the indoor unit's receiver each time a fan speed command is issued. If the IR receiver is dirty, misaligned, or has developed a fault, it may not detect the command — but the remote display still shows the new speed setting because the remote only updates its own screen; it has no feedback from the indoor unit. This creates a confusing situation where the remote clearly shows speed 3, but the unit is still running at speed 1. The homeowner concludes something is broken, when the break point is simply the receiving end of the IR path.

A blocked or faulty IR receiver is one of the most common command path failures and one of the cheapest to resolve — yet it is frequently skipped in favour of diagnosing the PCB or fan motor. The receiver is a small component on the indoor front panel, and it can be affected by dust accumulation, a piece of filter lint sitting in front of it, or physical damage from an aggressive clean. Testing whether other commands — mode, temperature, swing — also fail to register confirms whether the issue is the speed command specifically or the entire command path. If all commands are intermittent, the receiver or its connection to the board is the fault, not the fan motor.

• –Other commands may also feel delayed or ignored.
• –No audible change happens after a fan speed command.
• –Airflow stays the same across repeated command attempts.

The diagnostic clue here is that other commands also fail to register, not just the fan speed change — mode switches, temperature adjustments, and swing commands are equally inconsistent or ignored. This separates it from mode-limited behavior, where the unit is correctly processing commands but responding within the constraints of its operating mode. Unlike a fan control fault, the display still changes on the remote side, but there is no corresponding reaction from the indoor unit to any IR command, pointing to the receiver or its wiring rather than the fan motor circuit. We test the IR receiver response and check whether the indoor PCB registers the command before moving to fan motor or board fault assumptions. Replacing the fan motor too early misses simple command path issues like a blocked IR sensor or faulty receiver.

Inverter units do not hold fan speed at one fixed level all the time. When the room is close to setpoint, the board may trim fan output even if you select high speed.

That means the unit may accept the command, but the airflow change feels small because cooling demand is already low.

The same pattern appears in dry and auto modes. Dry mode usually slows the fan to improve moisture removal, while auto mode lets the unit choose speed for you.

If the user expects the same response in every mode, normal control logic can look like a fault. Check the active mode and the model's speed rules before assuming the fan function is broken.

• –The issue appears only in certain modes or room conditions.
• –Cooling remains stable but airflow difference is hard to notice.
• –The pattern changes when the room load changes.

The pattern here is mode-specific or load-specific — fan speed appears fixed only when the unit is in a particular mode (dry, auto) or when the room is close to the setpoint temperature. Unlike a command path fault, all other commands work normally and the remote consistently produces a beep acknowledgement. Unlike a fan control fault, airflow does change when conditions change; the user simply cannot override it manually because the inverter algorithm or mode logic is controlling the output rather than the manual speed setting. We compare fan speed readings in each mode against actual airflow output to confirm the unit is responding normally for that condition. Normal mode behavior is often mistaken for a PCB fault.

The indoor fan motor on a split-system aircon is typically a DC brushless motor controlled by a signal from the indoor PCB that varies the motor's supply voltage or PWM duty cycle to achieve different speeds. If the PCB's fan output circuit fails — through a degraded driver transistor, a failed hall sensor in the motor, or a loose motor connector — the fan may run at only one speed regardless of what the remote commands. The user sees the display change correctly, hears the usual acknowledgment beep, but the airflow and motor sound stay constant.

The diagnostic trap here is attributing fixed-speed fan behavior to a completely failed PCB. The fan motor drive circuit is one output path on the board; the rest of the board — the compressor control, the louver motor, the display, the command reception — may all be working correctly. Replacing the full board for a fault that may be isolated to the fan drive stage, or even to the motor's internal hall sensor, is an avoidable overreach. Measuring the PCB's output signal to the fan motor under live conditions, and comparing it against expected values for each speed setting, separates a board-side fault from a motor-side fault before any parts are ordered.

• –Airflow response is inconsistent or suddenly drops while commands stay the same.
• –Indoor sound pattern changes without matching the selected fan speed.
• –The issue appears with other indoor control problems or noise.

The distinguishing sign here is that the fan locks to a single speed regardless of mode or room conditions — unlike mode-limited behavior, the issue is not tied to the operating mode or load. Unlike a command path fault, the indoor PCB correctly acknowledges speed commands with a beep and display change, but the airflow does not follow. Listen for a consistent motor sound that does not shift when speed commands are sent; a fan that sounds identical on speed 1 and speed 3 confirms the drive circuit or motor hall sensor is the fault, not the command path. Stop repeated command testing and let us assess fan motor current draw and indoor PCB output together. Long repeated testing hides the real pattern when the fault is intermittent.