What a Complete Fault Code Record Contains
A complete fault code note includes: the exact SPN and FMI numbers (or OEM-specific code if that is what the display shows), the source address (SA) or module name, whether each code is active or stored, all co-active codes present at the same time, the color of every illuminated warning lamp (red vs. amber/yellow matters), whether a derate is active and at what percentage if visible, vehicle year/make/model, engine make and model, current mileage, current engine hours, any recent service (oil change, fluid change, sensor replacement), and the driving conditions when the fault appeared.
Most drivers bring only the code number. Most technicians need all of these elements to form a diagnostic hypothesis before the vehicle arrives at the shop. A complete note before the call means the shop can identify the likely test path, prepare for the diagnostic session, and avoid a same-day parts run that delays the repair.
Why Active vs. Stored Status Matters
The active/stored distinction is the single most diagnostic-relevant piece of information after the code number itself. An active code means the ECM is detecting the fault condition right now during this key cycle. A stored code (also called an inactive or historical code) means the fault was detected at some point and logged, but the ECM does not currently detect the condition.
Active codes take diagnostic priority — the condition they describe is present and may be causing the current symptoms. A stored code that never recurs after clearing may be a past event that resolved on its own. Treating a stored code as if it were active leads to unnecessary repairs; missing an active code because the focus was on a stored one means the actual problem is overlooked. The note template prompts for status for every code in the list.
Red Lamps vs. Amber Lamps
Warning lamp color is a severity signal that the note template captures. A red stop-engine or stop-vehicle lamp requires immediate safe stopping — it represents an ECM determination that continued operation risks engine damage or a safety condition. An amber check-engine or malfunction indicator lamp means a fault is active but immediate stopping is not required — schedule service at the earliest safe opportunity.
Some faults illuminate both colors simultaneously or escalate from amber to red as the condition worsens. Noting which lamps are on, whether they are steady or flashing, and whether they changed during the trip provides context about the fault's progression that affects how the technician prioritizes the diagnostic.
Operational Context the Template Captures
Recent service history is directly relevant to many fault codes. A code that appeared hours after an oil change may trace to an over-full oil level or an incorrect viscosity. A fault appearing after a sensor replacement may indicate a connector issue from the reinstallation. A code appearing after a long idle may point to a DPF soot accumulation problem rather than a sensor fault.
Operating conditions at the fault event are equally valuable. A code appearing only at full load on a grade may point to a boost or fuel pressure issue that is marginal at light load. The same code appearing at idle on a flat road suggests a different root cause. The template includes fields for these contextual details so the technician receives a complete picture, not just a code list.
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
Why record fault codes on a template before calling a shop?
Technicians consistently report that complete code information significantly reduces diagnostic time. The code number alone — without active vs. stored status, related codes, warning lamps, derate state, mileage, engine hours, and recent operating history — leaves most of the diagnostic picture blank. A complete note before the call means the shop can prepare, identify the likely test path, and order parts proactively rather than starting cold.
Does the note template store my vehicle data anywhere?
No. The template runs in the browser with no backend. Nothing is submitted to a server, analytics system, or third party. Any data entered stays in your browser session and disappears when you close or navigate away from the page.
What is the most important thing to include in a fault code note?
Active vs. stored status matters more than most drivers realize. An active code means the ECM detects the condition right now; a stored code means it was detected at some point. Active codes take diagnostic priority. Without that distinction, a technician may focus on a stored historical code while an active, potentially more urgent condition is also present.