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

Interpreter Execute. 
All steps required to program an ECU are contained in a utility file. Those steps do 
not need to be synchronized between multiple utility files running in parallel, therefore no 
master execute
is required during the execution of these steps. All steps controlled by the interpreter (interpreter execute) 
are ECU oriented steps (physically addressed to the ECU to be programmed). 
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 274 of 336 
GMLAN Programming Environment
Master Execute
Pre-Utility File Process
Interpreter Execute
(up to n Interpreters
running in parallel)
Interpreter Execute
(up to n Interpreters
running in parallel)
Utility File #1
Interpreter #1
Part #1 of
Utility File #1
Utility File #...
Interpreter #...
Part #1 of
Utility File #...
Utility File #n
Interpreter #n
Master Execute
Part #1 of
Utility File #n
Programming session conclusion (SW-reset)
- synchronized between all utility files running in parallel -
Optional
Part #2 of
Utility File #n
Optional
Part #2 of
Utility File #...
Optional
Part #2 of
Utility File #1
vehicle oriented
ECU oriented
part #1 of the
Utility File
vehicle oriented
ECU oriented
part #2 of the
Utility File
(optional)
Figure 39: Programming Procedure - Overview 
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 275 of 336 
9.4.3.1 Programming Setup (Pre-Utility File) Process. 
The following steps (Table 229) are performed prior 
to the execution of one or multiple utility file(s) to make sure that the GMLAN network (including all GMLAN 
sub-networks) transitions to the programming state (vehicle oriented step). In addition the Pre-Utility File 
process determines the CAN communication parameters (setup of the diagnostic configuration matrix). All 
steps of the pre-utility file process are functionally addressed to all nodes on the GMLAN sub-networks (except 
certain steps included in the verification process) and performed automatically. 
Table 229: Steps of the Pre-Utility File Process 
Step 
Action 
13 
Wake-up link(s) - 
High voltage wake-up for SWCAN 
- gateways may cascade wake-ups (where 
applicable) across to the other subnets on the vehicle or the tester may need to use 
level $04
of 
diagnostic service 
InitiateDiagnosticOperation ($10)
to generate the wake-up (functionally 
addressed to gateway ECUs only). 
Note:
the tester must allow at least 500ms after issuing a wake-
up before transmitting any diagnostic request message (including tester present) to allow the ECU to 
process the wake-up and transition to a communication active state 
– see section 6.1 for wake-up 
requirements. 
14 
Start sending 
TesterPresent ($3E)
periodic messages to all nodes - all links as needed (using the 
AllNodes CANId and AllNodes extended address). 
15 
Use service 
ReadDataByIdentifier ($1A)
to determine diagnostic addresses and CAN Identifiers for 
all ECU(s) (excluding SPS_TYPE_C) on each subnet (setup of base diagnostic configuration matrix, 
DID $B0
). 

This determines the relationship of each ECUs diagnostic address and its physical request and 
response CAN Identifiers. 

SPS_TYPE_C ECUs would not respond since diagnostic responses have not been enabled yet. 

This step and the ReportProgrammedState ($A2) service step later in the process allow the 
utility file to only contain the node diagnostic address. The tester correlates the diagnostic 
address to the physical request and response CAN Identifiers. 
16 
optional 
step 
Send a