What SPN and FMI Numbers Mean in J1939
Every fault code on a J1939-connected commercial vehicle consists of at least two numbers: the SPN (Suspect Parameter Number) and the FMI (Failure Mode Identifier). The SPN identifies which parameter or circuit is being monitored — SPN 100 is engine oil pressure, SPN 102 is intake manifold pressure, SPN 157 is fuel rail pressure. The FMI describes how that parameter failed — FMI 1 means the measured value is below the normal range, FMI 3 means the signal voltage is above the electrical range, FMI 9 means the module is not receiving the expected J1939 data update.
Together, the SPN and FMI form a compact description of a monitored condition. SPN 100 FMI 1 says 'the oil pressure parameter is reading below its lower calibrated limit.' That translation is what the decoder provides — it maps the numbers to their vocabulary.
What the Decoder Shows and What It Does Not
The SPN/FMI decoder translates the code numbers into the parameter name, the monitored system, and the failure mode category. It links matched entries to the site's source-backed fault code pages where available. It does not tell you which physical part failed — a single SPN/FMI pair can result from a failed sensor, a wiring fault, a connector issue, or a genuine change in the monitored parameter. The decoder identifies the diagnostic territory; OEM service documentation maps the specific path.
The decoder also does not determine whether a code is active or stored, whether it is the root cause of a derate or a secondary effect of another fault, or whether the vehicle needs immediate service. Those judgments require the full code set, the active/stored status of each code, and access to OEM calibration data.
Using Decoder Output as a Starting Point
A decoded SPN/FMI is most useful when recorded alongside source address, active/stored status, all co-active codes, and the operating conditions at the time of the fault. An oil pressure code that appeared once during a cold start on a highway grade means something different from the same code appearing continuously at normal operating temperature. The decoder provides the vocabulary; context provides the direction.
When multiple codes are active simultaneously, communication faults (J1939 data link, CAN bus) and power or voltage faults typically take diagnostic priority — they can produce secondary codes in other systems and should be resolved first before interpreting component-level codes.
Privacy and Technical Boundaries
The decoder runs in your browser with no data submission to a server, analytics system, or external service. Input is not stored or transmitted. Avoid entering personally identifying vehicle information if your organization's data policy requires it.
Decoder output is educational and organizational — it does not replace OEM diagnostic software, a qualified technician's scan session, or the OEM service documentation that governs the specific vehicle, module version, and calibration being diagnosed.
Related Pages
Sources
- SAE J1939 Standards Collection SAE International · official · accessed 2026-05-05 · confidence medium
Source: SAE International, SAE J1939 Standards Collection. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - ELD Malfunctions and Data Diagnostic Events Federal Motor Carrier Safety Administration · government · accessed 2026-05-05 · confidence high
Source: Federal Motor Carrier Safety Administration, ELD Malfunctions and Data Diagnostic Events. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR 395.34 - ELD malfunctions and data diagnostic events Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR 395.34 - ELD malfunctions and data diagnostic events. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Does the SPN/FMI decoder tell me which part to replace?
No. The decoder identifies what the SPN monitors and what failure mode the FMI describes. It does not confirm which physical component failed, which wire is broken, or whether the fault is real or a sensor/wiring issue. It is a translation tool for the diagnostic message, not a repair decision tool.
Can the same SPN appear on multiple vehicle makes and mean different things?
Yes. J1939 SPN numbering is standardized by SAE, so SPN 102 is intake manifold pressure regardless of manufacturer. However, the thresholds that trigger a fault, the inducement strategy that follows, and the diagnostic procedures that apply all vary by OEM, engine family, model year, and calibration. The SPN identifies the parameter; the OEM's service documentation determines what to do about the fault.
What information should I enter alongside the SPN and FMI?
Source address (which module reported the fault), active vs. stored status, the full list of related codes active at the same time, warning lamp state, derate level, vehicle mileage, and engine hours. A single SPN/FMI without this context provides far less diagnostic value than the same code with the complete picture.