What a Complete Fault Code Record Contains
A useful fault code record contains more than just the code number. The minimum useful record includes: the SPN (Suspect Parameter Number), the FMI (Failure Mode Identifier), the source address (the module that reported the fault), whether the code is active or inactive at the time of recording, which warning lamps are illuminated (color and whether steady or flashing), and the vehicle's odometer reading and engine hours.
Additional context that significantly helps diagnosis includes: ambient temperature at the time of the fault, what the truck was doing when the fault appeared (cold start, highway cruise, loaded grade, low-speed maneuver, idle), any recent maintenance or repairs in the past 30 days, and whether the fault is new or has appeared before. A technician receiving a complete record can often direct their first diagnostic steps before the truck arrives at the shop.
How Modern Truck Displays Show Fault Codes
Heavy-duty truck instrument clusters display fault codes in a variety of formats depending on the OEM and model year. Some displays show a numeric SPN/FMI combination directly (for example, 'SPN 3364 FMI 1'). Others translate the code into a plain-language message ('DEF Quality Low'). Some display an OEM proprietary code number. The underlying J1939 SPN/FMI is the most useful form for diagnosis — if the display shows a plain-language message, check the vehicle's operator manual for how to access the numeric code.
Many current Freightliner, Kenworth, and Peterbilt trucks with telematics-enabled dashboards broadcast fault codes to fleet management software automatically. However, the automated telematics record may not capture all relevant context — the driver's description of the symptom, related warning lamps that appeared simultaneously, and operating conditions at fault onset are things only the driver can add to the record.
Common Recording Mistakes
The most common recording mistake is writing down only the code number without the FMI or source address. A SPN alone — for example, SPN 3364 — can match dozens of possible conditions (FMI 1, FMI 3, FMI 4, FMI 9, etc.) with different diagnostic implications. Without the FMI, the record is incomplete. A second common mistake is clearing codes before recording them — clearing removes the stored code from the ECM's active list, and the technician loses the information about what was active.
Recording a fault code message in plain language rather than the numeric code is a third common issue. 'DEF low' and 'DEF quality fault' are two different conditions with different causes and different repair paths — but both might appear as a dashboard message without clearly identifying which J1939 code triggered the alert. When possible, retrieve the numeric SPN/FMI using a diagnostic tool or the vehicle's built-in code display mode.
Tools for Recording Fault Codes in the Field
The simplest recording tool is a phone camera pointed at the instrument cluster display. A photo of the display at the moment the fault appears captures the exact message shown, which can be shared with a shop remotely. For more detailed recording, a basic J1939 scan tool (a handheld Bluetooth adapter paired with a phone app, or a standalone scan tool) connected to the 9-pin diagnostic port reads active and inactive fault codes with SPN, FMI, and source address.
Fleet management telematics systems (Samsara, Geotab, Omnitracs, and others) often capture fault code broadcasts automatically when connected to the J1939 network. These systems log the code, timestamp, vehicle speed, and some operating parameters at the time of the fault. A driver note captured through the telematics app — describing symptoms, conditions, and warning lamp status — completes the record that the automated system cannot provide.
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 - 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Besides SPN and FMI, what other information should I capture before driving to a shop?
Record the source address if the display shows it, whether the code is active or inactive, any warning lamp colors that are lit, whether the engine is in derate, the odometer and engine hours at the time of the fault, ambient temperature if extreme, and a brief note on what the truck was doing when the code appeared (cold start, highway, loaded grade, etc.). That context helps the technician significantly.
My fleet telematics already recorded the fault. Do I still need to write anything down manually?
Telematics captures most broadcast J1939 data, but it does not always capture source addresses, related codes that appeared simultaneously, lamp status at the exact moment of the fault, or the driver's description of what the truck was doing. A short manual note by the driver supplements the telematics record and often resolves the 'cannot reproduce' situation at the shop.
Should I include the source address in my fault code record if the display shows it?
Yes — if your display shows it, include it. Source address identifies which module reported the fault. Without it, a code like SPN 3364 FMI 1 could come from the engine ECM, the aftertreatment control module, or another module — and the repair path differs. If your display shows SA followed by a number or a module name, record it alongside the SPN and FMI.