ELM327LP datasheet(39/94 Pages) ELM

39 / 94 page

To this point we have only discussed the contents

(data portion) of an OBD message, and made only

passing mention of other parts such as headers and

checksums, which all messages use to some extent.

On Board Diagnostics systems are designed to be

very flexible, providing a means for several devices to

communicate with one another. In order for messages

to be sent between devices, it is necessary to add

information describing the type of information being

sent, the device that it is being sent to, and perhaps

which device is doing the sending. Additionally, the

importance of the message becomes a concern as

well – crankshaft position information is certainly of

considerably more importance to a running engine

than a request for the number of trouble codes stored,

or the vehicle serial number. So to convey importance,

messages are also assigned a priority.

The

information

describing

the

priority,

the

intended recipient, and the transmitter are usually

needed by the recipient even before they know the

type of request that the message contains. To ensure

that this information is obtained first, OBD systems

transmit it at the start (or head) of the message. Since

these bytes are at the head, they are usually referred

39 of 94

ELM327L

ELM327L DSA

Elm Electronics – Circuits for the Hobbyist

www.elmelectronics.com

to as header bytes. Figure 3 below shows a typical

OBD

message

structure

that

used

the

SAE J1850, ISO 9141-2, and ISO 14230-4 standards.

It uses 3 header bytes as shown, to provide details

concerning

the

priority,

the

receiver,

and

the

transmitter. Note that many texts refer to the receiver

as the ‘Target Address’ (TA), and the transmitter as

the ‘Source Address’ (SA).

Another concern when sending any message is

that errors might occur in the transmission, and the

received data may be falsely interpreted. To detect

errors, the various protocols all provide some form of

check on the received data. This may be as simple as

a sum calculation (ie a ‘running total’ of byte values)

that is sent at the end of a message. If the receiver

also calculates a sum as bytes are received, then the

two values can be compared and if they do not agree,

the receiver will know that an error has occurred.

Since simple sums might not detect multiple errors, a

more reliable (and more complicated) sum called a

Cyclic Redundancy Check (or ‘CRC’) is often used. All

of the protocols specify how errors are to be detected,

and the various ways of handling them if they occur.

The

OBD

data

bytes

are

thus

normally

Figure 3. An OBD Message

Figure 4. A CAN OBD Message

up to 7 data bytes

checksum

3 header bytes

priority

receiver

transmitter

OBD Message Formats

ID bits (11 or 29)

7 data bytes

checksum

PCI

data bytes (8 in total)

‘header’ bytes

ELM327LP датащи(PDF) 39 Page - ELM Electronics

ELM327LP датащи(HTML) 39 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 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94

датащи скачать

ссылки URL