Mack SPN 1569 FMI 31: Engine Protection Torque Derate
SPN 1569 FMI 31 (FMI 31) — Engine Protection System - Torque Derate - Condition Exists
Quick Answer
SPN 1569 FMI 31 means engine protection is actively cutting torque in response to a separate underlying fault - find and fix the accompanying code.
Critical — Stop Engine / Derate Risk
SPN 1569 FMI 31 is a summary code showing the engine protection system has actively limited torque due to another underlying fault. Like on shared-platform Volvo engines, this is always a symptom, and the real diagnostic job is finding the root-cause code.
Overview: Mack SPN 1569 FMI 31
This code is the effect, not the cause. Look for the specific fault code logged alongside it for the real repair target.
Repair Snapshot
Time
Varies by Root Cause
Difficulty
Advanced
Parts Cost
Varies by Root Cause
Dealer Labor
$200+ Diagnostic Fee
Tools Required
- Diagnostic Scan Tool with Full Fault History Access
What SPN 1569 FMI 31 Means
SPN 1569 FMI 31 is a summary code showing the engine protection system has actively limited torque due to another underlying fault. Like on shared-platform Volvo engines, this is always a symptom, and the real diagnostic job is finding the root-cause code.
Symptoms Drivers Notice
- Noticeable, often severe power loss
- Red warning lamp typically active
- Truck limited to a low fixed speed
- Always accompanied by a more specific fault code
Most Likely Root Causes
High coolant temperature triggering thermal protection
CommonOverheating is one of the most frequent derate triggers.
Low engine oil pressure
CommonInsufficient lubrication pressure triggers an aggressive protective derate.
Excessive DPF soot load
CommonA filter loaded beyond its safe threshold forces a performance limit.
Common Misdiagnoses (Don't Waste Parts)
Trying to clear only SPN 1569
Why it happens: It's the code drivers report.
Do this instead: Always pull the full fault list for the actual root-cause code.
Assuming an ECM software glitch
Why it happens: A sudden power loss can feel like a control fault.
Do this instead: This is intentional protective behavior - find the real trigger.
Master Tech Commentary
Mechanic's Notes
Shop tip: never treat SPN 1569 as the target of repair - find the accompanying code and fix that instead; this one clears on its own once the real problem is resolved.
Step-by-Step Diagnostic Procedure
- Step 1: Pull the full active fault list - SPN 1569 never appears alone.
- Step 2: Prioritize checking coolant temp, oil pressure, and DPF soot load codes first.
- Step 3: Check for SCR inducement codes if the derate feels gradual rather than sudden.
- Step 4: Review fault history timeline to see which code logged first.
- Step 5: Fix the root-cause code directly rather than attempting to clear SPN 1569 itself.
Professional service / OEM-level scan tools are recommended before clearing this fault for good.
Live Data & Freeze-Frame Tips
Review fault timestamp history - the code that logged first is almost always the true root cause.
Safety Warnings
- Do not attempt to bypass engine protection derates.
- Move to a safe location if the derate is severe enough to be unsafe in traffic.
When to Limp In vs Tow
If the root cause is critical (very low oil pressure or extreme overheating), do not continue driving - tow instead.
Prevention Tips for Fleets & Owner-Operators
- Address underlying faults promptly.
- Keep up with scheduled maintenance.
- Train drivers to report early warning lamps.
Related Fault Codes
SPN 110
Coolant temperature fault, one of the most common root causes of this derate.
SPN 100
Engine oil pressure fault, another frequent trigger.
Frequently Asked Questions
Can I fix this code directly?
No, it's a symptom code - fix the accompanying root-cause fault and this one resolves on its own.
Why did my truck suddenly lose power?
The engine protection system detected a condition severe enough to warrant an immediate torque cut.
Is it safe to keep driving?
Depends on the root cause - some are safe to limp on, others demand an immediate stop.
Will this recur after clearing?
Yes, if the underlying fault isn't repaired.
How do I find the real cause?
Pull the complete fault list - the specific accompanying code is the answer.