How to Read J1939 Fault Codes: SPN, FMI and SA Explained for Technicians

If you work on modern trucks or heavy equipment, you read fault codes every day — but the string "SPN 3226 FMI 1 SA 61" only helps if you know how to decode it. This guide explains exactly how J1939 diagnostic trouble codes are built, how to read each part, and how to turn a code into a root cause. It's written for technicians who want to actually diagnose, not just clear the light.

Why J1939 exists

In the early 1990s, every heavy-duty manufacturer ran its own proprietary diagnostic protocol — Cummins used one system, Detroit another, Caterpillar a third. A shop needed a different scan tool and cable for every brand. When a Freightliner with a Cummins engine, an Allison transmission and Meritor WABCO brakes rolled in, the technician needed three or four interfaces just to read everything.

SAE J1939 solved that. It unified all the electronic modules on a single high-speed CAN bus — running at 250 kbps through a 9-pin Deutsch connector — so one scan tool can talk to the whole truck. It replaced the older J1708/J1587 standard and is now the common language across Cummins, Detroit, PACCAR, Navistar and Volvo/Mack platforms.

Important: you cannot read J1939 codes with a typical 16-pin OBD-II car scanner. Heavy trucks use a 9-pin Deutsch (or the newer green Type 2 9-pin) connector, and the tool has to speak the J1939 CAN protocol.

The anatomy of a J1939 fault code

Every J1939 diagnostic trouble code (DTC) is built from three identifiers: SA, SPN and FMI. Read them together and you have a complete picture of what failed, where, and how.

SA — Source Address (where the code came from)

The SA tells you which module on the network reported the fault — the engine ECM, the transmission controller, the brake system, and so on. For example, SA 0 is typically the engine ECM. This matters because the same SPN can be reported by different modules; the SA tells you which one is talking.

SPN — Suspect Parameter Number (what has the problem)

The SPN identifies the specific parameter, sensor or component involved. There are more than 10,000 defined SPNs, covering everything from coolant temperature and fuel rail pressure to DEF tank level, exhaust gas temperature and transmission output shaft speed. Think of the SPN as the "what."

FMI — Failure Mode Identifier (how it failed)

The FMI is a standardized code (0–31, 32 defined modes) that describes the nature of the failure. Think of it as the "how." A few of the most common you'll see:

• FMI 0 — data valid but above normal range, most severe (e.g. dangerously high)
• FMI 1 — data valid but below normal range, most severe
• FMI 2 — data erratic, intermittent or incorrect
• FMI 3 — voltage above normal / shorted high
• FMI 4 — voltage below normal / shorted low
• FMI 5 — current below normal or open circuit
• FMI 7 — mechanical system not responding properly
• FMI 31 — condition exists

The same FMI numbers mean the same thing on every J1939-compliant truck — that consistency is what makes the system so useful once you learn it.

Decoding a code, step by step

Let's decode a real example: SPN 3226 / FMI 1.

• SPN 3226 = the aftertreatment DEF tank level (or a related SCR outlet parameter, depending on the platform)
• FMI 1 = data valid but below normal range

Put together: the system is reading a DEF-related value below its expected range. That immediately narrows your diagnosis to a wiring issue, a failed sensor, or an actually empty tank — not a DEF quality or dosing problem. You've eliminated half the possibilities before you've even picked up a multimeter.

Another example: SPN 91 / FMI 2 means the accelerator pedal position sensor (SPN 91) is reporting erratic data (FMI 2) — pointing you at the pedal sensor, its connector, or its wiring.

This decoding pattern — look up the SPN, look up the FMI, combine them into a root cause — works for every J1939 fault, no matter the engine make. That's the whole point of the standard.

From code to root cause: the workflow

A code tells you where to start, not what to replace. A disciplined workflow:

1. Record SA, SPN and FMI together, plus whether the code is active or stored (inactive). Intermittent/stored codes often point to wiring or connector problems rather than a dead component.
2. Cross-reference the SPN/FMI in your diagnostic software or an OEM database to get the exact parameter and the manufacturer's troubleshooting tree.
3. Test the physical component, wiring and connectors. Use a multimeter to verify voltage, resistance and continuity. For example, a DEF dosing valve solenoid typically reads around 10–15 ohms — an open reading points to a broken wire or failed coil. Always back-probe connectors; never pierce wire insulation.
4. Fix the root cause, clear the codes, and run a system check to confirm the fault doesn't return.

Most codes come down to the unglamorous basics: dirty filters, aging sensors, corroded connectors and poor wiring. Outdated module firmware can also cause communication glitches that throw codes with no physical fault.

What you need to read J1939 codes properly

Two things: an RP1210-compliant adapter to physically connect to the CAN bus, and the diagnostic software that decodes and troubleshoots the codes.

Common professional adapters include the Nexiq USB-Link 3, DG DPA 5 and Noregon DLA+. On the software side, the real advantage of dealer-level programs is that they don't just show the code — they provide guided troubleshooting, wiring diagrams and repair recommendations tied to each SPN/FMI. That's the difference between a generic reader and a tool that actually walks you to the fix:

• Cummins INSITE — guided diagnostics for Cummins engines
• Detroit DiagnosticLink (DDDL) — for Detroit engines and Freightliner
• PACCAR ESA — for Kenworth and Peterbilt
• Volvo & Mack Premium Tech Tool (PTT) — for Volvo and Mack
• Nexiq eTechnician — multi-brand, if your shop sees mixed traffic
• The 25-program Nexiq bundle — if you want every major brand covered in one install

A quick word on J1708/J1587

On trucks built before roughly 2007 you'll still encounter the older J1708/J1587 protocol. It runs much slower (9600 baud) and uses PID/SID identifiers instead of SPNs, but it uses the same 32 FMI failure modes. Many 9-pin connectors still carry J1708 on pins G and H for backward compatibility, which is why some software (and the right adapter) can read both. If you service older equipment, make sure your tool covers J1587 as well as J1939.

Bottom line

A J1939 fault code isn't a mystery — it's a structured message. SA tells you which module is reporting, SPN tells you what parameter is affected, and FMI tells you how it failed. Decode all three and you've already narrowed the diagnosis before touching a wire. The right adapter plus dealer-level software for your engine turns those numbers into guided troubleshooting and a faster, more accurate repair.

We supply and remotely install the dealer-level diagnostic software for every major truck and engine brand via TeamViewer. Not sure which tool or adapter fits your fleet? Message us on WhatsApp (+51 941 033 487) and we'll confirm before you buy.

---

Sources: this article draws on public technical explanations of the SAE J1939 standard from industry references including OTR Performance, Simma Software, J1939 Hub, PrimoDeTech, Car Code Finder and Torque Edge, alongside the SAE J1939 standard's defined SPN/FMI structure. Always follow the specific OEM troubleshooting procedure for your engine and fault code.