Scania · J1939 Network #2 Communication CircuitMedium

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

SPN 1231 FMI 9 (FMI 9) — J1939 Network #2 - Abnormal Update Rate

4.8/5· 128 reviews

Quick Answer

SPN 1231 FMI 9 means the secondary J1939 datalink on a Scania truck has an abnormal update rate, indicating a communication problem rather than an engine mechanical issue. It is Medium severity and typically affects secondary systems without impacting engine performance directly.

Overview: Scania SPN 1231 FMI 9

Modern trucks run multiple J1939 datalink networks to keep message traffic organized, and SPN 1231 covers Network #2, a secondary bus often used for body controllers, trailer communication, or auxiliary instrument functions depending on the truck's configuration. ProfessionalDieselRepair.com sees this fault most commonly traced back to a damaged wiring backbone or a missing termination resistor rather than any single failed module, so working through the network-level checks first saves significant diagnostic time compared to swapping controllers at random.

Repair Snapshot

Time

1.5 - 3 Hours

Difficulty

Intermediate

Parts Cost

$40 - $300

Dealer Labor

$400+

Tools Required

  • Scania SDP3
  • Multimeter
  • Jaltest Diagnostic Tool
  • Texa Diagnostic Software

What SPN 1231 FMI 9 Means

SPN 1231 FMI 9 means the secondary J1939 datalink (Network #2) is experiencing an abnormal update rate, meaning messages aren't arriving as frequently or reliably as expected between modules communicating on that bus. This is a communication network fault rather than a mechanical engine problem, and it can cause secondary systems like the instrument cluster or certain body controllers to behave erratically depending on what's wired to that specific network. The engine typically continues running normally.

Symptoms Drivers Notice

  • MIL or warning lamp illuminated
  • Erratic or missing data on the instrument cluster or auxiliary displays
  • Possible communication faults with body controllers or trailer systems on that network
  • No direct engine performance impact in most cases

Most Likely Root Causes

Damaged or corroded backbone wiring on Network #2

Common

Physical damage or corrosion anywhere along the network's two-wire backbone can disrupt communication timing for every module connected to that bus.

Missing or failed termination resistor

Common

J1939 networks require proper 120-ohm termination at each end of the backbone; a missing or damaged resistor causes signal reflection and communication errors.

Water-intruded inline connector

Occasional

Moisture at a splice or connector point along the network path can create intermittent communication disruptions.

Failing module actively flooding the network with error frames

Rare

A single malfunctioning module can occasionally disrupt communication for the entire network, requiring isolation by disconnecting modules one at a time.

Common Misdiagnoses (Don't Waste Parts)

Replacing the instrument cluster or body controller without checking the network wiring

Why it happens: A parts-cannon approach assumes the module displaying erratic data is itself broken rather than a victim of poor network communication.

Do this instead: Check backbone wiring integrity and termination resistance before replacing any individual module reporting communication errors.

Assuming this is an engine-related fault requiring engine diagnostics

Why it happens: Any J1939 SPN code can be mistaken for an engine problem by techs unfamiliar with network architecture.

Do this instead: Recognize that Network #2 faults are communication-related and typically don't require engine-specific diagnostic steps.

Skipping the termination resistance check

Why it happens: It's an easy step to overlook when troubleshooting feels like it should focus on active components rather than passive wiring elements.

Do this instead: Always measure termination resistance early in the diagnostic process, since it's quick and can immediately point toward or away from a network-level cause.

Master Tech Commentary

Mechanic's Notes

Shop tip from ProfessionalDieselRepair.com: always check termination resistance before chasing individual modules on a network fault like this. A missing or damaged terminating resistor at either end of the backbone will produce exactly this kind of abnormal update rate symptom across multiple devices at once, and it's a five-minute check that can save hours of module-by-module troubleshooting.

Step-by-Step Diagnostic Procedure

  1. Step 1: Connect Scania SDP3 and confirm SPN 1231 FMI 9, noting which specific modules are reporting communication issues on Network #2.
  2. Step 2: Inspect the J1939 Network #2 connector and backbone wiring for corrosion, loose pins, or physical damage at splice points.
  3. Step 3: Check termination resistors at both ends of the Network #2 backbone using a multimeter - a healthy J1939 network typically reads around 60 ohms across the two data lines when properly terminated.
  4. Step 4: Inspect for water intrusion at any inline connectors along the network's wiring path, particularly at chassis-to-cab or chassis-to-trailer junctions.
  5. Step 5: Repair or replace any damaged wiring or connectors, verify proper termination resistance, and clear codes with SDP3 before confirming stable communication on a road test.

Live Data & Freeze-Frame Tips

In SDP3, review the network diagnostic log to see which specific modules are reporting missed or delayed messages, which helps localize whether the problem is isolated to one section of the backbone or affects the entire network uniformly.

Safety Warnings

  • Turn the ignition off before disconnecting any network wiring or module connectors.
  • Use proper anti-static precautions when handling electronic control modules.
  • Inspect connectors for corrosion carefully to avoid further damaging fragile pins.
  • Verify all connectors are fully reseated and locked before returning the truck to service.

When to Limp In vs Tow

Towing is not necessary for this code since engine performance is typically unaffected. Address it when convenient, particularly if it's affecting trailer communication or other safety-related auxiliary systems.

Prevention Tips for Fleets & Owner-Operators

  • Inspect network backbone wiring and connectors during routine electrical system PM checks.
  • Verify termination resistors are intact any time network wiring is serviced or modules are added.
  • Protect inline connectors from moisture exposure with dielectric grease and proper seals.
  • Address intermittent instrument cluster glitches early before they develop into a stored network fault code.

Related Fault Codes

SPN 639 FMI 9

J1939 Network #1 abnormal update rate, the primary datalink network with a similar fault pattern.

SPN 630 FMI 12

Calibration memory fault, worth checking if network communication issues are accompanied by module programming errors.

SPN 629 FMI 12

Controller #1 (ECM) bad intelligent device fault, relevant if the ECM itself appears to be contributing to network communication problems.

Frequently Asked Questions

Can I drive with SPN 1231 FMI 9 active?

Yes, engine performance is typically unaffected by this network communication fault, though you may notice erratic behavior on displays or systems connected to Network #2.

How do I reset this code without a scanner?

A battery disconnect may temporarily clear the stored fault, but it will return once communication issues resume if the underlying wiring or termination problem isn't repaired.

Does this code affect engine performance?

Generally no, since Network #2 is typically used for secondary systems rather than core engine control, though this can vary depending on the truck's specific configuration.

What is J1939 Network #2 used for on Scania trucks?

It varies by configuration, but Network #2 commonly handles body builder connections, trailer communication, or certain auxiliary instrument functions separate from the primary engine control network.

How do I check network termination resistance?

With the ignition off, measure resistance across the two data lines (CAN High and CAN Low) at the diagnostic connector - a properly terminated J1939 network typically reads around 60 ohms.

Can a single bad module cause this fault for the whole network?

Yes, in rare cases a malfunctioning module can flood the network with error frames or disrupt timing for all connected devices, requiring isolation by disconnecting modules one at a time to identify the culprit.