SPN 613 FMI 19: Meaning and Fix
SPN 613 FMI 19 indicates the Engine Control Module (ECM) has detected a corrupted or invalid data packet on the J1939 CAN bus from a specific controller. This fault commonly appears after a forced DPF regeneration when a sensor, such as the exhaust gas temperature sensor, sends intermittent noise. Technicians frequently encounter this fault after replacing the ECM if the new unit’s software version mismatches the vehicle’s network configuration.
Common Symptoms
- Intermittent Power Loss: Engine suddenly loses power, especially during high-load operations, due to corrupted torque messages.
- Erratic Gauge Readings: Dashboard instruments like tachometer or coolant temperature display random spikes or dropouts.
- Transmission Harsh Shifts: Transmission receives faulty data, causing delayed or jerky gear engagements under acceleration.
- Check Engine Light On: Amber warning lamp illuminates, often with a logged diagnostic trouble code for network errors.
Probable Causes
- CAN Bus Wiring Fault: Damaged or corroded twisted-pair wiring, especially near the engine harness connector, causing signal reflection.
- ECM Software Mismatch: Updated ECM firmware incompatible with older controller versions, producing false data errors.
- Faulty Sensor Transmitter: Defective exhaust gas temperature sensor sending out-of-range frames due to internal short circuit.
- Termination Resistor Failure: Missing or open 120-ohm termination resistor at the bus end, causing data echo and CRC errors.
Advanced Technical Analysis
The ECM’s microcontroller continuously monitors the J1939 data link for message integrity using a cyclic redundancy check (CRC). When SPN 613 FMI 19 triggers, the ECM has received a frame with a computed CRC that does not match the transmitted checksum. This typically occurs when a sender’s internal clock drifts or when electromagnetic interference (EMI) from high-current devices, such as the starter motor, corrupts the data packet during transmission.
From an electrical perspective, the CAN bus uses differential voltage levels (2.5V ± 1V on CAN_H and CAN_L). A common cause is a pinched wire in the chassis harness that creates intermittent shorts to ground, causing the recessive-to-dominant transition to fail. The ECM’s debouncing timer, typically 250 ms, must see three consecutive valid frames before clearing the fault. If the noise persists, the fault remains active.
When the fault is active, the ECM enters a safety fallback strategy: it substitutes the missing data with a default value (e.g., torque limit set to 50% of rated). This prevents uncontrolled operation but causes a noticeable power derate. For example, on a MAN D26 engine, the ECM reduces fuel injection quantity by 30% until valid data is restored, protecting the aftertreatment system from overheating.
Long-term diagnosis requires capturing the fault with a J1939 data logger during a road test. Technicians should monitor the suspect node’s transmit counter and error frame count. A real-world case on a Deutz TCD 7.8 revealed that a corroded pin in the 120-pin ECM connector caused intermittent contact, generating CRC errors only in high humidity. Replacing the connector and applying dielectric grease resolved the issue permanently.
Step-by-Step Troubleshooting Guide
- Inspect CAN Harness: Visually check twisted-pair wiring for abrasion, corrosion, or chafing near the ECM and transmission connectors.
- Measure Termination Resistance: With ignition off, measure resistance between CAN_H and CAN_L at the diagnostic port; should be 60 ohms.
- Check Sensor Outputs: Using a scope, verify the suspect sensor’s CAN frame timing and voltage levels per J1939 specification.
- Update ECM Software: Flash latest calibration from manufacturer to ensure compatibility with all network controllers and sensors.