SPN 6992 FMI 19: Meaning and Fix
SPN 6992 FMI 19 indicates that the Engine Cylinder Combustion Request message (PGN 65460) received by the ECM contains invalid or corrupted data for cylinder 1. This fault often appears after a software update or when a non-genuine ECU is installed. Technicians frequently encounter it when a faulty J1939 backbone or a misconfigured engine brake controller sends a malformed request to exclude cylinder 1 from combustion.
Common Symptoms
- Rough Idle: Cylinder 1 may be intermittently cut out, causing uneven engine rotation at idle.
- Misfire Detection: ECM logs cylinder 1 misfire counts due to unexpected combustion exclusion requests.
- Reduced Power: Engine enters torque derate mode to protect components from unbalanced firing.
- Check Engine Lamp: Steady amber MIL lamp on dash with stored SPN 6992 FMI 19 fault.
Probable Causes
- Corrupted J1939 Message: A controller on the bus sends a combustion request with invalid data bits for cylinder 1.
- ECM Software Mismatch: After ECU reprogramming, the combustion request mapping does not align with the OEM calibration.
- Faulty Engine Brake ECU: Engine brake controller outputs a false ‘exclude’ command for cylinder 1 during normal operation.
- CAN Bus Termination Issue: Incorrect termination resistors cause bit errors in the combustion request message frame.
Advanced Technical Analysis
The ECM microcontroller monitors the Engine Cylinder Combustion Request message for valid data ranges. SPN 6992 FMI 19 triggers when the received 2-bit field for cylinder 1 is either ’10b’ (Reserved) or ’11b’ (Not available/Do not care) instead of ’00b’ or ’01b’. This indicates a sender logic error or a corrupted message frame on the J1939 bus.
Electrically, the fault may arise from a floating or shorted CAN_H/CAN_L line that corrupts the 2-bit field during transmission. The ECM checks the message integrity via a debouncing timer; the fault becomes active only if the error persists for more than 5 consecutive messages. A single transient glitch will not set the code.
Upon activation, the ECM sets the cylinder 1 combustion request to ‘Include for Combustion’ (01b) as a safety fallback. Simultaneously, it commands a torque derate of 25% to prevent unbalanced cylinder loading. The engine will run on all cylinders, but power is limited until the fault is cleared and the CAN bus issue resolved.
Long-term prevention requires verifying that all J1939 nodes use correct PGN 65460 data mapping per SAE J1939-71. In workshops, this code commonly appears after installing a non-OEM engine brake controller. Always check the source address of the sender using a CAN analyzer. If the sender is the brake ECU, update its firmware or replace it with an OEM unit.
Step-by-Step Troubleshooting Guide
- Scan Bus Traffic: Use a J1939 analyzer to capture PGN 65460 and identify the source address sending invalid data.
- Verify ECU Calibration: Compare the ECM calibration version against the OEM spec; reflash if mismatch is found.
- Inspect CAN Termination: Measure resistance between CAN_H and CAN_L at the ECM connector; must be 60 ohms.
- Test Engine Brake Controller: Disconnect the engine brake ECU and check if SPN 6992 FMI 19 clears from active faults.