OnlineTool BMW software updates in E-Sys use a TAL. It describes which units will be processed and what the program will do. Understand the plan before starting: software updates and coding may be part of the same job.
This guide explains TAL contents and viewing a saved file in E-Sys 25.10.01.
What TAL means
TAL lists operations for vehicle control units. Its name comes from the German Transaktionsliste, meaning transaction list. Here, a transaction is a program operation such as writing software.
A plan can involve one unit, several units or the whole vehicle. It lists units, operations and software components. Opening a TAL displays these details. Executing it is a separate action in TAL-Processing.
The file tree contains TalLine entries. Each relates to a particular unit and operation type. A unit may appear in several entries, for example one for software and another for coding data.
Common operations in a plan
Start with these three labels:
| Label | Meaning |
|---|---|
| SWDeploy | Writing software and associated data |
| CDDeploy | Writing coding data — the unit's settings |
| BLFlash | Writing the bootloader, involved in starting the unit and loading its software |
A TAL can contain other operations. Check their purpose in the documentation for the particular procedure.
SWDeploy and CDDeploy for one unit mean that the plan includes both programming and coding. The unit name alone does not describe the whole job; expand its entries.
TAL, FA and SVT
FA describes the vehicle and equipment. SVT Actual describes the current units and components, while SVT Target describes the intended configuration.
TAL-Calculating can calculate TAL from SVT Actual and SVT Target. Differences between the current and intended states produce an operation plan.
Before calculation, check that the input describes the vehicle and the target matches the repair or update. If coding is included, execution also requires suitable FA. VIN alone is insufficient for this part of the job.
Opening a saved TAL
You need the saved plan file.
- Open Editors & Viewers → TAL-Editor.
- Select File → Open and choose the TAL.
- Select Expand Tree to expand the first level, then expand relevant entries manually.
- If Filter active is enabled, turn it off to view the full tree.
In each TalLine, find BaseVariant, the unit variant, and DiagAddress, its diagnostic address. The address identifies the unit, while VIN identifies the whole vehicle.
Inspect the operation type and software components with their versions. Check every entry for the required unit to see the complete planned work.
Checks before execution
Compare the TAL with the job: affected units, planned operations and software versions. If additional units appear, establish why they are included before proceeding.
Execution requires the appropriate software files. Check SWE availability in TAL-Processing checks whether the software components are available. SWE is a software unit used by E-Sys. This checks data availability; assess the correctness of the job separately.
Programming also requires an external vehicle power supply meeting the procedure's requirements. After execution, save the result and check the affected vehicle functions.
Example
To update one unit's software, open the prepared TAL, find the unit and inspect all of its entries.
If they include SWDeploy and CDDeploy, account for both software writing and coding. Check FA and the files against the listed versions. BLFlash means that the plan also includes writing the bootloader.
If other units appear, establish why they are included and whether this matches the procedure. Once the plan is understood, prepare execution according to the instructions for the particular vehicle and job.
Check programming protection
If the prepared TAL requires PPT Basic, create the request for that variant. A token does not replace software, FA or plan preparation.