KDS provides electronic theft protection for vehicle components by linking a protected component to the vehicle. After replacing a unit, renewed pairing — Re-Pairing — may be required. The operation uses a KDS token.

This guide covers E-Sys 25.10.01 → Expert Mode → KDS Extended. The vehicle connection is already established. It applies where diagnostics identify a need for Re-Pairing and the response is intended for this module.

1. Read the KDS system

  1. Open Standard actions.
  2. Select Read KDS and wait for completion.
  3. Inspect the participants under Master and Clients.

Master is the central protection participant. Clients are the protected components linked to it. The read shows which participants are present in the connected vehicle.

Open KDS Status and select Quick check. Save its result text or capture the window for comparison afterwards.

ERROR_CLIENT_NOT_PAIRED indicates a component without a link to the central participant. MASTER_OK_CLIENT_INVALID indicates a Client problem while Master is valid. These messages guide diagnosis; choose the actual repair operation from its results.

2. Create a Re-Pairing request

Open Extended actions.

  1. Select the components specified by the repair procedure in the participant tree.
  2. Under Create a request file for a Secure Token (Set), select Re-Pairing.
  3. Select Create request file.
  4. Save the request in the job folder. Record the vehicle, E-Sys version, selected participants and operation.

The request can concern selected participants or the whole KDS system. Check that the selection matches the planned work before creating the file.

The request contains operation data. VIN alone is insufficient to prepare this token.

3. Obtain the response for this request

Submit the original request for KDS token preparation after checking it against the service requirements. Keep its contents unchanged.

Before ordering, establish that the chosen source provides a response for Re-Pairing in KDS Extended. The name “KDS token” alone does not establish this.

Save the response beside the request. This preserves the link between the planned work and its result.

If a new request is created or the participants change, establish which request the current procedure expects. A response belongs to the operation for which it was prepared.

4. Select and write the response

Return to Extended actions in KDS Extended.

  1. Find Write existing Secure Token (Set) to vehicle.
  2. Use … in its File Name field to select the response intended for this request and module.
  3. Select Write Secure Token (Set).
  4. Wait for completion, read the operation result and save the messages.

Selecting the file loads it for application. Check the write result separately in the E-Sys messages.

5. Check pairing and component operation

Open Standard actions again and perform Read KDS. Run Quick check under KDS Status.

Compare the result with the initial state. MASTER_OK_CLIENT_OK reports a normal state for both sides in this check.

Check the replacement component's operation in the vehicle. If pairing is restored but the function remains unavailable, continue diagnosis of settings, software and equipment.

For a rejection, keep the full message, request, response and selected operation details. These help identify the affected stage: request creation, token preparation or application in the vehicle.

Example

If diagnostics identify Re-Pairing after a component replacement, read KDS, record the initial state, select participants and create the request. Obtain a response for that request intended for KDS Extended.

Select the response in the token writing section. After the operation, read KDS again, compare Quick check with the initial state and check the component in the vehicle.

Check the KDS response purpose

This procedure requires a response for Re-Pairing in KDS Extended. Before ordering, establish that the chosen source provides that particular result.

Read about KDS tokens