The J1939 Network #2 parameter, designated as Suspect Parameter Number (SPN) 1231, is a critical diagnostic data point used to monitor the operational status and integrity of the secondary Controller Area Network (CAN) bus, often referred to as the J1939-2 or “red” bus, within a vehicle or equipment architecture. Unlike SPNs that report a physical measurement like temperature or pressure, this SPN indicates the functional health of the communication network itself. It is utilized by any Electronic Control Unit (ECU) capable of acting as a network gateway or that is physically connected to the J1939 #2 backbone, including engine control modules (ECMs) from Cummins (e.g., ISX15, X15), Detroit Diesel (DD13, DD15, DD16), PACCAR (MX-11, MX-13), and Volvo (D11, D13, D16). In modern heavy-duty trucks and off-highway equipment, the primary J1939 bus (#1) typically handles powertrain control (engine, transmission, retarder), while the secondary bus (#2) is often dedicated to auxiliary systems such as aftertreatment control (DEF dosing, SCR), body controllers, and telematics gateways. SPN 1231 is therefore vital because a failure on this bus can lead to a complete loss of communication with emissions control systems, causing immediate power derates, forced regeneration lockouts, or vehicle speed limitations, making it a top-priority diagnostic parameter for any technician.
Technical Overview
SPN 1231 is not a measurement derived from a sensor or actuator in the traditional sense. Instead, it is a software-generated status value calculated by an ECU (typically the engine ECM or a dedicated gateway module) that monitors the health of the J1939 Network #2 communication bus. The engineering behind this parameter involves the ECM periodically transmitting a “Network Heartbeat” message or monitoring the bus for the presence of expected messages from other ECUs. The value of SPN 1231 is a discrete integer, not a continuous analog voltage or frequency. According to SAE J1939-73, the parameter’s value correlates to a specific network state. A value of ‘0’ typically indicates that Network #2 is operating normally and all expected communication is present. A value of ‘1’ or higher (often up to ‘3’ or ‘4’ depending on the OEM) indicates a fault, such as a bus-off condition, a missing node, or a physical layer failure (e.g., short circuit, open circuit). The signal type is a CAN data field embedded within a Parameter Group (PG) — in this case, the “Stop Start Broadcast” PG (PGN 0x00FEEE or similar, depending on OEM implementation). The normal operating range for SPN 1231 is strictly ‘0’ when the bus is healthy. Any non-zero value indicates an active or latched fault. The ECM determines this state by monitoring its own CAN controller status registers; if the CAN controller enters a “Bus Off” state due to excessive error frames, the ECM sets SPN 1231 to a fault value. For example, on a Detroit Diesel DD15 engine, the ECM (DDEC) continuously monitors the J1939-2 bus for the presence of the Aftertreatment Control Module (ACM) messages. If the ACM stops transmitting, SPN 1231 will be set to a non-zero value, triggering a diagnostic trouble code (DTC) with a Failure Mode Identifier (FMI) such as FMI 9 (Abnormal Update Rate) or FMI 14 (Root Cause Not Known).
J1939 Network Behavior
On the J1939 CAN bus, SPN 1231 is transmitted as part of a dedicated broadcast message, typically assigned to a Parameter Group Number (PGN) that is specific to network management or broadcast status. While the exact PGN varies by OEM, it is commonly found within the range of PGN 0x00FE00 to 0x00FEFF (Proprietary A or B) or within a standardized diagnostic PGN. The transmission rate for this parameter is not high-speed like engine data (e.g., 100 ms); it is typically broadcast at a slower, non-periodic rate, often once per second (1 Hz) or only upon a state change (event-driven). The Source Address (SA) for this message is the ECU that is acting as the network monitor or gateway, which could be the engine ECM (SA 0x00), a transmission ECU (SA 0x03), or a dedicated vehicle control unit (VCU). Other ECUs on the network, such as the Aftertreatment Control Module (ACM), the Anti-lock Braking System (ABS), or the Body Controller, do not directly transmit SPN 1231 but they consume the data. When a gateway ECU broadcasts a non-zero value for SPN 1231, other ECUs interpret this as a command to cease communication on the #2 bus or to enter a safe state. For instance, a PACCAR MX-13 engine ECM (SA 0x00) broadcasting SPN 1231 = 1 will cause the ACM (SA 0x23) to stop requesting DEF dosing, preventing potential damage from a corrupted bus. The network behavior is designed to isolate the faulty segment and prevent a cascading failure across the entire vehicle network.
Diagnostic Importance
Faults associated with SPN 1231 are considered critical because they directly impact the ability of the engine and aftertreatment systems to communicate. The ECM activates severe engine protection strategies when this parameter indicates a fault. On a Cummins ISX15, an active SPN 1231 fault will trigger a progressive power derate, often starting at 25% and escalating to a 50% power reduction within minutes if the condition persists. Additionally, the ECM will inhibit or lock out the Diesel Particulate Filter (DPF) regeneration process, as it cannot safely command the aftertreatment system without a reliable network. Ignoring an active fault code for this parameter can lead to catastrophic consequences: the DPF can become completely clogged with soot, requiring a costly off-vehicle cleaning or replacement; the Selective Catalytic Reduction (SCR) system may fail to inject DEF, leading to high NOx emissions and eventual catalyst damage; and in some cases, the vehicle may enter a “limp home” mode with a maximum speed of 5-10 mph. For example, a Volvo D13 engine with an active SPN 1231 fault will display a “Engine System Failure” warning on the dashboard and limit engine speed to 1400 RPM. The diagnostic importance cannot be overstated — this is a network-level fault that requires immediate attention to restore full vehicle functionality and prevent secondary damage to expensive emissions components.
Common Failure Patterns
Real-world failure scenarios for SPN 1231 are almost exclusively related to the physical layer of the J1939 #2 bus, not the ECUs themselves. The most frequent cause is wiring issues, specifically a short circuit between the CAN High (CAN_H) and CAN Low (CAN_L) wires, or a short to battery voltage or ground. This is common in areas where the network harness is exposed to chafing, such as near the frame rail, behind the cab, or near the exhaust aftertreatment system. A second common pattern is a failed termination resistor. The J1939 #2 bus requires two 120-ohm termination resistors at each end of the backbone. If one resistor fails (opens), the bus signal becomes severely degraded, causing communication errors that manifest as SPN 1231 faults. Sensor degradation is less common, but a failing ACM or DEF pump controller can generate excessive electrical noise on the bus, driving the network into a “Bus Off” state. Contamination from moisture or corrosion in Deutsch connectors (e.g., DT, DTM, or HD30 series) is a frequent issue in off-highway equipment from John Deere or Caterpillar, where the harness is exposed to mud, salt, and high-pressure washing. Calibration drift is not applicable here, as this is a digital status parameter. Mechanical failures, such as a pin pushed out of a connector during a recent repair, are also a leading cause of intermittent SPN 1231 faults.
Diagnostic Approach
The diagnostic strategy for any fault code involving SPN 1231 must begin with a systematic verification of the physical network layer. The essential tools include a digital multimeter (DMM) capable of measuring resistance and voltage, a J1939 breakout box or back-probe pins, and a high-quality oscilloscope (preferably 2-channel or 4-channel) for analyzing CAN bus waveforms. The first step is to disconnect the vehicle batteries and measure the resistance between CAN_H and CAN_L at the diagnostic connector (typically the 9-pin Deutsch connector). The expected value is approximately 60 ohms (two 120-ohm resistors in parallel). A reading of 120 ohms indicates one missing termination resistor; an open circuit (OL) indicates both are missing or a break in the backbone. Next, measure the voltage between CAN_H and ground, and CAN_L and ground with the batteries reconnected and key-on, engine-off. CAN_H should read approximately 2.5V DC, and CAN_L should read approximately 2.5V DC. A reading near 0V or 5V indicates a short to ground or power. An oscilloscope is then used
Fault Codes for SPN 1231
FMI 0: Data valid but above normal operational range (most severe)
This fault indicates the J1939 Network #2 (Stop Start Broadcast) data link voltage is above the normal operational range, typically exceeding 5.0V on the CAN_H line. In practice, this often occurs after a jump-start or when a non-J1939 compliant component is connected to the backbone. Technicians fr
View SPN 1231 FMI 0 Diagnostic Guide →
FMI 1: Data valid but below normal operational range (most severe)
The fault code SPN 1231 FMI 1 relates to the J1939 Network #2, particularly impacting the Stop Start Broadcast function. This fault indicates that the data is valid but falls below the normal operational range. Technicians frequently encounter this issue after a software update or ECM replacement, e
View SPN 1231 FMI 1 Diagnostic Guide →
FMI 2: Data erratic, intermittent or incorrect
SPN 1231 FMI 2 indicates erratic or corrupted data transmission within the secondary J1939 network’s Stop Start Broadcast messages. This fault commonly appears during engine start-stop cycling operations when multiple ECMs fail to maintain synchronized communication timing. Technicians frequently en
View SPN 1231 FMI 2 Diagnostic Guide →
FMI 3: Voltage above normal or shorted high
SPN 1231 FMI 3 indicates excessive voltage on the secondary J1939 network bus handling stop-start broadcast messages. This fault commonly appears in European commercial vehicles after ECM replacement or during harsh weather conditions when moisture infiltrates CAN bus connectors. The stop-start syst
View SPN 1231 FMI 3 Diagnostic Guide →
FMI 4: Voltage below normal or shorted low
SPN 1231 FMI 4 indicates voltage below normal on J1939 Network #2 affecting stop-start broadcast functionality. This fault commonly appears after battery replacement or alternator failure when the ECM detects insufficient voltage for proper network communication. The stop-start system requires stabl
View SPN 1231 FMI 4 Diagnostic Guide →
FMI 5: Current below normal or open circuit
SPN 1231 with FMI 5 is a critical fault code related to the J1939 network communication, specifically indicating an open circuit or below normal current in Network #2. This code often surfaces after an ECM replacement when connections are not properly secured. Technicians frequently encounter this d
View SPN 1231 FMI 5 Diagnostic Guide →
FMI 6: Current above normal or grounded circuit
SPN 1231 FMI 6 indicates excessive current or grounded circuit condition in the secondary J1939 network managing stop-start broadcast communications. This fault commonly appears during engine start attempts when the ECM detects abnormal current draw through the network termination resistors. Technic
View SPN 1231 FMI 6 Diagnostic Guide →
FMI 7: Mechanical system not responding properly
This fault indicates the J1939 Network #2 stop-start broadcast message is not receiving a proper mechanical response from a connected device, such as a transmission or auxiliary controller. The ECM expects a confirmation signal within a defined window; if missing, FMI 7 sets. In practice, this code
View SPN 1231 FMI 7 Diagnostic Guide →
FMI 9: Abnormal update rate
SPN 1231 FMI 9 indicates abnormal update rate issues within the J1939 Network #2 Stop Start Broadcast system. This fault commonly manifests during urban delivery operations when stop-start systems experience rapid cycling, causing ECM communication timing conflicts. The abnormal update rate disrupts
View SPN 1231 FMI 9 Diagnostic Guide →
FMI 11: Root cause not known
SPN 1231 FMI 11 typically arises in systems utilizing J1939 Network #2. This fault indicates an unknown root cause affecting network communication. Technicians often encounter this issue after performing software updates or replacing network-related hardware, such as the ECM. It is crucial to assess
View SPN 1231 FMI 11 Diagnostic Guide →
FMI 12: Bad intelligent device or component
SPN 1231 FMI 12 indicates a defective intelligent device within J1939 Network #2 controlling stop-start broadcast functions. This fault commonly appears after ECM software updates or when start-stop modules experience internal microprocessor failures. The defective component disrupts network communi
View SPN 1231 FMI 12 Diagnostic Guide →
FMI 13: Out of calibration
SPN 1231 FMI 13 indicates the J1939 Network #2 stop-start broadcast message is out of calibration. This typically occurs after an ECU replacement or software update where the internal timing parameters for the broadcast do not match the network master. Technicians often see this fault after swapping
View SPN 1231 FMI 13 Diagnostic Guide →
FMI 14: Special instructions
This fault indicates the Engine Control Module (ECM) has received a manufacturer-specific ‘special instructions’ request over J1939 Network #2, often related to stop-start system commands. Technicians frequently encounter this code after a forced DPF regeneration or after replacing the ECM, as the n
View SPN 1231 FMI 14 Diagnostic Guide →
FMI 18: Data valid but below normal operating range (moderately severe)
SPN 1231 with FMI 18 refers to data being valid yet below the expected operating range for J1939 Network #2. This fault often arises after replacing the ECM without proper configuration. The issue can affect communication protocols, leading to sub-optimal performance in connected systems. Technician
View SPN 1231 FMI 18 Diagnostic Guide →
FMI 31: Condition exists
SPN 1231 FMI 31 indicates a persistent condition exists within J1939 Network #2, specifically affecting stop-start system broadcast messages. This fault commonly manifests during fleet operations when multiple ECMs attempt simultaneous communication during engine restart sequences. Technicians frequ