Have Additional Questions? Contact Us →
A dashboard warning that says “AdBlue fault” is rarely enough to diagnose a Euro 5 or Euro 6 lorry. The real value is in the stored diagnostic information: the fault code, its status, the freeze-frame data and the conditions under which it returned. Understanding AdBlue fault code meanings helps a workshop separate a simple wiring issue from a failed NOx sensor, poor reductant quality or an SCR efficiency problem that may lead to a torque derate or start inhibit.
For fleet operators, the distinction matters. Replacing parts on assumption is expensive; allowing an active SCR fault to progress can be more expensive still. Read the code with suitable heavy-duty diagnostics, record it before clearing anything, then test the system identified by the code rather than the warning lamp alone.
Reading AdBlue fault code meanings correctly
On many commercial vehicles, diagnostic information is displayed as an SPN and FMI pair. SPN means Suspect Parameter Number – it identifies the circuit, sensor, component or system being monitored. FMI means Failure Mode Identifier – it indicates how the value or signal is considered faulty.
A display may also show an OEM-specific number, an engine warning level, a count of active faults, or an abbreviated description such as “reductant pressure low” or “NOx sensor signal implausible”. DAF, MAN, Iveco, Mercedes-Benz, Scania, Renault and Volvo do not always present the information in the same format. The same underlying issue can therefore appear under a different manufacturer description or additional proprietary code.
Treat the code as the starting point, not a parts order. A pressure-related code, for example, may be caused by a pump module, a blocked line, crystallised deposits, poor electrical supply, a connector fault or a control-unit issue. The manufacturer wiring diagram, live data and guided test routine determine which of those is actually present.
What the FMI usually tells you
The FMI often narrows the diagnostic path quickly. Its wording can vary between diagnostic tools, but these common J1939 interpretations are useful in the workshop:
- FMI 0 generally indicates a signal or parameter above the normal operating range at a severe level, while FMI 1 indicates below normal range at a severe level.
- FMI 2 points to an erratic, intermittent or incorrect signal. This is frequently relevant to sensor plausibility, network communication or unstable electrical connections.
- FMI 3 and FMI 4 usually concern voltage. FMI 3 is commonly voltage above normal or a short to positive; FMI 4 is voltage below normal or a short to ground.
- FMI 5 and FMI 6 commonly indicate current faults, such as an open circuit, low current, high current or a short circuit in an actuator circuit.
- FMI 7 suggests a mechanical system is not responding correctly. On an SCR system, this may direct attention towards dosing hardware, valves or pump operation.
- FMI 8, 9 and 10 can relate to abnormal frequency, update rate or rate of change. Check CAN communication, sensor output and operating conditions before condemning a component.
- FMI 13 may indicate calibration is required, FMI 14 refers to a manufacturer-specific special instruction, and FMI 15 to FMI 18 often identify a parameter that is high or low at different severity levels.
Do not rely on FMI interpretation in isolation. An FMI 4 on a heated AdBlue line points towards an electrical low-voltage condition, but the cause may be harness damage, water ingress, a poor earth, connector corrosion or a failed heater circuit. Measure the circuit under load where the manufacturer procedure requires it.
The SCR faults seen most often in workshops
Most AdBlue-related codes fall into a small number of fault families. Knowing the family makes first checks faster and prevents unnecessary replacement of expensive SCR components.
AdBlue level, temperature and quality faults
The tank assembly may contain level, temperature and quality sensing functions, depending on the vehicle. A low-level reading that does not match the tank contents can be a sensor issue, wiring problem or tank module failure. A temperature signal outside a credible range can affect freeze protection and dosing strategy.
Quality faults need a more careful approach. Correct AdBlue is an aqueous urea solution to ISO 22241 specification. Contamination, dilution, incorrect fluid, aged stock or residue introduced during filling can produce a quality or concentration fault. Confirm the fluid condition and check for contamination before replacing sensors. If the vehicle has been topped up from an unsuitable container, the fault may be genuine even where the electrical system tests correctly.
Dosing pump, heater and pressure faults
The dosing system must build and regulate the required pressure before it can inject AdBlue accurately. Codes referring to low pressure, pump speed, pump current or line heating should lead to checks of battery voltage, fuses, relays, power supply, earth points, harness condition and connectors before replacing the delivery module.
Crystallisation is a practical consideration. White urea deposits around the injector, line connections or tank unit can restrict flow and damage seals. However, deposits are evidence of a problem, not automatic proof that the pump has failed. Inspect the injector seating, dosing line and exhaust connection for leaks, then use commanded actuator tests and live pressure data where supported by the diagnostic tool.
NOx sensor and SCR efficiency faults
NOx sensor faults are common on high-mileage Euro 6 vehicles. The system relies on upstream and downstream readings to calculate SCR conversion efficiency. A sensor code may identify heater performance, internal electronics, communication, slow response or implausible readings.
An SCR efficiency code does not automatically mean the catalyst is defective. Poor dosing, incorrect AdBlue concentration, exhaust leaks, a biased NOx sensor, low exhaust temperature, incomplete regeneration issues or catalyst deterioration can all affect the calculated result. Check whether the fault returns under the specific operating conditions required by the manufacturer. An efficiency monitor may not run during a short workshop idle test.
Inducement and start-inhibit warnings
Inducement codes require prompt attention because the control system has decided the emissions fault has persisted beyond an allowed threshold. Depending on the manufacturer and severity, the lorry may receive a warning, speed restriction, torque reduction or a countdown to start inhibit.
The inducement message is normally a consequence, not the root cause. Clearing it without resolving the triggering fault may temporarily remove the message, but it will return once the monitor runs again. Record the active and pending faults, repair the cause, complete any required reset or adaptation procedure, and verify that the system has passed its monitor conditions.
A practical diagnostic order for SCR warnings
Start with a full vehicle scan, not only the engine ECU. SCR faults can involve the engine management system, aftertreatment controller, body controller and CAN network. Save fault reports and freeze-frame information, particularly engine temperature, exhaust temperature, reductant level, pressure, vehicle speed and battery voltage.
Next, establish whether the code is active, stored or intermittent. An active electrical fault normally justifies immediate circuit checks. An intermittent sensor or communication fault may need a harness inspection, connector tension test and road test with live data recording. Clearing faults before recording their context removes evidence that may be needed later.
Then inspect the basics: correct AdBlue in the tank, obvious leaks, damaged wiring, rubbed-through harnesses, corroded connectors and signs of crystallisation. Check battery condition and charging voltage as low system voltage can create multiple misleading aftertreatment codes.
Use live values to compare commanded and actual operation. Depending on the vehicle, this may include tank level, reductant temperature, quality value, pump pressure, dosing command, exhaust temperatures and both NOx readings. A good diagnostic tool is valuable because it shows whether the ECU is requesting a function and whether the component is responding.
Finally, carry out the manufacturer-approved repair, reset or commissioning routine where required. Some replacement NOx sensors, pump modules and control units need coding, adaptation or a guided test. Confirm the repair with a road test or controlled monitor run, not only by checking that the warning lamp is off in the workshop.
What a fault code cannot confirm
A code identifies the ECU’s observed fault condition. It does not always identify the failed part. For example, a downstream NOx reading that appears implausible might result from the sensor itself, an exhaust leak, wiring damage, a supply issue or an SCR system fault affecting the gas composition.
This is why generic code lists have limits. They are useful for translating terminology, but OEM data remains essential for pinouts, resistance values, test conditions and repair procedures. On commercial vehicles, component location and wiring can differ by engine, chassis layout, production year and emissions variant.
For workshops handling repeat SCR cases, keep diagnostics disciplined: capture the original data, test the circuit and system conditions, fit compatible parts where a component is proven faulty, and complete the required verification procedure. That approach protects repair time, reduces repeat visits and gives the operator a compliant repair with a clear technical record.
