Start with the intended result
A control unit, or ECU, runs software and stores settings for the vehicle. Some functions also need permission.
| Result | Operation | What changes |
|---|---|---|
| Configure behaviour for the equipment | Coding | Setting values |
| Install different software | Programming | Unit software |
| Authorise a protected function | Activation | Permission code or token |
Choose the operations from the installed equipment, software and repair procedure. Settings cannot install a missing camera, and a permission cannot replace the software required by a function.
Understand the coding data
FA, or Vehicle Order, describes the vehicle configuration. VO coding derives settings from it. Factory FA may differ from the configuration required after a retrofit.
SVT lists units and their hardware and software components. Actual describes the read state; Target describes the intended state. Keep that distinction when saving files.
CAFD identifies the coding description CAF. NCD contains specific setting values. FDL presents those values as functions and parameters for viewing or editing. Whether changes can be written depends on the unit and software. Saving an edited file does not itself change the vehicle. Secure Coding requires the appropriate digital signature.
Understand programming and permissions
E-Sys uses TAL to specify units and operations. It can include software deployment and coding. Check all affected units, versions and required software files before execution. Programming needs an external power supply meeting the relevant BMW procedure.
FSC authorises a particular function; factory FSC does not cover every future map version. SFA manages protected features. KDS concerns component theft protection and pairing. CBB concerns unit certificates and bindings. PPT Basic authorises the corresponding protected programming operations. Similar file extensions do not make their responses interchangeable.
Example
For a replacement head unit, identify the procedure's software, settings and feature permissions before selecting a token. If the fault is unclear, use ISTA diagnostics and its Test plan to investigate the symptom.
To inspect data in E-Sys 25.10.01 with the vehicle connected, open Coding. Read and save FA under Vehicle Order. Read SVT Actual using Read (ECU) and save it separately. Read coding data for the required CAFD to obtain its current NCD, then view it in the FDL editor. These actions retrieve data rather than write new settings.
Confirm each stage
Save the inputs and operation report, then test the function in the vehicle. Receiving a file, completing a write and restoring the required behaviour are separate results.