Download eLinehub — Technician and Mechanic Software for Windows

Q: Do I need to install a VCI driver on the Technician or Mechanic PC?

Technician PC: always install the VCI manufacturer driver — required for all VCI types so OEM software can enumerate the mapped device. Mechanic PC: standard USB J2534 devices and ENET cables do not require a driver. RNDIS-based VCIs (such as the JLR DoIP VCI, which presents as a USB network adapter) do require the driver on the Mechanic PC. If unsure, install the driver on the Mechanic PC — it causes no problems if the device does not need it.

Run ISTA, XENTRY, ODIS, SPS2 and FDRS on any workshop’s VCI over the internet. Not remote desktop. No hardware relay box.

No credit card required for trial

Mechanic software is free to use

Windows 7+ (64-bit) — Windows only

Technician Software

Run ISTA, XENTRY, ODIS, SPS2 and FDRS on any workshop’s VCI over the internet — the mapped VCI appears on your PC as a locally connected device.

Free trial includes Credits for complete ECU programming and coding sessions.

Download

Mechanic Software

Share your VCI securely with a remote Technician. The workshop keeps the vehicle, the VCI and all customer relationships.

Free to use. No account required for basic use.

Download

First-time workflow

Technician

1.

Install eLinehub Technician Software and sign in.

2.

Accept the incoming order via Passcode.

3.

Select the shared VC and initiate the connection, then launch your OEM software.

Technician Complete Guide

Mechanic

1.

Connect the VCI to the vehicle OBD port and to the On-Site PC.

2.

Install eLinehub Mechanic software and create an order with vehicle details.

3.

Provide the generated Passcode to the Technician.

Mechanic Complete Guide

Screenshots

How eLinehub Works

Topology diagram showing a physical VCI connected to the on-site workshop PC, mapped through eLinehub over the internet to appear as a local USB or Ethernet device on the remote Technician's PC.

The workshop VCI — USB J2534 or Ethernet/DoIP — is mapped to the Technician's PC as a local device. OEM software on the Technician PC enumerates it exactly as it does on a local bench: same device ID, same Ethernet adapter behavior, same protocol timing.

Technician Software Screenshots

Technician Software Installation

The installation interface of eLinehub Technician Software, showing the setup process required before accepting remote diagnostic orders and connecting to a workshop's shared VCI.

Mechanic Software Screenshots

Mechanic Software Installation

The installation interface of eLinehub Mechanic Software, showing the setup process for preparing the on-site workshop PC.

Frequently Asked Questions

Q: Is eLinehub free to download?

Yes. Both Technician and Mechanic software are free to download. Mechanic software is free to use with no restrictions. Technician software includes a free trial with Credits for complete ECU programming and coding sessions — no credit card required.

Q: Does the workshop PC need XENTRY, ISTA or ODIS installed?

No. The workshop only needs eLinehub Mechanic installed and a VCI connected to the vehicle via USB or wired Ethernet. All OEM software, licenses and online accounts stay exclusively on the Technician PC.

Q: Which VCIs does eLinehub support?

All J2534 PassThru devices (VAS6154A, CarDAQ-Plus 3, VCM3, MDI2 and equivalents), Ethernet-based VCIs via Virtual Bridge (BMW ENET, SD Connect C4/C6, JLR DoIP VCI, ICOM), and RNDIS USB-Ethernet adapters. If the VCI has a working driver on Windows and connects locally, eLinehub can map it remotely.

Q: Do I need to install a VCI driver on the Technician or Mechanic PC?

Technician PC: Always install the VCI manufacturer driver. This is required regardless of VCI type — eLinehub presents the mapped VCI as a local device, and the OEM software (ISTA, XENTRY, ODIS, SPS2, etc.) needs the driver to enumerate it correctly.

Mechanic PC: Depends on the VCI type.

Standard USB J2534 devices (VAS6154A, MDI2, VCM3, CarDAQ-Plus 3 and similar): driver not required on the Mechanic PC.
ENET cables (BMW ENET and similar): driver not required on the Mechanic PC.
RNDIS VCIs (devices that appear as a USB network adapter on Windows, such as the JLR DoIP VCI): driver required on the Mechanic PC.
Not sure which type your VCI is? Install the manufacturer driver on the Mechanic PC — it causes no problems if the device does not need it, and prevents the connection from failing if it does.

Q: What is Build LAN and when should I use it?

Build LAN creates a virtual LAN between the Technician and Mechanic sides. It is designed for workflows that require network-layer access to the vehicle or VCI rather than a J2534 or DoIP API.
For example, if you already use a LAN-based USB redirection tool to map USB devices over a local network, Build LAN lets you keep using that same software remotely — the Technician and Mechanic appear on the same virtual LAN, so the USB redirection tool works exactly as it would in a local workshop.

Release Notes

V1.7.2 — 5/10/2026 (Latest)

Significantly faster connections, with up to 5× speed improvement on low-end devices
USB plugin installation is now smoother and compatible with existing USB software on your device, with fewer unnecessary restarts
Improved USB dongle mapping compatibility, resolving function loss affecting select dongle models
New dual-channel VCI support combining USB device mapping and network adapter bridging simultaneously, compatible with BYD, Bosch, and more
New Build LAN mode creates a virtual local area network between the Technician and Mechanic, enabling seamless integration with your existing USB sharing software for greater flexibility
Redesigned subscription experience: plan details are now easier to compare, Custom Mechanic Software is available as a standalone subscription, flexible monthly and annual billing options are now available, and the subscription flow is more streamlined