www.bmwcoders.

com
 
 
Vehicle programming
 

Guide to action
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Guide to action
 

Programming with SG-D system

 
 
 
 
 
 
 
 
 
 
 

 
 
 

 
 
 
Project: Vehicle programming
Authors: Wolfgang Schühle,
Tobias Thiemann ESG,
ESG
Revision: 1.6
Valid from: E-Sys 3:12
Date: 11/18/2009
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Contents
 
A Einleitung4
 
1.1 Änderungsdokumentation4
 
2.1 Vertraulichkeit4
 
1.3 Purpose of Dokuments5
 
4.1 Referenzen5
 
1.5 Abkürzungen5
 
1.6 Abbildungsverzeichnis7
 
2 Grundlagen9
 
2.1 Programmierablauf9
 
2.2 Konfiguration9
 
2.2.1 Program 9
 
2.2.2 System Data / Fingerprint 10
 
2.2.3 FSC 11
 
2.2.4 Options 12
 
2.2.5 Connections 13
 
2.2.6 External Applications 14
 
2.2.7 EST 15
 
ODX 2.2.8 15
 
3 Creating a PDX-container components 17
 
3.1 Charging of PDX-Templates17
 
3.2 Adding the SG-software17
 
3.3 Inserting and BLUP-/FLUP-Dateien BLUMap18
 
4.3 Inserting Benutzerdokumenten20
 
5.3 Activation Code for EraseMemory21
 
3.6 definition of Programmierreihenfolge21
 
7.3 Saving the Komponentencontainers22
 
08.03 ODX Checker23
 
3.9 Import of components into the container PSdZ24
 
3:10 Containerupdate24
 
4 Creation of TAL26
 
4.1 Manual creation of the TAL TAL Editor26
 
4.2 Automatic TAL Berechnung28
 
4.3 generation of TAL in PDX Charger28
 
4.4 Creating a TAL BLUP/FLUP29
 
4.4.1 Automatic calculation module in the "local loop calculation" 29

  Seite 2 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
4.4.2 Automatic calculation of the PDX-Charger 29
 
4.4.3 Manual creation of the TAL 29
 
5 Verbindungsaufbau32
 
5.1 Selection of TargetSelectors32
 
5.1.1 Connection via Gateway 32
 
5.1.2 Direct connection 33
 
5.2 Selection of the physical Interface33
 
5.2.1 Connection via Ethernet 33
 
Connection via gateway URL 34
 
Connection on chassis number (VIN) 34
 
5.2.2 Connection via CANCard 34
 
5.2.3 Connection via Omitec 35
 
5.2.4 Connection via radio 36
 
5.3 Test of Verbindung36
 
6 TAL Abarbeitung38
 
7 Special Features Übernahmesteuergeräten40
 
1.7 Mapping40
 
7.2 AIFContents41
 
8 Individualdatenrettung42
 
1.8 IDRlight42
 
8.1.1 IDBackup 42
 
Automatic calculation of the TAL 42
 
Manual creation of the TAL 42
 
Reading and storing of individual data 43
 
8.1.2 IDRestore 43
 
Automatic calculation of TAL 43
 
Manual creation of the TAL 43
 
Restore the individual data 44

  Seite 3 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

1Introduction
 
 
1.1 Amendment documentation
 
 
Revision Date Description Author
 
0.107.12.06Erstanlage the document Wolfgang Schühle, ESG
 
1.011.01.07Dokument completely revised Tobias Thiemann, ESG, ES-71
 
1.102.02.07Beschreibung of the component name in 3.4 ergänztTobias Thiemann, ESG, ES-71
 
1.204.05.07Kapitel 7 "transfer-ECU" is added Tobias Thiemann, ESG, ES-71
 
  Switching to e-Sys 3.0  
2.022.05.07 Tobias Thiemann, ESG, ES-71
Chapter 2, 5 and 6 revised
 
  Restructuring of Chapter 4  
2.119.07.07 Tobias Thiemann, ESG, ES-71
Reconstruction of the sections 4.2 and
4.3
 
   
  Switching to e-Sys 1.3  
3.011.09.07 New system of Section 3.4 Tobias Thiemann, ESG, ES-71
Sections 4.3 and 5.2.1 changed
 
3.113.12.07Kleinere adjustments to E-Sys 3.3.1Tobias Thiemann, ESG, ES-71
 
  Switching to e-Sys 3.3  
4.020.12.07 Tobias Thiemann, ESG, ES-71
Section 3.4 completely revised
 
  Switching to e-Sys 4.3  
5.025.03.08 Tobias Thiemann, ESG, FZ-620
Section 2.2 and adds revised
 
   
  Switching to e-Sys 3.5  
5.123.04.08 Section 3.6 is new Tobias Thiemann, ESG, FZ-620
Section 4.3 revised
 
5.212.06.08Wechsel to e-Sys 3.6Tobias Thiemann, ESG, FZ-620
 
   
  Switching to e-Sys 7.3  
5.307.08.08 Section 3.3 is new Tobias Thiemann, ESG, FZ-620
Section 4.4 is new
 
3.4 5.405.09.08Abschnitt newly created tobias Thiemann, ESG, FZ-620
 
  License Note added in Section 3.8  
5.504.11.08 Tobias Thiemann, ESG, FZ-620
Note the layout boxes changed
 
5.610.12.08Kapitel eight newly created Tobias Thiemann, ESG, FZ-242
 
   
  Switching to e-Sys 3:10  
6.005.06.09 Section 2.2 updated Tobias Thiemann, ESG, FZ-242
Chapter 5 for complete elimination of the B2V revised
 
   
  Switching to e-Sys 3:12  
6.118.11.09 Some screenshots adapted Tobias Thiemann, ESG
Section 5.2.2 revised
 
 
2.1 Confidentiality
 
 
This document is only available for inspection by persons determined directly involved in the project. A
Transmission, particularly to contractors outside of the BMW Group, with the respective

  Seite 4 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Project managers coordinate and depends on the rules of confidentiality in
Development
agreement.
 
 
1.3 Purpose of the
document
 
 
This document describes the process of programming with E-SG system. It is assumed that even a valid
software units (Swen) with a current version of the SWE-generator were produced. Dealing with the SWE-
generator is described in [SWEGEN].
 
 
1.4 References
 
 
Reference Version Date Description Author

[SWEGEN] 1.0 11/28/2006 Guide to action SWE-generator Patrick Wagner, ESG

 
GIS on the "BMW Standard Tools Development /
standard tools / generators and file templates /
SWE-generator (L6) / application"

[LH_FP_SWL] 9 04/18/2008 LH "Part 2 FP logistics software," 10000967 - 000-09 Dr. Olaf Kluge, BMW
 
Available in SAP

[FA_GEN] 4 07/02/2009 FA-generator Markus Wolf, BMW

 
GIS on the "BMW Standard Tools Development /
standard tools / generators and file templates / FA-
generator (L6) / application"

 
 
 
1.5 Abbreviations
 
 
Abbreviation Significance
   

CAF Coding Application File

   

E-Sys New programming system for the e-portfolio

FA Vehicle Order
   

FP Vehicle profile

FSC Unlock code

   

GIS Global Information Services

   

GUI Graphical User Interface

KIFA Areas: body, interior, chassis, drive train

   

HIS Compatibility and Information System

LAN Local Area Network

   

ODX Open Diagnostic Data Exchange

  Seite 5 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Abbreviation Significance
   

PDX Packed ODX

   

PSdZ Programming system of the future

   

SG Control unit

SG-ID ECU Identifier

   

SGBM ECU description model

   

SGBM ID ECU description model identifier

   

SWLdZ Software Logistics for the Future

   

SREC Motorola SREC format

SVK ECU ID shoring

   

SVT (actual) Shoring system programming table of actual condition

   

SVT (target) Table of shoring system programming reference state

   

SWE Software unit

   

TAL Transaction List

VCM Vehicle Configuration Management

   

VIN Vehicle Identification Number (VIN)

  Seite 6 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
 
1.6 List of Figures
 
 
Figure 1: Mask
 
Figure 2: Settings for encoding and fingerprint .......................................... ..................................... 11
 
Figure 3: Settings for unlock codes ............................................ .................................................. .12
 
Figure 4: Other Options
 
Figure 5: Connection settings
 
Figure 6: Settings for external applications ........................................... ........................................... 14
 
Figure 7: Settings for developers Softtoken ............................................ ............................................. 15
 
Figure 8: Settings for ODX
 
Figure 9: PDX PDX Charger with open template ....................................... ...................................... 17
 
Figure 10: Adding a BLUPs for container components .......................................... .................. 18
 
Figure 11: Adding a file to PDX BLUMap container ...................................... ....................... 19
 
Figure 12: Display of the PDX-BLUMap Charger ........................................ ............................................. 19
 
Figure 13: Adding user documentation for PDX-container ........................................ ....... 20
 
Figure 14: User documentation in PDX containers .......................................... .................................. 20
 
Figure 15: Construction of an ECUVariantPattern below the SG-version ....................................... ............ 21
 
Figure 16: SWESEQ-editor with open SWESEQ file ....................................... ............................... 22
 
Figure 17: Reports on
 
Figure 18: Excerpt from the File Explorer to import the ODX data ................................... .............. 24
 
Figure 19: Update of the PDX-container
 
Figure 20: Adding a new transaction ........................................... ............................................. 26
 
Figure 21: TAL Editor ....................................... mask with open TAL ................................................ 27
 
Figure 22: Calculation of the TAL from SVT SVT actual and target .................................... ................................... 28
 
Figure 23: TAL / SVT production from a SG variant ..................................... ....................................... 29
 
Figure 24: Adding a BlFlash transaction .......................................... 30 ............................................
 
Figure 25: Delete the given entry BLFlashTA ......................................... ............................ 30
 
Figure 26: Adding a BLFlashTA ........................................ based on a file .......................... 31
 
Figure 27: TAL-line with
 
Figure 28: Button to open the connection dialog .......................................... ................................... 32
 
Figure 29: Connection dialog e-Sys
 
Figure 30: Possible Targetselektoren for connection through ZGW ........................................ .............. 33
 
Figure 31: Possible Targetselektoren for direct ECU connection ....................................... ............ 33
 
Figure 32: Establishing a connection via gateway URL ........................................ ................................... 34
 
Figure 33: Establishing a connection via chassis number (VIN) ....................................... .................. 34
 
Figure 34: Example of allocation of "PRODIAS CAN Driver CAN 1/2" .................................. ......................... 35
 
Figure 35: Structure of a direct CAN connection through FA-CAN ..................................... 35 ........................
 
Figure 36: Settings for connection Omitec interface ........................................ ..................... 36
 
Figure 37: Settings for connection via radio interface ........................................ ........................... 36
 
Figure 38: Read SVK

  Seite 7 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Figure 39: TAL-processing
 
Figure 40: TAL-matrix for optimizing the selection of transactions ....................................... ....................... 39
 
Figure 41: Container with mapping files for AMP_TOP and MULF_Basis ...................................... 40 ......
 
Figure 42: TAL for MULF_Basis with AifContents .......................................... ............................................. 41
 
Figure 43: Settings for IDRestore the TAL calculation ....................................... ....................... 43
 
Figure 44: Manually created for TAL IDRestore .......................................... ................................................ 44

  Seite 8 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

2Grundlagen
 
 
2.1 Programming sequence
 
 
To program a device with e-tax system following individual steps:
 

• Creating a PDX-container components

Charging the PDX-templates
Creation of SG variants and add the SG software (bootloader, program, data, coding) in the
form of Swen
 

Adding configuration files (mapping, SWE-order ...)

Storage of the container components
2) Import the components into the container PSdZ.
 
3) Creating a Transaction List (TAL), in which the programming system to be implemented
Actions are specified by the user
 
4) Establishing a connection to the controller
 
5) processing of the TAL (programming of the data to the ECU) The
implementation of these steps is the subject of this document.

 
2.2 Configuration
 
All programs and user settings in the menu "Options Settings are changed. " System of specific
information in the file
 

• ESYS_INSTALL \ config \ Esys.properties

stored user-specific settings are
 

• C: \ Documents and Settings \ <user> \ Esys \ EsysUser.properties

saved. The most important settings are explained in more detail below again.
 
 
2.2.1 Program
 
General settings are on the card "program" (see Figure 1), the following
Settings can be made:
• "Directory": Here, the path for the data directory specified by the e-system data structure is
created. This directory is referred to as ESYS_DATA. In
the directory ESYS_DATA / psdzdata later imported to the PDX-container.
 

• "Footprint": Sets the maximum memory for E-system (or the Java Virtual Machine)
fixed. The value must not exceed the physical memory!
 

• "Language": Turns the E-system interface between German and English to.
• "Logging": Specifies the settings for the logging of e-system fixed. The log files are
automatically at startup of e-system directory ESYS_DATA / logs after the pattern
E-Sys_yyyymmdd_hhmmss.log generated. Old log files can be deleted by selecting the
checkbox at the start of each e-Sys.

  Seite 9 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 1: Mask for program settings
 
 
2.2.2 System Data / Fingerprint
 
On the tab "System Data" (see Figure 2), the settings for encoding and fingerprint can be configured. The
fingerprint contains the date and information programming to the programming system, which are written in
programming in the controller and stored there. It is composed as follows:
• Byte 1-3: Current system date.
• Byte 4, bit 7 .4: Length of the fingerprints, always 0x8 (long finger print).
• Byte 4, bit 3 .0 "testers use code" adjustment in accordance with system data.
• Byte 5-6: "PlantID / DealerID / SystemSupplierNr" depending on the tester application identifier.
• Byte 7: "programming model", always 0x01.
• Byte 8-11: "Programming Device Serial Number" adjustment in accordance with system data.
• Byte 12-13: Mileage, always 0x00 00th
Moving the cursor over one of the input fields a tooltip will appear with the objective for the field
Values.
 
The "ignoreErrors" increases the fault tolerance of the system in preparation for programming, there is
continued despite negative responses or failure to SG with the programming, if possible.
 
Achtung: Is "ignoreErrors" enabled, may also be faulty controller are programmed
successfully.

  Seite 10 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 2: Settings for encoding and fingerprint
 
 
2.2.3 FSC
 
In the tab "FSC" (see Figure 3) controls for the handling of access codes are set. If "verify" is activated,
the activation code used to load and save are checked for validity.
Some campaigns also an FSC certificate is required, the box in the "FSC" actions can be specified.
"Periodic inspection" ensures that carried out some additional actions the status of FSC in the FSC-control
device.

  Seite 11 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 3: Settings for unlock codes
 
 
2.2.4 Options
 
On the tab "Options" (see Figure 4), the following settings:
• "Message to abort ..." Determines whether to abort an action after a message is
displayed.
• "Query on leaving ..." Determines whether to be performed when leaving a module with an
unsaved file is a security check.
• "VCM upgrade for TAL-processing": Determines whether the VCM (Vehicle Configuration
Modules) to the TAL-processing will be updated automatically. This is after programming FA, FP,
I-Level and SVT in the VCM module and FA-I and stage in the VCM-written backup. If no
controller with VCM or VCM backup module installed, it comes with VCM update to a timeout
error.
• "Prior to the TAL-generation ..." Determines whether to display in the TAL in the PDX-generation
Charger dialogue with functional limitations.
• "Swen availability check ..." Determines whether the availability of all the materials to be tested
in the TAL TAL SWEN before the execution. Is not one of the SWEN in the TAL are available
which TAL execution with an appropriate error message is canceled.
• "Update on MSM TAL execution": Determines whether the MSM (Master Security Module)
will be updated automatically after execution of the TAL. It will be processed according to the TAL
transport key for all CSM-control devices (Client Security Module) is transmitted to the MSM (in
CGW) and triggered their further distribution in the electrical system. To which control devices are
considered for the update is determined beforehand from the SVT in the VCM.
• "Show message after building up a connection": Determines whether a successful
Connection is confirmed by an info dialog or not.

  Seite 12 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 4: Other Options

 
With the radio buttons in the box "E-mode system" can e-systems between the car and the motorcycle-mode
can be switched. The functionality is then tailored to the selected mode.
 
 
2.2.5 Connections
 
In the tab "Connections" (see Figure 5), an additional transmission timeout can be specified, which adds to
the normal service time-out is taken into account and thus the transmission time of a diagnostic service
between tester and ECU. The maximum value for this timeout is 1000ms.
In addition, special settings for connections over radio and ICOM are specified.

  Seite 13 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 5: Connection settings

 
 
2.2.6 External Applications
 
In the tab "External Applications" (see Figure 6) to an external editor, a browser and the path of the SWE-
generator can be adjusted to suitable file formats from e-system to open out in the specified applications.

 
Figure 6: Settings for external applications

  Seite 14 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
2.2.7 EST
 
In the tab "EST" (see Figure 7) the location of the developer soft token (EST) specifies what is required to
encode a functional data list (FDL).

 
Figure 7: Settings for developers Softtoken
 
 
ODX 2.2.8
 
In the tab "ODX" (see Figure 8) and then to "ODX control path" of the location of the ODX Checker rules are
specified, the ODX Checker module uses the PDX-Charger to the structure of an ODX To check PDX-
Containers/-Templates. From e-sys 3.4.0 is here by default when you install the directory C: entered \ Data \
Rules, in which the rules of the E-system installation will be copied.
Under "Component documentation", the maximum size of the additional documents may be drawn that
can be inserted into the PDX-container (see section 3.4).

  Seite 15 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 8: Settings for ODX

  Seite 16 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
3Erstellung a PDX-component container
 
The following chapter describes the creation of a PDX-container components is described based on a
template and its PDX-import into the PSdZ.
 
 
3.1 Charging of PDX-templates
 
To create a component container, you must first template in the current PDX-module data handling →PDX-
Charger to be loaded. The current templates for the various series can be found on the GIS under
 
BMW Standard Tools Entwicklung
 

Standard Tools/Programmierung/E-Sys/ PDX templates

 
 
3.2 Adding the SG software
 
 
In the folder structure of the PDX-templates, you can now create the context menu by clicking the right
mouse button on the element PDX-container new SG variants. Each new SG-variant must first be assigned
to a base variant. This is done by selecting the desired base version from the drop down box of the same
element. For each variant SG Any name can be forgiven, however, may not be identical to that of a base
variant.

 
Figure 9: PDX PDX Charger with open template
 
Finally, below the base variant of the respective software units by right clicking on the
Element SWE and selection are supplemented by adding. The corresponding SWE files

  Seite 17 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
then be selected via a file dialog. The SWEN be entered in the BSW format in the template. You will be
automatically extracted and processed during the import.
The data required for coding Coding Application Files (CAF) will not be suspended for the SG-version, but
below the CAF element in the template. They are therefore not assigned to SG version. The same is true for
describing the SVT files that contain the desired state of the component. You can add the element of SVT. All
other configuration files, such as the
Mapping files for the takeover or control devices SWESEQ file (see 3.6) to control the
Programming sequence will be inserted below the Config element.
 
 
3.3 Inserting and BLUP-/FLUP-Dateien BLUMap
 
 
Bootloader updater process classes BLUP / FLUP be similarly added to the traditional boot loader SWEN
the process class BTLD together with other software units below SWE in the ECU variant (see labeling in
Figure 10). The selection of the files is done as usual in a file dialog.

 
Figure 10: Adding a component to the container BLUPs
 
Includes an ECU version (in our example, EVAL S12X) at least one of the SWE process class or FLUP
BLUP can be added using the context menu of the basic variant of the corresponding BLUMap file (see
Figure 11).
The selection of BLUMap file is again using a file dialog. After selection, the name for the file BLUMap be
changed. The naming convention for files is BLUMap blumap_ <Basisvarianten-Name> _ <EE-
Komponenten-Name>. Xml.
BLUMap was added to the container file, the file appears in the tree structure of the PDX-
Chargers below config / blumaps, not below the ECU variant (see labeling in Figure
12). That for an ECU variant BLUMap was deposited in the container, can be recognized by the node
"Bootloader Map: yes" below the ECU variant (see red circle in Figure 12).

  Seite 18 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 11: Adding a file to PDX BLUMap container

 
During the import of container, the PDX-BLUP / FLUP-SWEN directory psdzdata \ swe \ blup or psdzdata \
swe \ flup which BLUMap directory psdzdata \ main series \ <BRV> \ <Project> \ mapping \ blumaps
stored.

 
Figure 12: Display of BLUMap in PDX-Charger

  Seite 19 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
4.3 Insert user documents
 
 
With the addition of user documents the developer the opportunity to also ODX-party content via the
component container has to be redistributed (TAL, manuals, etc.). Added to the document via the
context menu of the node DOC (see Figure 13).

 
Figure 13: Adding user documentation for PDX-container
 
The added files are stored in containers in a ZIP archive named
<compName> _Doku.zip Saved and PDX-Charger DOC listed below (see Figure 14).

 
Figure 14: User documentation in PDX-container
 
The maximum size of the ZIP archive is limited to 1MB by default, but can in Options →
Settings →ODX be adjusted.

  Seite 20 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
5.3 Activation Code for EraseMemory
 
 
The activation code is an additional parameter of the diagnostic service EraseMemory, it serves to protect
the controller from being accidentally erased the memory. SC controllers use the activation code, which is
why it is enabled by default for each new SG variant. If it is not supported by a control device, it must be
switched off in the corresponding SG variant. These specify the boot loader ID, or address the diagnosis is
necessary to identify the particular variant in the ECU programming unique (variant identification) is.

 
Figure 15: Construction of an ECUVariantPattern below the SG-variant
 
For this purpose, must first be created below the SG model, with a ECUVariantPattern be given to either
the boot loader ID, or address the diagnostic needs. The
(De) activation of EraseMemory takes place via the switch activation (see Figure 15).
 
 
3.6 defining the programming sequence
 
 
By including an order file in the PDX containers, it is possible to specify a programming sequence for the
SWEN a control device. This file has the naming convention sweseq_ <Bootloader-ID>. Obey
xml.xxx_yyy_zzz, which refers to the eight-digit <Bootloader-ID> bootloader SGBM ID of the control device,
such as sweseq_01020304.xml.001_002_003 for the boot loader of SC templates.
Figure 16 shows the SWESEQ editor that allows in-system e SWESEQ files can be created. It can specify
dependencies but only for the programming ("A must be programmed before B and C"), no fixed
programming sequence. The programming system then determines the set of possible dependencies
programming sequence and passes through them.
 
Achtung: SWESEQ the file contains cyclic dependencies ("A before B" and "B before A"), it comes
to a stop with the programming.
 
For each function within the file SWESEQ EcuDependencies a new section be created. Within such a
section, the following items are to be filled:
• BootloaderId: The BootloaderId of the control device for which the dependence is to be determined
• Base variant: The basic version of the affected control unit
• Physical offset: The diagnostic address of the controller (hexadecimal)
• Preconditions: A list of IDs of SGBM Swen, from the front of the SWEN Dependors

  Seite 21 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
must be programmed
• Dependors: A list of IDs of SGBM Swen, from the preconditions for the SWEN
must be programmed
 
In the example in Figure 16, it again at a SG with SC-template (01,020,304 bootloader ID, address
0x7E diagnosis, baseline variant Evalboard) the SWE 11,121,314 21,222,324 before the SWEN,
Be programmed and 31323334 41,424,344th The order among the latter three SWEN can be chosen
arbitrarily by the programming system.

 
Figure 16: SWESEQ editor open file SWESEQ
 
Achtung: The sweseq file can also be used to dependencies between master boot loader (BTLD)
and slave boot loader (FLSL) set. Is no dependence in the sweseq file set, the slave boot loader is
programmed first! Structural dependencies (eg BTLD before SWFL, SWFL before the Cafe) need not
be separately specified. Contradicting the user-specified dependencies these basic rules is that
programming with a
appropriate error message stopped.
 
 
7.3 Storage of the container components
 
 
If the item contains all the desired SG variants and configuration files must for later
Be used (eg import into the PSdZ) is stored. It makes sense here is the use of
"Save As ..." function, otherwise the template used PDX will be overwritten. In naming the E / E
components container BBBB_KKK.xxx_yyy_zzz.eee the naming convention (see Table 1) is observed. A
valid container name would accordingly, for example
F001_EVAL 1.001_002_003.pdx.
 
BBBB Series composite
 
KKK Component name (variable length) in accordance
with [LH_FP_SWL] FP_4758 (hyphens are to be
replaced by two underscores).

  Seite 22 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Xxx Major version (decimal)

yyy minor version (decimal) Zzz

Patch (decimal)

Eee File extension by default pdx

 
Table 1: Legend for identification of the container components
 
 
08.03 ODX Checker
 
 
After saving, the container with the help of the ODX checker (see Figure 17, green box) are checked for
formal correctness. The ODX Checker required by the rules of the E-system installation in the directory C:
copy \ Data \ Rules (see 2.2.8). The ODX ODX checker detects errors in the structure, such as sensitive in
ECU-variant patterns, and lists them in the bottom pane (see Figure 17 messages per ODX check, red
box).
 
Achtung: The E-system includes installation package for both BMW ODX-written rules, and ODX
rules from a purchased package (ASAM). Will e-system installed on a computer that is not the
BMW Group is one, then the user must either
1) a license to buy ASAM rules (for more information, visit http://www.asam.net) Or
2) the ASAM rules whatsoever. These can be found in the E-system data
directory: C: \ Data \ Rules \ asamrules.jar
If not, the user violates the licensing law!
 
 
 

Figure 17: Check messages after ODX

  Seite 23 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
3.9 Import of components into the container PSdZ
 
 
Before the content can be used in the PDX-container for programming in e-system, it must be imported via
the "Import into PsdZ" in the PSdZ. During the import of PDX-container, a container name from the differing
project name must be specified under which the project is displayed when opening a connection among
others. Thus, the libraries contained in the container can be included, must be e-system may be restarted
after the import! The application then displays an appropriate message.
When importing the data is processed from the container and placed in the ESYS_DATA / psdzdata provided
locally for use in e-system. To avoid unexpected effects due to inconsistent data sets, it is recommended to
use containers with different template versions to delete the subdirectories of ESYS_DATA / psdzdata before
the import of PDX-container. The contents of ESYS_DATA / psdzdata can e-system at any time in the File
Explorer (see Figure 18) can be viewed and deleted.

Achtung: Since the files in the directory psdzdata / extLibs of the Java VM to be used can not
delete this directory, as long as e-Sys is open.
 
 
 

Figure 18: Excerpt from the File Explorer to import of ODX Data
 
 
3:10 Update containers
 
 
It is also possible to bring a present component container to automatically migrate to a newer PDX
templates. Be open to the container components must first be in PDX-Charger. The update functionality is
then initiated via the Update button (see Figure
19). Using a file dialog, the new PDX-template is selected and confirmed. I then replaced the sys-template-
specific content in the container through the components of the selected template, the component-specific
information remain unchanged. The container thus generated can then use File
→Save As ... under a new name can be saved (cf. 3.7).
 
Achtung: A container update is only possible if the template version of this
Container and the new version of the template version in the main match.

  Seite 24 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 19: Update of the PDX-container

  Seite 25 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
4Erstellung the TAL
 
To program a controller in e-system, it must be by the developer initially a transaction list (TAL) is
created. This can either be created manually in the TAL-editor with automatic calculation or from a TAL-
SG variant in the PDX-Charger.
 
 
4.1 Manual creation of the TAL TAL editor
 
 
In the TAL in the module editor "editor & viewer" can function file →New or its icon in the toolbar or create
a blank file VALLEY →Open an existing local loop can be edited.
In recreating the TAL TAL in the editor must be per control unit and a class action will use its own local loop
line with a unique ID. Moreover, in any TAL-line the basic version (not the component name), and the
hexadecimal address of the desired diagnostic controller register (see Table 2). The remaining attributes
(ExecutionStatus, FlashPreReqs, CodingPreReqs, ...) remain in the default state.
 
Talline Unique ID for each TAL-Line (decimal)
 
Base Variant Basic version of the controller to be programmed as the PDX-container

DiagAddress Diagnostic address of the controller to be programmed (in hexadecimal) Table

2: Basic elements of a TAL-Line

Fundamental part of any TAL-line course, the SWEN to be programmed. This

can be added by right clicking on the item TalLine_ID = 0 and select New (see Figure 20). When
adding a transaction, it is important to use the correct action class, for example SWDeploy for
programming and application data. A summary of current transaction classes are Table 3

 
Figure 20: Adding a new transaction

  Seite 26 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Figure 21 shows an example of a local loop is shown to program the SWEN of SC templates. For this
purpose, a TAL-line for the boot loader (ID = 1) and one for the software created (id = 2). For the
application in SWEN TAL-line transactions of type 2, four SWDeploy were inserted. The attributes of the
element below SgbmIdentifier (Process Class, ID, Main Version, ...) were calculated
filled to comply with the file name to be programmed Swen.
 
Achtung: If the versions in the TAL are not consistent with those in the filename, this will lead to
discontinuation of programming!
 

 
Figure 21: TAL TAL editor mask with open
 
The TAL-line for the boot loader was filled with a similar BLFlash transaction.
 
SWDeploy Application software and data (SWFL)
 
CDDeploy Coding (the Cafe)
 
BLFlash Bootloader / slave boot loader (BTLD / FLSL)
 
Table 3: Common transaction classes in the TAL

  Seite 27 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
4.2 Automatic calculation of TAL
 
 
In the module "TAL-measure" is a TAL by specifying an actual SVT SVT and a target can be calculated
(Figure 22). The SVT is indicating the current Verbauzustand, can either be downloaded from the VCM or
read directly from the control devices or from a file. The intended target is Verbauzustand SVT, if any,
calculated from the HIS or be loaded from a file. When calculating a target of KIS Verbaustandes an FA
must also loaded and activated, and a goal-I level can be specified.
Is both an actual and an SVT SVT nominal load, the difference in the left window is shown in color. Click the
button "Calculate" Now, a local loop can be generated to the vehicle (the SG network) from the actual
situation in the target state transferred. The calculated TAL can now be stored, edited or editor in the TAL
executed directly. If the checkbox "ECUs from SVTsoll" enabled, all control devices included in the
calculation, the target in the SVT are included. Controllers, which only appear in the actual SVT will be
discarded.
 
Achtung: The TAL-calculation works only with an open connection.
 

 
Figure 22: Calculation of the TAL from SVT SVT actual and target
 
 
4.3 generation of TAL in PDX-Charger
 
 
Is not HIS knowledge base available, it may be useful to produce a TAL directly from the data of the PDX-
container. The TAL-production is possible both for the entire container as well as for individual ECU variations.
Encouraged, the generation of the TAL by the menu item "Generate TAL" in the context menu of the ECU
variant (see Figure 23) or the root container element. In the TAL are then automatically transferred all Swen,
the variant associated with the ECU directly. Depending on the nature of the container, then it may be
necessary in a Wizard to assign version numbers, addresses diagnosis and CAF files to the ECU version
manually, if this assignment from the ODX data is clearly not possible.
In an analogous manner instead of a local loop may also be a SVT_soll in PDX-Charger are calculated
("Generate SVT"). This SVT may be in the module "TAL-calculation" is a local loop based on a read-current
state is calculated (see Section 4.2). Advantage: it produced only the really necessary transactions in the
TAL.
 
Achtung: Be open to produce a TAL / SVT in PDX-charger must be connected (see Chapter 5), there
must be a real control unit may be present. The connection type can be chosen arbitrarily in this
case.

  Seite 28 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 23: TAL / SVT-generation version of an SG
 
 
4.4 Creating a TAL with BLUP / FLUP
 
 
4.4.1 Automatic calculation module in the "local loop calculation"
 
The TAL-automatic calculation functions described with BLUP / FLUP-SWEN as described in Section 4.2.
The SVT_ist or SVT_soll contains each of the process class Ist-/Soll-Bootloader BTLD / FLSL. Using the
information from the BLUMap be required from the BLUP / FLUP-SWE calculated for the local loop.

Achtung: This method requires a connection with a project is necessary for the valid BLUMaps the
respective control units contains.
 
 
4.4.2 Automatic calculation of the PDX-Charger
 
 
Achtung: The calculation of a TAL with BLUP / FLUP-swen in PDX-Charger is not possible. Of the
present state necessary for the calculation of the control devices is not included in PDX-Charger
available.
 
 
4.4.3 Manual creation of the TAL
 
In order to BLUP transaction manually insert into a loop, do the following:
 
First Create a Line VALLEY-BLUP for the transaction and add a BLFlash transaction (see Figure
24).

  Seite 29 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 24: Adding a transaction BlFlash
 
Second Delete the default entry generated BLFlashTA
BLFlash_BTLD_00000000_001_000_000 (see Figure 25).
 

 
Figure 25: Delete the given entry BLFlashTA
 
Third Create a new BLFlashTA from a file (see Figure 26).

  Seite 30 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 26: Adding a BLFlashTA based on a file

 
4th Select the desired file dialog BLUP file. It creates a BLFlash transaction that both the SGBM ID
of BLUP (SgbmIdentifier) and the ID of the encapsulated SGBM BTLD (Contained bootloader)
contains (see Figure 27).
 

 
Figure 27: TAL-line transaction with BLUP

  Seite 31 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
5Verbindungsaufbau
 
Before starting with the SG-programming or coding, a connection must be established with the vehicle.
Prerequisite for this is a successful PDX imported container (see Section 3). The dialog for setting up a
connection is opened in E-system via the connection icon in the toolbar (see Figure 28).

 
Figure 28: Button to open the connection dialog
 
The E-system connection dialog (see Figure 29) is divided into two parts. In the text box in the upper half is
the "Target Selector" is selected. Here it is decided which of the PDX imported container is used as a data
source to connect. Should be in the lower part of the dialog to be specified, which is built on the physical
interface connection. Which parameters must be selected for which connection is explained in the following
sections.

 
Figure 29: Connection dialog e-Sys
 
 
5.1 Selecting the Target Selector
 
 
Each "Target Selector" is composed of two parts, the "Project" and the "VehicleInfo". About the
"Project" is selected, which is used the imported ODX container for the connection. About the "VehicleInfo"
decides whether a direct connection should be made to the controller, or if the controller is connected via a
gateway (CGW). Consequently, for each imported container in the connection dialog offered two target
selectors, one for the direct connection and a connection via the CGW.
 
 
5.1.1 Connection via Gateway
 
This connection type is selected if a gateway (CGW) between tester and control device (s)
is located. All services are e-mailed to the CGW system, from which they base on the

  Seite 32 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Routing table are forwarded to the sub networks in CGW.
 
Achtung: If a connection is established through ZGW be, must be in the connection dialog
always used as a target, a target selector WITHOUT adding "_DIRECT" (see Figure 30).
 

 
Figure 30: Possible Targetselektoren for a connection on CGW
 
 
5.1.2 Direct connection
 
In the direct connection, the test computer, for example via a CANCard connected directly to the SG to be
programmed, it is not used ZGW.
 
Achtung: If a direct connection can be established, must be in the connection dialog always uses
the target VehicleInfo WITH the addition of "_DIRECT" (see Figure 31).
 

 
Figure 31: Possible Targetselektoren for direct ECU connection
 
 
5.2 Selection of the physical interface
 
 
Via the radio buttons in the lower part of the connecting dialogue, the user decides which physical
interface for the connection to the control unit / ZGW to be used.
 
 
5.2.1 Connection via Ethernet
 
A connection over Ethernet, either by specifying the gateway URL or by selecting a
Be on the vehicle chassis number (VIN) built. To establish a connection to the vehicle

  Seite 33 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
can be made to have the computer and test the vehicle (CGW) located in the same IP subnet. If there is no
DHCP server on that subnet, use the default ZGW an IP address like 169.254.xx This means that the test
computer must also be an address of the form
169.254.uv obtained, so that a network connection can be established. As the subnet mask is
255.255.0.0, set in this case. Windows XP supports this address class as the "Alternative
Configuration" in the TCP / IP properties of a network connection.
 
 
Connection via gateway URL
 
If the IP address of the gateway known, the connection can be opened directly by specifying the URL
(see Figure 32). This allowed the specification of the protocol (tcp :/ /) and Port (6801) are not
forgotten, a valid gateway URL is for example, tcp :/ / 169.254.47.11:6801.

 
Figure 32: Establishing a connection via gateway URL
 
 
Connection on chassis number (VIN)
 
When you open the connection dialog will be broadcast automatically detects the connection dialog
accessible vehicles and the e-system "Connection of vehicle identification number (VIN)" is displayed (see
Figure 33). If there is no vehicle available, this type of connection is disabled. After selecting the desired
vehicle then the connection can be established.

 
Figure 33: Establishing a connection via chassis number (VIN)
 
 
5.2.2 Connection via CANCard
 
Supported by E-Sys CAN hardware and the supported driver versions, please refer to the respective
release notes for each release. The latest drivers for the CAN card, visit the
Vector website (http://www.vector-informatik.de).
 
 
Achtung: Before programming needs to "Control Panel →Vector Hardware Config "the
Link driver "PRODIAS-CAN CAN Driver 1" used to program the CAN channel and
"PRODIAS-CAN CAN Driver 2" other valid channel will be assigned (see Figure 34)!

  Seite 34 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 34: Example of allocation of "PRODIAS CAN Driver CAN 1/2"
 
In the connection dialog e-system, the "connection via bus" is selected. In the left drop-down box
is the bus to indicate, via which the connection should be established. In the right drop-down box as
Interface "VECTOR_DIRECT" set (see Figure 35).
 

 
Figure 35: Structure of a direct CAN connection through FA-CAN
 
 
5.2.3 Connection via Omitec
 
Prerequisite for the use of Omitec interface, the installation of Omitec Edibas-driver. See the installation
instructions on the package with GIS:
 
 
BMW Standard Tools Entwicklung
 
Standard Tools/Fahrzeug-Kommunikation/EDIABAS/HW-Interface/
 
EDIABAS interface Omitec
 
 
In the connection dialog then the "connection via bus" as well as the bus name and the interface
"STD_OMITEC" option (see Figure 36).

  Seite 35 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 36: Settings for connection Omitec interface
 
 
5.2.4 Connection via radio
 
Prerequisite for the use of the radio interface, the installation of Edibas. You can Edibas in
Under the standard set of GIS tools to
 
 
BMW Standard Tools Entwicklung
 
Standard Tools/Programmierung/Tool Installation Entwicklung/FüW rindows XP/
 
WINKFP 5.1.6 - EDIABAS 7.0.0.500 - NFS 4.8.0.4 - 5.0.2.0 INPA
 
 
download. For connection via radio, select "connect via bus" stating the
Bus name and the interface "STD_FUNK" (see Figure 37).
 
Note: For a wireless connection settings in other email systems is necessary (see section
2.2.5).
 

 
Figure 37: Settings for connection via radio interface
 
 
5.3 Test the connection
 
 
To test the connection and to check whether all input devices will actually work, it is recommended that after
establishing the connection the current OCC from control devices to read. This functionality is in the module
"Expert Mode →Coding "(see Figure 38). Once the connection is displayed on the left side of the
Verbaustand all connected controllers. If an error message or a blank SVT, please check the connection
settings again!

  Seite 36 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
Figure 38: Read SVK

  Seite 37 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
6TAL-processing
 
Be the actual programming operation is performed in the module TAL processing (see Figure 39), in which
the registered transactions in the local loop (see creating the TAL) is executed. Prerequisite for the execution
of TAL TAL thus charged, and a valid VIN (Vehicle Identification Number VIN) are. The VIN can be either
loaded from a vehicle order (FA) is read or entered directly into the field provided. Both FA VIN and can, if
available, can be read from the VCM (read buttons reading (VCM) or VIN (VCM)). TAL and FA can be
opened using the "Edit" button directly in the appropriate editor.
 
AchtungIncludes the selected Codiertransaktionen TAL, a VIN is not sufficient for processing,
it is a suitable FA (faVersion = "3") is required. Vehicle contracts can be comfortable with the
tool [FA_GEN] are created.
 

 
Figure 39: TAL-processing
 
The following controls are relevant to the TAL-processing:
• Start: Here, the TAL processing is started. Undergoing a TAL-processing, changes the
Lettering to "break" and the processing can be interrupted.
• Stop: Cancels the execution from the TAL is not activated until the start of execution.
• Blank: Clears the log window.
• Events: Specifies whether to display during the TAL processing events in the log window or not.
The selected events will be displayed during the execution of the TAL in the log window (tab "Log").
• Event type: Display indicates which types of events in the local loop execution. Furthermore, it
is possible to exclude certain control devices or classes of transaction processing. To this end, the tab
is "SG" (see Figure 40). With a matrix can be selectively controlled, which charged the transactions to
be executed for which TAL controller. Thus, any subset of an existing local loop will be executed.

  Seite 38 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 40: TAL-matrix for optimizing the selection of transactions

  Seite 39 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

7Besonderheiten to takeover control devices

 
 
1.7 Mapping
 
 
To deal with the takeover control units in L6-environment, you must have the logistical information in the
takeover-SG (ZB-number, hardware ID, hardware reference, ...) is mapped to the L6-SGBM identifier. This is
done with the help of mapping files that are created in the editor and tickets in the PDX-Charger under
Config components involved in the container (see Figure 41).

 
Figure 41: Container with mapping files for AMP_TOP and MULF_Basis
 
The following is briefly sketched, which contains which file mapping information and how the respective
Mapping is performed:
• _BTLD: Mapping of the hardware reference to the SGBM ID and the version of the bootloader (BTLD).
• _CAFD: For example, mapping the number on the ID SGBM CAF-file (the Cafe). As a major
release from the service of BMW_vehicleManufacturerCodingIndex "Ident_Lesen" is used. The
Minor version and patch version of the coding are the Service "Aenderungsindex the
Coding to read "determined.
• _HWEL: Mapping of hardware ID (PECUHN) and hardware reference (ZZZPPP) on SGBM ID and
hardware version of the electronics (HWEL). If no hardware number of the controller are read, the
mapping is only based on the reference hardware.
• _TYPNR: For example, mapping the number on the type approval number.
• _ZB: Mapping example program reference number and the software version of the controller (SGBM
IDs and versions). Agree to any information on the program version with the mapping files, only the
SGBM ID is returned with the release of 000 million mapping.

  Seite 40 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
7.2 AIFContents
 
 
Need to program an ECU Mischverbau-in e-system in the TAL addition, the contents of the
User Info box (AifContents) are filled (see Figure 42).
 

 
Figure 42: TAL for MULF_Basis AifContents
 
The following entries are to be made there:
• BmwAssemblyNumber: The assembler number that after programming in the AIF / UIF
is written
• BmwCalibrationDataSetNumber: SW _TYPNR number from the file-mapping for controllers with
"large" AIF (51 or 64 bytes), or "0000000"
• BmwExhaustRegulationOrTypeApprovalNumber: _TYPNR Type approval from the
mapping file for emissions-related parts, or "0000000"
 

• PrgRef: The program of the reference to program software

 
 
Achtung: The information entered in the TAL AifContents at the end of a successful
programming operation is written into the controller. If this information is incorrect, can then be
performed for this timer no longer mapping. Thus, the control unit with E-system is not
programmable!

  Seite 41 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

 
8Individualdatenrettung
 
The Individual Data Recovery (IDR) is used in a defective but still capable of diagnostics before SG SG-
exchange individual data of the vehicle / driver from the affected controller and read this einzuspielen
after the exchange in the new SG.
 
 
1.8 IDRlight
 
 
IDRlight is a variant of the IDR, which is used by EA.
 
 
8.1.1 IDBackup
 
As IDBackup refers to the reading and storing of individual data. To perform a IDBackup, one needs
first a suitable TAL. This can either be suitably VALLEY SVTist / SVTsoll calculated automatically or
manually.
 
 
Automatic calculation of the TAL
 
In order to automatically calculate the TAL IDBackup with e-systems can be, you need a
SVTist / SVTsoll, the following requirements:
• Wherein said control unit from which the individual data to be read, must be in the
SVTist / SVTsoll at least one hardware element (HWEL) in either the SGBM ID or in the
Versions differ.
 
KIS is no database available for appropriate SVTsoll auszuleiten automatically, it is advisable to adjust the
SVTist in TAL editor suitable to use as a SVTsoll. If these files in the module "comfort mode →TAL-loaded
calculation "can be calculated from an appropriate TAL them (see 4.2).
 
Achtung: When calculating the TAL may cause warnings when no HIS-DB is available or not certain
modules can be used. I.d.R. But these warnings can be ignored.
 
The calculated TAL can be stored in the module and then "Viewer & Editor →TAL-editor "or opened in any
XML editor.
 
 
Manual creation of the TAL
 
The TAL for IDBackup can also be created manually in the TAL editor. The following elements must be
created for a functioning IDBackup in the TAL at least:
• HWInstall a transaction for the affected SG (any content)
• HWDeinstall a transaction for the affected SG (any content)
• IDBackup a transaction for the affected SG
Be created for each of these transactions must have its own local loop line (see 4.1). Within the
Transaction must be IDBackup IDBackupLight element inserted.
 
Achtung: Within a transaction can e-IDBackupntweder IDBackup one-oder IDBackupLight an
element to be inserted. When creating a new transaction automatically generated IDBackup
IDBackupTA element must therefore be deleted first before a IDBackupLight element can be created.

  Seite 42 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 
Reading and storing of individual data
 
To read the individual data must be generated in the TAL module now "Expert Mode →TAL-processing can
be carried out "(see Chapter 6). If the individual data recovery is successful, the TAL-processing finishes
with a status of "FinishedForHWTransactions_BackupOK." If this status reached, the menu item "Tools
→Individual data recovery ... "specifies a directory in which the individual data to be stored. The data is then
displayed in the XML file IDBackup.bak stored in the specified directory.
 
 
8.1.2 IDRestore
 
Even the IDRestore, so writing back the read data into the control unit is controlled via a TAL. Again, the TAL
can be calculated either automatically or manually. The auto calculation requires that backup data is present
in the form of file IDBackup.bak.
 
 
Automatic calculation of TAL
 
To calculate the IDRestore transaction in the module "comfort mode →TAL calculation must "not be
different and SVTist SVTsoll. It is advisable to fill both fields with the current SVTist to ensure correct
InstalledECUList is generated. This transaction is in fact a IDRestore calculated, it must also set the hook
in the check box "Individual Recovery" and the directory containing the file IDBackup.bak be specified in
the adjacent field (see Figure 43). Subsequently
can calculate the TAL and the TAL are triggered saved, it will contain exactly the data that was
stored in the file IDBackup.bak.
 
Achtung: When calculating the TAL may cause warnings when no HIS-DB is available or not certain
modules can be used. I.d.R. However, these warnings
be neglected.
 
 
 

 
Figure 43: Settings for the local loop calculation IDRestore
 
 
Manual creation of the TAL
 
The TAL for IDRestore can be generated manually. This requires the editor in a TAL TAL TAL only one line
with a IDRestore transaction will be created (baseline and do not address diagnosis). Be included within that
transaction must be a IDRestore IDRestoreLight element, then any number in the data records, each with a
data identifier and the associated
Data (values) can be created (see Figure 44).
 
Achtung: Within a transaction can e-IDRestorentweder IDRestore one-oder IDRestoreLight an
element to be inserted. When creating a new transaction automatically generated IDRestore
IDRestoreTA element must therefore be deleted first before a IDRestoreLight element can be created.

 
Seite 43 von 44
   www.bmwcoders.com

Bedienungsanleitung: SG-Programmierung mit E-Sys 18.11.2009

 
 

Figure 44: Manually created for TAL IDRestore

 
 
Restore the individual data
 
To restore the individual data into the control unit must be processed now, only the calculated or manually
created in the TAL module "TAL-processing". Writing back the data is successfully completed, the TAL-
processing status is "Finished".

  Seite 44 von 44