Diesel Technician Training
Understanding how fault codes work — and how to follow a diagnostic flow — is the difference between a fast, accurate repair and an expensive parts cannon. This guide covers the fundamentals every diesel technician needs.
How SPN/FMI Works
SPN (Suspect Parameter Number) identifies the system or component that has a fault. Think of it as the "what" — which sensor, actuator, or circuit is involved.
FMI (Failure Mode Identifier) identifies how the component failed. Think of it as the "how" — whether the signal is too high, too low, open circuit, short to ground, or something else.
When you're ready to work on the truck, reference the torque specs guide for fastener values, fluid capacities for fill specs, and the sensor locations guide to find components on your specific platform.
| FMI | Meaning |
|---|---|
| 0 | Data valid but above normal operating range |
| 1 | Data valid but below normal operating range |
| 2 | Data erratic, intermittent, or incorrect |
| 3 | Voltage above normal or shorted high |
| 4 | Voltage below normal or shorted low |
| 5 | Current below normal or open circuit |
| 6 | Current above normal or grounded circuit |
| 7 | Mechanical system not responding properly |
| 8 | Abnormal frequency, pulse width, or period |
| 9 | Abnormal update rate |
| 10 | Abnormal rate of change |
| 11 | Root cause not known |
| 12 | Bad intelligent device or component |
| 13 | Out of calibration |
| 14 | Special instructions |
| 19 | Received network data in error |
Example: SPN 3251 FMI 0 — SCR Catalyst Efficiency, data valid but above normal range. This means the SCR is not converting NOx at the expected rate — the signal is valid, but the efficiency is too low.
How OBD-II Works
OBD-II (On-Board Diagnostics II) is the standardized diagnostic protocol used on light-duty vehicles (under 14,000 lbs GVWR) and diesel pickups. It uses P-codes (Powertrain), U-codes (Network), B-codes (Body), and C-codes (Chassis).
P-code structure: P0xxx = generic (SAE standard), P1xxx = manufacturer-specific. The second digit identifies the system (fuel, ignition, emissions, etc.), and the last two digits identify the specific fault.
Example: P0087 — Fuel Rail/System Pressure Too Low. This is a generic SAE code that applies across all OBD-II vehicles. P1093 on a Duramax is manufacturer-specific for the same general issue.
Heavy-duty trucks (Class 6–8) use J1939 (SPN/FMI) instead of OBD-II, though many modern trucks support both protocols.
How to Follow Diagnostic Flows
- 1
Read all fault codes
Pull active, pending, and historical codes. Active codes are current faults. Pending codes are faults that have occurred but not yet triggered the MIL. Historical codes show past failures.
- 2
Identify the primary fault
When multiple codes are present, identify the root cause code. Secondary codes are often caused by the primary fault. Fix the root cause first.
- 3
Check live data
Review sensor readings in live data mode. Compare actual values to expected ranges. A sensor reading that is stuck, erratic, or out of range points to the failing component.
- 4
Follow the diagnostic tree
Use the OEM diagnostic tree for the specific fault code. The tree walks you through tests in order of likelihood and cost — cheapest tests first.
- 5
Test before replacing
Confirm component failure with a meter or scope before ordering parts. A fault code points to a circuit, not necessarily a failed component.
- 6
Verify the repair
Clear codes, perform a drive cycle, and confirm the fault does not return. Check live data to confirm values are back in spec.
Avoiding Parts Cannon Repairs
A fault code identifies a circuit or system — not a specific failed part. SPN 3226 FMI 4 (NOx sensor voltage low) could be a failed sensor, a wiring short, or a connector issue. Test before replacing.
The most expensive part is rarely the first thing to check. Start with the cheapest, most likely cause — connectors, wiring, fuses — before condemning a $400 sensor.
Intermittent faults are caused by intermittent connections. Wiggle-test connectors and harnesses while monitoring live data. A fault that appears under vibration is almost always a connector or wiring issue.
If a replaced part fails again quickly, the root cause was not fixed. A second NOx sensor failure usually means DEF quality or a DEF injector problem was never addressed.
Document your diagnostic process. If the repair doesn't fix the problem, your notes tell you what you already tested and ruled out.
Put it into practice
Run a guided diagnosis on a real fault code or use Technician Chat for quick reference lookups.