SPN 1569 FMI 9: Meaning and Fix
This fault indicates the Engine Protection Torque Derate information message (PGN 65254) is not being received at the expected periodic rate. The ECM interprets this as a loss of critical engine protection data, forcing a torque reduction. Technicians commonly encounter this after ECM replacement or wiring repairs where the engine protection module’s CAN bus connection is disturbed, causing intermittent message loss.
Common Symptoms
- Reduced Power: Engine torque is limited to a severe derate percentage, typically below 50%, based on SPN 544.
- Warning Lamp: Red or amber engine warning lamp illuminates steady on the dash, indicating an active derate.
- No Cruise Control: Cruise control is disabled because the ECM cannot verify safe torque limits from the protection module.
- Hesitation on Load: Vehicle struggles to accelerate under load, especially on grades, due to the torque cap.
Probable Causes
- CAN Bus Fault: Open, short, or high resistance on the CANH or CANL lines between the engine protection module and ECM.
- Module Power Loss: Engine protection controller (e.g., Bosch EDC17) loses 12V or ground, stopping message transmission.
- ECM Software Glitch: Corrupted or incompatible J1939 configuration in the ECM after a flash update or parameter change.
- Damaged Connector: Corroded or bent pins at the engine protection module 70-pin connector, causing intermittent signal drop.
Advanced Technical Analysis
The ECM’s microcontroller runs a dedicated J1939 receive task that expects the Engine Protection Torque Derate Information message (PGN 65254) every 100 ms. When the message fails to arrive within a 300 ms timeout window, the FMI 9 is set. The ECM then activates a severe torque derate, capping output to a value stored in memory (typically 30% of reference torque) to prevent catastrophic engine damage under unmonitored conditions.
Electrically, the abnormal update rate is often caused by a marginal CAN bus termination or a single-wire failure. The engine protection module uses a dedicated transceiver (e.g., TJA1050) that requires a stable 2.5V common-mode voltage. A slight offset due to a corroded ground can cause the transceiver to miss arbitration, dropping the periodic transmission. The ECM’s debouncing timer confirms the fault after three consecutive missed messages.
From a safety architecture perspective, the derate is a fallback defined in ISO 26262 ASIL B. The ECM cannot distinguish between a genuine module failure and a communication glitch, so it defaults to the most restrictive torque limit. This is a deliberate design choice: under severe conditions, a false derate is safer than allowing unmonitored engine operation. The derate remains active until the message resumes for at least 10 consecutive cycles.
Long-term diagnosis should include a CAN bus traffic analysis using a J1939 data logger. Real-world workshops have traced this fault to a loose pin in the engine protection module’s 12-pin Deutsch connector, often after a DPF regeneration event that caused thermal cycling. Replacing the connector and verifying the termination resistor (120 ohms across CANH-CANL) resolves the issue permanently. Always clear the fault after repair with a 10-minute key-off cycle.
Step-by-Step Troubleshooting Guide
- Check CAN Bus: Measure resistance between CANH and CANL at the ECM; must be 60 ohms (terminated) or 120 ohms (unterminated).
- Verify Module Power: Confirm 12V and ground at the engine protection module connector with key-on; check for voltage drop.
- Inspect Connectors: Remove and visually inspect all pins for corrosion, bending, or pushed-back terminals; clean with contact cleaner.
- Monitor Message Rate: Use a J1939 scanner to verify PGN 65254 transmits every 100 ms; if missing, replace the protection module.