eLinehub Remote Connection Setup Guide

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.

New to eLinehub? See the Operating Instructions for an overview of how the platform works.

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:

Technician Side

Install the official driver for the VCI device you intend to connect.

Mechanic Side

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:

Mechanic USB

Maps the USB VCI on the Mechanic’s computer to your PC.

Mechanic Network Adapter

Bridges the network adapter on the Mechanic’s computer to your PC. Used for DoIP and RNDIS-based VCI devices.

No Device (Build LAN)

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:

Not SharedThe Mechanic has not shared this device type.

with EthernetThis network adapter was generated by a USB device — the USB VCI produced a virtual network adapter as a side effect.

via USBThis USB device simultaneously generated a virtual network adapter.

Unplugged / Internet activeWhether the network adapter currently has a network cable connected, and whether that cable has internet access.

Not supportedThis network adapter does not support remote connection.

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. Network Adapter Connection Configuration

This section applies only when Mechanic Network Adapter is selected as the connection device.

Select the bridge mode based on which OEM diagnostic software you are running:

eLinehub LinkDefault

Bridges the Mechanic network adapter to the eLinehub Link virtual adapter on your PC. The correct starting point for most diagnostic software. If you are unsure which mode to use, start here.

eLinehub vNet

Bridges the Mechanic network adapter to the eLinehub vNet virtual adapter on your PC. Use when your diagnostic software requires communication with a specific local network adapter rather than auto-discovering the device.

Physical Adapter

Bridges the Mechanic network adapter to a physical network adapter on your PC — for setups where the diagnostic software must bind to a physical NIC on the same machine, or when the software runs on a separate computer.

Common OEM Software Bridge Mode Reference

OEM Software	VCI	Recommended Mode
BMW ISTA	ICOM Next / ICOM A2	eLinehub Link
Mercedes-Benz XENTRY	SD Connect C4 / C5 / C6	eLinehub Link
VW / Audi / Skoda / SEAT ODIS	VAS 6154A and similar DoIP devices	eLinehub Link
Any DoIP or RNDIS VCI (general)	—	eLinehub Link (default)
Software requiring specific local adapter binding	—	eLinehub vNet
Software requiring a physical network card	—	Physical Adapter

If your software or VCI is not listed, eLinehub Link is the correct starting point for all standard DoIP setups.

5. Initiate Connection and Network Monitoring

After selecting the appropriate device and mode, choose the connection type and connect:

RelayRecommended

Routes data through eLinehub servers. Compatible with all device types. Select the server with the lowest latency from the server list.

Direct (P2P)USB Only

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

Wait for VCI initialization before launching your OEM software. The device should appear as connected in your software’s device list before you start a session. Starting the software before initialization finishes is the most common cause of VCI recognition failures on first connection.

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:
1. Disconnect and retry.
2. Restart both the Technician and Mechanic software, then retry.
3. Restart both computers, then retry.
4. Check whether any other USB sharing software is installed on either computer. If so, uninstall it, restart, and retry.
5. 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.

Do not perform any diagnostic or programming operations while switching. Switching causes a brief network interruption. If the diagnostic software behaves abnormally after switching, restart it, or click Switch again to return to diagnostic priority mode.

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.

Frequently Asked Questions

QWhat is the difference between Relay and Direct (P2P) connection modes?

Relay routes data through eLinehub servers and is compatible with all device types. Direct (P2P) establishes a peer-to-peer connection with lower latency, but applies to USB devices only, requires wired connections on both sides, and requires RTT below 80 ms. If Relay latency is acceptable for your workflow, Relay is the simpler and more reliable choice.

QDo I need to install drivers on the Mechanic’s computer?

For standard USB diagnostic devices, no driver installation is needed on the Mechanic side. For RNDIS devices, the appropriate driver must be installed before the session starts. If the device type is uncertain, install drivers on the Mechanic side as a precaution.

QWhich bridge mode should I use for BMW ISTA or Mercedes-Benz XENTRY?

Both BMW ISTA (with ICOM Next or ICOM A2) and Mercedes-Benz XENTRY (with SD Connect C4/C5/C6) use eLinehub Link. This is the general-purpose mode for most DoIP and Ethernet-based diagnostic platforms. Switch to eLinehub vNet only if your software requires binding to a specific local network adapter.

QWhy did I lose internet access on the Technician side after connecting?

When the connected VCI or vehicle exposes a gateway, it can override your default internet route. The diagnostic connection itself stays active. Use the Switch button in the system panel to toggle between diagnostic priority mode and internet access mode. Avoid switching during an active diagnostic or programming operation.

QWhat should I do if USB mapping keeps getting stuck?

Restart both the Technician and Mechanic software and retry. If the problem continues, check whether any other USB sharing software is installed on either computer — conflicts with other USB sharing tools are the most common cause. Uninstall the conflicting software, restart both computers, and retry. If uninstalling is not an option, switch to No Device (Build LAN) mode and use it alongside your existing USB sharing software.

QWhat if the detection plugin installation triggers a conflict warning?

eLinehub will attempt to remove the conflicting software automatically. If that fails, manually uninstall the conflicting program, restart your computer, then reopen eLinehub and connect.

QHow long should I wait after connecting before launching OEM diagnostic software?

Wait until the VCI appears as connected in your OEM software’s device list. The first few seconds after the channel connects are used for system and driver initialization — the duration varies with hardware and network conditions. Launching the software before initialization finishes is the most common cause of VCI recognition failures on first connection.

QWhat are the network requirements for ECU programming sessions?

For ECU flashing, SCN coding, SFD token operations, and GeKo unlock sessions: RTT below 50 ms, packet loss below 0.5%, wired connections on both sides. For standard diagnostics, fault reading, and live data: RTT below 150 ms, packet loss below 1%. Both sides need a minimum of 10 Mbps upload bandwidth.

QCan I use P2P mode when connecting via network adapter?

No. P2P (Direct) mode applies to USB device connections only. Network adapter bridging — eLinehub Link, eLinehub vNet, or Physical Adapter — always uses Relay mode.

QWhat is "No Device (Build LAN)" mode used for?

This mode builds a virtual LAN between the two computers without mapping a specific device. It is designed for use alongside third-party USB sharing software, or when a virtual network link is needed without a device mapping session.

How to Set Up a Remote Diagnostic Connection with eLinehub