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

Table 228: Steps of the Retrieve SPS Data Process Programming Session
Step Action
11
Connect tester to SPS database.
•
Select node(s) to be programmed.
•
If node replacement, identify information (if necessary) to be retrieved from the old ECU to transfer
to the new ECU 
Note 1
.
•
Generate security key(s).
•
Retrieve SW/CAL Modules to download.
12
Reconnect tester.
Note 1: 
For remote programming, where an ECU is replaced and requires data read from the old ECU and written into the replacement
ECU the technician must connect to the SPS database twice. The first time is to identify which data must be read from the old ECU, the
second time is to generate the key for the replacement ECU and to retrieve the software/calibration file(s) to be downloaded.
9.4.3 Programming Session. 
(Figure 39) The Programming Session consists of two distinct types of
diagnostic service executions:
1. 
Master Execute. 
All steps required to start a programming event and all steps required to be synchronized
between multiple utility files running in parallel are executed only once (master execute). Those steps are
the ones defined for the 
Pre-Utility File Process 
and the synchronization between the utility file at the
point in time when the utility file reaches the point where a SW-reset of the physical ECU is required to
finalize the programming of this node (conclusion of the programming event). All steps controlled by the
master execute are vehicle oriented steps (functionally addressed to all nodes).
2. 
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).