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

Page 169
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
150/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 169 of 336
8. Prior to programming, increase/reduce the voltage level to a value where the device is not capable of
being programmed. Verify that the node sends back a $7F $36 $83 negative response to a request for this
service.
Procedure 4: 
Optional. These additional steps should be performed if $Level $80 is implemented.
1. Perform Procedure 1 and then send a mode $36 request with ONLY the $Level data byte (starting address
bytes missing), verify the node responds with $7F $36 $12.
2. Perform Procedure 1 and then send a mode $36 request with $Level $80 and an invalid starting address,
verify the node responds with $7F $36 $31.
3. Perform Procedure 1 and then send a mode $36 request with $Level $80, a valid starting address, and a
data block size that results in an invalid address. Verify that the node responds with $7F $36 $31.
Procedure 5: 
Optional. To be verified if the node requires a specific order in which software/calibration files
are downloaded.
1. Obtain an archive file or a utility file which will cause the software/calibration parts to be downloaded in an
order that is unacceptable to the boot software programming executive. Attempt to program the node using
a programming tool (e.g., DPS Tool or SPS Tool created by Service Operations). Verify that the
programming event fails as a result of a $7F $36 $22 response at the appropriate time.
Procedure 6: 
Optional - to be performed if the ECU supports negative response code $89
(DEVICE_TYPE_ERROR).
1. Obtain ECUs with each possible type of permanent memory device. Perform Procedure number 1 and
then download one of the allowed programming algorithms. Verify that the negative response $7F $36 $89
is sent if the algorithm downloaded was not the correct one for that permanent memory device. Verify that
the positive response is sent if the correct algorithm was downloaded.
2. Repeat step 1 of this procedure for each possible combination of programming algorithm and permanent
memory device.
Procedure 7: 
Optional. To be verified if the node requires data file compatibility checks.
1. Obtain an archive file that contains data files that are not compatible (either operational software not
compatible with the boot software or a calibration file that is not compatible with the operational software).
Attempt to program the node using a programming tool (e.g., DPS Tool or SPS Tool created by Service
Operations). Verify that the programming event fails as a result of a $7F $36 $85 response at the
appropriate time.