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

FailureRecordIdentifier
See request message data parameter definition section.
PIDRecord#
This parameter consists of a 2-byte PID value used to identify the PID data and the actual PID data itself (ECU
signal/parameter data). The number of data bytes in the record is dependant upon the PID being reported.
DPIDRecord#
This parameter consists of a 1-byte DPID number used to identify which signal/parameter data is being
reported and the actual ECU signal/parameter data itself. The number of data bytes in the record is dependant
upon the DPID being reported.
8.3.4 Supported Negative Response Codes (RC_). 
The following negative response codes shall be
implemented for this service. The circumstances under which each response code would occur are
documented in Table 63 below:
Table 63: Supported Negative Response Codes
Hex Description
Cvt Mnemonic
12
SubFunctionNotSupported-InvalidFormat
1. A readFailureRecordIdentifiers request message does not contain one data
byte following the service identifier.
2. A readFailureRecordParameters request message does not contain five data
bytes following the service identifier.
3. The request message contains a sub-parameter which is not supported.
M
SFNS-IF
22
ConditionsNotCorrectOrRequestSequenceError
This response code shall be used if internal conditions within the node (ECU)
prevent the reading of failure record information stored in the node (ECU).
C CNCORSE
31
RequestOutOfRange
A request for the parameters in a failure record contains a failure record
identifier (failure record number + DTC identifier) that does not correspond to a
single unique failure record or is not a valid failure record identifier for the node.
M
ROOR
78
RequestCorrectlyReceived-ResponsePending
See 7.2 Return Code Definition.
C
RCR-RP
Page 90

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
80/298