Where the request comes from
E-Sys uses TAL for programming. The protection check uses planned operations, software information and vehicle data. If permission is required, the program creates the original request.
Programming Protection Token Basic applies in Field-Mode, the vehicle's normal operating mode. VIN alone cannot describe the planned operation. Software data, the plan and the procedure's programming requirements must already be prepared. Programming requires an appropriate external vehicle power supply.
Example
With appropriate prepared inputs in E-Sys 25.10.01, open Expert Mode → TAL-Processing.
- Select Check Programming Protection and inspect the affected units and protection variant.
- Continue these steps only for PPT Basic. In Programming Protection Basic (Field-Mode), select Create request file.
- Keep the request unchanged, check service requirements and obtain the response. Save it separately beside the request.
- Select the response in the same TAL-Processing row. A path shows selection; token suitability is checked when the plan starts.
- When the vehicle and all programming requirements are ready, Start executes the plan and checks the token for protected operations.
- Inspect completed actions and errors, then test the affected vehicle functions.
Another mechanism's response, such as an ISTA diagnostic token, does not authorise this operation.
Assess a rejection
Keep the exact message and E-Sys version. Distinguish a permission rejection from failure while executing the operation. A token file does not establish successful programming.
Check that the response belongs to the request and protection variant. If the planned work changed, do not assume the old pair still fits. Assess the result from the operations actually performed and the vehicle checks.