OBD-II PIDs

OBD-II PIDs
OBD-II PIDs (On-board diagnostics Parameter IDs) are codes used to request data from a vehicle, used as a diagnostic tool. SAE standard J/1979 defines many PIDs, but manufacturers also define many more PIDs specific to their vehicles. All light duty vehicles (e.g. less than 8,500 pounds) sold in North America since 1996, as well as medium duty vehicles (e.g. 8,500-14,000 pounds) beginning in 2005, and heavy duty vehicles (e.g. greater than 14,000 pounds) beginning in 2010, are required to support OBD-II diagnostics, using a standardized data link connector, and a subset of the SAE J/1979 defined PIDs (or SAE J/1939 as applicable for medium/heavy duty vehicles), primarily for state mandated emissions inspections. Typically, an automotive technician will use PIDs with a scan tool connected to the vehicle's OBD-II connector. The technician enters the PID The scan tool sends it to the vehicle's bus (CAN, VPW, PWM, ISO, KWP. After 2008, CAN only) A device on the bus recognizes the PID as one it is responsible for, and reports the value for that PID to the bus The scan tool reads the response, and displays it to the technician

Modes
There are ten modes of operation described in the latest OBD-II standard SAE J1979. They are as follows (the 0x prefix indicates a hexadecimal radix): 0x01. Show current data 0x02. Show freeze frame data 0x03. Show stored Diagnostic Trouble Codes 0x04. Clear Diagnostic Trouble Codes and stored values 0x05. Test results, oxygen sensor monitoring (non CAN only) 0x06. Test results, other component/system monitoring (Test results, oxygen sensor monitoring for CAN only) 0x07. Show pending Diagnostic Trouble Codes (detected during current or last driving cycle) 0x08. Control operation of on-board component/system 0x09. Request vehicle information 0x0A. Permanent DTC's (Cleared DTC's) Vehicle manufactures are not required to support all modes. Each manufacturer may define additional modes above #9 (e.g.: mode 22 as defined by SAE J2190 for Ford/GM, mode 21 for Toyota) for other information (e.g.: the voltage of the Traction Battery [1] in a HEV).

Standard PIDs
The table below shows the standard OBD-II PIDs as defined by SAE J1979. The expected response for each PID is given, along with information on how to translate the response into meaningful data. Again, not all vehicles will support all PIDs and there can be manufacturer-defined custom PIDs that are not defined in the OBD-II standard. Note that modes 1 and 2 are basically identical, except that Mode 1 provides current information, whereas Mode 2 provides a snapshot of the same data taken at the point when the last diagnostic trouble code was set. The exceptions are PID 01, which is only available in Mode 1, and PID 02, which is only available in Mode 2. If Mode 2 PID 02 returns zero, then there is no snapshot and all other Mode 2 data is meaningless. Please, note that when using Bit-Encoded-Notation, quantities like C4 means bit 4 from data byte C. Each bit is numerated from 0 to 7, so 7 is the most significant bit and 0 is the least significant bit.

OBD-II PIDs

Mode PID (hex) (hex)

Data bytes returned 4

Description

Min value

Max value

Units

Formula

01

00

PIDs supported [01 - 20]

Bit encoded [A7..D0] == [PID 0x01..PID 0x20] See below. Bit encoded. See below.

01

01

Monitor status since DTCs cleared. (Includes malfunction indicator lamp (MIL) status and number of DTCs.) Freeze DTC Fuel system status Calculated engine load value Engine coolant temperature Short term fuel % trimBank 1 0 -40 -100 Subtracting Fuel (Rich Condition) -100 Subtracting Fuel (Rich Condition) -100 Subtracting Fuel (Rich Condition) -100 Subtracting Fuel (Rich Condition) 0 0 100 215 99.22 Adding Fuel (Lean Condition) 99.22 Adding Fuel (Lean Condition) 99.22 Adding Fuel (Lean Condition) 99.22 Adding Fuel (Lean Condition) 765 255 % C %

01 01 01 01 01

02 03 04 05 06

2 2 1 1 1

Bit encoded. See below. A*100/255 A-40 (A-128) * 100/128

01

07

Long term fuel % trimBank 1

(A-128) * 100/128

01

08

Short term fuel % trimBank 2

(A-128) * 100/128

01

09

Long term fuel % trimBank 2

(A-128) * 100/128

01 01

0A 0B

1 1

Fuel pressure Intake manifold absolute pressure Engine RPM Vehicle speed Timing advance

kPa (gauge) A*3 kPa (absolute) rpm km/h A

01 01 01

0C 0D 0E

2 1 1

0 0 -64

16,383.75 255 63.5

((A*256)+B)/4 A

relative to A/2 - 64 #1 cylinder C grams/sec % A-40 ((A*256)+B) / 100 A*100/255 Bit encoded. See below. [A0..A3] == Bank 1, Sensors 1-4. [A4..A7] == Bank 2...

01 01 01 01 01

0F 10 11 12 13

1 2 1 1 1

Intake air temperature MAF air flow rate Throttle position Commanded secondary air status Oxygen sensors present

-40 0 0

215 655.35 100

01

14

Bank 1, Sensor 1: Oxygen sensor voltage, Short term fuel trim

0 -100(lean)

1.275 99.2(rich)

Volts %

A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc)

OBD-II PIDs

3
2 Bank 1, Sensor 2: Oxygen sensor voltage, Short term fuel trim Bank 1, Sensor 3: Oxygen sensor voltage, Short term fuel trim Bank 1, Sensor 4: Oxygen sensor voltage, Short term fuel trim Bank 2, Sensor 1: Oxygen sensor voltage, Short term fuel trim Bank 2, Sensor 2: Oxygen sensor voltage, Short term fuel trim Bank 2, Sensor 3: Oxygen sensor voltage, Short term fuel trim Bank 2, Sensor 4: Oxygen sensor voltage, Short term fuel trim OBD standards this vehicle conforms to Oxygen sensors present 0 -100(lean) 1.275 99.2(rich) Volts % A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) A/200 (B-128) * 100/128 (if B==0xFF, sensor is not used in trim calc) Bit encoded. See below.

01

15

01

16

0 -100(lean)

1.275 99.2(rich)

Volts %

01

17

0 -100(lean)

1.275 99.2(rich)

Volts %

01

18

0 -100(lean)

1.275 99.2(rich)

Volts %

01

19

0 -100(lean)

1.275 99.2(rich)

Volts %

01

1A

0 -100(lean)

1.275 99.2(rich)

Volts %

01

1B

0 -100(lean)

1.275 99.2(rich)

Volts %

01

1C

01

1D

Similar to PID 13, but [A0..A7] == [B1S1, B1S2, B2S1, B2S2, B3S1, B3S2, B4S1, B4S2] A0 == Power Take Off (PTO) status (1 == active) [A1..A7] not used 0 65,535 seconds (A*256)+B Bit encoded [A7..D0] == [PID 0x21..PID 0x40] See below. 0 65,535 km (A*256)+B

01

1E

Auxiliary input status

01 01

1F 20

2 4

Run time since engine start PIDs supported [21 - 40]

01

21

Distance traveled with malfunction indicator lamp (MIL) on Fuel Rail Pressure (relative to manifold vacuum) Fuel Rail Pressure (diesel, or gasoline direct inject) O2S1_WR_lambda(1): Equivalence Ratio Voltage

01

22

5177.265

kPa

((A*256)+B) * 0.079

01

23

655,350

kPa (gauge) ((A*256)+B) * 10

01

24

0 0

1.999 7.999

N/A V

((A*256)+B)*2/65535 or ((A*256)+B)/32768 ((C*256)+D)*8/65535 or ((C*256)+D)/8192 ((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01

25

O2S2_WR_lambda(1): Equivalence Ratio Voltage O2S3_WR_lambda(1): Equivalence Ratio Voltage

0 0

2 8

N/A V

01

26

0 0

2 8

N/A V

((A*256)+B)*2/65535 ((C*256)+D)*8/65535

OBD-II PIDs

4
4 O2S4_WR_lambda(1): Equivalence Ratio Voltage O2S5_WR_lambda(1): Equivalence Ratio Voltage O2S6_WR_lambda(1): Equivalence Ratio Voltage O2S7_WR_lambda(1): Equivalence Ratio Voltage O2S8_WR_lambda(1): Equivalence Ratio Voltage Commanded EGR EGR Error Commanded evaporative purge Fuel Level Input # of warm-ups since codes cleared Distance traveled since codes cleared Evap. System Vapor Pressure Barometric pressure 0 0 2 8 N/A V ((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01

27

01

28

0 0

2 8

N/A V

((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01

29

0 0

2 8

N/A V

((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01

2A

0 0

2 8

N/A V

((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01

2B

0 0

2 8

N/A V

((A*256)+B)*2/65535 ((C*256)+D)*8/65535

01 01 01 01 01

2C 2D 2E 2F 30

1 1 1 1 1

0 -100 0 0 0

100 99.22 100 100 255

% % % % N/A

100*A/255 (A-128) * 100/128 100*A/255 100*A/255 A

01

31

65,535

km

(A*256)+B

01 01

32 33

2 1

-8,192 0

8,192 255

Pa kPa (Absolute) N/A mA

((A*256)+B)/4 (A is signed) A

01

34

O2S1_WR_lambda(1): Equivalence Ratio Current O2S2_WR_lambda(1): Equivalence Ratio Current O2S3_WR_lambda(1): Equivalence Ratio Current O2S4_WR_lambda(1): Equivalence Ratio Current O2S5_WR_lambda(1): Equivalence Ratio Current O2S6_WR_lambda(1): Equivalence Ratio Current O2S7_WR_lambda(1): Equivalence Ratio Current

0 -128

1.999 127.99

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

35

0 -128

2 128

N/A mA

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

36

0 -128

2 128

N/A mA

((A*256)+B)/32768 ((C*256)+D)/256 - 128

01

37

0 -128

2 128

N/A mA

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

38

0 -128

2 128

N/A mA

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

39

0 -128

2 128

N/A mA

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

3A

0 -128

2 128

N/A mA

((A*256)+B)/32,768 ((C*256)+D)/256 - 128

OBD-II PIDs

5
4 O2S8_WR_lambda(1): Equivalence Ratio Current Catalyst Temperature Bank 1, Sensor 1 Catalyst Temperature Bank 2, Sensor 1 Catalyst Temperature Bank 1, Sensor 2 Catalyst Temperature Bank 2, Sensor 2 PIDs supported [41 - 60] 0 -128 2 128 N/A mA ((A*256)+B)/32,768 ((C*256)+D)/256 - 128

01

3B

01

3C

-40

6,513.5

((A*256)+B)/10 - 40

01

3D

-40

6,513.5

((A*256)+B)/10 - 40

01

3E

-40

6,513.5

((A*256)+B)/10 - 40

01

3F

-40

6,513.5

((A*256)+B)/10 - 40

01

40

Bit encoded [A7..D0] == [PID 0x41..PID 0x60] See below. Bit encoded. See below. 0 0 0 0 -40 0 0 0 0 0 0 0 65.535 25,700 2 100 215 100 100 100 100 100 100 65,535 65,535 255, 255, 255, 2550 V % N/A % C % % % % % % minutes minutes , V, mA, kPa ((A*256)+B)/1000 ((A*256)+B)*100/255 ((A*256)+B)/32768 A*100/255 A-40 A*100/255 A*100/255 A*100/255 A*100/255 A*100/255 A*100/255 (A*256)+B (A*256)+B A, B, C, D*10

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F

4 2 2 2 1 1 1 1 1 1 1 1 2 2 4

Monitor status this drive cycle Control module voltage Absolute load value Command equivalence ratio Relative throttle position Ambient air temperature Absolute throttle position B Absolute throttle position C Accelerator pedal position D Accelerator pedal position E Accelerator pedal position F Commanded throttle actuator Time run with MIL on

Time since trouble codes cleared 0 Maximum value for equivalence ratio, oxygen sensor voltage, oxygen sensor current, and intake manifold absolute pressure Maximum value for air flow rate from mass air flow sensor Fuel Type Ethanol fuel % Absolute Evap system Vapour Pressure Evap system vapor pressure Short term secondary oxygen sensor trim bank 1 and bank 3 Long term secondary oxygen sensor trim bank 1 and bank 3 Short term secondary oxygen sensor trim bank 2 and bank 4 0 0 0, 0, 0, 0

01

50

2550

g/s

A*10, B, C, and D are reserved for future use From fuel type table see below

01 01 01

51 52 53

1 1 2

100 327.675

% kPa

A*100/255 1/200 per bit

01 01

54 55

2 2

-32,767 -100

32,768 99.22

Pa %

A*256+B - 32768 (A-128)*100/128 (B-128)*100/128 (A-128)*100/128 (B-128)*100/128 (A-128)*100/128 (B-128)*100/128

01

56

-100

99.22

01

57

-100

99.22

OBD-II PIDs

6
2 Long term secondary oxygen sensor trim bank 2 and bank 4 Fuel rail pressure (absolute) Relative accelerator pedal position Hybrid battery pack remaining life Engine oil temperature Fuel injection timing Engine fuel rate Emission requirements to which vehicle is designed PIDs supported [61 - 80] -100 99.22 % (A-128)*100/128 (B-128)*100/128 ((A*256)+B) * 10 A*100/255

01

58

01 01

59 5A

2 1

0 0

655,350 100

kPa %

01

5B

100

A*100/255

01 01 01 01

5C 5D 5E 5F

1 2 2 1

-40 -210.00 0

210 301.992 3212.75

C L/h

A - 40 (((A*256)+B)-26,880)/128 ((A*256)+B)*0.05 Bit Encoded

01

60

Bit encoded [A7..D0] == [PID 0x61..PID 0x80] See below. 125 % A-125

01

61

Driver's demand engine - percent -125 torque Actual engine - percent torque Engine reference torque Engine percent torque data -125 0 -125

01 01 01

62 63 64

1 2 5

125 65,535 125

% Nm %

A-125 A*256+B A-125 Idle B-125 Engine point 1 C-125 Engine point 2 D-125 Engine point 3 E-125 Engine point 4 Bit Encoded

01

65

Auxiliary input / output supported Mass air flow sensor Engine coolant temperature Intake air temperature sensor Commanded EGR and EGR Error Commanded Diesel intake air flow control and relative intake air flow position Exhaust gas recirculation temperature Commanded throttle actuator control and relative throttle position Fuel pressure control system Injection pressure control system Turbocharger compressor inlet pressure Boost pressure control Variable Geometry turbo (VGT) control Wastegate control

01 01 01 01

66 67 68 69

5 3 7 7

01

6A

01

6B

01

6C

01 01 01

6D 6E 6F

6 5 3

01 01

70 71

9 5

01

72

OBD-II PIDs

7
5 5 7 7 5 Exhaust pressure Turbocharger RPM Turbocharger temperature Turbocharger temperature Charge air cooler temperature (CACT) Exhaust Gas temperature (EGT) Bank 1 Exhaust Gas temperature (EGT) Bank 2 Diesel particulate filter (DPF) Diesel particulate filter (DPF) Diesel Particulate filter (DPF) temperature NOx NTE control area status PM NTE control area status Engine run time PIDs supported [81 - A0] Bit encoded [A7..D0] == [PID 0x81..PID 0xA0] See below. Special PID. See below.

01 01 01 01 01

73 74 75 76 77

01

78

01

79

Special PID. See below.

01 01 01

7A 7B 7C

7 7 9

01 01 01 01

7D 7E 7F 80

1 1 13 4

01 01 01 01 01 01 01

81 82 83 84 85 86 87

21 21 5

Engine run time for AECD Engine run time for AECD NOx sensor Manifold surface temperature NOx reagent system Particulate matter (PM) sensor Intake manifold absolute pressure

01

A0

PIDs supported [A1 - C0]

Bit encoded [A7..D0] == [PID 0xA1..PID 0xC0] See below. Bit encoded [A7..D0] == [PID 0xC1..PID 0xE0] See below. ? ? ? Returns numerous data, including Drive Condition ID and Engine Speed* B5 is Engine Idle Request B6 is Engine Stop Request* BCD encoded, See below. 3 codes per message frame, BCD encoded. See below. Clears all stored trouble codes and turns the MIL off.

01

C0

PIDs supported [C1 - E0]

01

C3

01

C4

02 03

02 N/A

2 n*6

Freeze frame trouble code Request trouble codes

04

N/A

Clear trouble codes / Malfunction indicator lamp (MIL) / Check engine light OBD Monitor IDs supported ($01 $20)

05

0100

OBD-II PIDs

8
O2 Sensor Monitor Bank 1 Sensor 1 O2 Sensor Monitor Bank 1 Sensor 2 O2 Sensor Monitor Bank 1 Sensor 3 O2 Sensor Monitor Bank 1 Sensor 4 O2 Sensor Monitor Bank 2 Sensor 1 O2 Sensor Monitor Bank 2 Sensor 2 O2 Sensor Monitor Bank 2 Sensor 3 O2 Sensor Monitor Bank 2 Sensor 4 O2 Sensor Monitor Bank 3 Sensor 1 O2 Sensor Monitor Bank 3 Sensor 2 O2 Sensor Monitor Bank 3 Sensor 3 O2 Sensor Monitor Bank 3 Sensor 4 O2 Sensor Monitor Bank 4 Sensor 1 O2 Sensor Monitor Bank 4 Sensor 2 O2 Sensor Monitor Bank 4 Sensor 3 O2 Sensor Monitor Bank 4 Sensor 4 O2 Sensor Monitor Bank 1 Sensor 1 O2 Sensor Monitor Bank 1 Sensor 2 O2 Sensor Monitor Bank 1 Sensor 3 O2 Sensor Monitor Bank 1 Sensor 4 O2 Sensor Monitor Bank 2 Sensor 1 O2 Sensor Monitor Bank 2 Sensor 2 O2 Sensor Monitor Bank 2 Sensor 3 0.00 1.275 Volts 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Rich to lean sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage

05

0101

05

0102

0.00

1.275

Volts

05

0103

0.00

1.275

Volts

05

0104

0.00

1.275

Volts

05

0105

0.00

1.275

Volts

05

0106

0.00

1.275

Volts

05

0107

0.00

1.275

Volts

05

0108

0.00

1.275

Volts

05

0109

0.00

1.275

Volts

05

010A

0.00

1.275

Volts

05

010B

0.00

1.275

Volts

05

010C

0.00

1.275

Volts

05

010D

0.00

1.275

Volts

05

010E

0.00

1.275

Volts

05

010F

0.00

1.275

Volts

05

0110

0.00

1.275

Volts

05

0201

0.00

1.275

Volts

05

0202

0.00

1.275

Volts

05

0203

0.00

1.275

Volts

05

0204

0.00

1.275

Volts

05

0205

0.00

1.275

Volts

05

0206

0.00

1.275

Volts

05

0207

0.00

1.275

Volts

OBD-II PIDs

9
O2 Sensor Monitor Bank 2 Sensor 4 O2 Sensor Monitor Bank 3 Sensor 1 O2 Sensor Monitor Bank 3 Sensor 2 O2 Sensor Monitor Bank 3 Sensor 3 O2 Sensor Monitor Bank 3 Sensor 4 O2 Sensor Monitor Bank 4 Sensor 1 O2 Sensor Monitor Bank 4 Sensor 2 O2 Sensor Monitor Bank 4 Sensor 3 O2 Sensor Monitor Bank 4 Sensor 4 4 1x5 mode 9 supported PIDs 01 to 20 VIN Message Count in command 09 02 0.00 1.275 Volts 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage 0.005 Lean to Rich sensor threshold voltage Bit encoded Returns 1 line/packet (49 01 05 00 00 00 00), where 05 means 05 packets will be returned in VIN digits. Returns the VIN as a multi-frame response using the ISO 15765-2 protocol. This is typically five frames, with the first frame encoding the size and count. Returns multiple lines, ASCII coded

05

0208

05

0209

0.00

1.275

Volts

05

020A

0.00

1.275

Volts

05

020B

0.00

1.275

Volts

05

020C

0.00

1.275

Volts

05

020D

0.00

1.275

Volts

05

020E

0.00

1.275

Volts

05

020F

0.00

1.275

Volts

05

0210

0.00

1.275

Volts

09 09

00 01

09

02

5x5

Vehicle identification number (VIN)

09 09

04 06

varies 4

calibration ID calibration

In the formula column, letters A, B, C, etc. represent the decimal equivalent of the first, second, third, etc. bytes of data. Where a (?) appears, contradictory or incomplete information was available. Someone with a copy of the 2006 SAE HS-3000 should fact-check these.

Bitwise encoded PIDs

Some of the PIDs in the above table cannot be explained with a simple formula. A more elaborate explanation of these data is provided here: Mode 1 PID 00: A request for this PID returns 4 bytes of data. The four bytes are giving information about which of the next 32 PIDs are supported. The response can be decoded like this: If the car response is BE 1F A8 13, then transform that in binary. B E 1 F A 8 1 3 ---- ---- ---- ---- ---- ---- ---- ---------1011 1110 0001 1111 1010 1000 0001 0 0 1 1 1234 5678 .... .... .... .... .... 29 30 31 32

supported? PID num 0 = not supported 1 = supported

OBD-II PIDs Mode 1 PID 01: A request for this PID returns 4 bytes of data. The first two bytes are identical for both spark ignition (Gasoline) and compression ignition (Diesel) engines. The third and fourth bytes are to be interpreted differently depending on if the engine is spark ignition or compression ignition. In the second (B) byte, bit 3 tells you which way to interpret the C and D bytes, with 0 being spark and 1 (set) being compression. The first byte contains two pieces of information. Bit A7 (the eighth bit of byte A, the first byte) indicates whether or not the MIL (check engine light) is illuminated. Bits A0 through A6 represent the number of diagnostic trouble codes currently flagged in the ECU. The second, third, and fourth bytes give information about the availability and completeness of certain on-board tests. Note that test availability signified by set (1) bit; completeness signified by reset (0) bit:
Bit Name Definition Number of confirmed emissions-related DTCs available for display. Off or On, indicates if the CEL/MIL is on (or should be on) 0 = Spark ignition monitors supported 1 = Compression ignition monitors supported

10

A0-A6 DTC_CNT A7 B3 B7 MIL NO NAME

RESERVED RESERVED

Here are the common bit B definitions, they're test based. Test available B0 B1 B2 Test incomplete B4 B5 B6

Misfire Fuel System Components

The byte C and D spark ignition monitors: Test available Catalyst C0 Heated Catalyst C1 Evaporative System C2 Secondary Air System C3 A/C Refrigerant C4 Oxygen Sensor C5 Oxygen Sensor Heater C6 EGR System C7 And the byte C and D compression ignition monitors: Test available NMHC Cat C0 NOx/SCR Monitor C1 Boost Pressure C3 Exhaust Gas Sensor C5 PM filter monitoring C6 EGR and/or VVT System C7 Test incomplete D0 D1 D3 D5 D6 D7 Test incomplete D0 D1 D2 D3 D4 D5 D6 D7

NMHC *may* stand for non-methane hydrocarbons catalyst, but J1979 does not enlighten us. Mode 1 PID 03: A request for this PID returns 2 bytes of data. The first byte describes fuel system #1. Only one bit should ever be set.

OBD-II PIDs
A0 A1 A2 A3 A4 A5-A7 Open loop due to insufficient engine temperature Closed loop, using oxygen sensor feedback to determine fuel mix Open loop due to engine load OR fuel cut due to deceleration Open loop due to system failure Closed loop, using at least one oxygen sensor but there is a fault in the feedback system Always zero

11

The second byte describes fuel system #2 (if it exists) and is encoded identically to the first byte. Mode 1 PID 12: A request for this PID returns a single byte of data which describes the secondary air status. Only one bit should ever be set. A0 A1 A2 A3-A7 Upstream of catalytic converter Downstream of catalytic converter From the outside atmosphere or off Always zero

Mode 1 PID 1C: A request for this PID returns a single byte of data which describes which OBD standards this ECU was designed to comply with. The hexadecimal and binary representations of the data byte are shown below next to what it implies: 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 00000001b 00000010b 00000011b 00000100b 00000101b 00000110b 00000111b 00001000b 00001001b 00001010b 00001011b 00001100b 00001101b OBD-II as defined by the CARB OBD as defined by the EPA OBD and OBD-II OBD-I Not meant to comply with any OBD standard EOBD (Europe) EOBD and OBD-II EOBD and OBD EOBD, OBD and OBD II JOBD (Japan) JOBD and OBD II JOBD and EOBD JOBD, EOBD, and OBD II

Mode 1 PID 41: A request for this PID returns 4 bytes of data. The first byte is always zero. The second, third, and fourth bytes give information about the availability and completeness of certain on-board tests. Note that test availability signified by set (1) bit; completeness signified by reset (0) bit: Test enabled Misfire B0 Fuel System B1 Components B2 Reserved B3 Catalyst C0 Heated Catalyst C1 Evaporative System C2 Secondary Air System C3 A/C Refrigerant C4 Oxygen Sensor C5 Oxygen Sensor Heater C6 Test incomplete B4 B5 B6 B7 D0 D1 D2 D3 D4 D5 D6

OBD-II PIDs EGR System C7 D7

12

Mode 3: (no PID required) A request for this mode returns a list of the DTCs that have been set. The list is encapsulated using the ISO 15765-2 protocol. If there are two or fewer DTC's (4 bytes) they are returned in an ISO-TP Single Frame (SF). Three or more DTCs in the list are reported in multiple frames, with the exact count of frames dependent on the communication type and addressing details. Each trouble code requires 2 bytes to describe. The text description of a trouble code may be decoded as follows. The first character in the trouble code is determined by the first two bits in the first byte: A7 A6 -- -0 0 0 1 1 0 1 1 First DTC character ------------------P - Powertrain C - Chassis B - Body U - Network

The four following digits are BCD encoded. The second character in the DTC is a number defined by A5 A4 -- -0 0 0 1 1 0 1 1 Second DTC character -------------------0 1 2 3

The third character in the DTC is a number defined by A3 A2 A1 A0 -- -- -- -0 0 0 0 0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 1 0 1 1 0 0 1 1 1 1 0 0 0 1 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 1 0 1 1 1 1 0 1 1 1 1 Third DTC character ------------------0 1 2 3 4 5 6 7 8 9 A B C D E F

The fourth and fifth characters are defined in the same way as the third, but using bits B7..B4 and B3..B0. The resulting five-character code should look something like "U0158" and can be looked up in a table of OBD-II DTCs.

OBD-II PIDs Hexadecimal characters (0-9,A-F), while relatively rare, are allowed in the last 3 positions of the code itself.

13

Fuel Type Coding

Mode 1 PID 0x51 returns a value from an enumerated list giving the fuel type of the vehicle. The fuel type is returned as a single byte, and the value is given by 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 Gasoline Methanol Ethanol Diesel LPG CNG Propane Electric Bifuel running Gasoline Bifuel running Methanol Bifuel running Ethanol Bifuel running LPG Bifuel running CNG Bifuel running Prop Bifuel running Electricity Bifuel mixed gas/electric Hybrid gasoline Hybrid Ethanol Hybrid Diesel Hybrid Electric Hybrid Mixed fuel Hybrid Regenerative

Special PIDs
Some PIDs are to be interpreted specially, and aren't necessarily exactly "bitwise encoded" Mode 1 PID 78 A request for this PID will return 9 bytes of data. The first byte is a bit encoded field indicating which sensors are supported: Sensor Supported A0 A1 A2 A3 A4 A5 A6 A7

EGT11 EGT12 EGT13 EGT14 Reserved Reserved Reserved Reserved

The remaining bytes are 16 bit integers indicating the temperature in Degrees celsius in the range -40 to 6513.5 (scale 0.1) using the usual ((A*256)+B)-40 formula.

OBD-II PIDs Mode 1 PID 79 A request for this PID will return 9 bytes of data. See Mode 1 PID 78 (above) for a description.

14

Non-standard PIDs
The majority of all OBD-II PIDs in use are non-standard. For most modern vehicles, there are many more functions supported on the OBD-II interface than are covered by the standard PIDs, and there is relatively minor overlap between vehicle manufacturers for these non-standard PIDs. AutoEnginuity, who manufactures OBD-II scan tools, provides the following example on their website[2]: Although Ford does implement the largest subset of the OBDII standard, the typical vehicle only supports 20 - 40 [standard] sensors and is limited to the emissions powertrain. Using the enhanced Ford interface, a typical Ford vehicle will support 200 - 300 sensors within half a dozen systems; that's essential systems such as ABS, airbags, GEM, ICM, etc. Our enhanced Ford interface coverage is only matched by factory tools; we have support for 3,400+ [Ford] sensors selected from all 58 [Ford] systems. There is very limited information available in the public domain for non-standard PIDs. The primary source of information on non-standard PIDs across different manufacturers is maintained by the US-based Equipment and Tool Institute and only available to members. The price of ETI membership for access to scan codes starts from US $7500[3] However, even ETI membership will not provide full documentation for non-standard PIDs. ETI state[3] Some OEMs refuse to use ETI as a one-stop source of scan tool information. They prefer to do business with each tool company separately. These companies also require that you enter into a contract with them. The charges vary but here is a snapshot of today's per year charges as we know them: GM $50,000 Honda $5,000 Suzuki $1,000 BMW $7,000 plus $1,000 per update. Updates occur every quarter. (This is more now, but do not have exact number)

CAN (11-bit) Bus format

The PID query and response occurs on the vehicle's CAN Bus. Standard OBD requests and responses use functional addresses. The diagnostic reader initiates a query using CAN ID 0x7DF, which acts as a broadcast address, and accepts responses from any ID in the range 0x7E8 to 0x7EF. ECUs that can respond to OBD queries listen both to the functional broadcast ID of 0x7DF and one assigned ID in the range 0x7E0 to 0x7E7. Their response has an ID of their assigned ID plus 8 e.g. 0x7E8 through 0x7EF. This approach allows up to eight ECUs, each independently responding to OBD queries. The diagnostic reader can use the ID in the ECU response frame to continue communication with a specific ECU. In particular, multi-frame communication requires a response to the specific ECU ID rather than to ID 0x7DF. CAN bus may also be used for communication beyond the standard OBD messages. Physical addressing uses particular CAN IDs for specific modules (e.g., 720 for the instrument cluster in Fords) with proprietary frame payloads.

OBD-II PIDs

15

Query
The functional PID query is sent to the vehicle on the CAN bus at ID 7DFh, using 8 data bytes. The bytes are:
Byte -> SAE Standard _0_ Number of additional data bytes: 2 _1_ Mode 01 = show current data; 02 = freeze frame; etc. _2_ _3_ _4_ _5_ _6_ _7_

PID code not used (e.g.: 05 = Engine coolant temperature) (may be 55h)

Vehicle specific Number Custom mode: (e.g.: 22 = enhanced data) PID code of (e.g.: 4980h) additional data bytes: 3

not used (may be 00h or 55h)

Response
The vehicle responds to the PID query on the CAN bus with message IDs that depend on which module responded. Typically the engine or main ECU responds at ID 7E8h. Other modules, like the hybrid controller or battery controller in a Prius, respond at 07E9h, 07EAh, 07EBh, etc. These are 8h higher than the physical address the module responds to. Even though the number of bytes in the returned value is variable, the message uses 8 data bytes regardless. The bytes are:
Byte -> SAE Standard 7E8h, 7E9h, 7EAh, etc. _0_ Number of additional data bytes: 3 to 6 _1_ Custom mode Same as query, except that 40h is added to the mode value. So: 41h = show current data; 42h = freeze frame; etc. _2_ PID code (e.g.: 05 = Engine coolant temperature) _3_ value of the specified parameter, byte 0 _4_ value, byte 1 (optional) _5_ _6_ _7_

value, byte value, byte not used 2 3 (may be (optional) (optional) 00h or 55h)

Vehicle specific 7E8h, or 8h + physical ID of module. Vehicle specific 7E8h, or 8h + physical ID of module.

Number of additional data bytes: 4to 7 Number of additional data bytes: 3

Custom mode: same as PID code query, except that 40h is (e.g.: 4980h) added to the mode value.(e.g.: 62h = response to mode 22h request) 7Fh this a general response usually indicating the module doesn't recognize the request. Custom mode: (e.g.: 22h = enhanced diagnostic data by PID, 21h = enhanced data by offset) 31h

value of the specified parameter, byte 0

value, byte value, byte value, byte 1 2 3 (optional) (optional) (optional)

not used (may be 00h)

OBD-II PIDs

16

References
[1] http:/ / www. eaa-phev. org/ wiki/ Escape_PHEV_TechInfo#PIDs [2] "AutoEnginuity's Scan Tool - Enhanced interface for Ford" (http:/ / www. autoenginuity. com/ products-software. html#EI01). . Retrieved 30 September 2009. [3] "ETI Full Membership FAQ" (http:/ / www. etools. org/ files/ public/ Full_Member_FAQ. htm). . Retrieved 30 September 2009.showing cost of access to OBD-II PID documentation

External links
OBD-II Codes Definition (http://www.obd-2-codes.com/) OBD-II codes definition, description and repair information. (http://www.permoveo.ltd.uk/TechnicalResources.aspx) OBD code definitions, including manufacture codes. (http://www.motorstate.com.ua/a/31998L0069.htm) Directive 98/69/EC of the European Parliament and of the Council of 13 October 1998. CAN Bus Vehicles (http://www.auterraweb.com/aboutcan.html), make, model and year vehicles that support OBD II CAN bus Fault Code Examples (http://kbmsystems.net/files/Engine ECU Fault Code Reading with OBDKey.pdf) Sample fault code data read using the OBDKey Bluetooth, OBDKey USB and OBDKey WLAN vehicle interface units.

Article Sources and Contributors

17

Article Sources and Contributors

OBD-II PIDs Source: http://en.wikipedia.org/w/index.php?oldid=480268184 Contributors: 00Asti, 4johnny, Alf.laylah.wa.laylah, Austinmurphy, Bill Michaelson, Bobblewik, CMG, CZmarlin, Carlb, Cobrajet carl, Cobrajet7071, DavideAndrea, Dcm684, Donald.becker, Download, Duffbeerforme, Eastmain, Egil, Frdric, Gnukix, HamishAhern, Hbachus, Imzjustplayin, Ivanl, Jfinney10, Jynx-Me, Lightner, Martin.barrera.c, Mboverload, Mouser, OBDII-Tech, OSX, PigFlu Oink, Pmsyyz, Raulakh, Ron Ritzman, Russ138, Russer3232, Sbmeirow, Teferrin, Titogarci, Tripzero, Uncle G, 103 anonymous edits

License
Creative Commons Attribution-Share Alike 3.0 Unported //creativecommons.org/licenses/by-sa/3.0/