Understanding SPN and FMI in J1939 Fault Codes

SPN and FMI work as a pair on J1939 vehicles, with the first identifying the parameter and the second describing the type of condition being reported.

What SPN and FMI mean

A J1939 diagnostic fault is commonly displayed with an SPN and an FMI. SPN means Suspect Parameter Number and identifies the parameter involved. FMI means Failure Mode Identifier and describes the type of condition reported. The pair gives the technician more context than either number by itself, but it still needs to be interpreted for the controller reporting it.

Record the complete fault entry

Record the complete fault entry, including the source controller, active or inactive status and available occurrence or event information. A diagnostic application may also display a manufacturer-specific code and description. Retain those details rather than copying only the SPN, because an incomplete record can send the investigation toward the wrong system or procedure.

What an FMI can tell you

An FMI can describe conditions such as a signal outside its expected range, a circuit-related problem or an abnormal operating response. It does not prove which part has failed. A sensor-related code may require investigation of the sensor, connections, power supply or conditions being measured, depending on the manufacturer's diagnostic instructions.

Look up the right procedure

Look up the code in service information matched to the engine or component and its controller generation. Check related faults and the conditions under which the code is set. Compare the relevant data with the complaint before deciding which test to perform. Avoid using a generic Internet code description as a substitute for the correct fault procedure.

Connect the numbers to evidence

Preserve the original scan and document the checks that lead to a confirmed cause. After repair, complete the specified verification and compare the new results with the original report. Explain the finding in terms of the fault condition and supporting evidence. A useful diagnostic record connects the numbers to what was actually tested, rather than treating the code as a direct instruction to replace a named component.

More reading on spn and fmi

Read next about active and inactive status and the protocols behind the messages. Manufacturer bulletins show how a specific code is handled, and this reference document is one example of that level of detail.