Fiat Kwp2000

FIAT STANDARD DIAGNOSTIC PROTOCOL ON KLINE KWP 2000

Page:

/6

Date: 06/07/2000

 D.T.  F.V.  S.I.E.E.  S.S.E.  tel. 683.4766

MANAGER:

Mr. CIRIMBILLI Riccardo

 D.T.  F.V.  S.I.E.E.  S.S.E.  tel. 683.5423

Code

Eng. ANTONIOLI Bruno

PURPOSE This document describes Fiat requirements for the implementation of Keyword Protocol 2000 (KWP2000) services on Kline, defining the general rules.

Change

Date

=

Apr. ’’97

Edition   New.

(RG)

=

July ’’98

Edition 2  Completely revised.

(RG)

=

Mar. ’’99

Edition 3  Completely revised.

(RG)

A

Mar. ’’99

=

06.07.’’00

Edition

4

Ch.



SUPERVISOR:

TFO



normazione

07223

Description

““  Note at § 4.3 corrected. RLI list at § 7..2. modified. Some editing changes made

(RG)

Edition 4  Following para. have been revised: D Para. 2. Standard ISO/Para. 2.2. Reference standards list updated D para. 4.3 Timing data changed D para. 4.4.3.3 Timing DownLoad Session D para. 4.5. communication start/stop conditions changed D para. 5.2.2. ResponseCodes table modified. (h and 0h note NACK 0x78). D para. 6..2.. diagnostic session added for starting of components 89h and 84 D para. 6..2.3. DiagnosticService List D para. 6.3 securityAccess service D para. 7..2.. RLI 80h9Fh management changed D 8.2.2.3. Error Memory structure D Para 2 ScanTool added

ANY PRINTED COPY IS TO BE DEEMED AS UNCHECKED; THEREFORE THE UPDATED COPY MUST BE CHECKED IN THE APPROPRIATE WEB SITE

PUBLISHED BY SATIZ  NORMAZIONE

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

““

07223

Page

2

Change

CONTENTS  SCOPE

page 5

2 REFERENCE STANDARDS

page 5

2.

ISO Standard

page 5

2.2

Other Standards

page 5

3 DEFINITIONS AND ABBREVIATIONS 3.

Service identifiers

page 6

4 COMMUNICATION

page 7

4.

Introduction

page 7

4.2

Initialization

page 8

4.2. Fast initialization

page 8

4.2.2 5Baud initialization

page 8

4.2.3 Key Bytes

page 9

4.2.4 Physical addresses assigned to ECU and Diagnostic Tool

page 0

4.3

Communication timings

page 0

4.4

Communication services

page 

4.4. startCommunication service

page 

4.4.2 stopCommunication service

page 

4.4.3 accessTimingParameter service

page 2

Protocol structure

page 3

4.5

5 GENERAL RULES

page 4

5.

Service Identifier

page 4

5.2

negativeResponse

page 5

5.2. Message data bytes

page 5

5.2.2 Parameter Definitions

page 5

6 DIAGNOSTIC MANAGEMENT FUNCTIONAL UNIT CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

page 6

page 20

6.0

Introduction

page 20

6.

startDiagnosticSession service

page 2

6.. Message data bytes

page 2

6..2 Parameter Definitions

page 22

stopDiagnosticSession service

page 24

6.2. Message data bytes

page 24

securityAccess service

page 25

6.3. Message data bytes

page 26

6.3.2 Parameter Definitions

page 27

testerPresent service

page 28

6.4. Message data bytes

page 28

6.5

ecuReset service

page 29

6.6

readEcuIdentification service

page 29

6.6. Message data bytes

page 29

6.6.2 Parameter Definitions

page 30

6.2 6.3

6.4

continued

PUBLISHED BY SATIZ  NORMAZIONE

Page 3 Change

CONTENTS

7 DATA TRANSMISSION FUNCTIONAL UNIT

page 32

7.0

Introduction

page 32

7.

reaDataByLocalIdentifier service

page 32

7.. Message data bytes

page 32

7..2 Parameter Definitions

page 32

7.2

readDataByCommonIdentifier service

page 34

7.3

readMemoryByAddress service

page 34

7.4

dynamicallyDefinedLocalIdentifier service

page 34

7.5

writeDataByLocalIdentifier service

page 34

7.5. Message data bytes

page 34

7.6

writeDataByCommonIdentifier service

page 34

7.7

writeMemoryByAddress service

page 34

8 STORED DATA TRANSMISSION FUNCTIONAL UNIT

page 35

8.0

Introduction

page 35

8.

readDiagnosticTroubleCodes service

page 35

8.2

readDiagnosticTroubleCodesByStatus service

page 35

8.2. Message data bytes

page 35

8.2.2 Parameter Definitions

page 36

readStatusOfDiagnosticT roubleCodes service

page 40

8.3. Message data bytes

page 40

readFreezeFrameData service

page 4

8.4. Message data bytes

page 4

clearDiagnosticInformation service

page 42

8.5. Message data bytes

page 42

8.3 8.4 8.5

9 INPUT/OUTPUT CONTROL FUNCTIONAL UNIT

page 43

9.0

Introduction

page 43

9.

inputOutputControlByLocalIdentifier service

page 43

9.. Message data bytes

page 43

9..2 Parameter Definitions

page 44

inputOutputControlByCommonIdentifier service

page 47

9.2

REMOTE ACTIVATION OF ROUTINE FUNCTIONAL UNIT

page 48

0.0 Introduction

page 48

0. startRoutineByLocalIdentifier service

page 48

0..

Message data bytes

page 48

0..2

Parameter Definitions

page 49

0.2 startRoutineByAddress service

page 50

0.3 stopRoutineByLocalIdentifier service

page 50

0.3.

Message data bytes

page 50

0.4 stopRoutineByAddress service

page 50

0.5 requestRoutineResultsByLocalIdentifier service

page 5

0.5.

Message data bytes

page 5

0.5.2

Parameter Definitions

page 52

0.6 requestRoutineResultsByLocalAddress service

page 52 continued

PUBLISHED BY SATIZ  NORMAZIONE

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

continued

0

07223

Page

07223

4

Change

CONTENTS

continued 

UPLOAD DOWNLOAD FUNCTIONAL UNIT .0 Introduction

page 53

. requestDownload service

page 53

..

Message data bytes

page 53

..2

Parameter Definitions

page 54

.2 requestUpload service

page 54

.3 transferData service

page 55

.3.

Message data bytes

.4 requestTransferExit service .4. 2

page 53

page 56

Message data bytes

SCAN TOOL

page 56 page 57

2. 4. TECHNICAL REQUIREMENTS 2..

page 55

page 57

4..2.

Application timing parameter definition

page 57

2..2

4..4.

Data not available

page 57

2..3

4..4.3.2. Data not available within P2 timing

page 57

2.2 5. Diagnostic service definition

page 58

2.3 5..

Service $0  Request current powertrain diagnostic data

page 58

2.4 5.2.

Service $02  Request powertrain freeze frame data

page 58

2.5 5.3.

Service $03  Request emissionrelared diagnostic information

page 58

2.6 5.4.

Service $04  Clear/reset emission related powertrain diagnostic information page 58

2.7 5.5.

Service $05  Request oxygen sensor monitoring test result

page 58

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

2.8 5.6. Service $06  Request onboard monitoring test result for noncontinuosly monitored system page 58 2.9 5.7. Service $07  Request onboard monitoring test result for continuosly monitored system

page 58

2.0 5.8.

Service $08  Request control of onboard system, test or components

page 58

2. 5.9.

Service $09  Request vehicle information

page 58

Annex A PID (Parameter ID)/TID (Test ID)/INFOTYPE supported definition

page 59

Annex D (CCM) TIDs (Test ID) for servicce $08 scaling and definition

page 60

Annex E (CCM  TCM/CAE) INFOTYPEs for service $09 scaling and definition

page 6

Annex B (TCM/CAE) PIDs (Parameter ID) for service $0 scaling and definition

page 62

PUBLISHED BY SATIZ  NORMAZIONE

Page 5 Change

07223



SCOPE This document describes FIAT requirements for the implementation of the KWP 2000 communication protocol in FIAT products, defining the general rules; a document will be written for each application, containing the detailed description of each service. This document shall be named ““Specifica di Diagnosi Finalizzata SDF xxxx””. Said document will not contain the definition of the protocol toward the SCAN TOOL (ISO 42304). For security reasons some implementation parts will not be described in any document but will be given only to persons responsible for such operations. 2

REFERENCE STANDARDS 2.

ISO Standards |ISO 4230 |

Road Vehicles –– Diagnostic Systems  Keyword Protocol 2000 Part  : Physical Layer

|ISO 42302 |

Road Vehicles –– Diagnostic SystemsKeyword Protocol 2000 Part 2 : Data Link Layer, Error Handling

|ISO 42303 |

Road Vehicles –– Diagnostic Systems  Keyword Protocol 2000 Part  : Implementation

|ISO 942 |

CARB requirements for interchange of Digital Information

2.2 |FIAT 07234

|

General specifications for Selfdiagnosis

|SAE J 202

|

Diagnostic Trouble Code

|SAE J 286

|

E/E Diagnostic Data Link Security

|Keyword Protocol 2000 | Implementation of Diagnostic services, Recommended Practice  version .4, September 6, 997.

PUBLISHED BY SATIZ  NORMAZIONE

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

Other Standards

Page

07223

6

Change

3

DEFINITIONS AND ABBREVIATIONS 3.

Service identifiers

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

English

Italian

startCommunication

Inizio comunicazione

stopCommunication

Termine comunicazione

accessTimingParameter

Accesso ai parametri di comunicazione

startDiagnosticSession

Inizio sessione diagnostica

stopDiagnosticSession

Termine sessione diagnostica

securityAccess

Accesso alle procedure di sicurezza

testerPresent

Blocco di mantenimento comunicazione

readECUIdentification

Lettura codice identificativo ECU

readDataByLocalIdentifier

Lettura parametri

writeDataByLocalIdentifier

Scrittura parametri

readDiagnosticTroubleCodesByStatus

Lettura codici errori presenti in centralina raggruppati tramite il loro stato

readStatusOfDiagnosticT roubleCodes

Lettura parametri ambientali collegati ad un singolo errore

readFreezeFrameData

Lettura blocco informazioni catturate durante il rilevamento di anomalie rilevanti per le emissioni

clearDiagnosticInformation

Cancellazione memoria errori

inputOutputControlByLocalIdentifier

Operazioni effettuate su attuatori (attivazioni, tarature, etc.)

startRoutineByLocalIdentifier

Attivazione programma residente

stopRoutineByLocalIdentifier

Interruzione programma residente attivato in precedenza

requestRoutineResulByLocalIdentifier

Informazioni sullo stato programma (in esecuzione) attivato in precedenza

requestDownload

Richiesta di programmazione

transferData

Comando utilizzato per trasferire i dati da programmare

requestTransferExit

Richiesta chiusura procedura di programmazione

PUBLISHED BY SATIZ  NORMAZIONE

Page 7

07223

Change

4

COMMUNICATION 4.

Introduction The structure of the messages is described in the document ISO 42302; in the following paragraph are briefly described the possible formats and some limitations/differences with respect to the reference document.

Data bytes Fmt

SID

Checksum

Data

CS 1 byte

Checksum calculation

Header without address information, no additional lenght byte Data bytes Fmt

Len

SID

Checksum

Data

CS

Checksum calculation

1 byte

Header without address Information, additional length byte Data bytes Fmt

Tgt

Src

SID

Checksum

Data

CS 1 byte

Checksum calculation

Data bytes Fmt

Tgt

Src

Len

SID

Checksum

Data

CS 1 byte

Checksum calculation Header with address Information, additional length byte Fmt Tgt Src Len

Format byte Target address (optional) Source address (optional) additional length byte (optional)

SID Data CS

Service Identification Byte depending on service Checksum byte

The data field is described in this document. Shaded areas (header, checksum) are described in ””Keyword Protocol 2000  Part 2: Data Link Layer

N.B.: For the response block the ECU shall always use the same format sent by the Tester for the request block.

PUBLISHED BY SATIZ  NORMAZIONE

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

Header with address Information, no additional length byte

8

Page

07223

Change

4.2

Initialization The ECU shall accept both 5 Baud initialization and Fast Initialization.

5 Baud initialization Address (2s) 5 Baud

synchronisation pattern ””$55”” KB1 W1 60...300ms

W5 300 ms

W2 5...20ms

KB2

KB2

W3 W4 1...20ms 25..50ms 10400 Baud

Address

W4 25..50ms

After Initialization P3

Fast Initialization T

WuP

W5 300 ms

25ms

T * normal timing ** extended timing Client (tester) shall always support extended timing during fast initialization!

iniL

(50ms)

P2

25...50 ms* 0..1000ms** StartCommunication StartCommunication request positive response 10400 Baud

Client (Tester) Transmission

CONFIDENTIAL THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION

55...5000ms* 0...1000 ms** Service request

Server (ECU)Transmission

4.2.

Fast initialisation See Std. ISO 42302 4.2.2

5Bd initialization After receiving the 5baud address, the ECU transmits the synchronization sequence ““55H”” and two key bytes (*). The Tester shall transmit the complement of key byte 2 after which the ECU will transmit complement of the address. If the ECU doesn’’t get this byte correctly it shall stop communication and automatically reset for a new diagnostic session. After a waiting time w5 the Tester is allowed to retry initialization. (*) The baud rate used by both the E.C.U. and Tester shall be 0.4 Kb %.

PUBLISHED BY SATIZ  NORMAZIONE

Page 9

07223

Change

4.2.2.

Initialization timings diagram The initialization has the following timing diagram:

W5

Address W Syn W2

K

W3

K2

W4

K2 compl.

W4

Add. Compl.

 Time before initialization

: w5 > 300ms.

 Time between initialization and ISO code

: 60 ms