What an error code is, and is not
An error code is the boiler control's report of a condition it detected, phrased in whatever language the controller speaks. It is not a diagnosis, and the difference matters every time a code appears. A lockout saying the burner did not prove a flame, for example, does not say why: the gas supply, the ignition components, the grounding, the venting and the control module each have to be tested on site. The same logic runs through nearly every family of codes, overheat, low water pressure, vent faults, sensor faults: the code names the protection that tripped, and the cause is confirmed by a technician's measurements, not by the display.
That is why the most useful thing a homeowner can do with a code is also the simplest: write it down exactly as displayed, note what the boiler was doing when it appeared, and report both to the technician. Truncated or paraphrased codes, and the lost context around them, are the small errors that turn a straightforward diagnosis into a second visit.
The display languages on today's boilers
Manufacturers phrase their codes differently, and the format is tied to the controller, not to the brand's marketing. IBC's SL Series G3 and VX boilers run the V-10 touchscreen controller, which shows descriptive text alerts, such as an ignition message identifying the condition by name, rather than numeric codes; IBC's SFC combi and SFT tankless appliances use a numeric-display control that prints F-numbered fault codes instead. Navien's NCB, NFB, NFC and NHB appliances display E-codes such as E001 on the front panel. NTI's FTVN and TRX controllers print grouped codes in which a leading group and a following number, such as 1 01, separate the fault family from the specific fault, while its TFTN manual tables print longer forms such as 101 1. Viessmann's Vitodens controls print F.x fault codes such as F.5, with the number after the dot identifying the specific fault within the fault family.
The table below summarizes the formats documented on this site, where each brand's error-code index records codes exactly as the manual tables print them, tied to the specific controller and manual version. Those details are not decoration: the same display can carry different meanings across controller generations, which is why every code on this site is recorded with the scope, the controller and the manual that documents it.
| Brand and product family | Controller / display | Format | Example from the site's code index |
|---|---|---|---|
| IBC SL Series G3, VX | V-10 touchscreen | Text alerts, no numeric code | Error – Ignition trials exceeded |
| IBC SFC combi, SFT tankless | Numeric-display control | F-numbered codes | F000 (heat exchanger sensor fault) |
| Navien NCB, NFB, NFC, NHB | Front-panel display | E-codes | E001 (heat exchanger overheat) |
| NTI FTVN, TRX | Front-panel display | Grouped codes | 1 01 (over-temperature or sensor safety test) |
| NTI TFTN | Front-panel display | Grouped codes, longer form | 101 1 (overheat) |
| Viessmann Vitodens 100-W, 200-W | Display with fault history | F.x fault codes | F.5 (sensor lead break or short circuit) |
What the format tells you before the lookup
The format itself carries meaning. A descriptive text alert tells you the condition in words and still needs the manual's procedure to resolve. A numeric code tells you nothing until it is looked up in the right table, which is why the controller and manual version matter so much. A grouped code is a small taxonomy: the leading group often places the fault in a family, such as water temperature and flow, sensors, or the gas train, so two codes sharing a group are likely to share a diagnosis path even when their members differ. A dot-delimited code such as Viessmann's F.x is the same idea: the family before the dot and the specific member after it.
The formats also differ in how they treat warnings versus lockouts. Some controllers display informational and maintenance messages, which leave the boiler running or limit it gently, while others reserve codes for blocking conditions that stop the appliance until reset or repaired. The manual tables classify each code, and the severity classification is part of what the code index on this site records for each documented code, because 'the boiler stopped' and 'the boiler is asking for a service' deserve different responses even when both appear on the same display.
Same code, different boiler: match the controller and manual
Code numbers are not standardized across the industry, and they are not even consistent within one brand across controller generations. A code that means one thing on a current controller can mean something else on an earlier one, which is why any lookup has to start from the exact appliance: its brand, its series and the controller it actually carries. The error-code scope rules used on this site exist for exactly this reason: each code record names the series and controller it applies to, and identical numbers with different meanings are kept as separate records rather than merged.
The manuals themselves make the same point. IBC's SL G3 installation manual documents the V-10 text alerts in its error sections, and the model's own documentation notes that earlier SL boilers with different controllers may display different wording for the same condition. Navien's NCB-H manual, NTI's FTVN and TFTN manuals and Viessmann's Vitodens service instructions each contain the lookup tables for their own controllers, and those manuals are the authority for the codes recorded on this site, cited on every code page.
A code read correctly: a worked example
Take a display showing E003. The first step is to match it to the appliance, not to the brand name: the Navien NCB-H manual is the authority for that controller. Its fault table describes E003 as an ignition failure, shown after the boiler attempts ignition ten times without detecting a flame, and cleared manually. From that one line a homeowner learns three things without opening anything: the boiler is failing to light rather than overheating or losing pressure, the control has already tried a set number of times and given up, and a manual reset, not repeated power cycling, is what clears it.
The same entry also shows what the code cannot say. 'No flame detected' does not identify the cause; the manual's own troubleshooting points to the gas supply, the igniter electrode, the flame rod and the gas control valve, and only a technician's measurements separate those. Compare it with E012 on the same appliance, documented as flame loss during combustion after twenty consecutive losses. E003 and E012 sit one step apart in the same sequence, yet they point at different checks, which is exactly why a code must be read from the manufacturer's table rather than from memory or a forum post.
Warnings, blocks and lockouts: the words controls use
Manufacturer manuals describe faults with a small vocabulary worth knowing. A warning or maintenance message is information the control passes to the owner while the appliance keeps running. A blocking condition holds off the current demand but can clear itself, or be cleared by a change in conditions, such as a sensor reading returning to range. A lockout is firmer: the control has stopped the appliance and will not restart until it is reset or the fault is corrected, and some controls extend the wait after each attempt. A safety lockout is reserved for the conditions that protect against unsafe combustion or operation, and those manuals direct the reader to a qualified technician.
Knowing which word applies changes the response. A blocked boiler may be waiting for a condition a technician can name; a locked-out boiler is telling you the control already refused to continue. Either way the path is the same: note the exact wording, check the safe items, and have a licensed technician read the manual's procedure against the appliance's actual measurements rather than against the message alone.
Codes that need action now versus codes to book
Codes are not all equal, and the code index on this site records a severity for each documented code so the response matches the condition. An informational or maintenance message may leave the boiler running and simply ask for a service visit. An attention code may pause or limit the appliance until conditions change. A lockout code stops the boiler until it is reset or repaired, and a code that returns after every reset is a service matter rather than a resetting exercise. A safety code, or any message that travels with a gas smell or a carbon-monoxide alarm, is not a code question at all: leave the building and call from outside first.
The reason severity matters is that the same display carries messages from different levels. Treating every code as an emergency wastes a technician's time and a homeowner's money, while treating a lockout as a nuisance by clearing it repeatedly can hide a fault that is getting worse. The code page states what the manual documents the code as, and that documented level is the one to respond at.
Recording a code the way a technician needs it
A useful record is more than the code itself. Write down the exact characters and punctuation as they appear, because different controllers format the same fault differently, and photograph the display rather than trusting memory. Note when the code appears: on startup, after a period of running, only when a hot-water tap is opened, or only in cold weather. Add what the boiler was doing at the time, how many times it has happened, the pressure gauge reading if the appliance has one, and any recent service, repair or power interruption. If the control keeps a fault history, mention that, because a technician can read the stored log at the visit.
That context does work the code cannot. A flame code that appears only after a long run points somewhere different from one that appears on every light. A pressure code that returns after a recent drain-down tells the technician a fill step may have been missed. None of these notes is a diagnosis, but they shorten the road to one, and they cost nothing to collect.
A code names a condition, not a failed part
One habit separates a quick repair from a parts lottery: treating the code as a question to be answered by measurement rather than a part to be replaced. A code that says the burner did not prove flame can be caused by gas pressure, an electrode gap, a contaminated flame rod, a grounding fault or a venting restriction, and the manual's procedure tests them in order. Replacing the most expensive component first, or swapping parts until the code stops, is not how the manuals are written and usually costs more than the diagnosis would have.
This is also why the code index on this site names the uncertainty on each entry. The meaning recorded by the manufacturer is the reliable part; the cause behind it is confirmed on site, with instruments, against the appliance. When a code is not on the site, the manual for the exact model is the fallback, and every model page links that manual with its version number.
Safe first steps, whatever the code
The safe response to a code does not depend on knowing its meaning. First, note the exact code and what the appliance was doing when it appeared. Second, if you smell gas, stop, leave the building and call your gas utility's emergency line or 911 from outside before anything else; a code is not a gas leak, but the smell test overrides every other step. Third, if a carbon-monoxide alarm sounds anywhere in the building, leave immediately and call 911 from outside, and do not run the appliance again until it has been checked, since several code families, venting, flame and over-temperature protections, exist precisely because combustion and exhaust problems are dangerous.
Do not keep resetting the boiler to force more ignition attempts or to clear a recurring code: a reset clears the message, not the cause, and repeated attempts can turn a service call into an emergency call. Do not remove covers, touch gas or ignition components, or bypass any safety device. If the boiler is off, leave it off and call a licensed technician; if it is running and the code is informational, book the service or repair visit and watch whether the code returns. The repair, emergency and maintenance services on this site, delivered with ROMA Heating & Cooling in Greater Vancouver, diagnose codes against the manufacturer's procedure rather than against folklore.
- Write down the exact code or alert text and what the boiler was doing when it appeared
- If you smell gas or a CO alarm sounds, leave the building and call 911 from outside
- Match the code to the appliance's controller generation and manual before interpreting it
- Do not repeatedly reset, remove covers, or touch gas, ignition or combustion components
- Use the error-code index on this site to see the documented meaning, severity and safe steps for your code
Find the controller and manual before you look up the code
A code means nothing until it is matched to the control that printed it, and the appliance in a Greater Vancouver home is not always the model the owner believes it is. The starting point is the rating plate on the boiler, which carries the brand, the model number and the serial number; the controller is usually named on the display bezel or on the cover of the manual, and the manual version matters because the same code can be redefined between editions. Photograph the rating plate and the display together, because a technician can identify the exact series and controller from those two images faster than from a spoken description.
The difference between a boiler series and its controller is easy to miss. A single series can ship with more than one control over its production life, and a controller can be used across several series, so knowing only the brand name is not enough to decode a code safely. The error-code index on this site records each code against the series, the controller and the manual that document it, and it keeps identical numbers with different meanings as separate entries for exactly that reason. This site's serial-number guides for several brands explain how to read the rating plate and the date of manufacture, which helps pin the production era and therefore the controller that is likely fitted. When a code is not on the site, the manual for the exact model, linked from its model page, is the authority.
Codes that only appear in cold weather
Some code families show up almost only in winter, and knowing that narrows the response. Condensing boilers produce acidic condensate continuously while they fire, and an exposed drain line or a sidewall vent terminal can freeze during a Greater Vancouver cold snap. The appliance then reports a condensate, vent or flame condition that would never appear in July, even though nothing in the control has failed. A code that arrives with the first hard freeze and clears when the weather moderates is describing the weather as much as the boiler.
The safe homeowner actions in that situation are limited and specific. Snow or ice that has buried an exterior vent terminal can be cleared from a safe distance, without reaching inside the terminal, and the same applies to a visible ice plug at a condensate discharge point. Beyond that, the trap, the drain routing and any condensate pump are part of the boiler's flue-gas seal and belong to a service visit, because condensate is mildly acidic and the trap is a safety component. A code that repeats after the weather warms is not a winter condition and should be diagnosed on its own terms.
It is worth separating a cold-weather code from a cold-weather symptom. Low system pressure, a boiler that short-cycles on a very cold morning, and a radiator that is slow to warm are seasonal experiences rather than error codes, and each has its own page on this site. Recording the exact code is what tells those apart: a code names a specific protection the control tripped, while a general complaint about cold performance does not.
The code families, and what each one points at
Codes look chaotic because there are hundreds of them, but almost every boiler fault belongs to one of a few families, and identifying the family is a useful step before the exact entry is looked up. A family names the system the control is protecting rather than the failed part: an ignition code means the boiler tried and failed to prove a flame, a pressure code means the sealed loop's water content or its low-water protection was outside its limits, and a sensor code means a temperature or pressure signal the control depends on was missing or out of range. The family tells you whether the boiler stopped for a combustion reason, a water reason or an electrical one.
The families are not invented here; they are the groupings the manufacturers' own fault tables use. Navien's NCB-H manual organises its codes around heat-exchanger overheat, ignition and flame, thermistors, water pressure, the gas train, the fan and vent path, and the control board and its communications. IBC's V-10 controller names the same conditions in words, with alerts such as Water High-Limit, Low Water Cutoff, Low RPM / air flow and Controller Board. Viessmann's F.x codes separate the fault family before the dot from the specific fault after it, which is the same idea in a compact form. The table below maps the families to what each one is protecting, with examples of the codes already documented on this site.
| Fault family | What the control is protecting | Examples documented on this site |
|---|---|---|
| Ignition and flame | Proof that a burner flame was established and stayed lit | E003 (ignition failure), E012 (flame loss), IBC text alert Error – Ignition trials exceeded |
| Overheat and high limit | Water, burner and flue-gas temperature limits | E001 and E016 (heat exchanger overheat), E030 (exhaust overheat), IBC alerts Water High-Limit and Vent High Limit |
| Water pressure and flow | The sealed loop's water content and its low-water protection | E302 (low water pressure), E352 (high water pressure), E777 (low water cutoff activated), IBC alerts Low Water Cutoff and Low Water Pressure |
| Temperature and sensor circuits | The thermistor and sensor signals the control relies on | E205 (heating supply sensor), E218 (heating return sensor), E047 (exhaust thermistor), Viessmann F.5 (sensor lead break or short circuit) |
| Air, vent and condensate path | Fan, air proving and the flue-gas route | E109 (abnormal fan motor), E110 (exhaust blockage), E762 (vent pipe not fully inserted), IBC alerts Low RPM / air flow and Fan Pressure |
| Gas train and installation settings | Fuel type and the gas-side configuration | E773 (improper gas type detected), E788 (incorrect gas type setting), E060 (abnormal dual venturi) |
| Control, memory and communication | The board, its wiring and the devices linked to it | E515 (abnormal PCB), E594 (abnormal EEPROM), E782 (front panel communication), IBC alerts Controller Board and No Boilernet Comm |
What the family tells you before you look up the exact code
Two conclusions follow from the table. First, the family is not the diagnosis either: an ignition code can come from the gas supply, the igniter, the flame rod, the grounding or a venting restriction, and only measurement on site separates them. Second, some families carry more urgency than others. The overheat, flame and vent families exist because combustion and exhaust problems can be dangerous, so a code in one of those families that returns after a reset is a call for a licensed technician rather than another reset. The exact severity is recorded per code on this site's code index, because the family points the direction and the individual entry states the level.
The fault history: the code you never saw
A code that appears and then clears itself can leave a homeowner wondering whether anything happened at all. Something did: the control detected a condition, acted on it, and returned to normal. Many controls keep a fault history, and some show past faults in a status or service menu even after the display has gone back to its usual reading. Viessmann's Vitodens controls keep a fault history, and IBC's V-10 controller documents a Status menu reached through its SIM menu, which is where a stored or cleared condition is read.
That history is worth more than a single snapshot. A boiler that has logged the same ignition or pressure fault several times is telling a technician the condition is repeating even though the owner only saw it once. When a code has cleared, note the date and what the boiler was doing, and tell the technician that the control keeps a log; reading the stored faults is part of the visit. Where the manual documents how to view the history, the entries can be photographed in advance, which gives the same evidence the exact code would have given.
A self-clearing code should not be dismissed as a glitch. Automatic-reset entries such as a low-water-pressure or high-water-pressure code describe a real measurement the control made; it simply returned to range on its own. A code that clears once after a one-off event, such as a pressure dip during a drain-down, may need nothing more than a note. The same code returning over days or weeks is a pattern, and a pattern is what a technician can act on.
Where to look your code up
The error-code index on this site records the documented codes for the brands it covers, IBC, Navien, NTI and Viessmann, each entry tied to the series, controller and manual that document it, with the documented meaning, the uncertainty around it, severity and safe first steps. Starting there answers the first question, what does the manual say this code is, and the code page cites the manual section so the claim can be checked against the source. The brand error-code pages group codes by brand, and each model page links the codes that apply to its controller.
When a code is not on this site, the authoritative fallback is the manufacturer's manual for the exact model, which every model page on this site links with its version number. From there the path is the same as for any code: note it, check the safe items, and call a licensed technician who can read the manual's procedure and the appliance's actual measurements together. Codes are the boiler's way of starting the conversation; the diagnosis still happens on site.