SPN 6992, labeled Engine Cylinder 1 Exclude from Combustion Request, is a SAE J1939 control parameter that allows an external system or controller to command the engine ECU to deliberately skip cylinder 1 from participating in the combustion cycle. Unlike fault-driven cylinder deactivation, this parameter represents an intentional, commanded exclusion — a calibration or operational request rather than a failure response. It is commonly encountered in advanced powertrain architectures found on Cummins ISX15, X15, and Westport HPDI natural gas platforms, as well as in hybrid-electric integration systems from Volvo and PACCAR where auxiliary controllers coordinate with the engine ECM during regeneration events, engine braking optimization, or cylinder-selective fuel strategies. Understanding this parameter is essential for diagnosing abnormal combustion behavior, misfire attribution, and emissions non-conformance in modern electronically managed diesel and alternative-fuel engines.
Technical Overview
The engineering basis for SPN 6992 lies in the engine ECM’s ability to selectively suppress fuel injection to individual cylinders on a per-cycle basis. When the exclusion request is active — encoded as 00b in the two-bit data field — the ECM inhibits the injector driver circuit for cylinder 1, preventing fuel delivery during that combustion event. The parameter itself is not derived from a physical sensor; it is a commanded value originating from a requesting controller, such as a hybrid vehicle control module (HVCM), an aftertreatment control module (ACM), or a transmission ECU performing powertrain torque coordination. The signal is purely digital, transmitted as a CAN message payload over the J1939 network. The four possible states are precisely defined: 00b (Exclude from Combustion), 01b (Include for Combustion), 10b (Reserved — not to be used in production calibrations), and 11b (Not available/Do not care — the engine ECM applies its own internal strategy without external direction). In normal operation, the parameter resolves to 01b during standard load cycles, while 11b is typical during cold start phases when the requesting controller has not yet initialized or has no preference to assert.
J1939 Network Behavior
SPN 6992 is transmitted as part of the Engine Cylinder Combustion Request Parameter Group (PG), which encapsulates similar two-bit exclusion requests for each individual cylinder — SPN 6992 through SPN 7003 cover cylinders 1 through 12 respectively in most implementations. The PGN associated with this parameter group is proprietary in many OEM implementations, transmitted using Peer-to-Peer (PDU1, PS = Destination Address) messaging from the requesting controller to the engine ECM. Transmission rates typically fall between 10 ms and 100 ms depending on the urgency of the combustion control request; during active hybrid torque intervention events, the cycle time may drop to 10 ms to maintain precise combustion control. The source address is that of the originating controller — commonly the HVCM or ACM — while the destination address targets the engine ECM (source address 0x00 on most North American truck platforms). Sniffing this traffic with a J1939-capable tool such as the Cummins INSITE, Detroit Diesel DiagnosticLink, or a third-party analyzer like the Vector CANalyzer will reveal whether the exclusion command is being properly asserted and acknowledged, and whether the engine ECM is confirming receipt through its own status broadcast PGNs.
Diagnostic Importance
When SPN 6992 is incorrectly asserted or remains in the 00b exclusion state outside of a commanded event, the consequences for engine operation are significant. Persistent cylinder 1 exclusion causes unbalanced torque output, elevated vibration, increased HC and CO tailpipe emissions due to unburned fuel passing through to the aftertreatment system, and potential diesel particulate filter (DPF) loading acceleration. In turbocharged applications — virtually all modern on-highway engines — asymmetric combustion loading can generate compressor surge events and turbocharger speed imbalance. Cummins engine protection logic, for instance, monitors per-cylinder contribution through individual cylinder power balance tests; if cylinder 1 is persistently excluded by a stuck command, the ECM may log a companion fault for cylinder imbalance and initiate a derate if operating hours under that condition exceed threshold limits. Ignoring an active or pending fault related to this SPN risks catalyst thermal damage in SCR systems relying on consistent exhaust enthalpy, warranty non-conformance in fleet environments, and potential mechanical damage from vibration-induced component fatigue over extended duty cycles.
Common Failure Patterns
The most frequently encountered failure scenario is a stuck exclusion command originating from a malfunctioning HVCM or ACM that has entered a fault state and is broadcasting 00b continuously. This is commonly seen on Volvo D13 hybrid platforms and PACCAR MX-13 installations where the hybrid controller loses communication with the battery management system and defaults to a protective state that includes cylinder exclusion requests. A second common pattern involves J1939 message timeout — the engine ECM receives no update from the requesting controller, transitions the parameter internally to a default state, and logs a communication fault that can be misidentified as an injector or combustion hardware problem. CAN bus wiring faults — particularly shield continuity failures on the twisted pair between the HVCM and engine ECM — cause intermittent message corruption that manifests as sporadic exclusion commands. Technicians on John Deere PowerTech and Cummins QSX-series industrial engines have also documented calibration mismatches following ECM reprogramming where the cylinder exclusion enable/disable feature flag was incorrectly set, causing the exclusion request PGN to be ignored entirely.
Diagnostic Approach
Begin diagnosis by connecting a J1939-compliant diagnostic tool — Cummins INSITE, Detroit DiagnosticLink, or Volvo VCADS Pro — and capturing live data for SPN 6992 under operating conditions. Confirm the current bit state: if the value reads 00b outside of a known hybrid intervention event, the exclusion is incorrectly asserted. Use a CAN bus analyzer to identify the source address of the transmitting controller and verify whether the exclusion message is originating from the correct node. Inspect the J1939 datalink wiring between the requesting controller and engine ECM for shield integrity, terminal resistance (120Ω termination at each end of the backbone), and voltage levels (CAN-H nominally 2.5–3.5V, CAN-L nominally 1.5–2.5V during dominant bit). Clear all active DTCs and perform a key-cycle reset to determine if the exclusion command clears; persistent 00b after reset points to a controller hardware fault or corrupted calibration in the requesting ECU. If the parameter reverts correctly to 01b after clearing, suspect intermittent CAN communication or a thermal-related controller fault in the HVCM or ACM. Escalate to OEM factory software — Cummins INSITE Guided Diagnostics, Detroit DDL Guided Step Tests, or Volvo VCADS parameter verification routines — when hardware checks are inconclusive, as these platforms provide cylinder-level actuator tests and combustion request override capabilities that generic scan tools cannot replicate.
Fault Codes for SPN 6992
FMI 19: Received network data in error
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