GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 69 of 336
Tester
ECU
FlowControl
frame with
FS=0, BS = 0, STmin = 5
FirstFrame
FirstFrame
FlowControl
ConsecutiveFrame
ConsecutiveFrame
ConsecutiveFrame
ConsecutiveFrame
ConsecutiveFrame
Request
ConsecutiveFrame
ConsecutiveFrame
ConsecutiveFrame
ConsecutiveFrame
:
:
only one
FlowControl
following the
FirstFrame
all ConsecutiveFrames
are sent in a row
separated by STmin
5 ms
5 ms
5 ms
ConsecutiveFrame
Figure 32: ECU Requirements for Multi-Frame Request Messages - Example Message Flow
Table 39: USDT Request Message Flow Example
T = Frame Sent By Tester; N = Frame Sent By Node; shaded region indicates PCI
T(USDT-
FF
)
241
10
24
3B
45
01
02
03
04
N(USDT-
FC
)
641
30
00
05
---
---
---
---
---
T(USDT-
CF
)
241
21
05
06
07
08
09
0A
0B
T(USDT-
CF
)
241
22
0C
0D
0E
0F
10
11
12
T(USDT-
CF
)
241
23
13
14
15
16
17
18
19
T(USDT-
CF
)
241
24
1A
1B
1C
1D
1E
1F
20
T(USDT-
CF
)
241
25
21
22
---
---
---
---
---
7 Negative Response ($7F) Service Definition
The negative response service shall be used by an ECU to indicate that a diagnostic service request message
is either invalid, being terminated, or currently cannot be acted upon at the time of the request. Included in the
negative response message is a return code to indicate to the tool the reason the negative response message
was sent. This service shall use the USDT response CAN Identifier when transmitted on the link.
CameraLoops.com
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 70 of 336
7.1 Negative Response Message Format (Table 40).
Table 40: Negative Response Message Format
Data Byte
Parameter Name
Cvt
Note 1
Hex Value Mnemonic
#1
Negative
Response Service Identifier
M
7F
SIDNR
#2
requestServiceId
M
xx
SIDRQ
#3
returnCode
M
xx
RC_
#4
deviceControlLimitExceeded = [ExceededLimitMsb
C
xx
DCLEH
#5
ExceededLimitLsb]
C
xx
DCLEL
Note 1:
C
= Conditional:
If returnCode
= $E3 then the deviceControlLimitExceeded parameter is appended.
7.2 Return Code Definition.
The following subsections specify the definition of each return code. Each
GMLAN Enhanced Diagnostic Service includes a subsection which lists the return code(s) supported by the
service. All values which are currently not used as return codes are reserved
by this document for future
expansion as necessary.
7.2.1 ServiceNotSupported ($11, RC_SNS).
This response code indicates that the requested action will not
be taken because the ECU does not support the requested service. This return code is only valid for physically
addressed diagnostic requests.
Example:
The ECU shall send this response code if the tester sends a physically addressed request message
with a service Identifier which is either unknown or not supported by the ECU. If a tester sends a valid
functionally addressed diagnostic request for a service that is not supported by the ECU, then the ECU shall
ignore the request (no response shall be sent). Refer to the
Diag_API_Process_Recv_Msg()
function in the
pseudo code of the ReportProgrammedState service ($A2) for implementation details on this response code.
7.2.2 SubFunctionNotSupported-InvalidFormat ($12, RC_SFNS_IF).
This response code indicates that the
requested action will not be taken because the ECU does not support the arguments of the request message
or the format of the argument bytes do not match the prescribed format for the specified service.
Example:
The ECU shall send this response code in case the tester has sent
a request message with a
known and supported service Identifier but with
sub-function parameters
which are either unknown or not
supported or have an invalid format.
Do'stlaringiz bilan baham: