General Specification Electrical Function gmw3110 General Motors Local Area Network Enhanced Diagnostic Test Mode Specification

8.17.7.1 General Verification Procedures (any node, any link). 
Procedure 1: 
(Perform this procedure when conditions would allow a programming event).
 
1. Disable normal communication, send a requestProgrammingMode message ($A5 $01). Verify the positive 
response ($E5) message. 
2. Send an enableProgrammingMode request ($A5 $03). Verify no response is sent. 
3. Wait at least 100ms (but less than P3
C
ms), send a request for a supported mode (e.g., Mode $34 
RequestDownload). Verify the proper response. 
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 192 of 336 
4. Keep the device in enableProgrammingMode for at least 2 minutes by sending TesterPresent (mode $3E) 
messages at an interval less than P3
C
ms. Verify that no normal communication messages are 
transmitted. 
5. Verify that the device communicates in Programming Mode by periodically sending valid request 
messages. 
6. If the device is programmable, verify that the device is capable of being programmed using a released 
utility file and the correct interpreter software. 
7. Repeat the first 4 steps of this procedure and then send a ReturnToNormalMode ($20) message. Verify 
that the ECU performs a software reset. 
8. Repeat the above procedure except end the programming event by allowing a P3
C
(TesterPresent) timeout 
to occur (instead of sending a mode $20 request). Verify that the ECU performs a software reset. 
Procedure 2: 
1. Disable normal communication then send a requestProgrammingMode message ($A5 $01) with extra data 
bytes. Verify the negative response ($7F $A5 $12) message. 
2. Disable normal communication then send a message with no sub-function parameter byte after the service 
Id. Verify the negative response ($7F $A5 $12) message. 
3. Disable normal communication then send a message with an invalid sub-function parameter byte after the 
service Id. Verify the negative response ($7F $A5 $12) message. 
4. Send requestProgrammingMode message ($A5 $01) without disabling normal communication. Verify the 
negative response ($7F $A5 $22) message. 
5. If applicable, create conditions under which the node should not allow a programming event to take place. 
Then send a requestProgrammingMode message ($A5 $01). Verify the negative response ($7F $A5 $22) 
message. 
6. Send 
a 
request 
to 
enableProgrammingMode 
($03) 
without 
having 
previously 
sent 
a 
requestProgrammingMode ($01) request. Verify the negative response ($7F $A5 $22) message. 
7. Disable normal communication, send a requestProgrammingMode message ($A5 $01). Verify the positive 
response ($E5) message. Send a ReturnToNormalMode ($20) request message and verify the positive 
response. Then send a request to enableProgrammingMode ($03) and verify the negative response ($7F 
$A5 $22) message. 
8. Disable normal communication, send a requestProgrammingMode message ($A5 $01). Verify the positive 
response ($E5) message. Allow a P3
C
timeout to occur and then send a request to 
enableProgrammingMode ($03) and verify the negative response ($7F $A5 $22) message. 
9. Repeat steps 1 and 2 of Procedure 1 above. Then send a request for this service with a supported sub-
parameter. Verify the proper negative response (7F $A5 $22) and that there is no impact to the current 
programming event. Repeat this procedure for each supported sub-parameter of this service. 
10. Repeat steps 1 and 2 of Procedure 1 above. Then send a request for this service with an unsupported 
sub-parameter. Verify the proper negative response (7F $A5 $22) and that there is no impact to the 
current programming event.