Detailed guide for SPN 1569 FMI 31
Back to top ↑What this fault means
SPN 1569 FMI 31 generally indicates that an engine protection or emissions strategy has reduced available engine torque. It is commonly a result or status code rather than the original failure that caused the problem.
That distinction matters. Replacing components because of SPN 1569 alone usually does not solve the truck. The useful diagnostic information is normally found in the other active or recently active fault codes.
What you may notice
The truck may have reduced power, limited throttle response, an engine-protection message, an emissions inducement warning or another derate indication. The amount of torque reduction depends on the engine and calibration.
What to check first
Record every active and inactive fault before clearing anything. Look for codes involving aftertreatment, DEF/SCR operation, DPF soot load, engine temperature, oil pressure, sensor plausibility, communication or other engine-protection conditions.
Determine which fault occurred first and which code is actually commanding the protection strategy.
Diagnostic approach
Repair the underlying fault instead of treating SPN 1569 as a failed component. Confirm sensor readings are plausible, inspect affected circuits and complete the OEM diagnostic procedure for the companion code.
After the root problem has been repaired, clear codes only when appropriate and verify the repair with the required road test, regeneration or OEM reset procedure.
Do not repeatedly clear SPN 1569 without correcting the cause. The derate can return because the ECM still sees the condition that triggered protection.
OEM definitions and inducement strategies vary, so confirm the exact SPN/FMI meaning and reset procedure for the engine being serviced.
Mechanic community notes for SPN 1569 FMI 31
Back to top ↑Real-world tips from technicians. Submissions are moderated to keep spam and “my cousin fixed it with duct tape” content out.
Share your fix / advice
Keep it useful: symptoms, what you checked, what fixed it, and whether the code stayed inactive after a drive cycle.