Honda · Acura · i-HDS · Honda Antares Capsule · J2534 Rewrite · Honda Sensing

Honda / Acura i-HDS Remote Programming:
Antares Capsule Mapped to Your Technician PC

CoversAll Honda & Acura (2002MY+)Prologue & ZDX: see GM MDI 2 page

The Honda Antares Capsule must appear as a local USB device on the machine running i-HDS and J2534 Rewrite — ECM/PCM replacement, IMMO registration, CVT TCM programming, and Honda Sensing calibration all have this hard requirement. eLinehub maps the HAC at the Mechanic’s workshop to your Technician PC at the USB device and driver level. i-HDS and HAC Device Manager find it as a locally connected device, your VSP credentials run the IMMO registration from your machine, and J2534 Rewrite communicates through the same driver path it uses with a physically connected HAC.

  • HAC mapped at driver level via USB — i-HDS and HAC Device Manager discover it through the standard driver path, no configuration changes required
  • IMMO registration, J2534 Rewrite, and Honda Sensing calibration all run from your PC with your own i-HDS subscription and VSP credentials
  • The workshop installs only eLinehub Mechanic (free) — no i-HDS license, no VSP registration at the workshop
Download Technician Software — Free TrialDownload for Mechanics — Free

The workshop connects the HAC and the vehicle. You bring i-HDS and VSP credentials. eLinehub provides the bridge. · By eLinehub ·

Who uses this page
Independent Diagnostic Technician
You hold an active i-HDS subscription and NASTF VSP credentials, and want to perform remote ECM/PCM replacement, CVT TCM programming, J2534 Rewrite updates, and Honda Sensing calibration for workshops that have the HAC but no i-HDS license.
Tool, Parts & Training Provider
You supply Honda Antares Capsule hardware, OEM replacement ECMs, TCMs, or ADAS sensor components, and want to bundle remote i-HDS programming as a post-sale service without requiring a full i-HDS setup at every customer workshop.
Repair Shop Chain or Fleet Operator
You operate multiple Honda and Acura service bays or collision centers and need centralized remote ECU programming and Sensing calibration without stationing a VSP-credentialed i-HDS specialist at each site.
1 — i-HDS Requirements

Why Honda and Acura Repairs Require i-HDS — Not Just a Scan Tool

On Honda and Acura, replacing a module or repairing ADAS hardware is the mechanical half of the job. The vehicle will not start, shift correctly, or pass legal safety checks until i-HDS completes the associated software-dependent procedures. No aftermarket tool can complete immobilizer registration, transfer A/T ID data, or run Honda Sensing calibration.

The four job types below cover the most common cases where i-HDS with a locally recognized J2534 VCI is the only path to completion.

ECM/PCM Replacement — IMMO Registration and J2534 Rewrite

Civic · Accord · CR-V · HR-V · Pilot · Odyssey · Acura MDX, RDX, TLX (2002MY+)

Unlike a mechanical engine component, a replacement ECM or PCM on any 2002 and later Honda or Acura requires three software-dependent steps before the vehicle will run. i-HDS must push any pending calibration and firmware via J2534 Rewrite, transfer engine oil life data and A/T ID characterization data from the original unit, and complete immobilizer registration. Honda’s IMMO access requires NASTF Vehicle Security Professional (VSP) credentials tied to the performing technician’s identity. A shop without an active i-HDS subscription and VSP registration cannot complete this procedure; the vehicle will not start.

CVT TCM Replacement — A/T ID Characterization Data Transfer

Civic 10G+ · Accord 10G+ · CR-V 5G+ (CVT-equipped variants)

Unlike most automatic transmission modules, the Honda CVT TCM ships without A/T ID characterization data matched to the specific powertrain it will serve. i-HDS reads that data from the existing ECM via the Replace TCM/PCM menu and writes it into the new unit before the vehicle can be driven. Without this transfer, shift quality is abnormal from the first drive and the vehicle throws transmission codes. There is no aftermarket-tool path for this data transfer on Honda CVT platforms.

Honda Sensing Recalibration — Radar and Camera (MCU)

CR-V 5G+ · Accord 10G+ · Civic 10G+ (Sensing-equipped; required after any front-end disturbance, windshield replacement, or airbag deployment)

Unlike warning systems that alert the driver to a sensor fault, Honda’s millimeter-wave radar and Multipurpose Camera Unit (MCU) continue operating after misalignment — activating CMBS on phantom targets with no indicator to the driver. Recalibration is required whenever the front bumper area is disturbed, the windshield is replaced, or an airbag deploys. Each sensor requires a separate calibration routine run through i-HDS with the appropriate calibration target. Collision shops cannot legally return these vehicles without completing both calibrations; i-HDS is the only OEM-path tool for Honda Sensing.

J2534 Rewrite — Service Bulletin Firmware Updates

All Honda and Acura (ECM · ABS · VSA · all J2534-reprogrammable modules)

Unlike generic scan-tool updates, Honda service bulletin firmware updates for ECM, ABS, VSA, and other reprogrammable control units have no aftermarket-tool path. i-HDS J2534 Rewrite identifies the installed calibration version on the target module, downloads the update if a newer version is available from Honda’s servers, and applies it over the connected J2534 VCI. Without an active i-HDS subscription and a J2534 VCI recognized as a local device on the Technician’s machine, these updates cannot be completed.

Platform scope note: 2024 and later Honda Prologue and Acura ZDX use a GM-derived platform and require GM Techline Connect with SPS2 — not i-HDS. All other Honda and Acura vehicles use i-HDS with a J2534 VCI.

2 — HAC USB Device Mapping

How eLinehub Maps the Honda Antares Capsule to Your i-HDS Session

Unlike screen-sharing tools, which move the display of a session running at the workshop, eLinehub maps the HAC hardware itself at the driver and OS level on the Technician’s PC. The Mechanic connects the HAC via USB; eLinehub carries the full USB device connection across the internet. HAC Device Manager and i-HDS on the Technician’s machine find the remote HAC through the standard driver path — the same path they use for a physically connected device.

Driver-Level Mapping — No i-HDS Configuration

Unlike approaches that require software configuration or pass-through layers, eLinehub maps the HAC at the driver and OS level so HAC Device Manager and i-HDS recognize it through the standard driver path — identical discovery behavior to a physically connected device. No changes to i-HDS settings or HAC Device Manager are needed.

VSP Session Stays on Technician PC

IMMO registration requires NASTF VSP credentials tied to the performing technician. Because i-HDS runs on the Technician’s own PC — not the workshop PC — the VSP identity check runs normally. The workshop has no need for VSP credentials or an i-HDS subscription.

Relay and P2P Both Available

Both Relay mode and P2P (Direct) mode are available for USB-mapped HAC sessions. Relay mode routes through eLinehub’s infrastructure and is the default recommendation for J2534 Rewrite and IMMO sessions. P2P reduces RTT by approximately 10–30 ms when both endpoints are on wired connections; check RTT and packet loss before selecting either mode.

Screen Sharing vs Hardware Relay vs eLinehub

CapabilityScreen Sharing OnlyHardware Relay DeviceeLinehub
HAC recognized as local USB device✗ HAC stays at workshopVaries✓ Mechanic USB mode
i-HDS runs on Technician’s PC✗ i-HDS runs on workshop PC
VSP credentials from Technician’s PC✗ Workshop must hold VSP accountVaries
J2534 Rewrite stable for ECM flashInconsistent✓ Relay mode (default)
P2P low-latency mode availableN/AN/A✓ When RTT < 80 ms, both wired
Workshop needs i-HDS or VSP credentialsYes — i-HDS runs at workshopRequired for most setups✓ No — Mechanic software only
Per-session billing, no hardware costN/A✗ Hardware purchase required
← scroll to compare all three approaches →
3 — Real Job Workflows

Three Honda / Acura Remote Programming Scenarios

Each scenario starts from the point where the mechanical work is done and the HAC is available at the workshop PC.

A

ECM/PCM Replacement and IMMO Registration — Civic or Accord

Primary audience: Independent diagnostic technician with i-HDS + VSP credentials; workshop or body shop that has the HAC but no i-HDS subscription.

Mechanic Side
  1. Connect the HAC to the vehicle OBD-II port and to the workshop PC via USB cable. Open HAC Device Manager — confirm the HAC appears under USB Capsule. In eLinehub Mechanic, confirm the HAC is listed as an available device and publish the order. Notify the Technician that the replacement ECM is installed and the vehicle is ready.
  2. After the Technician accepts and the session is live, follow any instructions during the session — you may be asked to cycle the ignition or confirm a dashboard indicator at specific steps.
Technician Side
  1. Accept the order. In eLinehub Technician, select Mechanic USB. Confirm packet loss is 0% and RTT is under 80 ms. Wait for HAC initialization to complete in HAC Device Manager before launching i-HDS.
  2. Launch i-HDS. Navigate to PGM-FI → Replace ECM/PCM Menu → Read Data to transfer engine oil life data to the replacement ECM. Then navigate to A/T system → Replace TCM/PCM Menu → Read Data to transfer A/T ID characterization data.
  3. Write the VIN to the new module using the VIN registration function in i-HDS.
  4. Navigate to IMMOBI and complete immobilizer registration using your NASTF VSP credentials. The IMMO procedure requires a live VSP session — the vehicle will not start without completing this step.
  5. Launch J2534 Rewrite and apply any pending firmware update for the new ECM. Confirm successful completion.
  6. Run idle learn and CKP pattern learn procedures. Ask the Mechanic to confirm no active DTCs before ending the session.

One i-HDS subscription with VSP credentials can serve multiple workshops this way — each installs only eLinehub Mechanic (free) and provides the HAC and vehicle. The i-HDS license, J2534 Rewrite access, and VSP credentials remain on the Technician’s machine.

B

Honda Sensing Radar Recalibration After Collision Repair — 2021 CR-V

Primary audience: ADAS calibration specialist; collision repair shop without i-HDS. Required after front bumper disturbance, radar removal, airbag deployment, or windshield replacement.

Mechanic Side
  1. Confirm wheel alignment is complete — Honda requires four-wheel alignment before any Sensing calibration. Verify the radar mounting bracket is intact and that the replacement bumper is the ADAS-equipped variant; non-Sensing grille cutouts will cause calibration failure.
  2. Connect the HAC to the OBD-II port via USB. Confirm it appears as available in eLinehub Mechanic and publish the order. Position the radar reflector (trihedral corner target) in front of the vehicle when instructed by the Technician — exact distance and alignment will be specified on screen.
Technician Side
  1. Accept the order. Select Mechanic USB. Confirm packet loss is 0% before launching i-HDS. Navigate to the millimeter-wave radar calibration routine.
  2. i-HDS displays the required target distance and positioning specification for this CR-V variant. Instruct the Mechanic to position the trihedral reflector at the specified distance directly in front of the vehicle.
  3. Execute the calibration sequence. i-HDS communicates with the radar module through the mapped HAC, captures the calibration frame, computes the offset correction, and reports pass or fail. Calibration typically completes in under 5 minutes when the target is correctly positioned.
  4. If the windshield camera (Multipurpose Camera Unit) was disturbed during the repair, run the camera calibration sequence in the same session using the separate target setup specified by i-HDS.
  5. Confirm all Honda Sensing DTCs are cleared. Ask the Mechanic to confirm no warning lights are active before ending the session.

A single ADAS calibration specialist with an i-HDS subscription can cover multiple collision bays across a region — each shop handles vehicle positioning and calibration target setup; the specialist executes the i-HDS calibration routine remotely.

C

J2534 Rewrite Service Bulletin Update — Civic, Accord, and Acura

Primary audience: Independent i-HDS programmer handling bulletin work for shops without an i-HDS subscription. Applies to any Honda or Acura with a pending ECM, ABS, VSA, or other reprogrammable module bulletin.

Mechanic Side
  1. Confirm the applicable service bulletin number and the target control module with the Technician. Connect the HAC, Denso DST-i, Bosch MVCI, or other Honda-validated J2534 USB VCI to the OBD-II port and to the workshop PC.
  2. In eLinehub Mechanic, confirm the VCI appears as an available device and publish the order. Include the bulletin number in the order notes so the Technician can confirm the correct update before starting.
Technician Side
  1. Accept the order. Select Mechanic USB. Confirm packet loss is 0% and RTT is under 80 ms. Wired Ethernet on both sides is required for J2534 Rewrite flash sessions.
  2. Launch i-HDS and open J2534 Rewrite. Confirm the vehicle VIN. J2534 Rewrite identifies the installed calibration version on the target module.
  3. If a newer version is available, J2534 Rewrite downloads the update from Honda’s servers and applies it over the mapped VCI connection. Do not interrupt the connection during the flash.
  4. Confirm successful completion in J2534 Rewrite. Clear any update-related DTCs. Check whether additional modules are flagged in the same i-HDS session before ending.

Shops refer bulletin work to an independent specialist via eLinehub Mechanic without installing any OEM software — the shop only needs the VCI connected to the vehicle. The specialist handles the session using their own i-HDS subscription and J2534 Rewrite access.

Ready to try on a live Honda or Acura?

Free welcome Credits included — no credit card required to get started.

Download Technician Software — Free Trial
4 — Getting Started

End-to-End Setup

System requirements: Windows 10 or Windows 11 (64-bit) recommended; Windows 7 64-bit minimum. Not supported on Mac, Linux, Android, or Windows ARM.

Wired Ethernet is required on both sides for J2534 Rewrite sessions. See Section 5 for latency and bandwidth requirements.

Mechanic Side — Workshop
  1. Download and install eLinehub Mechanic on the workshop Windows PC. No i-HDS installation, no VSP credentials, and no HAC driver setup required on this machine.
  2. Connect the HAC to the vehicle OBD-II port and to the workshop PC via USB cable. Open HAC Device Manager and confirm the HAC appears under USB Capsule.
  3. In eLinehub Mechanic, confirm the HAC appears as a shareable device and publish the service order. Maintain the USB connection until the Technician confirms the session is complete.
Download for Mechanics — FreeMechanic Setup Guide →
Technician Side — You
  1. Download and install eLinehub Technician on the Windows PC where i-HDS, J2534 Rewrite, and HAC Device Manager are already installed. Windows 10 or Windows 11 (64-bit) required.
  2. Ensure HAC Device Manager and the HAC driver are installed on this PC. eLinehub will prompt you during setup if the driver is not detected. i-HDS recognition of the mapped device depends on this driver being present.
  3. Keep your existing i-HDS subscription, J2534 Rewrite access, and NASTF VSP credentials on this machine. eLinehub adds no layer between i-HDS and the VCI.
  4. Accept an incoming order. Select Mechanic USB in eLinehub Technician. Check RTT and packet loss before launching i-HDS.
  5. Use Relay mode for J2534 Rewrite and IMMO sessions — it provides the most consistent path regardless of NAT configuration. Switch to P2P only when both endpoints are on wired Ethernet and RTT is under 80 ms.
Download Technician Software — Free TrialTechnician Setup Guide →
5 — Network

Network Requirements

Honda J2534 Rewrite flash sessions are sensitive to connection interruption. A flash that loses the VCI connection mid-write can leave a module in an unrecoverable state. Both sides need a minimum 10 Mbps upload bandwidth; check RTT and packet loss in eLinehub Technician before starting any programming session.

Session TypeRTT TargetPacket LossConnection
Fault reading / scan-only diagnosticsUnder 120 msNot criticalWired or stable Wi-Fi
Honda Sensing calibration (radar / MCU camera)Under 100 ms0%Stable Wi-Fi acceptable
CVT TCM A/T data transferUnder 80 ms0%Wired recommended
ECM/PCM IMMO registrationUnder 80 ms0%Wired required
J2534 Rewrite ECM / module flashUnder 80 ms0%Wired required, both sides
← scroll to see all columns →

Wired Ethernet required for J2534 Rewrite. The HAC already connects to the workshop PC via USB as Honda requires. The remaining variable is the network path between the two machines. Wi-Fi on either endpoint introduces packet loss risk that can interrupt a flash mid-write.

Relay vs P2P mode: Relay mode routes through eLinehub’s server infrastructure and is the default recommendation for all Honda/Acura programming sessions — it provides the most consistent path regardless of NAT configuration. P2P (Direct) mode is also available for USB-mapped HAC sessions and reduces RTT by approximately 10–30 ms when both endpoints are on wired connections. Check RTT and packet loss in eLinehub Technician before selecting P2P.

If the connection drops mid-flash: Do not relaunch i-HDS or J2534 Rewrite immediately. Wait for eLinehub to re-establish the VCI mapping and confirm the device shows as connected in HAC Device Manager, then assess module status before deciding whether to retry.

6 — Hardware Compatibility

Compatible Honda & Acura VCI Hardware

eLinehub maps any J2534-1/J2534-2 compliant USB VCI that Honda has validated for i-HDS. The Mechanic uses the VCI at the workshop; the Technician installs the matching driver package on their PC. The table below lists confirmed-compatible hardware.

VCI HardwareConnection Modei-HDSJ2534 RewriteNotes
Honda Antares Capsule (HAC)USB (Mechanic USB mode)Honda-recommended. HAC Device Manager manages registration. USB Capsule mode required for eLinehub sessions.
Denso DST-iUSBPrevious Honda-approved VCI. Install DST-i J2534 driver on Technician PC.
Bosch MVCIUSBHonda-validated J2534-1/J2534-2. Install Bosch J2534 driver package on Technician PC.
Honda-validated J2534 pass-thruUSBMust be on Honda’s i-HDS VCI Application Table. Technician PC needs matching J2534 driver.
← scroll to see all columns →

2024 Honda Prologue and Acura ZDX: These vehicles use a GM-derived platform (Ultium) and require GM Techline Connect (TLC) with an SPS2 subscription, not i-HDS. eLinehub supports GM MDI 2 for TLC and SPS2 sessions; see the GM MDI 2 remote programming page for that workflow.

7 — Business Protection

Customer Protection

eLinehub is built so that the Technician’s workshop relationships stay with the Technician — not with the platform.

Passcode Order Protection

Every order requires a Passcode to accept. No other specialist on the platform can pick up a workshop’s job without it. The Mechanic shares the Passcode directly with the Technician they already work with — the relationship stays private.

Custom Mechanic Software

Distribute a white-label Mechanic build permanently linked to your Technician account. Orders from that workshop are auto-assigned to you by default, with no Passcode exchange needed for routine Honda and Acura sessions. No other specialist can claim the workshop through a white-label install.

Secure Order Sharing

For complex multi-module jobs — such as an ECM replacement followed by a Sensing calibration in the same session — you can share a specific order with a trusted colleague. They see the VCI data for that order only, not the Mechanic’s contact details or any other orders.

8 — Common Questions

Honda / Acura i-HDS Remote Programming FAQ

Eight questions covering HAC USB driver mapping, i-HDS device discovery, VSP credentials, J2534 Rewrite stability, P2P mode, compatible VCI hardware, Honda Prologue scope, and network drop recovery.

QDoes i-HDS actually detect the Honda Antares Capsule as a local USB device through eLinehub?
A
eLinehub maps the HAC at the USB device and driver layer on the Technician’s PC. The HAC Device Manager and i-HDS find the capsule as a locally connected device — because at the driver layer, it is. No i-HDS settings changes or additional plug-ins are required on either side.
QCan I perform a full ECM/PCM replacement — including IMMO registration — through an eLinehub session?
A
Full ECM/PCM replacement — VIN write, oil life and A/T characterization data transfer, IMMO registration, J2534 Rewrite firmware update, and idle learn — all run through the mapped HAC connection, provided you hold NASTF VSP credentials. The IMMO registration step requires your VSP identity; eLinehub does not affect or bypass that requirement.
QDoes J2534 Rewrite work over the mapped USB connection?
A
J2534 Rewrite communicates through the mapped HAC using the same J2534-1/J2534-2 protocol path it uses locally. Honda’s requirement — stable wired USB between the HAC and the laptop — is satisfied at the Mechanic’s workshop; eLinehub extends that physical connection over the network to the Technician’s PC.
QWe distribute J2534 VCI hardware. Can we offer Honda remote programming as an add-on to our customers?
A
A J2534 VCI reseller’s customer workshop runs eLinehub Mechanic and connects the VCI — no i-HDS installation or subscription on their end. A programming specialist holds the i-HDS account and handles the remote session. Programming capability is added to every VCI sale without requiring the customer to acquire OEM software access or NASTF credentials.
QCan one i-HDS technician handle Honda Sensing calibrations for multiple collision locations without traveling?
A
A single credentialed technician accepts calibration orders from any shop running eLinehub Mechanic with a compatible VCI connected to the vehicle. Radar and camera sessions run sequentially from one workstation — the shop handles vehicle positioning and calibration target setup, the technician executes the i-HDS calibration routine remotely. This is the central-specialist model: one i-HDS subscription covers multiple collision locations without dispatching.
QWhat Honda VCI hardware works with eLinehub besides the HAC?
A
Any J2534-1/J2534-2 compliant USB VCI on Honda’s i-HDS VCI Application Table will work — including the Denso DST-i and Bosch MVCI. The Technician’s machine needs the corresponding driver package installed for whichever VCI the Mechanic has connected. Generic J2534 pass-thru devices that completed Honda’s independent validation program are also supported.
QDoes eLinehub work for the 2024 Honda Prologue or Acura ZDX?
A
The 2024 Honda Prologue and Acura ZDX use a GM-derived platform and require GM Techline Connect with an SPS2 subscription — not i-HDS. eLinehub supports GM MDI 2 for TLC sessions separately; that workflow is covered on the GM remote programming page. For all other Honda and Acura vehicles, i-HDS with a J2534 VCI is the correct path.
QWhat should I do if the network drops during a J2534 Rewrite flash?
A
The critical step is to wait — do not relaunch i-HDS or J2534 Rewrite immediately. Wait for eLinehub to re-establish the VCI mapping and confirm the device shows as connected in HAC Device Manager, then assess module status before deciding whether to retry. Using wired Ethernet on both sides and Relay mode significantly reduces mid-flash disconnect risk.