eLinehub maps physical VCI hardware from the workshop to your Windows PC over the internet. Your OEM diagnostic software — ISTA, XENTRY, ODIS, GDS2, or any J2534-compatible platform — detects the remote VCI as a locally connected device. This guide covers every step from pre-connection checks to troubleshooting common issues.
1. Preparation Before Connection
Before you initiate the connection, confirm two things:
- Software status — Both Technician and Mechanic software must be open and showing a normal network connection.
- Order status — The Technician must have accepted the remote order published by the Mechanic.
2. Device and Driver Check
Check the driver setup on both sides before initiating the connection:
Install the official driver for the VCI device you intend to connect.
- Standard USB diagnostic device — No driver installation required.
- RNDIS device — The appropriate driver must be installed before connecting.
If the device type is uncertain, install drivers on the Mechanic side as a precaution.
3. Select Mechanic Device
For privacy and security, the software automatically filters out USB devices and network adapters unrelated to diagnostics.
3.1 Select Connection Device
Choose the device type that matches your VCI and diagnostic workflow:
Maps the USB VCI on the Mechanic’s computer to your PC.
Bridges the network adapter on the Mechanic’s computer to your PC. Used for DoIP and RNDIS-based VCI devices.
Builds a virtual LAN between the two computers without mapping a specific device. For third-party USB sharing setups or virtual network links without a device mapping session.
3.2 Device Status Indicators
The device list shows the current state of each available device:
3.3 Detection Plugin
If the device you expect is not appearing in the list, a detection plugin may need to be installed. After installation, the plugin takes effect on both computers simultaneously:
- USB device not showing? — Install the USB detection plugin.
- Network adapter not showing? — Install the adapter detection plugin.
4. Select the Adapter to Bridge To
When you install eLinehub, the Technician software creates two virtual network adapters on your PC: eLinehub Link and eLinehub vNet. These appear alongside your existing physical network adapters. To bridge, you select one adapter from this list. The Mechanic’s network adapter is then mapped to whichever adapter you choose.
Three Adapters, One Choice
- eLinehub Link — Simplest and broadest coverage. One PC, no cable. Works with the vast majority of diagnostic software. Start here.
- eLinehub vNet — Same single-PC setup, no cable. For the small number of diagnostic platforms that require binding to a specific local network adapter.
- Physical Adapter — Covers every scenario, but requires a network cable and a more involved setup. This is the universal fallback for situations where virtual adapters are not sufficient: software that demands a real physical NIC, OEM online programming that runs through a VPN, or diagnostic devices that cannot install eLinehub.
Bridges the Mechanic’s network adapter to the eLinehub Link virtual adapter on your PC. The default choice for most diagnostic software — no cable required.
Bridges the Mechanic’s network adapter to the eLinehub vNet virtual adapter on your PC. Use when your diagnostic software requires binding to a specific local network adapter rather than discovering the VCI through standard network communication.
Bridges the Mechanic’s network adapter to a physical network adapter on your PC. A network cable connects this adapter to the diagnostic PC or device. Required when: the diagnostic software must use a real physical NIC, the session involves OEM online programming through a VPN client, or the diagnostic device cannot install eLinehub (Android tablets, dedicated OEM diagnostic units). For dual-machine setup and VM configuration details, see Network Adapter Bridging Technical Guide.
Whether a static IP needs to be configured on the bridged adapter depends on your diagnostic software’s requirements. Some platforms require a specific IP address to communicate with the VCI; others discover it automatically. Refer to your OEM software’s network setup instructions to determine whether a static IP is needed.
Which Adapter Should You Choose?
Answer two questions you already know the answer to — then match your row in the table:
- Question 1: Does this session require OEM online programming or a VPN connection to the manufacturer’s server?
- Question 2: Can you install eLinehub on the computer that runs the diagnostic software? (It must be a Windows PC, not a locked-down OEM unit or Android tablet.)
| Your Scenario | Bridge to This Adapter | Cable Required | Typical Software |
|---|---|---|---|
| No VPN — eLinehub installed on the diagnostic PC | eLinehub Link (Recommended) | — | BMW ISTA, Mercedes-Benz XENTRY, VW/Audi ODIS, most DoIP platforms |
| Same as above, but software requires binding to a local adapter | eLinehub vNet (Advanced) | — | Zeekr, Avatr (Chinese EV brands requiring local adapter binding) |
| Same as above, but software requires a physical network card | Physical Adapter — USB-to-Ethernet loopback on the same PC | ✓ | Chang’an, Hongqi (Chinese new-energy brands — verified) |
| No VPN — but the diagnostic device cannot install eLinehub | Physical Adapter — dedicated second PC with cable | ✓ | Tesla / Xiaomi (Android tablet), Porsche PiWIS, Mercedes dedicated diagnostic units |
| OEM online programming or VPN required — maximum stability | Physical Adapter — dedicated second PC with cable (recommended) | ✓ | Mercedes XENTRY Online, BMW online programming, JLR Pathfinder online |
| OEM online / VPN required — single-machine preferred | Physical Adapter — VM on the same PC | Optional | Multiple OEM VPNs in separate VMs |
Not listed? eLinehub Link covers the vast majority of diagnostic platforms. If your specific software has adapter-binding requirements not met by Link, move one level up — from Link to vNet, or from vNet to Physical Adapter. Each level includes the full coverage of the one below it.
OEM Software Quick Reference
For standard local and offline diagnostic sessions (no OEM VPN), this table maps common OEM software to the recommended adapter:
| OEM Software | VCI | Recommended Adapter |
|---|---|---|
| BMW ISTA | ICOM Next / ICOM A2 / ENET Cable | eLinehub Link |
| Mercedes-Benz XENTRY | SD Connect C4 / C5 / C6 / ENET Cable | eLinehub Link |
| VW / Audi / Skoda / SEAT ODIS | VAS 6154A and similar DoIP devices | eLinehub Link |
| JLR Pathfinder / SDD | JLR DoIP VCI | eLinehub Link |
| Any DoIP or RNDIS VCI (general) | — | eLinehub Link |
When the same software is used for OEM online programming (connecting to manufacturer servers through a VPN), the Physical Adapter with a dedicated second PC is recommended. See the decision table above.
5. Initiate Connection and Network Monitoring
After selecting the appropriate device and mode, choose the connection type and connect:
Routes data through eLinehub servers. Compatible with all device types. Select the server with the lowest latency from the server list.
Establishes a peer-to-peer connection with lower latency. USB devices only — does not support network adapter mapping. Requires wired connections on both sides and RTT below 80 ms.
Minimum Network Requirements
| Operation Type | Max RTT | Max Packet Loss | Connection |
|---|---|---|---|
| Diagnostics, fault reading, live data, variant coding | 150 ms | 1% | Wired or stable Wi-Fi |
| ECU flashing, SCN coding, parameterization, SFD / GeKo unlock | 50 ms | 0.5% | Wired — both sides |
Minimum upload bandwidth: 10 Mbps on both sides.
The connection panel displays real-time data for both sides: city, connection type (Wi-Fi / Wired), proxy status, latency, packet loss rate, and live network speed.
After the Connection Establishes
6. Common Problems and Troubleshooting
6.1 Initialization Takes Longer Than Expected (Normal)
Two initialization stages run automatically after the channel connects:
- System and driver initialization — Runs in the first seconds after connection. Duration depends on the hardware performance and network conditions of both computers.
- USB device mapping delay — After the channel connects, there is a brief delay before the USB device appears on your PC. This is expected.
Neither of these requires any action. Wait for the device to appear before proceeding.
6.2 Connection and Network Issues
Network lag or high latency — Disconnect and reconnect, or switch between Relay and Direct mode.
USB mapping failed
- With a Windows error code — Click the error code to view the official Windows explanation page and follow the resolution steps.
- Repeatedly stuck in “Mapping to Technician side” status — Work through these steps in order:
- Disconnect and retry.
- Restart both the Technician and Mechanic software, then retry.
- Restart both computers, then retry.
- Check whether any other USB sharing software is installed on either computer. If so, uninstall it, restart, and retry.
- If you prefer not to uninstall, switch to No Device (Build LAN) mode and use it alongside your existing USB sharing software.
Technician cannot access the internet after connecting — When the connected VCI device or vehicle exposes a gateway, it can override the Technician’s default internet route. The diagnostic connection itself remains unaffected.
Use the Switch button in the system panel to toggle between two modes:
- Diagnostic priority mode — Optimized for vehicle communication.
- Internet access mode — Restores normal internet access.
6.3 Detection Plugin Installation Conflict
If a software conflict is detected during USB plugin installation, eLinehub will attempt to remove the conflicting software automatically. If automatic removal fails, manually uninstall the conflicting program, restart the computer, and open eLinehub again to reconnect.
7. Technical Support
For issues not covered above, contact the support team at support@elinehub.com.