Peterbilt · J1939 Network #2 (Secondary CAN Bus)High

Peterbilt SPN 1231 FMI 9: J1939 Network #2 Communication Fault

SPN 1231 FMI 9 (FMI 9) — J1939 Network #2 abnormal update rate — the secondary CAN bus is not delivering messages at the expected frequency.

4.8/5· 128 reviews

Quick Answer

SPN 1231 FMI 9 on a Peterbilt means the secondary J1939 CAN network is not delivering messages at the expected rate. Check termination resistors, harness integrity, and module power before deep electrical diagnosis.

Overview: Peterbilt SPN 1231 FMI 9

Peterbilt SPN 1231 FMI 9 is a J1939 Network #2 communication fault indicating that messages on the secondary CAN bus are arriving at an abnormal (too slow or absent) rate. J1939 Network #2 carries time-sensitive data between the aftertreatment module, transmission controller, and sometimes body controllers on Peterbilt platforms. When FMI 9 is logged, the ECM has detected a breakdown in the expected message cadence, which can prevent the aftertreatment controller from reporting DEF consumption and SCR status — potentially triggering a derate. Correct diagnosis requires understanding the full CAN topology and using proper J1939-aware tools. Technicians at ProfessionalDieselRepair.com recommend verifying termination resistors and module power supply before chasing individual wire faults.

Repair Snapshot

Time

2 - 5 Hours

Difficulty

Advanced

Parts Cost

$20 - $400

Dealer Labor

$600+

Tools Required

  • PACCAR Davie4
  • Texa Diagnostic Tool
  • Digital Multimeter (Ω mode)
  • CAN Bus Termination Resistor Set (120 Ω)
  • Wiring Diagram for Vehicle CAN Architecture

What SPN 1231 FMI 9 Means

Peterbilt SPN 1231 FMI 9 is stored when the ECM detects that messages on J1939 Network #2 are arriving less frequently than required, or not at all. SPN 1231 is the J1939 Network #2 parameter — the secondary high-speed CAN bus that typically carries aftertreatment, transmission, or body controller communications depending on vehicle configuration. FMI 9 (abnormal update rate) means the receiving module is not seeing expected parameter group numbers (PGNs) from one or more transmitting modules on that network. Root causes include a damaged CAN harness, missing or incorrect termination resistors, a defective node pulling the bus to a dominant state, or a module that has lost power.

Symptoms Drivers Notice

  • Multiple communication-related fault codes active alongside SPN 1231 FMI 9.
  • Aftertreatment or transmission control faults appearing without mechanical cause.
  • Engine derate because the ECM cannot confirm aftertreatment status from the aftertreatment control module.
  • Instrument cluster warnings or missing gauge readings.
  • Modules going offline and becoming unreachable during diagnostic scanning.

Most Likely Root Causes

Damaged or corroded CAN harness between modules

Common

Chafing or moisture intrusion in the secondary CAN harness breaks continuity on CAN-High or CAN-Low, preventing messages from reaching the ECM and triggering FMI 9.

Missing or failed CAN bus termination resistor

Common

Each J1939 segment requires two 120 Ω termination resistors. A resistor that has drifted out of tolerance or opened causes signal reflections that corrupt PGN delivery timing.

Module loss of power or ground on secondary network

Occasional

If a module connected to J1939 Network #2 loses its ignition supply or ground, it stops transmitting expected PGNs, causing the ECM to log FMI 9 for those missing messages.

Common Misdiagnoses (Don't Waste Parts)

Parts-cannon replacement of the aftertreatment control module

Why it happens: The aftertreatment module often disappears from the module list during a CAN fault, leading technicians to replace it even though the module is fine but offline due to a broken harness.

Do this instead: Confirm the module has power and ground before condemning it. Measure supply voltage at the module connector.

Replacing the ECM instead of fixing the CAN harness

Why it happens: A long list of communication faults across multiple modules is sometimes blamed on a failed ECM.

Do this instead: A failing ECM rarely causes a single-network communication fault. Confirm CAN bus resistance and topology before considering ECM replacement.

Overlooking the termination resistors

Why it happens: Termination resistors are small, inexpensive, and often overlooked because they rarely fail.

Do this instead: Measure both 120 Ω resistors with a multimeter as a standard step in any CAN bus diagnostic. It takes less than two minutes.

Master Tech Commentary

Mechanic's Notes

J1939 Network #2 faults are notoriously time-consuming to trace without proper CAN topology documentation. At ProfessionalDieselRepair.com we always start with a full module scan using PACCAR Davie4 or Texa to identify which modules have gone silent — the silent module is downstream of the break. A missing module in the scan is worth more than any fault code description. Check the chassis harness at known flex points: the frame rail near the fifth wheel and the harness boot through the cab firewall. On Peterbilt 579 and 389 platforms, aftertreatment module connectors near the DEF tank are a recurring corrosion site for the secondary CAN network.

Step-by-Step Diagnostic Procedure

  1. Step 1: Connect PACCAR Davie4 or a Texa diagnostic interface to list all active and inactive fault codes. Identify every module reporting communication errors — this map reveals which segment of the CAN network is affected.
  2. Step 2: With the ignition OFF, locate the J1939 Network #2 termination resistors (typically two 120 Ω resistors, one at each end of the bus segment). Disconnect both resistors and measure resistance at each. A reading significantly above or below 120 Ω indicates a failed terminator.
  3. Step 3: Measure resistance between the CAN-High and CAN-Low wires on the secondary network with both termination resistors disconnected. Normal point-to-point resistance is open (no continuity). Any low resistance indicates a wire short between the two CAN lines.
  4. Step 4: Inspect the CAN harness backbone — particularly harness junctions near the chassis frame rail, the firewall feedthrough, and the aftertreatment module connector — for chafed insulation, water intrusion, or corrosion.
  5. Step 5: After repairing harness damage or replacing a defective termination resistor, reconnect modules and use PACCAR Davie4 or Texa live data to confirm all expected PGNs are being received at their normal rate before clearing codes.

Live Data & Freeze-Frame Tips

In PACCAR Davie4 or Texa, navigate to the module communication status screen to identify which modules are online versus offline. An offline module pinpoints the broken network segment. In J1939 live data mode, confirm PGNs from the aftertreatment module (typically PGN 65110, 64892, or similar) are arriving at their specified rate (usually 1 Hz). Intermittent dropouts visible in live data indicate a marginal connection rather than a hard fault.

Safety Warnings

  • Always perform CAN bus resistance tests with the ignition OFF and all modules de-energized for accurate readings.
  • Do not disconnect multiple modules simultaneously — re-connect them one at a time and check bus resistance after each to avoid introducing a new fault.
  • Wear appropriate PPE when inspecting the chassis harness under the vehicle.
  • Use a wiring diagram specific to the vehicle build date before cutting or splicing CAN harness wires — multi-generation trucks use different network topologies.

When to Limp In vs Tow

Tow the vehicle if the derate has reduced power below a safe level for highway operation, or if the aftertreatment module is completely offline and the truck is at risk of a forced idle shutdown due to missing DEF quality or DPF data.

Prevention Tips for Fleets & Owner-Operators

  • Inspect CAN harness boots and grommets at the firewall and frame rail during each annual preventive maintenance service.
  • Apply dielectric grease to all outdoor-facing J1939 connector terminals, especially at the DEF module and aftertreatment housing.
  • After any body or trailer modification near the chassis, inspect the CAN harness for contact with new hardware.
  • Verify termination resistor values whenever replacing a major module on the secondary CAN network.

Related Fault Codes

SPN 1231 FMI 14

J1939 Network #2 special instruction — often accompanies FMI 9 when the network fault has escalated.

SPN 3364 FMI 9

DEF quality sensor abnormal update rate — a common secondary fault when the aftertreatment module drops off J1939 Network #2.

SPN 4094 FMI 9

DPF soot load abnormal update rate — another aftertreatment parameter that goes missing when the secondary CAN bus fails.

Frequently Asked Questions

What is Peterbilt SPN 1231 FMI 9?

SPN 1231 is J1939 Network #2 (the secondary CAN bus). FMI 9 means the ECM is not receiving messages from one or more modules on that network at the expected rate.

Does SPN 1231 FMI 9 cause a derate?

Yes. If the aftertreatment control module stops reporting over J1939 Network #2, the ECM cannot confirm SCR and DPF status, which typically triggers a derate or shutdown timer.

How do I test J1939 Network #2 termination resistors?

With the ignition off and both termination resistors disconnected, measure resistance across each one. Both should read approximately 120 Ω. Connect both and measure at the bus — you should read approximately 60 Ω.

Which modules use J1939 Network #2 on a Peterbilt?

Typically the aftertreatment control module, transmission controller, and sometimes the ABS or body controller are on the secondary network. Consult the vehicle-specific wiring diagram for exact topology.

Can a bad aftertreatment module cause SPN 1231 FMI 9?

Yes, but confirm the module has power and ground before replacing it. A module that is offline due to a blown fuse will produce the same fault as one that has failed internally.

How long does it take to diagnose Peterbilt SPN 1231 FMI 9?

Simple faults such as a failed termination resistor take under an hour. Tracing a harness break in the chassis backbone can take 3–5 hours depending on vehicle configuration.