Autodata - Diagnostic Trouble Codes Fault locations and probable causes - 2004 edition

05.02.2017 Views

Trouble codes If the trouble code is greater than 9, long flashes are used for the tens and short flashes for the units. For example - Fig. 5 shows one long flash, and two short flashes Fig. 5 separated by a short pause, indicating trouble code 12. In 1988 the California Air Resources Board (CARB) introduced legislation covering all new cars sold in California. These new laws governed on-board diagnostic 1 2 -- requirements for emissions related faults and began the process of standardization in the US and eventually Europe. These regulations were known as onboard diagnostic systems - phase I (OBD-I) and were subsequently adopted by the vehicle manufacturers, for states other than California. The basic requirements of OBD-l were as follows: A043243 A malfunction indicator lamp (MIL), to provide a visible warning that an emissions related fault had been logged by the engine control module (ECM). Provision for the logging and storage, for subsequent retrieval, of diagnostic trouble codes (DTC)/flash codes for emissions related faults. The location of the diagnostic socket, the method of access to the trouble codes and the configuration and scope of the self-diagnosis was left to individual vehicle manufacturers. This resulted in an almost complete lack of standardization, requiring the technician to adopt different procedures and to use different equipment for each vehicle. In 1995 the California Air Resources Board (CARB), after consultation with the Society of Automotive Engineers (SAE), introduced further legislation covering all new cars sold in California. These regulations are known as OBD-ll and have been adopted for all states. They closely define trouble code logging and retrieval. More significantly they require monitoring of the operation of the system and components, in addition to detecting component failures. OBD-ll also covers systems other than engine management. Basically the US OBD-II regulations have been adopted for European vehicles and are known as EOBD - European On Board Diagnostics. These EOBD regulations became mandatory for most new petrol engined vehicles produced after January 1 st 2000 (diesel and LPG engined cars were not required to comply until 2003). Most petrol engined vehicles already in production before January 1 st 2000 were granted exemption until January 1 st 2001. EOBD codes Basic requirements Malfunction indicator lamp (MIL) located on the instrument panel, which either flashes or illuminates continuously, when a fault is detected. If no fault is present the MIL Fig. 6 - should illuminate when the ignition is switched on and extinguish when the engine starts. Standard configuration of 16 pin data link connector (DLC) The 16 pins of the DLC are arranged in two parallel rows, 1-1-1111 with certain pin connections defined by the EOBD regulations and the rest allocated by the vehicle manufacturer - Standard location for the DLC The standard location for the DLC is defined as being between the driver's end of the instrument panel and 300 mm beyond the vehicle centre line, accessible from the driver's seat. The recommended location is between the steering column and the vehicle centre line. A081444 10 1 56 1 Trouble codes /nutodata

Trouble codes I Format of EOBD codes Standard, 5 element alpha-numeric format, trouble codes, made up as follows: Letter prefix defines system designation B C P U Body Chassis Powertrain Network communications systems First digit defines code type I 0 ( Standard EOBD I ( 1 I Defined by vehicle manufacturer I 2 Standard EOBD 3 Standard EOBDIdefined by vehicle manufacturer Second digit defines system identification / 0 1 Standard code (refer to PO code list) I / 1 1 Fuel or air I ( 2 1 Fuel or air I 1 3 1 Ignition I 1 4 1 Emission control I 1 5 1 Speed control (idle, vehicle etc.) 1 1 6 1 Trip computer 1 7 8 Transmission Transmission 1 9 1 Transmission I Third and fourth digits define specific fault These digits define general malfunction, range or performance of component or system, low or high input Example code POl08 This code is logged when a high input is detected in the pressure circuit of the manifold absolute pressure (MAP) sensor or barometric pressure (BARO) sensor I P 1 System - Powertrain I Code type - EOBD System identification (fuel or air) - manifold absolute pressure (MAP) sensorlbarometric pressure (BARO) sensor Pressure circuit 8 High input I NOTE: Emissions related problems have a IS0 defined list of codes and definitions starting with P0001.

<strong>Trouble</strong> codes<br />

If the trouble code is greater than 9, long flashes are used<br />

for the tens <strong>and</strong> short flashes for the units. For example<br />

- Fig. 5 shows one long flash, <strong>and</strong> two short flashes<br />

Fig. 5<br />

separated by a short pause, indicating trouble code 12.<br />

In 1988 the California Air Resources Board (CARB)<br />

introduced legislation covering all new cars sold in<br />

California. These new laws governed on-board diagnostic 1 2<br />

--<br />

requirements for emissions related faults <strong>and</strong> began the<br />

process of st<strong>and</strong>ardization in the US <strong>and</strong> eventually<br />

Europe.<br />

These regulations were known as onboard diagnostic<br />

systems - phase I (OBD-I) <strong>and</strong> were subsequently<br />

adopted by the vehicle manufacturers, for states other<br />

than California.<br />

The basic requirements of OBD-l were as follows:<br />

A043243<br />

A malfunction indicator lamp (MIL), to provide a visible<br />

warning that an emissions related fault had been logged<br />

by the engine control module (ECM).<br />

Provision for the logging <strong>and</strong> storage, for subsequent<br />

retrieval, of diagnostic trouble codes (DTC)/flash codes for<br />

emissions related faults.<br />

The location of the diagnostic socket, the method of<br />

access to the trouble codes <strong>and</strong> the configuration <strong>and</strong> scope of the self-diagnosis was left to individual vehicle<br />

manufacturers.<br />

This resulted in an almost complete lack of st<strong>and</strong>ardization, requiring the technician to adopt different procedures <strong>and</strong> to<br />

use different equipment for each vehicle.<br />

In 1995 the California Air Resources Board (CARB), after consultation with the Society of Automotive Engineers (SAE),<br />

introduced further legislation covering all new cars sold in California.<br />

These regulations are known as OBD-ll <strong>and</strong> have been adopted for all states. They closely define trouble code logging<br />

<strong>and</strong> retrieval. More significantly they require monitoring of the operation of the system <strong>and</strong> components, in addition to<br />

detecting component failures.<br />

OBD-ll also covers systems other than engine management.<br />

Basically the US OBD-II regulations have been adopted for European vehicles <strong>and</strong> are known as EOBD - European On<br />

Board <strong>Diagnostic</strong>s.<br />

These EOBD regulations became m<strong>and</strong>atory for most new petrol engined vehicles produced after January 1 st 2000<br />

(diesel <strong>and</strong> LPG engined cars were not required to comply until 2003). Most petrol engined vehicles already in production<br />

before January 1 st 2000 were granted exemption until January 1 st 2001.<br />

EOBD codes<br />

Basic requirements<br />

Malfunction indicator lamp (MIL) located on the instrument<br />

panel, which either flashes or illuminates continuously,<br />

when a fault is detected. If no fault is present the MIL<br />

Fig. 6<br />

-<br />

should illuminate when the ignition is switched on <strong>and</strong><br />

extinguish when the engine starts.<br />

St<strong>and</strong>ard configuration of 16 pin data link connector (DLC)<br />

The 16 pins of the DLC are arranged in two parallel rows, 1-1-1111<br />

with certain pin connections defined by the EOBD<br />

regulations <strong>and</strong> the rest allocated by the vehicle<br />

manufacturer -<br />

St<strong>and</strong>ard location for the DLC<br />

The st<strong>and</strong>ard location for the DLC is defined as being<br />

between the driver's end of the instrument panel <strong>and</strong><br />

300 mm beyond the vehicle centre line, accessible from<br />

the driver's seat.<br />

The recommended location is between the steering<br />

column <strong>and</strong> the vehicle centre line.<br />

A081444<br />

10<br />

1 56 1 <strong>Trouble</strong><br />

codes<br />

/nutodata

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!