OnlineTool E-Sys or ISTA may request a code, token or data file. Choose the service according to the action that needs it. “Token” alone is insufficient: diagnostics, programming and feature restoration use different permissions.
Start with the operation being performed. The program module, message and created request help identify the required result.
Vehicle data and permissions
Preparation may require FA — vehicle configuration data and SVT — control unit and software data. This pair can be used to prepare signed NCD coding data for the appropriate configuration.
The program may require permission when preparing or starting an action. An ISTA diagnostic function and E-Sys programming protection require different authorisations.
| Required result | Service | Input data |
|---|---|---|
| Original vehicle equipment records | Factory FA | Complete VIN; SVT must be obtained separately |
| Signed coding data | NCD 2.0 / 3.0 | Matching FA and SVT for the required configuration |
| Available factory feature authorisation codes | Factory FSC | Complete VIN |
| Permissions for available factory features | SFA — Secure Feature Activation | Complete VIN |
| A token for a component protection operation | KDS — component protection | Request from the KDS procedure |
| A certificate and binding validation response | CBB Validation | Request from the validation procedure |
| Permission to continue a protected ISTA diagnostic function | ISTA diagnostic token | Request saved by ISTA for that function |
| E-Sys programming protection permission | Programming Protection Token Basic (PPT Basic) | Request from Programming Protection Basic (Field-Mode) |
Use the table to identify the relevant service. Compare its requirements with the vehicle data or original request before ordering. A service name does not establish compatibility with every unit or software version.
Why some services use VIN and others need a file
For Factory FA, provide VIN to retrieve the original configuration. The result is FA only, without SVT. For a job that needs both files, obtain suitable unit data separately, for example by reading SVT Actual from the vehicle.
If the program creates a request for a particular action, submit that request. It contains the data needed to prepare a response. VIN and a screenshot help explain the situation but do not replace the file.
Keep the request unchanged. Save the response beside it as a separate file so results from different jobs remain distinguishable.
Example: E-Sys requires programming permission
Prepare the unit operation plan and check programming protection first.
If E-Sys requires PPT Basic for the chosen operation, use that service and submit the request from Programming Protection Basic (Field-Mode). Return the response to the same E-Sys row. An ISTA diagnostic token belongs to a diagnostic function in another program and does not authorise this operation.
After selecting the response, continue according to the E-Sys procedure. The token is checked when the prepared plan starts. Assess programming results after execution.
If the message does not identify the result clearly
Keep the exact message, program name and version. Record the operation and the step where it stopped. Keep any request the program created.
Use these details to identify the correct service before another order. Buying a different token at random may miss the cause: the problem may concern applying an existing response or the subsequent vehicle operation.
Open the appropriate service
Match the operation and input data with the table first. Choose the corresponding service from the catalogue. Receiving a result and applying it are separate stages.