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

Table 229: Steps of the Pre-Utility File Process
Step Action

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
244/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 275 of 336
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