F1-407-1355-002 - M145 TPMS Diagnostics Specification V1 - 02

Diagnostics Specification
M145 TPMS
Maserati
Author: James Shingleton Last modified by: Sathyan Jeyahar Version 1.02 of 11/02/2010
F1-407-1355-002 -M145 TPMS Diagnostics Specification V1_02.doc
BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 1 of 59
Authors: Name Company, Dept. Contact James Shingleton BERU f1systems, R&D Tel.: +44 1379 646216 Fax: +44 1379 646900 E-Mail: james.shingleton@bf1systems.com Sathyan Jeyahar BERU f1systems, R&D Tel.: +44 1379 646200 Fax: +44 1379 646900 E-Mail: sathyan.jeyahar@bf1systems.com Revisions list: Version Author Date Status 1.01 JRS 11/02/2010 First draft 1.02 SJ 11/02/10 Second draft Reason
Document created
Routine control behaviour updated, Writing of Active pressure map removed, ReadStatusofDTC behaviour updated
Table of Contents 1 2
2.1 2.2
Conventions ..................................................................................................... 5 Overview ........................................................................................................... 6

Control Unit................................................................................................................................................. 6 Variants ....................................................................................................................................................... 6
3
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13
Protocol Services............................................................................................. 7
Overview ..................................................................................................................................................... 7 ($10) StartDiagnosticSession ...................................................................................................................... 8 ($14) ClearDiagnosticInformation............................................................................................................... 9 ($17) ReadStatusOfDiagnosticTroubleCodes............................................................................................ 10 ($18) ReadDiagnosticTroubleCodesByStatus ........................................................................................... 11 ($1A) ReadEcuIdentification..................................................................................................................... 12 ($20) StopDiagnosticSession..................................................................................................................... 13 ($21) ReadDataByLocalIdentifier ............................................................................................................. 14 ($27) securityAccess ................................................................................................................................. 15 ($31) StartRoutineByLocalIdentifier......................................................................................................... 17 ($32) StopRoutineByLocalIdentifier ......................................................................................................... 18 ($3B) WriteDataByLocalIdentifier............................................................................................................ 19 ($3E) TesterPresent ................................................................................................................................... 20
4 5
Error Handling................................................................................................ 21 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
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 7
7.1 7.2
Proposal for EOL Test Cycle......................................................................... 47 Index ............................................................................................................... 48

Protocol Services ....................................................................................................................................... 48 Service Index, Diagnostic Instance............................................................................................................ 48
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 10 11
Referenced Documents ................................................................................. 52 List of Event Codes ....................................................................................... 53 List of Error Codes ........................................................................................ 56
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.
Overview
2.1 Control Unit

Tyre Pressure Monitoring System (TPMS)
2.2 Variants
Basic variant
Protocol Services
3.1 Overview
SID $10 $14 $17 $18 $1A $20 $21 $27 $31 $32 $3B $3E
phys func multi
Service Identifier Definition Name StartDiagnosticSession ClearDiagnosticInformation ReadStatusOfDiagnosticTroubleCodes ReadDiagnosticTroubleCodesByStatus ReadEcuIdentification StopDiagnosticSession ReadDataByLocalIdentifier SecurityAccess StartRoutineByLocalIdentifier StopRoutineByLocalIdentifier WriteDataByLocalIdentifier TesterPresent
= = = physical addressing is supported functional addressing is supported a single service prompts several (cyclic) responses
phys X X X X X X X X X X X X
func
multi
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
Specific for FIAT Subfunction: ($10 $8A-$F9) BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 7 of 59 Session devoted to starting components Subfunction: ($10 $89) 2) SID Service Identifier Definition Name
Normal/Default Session Subfunction: ($10 $81)
$10 $14 $17 $18 $1A $20 $21 $27 $31 $32 $3B $3E
StartDiagnosticSession ClearDiagnosticInformation ReadStatusOfDTC ReadDTCByStatus ReadEcuIdentification StopDiagnosticSession ReadDataByLocalId SecurityAcces StartRoutineByLocalIdentifier StopRoutineByLocalIdentifier WriteDataByLocalIdentifier TesterPresent With this service the control units remain in the appropriate Diagnostic Session. The request is answered by the ECU
X X X X X X X X X X X
End Of Line Vehicle Manufacturer Session Subfunction: ($10 $83)
3.2 ($10) StartDiagnosticSession

STDS (StartDiagnosticSession) Request: Byte #1 #2 Name SID-RQ DIAGNOSTIC MODE Value $10 $81
Positive Response: Byte #1 #2 Name SID-PR DIAGNOSTIC MODE Value $50 $81
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Value $7F $10 $xx
Negative Response Codes: Response Code 0x12
3.3 ($14) ClearDiagnosticInformation

CDI (ClearDiagnosticInformation) Request: Byte #1 #2 #3 Name SID-RQ GROUP OF DTC GROUP OF DTC Value $14 $FF $00
Positive Response: Byte #1 #2 #3 Name SID-PR GROUP OF DTC GROUP OF DTC Value $54 $FF $00
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Routine not complete Value $7F $14 $xx
Negative Response Codes: Response Code 0x12 0x23
3.4 ($17) ReadStatusOfDiagnosticTroubleCodes

RSODTC (ReadStatusOfDiagnosticTroubleCodes) Request: Byte #1 #2 #3 Name SID-RQ DTC NUMBER (HIGH BYTE) DTC NUMBER (LOW BYTE) Value $17 $xx $xx
Positive Response: Byte #1 #2 $3 $4 $5 $6 $7 $8 $9 $10 $11 $12 Name SID-PR NUMBER OF DTC 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 ] Value $57 $xx $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: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Value $7F $17 $xx
Negative Response Codes: Response Code 0x12 Error text subFunction not supported, invalid format
To see full information on this service, please go to chapter 5.1.5.6
3.5 ($18) ReadDiagnosticTroubleCodesByStatus

RDTCBS (ReadDiagnosticTroubleCodesByStatus) Request: Byte #1 #2 #3 #4 Name SID-RQ OPTION: ALL IDENTIFIED GROUP OF DTC GROUP OF DTC Value $18 $00 $FF $00
Positive Response: Byte #1 #2 #3 : : : : : : #n Name SID-PR NUMBER OF STORED DTCs LIST OF DTC AND STATUS=[ DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC : DTC (HIGH BYTE) (LOW BYTE) STATUS OF DTC ] Value $58 $xx $xx $xx $xx : $xx $xx $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Value $7F $18 $xx
Negative Response Codes: Response Code 0x12 Error text subFunction not supported, invalid format
3.6 ($1A) ReadEcuIdentification

REI (ReadEcuIdentification) Request: Byte #1 #2 Name SID-RQ IDENTIFICATION OPTION Value $1A $xx
Positive Response: Byte #1 #2 #3 : #n Name SID-PR IDENTIFICATION OPTION DATA Value $5A $xx $xx : $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Value $7F $1A $xx
3.7 ($20) StopDiagnosticSession

(StopDiagnosticSession) Request: Byte #1 #2 Name SID-RQ DIAGNOSTIC MODE Value $20 $81
Positive Response: Byte #1 #2 Name SID-PR DIAGNOSTIC MODE Value $60 $81
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Value $7F $20 $xx
3.8 ($21) ReadDataByLocalIdentifier

RDBLI (ReadDataByLocalIdentifier) Request: Byte #1 #2 Name SID-RQ LID Value $21 $xx
Positive Response: Byte #1 #2 #3 : #n Name SID-PR LID DATA Value $61 $xx $xx : $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format securityAccessDeined Value $7F $21 $xx
To see full information on this service, please go to chapter 5.1.6
3.9 ($27) securityAccess

SA (securityAccess) Request #1: Byte #1 #2 Name SID-RQ #1 ACCESS MODE Value $27 $03
Positive Response #1: Byte #1 #2 #3 #4 Name SID-PR #1 ACCESS MODE SEED #1 (HIGH BYTE) (LOW BYTE) Value $67 $03 $xx $xx
Negative Response #1: Byte #1 #2 #3 Name SID-NR #1 SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Conditions not correct Required time delay not expired Value $7F $27 $xx
Negative Response Codes #1: Response Code 0x12 0x22 0x37 Request #2: Byte #1 #2 #3 #4 Name SID-RQ #2 ACCESS MODE KEY #1 (HIGH BYTE) (LOW BYTE) Value $27 $04 $xx $xx
Positive Response #2: Byte #1 #2 #3 Name SID-PR #2 ACCESS MODE SECURITY ACCESS ALLOWED Value $67 $04 $34
Negative Response #2: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Conditions not correct, Request sequence error Invalidkey Value $7F $27 $xx
Negative Response Codes #2: Response Code 0x12 0x22 0x35
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 Testers 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).
3.10 ($31) StartRoutineByLocalIdentifier

STRBLI (StartRoutineByLocalIdentifier) Request: Byte #1 #2 #3 : #n Name SID-RQ LID DATA Value $31 $xx $xx : $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format securityAccessDeined Value $7F $31 $xx
3.11 ($32) StopRoutineByLocalIdentifier

SRBLI (StopRoutineByLocalIdentifier) Request: Byte #1 #2 #3 : #n Name SID-RQ LID DATA Value $32 $xx $xx : $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text Value $7F $32 $xx
Negative Response Codes: Response Code
3.12 ($3B) WriteDataByLocalIdentifier

WDBLI (WriteDataByLocalIdentifier) Request: Byte #1 #2 #3 : #n Name SID-RQ LID DATA Value $3B $xx $xx
Positive Response: Byte #1 #2 Name SID-PR LID Value $7B $xx
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Error text securityAccessDeined Value $7F $3B $xx
3.13 ($3E) TesterPresent

TP (TesterPresent) Request: Byte #1 Name SID-RQ Value $3E
Positive Response: Byte #1 Name SID-PR Value $7E
Negative Response: Byte #1 #2 #3 Name SID-NR SID-RQ RESPONSE CODE Value $7F $3E $xx
Negative Response Codes: Response Code Error text
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. Negative Response Codes: Response Code Hex Value $11 $12 $21 $22 $23 $27 $31 $33 $35 $37 $80 Definition of Response Code ServiceNotSupported subFunctionNotSupported-invalidFormat busy-repeatRequest conditionsNotCorrectOrRequestSequenceError routineNotComplete securityAccess requestOutOfRange securityAccessDenied invalidKey requiredTimeDelayNotExpired serviceNotSupportedInActiveDiagnosticMode Description
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 SubFunctionNotSupportedInvalidFormat ($7F $10 ResponseCode $12)
Contents
5.1 Basic Variant 5.1.1 ECU Configuration

Parameter Block Size (TPDU.BS) Separation Time (TPDU.ST) CAN Id. of the diagnostic request message from Tester CAN Id. of the diagnostic response message from ECU Receive buffer size Value FFh 0ms or as requested from tester 7B0h 7DCh 120 bytes
5.1.2
ECU Physical Address

ECU Address (hex) A2 Diagnostic Tool Address (hex) F1
5.1.3 5.1.3.1
Sessions ($10 $81) startDiagnosticSession
This Diagnostic Session allows the KWP2000 Services which are used for reading errors, identification and data. Service Start Example: Request: Byte #1 #2 #03 Name SID-RQ DIAGNOSTIC MODE, Default Session BaudrateIdentifier Value $10 $81 $00 Protocol service ($10) StartDiagnosticSession, see page 8
Positive Response: Byte #1 #2 Name SID-PR DIAGNOSTIC MODE, Default Session Value $50 $81
5.1.4 5.1.4.1
Service Read
Identifications ($1A) ReadECUIdentification

Protocol service ($1A) ReadEcuIdentification, see page 12
Subfunction: IDENTIFICATION OPTION ($80, $91, $92, $94, $97, $99)
Hex Identification Option Value 80 91 Identification Code FIAT drawing number
ECU # of Data Identification Bytes Format Data Format All the following 61 data "123456789" 11 ASCII
BERU f1systems Supported equivalent to Ferrari part number, e.g. "0 0 0 0 0 2 4 4 9 5 2" for ECU BERU f1systems Hardware Number 0 1 0 0 1 2 1 4 0 0 1 BERU f1systems Hardware Version A BERU f1systems Software Number 0 0 F 1 3 7 2 2 1 9 D BERU f1systems Software Version e.g. 05 02 (Value is displayed in hex) not supported "4F 83 01 07 2F" for part number 244952 for ECU not supported date of production, since ecu reprogramming by tester is not allowed
92 93 94 95 96 97 98 99
ECU Hardware Number Tbd ECU Hardware Version Tbd ECU Software Number Tbd ECU Software Version Omologation Number ISO Code Tester Code Date of download/production Tbd Tbd xx xx xx xx xx Tbd 20 02 03 25 [YY YY MM DD]
11 1 11 2 6 5 10 4
ASCII UNSGN ASCII UNSGN ASCII UNSGN ASCII BCD
Example: Request: Byte Name #1 SID-RQ #2 IDENTIFICATION OPTION, ISO Code Positive Response: Byte Name #1 SID-PR #2 IDENTIFICATION OPTION, ISO Code #3 DATA #4 DATA #5 DATA #6 DATA #7 DATA
Value $1A $97
Value $5A $97 $4F $83 $01 $02 $2A
5.1.5
Error Memory
Protocol service ($18) ReadDiagnosticTroubleCodesByStatus 2Byte Hex - All Identified, see page 11 ($17) ReadStatusOfDiagnosticTroubleCodes, see page 10 ($14) ClearDiagnosticInformation, see page 9
Service Read (identified errors - 2Byte Hex) Read (environment data) Delete (all errors)
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
B7B6B5B4B3B2B1B0
Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7
DTC fault symptom DTC fault symptom DTC fault symptom DTC fault symptom DTC fault symptom DTC storage state DTC storage state DTC warning lamp state
0=no fault symptom available for this DTC 1=above maximum threshold 2=below minimum threshold 4=no signal 8=invalid signal 0=test complete for this DTC or not applicable 1=test not complete for this DTC 0=error not saved 1=sporadic 2=error occurred temporarily 3=permanent 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.
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
Request: Byte #1 #2 #3
($FF) FNC_CLEAR_ERROR_MEMORY
Same as ($FF) Group of DTC, All
Name SID-RQ GROUP OF DTC, All (HIGH BYTE) GROUP OF DTC, All (LOW BYTE)
Value $14 $FF $00
Positive Response: Byte #1 #2 #3 Name SID-PR GROUP OF DTC, All (HIGH BYTE) GROUP OF DTC, All (LOW BYTE) Value $54 $FF $00
5.1.5.6
readStatusOfDiagnosticTroubleCodes
5.1.5.6.1 ($17 $00) StatusOfDTC

Request information on one DTC Request: Byte #1 #2 #3 Name SID-RQ DTC (HIGH BYTE) DTC (LOW BYTE) Value $17 $xx $xx
Positive Response: Byte #1 #2 $3 $4 $5 $6 $7 $8 $9 $10 $11 $12 Name SID-PR NUMBER OF DTC 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 ] Value $57 $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx
Negative Response: Byte #1 #2 #3 Name SID-NR #1 SID-RQ RESPONSE CODE Error text subFunction not supported, invalid format Value $7F $17 $xx
5.1.5.6.2 Environmental Conditions Parameter Table

Position 1 2 Description ECU Supply Voltage LINV Conversion Data / 10 [V] logged only when DTC corresponding to voltage is set. 0 in other cases. Data / 10 [V] logged only when DTC corresponding to voltage is set. 0 in other cases.
3 4
ECU Temperature Sensor Remaining Battery Life
5 6
Not Used Not Used
Data 40[ C] logged only when DTC corresponding to voltage is set. 0 in other cases. Data [months]. logged only when DTC corresponding to battery life less than 2 months is set. 0 in other cases.
5.1.5.7
readDiagnosticTroubleCodeByStatus
5.1.5.7.1 ($18 $00) DTCByStatus

RequestAllErrors Request: Byte #1 #2 #3 #4 Name SID-RQ OPTION: Identified 2 Byte Hex DTC and Status GROUP OF DTC Group of DTC Value $18 $00 $FF $00
Positive Response: Byte #1 #2 #3 : : : #n Name SID-PR NUMBER OF DTCs LIST OF DTC AND STATUS=[ DTC DTC STATUS : DTC DTC STATUS ] Value $58
5.1.6
($21) ReadDataByLocalIdentifier, Current Data (Snapshots)
Local Identifier: LID ($xx) Service Read Protocol service ($21) ReadDataByLocalIdentifier, see page 14
5.1.6.1
($21 $30) Diagnostic Service "read measurement data wheel electronic"
Status of modification Prepared / date Revised / date Name Description
02 James Shingleton / 14th June 2007 ($21 $30) Diagnostic Service "read measurement data wheel electronic" 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) 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! Production (EOL test), service 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 Value $21 $30 Value $61 $30 p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel. T [ C] = $xx-40 value range (phys.) (-40)...125 deg. p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) $xx $xx
Requirement Reference Addressee Default values
Request message: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 #3 #4 Record Local Identifier Current pressure value, wheel FL (at reference temperature 20C) Current pressure value, wheel FL
#5 #6
Current temperature value, wheel FL Current pressure value, wheel FR (at reference temperature 20C)
$xx $xx
#7
Current pressure value, wheel FR
#8 #9 #10
Current temperature value, wheel FR Current pressure value, wheel RL (at reference temperature 20C) Current pressure value, wheel RL
#11 #12 #13
Current temperature value, wheel RL Current pressure value, wheel RR (at reference temperature 20C) Current pressure value, wheel RR
#14 #15
Current temperature value, wheel RR Parameter status electronic control unit
p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel. T [ C] = $xx-40 value range (phys.) (-40)...125 deg. p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel. T [ C] = $xx-40 value range (phys.) (-40)...125 deg. p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) p [mbar] = $xx*0.025bar (pressure resolution = 0.025bar) value range (phys.) 0...5.375 bar rel. T [ C] = $xx-40 value range (phys.) (-40)...125 deg.
$xx
$xx $xx $xx
$xx $xx $xx
$xx $xx
Parameter status electronic control unit

B7B6B5B4B3B2B1B0 Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 learning status learning status learning status assignment status assignment status assignment status assignment status assignment status 1=system learning 1=system checking 1=system learned 1=Map 1 is active (Bridgestone tyres fitted) 1=Map 2 is active (Goodyear tyres fitted) 1=Map 3 is active (Michelin tyres fitted) 1=Map 4 is active (Pirelli tyres fitted) 1=Map 5 is active (Pirelli Corsa tyres fitted)
5.1.6.2
($21 $31) Diagnostic service "read status wheel electronic"

02 James Shingleton / 14th June 2007 ($21 $31) Diagnostic service "read status wheel electronic" 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: 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! Default values / not available / invalid Remaining durability of wheel electronic battery = FFh Default values / not available / invalid Parameter status wheel electronic position XX = FFh Value $21 $31 Value $61 $31 $xx $xx $xx $xx $xx $xx $xx $xx $xx
Request message: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 Record Local Identifier #3 Remaining durability of wheel electronic battery FL 0 ...120dec value range (phys.) #4 Parameter status wheel electronic position XX = FL #5 Remaining durability of wheel electronic battery FR 0 ... 120dec value range (phys.) #6 Parameter status wheel electronic position XX = FR #7 Remaining durability of wheel electronic battery RL 0 ... 120dec value range (phys.) #8 Parameter status wheel electronic position XX = RL #9 Remaining durability of wheel electronic battery RR 0 ... 120dec value range (phys.) #10 Parameter status wheel electronic position XX = RR #11 Parameter status electronic control unit
Parameter status wheel electronic position XX

B7B6B5B4B3B2B1B0 Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 sending mode position XX sending mode position XX 0=storage mode 1=normal 2=rapid (in case of puncture) 3=rapid (in case of excessive temperature)
hardware error position XX if X=1 measurement error position XX if X=1 autotransmit bit set position XX if X=1 roll switch bit set position XX if X=1 tx on LF request bit set position XX if X=1 power management indicator bit set position XX if X=1

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

02 James Shingleton / 14th June 2007 ($21 $32) Diagnostic service "read statistics on receipt of datagrams" This function enables reading of the statistics data on receipt of datagrams. 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! Default value / not available / invalid counter of datagrams received from wheel electronic = 00h Parameter status electronic control unit = FFh Value $21 $32 Value $61 $32 $xx $xx $xx $xx $xx $xx $xx $xx $xx
Status of modification Prepared / date Revised / date Name Description Requirement Reference Addressee Defaultvalues
Request message: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 Record Local Identifier #3 counter of datagrams received from wheel electronic FL (high byte) #4 counter of datagrams received from wheel electronic FL (low byte) #5 counter of datagrams received from wheel electronic FR (high byte) #6 counter of datagrams received from wheel electronic FR (low byte) #7 counter of datagrams received from wheel electronic RL (high byte) #8 counter of datagrams received from wheel electronic RL (low byte) #9 counter of datagrams received from wheel electronic RR (high byte) #10 counter of datagrams received from wheel electronic RR (low byte) #11 Parameter status electronic control unit

5.1.6.4
($21 $33) Diagnostic service "read identifier and position of wheel electronic"
02 James Shingleton / 14 June 2007 ($21 $33) Diagnostic service "read identifier and position of wheel electronic" 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.
th
Default values / not available = 00h invalid Parameter position wheel electronic = FFh Value $21 $33 Value $61 $33 $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx
Request message: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 Record Local Identifier #3 Identifier of wheel electronic FL (high byte) #4 Identifier of wheel electronic FL #5 Identifier of wheel electronic FL #6 Identifier of wheel electronic FL (low byte) #7 Identifier of wheel electronic FR (high byte) #8 Identifier of wheel electronic FR #9 Identifier of wheel electronic FR #10 Identifier of wheel electronic FR (low byte) #11 Identifier of wheel electronic RL (high byte) #12 Identifier of wheel electronic RL #13 Identifier of wheel electronic RL #14 Identifier of wheel electronic RL (low byte) #15 Identifier of wheel electronic RR (high byte) #16 Identifier of wheel electronic RR #17 Identifier of wheel electronic RR #18 Identifier of wheel electronic RR (low byte) #19 Parameter status electronic control unit

Example 1) 1001382118 dec = 3BAFE0E6 hex #3 Identifier of wheel electronic FL (high byte) #4 Identifier of wheel electronic FL #5 Identifier of wheel electronic FL #6 Identifier of wheel electronic FL (low byte) Example 2) 1500035925 dec = 5968BB55 hex #7 Identifier of wheel electronic FR (high byte) #8 Identifier of wheel electronic FR #9 Identifier of wheel electronic FR #10 Identifier of wheel electronic FR (low byte) Example 3) 1001375227 dec = 3BAFC5FB hex #11 Identifier of wheel electronic RL (high byte) #12 Identifier of wheel electronic RL #13 Identifier of wheel electronic RL #14 Identifier of wheel electronic RL (low byte) Example 4) 1001365532 dec = 3BAFA01C hex #15 Identifier of wheel electronic RR (high byte) #16 Identifier of wheel electronic RR #17 Identifier of wheel electronic RR #18 Identifier of wheel electronic RR (low byte)
$3B $AF $E0 $E6
$59 $68 $BB $55
$3B $AF $C5 $FB
$3B $AF $A0 $1C
5.1.6.5
($21 $34) Diagnostic service "read event memory"

02 James Shingleton / 14th June 2007 ($21 $34) Diagnostic service "read event memory" This function enables reading of the entries in the event memory. The error and event codes and their meanings can be taken from the tables at the end of this document.
Status of modification Prepared / date Revised / date Name Description Requirement Reference Addressee Default values
Request message format: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 Record Local Identifier #3 Event code Byte 0 #4 Event code Byte 1 #5 Event code Byte 2 #6 Event code Byte 3
Value $21 $34 Value $61 $34 $xx $xx $xx $xx
5.1.6.6
Stored Data
5.1.6.6.1 ($21 $82) Sincom And Factory

Local Identifier: LID ($82) Read Positive Response: Byte 05 Bit Name SincomAndFactory Conversion ASCII Comments Written by tester
5.1.6.6.2 ($21 $83) Serial Number

Local Identifier: LID ($83) Read Positive Response: Byte 2 bytes Bit Name Serial number Conversion UNSGN Comments Defined by BERU f1systems
5.1.6.6.3 ($21 $90) VIN (Vehicle Identification Number)

Local Identifier: LID ($90) Read Positive Response: Byte 0 16 Bit Name VIN Conversion ASCII Comments Written by tester
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
5.1.8
Service Write
($3B) WriteDataByLocalIdentifier, Write Memory Block

Protocol service ($3B) WriteDataByLocalIdentifier
5.1.8.1
($3B $82) Diagnostic service "SincomAndFactory"

01 James Shingleton / 08 June 2007 ($3B $82) Diagnostic service "SincomAndFactory" This function enables the Sincom, Plant and Location code to be written into the ECU.
th
Request message: Byte Parameter Description #1 Write Data By Local Identifier Request Service ID #2 Record Local Identifier #3 Sincom (Byte 1) #4 Sincom (Byte 2) #5 Sincom (Byte 3) #6 Factory (Byte 1) #7 Factory (Byte 2) #8 Series (Byte 1) Positive response message: Byte Parameter Description #1 Write Data By Local Identifier Positive Response ID #2 Record Local Identifier Negative Response: Byte Name #1 SID-NR #2 SID-RQ #3 RESPONSE CODE Negative Response Codes: Value Definition of Response Code $12 subFunction not supported, invalid format $33 securityAccessDeined
Value $3B $82 $xx $xx $xx $xx $xx $xx Value $7B $82 Value $7F $3B $xx
Description in case the format of the message sent to the ECU is not correct in case the ECU has not been unlocked using the security access procedure.
5.1.8.2
($3B $90) Diagnostic service "VIN (Vehicle Identification Number)"

01 James Shingleton / 08th June 2007 ($3B $90) Diagnostic service "VIN (Vehicle Identification Number)" This function enables VIN to be written into the ECU.
Request message: Byte Parameter Description #1 Write Data By Local Identifier Request Service ID #2 Record Local Identifier #3 V.M.I. (Byte 1) #4 V.M.I. (Byte 2) #5 V.M.I. (Byte 3) #6 V.D.S. (Byte 1) #7 V.D.S. (Byte 2) #8 V.D.S. (Byte 3) #9 V.D.S. (Byte 4) #10 V.D.S. (Byte 5) #11 V.D.S. (Byte 6) #12 V.I.S. (Byte 1) #13 V.I.S. (Byte 2) #14 V.I.S. (Byte 3) #15 V.I.S. (Byte 4) #16 V.I.S. (Byte 5) #17 V.I.S. (Byte 6) #18 V.I.S. (Byte 7) #19 V.I.S. (Byte 8) Positive response message: Byte Parameter Description #1 Write Data By Local Identifier Positive Response ID #2 Record Local Identifier Negative Response: Byte Name #1 SID-NR #2 SID-RQ #3 RESPONSE CODE Negative Response Codes: Value Definition of Response Code $12 subFunction not supported, invalid format $33 securityAccessDeined
Value $3B $90 $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx $xx Value $7B $90 Value $7F $3B $xx
Description in case the format of the message sent to the ECU is not correct in case the ECU has not been unlocked using the security access procedure.
($31) StartRoutineByLocalIdentifier ($32) StopRoutineByLocalIdentifier

Service Start Stop Protocol Service ($31) StartRoutineByLocalIdentifier ($32) StopRoutineByLocalIdentifier
5.1.8.3
($31 $03) Diagnostic service "execute test of wheel electronic"

01 James Shingleton / 17 May 2007 ($31 $03) Diagnostic service "execute test of wheel electronic" 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. 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! ($21 $33) Diagnostic service "read identifier and position of wheel electronic" Production (EOL test) Value $31 $03 $xx
th
Requirement Reference Addressee Default values:
Request message: Byte Parameter Description #1 Start Routine By Local Identifier Request Service ID #2 Routine Local Identifier #3 Parameter execute wheel sensor test, requested
Parameter execute wheel sensor test, requested

B7B6B5B4B3B2B1B0 0dec = Autoping FL 1dec = Autoping FR 2dec = Autoping RL 3dec = Autoping RR 4dec = Autoping ALL 5dec -> 255dec = reserved
Positive response message: Byte Parameter Description #1 Start Routine By Local Identifier Positive Response Service ID #2 Routine Local Identifier Execution of the routine is ended using the following request block of the Diagnostic Tester: Request message: Byte Parameter Description #1 Stop Routine By Local Identifier Request Service ID #2 Routine Local Identifier Positive response message: Byte Parameter Description #1 Stop Routine By Local Identifier Positive Response Service ID #2 Routine Local Identifier Negative Response: Byte Name #1 SID-NR #2 SID-RQ #3 RESPONSE CODE Negative Response Codes: Value Definition of Response Code $12 subFunctionNotSupportedinvalidFormat $22 conditionsNotCorrectOrRequestSequen ceError $22 $33 securityAccessDeined
Value $71 $03
Value $32 $03 Value $72 $03 Value $7F $31 $xx
Description in case value in Parameter execute wheel sensor test, requested value > 5 in case routine shall be stopped using StopRoutineByLocalIdentifier, but either no or any other is running at that time in case the status of the ECU is not system learned in case the ECU has not been unlocked using the security access procedure.
5.1.8.4
($31 $04) Diagnostic service "learn car wheels"

01 James Shingleton / 17 May 2007 ($31 $04) Diagnostic service "learn car wheels" 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. ($21 $31) Diagnostic service "read status wheel electronic" Production (EOL test), service
th
Requirement Reference: Addressee Default values
Request message: Byte Parameter Description #1 Read Data By Local Identifier Request Service ID #2 Record Local Identifier #3 Parameter learn car wheels Positive response message: Byte Parameter Description #1 Read Data By Local Identifier Positive Response Service ID #2 Record Local Identifier Execution of the routine is ended using the following request block of the Diagnostic Tester: Request message: Byte Parameter Description #1 Stop Routine By Local Identifier Request Service ID #2 Routine Local Identifier Positive response message: Byte Parameter Description #1 Stop Routine By Local Identifier Positive Response Service ID #2 Routine Local Identifier Negative Response: Byte Name #1 SID-NR #2 SID-RQ #3 RESPONSE CODE
Value $31 $04 $80 Value $71 $04
Value $32 $04 Value $72 $04 Value $7F $31 $xx
Negative Response Codes: Value Definition of Response Code Description $22 conditionsNotCorrectOrRequestSequen in case routine shall be stopped using StopRoutineByLocalIdentifier, but either no or any ceError other is running at that time $33 SecurityAccessDeined in case the ECU has not been unlocked using the security access procedure. $12 subFunctionNotSupportedin case bits 0-6 in Parameter learn car wheels are invalidFormat not = 0
5.1.8.5
($31 $06) Diagnostic service "delete event memory"

01 James Shingleton/ 24th May 2007 ($31 $06) Diagnostic service "delete event memory" This function allows the event memory to be deleted in connection with a code byte. 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.
Status of modification Prepared / date Revised / date Name Description Requirement
Reference Addressee Default values
Request message: Byte Parameter Description #1 Start Routine By Local Identifier Request Service ID #2 Routine Local Identifier #3 Code Byte Positive response message: Byte Parameter Description #1 Start Routine By Local Identifier Positive Response Service ID #2 Routine Local Identifier
Value $31 $06 $99 Value $71 $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: Byte Parameter Description #1 Stop Routine By Local Identifier Request Service ID #2 Routine Local Identifier Positive response message: Byte Parameter Description #1 Stop Routine By Local Identifier Positive Response Service ID #2 Routine Local Identifier Negative Response: Byte Name #1 SID-NR #2 SID-RQ #3 RESPONSE CODE Value $32 $06 Value $72 $06 Value $7F $31 $xx
Negative Response Codes: Value Definition of Response Code Description $22 conditionsNotCorrectOrRequestSequen in case routine shall be stopped using StopRoutineByLocalIdentifier, but either no or any ceError other is running at that time
$33
securityAccessDeined
in case the ECU has not been unlocked using the security access procedure.
6
Step 1 2 3 4 5 6 7 8 9 10
Proposal for EOL Test Cycle

Description Vehicle identification ($10$81$00) Init communication ($1A$80) Read ECU identification ($14$FF$00) Cancel DTC (key off then key on) ($10$81$00) Init communication ($21$33) Read wheel sensor IDs ($21$34) Read all Event Code bytes ($21$30) Read pressures for all wheels ($18$02$FF$00) Read and verify DTC Printout results Test successful Status BERU
Index
7.1 Protocol Services
SID $10 $14 $17 $18 $1A $21 $27 $31 $32 $3B $3E
Service Identifier Definition Name StartDiagnosticSession ClearDiagnosticInformation ReadStatusOfDiagnosticTroubleCodes ReadDiagnosticTroubleCodesByStatus - All Identified ReadEcuIdentification ReadDataByLocalIdentifier SecurityAccess StartRoutineByLocalIdentifier StopRoutineByLocalIdentifier WriteDataByLocalIdentifier TesterPresent
See page 8 9 10 11 12 14 15 17 18 19 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)"
Manufacturer-specific Data
8.1 Use of Byte Parameters as Text Markers

Parameter name Description 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 Default values
8.1.1

Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 sending mode position XX sending mode position XX 0=storage mode 1=normal 2=rapid (in case of puncture) 3=rapid (in case of excessive temperature)

B7B6B5B4B3B2B1B0
hardware error position XX if X=1 measurement error position XX if X=1 autotransmit bit set position XX if X=1 roll switch bit set position XX if X=1 tx on LF request bit set position XX if X=1 power management indicator bit set position XX if X=1
8.1.2

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

B7B6B5B4B3B2B1B0
8.1.3
Parameter test result and routine status

Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 reserved reserved reserved reserved reserved reserved routine status routine status
Parameter test result and routine status

B7B6B5B4B3B2B1B0
0=not started or finalised before end of execution or interrupted 1=not o.k. finalised 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.
8.1.4

B7B6B5B4B3B2B1B0 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

Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 reserved reserved reserved reserved reserved reserved reserved learn wheels fitted to car if X=1
Parameter learn car wheels

B7B6B5B4B3B2B1B0
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.
Referenced Documents
Description Version Author Date Status
Filename
10
List of Event Codes

Event Consequence 1 No internal fault consequence 2 No internal fault consequence 3 No internal fault consequence 4 No internal fault consequence 5 Tyre pressure of the affected tyre cannot be monitored 1 No internal fault consequence 2 No internal fault consequence 3 No internal fault consequence 4 No internal fault consequence 5 Tyre pressure of the affected tyre cannot be monitored
BERU f1systems Error Code
Event Description
Time of detection
Reset Condition
Ferrari event byte
Ferrari event bit
Event Cause
ECU category: wheel FL 1 0 225 Puncture, hard warning, dynamic A rapid pressure loss from the tyre is detected by the system Minimum pressure value, hard warning, static The tyre pressure has dropped below the hard warning tyre pressure limit. Threshold for warning, soft warning, static The tyre pressure has dropped below the soft warning tyre pressure limit. Threshold for over pressure warning The tyre pressure has exceeded the over pressure warning limit Excessive sensor temperature The sensor temperature has exceeded 120 C and shut down temporarily. Ploss > 350mbar/min Immediately Key 15 cycle: Transition from key 15 OFF to key 15 ON Ptyre > Pcold
1 114
Ptyre < Pcold - 500mbar
Immediately
2 110
Immediately
Ptyre > Pcold
1 1 1 1 1
3 118 4 238 5 6 7
Ptyre > 3.5bar Ttyre > 120 C
Immediately Immediately
Ptyre < 3.5bar Ttyre < 100 C
ECU category: wheel FR 2 0 225 Puncture, hard warning, dynamic A rapid pressure loss from the tyre is detected by the system Minimum pressure value, hard warning, static The tyre pressure has dropped below the hard warning tyre pressure limit. Threshold for warning, soft warning, static The tyre pressure has dropped below the soft warning tyre pressure limit. Threshold for over pressure warning The tyre pressure has exceeded the over pressure warning limit Excessive sensor temperature The sensor temperature has exceeded 120 C and shut down temporarily. Ploss > 350mbar/min Immediately Key 15 cycle: Transition from key 15 OFF to key 15 ON Ptyre > Pcold
1 114
Immediately
2 110
Immediately
Ptyre > Pcold
2 2
3 118 4 238
2 2 2
5 6 7 ECU category: wheel RL
Priority
0 225
Puncture, hard warning, dynamic A rapid pressure loss from the tyre is detected by the system Minimum pressure value, hard warning, static The tyre pressure has dropped below the hard warning tyre pressure limit. Threshold for warning, soft warning, static The tyre pressure has dropped below the soft warning tyre pressure limit. Threshold for over pressure warning The tyre pressure has exceeded the over pressure warning limit Excessive sensor temperature The sensor temperature has exceeded 120 C and shut down temporarily.
Ploss > 350mbar/min
Immediately
1 114
Immediately
Key 15 cycle: Transition from key 15 OFF to key 15 ON Ptyre > Pcold
1 No internal fault consequence 2 No internal fault consequence 3 No internal fault consequence 4 No internal fault consequence 5 Tyre pressure of the affected tyre cannot be monitored
2 110
Immediately
Ptyre > Pcold
3 3 3 3 3
3 118 4 238 5 6 7
ECU category: wheel RR 4 0 225 Puncture, hard warning, dynamic A rapid pressure loss from the tyre is detected by the system Minimum pressure value, hard warning, static The tyre pressure has dropped below the hard warning tyre pressure limit. Threshold for warning, soft warning, static The tyre pressure has dropped below the soft warning tyre pressure limit. Threshold for over pressure warning The tyre pressure has exceeded the over pressure warning limit Excessive sensor temperature The sensor temperature has exceeded 120 C and shut down temporarily. Ploss > 350mbar/min Immediately Key 15 cycle: Transition from key 15 OFF to key 15 ON Ptyre > Pcold 1 No internal fault consequence 2 No internal fault consequence 3 No internal fault consequence 4 No internal fault consequence 5 Tyre pressure of the affected tyre cannot be monitored
1 114
Immediately
2 110
Immediately
Ptyre > Pcold
4 4
3 118 4 238
4 4 4
5 6 7
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.
11
List of Error Codes

Environmental Conditions Logged [1] ECU Supply Voltage [2] LINV [3] ECU Temperature [1] ECU Supply Voltage [2] LINV [3] ECU Temperature [1] ECU Supply Voltage [2] LINV [3] ECU Temperature [4] Sensor Remaining Battery Life BERU f1systems Error Code Error Cause DTC Fault Symptom (bin) Time of detection
Reset Condition
Subassembly: ECU Control unit category: hardware 5001h 0000 ECU Failure 204 Internal Undervoltage Measuring undervoltage in the ECU regulated voltage supply circuitry 205 Internal Overvoltage Measuring excess voltage in the ECU regulated voltage supply circuitry 210 Internal Excess Temperature Measuring excess temperature in the ECU circuitry 208 LINV Undervoltage Measuring undervoltage in the LINV supply circuitry 209 LINV Excess voltage Measuring excess voltage in the LINV supply circuitry Control unit category: vehicle 5002h 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 VDD < 4.5V VDD > 5.2V Immediately Immediately VDD > 4.5V VDD < 5.2V
ECUTemp > 85 C LINV < 8.5V LINV > 13V
Immediately Immediately Immediately
ECUTemp < 85 C LINV > 8.5V LINV < 13V Degraded monitoring performance Degraded monitoring performance
0001
203 Voltage high key 30, excess voltage Measuring excess voltage in the vehicle electrical system on the protected side Control unit category: CAN
Vbatt > 18V
Immediately
Vbatt < 18V
5003h 0100
212 CAN bus no data Data required by TPMS missing from CAN messages 213 CAN bus bad data Data required by TPMS is invalid in the CAN messages Subassembly: wheel sensor Wheel sensor category: wheel sensor FL
Reception timeout of any Immediately CAN message Invalid data in one or more CAN messages Immediately
1000
Correct reception of CAN messages Correct reception of CAN messages
5010h
0000
142 Remaining battery lifetime low The remaining battery lifetime is less than 2 months.
Remaining-BatteryLifetime register < 2 months
Immediately
RemainingBatteryLifetime register > 2 months
Error Consequence System operates in stationary mode System operates in stationary mode Total failure of wheel sensor in approximately 2 months due to battery expiring
Event Cause
DTC Code
Priority
Status
5011h
0000
150 Sensor fault Internal measurement error
Measurement error bit in Immediately datagram set to 1
Measurement error bit in datagram set to 0 Internal sensor error bit in datagram set to 0 Datagram receeived
Pressure sensor defective. No correct pressure data supplied by wheel electronics 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
None
5013h
0000
146 Radio datagram not received No datagrams are received from the appropriate wheel sensor. Wheel sensor category: wheel sensor FR
No datagrams received for 160 secs
160 secs
No pressure monitoring for the wheel with the defective None wheel electronics
5020h
0000
Remaining battery lifetime low The remaining battery lifetime is less than 2 months.
Immediately
5021h
0000
Sensor fault Internal measurement error
RemainingBatteryLifetime register > 2 months Measurement error bit in datagram set to 0 Internal sensor error bit in datagram set to 0 Datagram receeived
Total failure of wheel sensor in approximately 2 months due to battery expiring Pressure sensor defective. No correct pressure data supplied by wheel electronics Pressure sensor defective. No correct pressure data supplied by wheel electronics
[4] Sensor Remaining Battery Life
None
5022h
0000
Sensor fault Internal sensor hardware error
Immediately
None
5023h
0000
Radio datagram not received No datagrams are received from the appropriate wheel sensor. Wheel sensor category: wheel sensor RL
160 secs
5030h
0000
Immediately
5031h
0000
RemainingBatteryLifetime register > 2 months Measurement error bit in datagram set to 0 Internal sensor error bit in datagram set to 0 Datagram receeived
Total failure of wheel sensor in approximately 2 months due to battery expiring Pressure sensor defective. No correct pressure data supplied by wheel electronics Pressure sensor defective. No correct pressure data supplied by wheel electronics
None
5032h
0000
Immediately
None
5033h
0000
Radio datagram not received No datagrams are received from the appropriate wheel sensor. Wheel sensor category: wheel sensor RR
160 secs
5040h
0000
Immediately
RemainingBatteryLifetime register > 2 months
Total failure of wheel sensor in approximately 2 months due to battery expiring
5041h
0000
Measurement error bit in datagram set to 0 Internal sensor error bit in datagram set to 0 Datagram receeived
Pressure sensor defective. No correct pressure data supplied by wheel electronics Pressure sensor defective. No correct pressure data supplied by wheel electronics
None
5042h
0000
Immediately
None
5043h
0000
Radio datagram not received No datagrams are received from the appropriate wheel sensor. Subassembly: digital receiving antenna Digital receiving antenna category: LIN interface front antenna
160 secs
5050h
0000
164 Antenna Fault No communication with antenna 172 Antenna Fault Wrong frequency antenna, or trigger connected 168 Antenna Fault LIN bus fault
No communication with antenna
5 secs
Antenna reconneted Correct frequency antenna connected Correct reception of LIN data signals from antenna Antenna reconneted Correct frequency antenna connected Correct reception of LIN data signals from antenna
5051h
0000
Wrong frequency 5 secs antenna connected, or trigger connected instead Incorrect reception of LIN 5 secs data signals from antenna
5052h
0000
No pressure monitoring for wheels which have datagrams received by this antenna No pressure monitoring for wheels which have datagrams received by this antenna No pressure monitoring for wheels which have datagrams received by this antenna
[1] ECU Supply Voltage [2] LINV [3] ECU Temperature
Digital receiving antenna category: LIN interface rear antenna 5060h 0000 164 Antenna Fault No communication with antenna 172 Antenna Fault Wrong frequency antenna, or trigger connected 168 Antenna Fault LIN bus fault No communication with antenna 5 secs
5061h
0000
Wrong frequency 5 secs antenna connected, or trigger connected instead Incorrect reception of LIN 5 secs data signals from antenna
5062h
0000
Subassembly: LF satellite trigger LF satellite trigger category: LIN interface front left trigger 5070h 0000 176 Trigger Fault No communication with trigger 184 Trigger Fault Wrong componentconnected 180 Trigger Fault LIN bus fault No communication with trigger Antenna connected 5 secs
Trigger reconneted Connect trigger Correct reception of LIN data signals from trigger
5071h
0000
5 secs
5072h
0000
Incorrect reception of LIN 5 secs data signals from trigger
LF satellite trigger category: LIN interface front right trigger
5080h
0000
176 Trigger Fault No communication with trigger 184 Trigger Fault Wrong componentconnected 180 Trigger Fault LIN bus fault
No communication with trigger Antenna connected
5 secs
Trigger reconneted Connect trigger Correct reception of LIN data signals from trigger Trigger reconneted Connect trigger Correct reception of LIN data signals from trigger Trigger reconneted Connect trigger Correct reception of LIN data signals from trigger
5081h
0000
5 secs
5082h
0000
LF satellite trigger category: LIN interface rear left trigger 5090h 0000 176 Trigger Fault No communication with trigger 184 Trigger Fault Wrong componentconnected 180 Trigger Fault LIN bus fault No communication with trigger Antenna connected 5 secs
5091h
0000
5 secs
5092h
0000
LF satellite trigger category: LIN interface rear right trigger 50A0h 0000 176 Trigger Fault No communication with trigger 184 Trigger Fault Wrong componentconnected 180 Trigger Fault LIN bus fault No communication with trigger Antenna connected 5 secs
50A1h
0000
5 secs
50A2h
0000

F1-407-1355-002 - M145 TPMS Diagnostics Specification V1 - 02

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

F1-407-1355-002 - M145 TPMS Diagnostics Specification V1 - 02

Enviado por

Direitos autorais:

Formatos disponíveis

Diagnostics Specification

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 1 of 59

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 2 of 59

Conventions ..................................................................................................... 5 Overview ........................................................................................................... 6

Error Handling................................................................................................ 21 Contents ......................................................................................................... 22

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

Proposal for EOL Test Cycle......................................................................... 47 Index ............................................................................................................... 48

Manufacturer-specific Data ........................................................................... 49

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 4 of 59

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 5 of 59

2.1 Control Unit

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 6 of 59

Normal/Default Session Subfunction: ($10 $81)

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

End Of Line Vehicle Manufacturer Session Subfunction: ($10 $83)

3.2 ($10) StartDiagnosticSession

Negative Response Codes: Response Code 0x12

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 8 of 59

3.3 ($14) ClearDiagnosticInformation

Negative Response Codes: Response Code 0x12 0x23

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 9 of 59

3.4 ($17) ReadStatusOfDiagnosticTroubleCodes

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

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 10 of 59

3.5 ($18) ReadDiagnosticTroubleCodesByStatus

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

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 11 of 59

3.6 ($1A) ReadEcuIdentification

Negative Response Codes: Response Code 0x12

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

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 12 of 59

3.7 ($20) StopDiagnosticSession

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 13 of 59

3.8 ($21) ReadDataByLocalIdentifier

Negative Response Codes: Response Code 0x12 0x33

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

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 14 of 59

3.9 ($27) securityAccess

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 15 of 59

Negative Response Codes #2: Response Code 0x12 0x22 0x35

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 16 of 59

3.10 ($31) StartRoutineByLocalIdentifier

Negative Response Codes: Response Code 0x12 0x33

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

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

BERU f1systems James Shingleton Diss, UK, 16.02.10 Page 17 of 59

3.11 ($32) StopRoutineByLocalIdentifier

Negative Response Codes: Response Code

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