Manual Elm 327 (page 34 of 94) (English)

612699

Zoom out

Zoom in

1/94

Interpreting Trouble Codes

Likely the most common use that the ELM327 will

be put to is in obtaining the current Diagnostic Trouble

Codes (or DTCs). Minimally, this requires that a mode

03 request be made, but first one should determine

how many trouble codes are presently stored. This is

done with a mode 01 PID 01 request as follows:

>01 01

To which a typical response might be:

41 01 81 07 65 04

The 41 01 signifies a response to the request, and

the next data byte (81) is the number of current trouble

codes. Clearly there would not be 81 (hex) or 129

(decimal) trouble codes present if the vehicle is at all

operational. In fact, this byte does double duty, with

the most significant bit being used to indicate that the

malfunction indicator lamp (MIL, or ‘Check Engine

Light’) has been turned on by one of this module’s

codes (if there are more than one), while the other 7

bits of this byte provide the actual number of stored

trouble codes. In order to calculate the number of

stored codes when the MIL is on, simply subtract 128

(or 80 hex) from the number.

The above response then indicates that there is

one stored code, and it was the one that set the Check

Engine Lamp or MIL on. The remaining bytes in the

response provide information on the types of tests

supported by that particular module (see the J1979

document for further information).

In this instance, there was only one line to the

response, but if there were codes stored in other

modules, they each could have provided a line of

response. To determine which module is reporting the

trouble code, one would have to turn the headers on

(AT H1) and then look at the third byte of the three

byte header for the address of the module that sent

the information.

Having determined the number of codes stored,

the next step is to request the actual trouble codes

with a mode 03 request (there is no PID needed):

>03

A response to this could be:

43 01 33 00 00 00 00

The ‘43’ in the above response simply indicates

that this is a response to a mode 03 request. The other

6 bytes in the response have to be read in pairs to

show the trouble codes (the above would be

interpreted as 0133, 0000, and 0000). Note that the

response has been padded with 00’s as required by

the SAE standard for this mode – the 0000’s do not

represent actual trouble codes.

As was the case when requesting the number of

stored codes, the most significant bits of each trouble

code also contain additional information. It is easiest to

use the following table to interpret the extra bits in the

first digit as follows:

Powertrain Codes - SAE defined0

“ “ - manufacturer defined

“ “ - SAE defined

“ “ - jointly defined

If the first hex digit received is this,

Replace it with these two characters

Chassis Codes - SAE defined4

“ “ - reserved for future

Body Codes - SAE defined8

Network Codes - SAE definedC

“ “ - reserved for future

“ “ - manufacturer defined

“ “ - reserved for future

Taking the example trouble code (0133), the first

digit (0) would then be replaced with P0, and the 0133

reported would become P0133 (which is the code for

an ‘oxygen sensor circuit slow response’). Note that

the ISO 15765-4 (CAN) protocol is very similar, but it

adds an extra data byte (in the second position),

showing how many data items (DTCs) are to follow.

To provide a few more examples, if the received

code was D016, you would replace the D with U1, and

the resulting trouble code would be U1016. Similarly,

1131 received would actually be for the code P1131.

34 of 94

ELM327

ELM327DSJ Elm Electronics – Circuits for the Hobbyist

www.elmelectronics.com

Report abuse

Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.

Product:

Forumrules

To achieve meaningful questions, we apply the following rules:

First, read the manual;
Check if your question has been asked previously;
Try to ask your question as clearly as possible;
Did you already try to solve the problem? Please mention this;
Is your problem solved by a visitor then let him/her know in this forum;
To give a response to a question or answer, do not use this form but click on the button 'reply to this question';
Your question will be posted here and emailed to our subscribers. Therefore, avoid filling in personal details.

new questions and answers
new manuals

You will receive an email to register for one or both of the options.

Get your user manual by e-mail

Enter your email address to receive the manual of Elm 327 in the language / languages: English as an attachment in your email.

The manual is 0,23 mb in size.

You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.

The manual is sent by email. Check your email

If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.

The email address you have provided is not correct.

Please check the email address and correct it.

Your question is posted on this page

Would you like to receive an email when new answers and questions are posted? Please enter your email address.

Info

Elm 327 Manual

Product: