[ Pobierz całość w formacie PDF ]
11.0
Introduction
This functional unit specifies negotiation services for data transfer as they have to be implemented by
the ECU and by the Tester.
11.1
requestDownload service
This service shall be used by the Tester to initialize data transfer from the Tester to the ECU (download).
After the ECU has received the request message requestDownload, it shall intiate all necessary actions
in order to receive the data before sending the positive response message.
11.1.1
Message data bytes
requestDownload Request Message
Data byte # Parameter Name Cvt Hex Value
#1 requestDownload Request service Id M 34
transferRequestP arameter = [
#2 memoryAddress (High Byte) M xx
#3 memoryAddress (Middle Byte) M xx
#4 memoryAddress (Low Byte) M xx
#5 dataFormatIdentifier M xx
#6 unCompressedMemorySize (High Byte) M xx
#7 unCompressedMemorySize (Middle Byte) M xx
#8 unCompressedMemorySize (Low Byte) M xx
]
requestDownload Positive Response Message
Data byte # Parameter Name Cvt Hex Value
#1 requestDownload Pos.Resp. Serv. Id M 74
#2 transferResponseP arameter = [ maxNumberOfBlockLength ] M xx
requestDownload Negative Response Message
Data byte # Parameter Name Cvt Hex Value
#1 negativeResponse service Id S 7F
#2 requestDownload Request service Id M 34
#3 M xx
responseCode = [ See § 5.2.2 - Parameter Definitions ]
PUBLISHED BY SATIZ - NORMAZIONE
CONFIDENTIAL
THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION
WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE
THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES
Page
53
07223
Change
11.1.2
Parameter Definitions
Formats supported for dataFormatIdentifier:
Hex Value Description Cvt
0x unCompressed M
1x Bosch Compression Method U
2x Hitachi Compression Method U
3x Marelli Compression Method U
4x Lucas Compression Method U
5x-Fx TBD U
x0 unEncrypted M
x1 Bosch Encrypting Method U
x2 Hitachi Encrypting Method U
x3 Marelli Encrypting Method U
x4 Lucas Encrypting Method U
x5-xF TBD U
11.2
requestUpload service
The service requestUpload is not used in the FIAT implementation of protocol KWP2000.
PUBLISHED BY SATIZ - NORMAZIONE
CONFIDENTIAL
THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION
WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE
THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES
Page 54
07223
Change
11.3
transferData service
This service shall be used by the Tester in order to transfer data to the ECU.
The FIAT KWP2000 on K-line does not implement data transfer in the opposite direction:
the positive response message transferData shall not contain any parameter.
11.3.1
Message data bytes
transferData Request Message
Data byte # Parameter Name Cvt Hex Value
#1 transferData Request service Id M 36
#2 TransferRequestParameter#1 U xx
: : : :
#n transferRequestP arameter#m U xx
transferData Positive Response Message
Data byte # Parameter Name Cvt Hex Value
#1 transferData Pos.Resp. Serv. Id M 76
transferData Negative Response Message
Data byte # Parameter Name Cvt Hex Value
#1 negativeResponse service Id S 7F
#2 transferData Request service Id M 36
#3 M xx
responseCode = [ See § 5.2.2 - Parameter Definitions ]
PUBLISHED BY SATIZ - NORMAZIONE
CONFIDENTIAL
THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION
WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE
THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES
Page
55
07223
Change
11.4
requestTransferExit service
11.4.1
Message data bytes
requestTransferExit Request Message
Data byte # Parameter Name Cvt Hex Value
#1 requestTransferExit Request service Id M 37
requestTransferExit Positive Response Message
Data byte # Parameter Name Cvt Hex Value
#1 requestTransferExit Pos.Resp. Serv. Id M 77
requestTransferExit Negative Response Message
Data byte # Parameter Name Cvt Hex Value
#1 negativeResponse service Id S 7F
#2 requestTransferExit Request service Id M 37
#3 M xx
responseCode = [ See § 5.2.2 - Parameter Definitions ]
PUBLISHED BY SATIZ - NORMAZIONE
CONFIDENTIAL
THE ONLY VALID REFERENCE IS THE ORIGINAL ITALIAN EDITION
WITHOUT PRIOR WRITTEN CONSENT BY FIAT AUTO S.P.A. IN CASE OF DISPUTE
THIS DOCUMENT MUST NOT BE REPRODUCED OR CIRCULATED TO THE THIRD PARTIES
Page 56
07223
Change
12
SCAN TOOL
This session describes the characteristics required by FIAT for ScanTool protocol improvement, based
on KWP 2000 (14230) on its own products; in particular this chapter details the differences compared
to Standard 15031 and gives other clarifications.
The FIAT applications structure has max two EOBD relevant control units (*), connected through K
line to ScanTool, engine control unit (CCM) and transmission control unit (TCU/CAE); the (*) Freeze-
Frame(FF) is only on CCM; in case of EOBD relevant errors found by TCU/CAE it will start the Mil
Request line and the CCM control unit will take on the FF data storage.
The chapters refer to Standard ISO 15031-5; f.e. 12.1 4 TECHNICAL REQUIREMENTS refer to Stan-
dard ISO 15031-5 chapter 4. TECHNICAL REQUIREMENTS
12.1
4. TECHNICAL REQUIREMENTS
12.1.1
4.1.2. Application timing parameter definition
12.1.1.1
4.1.2.2. Definition for ISO 14230-4
Parameter Minimum value Maximum value Description
ms. ms.
P2 k-line CCM 25 35 Start Response
CCM frame
P2 k-line TCU/CAE 36 50 Start Response
TCU/CAE frame
12.1.2
4.1.4. Data not available
12.1.2.1
4.1.4.1. ISO 14230-4 Data not available
In case of data not available or not supported, the CCM will give the correct NegativeResponse; the TCU/
CAE shall not consider the input in case of data not available or not supported.
12.1.3
4.1.4.3.2. ISO 14260-4 Data not available within P2 timing
If the data are not available within P2 Max timing, the ECUs shall respond with code 0x21 (busy-Repea-
[ Pobierz całość w formacie PDF ]