F1-407-1355-002 -M145 TPMS Diagnostics Specification V1_02

F1-407-1355-002 -M145 TPMS Diagnostics

Specification V1_02.doc

BERU f1systems James Shingleton

Diss, UK, 16.02.10 of 59

Diagnostics Specification M145 TPMS

Maserati

Author: James Shingleton Last modified by: Sathyan Jeyahar

Version 1.02 of 11/02/2010




Diss, UK, 16.02.10 of 59

Authors:

Name Company, Dept. Contact James Shingleton BERU f1systems, R&D Tel.: +44 1379 646216

Fax: +44 1379 646900 E-Mail: [email protected]

Sathyan Jeyahar BERU f1systems, R&D Tel.: +44 1379 646200 Fax: +44 1379 646900 E-Mail: [email protected]

Revisions list:

Version Author Date Status Reason 1.01 JRS 11/02/2010 First draft Document created

1.02 SJ 11/02/10 Second draft Routine control behaviour updated, Writing of Active pressure map removed, ReadStatusofDTC behaviour updated




Diss, UK, 16.02.10 of 59

Table of Contents 1 Conventions ..................................................................................................... 5 2 Overview........................................................................................................... 6

2.1 Control Unit................................................................................................................................................. 6

2.2 Variants ....................................................................................................................................................... 6 3 Protocol Services............................................................................................. 7

3.1 Overview ..................................................................................................................................................... 7

3.2 ($10) StartDiagnosticSession ...................................................................................................................... 8

3.3 ($14) ClearDiagnosticInformation............................................................................................................... 9

3.4 ($17) ReadStatusOfDiagnosticTroubleCodes............................................................................................ 10

3.5 ($18) ReadDiagnosticTroubleCodesByStatus ........................................................................................... 11

3.6 ($1A) ReadEcuIdentification..................................................................................................................... 12

3.7 ($20) StopDiagnosticSession..................................................................................................................... 13

3.8 ($21) ReadDataByLocalIdentifier ............................................................................................................. 14

3.9 ($27) securityAccess ................................................................................................................................. 15

3.10 ($31) StartRoutineByLocalIdentifier......................................................................................................... 17

3.11 ($32) StopRoutineByLocalIdentifier ......................................................................................................... 18

3.12 ($3B) WriteDataByLocalIdentifier............................................................................................................ 19

3.13 ($3E) TesterPresent ................................................................................................................................... 20 4 Error Handling................................................................................................ 21 5 Contents ......................................................................................................... 22

5.1 Basic Variant ............................................................................................................................................. 22 5.1.1 ECU Configuration............................................................................................................................ 22 5.1.2 ECU Physical Address....................................................................................................................... 22 5.1.3 Sessions ............................................................................................................................................. 22

5.1.3.1 ($10 $81) startDiagnosticSession .......................................................................................................... 22 5.1.4 Identifications .................................................................................................................................... 23

5.1.4.1 ($1A) ReadECUIdentification ............................................................................................................... 23 5.1.5 Error Memory.................................................................................................................................... 24

5.1.5.1 Error Code List ...................................................................................................................................... 24 5.1.5.2 Error Forget Counter ............................................................................................................................. 24 5.1.5.3 Event Code List ..................................................................................................................................... 24 5.1.5.4 $14 $FF $00 clearDiagnosticInformation.............................................................................................. 25

5.1.5.4.1 ($FF) Group of DTC, All........................................................................................................ 25 5.1.5.5 ($FF) FNC_CLEAR_ERROR_MEMORY ........................................................................................... 25 5.1.5.6 readStatusOfDiagnosticTroubleCodes................................................................................................... 26

5.1.5.6.1 ($17 $00) StatusOfDTC.......................................................................................................... 26 5.1.5.6.2 Environmental Conditions Parameter Table ........................................................................... 26

5.1.5.7 readDiagnosticTroubleCodeByStatus.................................................................................................... 28 5.1.5.7.1 ($18 $00) DTCByStatus ......................................................................................................... 28




Diss, UK, 16.02.10 of 59

5.1.6 ($21) ReadDataByLocalIdentifier, Current Data (Snapshots) ........................................................... 29 5.1.6.1 ($21 $30) Diagnostic Service "read measurement data wheel electronic" ............................................ 29 5.1.6.2 ($21 $31) Diagnostic service "read status wheel electronic"................................................................. 31 5.1.6.3 ($21 $32) Diagnostic service "read statistics on receipt of datagrams"................................................. 33 5.1.6.4 ($21 $33) Diagnostic service "read identifier and position of wheel electronic" .................................. 35 5.1.6.5 ($21 $34) Diagnostic service "read event memory" .............................................................................. 37 5.1.6.6 Stored Data ............................................................................................................................................ 38

5.1.6.6.1 ($21 $82) Sincom And Factory............................................................................................... 38 5.1.6.6.2 ($21 $83) Serial Number ........................................................................................................ 38 5.1.6.6.3 ($21 $90) VIN (Vehicle Identification Number) .................................................................... 38

5.1.7 ($27) securityAccess.......................................................................................................................... 39 5.1.8 ($3B) WriteDataByLocalIdentifier, Write Memory Block................................................................ 40

5.1.8.1 ($3B $82) Diagnostic service "SincomAndFactory" ............................................................................. 40 5.1.8.2 ($3B $90) Diagnostic service "VIN (Vehicle Identification Number)"................................................. 41 ($31) StartRoutineByLocalIdentifier ($32) StopRoutineByLocalIdentifier.......................................................... 42 5.1.8.3 ($31 $03) Diagnostic service "execute test of wheel electronic"........................................................... 42 5.1.8.4 ($31 $04) Diagnostic service "learn car wheels" ................................................................................... 44 5.1.8.5 ($31 $06) Diagnostic service "delete event memory" ........................................................................... 45 6 Proposal for EOL Test Cycle......................................................................... 47 7 Index ............................................................................................................... 48

7.1 Protocol Services ....................................................................................................................................... 48

7.2 Service Index, Diagnostic Instance............................................................................................................ 48 8 Manufacturer-specific Data........................................................................... 49

8.1 Use of Byte Parameters as Text Markers................................................................................................... 49 8.1.1 Parameter status wheel electronic position XX ................................................................................. 49 8.1.2 Parameter status electronic control unit............................................................................................. 50 8.1.3 Parameter test result and routine status.............................................................................................. 50 8.1.4 Parameter execute wheel sensor test, requested ................................................................................ 51 8.1.5 Parameter learn car wheels ................................................................................................................ 51

8.2 Use of Text Blocks as Text Markers ......................................................................................................... 52 8.2.1 SystemStatus Component .................................................................................................................. 52 8.2.2 RequestStopRoutine Component....................................................................................................... 52 8.2.3 StopRoutine Component.................................................................................................................... 52

9 Referenced Documents................................................................................. 52 10 List of Event Codes ....................................................................................... 53 11 List of Error Codes ........................................................................................ 56




Diss, UK, 16.02.10 of 59

1 Conventions

The diagnostic contents are described independently of the diagnostic protocol in this document. Counting of the bytes in the "Protocol Services" chapter begins – as in the standardised specifications (KWP 2000 ISO 14230/ISO 15765). In the "Contents" chapter only the transmitted useful data are described whereby a reference to the implemented protocol service is recorded respectively. You will find a list of the implemented protocol services in the "Protocol Services" chapter. In the "Contents" chapter, counting of the useful data bytes starts at zero (0). Within a data byte, the counting of the bits also starts at zero (0) (LSB - least significant bit), although this does not correspond to the order in which the data bits are transported.




Diss, UK, 16.02.10 of 59

2 Overview

2.1 Control Unit

Tyre Pressure Monitoring System (TPMS) 2.2 Variants

Basic variant




Diss, UK, 16.02.10 of 59

3 Protocol Services

3.1 Overview

SID Service Identifier Definition Name

phys func multi

$10 StartDiagnosticSession X $14 ClearDiagnosticInformation X $17 ReadStatusOfDiagnosticTroubleCodes X $18 ReadDiagnosticTroubleCodesByStatus X $1A ReadEcuIdentification X $20 StopDiagnosticSession X $21 ReadDataByLocalIdentifier X $27 SecurityAccess X $31 StartRoutineByLocalIdentifier X $32 StopRoutineByLocalIdentifier X $3B WriteDataByLocalIdentifier X $3E TesterPresent X

phys = physical addressing is supported func = functional addressing is supported multi = a single service prompts several (cyclic) responses The following table lists all Diagnostic Service Identifiers (SID) and Diagnostic Sessions which are supported by this Tyre Pressure Monitoring System application. The letter "X" indicates that a Diagnostic Service Identifier is available within the scope of a specified Diagnostic Session. Consequently, one column represents the available Diagnostic Service Identifier set within the scope of the specified Diagnostic Session. All other diagnostic services are answered in the DefaultMode with the negative response code ($7F $xx $80) “ServiceNotSupportedInActiveDiagnosticMode” SID Service Identifier Definition

Name

Nor

mal

/Def

ault

Ses

sion

S

ubfu

nctio

n: ($

10 $

81)

End

Of L

ine

Veh

icle

M

anuf

actu

rer S

essi

on

Sub

func

tion:

($10

$83

)

Ses

sion

dev

oted

to s

tarti

ng

com

pone

nts

Sub

func

tion:

($10

$89

) 2)

Spe

cific

for F

IAT

S

ubfu

nctio

n: ($

10 $

8A-$

F9)

$10 StartDiagnosticSession X $14 ClearDiagnosticInformation X $17 ReadStatusOfDTC X $18 ReadDTCByStatus X $1A ReadEcuIdentification X $20 StopDiagnosticSession X $21 ReadDataByLocalId X $27 SecurityAcces $31 StartRoutineByLocalIdentifier X $32 StopRoutineByLocalIdentifier X $3B WriteDataByLocalIdentifier X $3E TesterPresent

With this service the control units remain in the appropriate Diagnostic Session. The request is answered by the ECU

X




Diss, UK, 16.02.10 of 59

3.2 ($10) StartDiagnosticSession

STDS (StartDiagnosticSession)

Request:

Byte Name Value #1 SID-RQ $10 #2 DIAGNOSTIC MODE $81

Positive Response:

Byte Name Value #1 SID-PR $50 #2 DIAGNOSTIC MODE $81

Negative Response:

Byte Name Value #1 SID-NR $7F #2 SID-RQ $10 #3 RESPONSE CODE $xx

Negative Response Codes:

Response Code

Error text

0x12 subFunction not supported, invalid format




Diss, UK, 16.02.10 of 59

3.3 ($14) ClearDiagnosticInformation

CDI (ClearDiagnosticInformation)

Request:

Byte Name Value #1 SID-RQ $14 #2 GROUP OF DTC $FF #3 GROUP OF DTC $00

Positive Response:

Byte Name Value #1 SID-PR $54 #2 GROUP OF DTC $FF #3 GROUP OF DTC $00

Negative Response:



Response Code

Error text

0x12 subFunction not supported, invalid format 0x23 Routine not complete




Diss, UK, 16.02.10 of 59

3.4 ($17) ReadStatusOfDiagnosticTroubleCodes

RSODTC (ReadStatusOfDiagnosticTroubleCodes)

Request:

Byte Name Value #1 SID-RQ $17 #2 DTC NUMBER (HIGH BYTE) $xx #3 DTC NUMBER (LOW BYTE) $xx

Positive Response:

Byte Name Value #1 SID-PR $57 #2 NUMBER OF DTC $xx $3 $4 $5 $6 $7 $8 $9 $10 $11 $12

LIST OF DTC, STATUS AND ENVIRONMENT=[ DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC ENVIRONMENTAL CONDITION #1 ENVIRONMENTAL CONDITION #2 ENVIRONMENTAL CONDITION #3 ENVIRONMENTAL CONDITION #4 ENVIRONMENTAL CONDITION #5 ENVIRONMENTAL CONDITION #6 EVENT COUNTER ]

$xx $xx $xx $xx $xx $xx $xx $xx $xx $xx

If no DTCs are stored for the requested DTC number, then the “NUMBER OF DTC” (Byte #2) is set to $00, and no further bytes are sent. If a DTC is stored for the requested DTC number, then the “NUMBER OF DTC” is set to $01, and the data for the DTC follows.

Negative Response:



Response Code

Error text

0x12 subFunction not supported, invalid format To see full information on this service, please go to chapter 5.1.5.6




Diss, UK, 16.02.10 of 59

3.5 ($18) ReadDiagnosticTroubleCodesByStatus

RDTCBS (ReadDiagnosticTroubleCodesByStatus)

Request:

Byte Name Value #1 SID-RQ $18 #2 OPTION: ALL IDENTIFIED $00 #3 GROUP OF DTC $FF #4 GROUP OF DTC $00

Positive Response:

Byte Name Value #1 SID-PR $58 #2 NUMBER OF STORED DTCs $xx #3 : : : : : : #n

LIST OF DTC AND STATUS=[ DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC : DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC ]

$xx $xx $xx : $xx $xx $xx

Negative Response:



Response Code

Error text


To see full information on this service, please go to chapter 5.1.5.6




Diss, UK, 16.02.10 of 59

3.6 ($1A) ReadEcuIdentification

REI (ReadEcuIdentification)

Request:

Byte Name Value #1 SID-RQ $1A #2 IDENTIFICATION OPTION $xx

Positive Response:

Byte Name Value #1 SID-PR $5A #2 IDENTIFICATION OPTION $xx #3 : #n

DATA $xx : $xx

Negative Response:

Byte Name Value #1 SID-NR $7F #2 SID-RQ $1A #3 RESPONSE CODE $xx


Response Code

Error text


To see full information on this service, please go to chapter 5.1.4.1




Diss, UK, 16.02.10 of 59

3.7 ($20) StopDiagnosticSession

(StopDiagnosticSession)

Request:

Byte Name Value #1 SID-RQ $20 #2 DIAGNOSTIC MODE $81

Positive Response:

Byte Name Value #1 SID-PR $60 #2 DIAGNOSTIC MODE $81

Negative Response:





Diss, UK, 16.02.10 of 59

3.8 ($21) ReadDataByLocalIdentifier

RDBLI (ReadDataByLocalIdentifier)

Request:

Byte Name Value #1 SID-RQ $21 #2 LID $xx

Positive Response:

Byte Name Value #1 SID-PR $61 #2 LID $xx #3 : #n

DATA $xx : $xx

Negative Response:



Response Code

Error text

0x12 subFunction not supported, invalid format 0x33 securityAccessDeined To see full information on this service, please go to chapter 5.1.6




Diss, UK, 16.02.10 of 59

3.9 ($27) securityAccess

SA (securityAccess)

Request #1:

Byte Name Value #1 SID-RQ #1 $27 #2 ACCESS MODE $03

Positive Response #1:

Byte Name Value #1 SID-PR #1 $67 #2 ACCESS MODE $03 #3 #4

SEED #1 (HIGH BYTE) (LOW BYTE)

$xx $xx

Negative Response #1:

Byte Name Value #1 SID-NR #1 $7F #2 SID-RQ $27 #3 RESPONSE CODE $xx

Negative Response Codes #1:

Response Code

Error text

0x12 subFunction not supported, invalid format 0x22 Conditions not correct 0x37 Required time delay not expired Request #2:

Byte Name Value #1 SID-RQ #2 $27 #2 ACCESS MODE $04 #3 #4

KEY #1 (HIGH BYTE) (LOW BYTE)

$xx $xx

Positive Response #2:

Byte Name Value #1 SID-PR #2 $67 #2 ACCESS MODE $04 #3 SECURITY ACCESS ALLOWED $34




Diss, UK, 16.02.10 of 59

Negative Response #2:


Negative Response Codes #2:

Response Code

Error text

0x12 subFunction not supported, invalid format 0x22 Conditions not correct, Request sequence error 0x35 Invalidkey

The Tester shall request the ECU to "unlock" itself by sending the service securityAccess request #1. The ECU shall respond by sending a "seed" using the service securityAccess positive response #1. The Tester shall continue by returning a "key" number back to the ECU using the service securityAccess request#2. The ECU shall compare this "key" to one internally stored. If the two numbers match, then the ECU shall enable the Tester’s access to specific KWP2000 services and indicate that with the service securityAccess positive response#2. If upon 2 attempts of a service securityAccess request#2 by the Tester, the two keys do not match, then the ECU shall insert a 10 second time delay before allowing further attempts. No additional time delay is required before the ECU responds to a securityAccess request#1 from the Tester after ECU power-on. If the ECU is already unlocked when a securityAccess request#1 is received, the ECU shall respond with a securityAccess positive response#1 service with a seed of (0). The Tester will use this method to determine if the ECU is locked by checking for a non-zero seed. The security system shall not prevent normal diagnostic or vehicle communications between the Tester and the ECUs. The ECU shall support reject messages if a secure mode is requested while the ECU is locked. The algorithm used to protect the ECU will use two bytes for the input and output variables (Seed & Key).




Diss, UK, 16.02.10 of 59

3.10 ($31) StartRoutineByLocalIdentifier

STRBLI (StartRoutineByLocalIdentifier)

Request:

Byte Name Value #1 SID-RQ $31 #2 LID $xx #3 : #n

DATA $xx : $xx

Positive Response:


DATA $xx : $xx

Negative Response:



Response Code

Error text

0x12 subFunction not supported, invalid format 0x33 securityAccessDeined To see full information on this service, please go to chapter 5.1.8




Diss, UK, 16.02.10 of 59

3.11 ($32) StopRoutineByLocalIdentifier

SRBLI (StopRoutineByLocalIdentifier)

Request:

Byte Name Value #1 SID-RQ $32 #2 LID $xx #3 : #n

DATA $xx : $xx

Positive Response:


DATA $xx : $xx

Negative Response:



Response Code

Error text

To see full information on this service, please go to chapter 5.1.8




Diss, UK, 16.02.10 of 59

3.12 ($3B) WriteDataByLocalIdentifier

WDBLI (WriteDataByLocalIdentifier)

Request:

Byte Name Value #1 SID-RQ $3B #2 LID $xx #3 : #n

DATA $xx

Positive Response:

Byte Name Value #1 SID-PR $7B #2 LID $xx

Negative Response:

Byte Name Value #1 SID-NR $7F #2 SID-RQ $3B #3 RESPONSE CODE $xx


Response Code

Error text

0x33 securityAccessDeined To see full information on this service, please go to chapter 5.1.8




Diss, UK, 16.02.10 of 59

3.13 ($3E) TesterPresent

TP (TesterPresent)

Request:

Byte Name Value #1 SID-RQ $3E

Positive Response:

Byte Name Value #1 SID-PR $7E

Negative Response:

Byte Name Value #1 SID-NR $7F #2 SID-RQ $3E #3 RESPONSE CODE $xx


Response Code

Error text




Diss, UK, 16.02.10 of 59

4 Error Handling

If a request received from the control unit cannot be processed, the control unit responds with one of the following Negative Response Codes (depending on the type of error). Specific Negative Response Codes are described in the individual services.


Response Code Hex Value

Definition of Response Code Description

$11 ServiceNotSupported $12 subFunctionNotSupported-invalidFormat $21 busy-repeatRequest $22 conditionsNotCorrectOrRequestSequenceError $23 routineNotComplete $27 securityAccess $31 requestOutOfRange $33 securityAccessDenied $35 invalidKey $37 requiredTimeDelayNotExpired $80 serviceNotSupportedInActiveDiagnosticMode

Remark: The communication timing is not affected by the response code unless it is specified. Example: StartDiagnosticSession ($81) If a requested DiagnosticMode is not supported, the ECU responds with SubFunctionNotSupported-InvalidFormat ($7F $10 ResponseCode $12)




Diss, UK, 16.02.10 of 59

5 Contents

5.1 Basic Variant

5.1.1 ECU Configuration

Parameter Value Block Size (TPDU.BS) FFh

Separation Time (TPDU.ST) 0ms or as requested from tester CAN Id. of the diagnostic

request message from Tester 7B0h

CAN Id. of the diagnostic response message from ECU

7DCh

Receive buffer size 120 bytes

5.1.2 ECU Physical Address

ECU Address (hex) Diagnostic Tool Address (hex) A2 F1

5.1.3 Sessions

5.1.3.1 ($10 $81) startDiagnosticSession

This Diagnostic Session allows the KWP2000 Services which are used for reading errors, identification and data.

Service Protocol service Start ($10) StartDiagnosticSession, see page 8

Example:

Request:

Byte Name Value #1 SID-RQ $10 #2 DIAGNOSTIC MODE, Default Session $81 #03 BaudrateIdentifier $00

Positive Response:

Byte Name Value #1 SID-PR $50 #2 DIAGNOSTIC MODE, Default Session $81




Diss, UK, 16.02.10 of 59

5.1.4 Identifications

5.1.4.1 ($1A) ReadECUIdentification

Subfunction: IDENTIFICATION OPTION ($80, $91, $92, $94, $97, $99)

Service Protocol service Read ($1A) ReadEcuIdentification, see page 12 Hex Value

Identification Option ECU Identification Data Format

# of Bytes

Data Format

BERU f1systems

80 Identification Code All the following data

61 Supported

91 FIAT drawing number "123456789" 11 ASCII equivalent to Ferrari part number, e.g. "0 0 0 0 0 2 4 4 9 5 2" for ECU

92 ECU Hardware Number Tbd 11 ASCII BERU f1systems Hardware Number “0 1 0 0 1 2 1 4 0 0 1”

93 ECU Hardware Version Tbd 1 UNSGN BERU f1systems Hardware Version “A”

94 ECU Software Number Tbd 11 ASCII BERU f1systems Software Number “0 0 F 1 3 7 2 2 1 9 D”

95 ECU Software Version Tbd 2 UNSGN BERU f1systems Software Version e.g. “05 02” (Value is displayed in hex)

96 Omologation Number Tbd 6 ASCII not supported 97 ISO Code xx xx xx xx xx 5 UNSGN "4F 83 01 07 2F" for part number 244952 for

ECU 98 Tester Code Tbd 10 ASCII not supported 99 Date of

download/production 20 02 03 25 [YY YY MM DD]

4 BCD date of production, since ecu re-programming by tester is not allowed

Example:

Request: Byte Name Value #1 SID-RQ $1A #2 IDENTIFICATION OPTION, ISO Code $97 Positive Response: Byte Name Value #1 SID-PR $5A #2 IDENTIFICATION OPTION, ISO Code $97 #3 DATA $4F #4 DATA $83 #5 DATA $01 #6 DATA $02 #7 DATA $2A




Diss, UK, 16.02.10 of 59

5.1.5 Error Memory

Service Protocol service Read (identified errors - 2Byte Hex) ($18) ReadDiagnosticTroubleCodesByStatus

2Byte Hex - All Identified, see page 11 Read (environment data) ($17) ReadStatusOfDiagnosticTroubleCodes, see

page 10 Delete (all errors) ($14) ClearDiagnosticInformation, see page 9

5.1.5.1 Error Code List The codes of the errors detected by the control unit are stored in the error memory. See tables about error and event codes and their meanings at the end of this document. The decoding of the byte "Status of errors" is described below: Status of errors B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 DTC fault symptom 0=no fault symptom available for this DTC

1=above maximum threshold Bit1 DTC fault symptom 2=below minimum threshold Bit2 DTC fault symptom 4=no signal Bit3 DTC fault symptom 8=invalid signal Bit4 DTC fault symptom 0=test complete for this DTC or not applicable

1=test not complete for this DTC Bit5 DTC storage state 0=error not saved

1=sporadic Bit6 DTC storage state 2=error occurred temporarily

3=permanent Bit7 DTC warning lamp state 0=warning lamp not activated due to error

1=warning lamp activated due to error

5.1.5.2 Error Forget Counter

After an error is no longer active in the system, it is held in memory for a period of 40 Key 15 cycles. After this number of cycles has passed, the error is deleted out of memory.

5.1.5.3 Event Code List

The codes of the events detected by the control unit are stored in the event memory. An event bit is set to “1” when the event occurs. It is only possible to read or delete the whole event memory. See tables about error and event codes and their meanings at the end of this document.




Diss, UK, 16.02.10 of 59

5.1.5.4 $14 $FF $00 clearDiagnosticInformation

5.1.5.4.1 ($FF) Group of DTC, All Same as ($FF) FNC_CLEAR_ERROR_MEMORY

5.1.5.5 ($FF) FNC_CLEAR_ERROR_MEMORY

Same as ($FF) Group of DTC, All Request:

Byte Name Value #1 SID-RQ $14 #2 GROUP OF DTC, All (HIGH BYTE) $FF #3 GROUP OF DTC, All (LOW BYTE) $00

Positive Response:

Byte Name Value #1 SID-PR $54 #2 GROUP OF DTC, All (HIGH BYTE) $FF #3 GROUP OF DTC, All (LOW BYTE) $00




Diss, UK, 16.02.10 of 59

5.1.5.6 readStatusOfDiagnosticTroubleCodes

5.1.5.6.1 ($17 $00) StatusOfDTC Request information on one DTC

Request:

Byte Name Value #1 SID-RQ $17 #2 DTC (HIGH BYTE) $xx #3 DTC (LOW BYTE) $xx

Positive Response:

Byte Name Value #1 SID-PR $57 #2 NUMBER OF DTC $xx $3 $4 $5 $6 $7 $8 $9 $10 $11 $12

LIST OF DTC, STATUS AND ENVIRONMENT=[ DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC ENVIRONMENTAL CONDITION #1 ENVIRONMENTAL CONDITION #2 ENVIRONMENTAL CONDITION #3 ENVIRONMENTAL CONDITION #4 ENVIRONMENTAL CONDITION #5 ENVIRONMENTAL CONDITION #6 EVENT COUNTER ]

$xx $xx $xx $xx $xx $xx $xx $xx $xx $xx

Negative Response:

Byte Name Value #1 SID-NR #1 $7F #2 SID-RQ $17 #3 RESPONSE CODE $xx


Response Code

Error text


5.1.5.6.2 Environmental Conditions Parameter Table

Position Description Conversion 1 ECU Supply Voltage Data / 10 [V] logged only when

DTC corresponding to voltage is set. 0 in other cases.

2 LINV Data / 10 [V] logged only when DTC corresponding to voltage is set. 0 in other cases.




Diss, UK, 16.02.10 of 59

3 ECU Temperature Data – 40[°C] logged only when DTC corresponding to voltage is set. 0 in other cases.

4 Sensor Remaining Battery Life Data [months]. logged only when DTC corresponding to battery life less than 2 months is set. 0 in other cases.

5 Not Used 6 Not Used




Diss, UK, 16.02.10 of 59

5.1.5.7 readDiagnosticTroubleCodeByStatus

5.1.5.7.1 ($18 $00) DTCByStatus RequestAllErrors Request:

Byte Name Value #1 SID-RQ $18 #2 OPTION: Identified 2 Byte Hex DTC and Status $00 #3 GROUP OF DTC $FF #4 Group of DTC $00

Positive Response:

Byte Name Value #1 SID-PR $58 #2 NUMBER OF DTCs #3 : : : #n

LIST OF DTC AND STATUS=[ DTC DTC STATUS : DTC DTC STATUS ]




Diss, UK, 16.02.10 of 59

5.1.6 ($21) ReadDataByLocalIdentifier, Current Data (Snapshots) Local Identifier: LID ($xx)

Service Protocol service Read ($21) ReadDataByLocalIdentifier, see page 14

5.1.6.1 ($21 $30) Diagnostic Service "read measurement data wheel

electronic" Status of modification

02

Prepared / date James Shingleton / 14th June 2007 Revised / date Name ($21 $30) Diagnostic Service "read measurement data wheel electronic" Description This function enables reading of measurement data of the wheel electronics.

Summary of following former services: 1) Diagnostic service “read measurement data wheel electronic” ($21 $01)

Requirement The position of the wheel electronics can only be read when the status of the control unit is “system learned”. Therefore the feedback provided by the learning status in the "Parameter setting electronic control unit" byte is important!

Reference Addressee Production (EOL test), service Default values • Default values / not available / invalid pressure = FFh (N.B.: 00h only

possible with absolute pressure values) • Default values / not available / invalid temperature = FFh • Parameter status electronic control unit = FFh

Request message:

Byte Parameter Description Value #1 Read Data By Local Identifier Request Service ID $21 #2 Record Local Identifier $30

Positive response message:

Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID

$61

#2 Record Local Identifier

$30

#3 Current pressure value, wheel FL (at reference temperature 20°C)

p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar)

$xx

#4 Current pressure value, wheel FL p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel.

$xx

#5 Current temperature value, wheel FL T [°C] = $xx-40 value range (phys.) (-40)...125 deg.

$xx

#6 Current pressure value, wheel FR (at reference temperature 20°C)


$xx




Diss, UK, 16.02.10 of 59

#7 Current pressure value, wheel FR p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel.

$xx

#8 Current temperature value, wheel FR T [°C] = $xx-40 value range (phys.) (-40)...125 deg.

$xx

#9 Current pressure value, wheel RL (at reference temperature 20°C)


$xx

#10 Current pressure value, wheel RL p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel.

$xx

#11 Current temperature value, wheel RL T [°C] = $xx-40 value range (phys.) (-40)...125 deg.

$xx

#12 Current pressure value, wheel RR (at reference temperature 20°C)


$xx

#13 Current pressure value, wheel RR p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel.

$xx

#14 Current temperature value, wheel RR T [°C] = $xx-40 value range (phys.) (-40)...125 deg.

$xx

#15 Parameter status electronic control unit $xx Parameter status electronic control unit B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 learning status 1=system learning Bit1 learning status 1=system checking Bit2 learning status 1=system learned Bit3 assignment status 1=Map 1 is active (Bridgestone tyres fitted) Bit4 assignment status 1=Map 2 is active (Goodyear tyres fitted) Bit5 assignment status 1=Map 3 is active (Michelin tyres fitted) Bit6 assignment status 1=Map 4 is active (Pirelli tyres fitted) Bit7 assignment status 1=Map 5 is active (Pirelli Corsa tyres fitted)




Diss, UK, 16.02.10 of 59

5.1.6.2 ($21 $31) Diagnostic service "read status wheel electronic"

Status of modification

02

Prepared / date James Shingleton / 14th June 2007 Revised / date Name ($21 $31) Diagnostic service "read status wheel electronic" Description This function enables reading the status of the wheel electronics.

Remaining durability of battery: Value range of the register for the remaining battery durability from 0dec to 120dec:


Reference Addressee Default values Default values / not available / invalid Remaining durability of wheel electronic

battery = FFh Default values / not available / invalid Parameter status wheel electronic position XX = FFh

Request message:



Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID $61 #2 Record Local Identifier $31 #3 Remaining durability of wheel electronic battery FL 0 ...120dec

value range (phys.) $xx

#4 Parameter status wheel electronic position XX = FL $xx #5 Remaining durability of wheel electronic battery FR 0 ... 120dec


#6 Parameter status wheel electronic position XX = FR $xx #7 Remaining durability of wheel electronic battery RL 0 ... 120dec


#8 Parameter status wheel electronic position XX = RL $xx #9 Remaining durability of wheel electronic battery RR 0 ... 120dec


#10 Parameter status wheel electronic position XX = RR $xx #11 Parameter status electronic control unit $xx




Diss, UK, 16.02.10 of 59

Parameter status wheel electronic position XX B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 sending mode position XX 0=storage mode

1=normal Bit1 sending mode position XX 2=rapid (in case of puncture)

3=rapid (in case of excessive temperature) Bit2 hardware error position XX if X=1 Bit3 measurement error position XX if X=1 Bit4 autotransmit bit set position XX if X=1 Bit5 roll switch bit set position XX if X=1 Bit6 tx on LF request bit set position XX if X=1 Bit7 power management indicator bit set position XX if X=1 Parameter status electronic control unit B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 learning status 1=system learning Bit1 learning status 1=system checking Bit2 learning status 1=system learned Bit3 assignment status 1=Map 1 is active (Bridgestone tyres fitted) Bit4 assignment status 1=Map 2 is active (Goodyear tyres fitted) Bit5 assignment status 1=Map 3 is active (Michelin tyres fitted) Bit6 assignment status 1=Map 4 is active (Pirelli tyres fitted) Bit7 assignment status 1=Map 5 is active (Pirelli Corsa tyres fitted)




Diss, UK, 16.02.10 of 59

5.1.6.3 ($21 $32) Diagnostic service "read statistics on receipt of datagrams" Status of modification

02

Prepared / date James Shingleton / 14th June 2007 Revised / date Name ($21 $32) Diagnostic service "read statistics on receipt of datagrams" Description This function enables reading of the statistics data on receipt of datagrams. Requirement The position of the wheel electronics can only be read when the status of the

control unit is “system learned”. Therefore the feedback provided by the learning status in the "Parameter setting electronic control unit" byte is important!

Reference Addressee Defaultvalues Default value / not available / invalid counter of datagrams received from wheel

electronic = 00h Parameter status electronic control unit = FFh

Request message:



Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID $61 #2 Record Local Identifier $32 #3 counter of datagrams received from wheel electronic FL (high byte) $xx #4 counter of datagrams received from wheel electronic FL (low byte) $xx #5 counter of datagrams received from wheel electronic FR (high byte) $xx #6 counter of datagrams received from wheel electronic FR (low byte) $xx #7 counter of datagrams received from wheel electronic RL (high byte) $xx #8 counter of datagrams received from wheel electronic RL (low byte) $xx #9 counter of datagrams received from wheel electronic RR (high byte) $xx #10 counter of datagrams received from wheel electronic RR (low byte) $xx #11 Parameter status electronic control unit $xx




Diss, UK, 16.02.10 of 59

Parameter status electronic control unit B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 learning status 1=system learning Bit1 learning status 1=system checking Bit2 learning status 1=system learned Bit3 assignment status 1=Map 1 is active (Bridgestone tyres fitted) Bit4 assignment status 1=Map 2 is active (Goodyear tyres fitted) Bit5 assignment status 1=Map 3 is active (Michelin tyres fitted) Bit6 assignment status 1=Map 4 is active (Pirelli tyres fitted) Bit7 assignment status 1=Map 5 is active (Pirelli Corsa tyres fitted)




Diss, UK, 16.02.10 of 59

5.1.6.4 ($21 $33) Diagnostic service "read identifier and position of wheel

electronic" Status of modification

02

Prepared / date James Shingleton / 14th June 2007 Revised / date Name ($21 $33) Diagnostic service "read identifier and position of wheel electronic" Description This function enables reading of the identifiers and positions of the wheel

electronics. Conversion of decimal wheel electronic identification number to hexadecimal byte: Step 1) convert decimal number to hexadecimal number Step 2) fill up four bytes reserved for the identifier of wheel electronic with hexadecimal number: start with the least significant position of the hexadecimal number filled in the lower nibble of the low byte of the identifier and so on. Conversion of hexadecimal byte to decimal wheel electronic identification number: Step 1) put together four bytes reserved for the identifier of wheel electronic to form the hexadecimal number: start with the highest nibble of the high byte filled in the most significant position of the hexadecimal number (omit leading zero) Step 2) convert hexadecimal number to decimal number.

Requirement Reference Addressee Default values Default values / not available = 00h

invalid Parameter position wheel electronic = FFh Request message:



Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID $61 #2 Record Local Identifier $33 #3 Identifier of wheel electronic FL (high byte) $xx #4 Identifier of wheel electronic FL $xx #5 Identifier of wheel electronic FL $xx #6 Identifier of wheel electronic FL (low byte) $xx #7 Identifier of wheel electronic FR (high byte) $xx #8 Identifier of wheel electronic FR $xx #9 Identifier of wheel electronic FR $xx #10 Identifier of wheel electronic FR (low byte) $xx #11 Identifier of wheel electronic RL (high byte) $xx #12 Identifier of wheel electronic RL $xx #13 Identifier of wheel electronic RL $xx #14 Identifier of wheel electronic RL (low byte) $xx #15 Identifier of wheel electronic RR (high byte) $xx #16 Identifier of wheel electronic RR $xx #17 Identifier of wheel electronic RR $xx #18 Identifier of wheel electronic RR (low byte) $xx #19 Parameter status electronic control unit $xx




Diss, UK, 16.02.10 of 59

Parameter status electronic control unit B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 learning status 1=system learning Bit1 learning status 1=system checking Bit2 learning status 1=system learned Bit3 assignment status 1=Map 1 is active (Bridgestone tyres fitted) Bit4 assignment status 1=Map 2 is active (Goodyear tyres fitted) Bit5 assignment status 1=Map 3 is active (Michelin tyres fitted) Bit6 assignment status 1=Map 4 is active (Pirelli tyres fitted) Bit7 assignment status 1=Map 5 is active (Pirelli Corsa tyres fitted) Example 1) 1001382118 dec = 3BAFE0E6 hex

#3 Identifier of wheel electronic FL (high byte) $3B #4 Identifier of wheel electronic FL $AF #5 Identifier of wheel electronic FL $E0 #6 Identifier of wheel electronic FL (low byte) $E6

Example 2) 1500035925 dec = 5968BB55 hex

#7 Identifier of wheel electronic FR (high byte) $59 #8 Identifier of wheel electronic FR $68 #9 Identifier of wheel electronic FR $BB #10 Identifier of wheel electronic FR (low byte) $55

Example 3) 1001375227 dec = 3BAFC5FB hex

#11 Identifier of wheel electronic RL (high byte) $3B #12 Identifier of wheel electronic RL $AF #13 Identifier of wheel electronic RL $C5 #14 Identifier of wheel electronic RL (low byte) $FB

Example 4) 1001365532 dec = 3BAFA01C hex

#15 Identifier of wheel electronic RR (high byte) $3B #16 Identifier of wheel electronic RR $AF #17 Identifier of wheel electronic RR $A0 #18 Identifier of wheel electronic RR (low byte) $1C




Diss, UK, 16.02.10 of 59

5.1.6.5 ($21 $34) Diagnostic service "read event memory" Status of modification

02

Prepared / date James Shingleton / 14th June 2007 Revised / date Name ($21 $34) Diagnostic service "read event memory" Description This function enables reading of the entries in the event memory. Requirement Reference The error and event codes and their meanings can be taken from the tables at

the end of this document. Addressee Default values

Request message format:



Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID $61 #2 Record Local Identifier $34 #3 Event code Byte 0 $xx #4 Event code Byte 1 $xx #5 Event code Byte 2 $xx #6 Event code Byte 3 $xx




Diss, UK, 16.02.10 of 59

5.1.6.6 Stored Data

5.1.6.6.1 ($21 $82) Sincom And Factory Local Identifier: LID ($82)

Read Positive Response:

Byte Bit Name Conversion Comments 0 – 5 SincomAndFactory ASCII Written by tester

5.1.6.6.2 ($21 $83) Serial Number

Local Identifier: LID ($83)


Byte Bit Name Conversion Comments 2 bytes Serial number UNSGN Defined by BERU f1systems

5.1.6.6.3 ($21 $90) VIN (Vehicle Identification Number) Local Identifier: LID ($90)


Byte Bit Name Conversion Comments 0 – 16 VIN ASCII Written by tester




Diss, UK, 16.02.10 of 59

5.1.7 ($27) securityAccess The following table lists the services which are protected by securityAccess, and the conditions for request of securityAccess.

diagnosticService ($21) readDataByLocalIdentifier ($3B) writeDataByLocalIdentifier ($31) startRoutineByLocalIdentifier




Diss, UK, 16.02.10 of 59

5.1.8 ($3B) WriteDataByLocalIdentifier, Write Memory Block Service Protocol service Write ($3B) WriteDataByLocalIdentifier

5.1.8.1 ($3B $82) Diagnostic service "SincomAndFactory" Status of modification

01

Prepared / date James Shingleton / 08th June 2007 Revised / date Name ($3B $82) Diagnostic service "SincomAndFactory" Description This function enables the Sincom, Plant and Location code to be written into the

ECU. Requirement Reference Addressee Default values

Request message:

Byte Parameter Description Value #1 Write Data By Local Identifier Request Service ID $3B #2 Record Local Identifier $82 #3 Sincom (Byte 1) $xx #4 Sincom (Byte 2) $xx #5 Sincom (Byte 3) $xx #6 Factory (Byte 1) $xx #7 Factory (Byte 2) $xx #8 Series (Byte 1) $xx


Byte Parameter Description Value #1 Write Data By Local Identifier Positive Response ID $7B #2 Record Local Identifier $82

Negative Response: Byte Name Value

#1 SID-NR $7F #2 SID-RQ $3B #3 RESPONSE CODE $xx

Negative Response Codes: Value Definition of Response Code Description

$12 subFunction not supported, invalid format

in case the format of the message sent to the ECU is not correct

$33 securityAccessDeined in case the ECU has not been unlocked using the “security access” procedure.




Diss, UK, 16.02.10 of 59

5.1.8.2 ($3B $90) Diagnostic service "VIN (Vehicle Identification Number)" Status of modification

01

Prepared / date James Shingleton / 08th June 2007 Revised / date Name ($3B $90) Diagnostic service "VIN (Vehicle Identification Number)" Description This function enables VIN to be written into the ECU. Requirement Reference Addressee Default values

Request message:

Byte Parameter Description Value #1 Write Data By Local Identifier Request Service ID $3B #2 Record Local Identifier $90 #3 V.M.I. (Byte 1) $xx #4 V.M.I. (Byte 2) $xx #5 V.M.I. (Byte 3) $xx #6 V.D.S. (Byte 1) $xx #7 V.D.S. (Byte 2) $xx #8 V.D.S. (Byte 3) $xx #9 V.D.S. (Byte 4) $xx #10 V.D.S. (Byte 5) $xx #11 V.D.S. (Byte 6) $xx #12 V.I.S. (Byte 1) $xx #13 V.I.S. (Byte 2) $xx #14 V.I.S. (Byte 3) $xx #15 V.I.S. (Byte 4) $xx #16 V.I.S. (Byte 5) $xx #17 V.I.S. (Byte 6) $xx #18 V.I.S. (Byte 7) $xx #19 V.I.S. (Byte 8) $xx


Byte Parameter Description Value #1 Write Data By Local Identifier Positive Response ID $7B #2 Record Local Identifier $90


#1 SID-NR $7F #2 SID-RQ $3B #3 RESPONSE CODE $xx


$12 subFunction not supported, invalid format

in case the format of the message sent to the ECU is not correct





Diss, UK, 16.02.10 of 59

($31) StartRoutineByLocalIdentifier

($32) StopRoutineByLocalIdentifier Service Protocol Service Start ($31) StartRoutineByLocalIdentifier Stop ($32) StopRoutineByLocalIdentifier

5.1.8.3 ($31 $03) Diagnostic service "execute test of wheel electronic" Status of modification

01

Prepared / date James Shingleton / 17th May 2007 Revised / date Name ($31 $03) Diagnostic service "execute test of wheel electronic" Description This function allows the testing for the presence of all wheel electronics fitted on

the vehicle by the ECU. For this to be executed, the control unit must be in the “system learned” status. Execution of the routine is ended by the KWP2000 Service StopRoutineByLocalIdentifier.


Reference ($21 $33) Diagnostic service "read identifier and position of wheel electronic" Addressee Production (EOL test) Default values: •

Request message:

Byte Parameter Description Value #1 Start Routine By Local Identifier Request Service ID $31 #2 Routine Local Identifier $03 #3 Parameter execute wheel sensor test, requested $xx




Diss, UK, 16.02.10 of 59

Parameter execute wheel sensor test, requested B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0

0dec = Autoping FL 1dec = Autoping FR 2dec = Autoping RL 3dec = Autoping RR 4dec = Autoping ALL 5dec -> 255dec = reserved


Byte Parameter Description Value #1 Start Routine By Local Identifier Positive Response Service ID $71 #2 Routine Local Identifier $03

Execution of the routine is ended using the following request block of the Diagnostic Tester: Request message:

Byte Parameter Description Value #1 Stop Routine By Local Identifier Request Service ID $32 #2 Routine Local Identifier $03


Byte Parameter Description Value #1 Stop Routine By Local Identifier Positive Response Service ID $72 #2 Routine Local Identifier $03


#1 SID-NR $7F #2 SID-RQ $31 #3 RESPONSE CODE $xx


$12 subFunctionNotSupported-invalidFormat

in case value in Parameter execute wheel sensor test, requested value > 5

$22 conditionsNotCorrectOrRequestSequenceError

in case routine shall be stopped using StopRoutineByLocalIdentifier, but either no or any other is running at that time

$22 in case the status of the ECU is not “system learned”





Diss, UK, 16.02.10 of 59

5.1.8.4 ($31 $04) Diagnostic service "learn car wheels"

Status of modification

01

Prepared / date James Shingleton / 17th May 2007 Revised / date Name ($31 $04) Diagnostic service "learn car wheels" Description • This routine enables the control unit to re-learn the wheels fitted to the car.

This can be used if the set of wheels on the car have not been learnt correctly Execution of the routine is ended by the KWP2000 Service StopRoutineByLocalIdentifier.

Requirement Reference: ($21 $31) Diagnostic service "read status wheel electronic" Addressee Production (EOL test), service Default values

Request message:

Byte Parameter Description Value #1 Read Data By Local Identifier Request Service ID $31 #2 Record Local Identifier $04 #3 Parameter learn car wheels $80


Byte Parameter Description Value #1 Read Data By Local Identifier Positive Response Service ID $71 #2 Record Local Identifier $04

Execution of the routine is ended using the following request block of the Diagnostic Tester: Request message:









$33 SecurityAccessDeined in case the ECU has not been unlocked using the “security access” procedure.

$12 subFunctionNotSupported-invalidFormat

in case bits 0-6 in Parameter learn car wheels are not = 0




Diss, UK, 16.02.10 of 59

5.1.8.5 ($31 $06) Diagnostic service "delete event memory" Status of modification

01

Prepared / date James Shingleton/ 24th May 2007 Revised / date Name ($31 $06) Diagnostic service "delete event memory" Description This function allows the event memory to be deleted in connection with a code

byte. Requirement • The event memory must be read before it can be deleted. Otherwise the

request is rejected. • If a wrong code byte is specified in the request block, the event memory is

not deleted and the code byte in the response block is $FF. Reference Addressee Default values

Request message:

Byte Parameter Description Value #1 Start Routine By Local Identifier Request Service ID $31 #2 Routine Local Identifier $06 #3 Code Byte $99


Byte Parameter Description Value #1 Start Routine By Local Identifier Positive Response Service ID $71 #2 Routine Local Identifier $06

Before the event memory can be deleted, it must be read. Otherwise the request is rejected: Everytime ECU is powered up Event memory should be read by service($21 $34) once irrespective of when event memory is buffered. Otherwise delete event memory request is rejected. Execution of the routine is ended using the following request block of the Diagnostic Tester: Request message:












Diss, UK, 16.02.10 of 59





Diss, UK, 16.02.10 of 59

6 Proposal for EOL Test Cycle

Step Description Test

successful Status BERU

1 Vehicle identification

2 ($10$81$00) Init communication 3 ($1A$80) Read ECU identification 4 ($14$FF$00) Cancel DTC (key off then key on) 5 ($10$81$00) Init communication 6 ($21$33) Read wheel sensor IDs 7 ($21$34) Read all Event Code bytes 8 ($21$30) Read pressures for all wheels 9 ($18$02$FF$00) Read and verify DTC 10 Printout results




Diss, UK, 16.02.10 of 59

7 Index

7.1 Protocol Services

SID Service Identifier Definition

Name See page

$10 StartDiagnosticSession 8 $14 ClearDiagnosticInformation 9 $17 ReadStatusOfDiagnosticTroubleCodes 10 $18 ReadDiagnosticTroubleCodesByStatus - All Identified 11 $1A ReadEcuIdentification 12 $21 ReadDataByLocalIdentifier 14 $27 SecurityAccess 15 $31 StartRoutineByLocalIdentifier 17 $32 StopRoutineByLocalIdentifier 18 $3B WriteDataByLocalIdentifier 19 $3E TesterPresent 20

7.2 Service Index, Diagnostic Instance

($21 $30) Diagnostic Service "read measurement data wheel electronic" ($21 $31) Diagnostic service "read status wheel electronic" ($21 $32) Diagnostic service "read statistics on receipt of datagrams" ($21 $33) Diagnostic service "read identifier and position of wheel electronic" ($21 $34) Diagnostic service "read event memory" ($21 $82) Sincom And Factory ($21 $83) Serial Number ($21 $90) VIN (Vehicle Identification Number) ($31 $03) Diagnostic service "execute test of wheel electronic" ($31 $04) Diagnostic service "learn car wheels" ($31 $06) Diagnostic service "delete event memory" ($3B $82) Diagnostic service "SincomAndFactory" ($3B $90) Diagnostic service "VIN (Vehicle Identification Number)"




Diss, UK, 16.02.10 of 59

8 Manufacturer-specific Data

8.1 Use of Byte Parameters as Text Markers

Parameter name Description Default values Parameter status wheel electronic position XX

Parameter status electronic control unit

Parameter test result and routine status

Parameter execute wheel sensor test, requested

Parameter set ECU mode Parameter position wheel electronic

Parameter number and position of wheel electronic

Parameter learn car wheels

8.1.1 Parameter status wheel electronic position XX Parameter status wheel electronic position XX B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 sending mode position XX 0=storage mode

1=normal Bit1 sending mode position XX 2=rapid (in case of puncture)

3=rapid (in case of excessive temperature) Bit2 hardware error position XX if X=1 Bit3 measurement error position XX if X=1 Bit4 autotransmit bit set position XX if X=1 Bit5 roll switch bit set position XX if X=1 Bit6 tx on LF request bit set position XX if X=1 Bit7 power management indicator bit set position XX if X=1




Diss, UK, 16.02.10 of 59

8.1.2 Parameter status electronic control unit Parameter status electronic control unit B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 learning status 1=system learning Bit1 learning status 1=system checking Bit2 learning status 1=system learned Bit3 assignment status 1=Map 1 is active (Bridgestone tyres fitted) Bit4 assignment status 1=Map 2 is active (Goodyear tyres fitted) Bit5 assignment status 1=Map 3 is active (Michelin tyres fitted) Bit6 assignment status 1=Map 4 is active (Pirelli tyres fitted) Bit7 assignment status 1=Map 5 is active (Pirelli Corsa tyres fitted)

8.1.3 Parameter test result and routine status Parameter test result and routine status B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 reserved Bit1 reserved Bit2 reserved Bit3 reserved Bit4 reserved Bit5 reserved Bit6 routine status 0=not started or finalised before end of execution or interrupted

1=not o.k. finalised Bit7 routine status 2=running

3=o.k. finalised If the status is "not started or finalised before end of execution or interrupted" a valid result is not available and the routine has to be restarted.




Diss, UK, 16.02.10 of 59

8.1.4 Parameter execute wheel sensor test, requested Parameter execute wheel sensor test, requested B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0

0dec = Autoping FL 1dec = Autoping FR 2dec = Autoping RL 3dec = Autoping RR 4dec = Autoping ALL 5dec -> 255dec = reserved

8.1.5 Parameter learn car wheels Parameter learn car wheels B 7 B 6 B 5 B 4 B 3 B 2 B 1 B 0 Bit0 reserved Bit1 reserved Bit2 reserved Bit3 reserved Bit4 reserved Bit5 reserved Bit6 reserved Bit7 learn wheels fitted to car if X=1




Diss, UK, 16.02.10 of 59

8.2 Use of Text Blocks as Text Markers

8.2.1 SystemStatus Component The position of the wheel electronics can only be read when the status of the control unit is “system learned”. Therefore the feedback provided by the learning status in the "Parameter setting electronic control unit" byte is important!

8.2.2 RequestStopRoutine Component Execution of the routine is ended using the following request block of the Diagnostic Tester:

8.2.3 StopRoutine Component Execution of the routine is ended by the KWP2000 Service StopRoutineByLocalIdentifier.

9 Referenced Documents

Filename Description Version Author Date Status

F1-407-1355-002 -M145 TPMS Diagnostics Specification V1_02.doc


Diss, UK, 16.02.10 of 59

10 List of Event Codes

Ferr

ari e

vent

byt

e

Ferr

ari e

vent

bit

BERU

f1sy

stem

s Er

ror

Code

Eve

nt D

escr

iptio

n

Eve

nt C

ause

Tim

e of

det

ectio

n

Res

et C

ondi

tion

Pri

ority

Eve

nt C

onse

quen

ce

ECU category: wheel FL

1 0 225 Puncture, hard warning, dynamic A rapid pressure loss from the tyre is detected by the system

Ploss > 350mbar/min Immediately Key 15 cycle: Transition from key 15 OFF to key 15 ON

1 No internal fault consequence

1 1 114 Minimum pressure value, hard warning, static The tyre pressure has dropped below the hard warning tyre pressure limit.

Ptyre < Pcold - 500mbar Immediately Ptyre > Pcold 2 No internal fault consequence

1 2 110 Threshold for warning, soft warning, static The tyre pressure has dropped below the soft warning tyre pressure limit.


1 3 118 Threshold for over pressure warning The tyre pressure has exceeded the over pressure warning limit

Ptyre > 3.5bar Immediately Ptyre < 3.5bar 4 No internal fault consequence

1 4 238 Excessive sensor temperature The sensor temperature has exceeded 120°C and shut down temporarily.

Ttyre > 120°C Immediately Ttyre < 100°C 5 Tyre pressure of the affected tyre cannot be monitored

1 5

1 6

1 7

ECU category: wheel FR












2 5

2 6

2 7

ECU category: wheel RL



Diss, UK, 16.02.10 of 59












3 5

3 6

3 7

ECU category: wheel RR












4 5

4 6

4 7



Diss, UK, 16.02.10 of 59

Abbreviations: Ploss = Pressure loss from the tyre Pcold = Recommended cold inflation pressure for the tyre Ptyre = Pressure in the tyre Ttyre = Temperature of tyre N.B. The value displayed in the Ferrari event byte is a logical sum of events: e.g. If on the FL there was a Rapid Pressure Loss, the value ‘0x01’ would be displayed in byte 1. If on the FL there was a Rapid pressure Loss and a Hard Warnings, the value ‘0x03’ would be displayed in byte 1. If on the FL there was an Over Pressure Warning, the value ‘0x08’ would be displayed in byte 1. If on the FL there was an Over Pressure Warnings and an Over Temperature Warning, the value ‘0x18’ would be displayed in byte 1.



Diss, UK, 16.02.10 of 59

11 List of Error Codes

DTC

Code

DTC

Faul

t Sym

ptom

(b

in)

BERU

f1sy

stem

s Er

ror

Code

E

rror

Cau

se

Eve

nt C

ause

Tim

e of

det

ectio

n

Res

et C

ondi

tion

Sta

tus

Pri

ority

Err

or

Con

sequ

ence

En

viro

nmen

tal

Con

ditio

ns L

ogg

ed

Subassembly: ECU

Control unit category: hardware

ECU Failure 204 Internal Undervoltage Measuring undervoltage in the ECU regulated voltage supply circuitry

VDD < 4.5V Immediately VDD > 4.5V

205 Internal Overvoltage Measuring excess voltage in the ECU regulated voltage supply circuitry

VDD > 5.2V Immediately VDD < 5.2V

210 Internal Excess Temperature Measuring excess temperature in the ECU circuitry

ECUTemp > 85°C Immediately ECUTemp < 85°C

208 LINV Undervoltage Measuring undervoltage in the LINV supply circuitry

LINV < 8.5V Immediately LINV > 8.5V Degraded monitoring performance

5001h 0000

209 LINV Excess voltage Measuring excess voltage in the LINV supply circuitry

LINV > 13V Immediately LINV < 13V Degraded monitoring performance

[1] ECU Supply Voltage [2] LINV [3] ECU Temperature

Control unit category: vehicle

0010 202 Voltage low key 30, undervoltage Measuring undervoltage in the vehicle electrical system on the protected side

Vbatt < 9V Immediately Vbatt > 9V Degraded monitoring performance

5002h

0001 203 Voltage high key 30, excess voltage Measuring excess voltage in the vehicle electrical system on the protected side

Vbatt > 18V Immediately Vbatt < 18V


Control unit category: CAN

0100 212 CAN bus no data Data required by TPMS missing from CAN messages

Reception timeout of any CAN message

Immediately Correct reception of CAN messages

System operates in stationary mode

5003h

1000 213 CAN bus bad data Data required by TPMS is invalid in the CAN messages

Invalid data in one or more CAN messages

Immediately Correct reception of CAN messages

System operates in stationary mode


Subassembly: wheel sensor

Wheel sensor category: wheel sensor FL

5010h 0000 142 Remaining battery lifetime low The remaining battery lifetime is less than 2 months.

Remaining-Battery-Lifetime register < 2 months

Immediately Remaining-Battery-Lifetime register > 2 months

Total failure of wheel sensor in approximately 2 months due to battery expiring

[4] Sensor Remaining Battery Life



Diss, UK, 16.02.10 of 59

5011h 0000 150 Sensor fault Internal measurement error

Measurement error bit in datagram set to 1

Immediately Measurement error bit in datagram set to 0

Pressure sensor defective. No correct pressure data supplied by wheel electronics

None

5012h 0000 154 Sensor fault Internal sensor hardware error

Internal sensor error bit in datagram set to 1

Immediately Internal sensor error bit in datagram set to 0


None

5013h 0000 146 Radio datagram not received No datagrams are received from the appropriate wheel sensor.

No datagrams received for 160 secs

160 secs Datagram receeived

No pressure monitoring for the wheel with the defective wheel electronics

None

Wheel sensor category: wheel sensor FR

5020h 0000 Remaining battery lifetime low The remaining battery lifetime is less than 2 months.





5021h 0000 Sensor fault Internal measurement error




None

5022h 0000 Sensor fault Internal sensor hardware error




None

5023h 0000 Radio datagram not received No datagrams are received from the appropriate wheel sensor.




None

Wheel sensor category: wheel sensor RL










None





None





None

Wheel sensor category: wheel sensor RR








Diss, UK, 16.02.10 of 59





None





None





None

Subassembly: digital receiving antenna

Digital receiving antenna category: LIN interface front antenna

5050h 0000 164 Antenna Fault No communication with antenna

No communication with antenna

5 secs Antenna re-conneted

No pressure monitoring for wheels which have datagrams received by this antenna


5051h 0000 172 Antenna Fault Wrong frequency antenna, or trigger connected

Wrong frequency antenna connected, or trigger connected instead

5 secs Correct frequency antenna connected


5052h 0000 168 Antenna Fault LIN bus fault

Incorrect reception of LIN data signals from antenna

5 secs Correct reception of LIN data signals from antenna



Digital receiving antenna category: LIN interface rear antenna

5060h 0000 164 Antenna Fault No communication with antenna

No communication with antenna

5 secs Antenna re-conneted



5061h 0000 172 Antenna Fault Wrong frequency antenna, or trigger connected

Wrong frequency antenna connected, or trigger connected instead

5 secs Correct frequency antenna connected


5062h 0000 168 Antenna Fault LIN bus fault

Incorrect reception of LIN data signals from antenna

5 secs Correct reception of LIN data signals from antenna



Subassembly: LF satellite trigger

LF satellite trigger category: LIN interface front left trigger

5070h 0000 176 Trigger Fault No communication with trigger

No communication with trigger

5 secs Trigger re-conneted



5071h 0000 184 Trigger Fault Wrong componentconnected

Antenna connected 5 secs Connect trigger


5072h 0000 180 Trigger Fault LIN bus fault

Incorrect reception of LIN data signals from trigger

5 secs Correct reception of LIN data signals from trigger



LF satellite trigger category: LIN interface front right trigger



Diss, UK, 16.02.10 of 59














LF satellite trigger category: LIN interface rear left trigger














LF satellite trigger category: LIN interface rear right trigger

50A0h 0000 176 Trigger Fault No communication with trigger





50A1h 0000 184 Trigger Fault Wrong componentconnected



50A2h 0000 180 Trigger Fault LIN bus fault





F1-407-1355-002 -M145 TPMS Diagnostics Specification V1_02

Documents

Transcript of F1-407-1355-002 -M145 TPMS Diagnostics Specification V1_02