JLR DoIP VCI
Remote Diagnostics & Programming

SDD with J2534-based CAN communication — stable for most diagnostic operations, but requiring a lossless connection to complete offline module programming without session timeouts.

Pathfinder with the JLR DoIP VCI introduces strict handshake timing and session-state requirements. The VCI must be the only active diagnostic interface on the PC.

Sole-VCI exclusivity enforced at OS level. High-burst DoIP traffic during ECU enumeration. CCF writes and VBF flash each require a continuous, lossless Ethernet session. TOPIx Cloud (2020MY+) requires the VCI to appear locally on the Technician’s PC.

Driver-Level Mapping — Your Credentials, Your Control

Unlike screen sharing, where Pathfinder runs on the workshop PC under a workshop-held JLR account, eLinehub maps the DoIP VCI at the OS and driver level to your own machine. Pathfinder sees a locally connected, exclusive VCI — sole-VCI exclusivity is satisfied before the software launches. Your Pathfinder subscription, LSID license, and TOPIx Cloud credentials never leave your PC.

Software-Only — No Hardware to Install, No Update Cycle

Unlike hardware relay boxes, eLinehub requires no per-workshop hardware purchase — no matching relay device at £300–800 per location, no firmware update cycle that risks breaking compatibility with new JLR VCI driver releases. eLinehub is software-only and works with the JLR DoIP VCI the workshop already owns. VXDIAG VCX SE JLR, Launch SmartLink C, and DA-DoIP VCI are also supported using the same workflow.

Sole-VCI Exclusivity Satisfied — No VPN Workaround

Unlike raw VPN tunnels, which cannot present the VCI as a local DoIP network adapter on the Technician’s PC, eLinehub injects the RNDIS adapter at the driver level. Pathfinder’s VCI discovery finds it on the expected local interface — no modifications to Pathfinder settings, no workarounds. All DoIP sessions use Relay Mode; no port forwarding or VPN configuration is required on either side.

1. Connect the JLR DoIP VCI to the workshop PC via USB cable, then connect the DoIP/Ethernet cable from the VCI to the vehicle OBD-II port.
2. In eLinehub Mechanic, select Mechanic Network Adapter. Enter vehicle details, publish the order, and use a wired internet connection throughout the session.

1. Accept the order. Wait for the JLR DoIP VCI to initialize and confirm it appears as a network adapter on your PC before launching Pathfinder.
2. Verify no other VCI drivers or diagnostic interfaces are active on your machine — competing adapters cause Pathfinder VCI discovery to fail.
3. Open the vehicle session in Pathfinder. Navigate to Module Programming → Replace ECU for the BCM. Pathfinder retrieves the VIN-correct VBF package from JLR’s servers via your TOPIx account and executes the flash.
4. Pathfinder runs VIN write and immobilizer alignment automatically on completion. Run a full network scan to clear residual DTCs and confirm no faults remain.

1. Install the replacement KVM module. Connect the JLR DoIP VCI to OBD-II and to the workshop PC.
2. In eLinehub Mechanic, select Mechanic Network Adapter and publish the order. Use a wired internet connection — the TOPIx session during key matching must remain authenticated throughout.

1. Accept the order. Launch Pathfinder after VCI initialization is confirmed.
2. Select the Range Rover Sport L494. Navigate to Module Programming → Keyless Vehicle Module (KVM #1731). Pathfinder connects to JLR’s IVS server, downloads the correct software for this VIN, and executes the KVM flash.
3. Run VIN Learning to register the module on the vehicle network after the flash.
4. Execute Key Matching: present each key fob per Pathfinder’s prompts. Test remote entry and engine start before closing the session.

1. Install the replacement BSM modules. Connect the JLR DoIP VCI to OBD-II and to the workshop PC. Park the vehicle on a level surface with tire pressures at spec before calibration begins.
2. In eLinehub Mechanic, select Mechanic Network Adapter and publish the order.

1. Accept the order. Launch Pathfinder after VCI initialization.
2. Select the Range Rover Velar L560. Open ADAS Calibration → Blind Spot Monitoring System. Pathfinder runs a VIN write step for the new modules before calibration.
3. Execute BSM Radar Initialization for each module. Pathfinder confirms sensor health and clears ADAS DTCs.
4. If the ACC forward radar was disturbed, run the forward radar static calibration routine separately with the vehicle stationary per Pathfinder’s specification. Confirm all ADAS fault codes are cleared before releasing the vehicle.

1. Connect the JLR DoIP VCI to the workshop PC via USB cable, then connect the DoIP/Ethernet cable from the VCI to the vehicle OBD-II port.
2. Download and install eLinehub Mechanic on the workshop PC. No JLR software, no Pathfinder account, and no TOPIx Cloud subscription required at the workshop.
3. Obtain connection credentials from your Technician before the first session — either a Passcode for the specific order, or a Custom Mechanic software build your Technician has provided.
4. Open eLinehub Mechanic, select the appropriate mapping mode, enter vehicle details, and publish the order. Maintain the connection until the Technician confirms the session is complete.

1. Download and install eLinehub Technician on the PC where JLR Pathfinder, SDD, and/or TOPIx Cloud are already installed. Windows 10 or Windows 11 (64-bit) required.
2. Ensure the JLR DoIP VCI driver (or third-party VCI driver) is installed on this PC. For Pathfinder sessions, confirm no other VCI drivers or diagnostic interfaces are active before accepting an order.
3. Keep your existing Pathfinder installation, TOPIx Cloud account, LSID license, and SDD setup on this machine. eLinehub adds no layer between your diagnostic software and the mapped VCI.
4. Accept an incoming order. Two connection options are available:
   
   Option A — Mechanic USB (simpler, no IP config): Select the JLR DoIP VCI as a USB device. Pathfinder discovers it via the J2534 driver. No network adapter configuration required.
   
   Option B — Mechanic Network Adapter → eLinehub Link: Select eLinehub Link as the bridging mode. Then set the eLinehub Link adapter to a static IP of 169.254.0.1, subnet mask 255.255.0.0 (no gateway). Pathfinder discovers the VCI via DoIP broadcast on this link-local network.
   
   All DoIP sessions use Relay Mode — no port forwarding or VPN required. Wait for VCI initialization before launching Pathfinder.

Before any VBF flash, CCF write, or KVM session: A mid-flash packet loss event carries the same consequences as losing local Ethernet — Pathfinder may abort the sequence and leave a module in a recovery state. Connect a battery support unit maintaining vehicle voltage at 12.5–14.5 V throughout any programming sequence. Do not attempt flash operations over a mobile hotspot or congested WiFi connection.

Connection mode: All JLR DoIP sessions — including VBF flash, CCF writes, and KVM programming via Pathfinder — use Relay Mode through the nearest eLinehub relay node. No port forwarding, no VPN configuration, and no P2P setup are required on either side.

eLinehub Link adapter IP (Network Adapter mode only): If using Mechanic Network Adapter → eLinehub Link, set the Technician’s eLinehub Link adapter to a static IP of 169.254.0.1 / 255.255.0.0 (no gateway). This is a one-time setup. Mechanic USB mode does not require any IP configuration.

VCI initialization: Wait for the JLR DoIP VCI to fully initialize on the Technician’s PC before launching Pathfinder. Opening Pathfinder before initialization completes returns a VCI discovery error and requires restarting the session.

Passcode Order Protection

Every order requires a Passcode to accept. No other specialist on the platform can pick up a workshop’s job without it. The Mechanic shares the Passcode directly with the Technician they already work with — the relationship stays private.

Custom Mechanic Software

Distribute a white-label Mechanic build permanently linked to your Technician account. Orders from that workshop are auto-assigned to you by default, with no Passcode exchange needed for routine sessions. No other specialist can claim the workshop through a white-label install.

Secure Order Sharing

For complex multi-ECU jobs — gateway programming, ADAS calibration requiring a second specialist — share a specific order with a trusted colleague. The colleague accesses only the VCI session for that order; they cannot see the Mechanic’s identity, contact details, or any other orders.