Identify the stopping point
ISTA provides diagnostics, service procedures and relevant programming functions. Some diagnostic actions need permission. ISTA creates their request and shows how to provide a response.
A file created by ISTA is not necessarily a diagnostic token request. Validation after replacement can concern a different task. Record the action and exact message rather than choose by the word token alone.
Preserve the input and instructions
Use the original request from that function. VIN or a screenshot cannot replace it. Keep the file unchanged and save ISTA's instructions, version and the step where it stopped.
Keep request and response separately in the job folder. A response from another check is not appropriate merely because the model matches.
Example
- Start the required check. If a protected diagnostic function requests a token, save the request through the displayed window.
- Save the instructions for applying the response. Use this procedure rather than assumed steps from another ISTA version.
- Check the request's purpose and submit it for an ISTA diagnostic token. Save the response beside it.
- Return to that check and follow ISTA's instructions. If a new request was created, establish which response the function now expects.
- After acceptance, run the function and assess its result before continuing diagnosis.
Distinguish the failure stages
If processing fails, verify that the input is the original diagnostic request and keep the message. If ISTA rejects the response, check the pair and application instructions, and record the version and exact rejection.
If acceptance succeeds but the function fails, investigate that diagnostic result. An accepted token does not establish that the equipment works correctly or remove the fault.
What completes the task
Downloading produces the response. Applying it permits the corresponding action. The vehicle decision comes from the completed diagnostic function and any further required checks.