SPN 4094 FMI 31: Frequently Asked Questions


Full Diagnostic Guide — SPN 4094 FMI 31

1. What does SPN 4094 FMI 31 mean?

SPN 4094 FMI 31 indicates that the engine control module (ECM) has detected that NOx levels in the exhaust stream have exceeded a calibrated threshold specifically due to poor diesel exhaust fluid (DEF) quality. This fault is triggered when the DEF concentration of urea falls below 32.5% or contains contaminants like water or hydrocarbons, causing insufficient NOx reduction in the SCR system. It is a condition-based fault, not a hardware short or open circuit.

2. What are the most common symptoms when this code is active?

Common symptoms include an active engine derate that reduces torque by up to 25% or more, illumination of the emissions warning lamp, and a noticeable loss of acceleration. Drivers may also observe increased exhaust opacity or a DEF quality warning on the dashboard. In severe cases, the vehicle may fail an emissions opacity test due to elevated NOx output. The derate typically escalates after 10–20 engine hours if the condition is not corrected.

3. How does the ECM determine that this specific failure (FMI 31) has occurred?

The ECM compares upstream and downstream NOx sensor readings. Under normal conditions, the SCR system should reduce NOx by at least 80–90%. When DEF quality is poor, the downstream NOx sensor detects values exceeding a calibrated limit (e.g., > 2.0 g/kW-hr) while the upstream sensor shows normal readings. The ECM then increments a fault timer. If the condition persists for a set duration (often 30–60 minutes of engine operation), FMI 31 is logged.

4. What is the difference between FMI 31 and other common FMIs for SPN 4094?

FMI 31 is specific to a condition where NOx limits are exceeded due to poor DEF quality. In contrast, FMI 1 (low voltage) indicates a sensor supply issue, FMI 3 (voltage high) points to a short to battery, and FMI 4 (open circuit) indicates a broken wire. FMI 31 does not involve electrical faults; it is a performance-based diagnostic that signals a chemical or fluid quality problem in the DEF system.

5. What are the most probable root causes?

The most probable root cause is contaminated or substandard DEF with urea concentration below 32.5% or containing impurities like salt or oil. A secondary cause is a partially clogged DEF injector that reduces flow rate below 200 mL/min, preventing proper NOx reduction. Other possibilities include a degraded SCR catalyst that has lost conversion efficiency, or a NOx sensor that has drifted and reads falsely high, though this is less common for FMI 31.

6. Can a purely mechanical issue cause this code without a faulty component?

Yes, a purely mechanical issue such as a restricted DEF supply line or a frozen DEF tank can cause this code. If the DEF pump cannot draw fluid due to a blocked filter or ice formation, the injector receives insufficient fluid, leading to poor NOx conversion. Additionally, a misaligned or leaking DEF injector nozzle can cause poor atomization. These issues are mechanical and do not require an electrical component failure.

7. What default actions does the ECM take when this code is active?

Upon detecting SPN 4094 FMI 31, the ECM typically initiates a progressive derate. Initially, engine torque may be reduced by 10–15%, increasing to 25–40% after 10–20 hours of operation. The ECM also disables the DEF quality monitoring system and logs the fault. If the condition is not corrected, the ECM may eventually limit vehicle speed to 5 mph or less. The warning lamp is illuminated immediately to alert the driver.

8. How do I perform a basic functional test for this component?

To test DEF quality, use a refractometer to measure the urea concentration; it should read 32.5% ± 1.5% at 20°C. For the DEF injector, perform an active test using a diagnostic tool to command a 200 mL/min flow for 30 seconds while monitoring downstream NOx sensor response. A healthy system should show a drop in NOx levels of at least 50% within 20 seconds. If no change occurs, suspect injector or fluid quality.

9. What specific electrical checks should I run before replacing parts?

Measure the voltage at the DEF injector connector with the ignition on; it should be 12V ± 0.5V relative to ground. Check the resistance of the injector solenoid coil; typical values are 2.5–5.0 ohms. Also verify the NOx sensor heater circuit resistance (should be 4–8 ohms) and supply voltage (12V). Inspect the CAN bus wiring at the NOx sensor for continuity and absence of shorts. Do not skip these checks to avoid unnecessary part replacement.

10. Is it possible that the ECM itself is responsible for this fault?

ECM failure is extremely rare for FMI 31. The fault is triggered by sensor inputs and fluid quality, not by ECM logic errors. However, if the ECM has corrupted calibration data or a failed internal CAN transceiver, it could misinterpret NOx sensor signals. Before considering ECM replacement, rule out all other causes: test DEF quality, inspect the injector, verify NOx sensor accuracy, and check for software updates. ECM replacement should be a last resort.

11. What is the complete step-by-step diagnostic procedure?

1) Read and record all active and inactive codes. 2) Check DEF level and quality with a refractometer. 3) Inspect DEF lines and injector for leaks or clogs. 4) Perform an active DEF injector flow test. 5) Monitor upstream and downstream NOx sensor data at idle and under load. 6) If NOx reduction is insufficient, replace DEF with known good fluid and retest. 7) If still failing, inspect SCR catalyst for damage. 8) Replace faulty injector or sensors as needed. 9) Clear codes and perform a road test.

12. How can I prevent this fault from recurring?

Use only API-certified DEF that meets ISO 22241 standards, with a urea concentration of 32.5%. Store DEF in a clean, sealed container away from direct sunlight and temperatures above 30°C to prevent degradation. Replace DEF filters at the manufacturer’s recommended intervals (typically every 100,000 miles). Periodically clean the DEF injector tip using a specialized cleaning solution. Avoid using additives or water to dilute DEF.

13. Does this fault affect fuel economy, emissions, or engine lifespan?

Yes, it directly impacts all three. Poor DEF quality reduces SCR efficiency, causing higher NOx emissions that can exceed regulatory limits. The resulting engine derate reduces fuel economy by 5–15% due to altered injection timing. Prolonged operation with this fault can lead to increased exhaust backpressure and soot loading, potentially damaging the DPF and reducing engine lifespan through excessive regeneration cycles.

14. Can I clear the code and continue operating the vehicle temporarily?

You can clear the code using a diagnostic tool, but the fault will likely reoccur within a few engine operating hours if the root cause (poor DEF quality) is not addressed. Clearing the code temporarily removes the derate, but the ECM will re-detect the condition and re-log the fault. Continued operation with poor DEF can cause permanent SCR catalyst damage. It is not recommended to drive more than 50 miles without corrective action.

15. When should I choose to replace the component versus repairing the wiring?

For FMI 31, wiring repairs are rarely applicable because the fault is not electrical. Replace the DEF injector if it shows flow below 150 mL/min during active testing or if the spray pattern is uneven. Replace the NOx sensors if they fail the heater resistance test or show offset readings > 0.5 g/kW-hr at key-on. Replace the SCR catalyst if it is physically cracked or if NOx conversion efficiency is below 50% after fluid and injector corrections.

16. What type of diagnostic tool do I need to read this fault code?

You need a J1939-compatible diagnostic tool that supports DTC reading and live data. A basic code reader that only displays generic OBD-II codes will not work, as SPN 4094 is a J1939 proprietary code. A tool that supports SAE J1939-73 and can interpret SPN and FMI fields is required. Examples include the Noregon JPRO, Cummins INLINE, or a professional-grade multimeter with J1939 interface.

17. What can a professional J1939 scanner do that a basic reader cannot?

A professional J1939 scanner can display live data from the NOx sensors (e.g., upstream and downstream NOx concentration in ppm), DEF injector flow rate, SCR inlet temperature, and DEF quality percentage. It can perform active tests like commanding the DEF injector to open and measuring flow. It also provides detailed fault logging with freeze frame data, such as engine load and RPM at the time of the fault, which a basic reader cannot access.

18. What are the key CAN bus parameters I should monitor when diagnosing this code?

Monitor PGN 61444 (Engine Speed and Load), PGN 65270 (SCR Catalyst Temperature), PGN 65132 (DEF Level and Quality), and PGN 61442 (NOx Sensor Output). Specifically, watch for the DEF quality parameter (SPN 3719) which should read 100% for good fluid. Also monitor the downstream NOx sensor (SPN 4094) reading; if it exceeds 500 ppm while upstream is below 200 ppm, the SCR system is not functioning correctly.

19. What is a PGN and how does it relate to SPN 4094?

A Parameter Group Number (PGN) is a 19-bit identifier in J1939 that groups related data parameters. For SPN 4094, the associated PGN is typically 61442 (NOx Sensor Output). The PGN defines the message structure on the CAN bus, while the SPN (Suspect Parameter Number) identifies a specific data item within that PGN. Understanding the PGN helps you locate the correct CAN message to monitor for NOx sensor data during diagnostics.

20. What components make up a complete J1939 Diagnostic Trouble Code (DTC)?

A complete J1939 DTC consists of four fields: the Suspect Parameter Number (SPN), which identifies the component or parameter (e.g., 4094 for NOx sensor); the Failure Mode Identifier (FMI), which describes the type of failure (e.g., 31 for condition exceeded); the Occurrence Count (OC), which indicates how many times the fault has occurred; and the SPN Conversion Method (CM), which is used for scaling. Each field is transmitted as part of a DM1 message.