On-Board Diagnostics (OBD)

On-board diagnostics (OBD) is the self-monitoring capability built into a vehicle's electronics. Control units watch engine, emissions and other systems, light a warning lamp when something goes wrong and store a standard diagnostic trouble code. The OBD-II standard defines those codes and data so any compatible tool can read them; the physical socket is covered under OBD interface.

What the standard defines

OBD began as a way to monitor emissions-related components and became a common language between vehicles and diagnostic tools. In Europe the equivalent requirement is often called EOBD. The standard sets out:

• Monitored systems: combustion, catalytic converter, oxygen sensors, fuel and evaporative systems, among others.
• Communication protocols used between the tool and the vehicle's control units.
• Standard parameters, such as engine speed, vehicle speed and coolant temperature, readable as live data.
• A common code format for faults, so the same code means the same thing across makes.

How fault codes work

When the engine control module detects a reading outside its expected range, it stores a diagnostic trouble code (DTC) and, for serious or emissions-related faults, lights the malfunction indicator lamp. Each code has a letter and four characters:

• The letter gives the system: P for powertrain, B for body, C for chassis, U for network communication.
• The next character shows whether the code is generic, shared by all makes, or manufacturer-specific.
• The remaining characters identify the subsystem and the precise fault, for example a catalyst efficiency problem or a misfire on one cylinder.

Alongside the code, the vehicle often saves freeze-frame data: a snapshot of conditions such as speed, engine load and temperature at the moment the fault appeared. Codes can be pending, confirmed or permanent depending on whether the fault repeats.

Why it matters for a fleet

A warning lamp seen by one driver is easy to ignore; a code reported to the fleet team is not. Reading codes helps decide whether a vehicle can finish its round or must go to the workshop, gives the garage a starting point, and builds a maintenance history per vehicle. Recurring codes across several vehicles of the same model can reveal a wider issue worth raising with the manufacturer or lessor. Codes signal a detected fault; they do not replace a mechanic's diagnosis.

How Dadycar helps

Dadycar is a French fleet management software that turns vehicle events into actions. Telematics brings vehicle data into the platform, without a box on compatible connected vehicles and with an optional tracker for the others. Alerts can notify the right person, work orders track the repair with the garage, and the vehicle file keeps the full history. Data is hosted in France, with OVHcloud.

FAQ

What is the difference between OBD and OBD-II?
OBD is the general concept of on-board self-diagnosis; OBD-II is the standardised second generation used on most modern cars and vans.

Does clearing a fault code fix the problem?
No. Clearing only erases the record; if the fault persists, the code returns.

Do all fault codes need immediate action?
No. Some are minor or intermittent. A flashing warning lamp or a safety-related code should be checked quickly.