SPN 1231 FMI 16: Meaning and Fix
SPN 1231 FMI 16 identifies a moderately severe condition on J1939 Network #2 where broadcasted data values exceed the defined normal operating range. Per SAE J1939-73, this fault activates when the Stop Start Broadcast parameter group reports anomalous signal levels persistently. Technicians commonly encounter this fault on MAN TGX and Mercedes-Benz Actros trucks after retrofitting telematics gateways, where added CAN nodes introduce excessive bus load, pushing network message timing beyond acceptable thresholds.
Common Symptoms
- Intermittent CAN Dropouts: Network #2 experiences repeated message loss events, causing sporadic communication failures between ECM, transmission, and body controllers.
- Delayed Engine Response: Engine torque commands exhibit measurable response lag due to corrupted or delayed broadcast messages across the J1939 secondary network segment.
- Active Fault Lamp Illumination: The amber warning lamp activates persistently, logged alongside related network SPNs, indicating sustained above-range broadcast data conditions.
- Stop-Start System Disabled: Automatic engine stop-start functionality is deactivated by the ECM as a protective response to unreliable Stop Start Broadcast parameter group signals.
Probable Causes
- Excessive CAN Bus Load: Addition of unauthorized telematics nodes or aftermarket gateways increases network utilization beyond the 80% bus load threshold defined by Bosch CAN specifications.
- Termination Resistor Failure: Missing or degraded 120-ohm termination resistors at network endpoints cause signal reflections, distorting broadcast message amplitude above normal operating parameters.
- ECM Firmware Incompatibility: Mismatched ECM software versions across networked control units generate conflicting broadcast cycles, violating SAE J1939-21 message timing and priority arbitration rules.
- Shielded Harness Degradation: Corroded or damaged twisted-pair shielding on Network #2 wiring introduces electromagnetic interference, elevating broadcast data signal levels beyond calibrated thresholds.
Advanced Technical Analysis
The ECM continuously monitors J1939 Network #2 message frames using internal CAN controller registers. For SPN 1231 FMI 16, the microcontroller compares received Stop Start Broadcast parameter group values against factory-calibrated upper thresholds stored in non-volatile memory. When decoded signal values persistently exceed the normal range, the diagnostic executive increments a fault counter. Once the counter surpasses the manufacturer-defined debounce limit, typically 10 consecutive detection cycles per Deutz and MAN ECM calibration data, the DTC is confirmed and stored.
Electrically, FMI 16 on Network #2 frequently originates from bus voltage irregularities rather than software alone. Bosch factory documentation specifies J1939 CAN High and CAN Low differential voltage must remain between 1.5V and 2.5V during dominant bit states. Termination resistance outside the 108–132-ohm acceptance band causes signal overshoot, extending dominant bit duration beyond the 1-microsecond nominal width. This timing violation causes receiving nodes to misinterpret broadcast message data bytes, artificially inflating decoded parameter values above the normal operating range.
Upon confirming SPN 1231 FMI 16, Mercedes-Benz and MAN ECM safety strategies initiate a controlled fallback mode. The Stop-Start control function is immediately suspended, preventing automatic engine shutdown events that could destabilize the compromised network. Some implementations also enforce a moderate torque derate of approximately 10–15% to reduce overall system communication demands. The ECM records freeze-frame data including engine speed, coolant temperature, and network bus load percentage at fault confirmation time, providing technicians with critical diagnostic context for root cause isolation.
Long-term diagnostic strategy requires CAN bus load analysis using tools such as the Softing CANalyzer or PEAK PCAN-USB adapter, measuring real-time frame utilization on Network #2. Workshops frequently discover this fault after fleet operators install non-OEM tracking devices without proper CAN gateway isolation. Preventive measures include enforcing strict node count limits per SAE J1939-11 physical layer specifications and verifying termination resistance with a calibrated ohmmeter before and after any wiring modification. Periodic harness inspection intervals of 100,000 km are recommended by MAN Truck & Bus service guidelines.
Step-by-Step Troubleshooting Guide
- Measure Bus Termination: Disconnect all ECUs and measure Network #2 resistance between CAN High and Low; verify reading falls within 55–65 ohms combined termination value.
- Analyze CAN Bus Load: Connect a J1939-compatible analyzer tool and capture live network traffic; confirm bus utilization remains below 80% during normal engine operating conditions.
- Inspect Harness Shielding: Physically inspect twisted-pair shielding continuity along Network #2 harness runs; repair any corroded shield grounds contributing to electromagnetic interference and signal distortion.
- Verify ECM Software Versions: Use OEM diagnostic software to confirm all networked control units share compatible firmware versions, eliminating broadcast timing conflicts causing above-range parameter readings.