Follow three selection steps
Identify whether the task needs vehicle records, unit settings or permission. Establish whether retrieval uses VIN or an operation request. Then check where the result will be applied.
| Task | Result | Required input |
|---|---|---|
| Retrieve original equipment records | Factory FA only | Complete VIN; obtain SVT separately |
| Prepare signed settings | NCD 2.0/3.0 | Matching FA and SVT |
| Retrieve available factory feature codes | Factory FSC | Complete VIN |
| Retrieve factory SFA feature tokens | SFA package | Complete VIN |
| Authorise component protection work | KDS token | Request for the relevant procedure |
| Validate unit certificates and bindings | CBB response | Validation request |
| Continue protected ISTA diagnostics | Diagnostic token | That function's request |
| Authorise protected programming | PPT Basic | Programming Protection Basic (Field-Mode) request |
The table identifies a direction. Check the chosen service's requirements for the actual unit, operation and program version before processing. A name does not establish every response's applicability.
Why a request needs to remain intact
VIN identifies the car. A procedure's request also describes the operation. KDS, CBB, diagnostic tokens and PPT Basic therefore need their appropriate original file.
Factory FA returns FA without SVT. If preparing NCD, obtain and check suitable unit data separately. Keep all input origins clear.
Save requests unchanged and responses as separate files, with the program version and job details. A screenshot explains a message but cannot replace the request.
Example
For E-Sys programming, check the prepared plan using Check Programming Protection. If it requires PPT Basic, create the request in Programming Protection Basic (Field-Mode), obtain that response and return it to the same row.
Continue the procedure and assess the report after TAL execution. An ISTA diagnostic response belongs to another function.
If selection is unclear
Record the exact message, version, operation and stopping point. Keep any generated request. Establish whether the issue concerns preparation, response application or the vehicle before selecting another service. Receiving a suitable file still leaves application and result checks to complete.