Страница 1 мировой engineering стандарты общая спецификация

Note 2
xx
xx
xx
xx
xx
PIDREC
PIDHB
PIDLB
PIDDB
:
PIDDB
Note 1: C
1 
= The number of data bytes associated with the PIDRecord is determined by the definition of the PID.
Note 2: C
2 
= The number of PIDRecords in the response is based on the number of PIDs that the ECU records into the failure record each
time a failure record is stored.
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
78/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 87 of 336
Page 88
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 88 of 336
8.3.3.2.2 readFailureRecordParameters Positive Response Format Using DPIDs (Table 61).
Table 61: ReadFailureRecordData(readFailureRecordParameters) Positive Response Message with
DPIDs
Data Byte Parameter Name
Cvt Hex Value Mnemonic
#1
ReadFailureRecordDataPositiveResponse Service Id
M
$52
SIDPR
#2
sub-function = [
readFailureRecordParameters ]
M
$02
LEV_
RFRP
#3
#4
#5
#6
failureRecordIdentifier = [
failureRecordNumber
DTCHighByte
DTCLowByte
DTCFailureTypeByte ]
M
xx
xx
xx
xx
FRDTCIREC
FRN
DTCHB
DTCLB
DTCFT
#7
#8
:
:
DPIDRecord#1 = [
DPID
DPIDDataByte#1
:
DPIDDataByte#m]
M
M
:
C
3
Note 1
xx
xx
xx
xx
DPIDREC
DPID
DPIDDB
:
DPIDDB
:
:
:
:
:
:
:
:
#n
DPIDRecord#k = [
DPID
DPIDDataByte#1
:
DPIDDataByte#m]
C
4