Fault Code
A diagnostic trouble code (DTC) generated by a vehicle's on-board diagnostics system when a sensor or system detects an abnormal condition, transmitted to fleet management platforms via telematics to alert managers before minor issues become major repairs.
Category: Fleet MaintenanceOpen Fleet Maintenance SoftwarePublished June 10, 2026Updated August 18, 2026
Evaluating software in this category?
Compare fleet maintenance software platforms with verified pricing, deployment details, and editorial verdicts.
Compare Fleet Maintenance Software software →How Fault Codes Are Generated and Transmitted
Modern commercial trucks contain multiple ECUs (Electronic Control Units) monitoring hundreds of parameters — coolant temperature, oil pressure, exhaust aftertreatment status, fuel injection timing, transmission fluid temperature, and more. When a sensor reading falls outside its defined range, the relevant ECU generates a DTC and stores it in the vehicle's fault memory. Telematics devices plugged into the J1939 or J1708 diagnostic port read these fault codes in real time and transmit them via cellular network to the fleet management platform, where they appear as alerts associated with the specific vehicle.
Fault Code Severity Levels
Standard J1939 fault code severity levels and fleet response guidelines
| Severity Level | Indicator | Driver Action | Fleet Response |
|---|---|---|---|
| Protect (most severe) | Red stop lamp | Pull over immediately, shut down engine | Dispatch recovery — do not continue operation |
| Amber warning | Yellow MIL lamp | Complete current delivery, report to shop | Schedule shop visit within 24–48 hours |
| Informational / pending | No lamp or pending code | None required | Log for next scheduled PM visit |
| Historical / inactive | Stored in memory, lamp off | None required | Review during next inspection |
High-Priority Fault Codes Fleet Managers Should Know
Not all fault codes carry equal urgency. Some — like SPN 110 (Engine Coolant Temperature) or SPN 100 (Engine Oil Pressure) at critical severity — require immediate engine shutdown to prevent catastrophic damage. Others, like SPN 3251 (DPF Differential Pressure) at amber severity, indicate a need for regen and can be managed within 24–48 hours. Fleet managers and dispatchers need a triaged fault code response policy, not a one-size-fits-all alarm system that buries critical codes under dozens of low-priority notifications.
Fault Code Management in Practice
A 65-truck bulk liquid carrier integrated their Samsara telematics platform with their fleet management system to route engine fault codes directly into open work orders. When a critical engine fault fires on any truck, the system automatically creates a work order, pages the on-call maintenance manager, and flags the truck as restricted in the dispatch system. In the first year of operation, this workflow caught four impending engine failures early enough to perform repairs in the shop rather than on the side of a highway — avoiding an estimated $180,000 in towing, emergency repair, and downtime costs.
Fault Code Noise: A Real Challenge in Fleet Operations
A common operational problem is fault code fatigue — telematics platforms generating dozens of low-severity alerts daily, causing dispatchers and managers to begin ignoring notifications entirely. Solving this requires a tiered alerting policy: critical and protect-level codes generate immediate SMS and phone alerts to the maintenance manager, amber codes generate daily digest emails, and informational codes are logged silently for PM review. Most telematics platforms support customizable alert thresholds — use them.
- Configure your telematics platform to route critical (protect-level) fault codes as immediate alerts to on-call maintenance staff
- Set amber-level fault codes to generate a daily digest report reviewed each morning by the fleet maintenance manager
- Establish a written fault code response policy: which codes require immediate pull-over, which allow completion of current run, which are logged for next PM
- Integrate fault code alerts with your fleet management system so every critical code auto-creates a work order
- Train dispatchers to recognize the red stop lamp vs. yellow MIL lamp distinction and the correct driver instruction for each
- Review historical fault code data monthly to identify vehicles with recurring codes — patterns often indicate underlying problems the repair is not fully resolving
- Restrict dispatching of any truck with an open critical fault code until cleared by maintenance
Fault Code FAQ
Quick answers to the questions buyers usually ask once the category, software, or rollout details start getting more specific.
A
An active fault code means the fault condition is currently present — the sensor is still reading out of range. A stored (historical) code means the fault occurred at some point but is not currently triggering. Stored codes are important diagnostic clues even when the lamp is off, particularly for intermittent issues that disappear when a technician inspects the truck.
A
J1939 is the standard diagnostic protocol for heavy-duty commercial vehicles and is readable by most modern telematics devices. Proprietary OEM codes (manufacturer-specific fault codes beyond the J1939 standard) may require OEM-specific diagnostic software to fully interpret. Some telematics platforms partner with diagnostic database providers to translate proprietary codes into plain-language descriptions.
A
Only protect-level (critical) fault codes should automatically block dispatch — these indicate conditions where continued operation risks engine or component destruction. Amber codes should generate a maintenance review but not necessarily a dispatch block. Automatically blocking trucks on every fault code will create operational chaos; the goal is a tiered response system, not a zero-tolerance policy for all DTCs.