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

Note 2
xx
xx
xx
xx
DPIDREC
DPID
DPIDDB
:
DPIDDB
Note 1: C
3 
= The number of bytes in a DPIDRecord is determined by the definition of the DPID. DPIDs can range in length from one to
seven bytes.
Note 2: C
4 
= The number of DPIDRecords in the response is based on the number of DPIDs 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
79/298
Page 89
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 89 of 336
8.3.3.3 Positive Response Message Data Parameter Definition (Table 62).
Table 62: Response Message Data Parameter Definition
Definition
sub-function
This byte is an echo of the sub-function parameter from the request message.
FailureRecordDataStructureIdentifier
This data parameter is used to indicate whether or not the ECU stores failure records in a PID or DPID format.
A PID is a 2-byte value pre-assigned to a specific piece of ECU signal/parameter data (e.g., rpm or Coolant
temperature are pieces of signal/parameter data, and each would have a unique two byte value used to
identify it). The number of data bytes associated with a specific PID is fixed when the PID is defined.
A DPID is a 1- to 7-byte set of ECU signals/parameters packed into a UUDT message reported via the $AA
service. If an ECU stores failure records in a DPID format, then the order of the signals/parameters within the
failure record match the way they are defined when reporting the DPID.