ELM327P datasheet(28/51 Pages) ELM

28 / 51 page

Setting the Headers (Cont’d)

28 of 51

ELM327

ELM327DSC

Elm Electronics – Circuits for the Hobbyist

www.elmelectronics.com

>AT SH xx yy zz

>AT CP vv

5 bits only

29 bit ID

Figure 5. Setting a 29 bit CAN ID

Electronics does not maintain lists of this information,

and cannot provide any further details for you. Mode

22 and others are described in more detail in SAE

document J2190, “Enhanced E/E Diagnostic Test

Modes”.

The ISO14230-4 standard defines its’ header

bytes a little differently. Advanced experimenters will

be aware that for ISO 14230-4, the first header byte

must always include the length of the data field, which

varies from message to message. From that, one

might assume that the you would need to redefine the

header for every message that is to be sent – not so!

The ELM327 always determines the number of bytes

that you are sending, and inserts that length for you, in

the proper place for the header that you are using. If

you are using the standard ISO 14230-4 header, the

length will be put into the first header byte, and you

need only provide the two (most significant) bits of this

byte when defining the header. What you place in the

rest of the byte will be ignored by the ELM327 unless

you set them all to 0’s. If they are all 0, it is assumed

that you are experimenting with KWP four byte

headers, and the ELM327 then creates the fourth

header byte for you. Again, you do not need to provide

any length to be put into this byte – it is done for you.

Addressing

within

the

CAN

(ISO

15765-4)

protocols is quite similar in many ways. First, consider

the 29 bit standard. The ELM327 splits the 29 bits into

a CAN Priority byte and the three header bytes that we

are now familiar with. Figure 5 shows how these are

combined for use by the ELM327.

The CAN standard states that for diagnostics, the

priority byte (‘vv’ in the diagram) will always be 1B (this

>AT SH xx yy zz

11 bit ID

Figure 6. Setting an 11 bit CAN ID

is the default value used by the ELM327). Since it is

rarely changed, it is assigned separately from the

other header bytes, using the CP command. Changing

of this value is usually only required if experimenting

with J1939 systems.

The next byte (‘xx’) describes the type of message

that this is, and is set to hex DB for functional

addressing, and to DA if using physical addressing.

The next two bytes are as defined previously for the

other standards – ‘yy’ is the receiver (or Target

Address), and ‘zz’ is the transmitter (or Source

Address). For the functional diagnostic requests, the

receiver is always 33, and the transmitter is F1, which

is very similar to ISO 14230-4.

Those that are familiar with the SAE J1939

standard will likely find this header structure to be very

familiar (J1939 is a CAN standard for use by ‘heavy-

duty vehicles’ such as trucks and buses). We use

slightly different terminology, but there is a direct

parallel between the bytes used by J1939 for the

headers and the grouping of the bytes in the ELM327.

Refer to page 36 for a discussion of the J1939 support

that is provided by the ELM327.

The final header format to discuss is that used in

11 bit CAN systems. They also use a priority/address

structure, but shorten it into roughly three nibbles

rather than three bytes. The ELM327 uses the same

commands to set these values as for other headers,

except that it only uses the 11 least significant (‘right-

most’) bits of the provided header bytes, and ignores

the others (as shown in Figure 6). It quickly becomes

inconvenient to have to enter six digits when only three

are required, so there is a special ‘short’ version of the

ELM327P Datasheet(PDF) 28 Page - ELM Electronics

ELM327P Datasheet(HTML) 28 Page - ELM Electronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51

Datasheet Download

Link URL