What This FMI Means
FMI 22 indicates a specific high-side condition defined by the OEM's proprietary fault classification logic. FMI values 22 and 23 are used in some manufacturer implementations to provide additional categorization granularity beyond the standard FMI definitions. The precise meaning depends entirely on which manufacturer's module is reporting it.
Because FMI 22 is OEM-defined rather than universally standardized, the same FMI value has different meanings when reported by a Cummins engine controller versus an Allison transmission controller or a Bendix brake controller. The source address in the fault code determines which manufacturer's definition applies.
How It Appears With SPN Codes
FMI 22 is less commonly encountered than FMI 0–12 and appears when the OEM's diagnostic logic has classified a specific fault condition into this category. The SPN combined with the source address provides the necessary context for interpretation.
OEM diagnostic software will provide the full description of the SPN/FMI 22 combination — Cummins Insite, Detroit DiagnosticLink, Allison DOC, Eaton ServiceRanger, or Bendix ACOM Pro depending on the reporting module. These tools translate the manufacturer-specific code into a readable description and guided procedure.
How to Approach Diagnosis
Look up the specific SPN/FMI 22 combination in OEM service documentation before proceeding. The OEM documentation describes what specific condition triggers FMI 22 for that SPN and provides the recommended diagnostic steps. Generic J1939 references cannot reliably interpret this FMI without OEM context.
Check for software version mismatches between modules if FMI 22 appeared after a reprogramming event. Incompatible calibration versions between modules that share J1939 data can produce unexpected fault classifications. Verifying all related modules are running correct, matched software versions is part of the post-programming verification.
What Drivers Should Record
Record the complete fault code including the source address (SA), SPN, and FMI 22. Include the status (active/inactive), any related codes, and operating conditions. The source address is critical because FMI 22 behavior depends on which manufacturer's module is reporting it.
Note any recent changes — software updates, module replacements, or component swaps — that preceded the appearance of FMI 22. Post-maintenance FMI 22 codes often have a clear trigger that helps the technician focus the investigation.
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 - NHTSA Manufacturer Communications Search National Highway Traffic Safety Administration · government · accessed 2026-05-05 · confidence high
Source: National Highway Traffic Safety Administration, NHTSA Manufacturer Communications Search. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
What is the practical difference between FMI 22 and FMI 20?
Both FMIs indicate a data value that is high, but the specific FMI categorization reflects how the module classifies the fault internally. FMI 22 is typically defined by OEM-specific logic that identifies a particular high- or low-condition in the module's control strategy. The specific difference is defined in the OEM service documentation for the SPN in question — the diagnostic approach is to look up the exact SPN/FMI 22 combination in OEM service information.
How do I know which module is responsible when FMI 22 appears on a network-received parameter?
Check the source address of the fault code. If the SA belongs to a module receiving data (like the transmission controller receiving engine torque), the fault was detected in the receiving module but its cause may be in the transmitting module. Cross-reference the transmitting module's own fault code log for related faults. The diagnostic tool's module identification screen shows which SA corresponds to which physical module.
Can FMI 22 be caused by a software version mismatch between modules?
Yes. If two modules are running incompatible software versions and interpret a shared parameter differently, one module may classify the received value as high-out-of-range even when the transmitting module considers its data valid. This is most likely after a module reprogramming event. Verifying that both modules are running the correct, matched calibration versions is part of the investigation for FMI 22 that appeared after recent software updates.