SPN 2029 FMI 2: Meaning and Fix
SPN 2029 FMI 2 indicates that the data received from Source Address 29 is erratic, intermittent, or incorrect per the J1939-81 network definition. This fault commonly appears after replacing a transmission ECU or adding an aftermarket device that conflicts with the existing CAN bus node address. Technicians often encounter this when a new component fails to properly arbitrate its source address, causing corrupted or missing messages.
Common Symptoms
- Intermittent data loss: ECU loses communication with SA 29 device, causing sporadic warning lamps and data gaps on the bus.
- Erratic component behavior: Device assigned to SA 29 may cycle on/off or output implausible values under varying engine loads.
- CAN bus errors logged: Network error counters increment; other ECUs report timeout or CRC failures related to SA 29 messages.
- Diagnostic tool instability: Service tool shows fluctuating or frozen parameters from SA 29, often requiring multiple connection attempts.
Probable Causes
- Faulty SA 29 node: Internal microcontroller failure or corrupted firmware on the device assigned to source address 29.
- CAN bus termination: Incorrect or missing 120-ohm termination resistors cause signal reflections that corrupt SA 29 data.
- Wiring harness damage: Chafed or corroded CAN_H/CAN_L wires near SA 29 device introduce intermittent shorts or opens.
- Address conflict: Two ECUs programmed with the same source address 29 cause bus arbitration errors and erratic data.
Advanced Technical Analysis
The ECM continuously monitors the consistency of messages from SA 29 using rolling counters and CRC checks. When the expected counter sequence is broken or CRC mismatches occur across multiple consecutive frames, the diagnostic sets FMI 2. This indicates the data stream is no longer deterministic, often due to noise or a failing transceiver on the transmitting node.
Electrical analysis reveals that debouncing timers in the receiving ECU wait for three to five consecutive valid messages before clearing the fault. Intermittent glitches from loose connectors or marginal supply voltage at SA 29 cause the timer to reset repeatedly, locking the fault active. Oscilloscope measurements on the CAN bus often show amplitude anomalies below the differential threshold of 1.5 V.
As a safety fallback, the ECM typically freezes any control strategy relying on SA 29 data and may initiate a torque derate if the signal is critical for drivetrain coordination. For example, if SA 29 belongs to a retarder controller, the ECM will disable retarder operation and log a related SPN 520197 FMI 31 to indicate a substitute value is used.
Long-term resolution requires verifying that the SA 29 device firmware matches the OEM’s latest release. In workshop practice, this fault frequently follows an ECU swap where the replacement unit was not correctly programmed with the original source address. Preventative measures include using shielded twisted-pair cable and ensuring all bus nodes share a common ground reference to minimize common-mode noise.
Step-by-Step Troubleshooting Guide
- Verify node address: Use a J1939 diagnostic tool to list all active source addresses and confirm only one device claims SA 29.
- Inspect bus termination: Measure resistance between CAN_H and CAN_L at the backbone; should read 60 ohms (±10%) with power off.
- Check wiring integrity: Perform a continuity and insulation resistance test on CAN_H, CAN_L, and shield from SA 29 to the nearest junction.
- Test transceiver output: Monitor SA 29 node output with an oscilloscope; verify dominant/recessive levels and clean bit transitions without ringing.
