Understand the plan
TAL, Transaktionsliste, lists units, operations and software components. Opening it displays information; execution starts separately in TAL-Processing.
Each TalLine relates to a unit and action. A unit may have entries for software and coding data.
| Label | Action |
|---|---|
| SWDeploy | Software and related data deployment |
| CDDeploy | Coding data deployment |
| BLFlash | Bootloader writing |
Check other operations against the particular procedure's documentation.
Example
In E-Sys 25.10.01, open Editors & Viewers → TAL-Editor and File → Open.
- Use Expand Tree for the first level, then open relevant entries. Disable Filter active to see the full tree.
- Identify BaseVariant and DiagAddress in TalLine. They identify the unit variant and address; VIN identifies the vehicle.
- Review every entry for the unit and record operations, components and versions.
- If expecting one unit, establish why any additional units are included before proceeding.
SWDeploy with CDDeploy requires accounting for software and settings. BLFlash adds bootloader writing.
Compare the inputs
SVT Actual describes current components and SVT Target the intended state. TAL-Calculating can derive the plan from these tables. FA describes configuration and is needed for included coding.
Check that Actual matches the car, Target matches the task and FA matches the intended equipment. VIN alone cannot replace these data.
Complete execution preparation separately
Check SWE availability in TAL-Processing checks software component availability. Having files does not establish that the task and versions are correct.
Programming needs the external power supply required by the procedure. Save the completed report and check affected vehicle functions afterwards. Reading the plan is preparation, not confirmation that the operations ran.