The Air-Cooled Chiller Fault Codes That Actually Matter: Reading Alarms Before They Trip You

Let me tell you what this article is not. It is not a lookup table of “Error 71 means X on a Carrier, Diagnostic 198 means Y on a Trane.” Those codes are manufacturer-specific, they change between controller generations, and the only correct source for yours is the service manual for your exact model. Anyone publishing a universal chiller fault-code table is guessing, and following it will send you down the wrong path.

What every air-cooled chiller controller shares — Carrier, Trane, York, Daikin, Multistack, the lot — is a much smaller set of things it is actually protecting against. There are only so many ways a vapour-compression machine can hurt itself. Once you understand those handful of protection categories and, crucially, what physical condition sits behind each one, you can read any chiller’s alarms, whatever the brand and whatever numbers it puts on the screen.

And the real skill, the one in the title, is catching the condition while it is still a warning — a value drifting toward a limit — rather than after it has become a lockout that shuts your building down at 2pm on the hottest day of the year.

Safety note. This is about interpreting what the controller tells you and understanding the physics. Any actual intervention on the refrigerant circuit or electrical system is work for a competent, qualified technician. If you are reading this to decide whether to call one, the answer is usually yes.

Alarm versus fault: the distinction that changes everything

An alarm is the controller’s response. A fault is the physical condition that caused it. They are not the same thing, and confusing them is why so much chiller troubleshooting chases its own tail.

“High pressure trip” is an alarm. It tells you the controller saw discharge pressure hit a limit and shut the machine down to protect it. It does not tell you why the pressure was high — that could be a dirty condenser coil, a failed condenser fan, an overcharge, non-condensable gas in the system, or recirculating hot air. The alarm is the same; the fault behind it is one of five different things needing five different responses.

So the useful question is never “what does this code mean.” It is “what physical condition is the controller protecting against, and which of the possible causes is it this time.” The code points you at the category. Your gauges, sensors and eyes find the cause within it.

The two-tier logic every controller uses

Modern chiller controllers almost universally work in two tiers, and understanding this is what lets you get ahead of a trip.

Warnings and limit modes come first. Before it shuts anything down, a good controller tries to avoid the trip. As a value approaches a limit, it takes protective action short of stopping: it unloads the compressor, stages on more condenser fans, or limits how much the machine can load up. You will see this as a “limit” or “override” or “prevention” status — the chiller is running, but not freely. This is the machine quietly telling you something is wrong while still doing its job.

Trips and lockouts come second. If the condition crosses the hard limit anyway, the controller trips to protect the equipment. Some faults auto-reset after a delay; others latch into a manual lockout that requires someone to physically acknowledge and reset it, precisely because they indicate something that should not be ignored.

The entire art of staying ahead of chiller failures lives in tier one. A machine that is spending hours a day in a “high pressure limit” mode has not tripped — so nobody gets a phone call — but it is running inefficiently, working its compressor hard, and sitting one hot afternoon away from a lockout. If your controller or BMS can log limit modes, those logs are the most valuable predictive data the chiller produces, and almost nobody reads them.

The protection categories that actually matter

Here are the ones worth understanding on any air-cooled chiller, what each is really about, and how to catch it early.

High discharge pressure

What it protects against: the high side of the system reaching a pressure that could rupture something or destroy the compressor. Cutout settings depend on refrigerant. Per AHRI 540, the high-pressure cutout is typically set around 85% of the refrigerant’s critical pressure — for R-134a that works out to roughly 488 psig, and one common air-cooled chiller line trips its switch at 405 psig. Your machine’s figure is on its data plate and in its manual.

On an air-cooled chiller in Malaysia this is the alarm you will meet most, because everything about high discharge pressure is made worse by heat. The causes, in rough order of how often we see them:

• Dirty or blocked condenser coil — the single most common, and entirely preventable
• Failed or wrong-rotation condenser fan
• Hot air recirculation around the unit — discharge air being pulled back into the intake
• Refrigerant overcharge
• Non-condensable gases (air) in the system, often after a poor repair
• High ambient simply exceeding the design condition

Catching it early: watch the gap between saturated condensing temperature and the ambient air entering the coil. On a healthy air-cooled machine that difference sits in a fairly consistent band. When it starts widening at the same ambient, the coil is fouling or airflow is dropping — weeks before it trips. This is the number to trend.

Low evaporator pressure / low refrigerant temperature

What it protects against: the evaporator getting cold enough to freeze the water inside it and split the tubes. A frozen evaporator is one of the most expensive things that can happen to a chiller.

Low-pressure cutout settings are refrigerant-specific — recommended minimums cited by one major compressor maker are around 55 psig for R-410A, 25 psig for R-22 and R-407C, and about 10 psig for R-134a — with a separate leaving-water temperature freeze limit on top.

Causes: low refrigerant charge, reduced or lost chilled water flow, a fouled evaporator, a failing expansion valve, or an excessively low leaving-water setpoint. Note that loss of water flow shows up here as well as on the flow switch — the water stops carrying heat in, the refrigerant temperature collapses, and the machine trips on low pressure or freeze protection.

Catching it early: a low-pressure trip that only happens at high load usually points at charge or flow. One that drifts down over weeks points at a slow refrigerant leak or a progressively fouling evaporator. Trend suction pressure at a fixed load.

Loss of water flow

What it protects against: running the compressor with insufficient or no water through the evaporator, which leads straight to a frozen, split evaporator. This is why the flow switch and the anti-freeze logic exist, and why you must never bypass a flow switch to get a machine running.

Causes: a closed or throttled valve, a failed or air-locked pump, a blocked strainer, a stuck or faulty flow switch itself. On a new install or after any pipework change, a closed isolation valve someone forgot is a classic.

Catching it early: trend the chilled water pressure drop across the evaporator, and keep strainers clean. A slowly rising strainer pressure drop is loss of flow arriving in slow motion.

Compressor short cycling and anti-recycle lockout

What it protects against: starting the compressor too often. Every start is electrically and mechanically stressful, and starts generate heat in the motor windings that needs time to dissipate. So controllers enforce a minimum time between starts.

The numbers are real and worth knowing. Guidance for small scroll compressors is often a maximum of around 10 to 12 starts per hour, which translates to a minimum of roughly five minutes from one start to the next. Larger machines can be far stricter: some screw chillers enforce a 30-minute start-to-start interval, partly to let the motor windings shed heat. Many controllers manage this with a “bucket” or credit system that allows a couple of free starts and then progressively enforces longer waits.

Here is the diagnostic gold in this one. If your chiller is repeatedly hitting its anti-recycle timer, the timer is not the problem — it is the symptom. Something is making the machine cycle too often, and it is almost always one of:

• Oversizing — the chiller satisfies the load too fast, shuts off, coasts, and restarts. The most common cause, and one you cannot fix in the controller.
• Low load — the building is asking for far less than the smallest step the chiller can make.
• Low water volume in the loop — too little water means temperature swings fast, so the chiller cycles chasing it. Often solved with a buffer tank, not a new chiller.
• A hunting setpoint or too-tight control band.

A machine that trips on anti-recycle lockout is telling you it is fundamentally mismatched to its load or its loop, which is worth far more to know than the lockout itself.

Motor and electrical protection

What it protects against: the compressor motor overheating or being damaged by bad power. This bundles several distinct alarms — motor overload, high motor temperature, phase loss, phase imbalance, phase reversal, under/over voltage.

Causes and why Malaysia matters here: phase reversal after any electrical work will spin a scroll backwards and damage it, so a phase-reversal alarm on a first start after maintenance is doing its job — do not defeat it, correct the phase sequence. Voltage and phase-imbalance issues track directly to supply quality, and in industrial estates and coastal sites, corroded terminations create the resistance and imbalance that trip these alarms. High motor temperature on a suction-cooled machine often traces back to high superheat or low charge — the return gas that cools the motor is arriving too hot.

Catching it early: log the three phase currents and the supply voltage balance periodically. Imbalance rarely appears overnight; it creeps.

High discharge temperature

What it protects against: cooking the compressor and breaking down its oil. Covered in depth in our compressor diagnosis article, but as an alarm category: field limits sit around 107°C for semi-hermetic compressors and up to roughly 127°C for some scrolls, and the discharge valve runs much hotter than the line. POE oil starts losing lubricity around 149°C.

Causes: high compression ratio, low suction pressure, high condensing pressure, high superheat — which means this alarm frequently rides in alongside a high-pressure or low-charge condition rather than alone.

Oil-related alarms (screw and some scroll machines)

What it protects against: running without adequate lubrication. On screw chillers especially, oil pressure or oil-flow alarms guard the bearings directly.

Causes: genuine low oil, oil logging in the system, a failing oil pump, refrigerant flooding diluting the oil, or a sensor fault. A “low oil flow at start” alarm often points at liquid refrigerant migrating to the compressor during the off cycle — which loops back to crankcase heater health and off-cycle migration.

Sensor and communication faults

What it protects against: acting on bad data. A failed thermistor, pressure transducer, or a lost communication link between modules will throw its own alarm.

Why it matters: a sensor fault can masquerade as a process fault. A drifting condenser pressure transducer can trip a high-pressure alarm on a perfectly healthy high side. Before chasing a refrigerant-side cause, it is always worth confirming the sensor reading against an independent gauge. Manufacturers’ own troubleshooting explicitly includes “verify the sensors are working correctly” as a first step on pressure trips, for exactly this reason.

Reading the pattern, not the code

Because alarms travel together, the combination tells you the fault faster than any single code.

The habit worth building: when an alarm appears, note every other value at that moment — both pressures, both saturated temperatures, discharge temperature, ambient, water flow, all three phase currents. That snapshot diagnoses the fault. The code alone rarely does.

Why this bites harder on Malaysian air-cooled chillers

High-pressure protection is your constant companion. An air-cooled machine rejecting heat into 33–35°C air all year has almost no headroom above its design condensing condition. A coil that is only slightly fouled, or one fan that has quietly failed, is enough to push it into high-pressure limit mode on a hot afternoon. In a temperate climate the same fault might never trip. Here, condenser cleanliness is not housekeeping — it is the difference between running and locked out.

Rooftop clustering causes phantom high-pressure trips. Where units are packed together on a roof, hot discharge air recirculates into intakes. The controller reads high condensing pressure and trips, the coil is clean, the fans work, and everyone is baffled — because the fault is siting, not the machine. Check inlet air temperature against genuine ambient before condemning anything.

Afternoon nuisance tripping is a signature. A chiller that runs all morning and trips on high pressure in the mid-afternoon heat, then resets and runs again, is not a mystery — it is a machine running too close to its condensing limit, being tipped over by peak ambient. It is telling you the high side has no margin, and the fix is on the condenser, not the reset button.

Coastal supply-quality issues trip motor protection. Salt-laden air corrodes electrical terminations at Port Klang, Prai, Pasir Gudang and similar sites, producing the resistance and imbalance that motor-protection alarms catch. Treat a recurring phase-imbalance alarm as a terminal-condition inspection, not just a supply complaint.

The reset-button trap. Because tripping so often traces to heat, and because the machine usually restarts once it cools, there is a strong temptation to just keep resetting. Every reset on an unaddressed fault is running the machine hard against its protection limits and shortening its life. A chiller that needs resetting regularly has a fault that has not been fixed — the alarm is working; the response to it is not.

What to actually do with this

1. Get the service manual for your exact chiller model and find its alarm list and protection setpoints. That is your real code table. Keep it with the machine.
2. Log limit and warning modes, not just trips. If your controller or BMS supports it, this is your early-warning system. A machine spending time in high-pressure limit is a trip waiting for a hot day.
3. Trend four things monthly: condenser approach (saturated condensing minus ambient), suction pressure at a fixed load, evaporator water pressure drop, and the three phase currents. Most alarms announce themselves in these numbers before they trip.
4. When an alarm fires, capture the whole snapshot before resetting. The surrounding values are the diagnosis.
5. Never bypass flow switches, freeze protection, or phase-reversal protection to force a machine to run. These guard against the failures that write off chillers.
6. Treat repeated resets as an open fault, not a solution.

The short version

Forget memorising codes. Every air-cooled chiller protects against the same handful of things: high side pressure, low side freezing, loss of flow, too-frequent starts, bad power, an overheating compressor, and lost lubrication. The controller warns before it trips — and in a Malaysian climate, where the high side has almost no thermal headroom, those warnings arrive early and often if anyone is watching.

Learn the categories, trend the four numbers, read the warning modes, and capture the full picture when something fires. Do that and you will be fixing conditions on a Tuesday morning that would otherwise have locked your building out on a Saturday afternoon.