eLinehub Technician User Guide: Remote Diagnostics Workflow

Securely receive orders, connect to remote VCIs, and perform advanced diagnostics and ECU programming with the official eLinehub Technician User Guide.

eLinehub is a pure-software remote automotive diagnostics platform. It maps a Mechanic’s physical VCI — whether USB-based or Ethernet/DoIP-based — directly to your computer as a locally connected device, so you can run your OEM diagnostic software exactly as if the hardware were sitting in front of you. No hardware relay boxes, no remote desktop workarounds. This guide covers the complete Technician workflow, from installation through completing an order.

Step 1: Download and Install

Open your browser and visit the official eLinehub website. Download the latest Technician installer. Once the download completes, run the file and follow the on-screen prompts to finish installation.

Step 2: Create Your Account

When you open the software for the first time, you’ll complete a brief registration:

1. Enter your email address and click Continue. A six-digit verification code will arrive in your inbox within a few seconds — enter it and submit.

2. Fill in your profile details. Select your country first — this setting cannot be changed later. Then choose your state, the car brands you work with, and your certification types.

3. Your email is set as your default username by default, but you can change it and add a profile photo. Review and accept the user agreement, then click Confirm to complete registration.

Step 3: Language Settings

The eLinehub Technician client supports multiple interface languages, including German, French, Russian, Spanish, Traditional Chinese, and more. To switch languages, open the Settings menu and select your preference from the dropdown.

Step 4: Before You Connect

Completing these checks on both sides beforehand eliminates the most common causes of failed or unstable connections.

Network Requirements

Both the Technician and Mechanic need a minimum upload speed of 10 Mbps. A wired Ethernet connection is strongly recommended on both ends — especially during ECU programming sessions. DoIP and other Ethernet-based diagnostic protocols enforce strict application-layer communication timing, and wireless connections can introduce variable latency and packet loss that trigger unexpected session drops.

Driver Installation

• Technician side: Install the official driver for the specific VCI model the Mechanic will be using. Without the correct driver, the device will not be recognized on your computer even after a successful connection is established.

• Mechanic side: Standard USB diagnostic devices do not require driver installation. RNDIS-based devices — those that present themselves as a virtual network adapter — require the corresponding driver. If the device type is unclear, install the driver to be safe.

Step 5: Receive Orders and Communicate

eLinehub uses a privacy-focused order system to keep customer and vehicle information from being exposed publicly. You can receive diagnostic requests in two ways:

• Passcode Order: The Mechanic generates a unique Passcode when publishing an order. Enter this Passcode in the software to claim and bind the job to your account.

• Team Mode: If you belong to a dedicated Technician Team, private orders assigned to the team will appear in your dashboard automatically — no Passcode required.

Once you’ve accepted an order, use the built-in Live Chat to discuss vehicle symptoms and service scope with the Mechanic before you begin.

Step 6: Establish the Remote Connection

When the Mechanic marks the order status as Ready, select it to open the connection setup panel.

6.1 Select the Device

Choose the specific device on the Mechanic’s computer to connect to:

• Mechanic USB — Connects to a USB-type VCI. Used for traditional CAN, K-Line, and J2534 Pass-Thru devices.

• Mechanic Network Adapter — Connects to a network adapter on the Mechanic’s machine. Used for DoIP-based VCIs and RNDIS devices.

• No Device (Build LAN) — Establishes a virtual LAN between both computers without attaching a device. Useful when combined with third-party diagnostic routing software.

If no devices appear in the list, click Refresh. If the target device still doesn’t show up, the software will display a prompt to install the detection plugin — click to install, and it will take effect on both computers simultaneously.

6.2 Configure Bridge Mode (Network Adapter connections only)

If you selected Mechanic Network Adapter, you must also choose how it is bridged to your computer. Select the mode that matches your diagnostic software’s network requirements:

• eLinehub Link — Bridges the Mechanic’s adapter to a virtual eLinehub Link adapter on your computer. This is the standard choice for most remote diagnostic scenarios, including DoIP-based workflows. Compatible with ISTA (BMW), XENTRY (Mercedes-Benz), Pathfinder (JLR), and similar OEM platforms.

• eLinehub vNet — Use this when your diagnostic software requires binding to a fixed IP address. After connecting, set your physical network adapter to obtain an IP automatically, then assign the required fixed IP to the eLinehub vNet adapter instead.

• Physical adapter — Bridges the Mechanic’s adapter to one of your physical NICs. Use this when your diagnostic software must bind specifically to a physical adapter, or when it runs on a separate computer that does not have the Technician software installed. After connecting, use a network cable to link the bridged adapter to the appropriate machine.

6.3 Select Transmission Mode

• Relay (Recommended) — Routes data through an eLinehub relay server. Compatible with all device types — both USB and network adapters. Select the server with the lowest latency from the list. For DoIP diagnostics, latency directly affects session stability: always choose the geographically closest server and verify the displayed latency is consistently low before launching your diagnostic software.

• Direct (P2P) — Establishes a peer-to-peer connection directly between both computers. Typically offers lower latency than Relay, but is limited to USB-type devices only. If Relay mode shows persistently high latency or poor throughput in your region, switch to Direct.

Click Connect to proceed.

6.4 Connection Startup

After clicking Connect, the system runs a brief initialization. The interface will display sequential status messages such as “Initializing…” and “Mapping to the Technician side…” This is normal. Do not interrupt the process or close the software during this stage.

Once ready, the connection lines between Mechanic PC and Me turn green. The software then displays a live Network Connection Status panel showing the network type (Ethernet, Wi-Fi, or Mobile Hotspot) for both parties, latency, packet loss rate, real-time speed, and total data transferred.

Allow a few seconds after the lines turn green before launching your diagnostic software — this gives the VCI time to complete device initialization on your side.

6.5 Internet Access Interruption

When the connected VCI or vehicle has an active gateway, your internet access may be interrupted while the diagnostic connection itself remains fully functional. This is expected behavior caused by routing priority, not a connection failure.

The Switch button in the connection panel toggles between two modes:

• Diagnostic Priority Mode — Optimized routing for vehicle communication.

• Internet Access Mode — Restores normal internet access on your computer.

Do not perform any diagnostic or programming operations while switching, as this causes a brief network interruption. If your diagnostic software behaves abnormally after switching, restart it — or click Switch again to return to Diagnostic Priority Mode.

Step 7: Launch Diagnostic Software

With the connection lines green and the network status panel showing stable readings, you can treat the setup as a local connection.

Open your OEM or professional diagnostic software — ISTA, ODIS, XENTRY, SDD, Pathfinder, or any J2534-compatible application. eLinehub’s USB redirection and network routing layer presents the remote VCI to your operating system as a locally attached device. Your diagnostic software operates with no awareness that the hardware is remote.

You can now perform all vehicle diagnostics, ECU programming, coding, and adaptation operations exactly as you would with a local setup.

Step 8: Complete the Order

When the session is finished, click Complete Order in the eLinehub software. The Mechanic receives a prompt to review and confirm. If the Mechanic does not respond within the timeout window, the system closes the order automatically. All past jobs are available under Order History.

Troubleshooting

Symptom	Most Likely Cause	Action
No devices visible in list	Detection plugin not installed	Click the install prompt shown in the device panel; installs on both sides simultaneously
Device listed but won’t connect	VCI driver missing on Technician side	Install the correct OEM driver for the VCI model and reconnect
High latency / frequent session drops	Network environment or relay server	Switch to a lower-latency relay server; switch both sides to wired; if USB-only, try Direct (P2P)
Connection stuck on “Mapping to Technician side”	Driver conflict or antivirus interference	Restart both computers; temporarily disable antivirus software; retry
USB mapping failed with Windows error code	Windows driver or hardware conflict	Click the error code to view the official Windows guidance; resolve as directed
Internet access lost during session	Vehicle or VCI gateway routing conflict	Use the Switch button to toggle between Diagnostic Priority and Internet Access modes
Plugin installation fails or conflicts	Conflicting software present on the system	eLinehub will attempt automatic removal; if it fails, manually uninstall the conflicting program, restart, and reconnect

For issues not covered above, contact the support team at support@elinehub.com.