How to Set Up a Remote Diagnostic Connection with eLinehub
- Mar 22
- 6 min read
Updated: Mar 28
eLinehub is a Windows-based remote vehicle diagnostics platform that maps physical VCI hardware over the internet, allowing a Technician to operate on-site diagnostic equipment as if directly connected to the vehicle. Whether you are running DoIP diagnostics, ECU programming, or Ethernet-based OEM procedures, this guide walks you through every step — from pre-connection preparation to troubleshooting common issues.
1. Preparation Before Connection
Software Status: Ensure both Technician and Mechanic software are open and the network connection is normal.
Order Status: Ensure the Technician has accepted the remote order published by the Mechanic.
2. Device and Driver Check
Before initiating the connection, please be sure to confirm the driver environment of both parties:
Technician: Must install the official driver of the device to be connected.
Mechanic:
Standard USB diagnostic device: No driver installation required.
RNDIS device: Driver must be installed.
Note: If unsure of the device type, it is recommended to uniformly install device drivers on the Mechanic side.
3. Select Mechanic Device
3.1 Select Connection Device
(For privacy and security reasons, the software automatically blocks irrelevant USB devices and network adapters)
Mechanic USB: Connect to the USB device on the Mechanic’s computer.
Mechanic Network Adapter: Connect to the network adapter on the Mechanic’s computer.
No Device (Build LAN): Build a virtual LAN between the Mechanic’s computer and the Technician’s computer; can be used in combination with third-party software.
3.2 Device Status Description
Not Shared: The Mechanic has not shared this type of device or remote desktop.
with Ethernet: This network adapter was generated by a USB device (i.e., the USB device produced a virtual network adapter as a side effect).
via USB: This USB device simultaneously generated a virtual network adapter.
Unplugged / Internet active: Indicates whether the current network adapter is plugged into a network cable, and whether the cable has network access capability.
Not supported: The network adapter does not support remote connection.
3.3 Plugin Installation Prompt
If the target device is not displayed in the list, please check if the detection plugin needs to be installed (after clicking install, it takes effect on both computers simultaneously):
USB not showing? Install detection plugin
Adapter not showing? Install detection plugin
4. Network Adapter Connection Configuration (Network Adapter Connection Only)
If “Network Adapter” is selected as the connection device, please choose the bridge mode according to the specific diagnostic scenario:
eLinehub Link: Bridge the Mechanic Network Adapter to the Technician’s “eLinehub Link” virtual network adapter.
Applicable Scenario: General-purpose mode, suitable for most diagnostic software.
eLinehub vNet: Bridge the Mechanic Network Adapter to the Technician’s “eLinehub vNet” virtual network adapter.
Applicable Scenario: Used when the diagnostic software requires communication with a local network adapter.
Physical adapter: Bridge the Mechanic Network Adapter to the Technician’s Physical adapter.
Scenario 1: The diagnostic software must bind to a physical adapter, and the computer has the eLinehub software installed. After remote connection, use a network cable to connect the bridged Technician physical adapter to the physical adapter specified by the local diagnostic software.
Scenario 2: The diagnostic software communicates with the network adapter, but the computer it is on does not have the Technician eLinehub software installed. After remote connection, use a network cable to connect the bridged Technician physical adapter to the computer running the diagnostic software.
5. Initiate Connection and Network Monitoring
After selecting the appropriate transmission mode, you can initiate the connection:
Relay (Recommended): High data transmission stability, compatible with all devices. Please select the server with the lowest latency from the list.
Direct (P2P): Low data transmission latency; USB devices only. If the Relay mode has high latency or slow network speed, you can try switching to this mode.
After the connection is established, the system panel will display in real time the monitoring data such as cities of both parties, network type (WiFi/Wired), proxy status, latency, packet loss rate, and real-time network speed.
6. Common Problems and Exception Troubleshooting
6.1 Initialization Time-consuming (Normal Phenomenon)
Software and Network Initialization: In the early stage of connection, system environment initialization takes a certain amount of time (depending on the hardware performance and network status of both computers).
USB Mapping Delay: After the channel connection is successful, there will be a brief delay when the USB device is mapped to the Technician computer.
6.2 Connection and Network Exceptions
Network Lag / High Latency: Please try disconnecting and reconnecting, or switch the connection mode (Relay/Direct).
USB Mapping Failed:
With Windows error code: Click the error code, view the official Windows explanation page, follow the guidelines to resolve it, and try again.
Repeatedly stuck in the “Mapping to Technician side” status, please follow these steps in order:
Disconnect and retry;
Restart 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 in combination with your existing USB sharing software.
Technician cannot access the internet: When the connected device or vehicle has a gateway, it may cause the Technician’s internet access to be interrupted (but the diagnostic connection is normal).
The “Switch” button toggles between two modes: diagnostic priority mode (optimized for vehicle communication) and internet access mode (restores normal internet access). You can click it to switch modes as needed.
Note: Do not perform any diagnostic or programming operations while switching, as it causes a brief network interruption.
If the diagnostic software runs abnormally after switching, please restart the diagnostic software; or click the “Switch” button again to restore the priority diagnostic mode.
6.3 Plugin Installation Conflict
If a software conflict is detected when installing the USB plugin, the eLinehub installer will attempt to automatically remove the conflicting software. If automatic removal fails, the user needs to manually uninstall the conflicting program, restart the computer, and then open the eLinehub software to connect.
7. Technical Support
If you encounter unresolved technical issues, please email our customer service: Support@elinehub.com, and we will reply as soon as possible.
Frequently Asked Questions
What is the difference between Relay and Direct (P2P) connection modes?
Relay mode routes data through eLinehub’s servers, offering maximum stability and compatibility with all device types. Direct (P2P) mode establishes a lower-latency peer-to-peer connection, but is only available for USB devices. If Relay mode exhibits high latency or slow speeds, switching to Direct is recommended where supported.
Do I need to install drivers on the Mechanic’s computer?
For standard USB diagnostic devices, no driver installation is required on the Mechanic side. For RNDIS devices, the appropriate driver must be installed. If the device type is uncertain, it is safest to install drivers on both sides before connecting.
What bridge mode should I use for DoIP diagnostics?
eLinehub Link is the recommended general-purpose mode and is suitable for most DoIP and Ethernet-based diagnostic scenarios. Only switch to eLinehub vNet if your diagnostic software requires communication with a local network adapter.
Why did the Technician lose internet access after connecting?
If the connected VCI device or vehicle exposes a gateway, it can override the Technician’s default internet route. Use the Switch button in the system panel to toggle between diagnostic priority mode and internet access mode as needed. Avoid performing diagnostic or programming operations during the switch.
What should I do if USB mapping keeps getting stuck?
First restart both the Technician and Mechanic computers. If the issue persists, temporarily disable or uninstall any antivirus software, as it may be intercepting the USB mapping process.
What if the detection plugin installation triggers a conflict warning?
The eLinehub installer will attempt to automatically remove the conflicting software. If it cannot do so, manually uninstall the conflicting program, restart your computer, then reopen eLinehub and proceed with the connection.
Start Your First Remote Diagnostic Session
Ready to connect? Download the eLinehub software, accept a remote order, and follow the steps in this guide to run your first remote diagnostic session — no additional hardware required on the Technician side.
