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

8.16.7 Node Verification Procedure. 
Procedure 1: 
(For Devices which have stored their permanent diagnostic CAN Identifiers.) 
1. Send a ReportProgrammedState request with invalid additional data bytes and verify the proper negative 
response reject message is sent ($7F $A2 $12). 
2. Send a ReportProgrammedState request at a time when the device cannot process this request within P2
C
(programmedState calculation not done) and verify the proper negative response (This is only required for 
devices which support such a situation.) followed by the proper positive response within P2
C
*. 
Procedure 2: 
(For Devices which have stored their permanent diagnostic CAN Identifiers.)
 
1. Send a request for this service to the ECU when it is fully programmed and verify the proper response. 
2. Send a request for this service to the ECU when it only has boot software present and verify the proper 
response. 
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 185 of 336 
3. Send a request for this service to the ECU when it has boot software and operational software present 
(no calibration data) and verify the proper response. 
4. Obtain a controller with default calibrations programmed in (only applicable if the ECU supports $A2 
response $03). Send a request for this service and verify that the ECU sends the $E2 $03 response. 
5. Create situations for each of the memory failure response codes that the ECU supports and verify the 
proper response. 
Procedure 3: 
(For SPS_TYPE_C ECUs when operating out of boot software.)
 
1. Send a request for each diagnostic service supported in the ECU (except services $28 and $A2) and 
verify that no response is sent. 
2. Send an all nodes request for service $28 and verify no response. Wait for a positive response from all 
ECUs (that have stored permanent diagnostic CAN Identifiers) and then send a request for $A2 service. 
Verify that a positive response is sent using the ECU
’s SPS_PrimeRsp CANId ($3xx). 
3. Repeat step 2 for each valid positive response value (programmedState) supported by the ECU when 
running out of boot, and verify the proper positive responses for each case. 
4. Send an all nodes request for service $28 and then repeat step 2 of Procedure 1 (if applicable). 
5. Repeat step 2 of this procedure. Send TesterPresent $3E messages at least once every P3
C
ms while 
requesting the other supported diagnostic services with the SPS_PrimeReq CANId ($0xx). Verify that the 
ECU continues to respond properly using the SPS_PrimeRsp CANId ($3xx). Stop sending TesterPresent 
($3E) messages and wait P3
Cmax
ms. Verify that the ECU no longer responds to diagnostic requests.