top of page

eLinehub Operating Instructions — Remote Automotive Diagnostics & Programming

  • Mar 25
  • 3 min read



What Is eLinehub?

eLinehub is a pure-software remote automotive diagnostics and programming solution. It works by mapping a Mechanic’s physical VCI (Vehicle Communication Interface) to a Technician’s computer over the network — so the Technician’s OEM diagnostic or ECU programming software sees the remote VCI as a locally connected device, with no hardware relay device required on either side.

The Mechanic is on-site at the vehicle. They connect the VCI to the vehicle and their local PC, then publish a session order through the Mechanic software. The Technician is remote. They accept the order, select the device to map, and run diagnostics or ECU programming from their own computer — using the same OEM software they would use locally.



How It Works

Which mapping method eLinehub uses depends on how the VCI communicates with the host PC:


  • USB Mapping: The Mechanic’s USB VCI is mapped to the Technician’s computer as a local USB device. This covers most USB-based VCI hardware.

  • Network Adapter Bridging: For VCIs that communicate via a network adapter — including DoIP (Diagnostics over IP) devices and RNDIS-class adapters — eLinehub bridges the Mechanic’s network adapter to the Technician’s computer. This is the method used for Ethernet-based diagnostic protocols such as DoIP (ISO 13400).

The Mechanic does not need diagnostic software installed. The Technician does not need any local VCI hardware.



System Requirements

  • Windows 7 or later, 64-bit. Windows 10 / 11 recommended.

  • Windows ARM, Mac, Linux, and Android are not supported.

  • Mechanic and Technician software can be installed on the same computer, but only one instance can run at a time.



Pre-Connection Preparation

Network Environment

  • Both sides require a minimum upload speed of 10 Mbps.

  • Wired connection is strongly recommended on both sides, particularly for ECU programming sessions where connection stability matters.

  • Some OEM diagnostic software enforces strict communication timing — lower latency generally produces more reliable device recognition and session behavior.

Mechanic Side

  • Connect the VCI to the vehicle and to the local PC.

  • Standard USB diagnostic devices do not require driver installation.

  • RNDIS-based devices (VCIs that appear as a network adapter on the host PC) require the corresponding driver. If unsure of the device type, install the driver to be safe.

Technician Side

  • Install the OEM or professional diagnostic software.

  • Install the driver that matches the VCI model being used on the Mechanic side.



Session Workflow

  1. The Mechanic opens the Mechanic software and publishes an order.

  2. The Technician accepts the order in the Technician software.

  3. The Technician selects the remote device and connection method, then initiates the connection.

  4. After the connection is established, wait for the VCI to complete initialization before launching the diagnostic software. This typically takes under 2 minutes depending on network conditions.

  5. The Technician proceeds with diagnostics or ECU programming as normal.

Note on plugins: USB device detection requires a plugin that can be installed directly within the software. If a software conflict is detected during installation, eLinehub will prompt you and attempt to resolve it automatically. If automatic resolution fails, you will be guided to handle it manually before proceeding.

For guidance on device selection, bridge mode options, and connection troubleshooting, open the Technician software and click the ⓘ icon in the Remote Connection panel.



Get Started

Download eLinehub and set up your first remote diagnostic session: https://www.elinehub.com/download



Technical Support

 
 
bottom of page