The Difference Between a Fault Code and a Warning Code

Why this matters

Not every code on a display means the system is broken right now. Some mean it already stopped; some mean it is still running but heading somewhere bad; some are just information. Treat all three the same and you either scare a customer over a code that was never urgent, or worse, walk away from one that was. Knowing which category you are looking at changes both your next move and what you tell the customer standing next to you.

The three categories

• Fault codes mean the system has stopped, or a safety interlock has locked it out, because a measured condition crossed a hard limit. The equipment will not run again until the fault is addressed and, on many boards, manually or automatically reset. This is the category that demands diagnosis before restart.
• Warning codes mean the system is still running, but a condition is trending toward a limit or has crossed a soft threshold that does not by itself justify shutting down. A warning is an early flag, not a stop sign. Ignore enough warnings and many of them mature into a fault later, but a warning code today is rarely an urgent shutdown call by itself. The exception: a warning tied to a safety-relevant reading (a slowly rising temperature near a limit, a slow refrigerant or pressure loss, an early ground-fault indication) should be treated with the same urgency as a fault, because the "soft" threshold exists precisely to catch a hazard before it becomes a hard stop.
• Informational or status codes are not problems at all: mode indicators, maintenance reminders, cycle counters. They tell you what the system is doing or when it wants service, not that anything is wrong.

How to tell which one you're looking at

The board's own behavior is the first clue: did the system actually stop running, or is it still operating? A code paired with the equipment being dead is almost always a fault. A code that appears while the system keeps running is almost always a warning or status message.

The second clue is the documentation's own language, when you have it. Manufacturers usually separate their code sheets into fault tables and warning or advisory tables. Do not assume; check which table the specific code lives in, because code numbering is not consistent between categories or between equipment lines.

The third clue, when documentation is thin, is the nature of what triggered it. A code tied to a hard safety limit (a pressure or temperature ceiling meant to prevent damage or injury) behaves like a fault even if the equipment technically kept running for a moment before shutting down. A code tied to a maintenance interval or an efficiency threshold behaves like a warning.

What changes based on the category

The mistake in both directions

Treating a warning like a fault wastes the customer's time and your credibility: you cannot justify an emergency call-out for a maintenance reminder. Treating a fault-adjacent warning like a routine status message is the more expensive mistake, because it leaves a real, developing problem running unattended until it becomes a shutdown, a leak, or worse. When you are not sure which bucket a code belongs in, default to treating it one level more seriously than you're tempted to, and confirm with documentation before you tell the customer to ignore it.

Document the category, not just the number

When you log a service visit, note whether the code was a fault, a warning, or informational, along with what you did about it. A history of repeated warnings with "monitored, no action" notes is exactly the trail that lets the next tech, or you in six months, connect a slow-building problem before it becomes an emergency call.

References

• Manufacturer documentation on fault vs. warning code tables and reset procedures
• Trade-standard practice for safety-interlock threshold design
• See related: Reading an Error Code, the Discipline Not the Lookup; The Error Code That Means Five Different Things