Full Diagnostic Guide — SPN 3713 FMI 31
1. What does SPN 3713 FMI 31 mean?
SPN 3713 FMI 31 indicates the Diesel Particulate Filter (DPF) active regeneration was inhibited because the system timed out before completion. The ECM monitors the regeneration process and sets this fault when the regeneration event does not finish within the expected time window, typically due to an interruption or system condition that prevents completion.
2. What are the most common symptoms when this code is active?
Common symptoms include regen lockout where the ECM refuses to initiate active regeneration despite soot load above threshold, the DPF warning lamp remaining continuously illuminated, engine power derate up to 25% to protect the DPF from thermal damage, and frequent premature regen attempts that exit before completion.
3. How does the ECM determine that this specific failure (FMI 31) has occurred?
The ECM calculates the expected regeneration duration based on soot load and exhaust temperature. If the regeneration event does not finish within this calculated time window—typically 30-45 minutes for a parked regen—and the soot load remains above threshold, the ECM sets FMI 31 to indicate a timeout condition.
4. What is the difference between FMI 31 and other common FMIs for SPN 3713?
FMI 31 specifically indicates a timeout condition where regen did not complete in the expected time. Other FMIs for SPN 3713, such as FMI 0 (data valid but above normal) or FMI 1 (below normal), indicate sensor range failures or system pressure issues. FMI 31 is unique because it relates to process completion rather than sensor signal validity.
5. What are the most probable root causes?
Most probable causes are an interrupted regen cycle (operator abort or ignition off), low battery voltage below 11.5V during regen causing ECM abort, faulty exhaust temperature sensors providing incorrect readings that prevent ECM from verifying regen conditions, or a clogged DPF with soot load exceeding 80% threshold beyond the ECM timeout window.
6. Can a purely mechanical issue cause this code without a faulty component?
Yes. A purely mechanical condition like a severely clogged DPF with soot load above 80% can cause the regeneration to take longer than the ECM timeout window, triggering FMI 31. Additionally, operator interruption by turning off the ignition or aborting a parked regen is a mechanical/operational cause that does not involve a faulty electronic component.
7. What default actions does the ECM take when this code is active?
The ECM locks out active regeneration, refusing to initiate any new regen events even if soot load exceeds threshold. It illuminates the DPF warning lamp continuously and may reduce engine torque by up to 25% to limit soot accumulation and prevent thermal damage. The timeout counter is set, requiring a diagnostic tool to reset before regen can be retried.
8. How do I perform a basic functional test for this component?
Use a scan tool to read DPF soot mass. If soot load exceeds 7 grams, attempt a forced stationary regeneration. Monitor exhaust inlet and outlet temperatures during the regen attempt; they should rise to 550-650°C. If the regen exits prematurely or temperatures do not reach target within 5 minutes, suspect sensor or voltage issues.
9. What specific electrical checks should I run before replacing parts?
Measure battery voltage at the ECM connector during a regen attempt; it must stay above 11.5V. Verify alternator output is >13.5V at idle. Check resistance and voltage supply to exhaust temperature sensors (typically 5V reference, signal return under 4.5V at operating temp). Ensure ground circuits have less than 0.1 ohm resistance.
10. Is it possible that the ECM itself is responsible for this fault?
It is unlikely but possible if the ECM has an internal fault affecting its timing calculations or regen control logic. Before suspecting the ECM, rule out all other causes: battery voltage, sensor accuracy, DPF clogging, and wiring integrity. ECM failure is only considered after all other probable causes have been eliminated through systematic testing.
11. What is the complete step-by-step diagnostic procedure?
1. Read fault codes and freeze frame data. 2. Check DPF soot load with scan tool; if >7g, attempt forced regen. 3. Verify battery voltage >12.4V and alternator output >13.5V. 4. Inspect exhaust temperature sensors for accuracy within ±15°C at idle. 5. Clear timeout flag using diagnostic tool. 6. Initiate stationary regen and monitor temperatures and duration. 7. If regen fails, inspect for exhaust leaks or restricted DPF.
12. How can I prevent this fault from recurring?
Ensure the vehicle completes full regeneration cycles without interruption—advise operators not to abort parked regens. Maintain battery voltage above 12.4V and alternator output above 13.5V. Replace faulty exhaust temperature sensors promptly. Perform regular DPF ash cleaning when soot load exceeds 80%. Use a diagnostic tool to reset timeout counters after each successful regen.
13. Does this fault affect fuel economy, emissions, or engine lifespan?
Yes. Fuel economy decreases because the engine operates in derate mode (up to 25% torque reduction) and frequent regen attempts consume extra fuel. Emissions increase as the DPF becomes less effective at trapping particulates. Engine lifespan may be reduced due to higher exhaust backpressure and thermal stress from incomplete regen events.
14. Can I clear the code and continue operating the vehicle temporarily?
You can clear the code with a diagnostic tool, but the underlying condition remains. The ECM will likely re-set the code as soon as another regen attempt times out. Temporary operation is possible but not recommended because the DPF soot load will continue to increase, leading to potential DPF damage or engine derate. Address root cause before clearing.
15. When should I choose to replace the component versus repairing the wiring?
Replace exhaust temperature sensors if they fail accuracy tests (±15°C at idle) or have internal shorts. Repair wiring if you find chafed, corroded, or broken wires at connectors or along harness—especially at sensor pigtails. For DPF replacement, only if soot load exceeds 7g and forced regen fails after all other causes are ruled out. Always repair wiring first.
16. What type of diagnostic tool do I need to read this fault code?
You need a J1939-compliant diagnostic tool that supports reading SPN 3713 and FMI 31. This can be a professional scan tool like a Noregon JPRO, Cummins Insite, or a heavy-duty multi-brand scanner. Basic OBD-II readers cannot access J1939 proprietary fault codes. The tool must also support forced regeneration and timeout counter reset functions.
17. What can a professional J1939 scanner do that a basic reader cannot?
A professional J1939 scanner can read and clear proprietary fault codes like SPN 3713 FMI 31, perform bidirectional tests (forced regen), monitor real-time exhaust temperatures and soot mass, reset timeout counters, and view freeze frame data. Basic readers only display generic OBD-II codes and cannot interact with DPF regeneration controls or J1939 parameter groups.
18. What are the key CAN bus parameters I should monitor when diagnosing this code?
Monitor SPN 3713 (DPF regeneration status) and SPN 3251 (DPF soot load) to assess regen state. Also monitor exhaust temperature sensors (SPN 3250 and SPN 3252) to verify proper temperature rise during regen. Battery voltage (SPN 168) should be above 12.4V. These parameters help determine if the timeout was caused by sensor inaccuracy or voltage drop.
19. What is a PGN and how does it relate to SPN 3713?
A PGN (Parameter Group Number) is a 18-bit identifier that groups related parameters transmitted on the J1939 bus. SPN 3713 is typically transmitted within PGN 64892 (DPF Regeneration Control) or PGN 65271 (Exhaust Gas Temperature). The PGN defines the message structure and timing, while the SPN identifies the specific data parameter within that message.
20. What components make up a complete J1939 Diagnostic Trouble Code (DTC)?
A complete J1939 DTC consists of four parts: SPN (Suspect Parameter Number) identifying the component or parameter, FMI (Failure Mode Identifier) indicating the type of failure, CM (Conversion Method) specifying data scaling, and OC (Occurrence Count) tracking how many times the fault has been detected. For SPN 3713 FMI 31, the CM is typically 0 or 1.