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

Data Byte Parameter Name 
Cvt 
Hex Value Mnemonic 
#1 
returnToNormalMode Positive Response Service Id 
M 
60 
SIDPR 
8.5.3.1 Positive Response Message Data Parameter Definition. 
There are no data parameters used by this 
service in the positive response message. 
8.5.4 Supported negative response codes (RC_). 
The following negative response codes (Table 77) shall 
be implemented for this service. The circumstances under which each response code would occur are 
documented in the table below. 
Table 77: ReturnToNormalMode Negative Response Codes 
Hex 
Description 
Cvt 
Mnemonic 
12 
SubFunctionNotSupported-InvalidFormat 
This code is returned if the request message format is incorrect (too many 
request message bytes). 
M 
SFNS-IF 
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 101 of 336 
8.5.5 ReturnToNormalMode Message Flow Example.
The following message flow example (Table 78) 
shows what happens when a tester transmits a $20 ReturnToNormalMode request while diagnostic periodic 
data is active ($AA service) and one-shot DTC information is being returned by the node in response to earlier 
tester requests. Since the DTC response messages are one-shot data, the node is able to continue sending 
the single shot UUDT frames after receiving the $20 request. Refer to the ReadDiagnosticInformation section 
for more details regarding the operation of service $A9. 
Since the information encapsulated in DPID $FE was scheduled, no further updates are received after the 
service $20 acknowledgement (although there is a residual message $FE response between the service $20 
request and positive acknowledgement. This is because the $FE DPID message was already in the protocol 
device at the time the $20 request was received). 
Refer to service $AA ReadDataByPacketIdentifier for more details regarding the operation of service $AA, and 
the Flash Programming section of this specification for more details about how mode $20 is used to end a 
programming session. 
The following assumptions are made in the example below: 
1. The tester had previously requested the node to report DTCs with a request for the $A9 service with a $81 
value in the sub-parameter field. The response to this request is in progress but has not completed at the 
time the $20 request is received. 
2. The tester had previously requested the node to transmit DPID $FE periodically. 
3. The node has loaded into the protocol device (but not yet sent) a periodic update of DPID $FE when it 
received the mode $20 request. 
4. The node has a USDT physical request CAN ID of $241. 
5. The node has a UUDT physical response CAN ID of $541. 
6. The node has a USDT physical response CAN ID of $641.