SPN/FMI Codes
Learn how Suspect Parameter Numbers and Failure Mode Identifiers work in heavy-duty diagnostics.
A free, independent source-verified educational reference for heavy-duty truck fault codes, SPN/FMI terms, J1939 diagnostics, ABS codes, transmission codes, symptoms, systems, and ELD malfunction categories.
Learn how Suspect Parameter Numbers and Failure Mode Identifiers work in heavy-duty diagnostics.
Browse FMI 0 through FMI 31 with cautious plain-English diagnostic context.
A plain-English introduction to the vehicle network used by modern heavy-duty trucks.
Focused guides to SPN, FMI, source address, PGN, CAN bus, and data link terminology.
Context for Cummins ECM faults, aftertreatment faults, and source verification needs.
DD13, DD15, and DD16 fault code categories with careful source-backed framing.
Brake and stability code categories for Bendix ABS, ATC, and ESP systems.
Trailer ABS, EBS, blink codes, and SPN/FMI context for WABCO/ZF systems.
Overview of AutoShift, UltraShift, and Endurant fault code formats.
FMCSA-backed explanations of ELD malfunctions and data diagnostic events.
Educational system pages for aftertreatment, ABS, DPF, SCR, transmission, and data link issues.
Symptom-based entry points for warning lights, derate, ABS lamps, DPF lights, and ELD indicators.
Brand and supplier context pages for official verification paths and related systems.
Focused SPN number topic pages that explain what to record and why FMI context matters.
Practical guides for recording codes, reading warning lights, and preparing technician notes.
Component-level educational pages for sensors, modules, aftertreatment, brakes, transmission, and ELD hardware.
FMCSA and eCFR source-backed ELD malfunction, driver, and carrier education pages.
FMCSA-backed explanations of ELD data diagnostic event categories and how to handle them.
Static browser-only decoders, note templates, and technician call checklists.
Many heavy-duty diagnostic messages combine a system identifier with a failure description. In J1939, the SPN points to the parameter being reported, while the FMI describes the type of abnormal condition. OEM fault numbers may add manufacturer-specific mapping that depends on engine serial number, model year, calibration, and diagnostic software version.
Always record the full code, active or inactive status, warning lamps, derate state, and related codes before drawing conclusions. A code is a starting point for diagnosis, not proof that a specific part has failed.
Learn SPN/FMI basics Browse systems Browse symptoms Diagnostic guides Manufacturer hubs
Each page below is tied to an official, government, or OEM source. Records without a verifiable source are excluded from search and sitemap.
Electronic Logging Device · Power compliance monitoring
Source-backed explanation of an ELD power malfunction or power data diagnostic event under FMCSA ELD rules.
Electronic Logging Device · Engine ECM data connection
FMCSA-backed explanation of ELD engine synchronization data diagnostic events and malfunctions.
Electronic Logging Device · Time synchronization
Conservative explanation of ELD timing compliance malfunctions using FMCSA and CFR sources.
Electronic Logging Device · Position measurement
FMCSA-backed explanation of ELD positioning compliance malfunctions and location data concerns.
Electronic Logging Device · Record storage and retrieval
Source-backed explanation of ELD data recording compliance malfunctions and first checks.
Electronic Logging Device · Roadside data transfer
FMCSA-backed explanation of ELD data transfer diagnostic events and compliance malfunctions.
SPN stands for Suspect Parameter Number — it identifies which system or parameter the ECM is reporting on. FMI stands for Failure Mode Identifier — it describes the type of fault, such as signal out of range, short to ground, or erratic data. Together they form the core of a J1939 diagnostic message used in most modern heavy-duty trucks.
Not necessarily. A fault code tells you what the control module observed, not which part has definitively failed. The same code can result from a bad sensor, wiring issue, connector corrosion, ECM calibration mismatch, or an actual component failure. Always record the full code, active or inactive status, related codes, and warning lamps before drawing conclusions.
No. This is an independent educational reference and is not affiliated with, endorsed by, or sponsored by any OEM, manufacturer, or government agency. Always verify diagnostic steps with official OEM service information and qualified technicians.