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

W
5 
= 
This DID may be written with service $3B at the discretion of the platform.
Position
1
2
3
4
5 ---
GMTV
2002 1
J
D
9 For 2002 Chevy Cavalier with LD9 engine
Hex value
66 31 4A 44 39 ---
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
Page 305
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
Table C20: Definition of GM Software Usage Description Data dataIdentifier
DID Description
R/W
Data Type
Len
$B7 
GM Software Usage Description (GMSUD)
R/W
6
USN/ASCII
5
This DID contains five bytes of data used to identify the intended usage of ECU development software.
The data is broken down as follows:
Byte 1 (Program Phase)
This byte is contains an ASCII value that represents the program phase that the software is target for
(e.g., B = Beta, G = Gamma, etc).
Byte 2 (Software Release Type/Calibration Release Type)
This byte is stored in USN format where the upper nibble represents the software release type and the
lower nibble represents the calibration release type. A value of $D = development, and $A = approved
for release by supplier.
Byte 3 (Software Release Number)
This byte is stored in USN format and represents the release number of the ECU software set. Software
revision numbers shall start at $01 and increment with each release.
Bytes 4 and 5 (PROM Identifier)
These two bytes are stored in USN format and are used to provide a unique representation of a
software version (e.g., 2000 NAO V6 PCM with level 2400 software = $09 $60).
W
6 
= 
This DID may be written with service $3B at the discretion of the platform.
Position
1
2
3
4
5 For Beta release with approved software and
GMSUD
B AA 2
2400
calibrations. 2
nd 
software release and software
Hex value
42 AA 02 09 60 revision level = 2400