Volkswagen Remote Diagnostics and ECU Programming — VAS6154A with ODIS via eLinehub

The four scenarios below cover the most common remote Volkswagen programming jobs handled through eLinehub: module replacement with SVM, SFD unlock on MQB EVO, VAG ODIS immobiliser adaptation via GeKo, and ADAS static calibration.

​

Scenario 1: Jetta 09G TCM Replacement — SVM Programming and Component Protection Release

A 2020 Jetta with a failed 09G automatic transmission control module arrives at an independent shop. The replacement is a new OEM TCM with no VIN-specific calibration loaded. ODIS must complete SVM and Component Protection release before the vehicle can leave the shop.

Mechanic (workshop):

1. Connect VAS6154A to the Jetta’s OBD-II port and to the workshop PC via USB cable.

2. Launch eLinehub Mechanic and install the USB device detection plugin if prompted — this activates on both PCs simultaneously. VAS6154A will appear under “Mechanic USB.” Confirm status shows active, then publish the order.

3. Keep ignition on and remain at the vehicle. SVM and GeKo procedures require continuous ignition throughout — do not cycle it unless the Technician instructs.​

Technician (remote):

1. Accept the order in eLinehub Technician. Select Mechanic USB as the device type and initiate the connection. Wait for VAS6154A initialization to complete before launching ODIS — launching before initialization shows no VCI in the device selector.

2. Launch ODIS-Service. Navigate to Vehicle → Start Diagnostic Session → Select VCI → VAS 6154A. Allow the full control unit scan to complete.

3. Navigate to Control Units → 02 Gearbox (J217) → Functions → Software Version Management (SVM). Log in to VW Online. ODIS contacts the SVM server, confirms the correct software build for this VIN, and flashes the TCM — typically 8–15 minutes on a wired connection.

4. After SVM completes, navigate to Control Units → 02 Gearbox (J217) → Functions → Component Protection → Release Component Protection. ODIS initiates a GeKo session. The VAG backend verifies the module-to-VIN association and releases Component Protection — typically 3–6 minutes of uninterrupted three-way communication.

5. Clear all DTCs across all control units and verify no residual faults.

​

Scenario 2: Golf GTI MQB EVO — SFD Token Unlock Before Airbag Control Unit Coding

A 2022 Golf GTI arrives after airbag deployment. The replacement airbag control unit (address 15) requires an SFD token before ODIS will permit coding or basic settings — it is a protected module on the MQB EVO platform, and the token window is time-limited.

Mechanic (workshop):

1. Connect VAS6154A to the Golf GTI’s OBD-II port. For this MQB EVO vehicle, VAS6154A uses DoIP — connect the VAS6154A LAN module cable to the workshop PC via wired Ethernet. If the RNDIS network adapter does not appear in Device Manager, install the network adapter detection plugin from within eLinehub Mechanic.

2. Launch eLinehub Mechanic. Select Mechanic Network Adapter (not Mechanic USB) for this DoIP session. Publish the order.

3. Keep ignition active and remain at the vehicle during the SFD token window. The Technician will confirm when it is safe to cycle ignition.​

Technician (remote):

1. Accept the order in eLinehub Technician. Select Mechanic Network Adapter, choose eLinehub Link as the bridging sub-mode, and initiate the connection.

2. Launch ODIS-Service. Select VAS 6154A in the VCI setup screen — eLinehub presents the DoIP adapter as a locally connected VAS6154A. Navigate to Vehicle → Start Diagnostic Session and allow the DoIP topology scan to complete (typically 60–90 seconds).

3. Navigate to Control Units → 15 Airbag → Security Access → Online Unlock SFD. ODIS requests an SFD token from VW’s server for this VIN. Once the token is returned, ODIS applies it within the validity window. Do not interrupt or suspend the session during this exchange.

4. After SFD unlock, navigate to Control Units → 15 Airbag → Coding → Long Coding and apply the correct configuration for this vehicle. Then navigate to Basic Settings → Airbag System Initialization and run the guided initialization sequence.

5. Clear all DTCs and confirm no active faults under address 15.

​

Scenario 3: VAG ODIS Immobiliser Adaptation — All-Keys-Lost via GeKo on Passat / Golf

A 2018 Passat arrives with all keys lost. The Immo 4 system requires ODIS to perform immobilizer adaptation (also referred to as immobiliser adaptation in EU markets) via a GeKo online session that binds a new key to the engine control unit and instrument cluster through VW’s backend server. No offline procedure exists for this platform.

Mechanic (workshop):

1. Connect VAS6154A to the Passat’s OBD-II port via USB. Ensure the new blank key is in the vehicle — ODIS will prompt for key insertion at a specific point.

2. Launch eLinehub Mechanic, select Mechanic USB, and publish the order.

3. Follow Technician instructions precisely during the key insertion and turn-sequence steps — the GeKo session has strict timing between the ODIS prompt and the physical key action.​

Technician (remote):

1. Accept the order in eLinehub Technician, select Mechanic USB, and initiate the connection. After VAS6154A initialization, launch ODIS-Service.

2. Navigate to Vehicle → Start Diagnostic Session. After the full scan, navigate to Control Units → 25 Immobilizer → Functions → Guided Functions → Key Matching / Immobilizer Adaptation → GeKo Online Key Learning.

3. Log in to VW Online with a GeKo-enabled account. ODIS simultaneously connects to VAS6154A at the vehicle and to the VAG GeKo server via the Technician’s internet connection — VW’s backend checks the VIN against the FAZIT database for theft status before authorizing key learning.

4. Follow the ODIS on-screen prompts for key insertion and turn sequence, communicating each step to the Mechanic in real time. The session cannot be paused.

5. After key learning completes, verify the new key starts the vehicle and clear any residual immobilizer-related DTCs.

​

Scenario 4: Atlas KAFAS3 Front Camera — Static Calibration After Windshield Replacement

A 2021 Atlas with Front Assist has had its windshield replaced. The KAFAS3 front camera system (J979) is storing a calibration fault and Front Assist is deactivated. ODIS guided function is required before delivery.

Mechanic (workshop):

1. Connect VAS6154A to the Atlas OBD-II port via USB and to the workshop PC. Position the vehicle on a level, flat surface inside the workshop with no overhead obstructions above the camera’s line of sight.

2. Launch eLinehub Mechanic, select Mechanic USB, and publish the order. The Technician will specify the required calibration target distance and type from the ODIS screen.

3. Follow Technician instructions for target repositioning during the calibration routine.​

Technician (remote):

1. Accept the order in eLinehub Technician, select Mechanic USB, and initiate the connection. After VAS6154A initialization, launch ODIS-Service.

2. Navigate to Vehicle → Start Diagnostic Session. After the full scan, navigate to Control Units → A9 Camera System Front (J979) → Functions → Guided Functions → KAFAS3 → Camera Calibration → Static Calibration.

3. ODIS displays the required target specifications for this Atlas variant. Confirm with the Mechanic that the target is correctly positioned per the ODIS setup screen.

4. Start the calibration routine. ODIS communicates with J979 through VAS6154A to capture the calibration frame, compute correction offsets, and write the values to the camera module — typically 5–10 minutes.

5. Navigate back to Control Units → A9 Camera System Front (J979) and clear all DTCs. Confirm Front Assist is active in the instrument cluster before ending the session.

Collision repair networks: A single ADAS specialist covers multiple shops across a region. Each shop handles positioning and target setup; the specialist performs the ODIS-guided calibration remotely.