Full Diagnostic Guide — SPN 5245 FMI 31
1. What does SPN 5245 FMI 31 mean?
SPN 5245 FMI 31 indicates that the aftertreatment DEF level sensor signal is continuously active or inactive beyond expected thresholds, as detected by the ECM. Specifically, FMI 31 means the signal is ‘condition exists’ – the sensor output remains stuck at a high or low value (e.g., above 4.9V or below 0.5V) for an extended period, preventing accurate DEF level monitoring. This can occur after a forced DPF regeneration or due to a wiring/sensor fault. The ECM uses this to trigger warning lamps and potential derates.
2. What are the most common symptoms when this code is active?
Common symptoms include the DEF low level warning lamp staying on despite a confirmed adequate DEF fill, engine torque derate up to 25% after 10 hours of continuous warning, no-restart condition after key-off due to SCR lockout, and intermittent lamp flicker during acceleration or vibration. These symptoms occur because the ECM cannot trust the DEF level reading, leading to safety strategies to protect the aftertreatment system.
3. How does the ECM determine that this specific failure (FMI 31) has occurred?
The ECM monitors the DEF level sensor voltage on the analog input. Under normal operation, the sensor should output 0.5V (empty) to 4.5V (full) with a 5V reference. FMI 31 is set when the voltage remains continuously above 4.9V or below 0.5V for a calibrated time (e.g., 10 seconds) or when the signal doesn’t change as expected during tank fill/empty cycles. The ECM also checks for rationality against engine run time and DEF consumption.
4. What is the difference between FMI 31 and other common FMIs for SPN 5245?
For SPN 5245, FMI 31 indicates a ‘condition exists’ – a stuck or invalid signal, not an open/short circuit. FMI 3 (voltage high) or FMI 4 (voltage low) are specific electrical faults (e.g., short to battery or ground). FMI 2 (erratic) means intermittent signal. FMI 31 is broader: the sensor output is out of expected range or stuck, but not necessarily a hard electrical failure. It often requires checking sensor calibration and wiring integrity.
5. What are the most probable root causes?
Probable causes include: sensor circuit short – signal wire shorted to battery or ground; faulty DEF level sensor – internal float or ultrasonic element failure providing stuck output above 4.9V or below 0.5V; ECM software mismatch – aftertreatment control module firmware incompatible with sensor output mapping; and corroded harness connector – moisture ingress at J1939 backbone or sensor connector creating intermittent high resistance. These lead to continuous or stuck signal conditions.
6. Can a purely mechanical issue cause this code without a faulty component?
Yes, a purely mechanical issue can cause this code. For example, if the DEF tank is overfilled or the sensor float is mechanically stuck due to debris or ice, the sensor output may remain high. Also, a kinked or pinched wiring harness can cause a short or open that simulates a stuck signal. Additionally, incorrect DEF quality or contamination can cause the sensor to read abnormally. Always check mechanical conditions before replacing parts.
7. What default actions does the ECM take when this code is active?
When SPN 5245 FMI 31 is active, the ECM illuminates the DEF low level warning lamp. After 10 hours of continuous warning, it initiates a 25% torque derate. If the condition persists and the vehicle is keyed off, the SCR system may lock out, preventing engine restart. The ECM also logs the DTC and may disable the DEF dosing system to prevent damage. These actions are designed to encourage prompt repair and reduce emissions.
8. How do I perform a basic functional test for this component?
First, manually measure the DEF tank level with a dipstick and compare to the sensor reading via a diagnostic tool. Then, with the ignition on, backprobe the sensor signal pin and verify voltage changes as you add or remove DEF. The voltage should range from 0.5V (empty) to 4.5V (full). If the voltage stays constant or out of range, perform a wiggle test on the harness while monitoring voltage to detect intermittent faults.
9. What specific electrical checks should I run before replacing parts?
Before replacing parts, check the sensor connector pins for corrosion, bent, or pushed-back pins. Measure the 5V reference voltage at the sensor connector – it should be 4.9-5.1V. Check the ground circuit for continuity and low resistance (<1 ohm). Backprobe the signal wire and verify it reads 0.5-4.5V depending on level. Also, check for shorts to battery or ground by disconnecting the sensor and measuring voltage on the signal wire (should be 0V with sensor disconnected).
10. Is it possible that the ECM itself is responsible for this fault?
Yes, the ECM can be responsible, although it’s less common. A software mismatch or internal ECM fault can cause incorrect processing of the sensor signal, leading to FMI 31. If all wiring and sensor tests pass, check for available ECM firmware updates. In rare cases, the ECM’s analog-to-digital converter may fail, causing a stuck reading. Use a diagnostic tool to monitor live data and verify the ECM is interpreting the signal correctly.
11. What is the complete step-by-step diagnostic procedure?
1. Scan for DTCs and record freeze frame data. 2. Visually inspect DEF tank level and sensor connector for damage/corrosion. 3. Connect diagnostic tool and monitor DEF level sensor voltage in live data. 4. Perform a manual dipstick test and compare. 5. Wiggle harness while watching voltage; note any fluctuations. 6. Measure 5V reference and ground at sensor connector. 7. If voltage is out of range, disconnect sensor and check for shorts. 8. If wiring is good, replace sensor. 9. Clear code and test drive. 10. If code returns, check ECM software and update if needed.
12. How can I prevent this fault from recurring?
To prevent recurrence, ensure DEF tank is kept clean and free of contaminants. Regularly inspect sensor connectors for corrosion and apply dielectric grease. Avoid overfilling the DEF tank. Perform periodic wiring harness checks, especially in areas prone to chafing. Keep ECM software up to date. Also, use high-quality DEF that meets ISO 22241 standards. During maintenance, test the sensor output and replace if it shows signs of wear or drift.
13. Does this fault affect fuel economy, emissions, or engine lifespan?
Yes, this fault can affect all three. The torque derate reduces engine power, which can increase fuel consumption as the driver may use higher throttle to maintain speed. The SCR system may disable DEF dosing, leading to increased NOx emissions. Over time, prolonged operation with derates can cause incomplete regeneration and soot buildup, potentially shortening engine and aftertreatment component lifespan. Addressing the fault promptly minimizes these impacts.
14. Can I clear the code and continue operating the vehicle temporarily?
You can clear the code with a diagnostic tool, but it will likely reappear if the root cause is not fixed. The ECM will re-detect the fault and re-illuminate the warning lamp, eventually leading to derate and lockout. Clearing the code may reset the 10-hour timer, but it’s only a temporary measure. Operating the vehicle without repair risks further derates and potential SCR lockout, so it’s not recommended for long-term use.
15. When should I choose to replace the component versus repairing the wiring?
Replace the sensor if it fails voltage output tests (stuck above 4.9V or below 0.5V) and wiring tests are normal. Repair wiring if you find a short, open, or high resistance in the harness or connectors. If corrosion is present, clean or replace connectors. If the wiring is chafed or damaged, repair the section. Use a multimeter to confirm the wiring is within specs before deciding to replace the sensor. If both are suspect, start with wiring repair as it’s cheaper.
16. What type of diagnostic tool do I need to read this fault code?
You need a diagnostic tool that supports SAE J1939 protocol and can read manufacturer-specific DTCs. This includes heavy-duty scan tools like those from Cummins, Detroit Diesel, or aftermarket options like a J1939-capable OBD-II adapter with appropriate software. The tool must be able to read SPN 5245 FMI 31 and display live data for the DEF level sensor. Basic OBD-II readers may not support J1939, so ensure compatibility.
17. What can a professional J1939 scanner do that a basic reader cannot?
A professional J1939 scanner can perform bi-directional tests, such as commanding the DEF sensor to output a specific voltage or triggering regeneration. It can read freeze frame data, monitor multiple PGNs simultaneously, and access manufacturer-specific fault codes and parameters. It can also calibrate sensors, update firmware, and perform DPF regeneration. Basic readers only display DTCs and limited live data, lacking the ability to diagnose complex aftertreatment issues or clear codes reliably.
18. What are the key CAN bus parameters I should monitor when diagnosing this code?
Monitor PGN 65189 (DEF Level) which contains the DEF level as a percentage and the sensor voltage. Also monitor PGN 65251 (Aftertreatment Control) for DEF dosing status, and PGN 65253 (Aftertreatment DEF Tank Information) for tank temperature and level. Additionally, monitor PGN 61443 (Electronic Engine Controller 2) for torque derate status. These parameters help correlate sensor readings with system behavior and confirm if the ECM is receiving the correct signal.
19. What is a PGN and how does it relate to SPN 5245?
A PGN (Parameter Group Number) is a J1939 message identifier that groups related parameters. SPN (Suspect Parameter Number) is a specific data field within a PGN. For SPN 5245, it is part of PGN 65189 (DEF Level). The PGN contains multiple SPNs, such as DEF level (SPN 5245) and DEF tank temperature. The ECM broadcasts this PGN on the CAN bus, and diagnostic tools decode the PGN to extract the SPN value and FMI status.
20. What components make up a complete J1939 Diagnostic Trouble Code (DTC)?
A complete J1939 DTC consists of four parts: SPN (Suspect Parameter Number) – identifies the component/system (e.g., 5245 for DEF level); FMI (Failure Mode Identifier) – describes the fault type (e.g., 31 for condition exists); OC (Occurrence Count) – number of times the fault has occurred; and CM (Conversion Method) – indicates how the data is scaled. Additionally, the DTC includes a status (active or inactive) and a timestamp. Together, these provide full diagnostic information for troubleshooting.