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

W
3 
=
Depending on the information being written, security may be required.
Position
1
2
3 …
OPTCODE
4293845
…
Hex Value
41 84 D5 …
Page 301
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
Table C13: Definition of ECU Diagnostic Address dataIdentifier
DID Description
R/W
Data Type
Len
$B0 
ECUDiagnosticAddress (ECUADDR
)
R/W
4
USN
1
This DID contains the diagnostic address of an ECU. This DID shall be supported by all ECUs when
executing operational software and by SPS_TYPE_B ECUs when executing boot software.
W
4 
= This DID is usually read only. An ECU may choose to allow this DID to be written when more than
one of a given hardware device can exist on a single vehicle. If this value is allowed to be written,

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
267/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 301 of 336
then both the operational software and the boot shall be capable of updating the value used.
Position
1 …
ECUADDR
17 ECM ECUDiagnosticAddress
Hex Value
11 …
Table C14: Definition of ECU Functional Systems and Virtual Devices dataIdentifier
DID Description
R/W
Data Type
Len
$B1 
ECUFunctionalSystemsAndVirtualDevices (ECUFSAVD)
R
USN
≥ 2
This DID contains the list of functional systems and virtual devices supported by the node (ECU). The
two lists are separated by a $FE separation character (AllNode functional system address). If an ECU
does not support any VD (because it does not support any VN) then it shall report a $00 following the
$FE to indicate that no VD is supported. The length of the DID depends on the number of supported
functional systems and virtual devices.
Position
1
2
3 …
ECUFSAVD
253 254 0 …
Hex Value
FD FE 00 The $FD functional system corresponds to gateway devices