Table of contents
Diagnostic Trouble Codes (DTCs) are standardised error codes generated by a vehicle’s onboard diagnostics system (OBD) when it detects abnormal behaviour. The codes are stored in the vehicle’s Electronic Control Unit (ECU) where drivers or mechanics can retrieve them using diagnostic tools and identify issues in plain English.
What are DTCs?
DTCs are triggered when a vehicle’s ECU detects an issue with one of its systems, such as engine misfires, emissions issues or sensor failures. They are a faster way for fleet managers and technicians to check what is wrong with a vehicle: removing the need to inspect components manually.
DTCs allow fleets to identify vehicle problems before breakdowns happen, enabling proactive maintenance and reducing roadside failures.This makes them a critical tool for uptime, safety and operational efficiency.
Once a DTC is detected by the ECU, it is communicated via different standards depending on the vehicle type — OBD-II or J1939. Light-weight vehicles typically communicate via OBD-II, whereas heavy-duty vehicles use J1939: a more advanced, data-rich standard.
Where do DTCs come from?
Modern vehicles are equipped with sensors to monitor their key systems. The sensors continuously send data to the ECU which evaluates it according to thresholds programmed by the manufacturer.
When the ECU detects an abnormal sensor reading, it assigns a DTC and stores the code in its memory. The ECU may also turn on a warning light or display a basic message on the dashboard. However, it cannot read out the actual DTC to the driver. To interpret it, you need to connect a diagnostic tool or telematics device. Many DTCs remain stored in the ECU until they are manually cleared by a driver, manager or mechanic.
How do DTCs work?
DTCs allow users to identify vehicle faults without physically inspecting each component, saving fleets time and errors.
Sensors collect data constantly
Sensors within a vehicle’s systems send real-time data to the vehicle’s computer. The ECU receives the sensor inputs and compares them to expected values to ensure each part is functioning correctly.
The ECU detects an issue
When a sensor reading doesn’t match its expected value, the ECU recognises it as a fault condition and creates and stores the appropriate code in response to the issue. The code will follow the OBD-II or J1939 communication standard, depending on the vehicle and how the ECU is programmed.
A tool reads and translates the code
A mechanic or fleet manager connects a diagnostic tool or telematics device to retrieve and interpret the stored codes. It shows which system is affected.
Once the issue has been fixed, the DTC can be cleared from the ECU using the same diagnostic tool.
How do you read DTCs?
DTCs are made up of letters and numbers that indicate the type of fault and system affected. Understanding the structure of the code is essential for diagnosing the issue correctly. The OBD-II format is standardised, meaning that any diagnostic tool or telematics system can read the generic fault code across different vehicle manufacturers. However, some manufacturer-specific codes and deeper diagnostic data may require specialised tools for full interpretation.
What does each part of a DTC mean?
Here’s a breakdown of the characters in an OBD-II DTC.
First character
Tells you which vehicle system has the issue.
P: powertrain (engine, transmission)
B: body (airbags, doors, HVAC)
C: chassis (brakes, steering, suspension)
U: network (network/communication)
Second character
Tells you if the code is standard (0) or manufacturer-specific (1).
Third character
Specificies which area of the system (indicated in the first character) the issue relates to. For example, within the powertrain system (a P-code), the functions affected may be:
1: fuel/air system
2: injector circuit
3: ignition or misfire
Fourth and fifth characters
Identify the exact issue. The last two characters are necessary to differentiate between types of faults affecting the same component.
Take the DTC P0102.
The fourth and fifth characters 02
within the fuel/air metering system indicate that the MAF sensor signal is too low. If they were ‘03’, however, it would indicate a different issue within the same component: that the MAF sensor signal is too high.
The full breakdown for P0102 would be:
P: powertrain
0: standard
1: fuel/air metering system
02: Mass Air Flow (MAF) sensor circuit low input
How do you interpret DTCs?
Diagnostic tools translate DTCs into plain English so fleet operators can read issues clearly. That said, understanding the structure of a DTC is still useful in terms of recognising which system is affected, spotting patterns across multiple faults and making decisions about urgency — all at a glance, when speed is critical.
What do DTC severity levels mean?
DTCs don’t contain a character that represents severity level. Severity can be inferred from the system affected and context.
The first letter warns you of system impact.
P – engine and emissions: can range from minor to critical
C – brakes and steering: likely to be severe and safety-critical
B – comfort systems: unlikely to be severe
U – communication systems: can vary widely
For instance, a C-code (which could be a brake issue) is often more urgent than a B-code (which may only be a window fault).
The last two digits also help communicate severity level.
If the digits correspond to:
Circuit failure: this is probably a serious issue
Performance issue: this could be a moderate issue
Intermittent/low signal: this type of fault is often less urgent
The vehicle itself will also give you signs when something is critically wrong.
Immediate attention required:
- Flashing check engine light
- Limp mode activated
- Loss of power
Repair soon:
- Solid warning light
- Noticeable performance issues
Monitor evolution:
- No light or intermittent light
- No noticeable driving impact
What are common DTCs and what do they mean?
The most common DTCs tend to involve fuel mixture, combustion issues and emissions systems since the engine and exhaust have many sensors and are governed by very tight thresholds, so even small deviations are detected. Subject to heat, pressure and wear, they are also more likely to develop issues over time.
1P0171 – system too lean (Bank 1)
P: powertrain
0: standard
1: fuel/air metering system
71: system too lean
What it tells you:
Area: engine
Subsystem: fuel/air mixture
Issue: not enough fuel (or too much air)
P0300 – random/multiple cylinder misfire
P: powertrain
0: standard
3: ignition/misfire system
00: random/multiple cylinder misfire
What it tells you:
Area: engine
Subsystem: fcombustion/ignition
Issue: misfires happening across multiple cylinders
P0420 – catalyst efficiency below threshold
P: powertrain
0: standard
4: emissions system
20: catalyst efficiency below threshold
What it tells you:
Area: engine/exhaust
Subsystem: emissions control
Issue: catalytic converter not performing efficiently
What are the risks of ignoring a DTC?
Ignoring a DTC, even of low severity, can lead to cost and productivity risks. Minor faults can escalate into serious issues if not properly investigated and resolved. For example, a common DTC like P0171 (system too lean) may appear minor, especially as the vehicle may still drive normally.
If left unresolved, however, it could lead to the engine overheating, increased wear on engine components and damage to the catalytic converter — costly component failures and considerable time in the workshop.
Not every DTC calls for immediate action. The best response is to note them and add follow-up checks to the maintenance calendar. Timely action helps protect fuel efficiency, improve safety, reduce downtime and support better maintenance planning.
What tools are used to diagnose DTCs?
There are two main types of tools for reading and diagnosing DTCs.
OBD diagnostic scanners
OBD diagnostic scanners are physical tools that you plug into a vehicle’s OBD port. They connect directly to the ECU to retrieve DTCs and their meanings which they show on a small screen.
Vehicle telematics systems
Vehicle telematics systems are composed of hardware and software. These connected systems continuously collect vehicle data, including DTCs, and display it on a fleet management platform. The benefits of using a vehicle telematics system are that diagnosis is automated, results are accessible remotely and monitoring is near real-time.
How and when should you clear a DTC?
You can clear DTCs with the same tool you use to read them — the OBD diagnostics scanner. In some cases, you may also be able to do so remotely with vehicle telematics systems. You simply plug in the scanner, read the code, fix the issue and then select ‘Clear codes’. The dashboard warning light should then turn off.
It’s important to only clear a code once a problem has been properly fixed. If the fault remains, the ECU will detect it again and the DTC will reappear. Unresolved problems can worsen over time and become serious safety risks.
What is the difference between OBD-II and J1939 diagnostic systems?
OBD-II and J1939 are vehicle diagnostic communication standards that define how fault codes and vehicle data are structured, transmitted and accessed.
OBD-II is the system used in LCVs. It works with the standardised DTC format (P-codes) and has a phyiscal port to plug into.
J1939 is the standard for HGVs, designed for fleets and real-time data. It provides a network connecting the ECUs and a more detailed fault structure. While OBD scanners have sequential access to a vehicle’s ECUs (sending a request to a specific module, receiving it and moving on to check another) with J1939, ECUs broadcast messages continuously over a shared network.
How can telematics help monitor DTCs?
Telematics systems automate DTC monitoring across all a vehicle’s ECU’s, so fleet operators can save time by diagnosing issues remotely instead of needing to physically access the vehicle.
As soon as an issue is detected, the telematics system sends out an alert so that fleet managers or drivers can take proactive action before it leads to downtime. This greater visibility over vehicle health simplifies fleet maintenance planning, minimises unexpected breakdowns and saves repairs costs.
This is known as real-time DTC monitoring, where vehicle data is continuously tracked and issues are reported as they occur.
Why are DTCs important for fleet managers?
DTCs are important for fleet managers as they point out the problems within their vehicles. Early visibility into issues enables proactive maintenance, which lowers repairs costs, extends vehicle lifespan and helps prevent breakdowns.
DTCs encourage data-driven decisions, providing the necessary information for fleet managers to act on strategically: prioritising repairs, tracking recurring issues and keep vehicles running safely and efficiently.