SPN 609 FMI 19: Meaning and Fix
This fault indicates the Controller #2 (typically an aftertreatment or secondary engine control module) has detected corrupted or invalid data received over the J1939 CAN bus. In practice, this code frequently appears after a forced DPF regeneration or following an ECU reflash where message counters or checksums become misaligned between primary and secondary controllers.
Common Symptoms
- CAN Bus Errors: Intermittent loss of communication between primary ECM and Controller #2 on J1939 backbone.
- Torque Derate: Engine power reduced by up to 40% as safety fallback when controller data integrity is compromised.
- Warning Lamps: Red STOP lamp and amber WARNING lamp illuminate simultaneously on the dashboard.
- Erratic Aftertreatment: DEF dosing or DPF regeneration cycles become unpredictable or fail to initiate.
Probable Causes
- Corrupted CAN Message: Faulty message counter or CRC from a secondary controller due to software mismatch.
- Electrical Noise: High-frequency interference from alternator or injector drivers coupling into the CAN bus.
- Termination Resistor: Missing or incorrect 120-ohm termination resistor at Controller #2 causing signal reflection.
- ECM Firmware Bug: Known issue in certain Bosch EDC17 versions where message timeouts are misreported as data errors.
Advanced Technical Analysis
The Controller #2 monitors each received J1939 message for the expected message counter (incrementing 0-15) and CRC. If the counter does not increment by exactly one, or the CRC fails, the ECM sets SPN 609 FMI 19. The fault is logged as a current or historic code depending on the debounce timer, typically set to 500 ms of continuous errors.
Electrical analysis should include CAN_H to CAN_L differential voltage measurement (nominal 1.5V to 3.5V idle, 2.5V dominant). Oscilloscope capture often reveals ringing or glitches on the bus. Technicians commonly find that a failing alternator diode produces 300-500 kHz noise that corrupts high-speed CAN messages (250 kbps).
Upon detecting the error, the ECM enters a limp-home mode that limits engine torque to 40% and disables cruise control. The aftertreatment system may also default to a safe state, preventing DEF injection to avoid uncontrolled reactions. This is a standard SAE J1939 safety fallback for data integrity faults.
Long-term resolution requires cross-referencing the latest manufacturer TSBs. For example, Deutz TCD 2015 engines had a factory bulletin requiring a CAN termination resistor check at the SCR controller. A real-world workshop case involved a Mercedes-Benz OM471 where a loose pin in the 120-pin connector caused intermittent CRC failures only under vibration.
Step-by-Step Troubleshooting Guide
- Inspect CAN Wiring: Measure resistance between CAN_H and CAN_L at Controller #2; should be 60 ohms with bus powered off.
- Check Termination: Verify 120-ohm resistor is present at both ends of the J1939 backbone using an ohmmeter.
- Update Firmware: Reflash both primary ECM and Controller #2 with latest manufacturer-approved software version.
- Oscilloscope Test: Capture CAN bus waveform during fault occurrence; look for voltage spikes below -1V or above 5V.
Have more questions about SPN 609 FMI 19?