Mercedes-Benz DoIP Remote Diagnostics: XENTRY Programming Without SD Connect — eLinehub
When the workshop you’re connecting to has no SD Connect, an ENET cable is all the hardware they need on their end. XENTRY runs on your PC — SCN coding, ECU flash and SOC commissioning on DoIP-generation Mercedes vehicles. No hardware relay box. No remote desktop.
If you hold XENTRY and a Mercedes Online account and the workshop you’re connecting to doesn’t have an SD Connect, this page covers how to get the job done. On DoIP-platform vehicles — W206, W223, EQE, EQS, Sprinter W907 — an ENET cable at the workshop is the only VCI hardware the job requires on their end. eLinehub bridges its network adapter to your diagnostic PC over the internet. XENTRY treats the vehicle as a locally connected DoIP target — SCN coding, online programming and SOC commissioning run on your machine with your own credentials.
The workshop provides the vehicle and the ENET cable. You bring XENTRY. eLinehub provides the bridge.
Free trial starts automatically.
Free to use for shops and field teams.
1. ENET Cable or SD Connect? Start Here
The right page depends on what VCI hardware the workshop has.
Approach | ENET Cable — this page | SD Connect C4 / C6 |
|---|---|---|
Workshop has | A passive OBD-II to RJ45 Ethernet cable | SD Connect C4 or C6 multiplexer |
Vehicle coverage | DoIP platforms only (2019+) | All Mercedes-Benz, CAN/K-Line through DoIP |
XENTRY Diagnosis | ✓ Full support | ✓ Full support |
DTS Monaco / Vediamo | Not validated — not supported | ✓ Full support |
Mechanic setup complexity | Plug in and share — no services to stop | C4: straightforward; C6: stop VCI management services first |
Hardware cost for workshop | Low — passive cable only | Higher — VCI multiplexer |
Use this page when the workshop’s vehicle is a 2019+ DoIP Mercedes and they have no SD Connect. Primary workflows: SCN coding, ECU flash, SOC commissioning via XENTRY.
Use the SD Connect guide when the workshop owns an SD Connect C4 or C6, when the vehicle is pre-DoIP (W204, W212, W222, pre-facelift W213, W906 Sprinter), or when you need DTS Monaco or Vediamo access. (Full technical breakdown on the SD Connect page.)
If you work with workshops of both types, the same Technician PC handles both — ENET cable and SD Connect sessions both run through eLinehub on the same XENTRY installation, switched between orders.
2. Which Mercedes-Benz Vehicles an ENET Cable Covers
From approximately the 2019 model year onward, Mercedes-Benz shifted its primary diagnostic communication to DoIP (Diagnostics over Internet Protocol, ISO 13400). DoIP routes diagnostic traffic over the vehicle’s Ethernet backbone. An ENET cable — a passive OBD-II to RJ45 adapter — gives XENTRY that Ethernet connection to the vehicle directly, without a multiplexer.
Platform | Model Series | Notes |
|---|---|---|
MRA2 | C-Class W206 (2022+), GLC X254 (2023+) | Full DoIP |
EVA2 | E-Class W213 (2020+ facelift) and W214, S-Class W223, GLE W167 facelift, GLS | Mixed DoIP and CAN FD; pre-facelift W213 and W212 are CAN-only |
EQ series | EQA, EQB, EQC, EQE, EQE SUV, EQS, EQS SUV | Full DoIP on all EV platforms |
MMA | Next-generation compact EV platform | Full DoIP |
Commercial | Sprinter W907 (2019+) | Full DoIP; W906 is CAN-only — use SD Connect |
ENET cable does not work on pre-DoIP vehicles. W204, W212, W222, W166 GLE, pre-facelift W213 and W906 Sprinter communicate via CAN/K-Line — those platforms need SD Connect C4/C6.
3. Why DoIP Vehicles Still Require XENTRY and SCN Access
Switching to DoIP did not change Mercedes-Benz’s requirement for online SCN coding — it extended that requirement to every control unit on a more connected vehicle network. A W206 C300, W223 S580 or EQS 580 4MATIC carries the same post-replacement coding requirements as older platforms:
-
ME engine control unit (W206, W223, W167 facelift) — flash and SCN are two separate steps
-
9G-Tronic transmission control unit (ETC) — the 9-speed automatic on EVA2 and newer platforms carries the same online SCN requirement as the 722.9 on older generations
-
ABS/ESP control unit
-
MBUX head unit and NTG7 infotainment modules
-
SRS airbag control unit (ACM)
-
Door control units (DCU) — SCN required per Mercedes service bulletins on W206 and W223
-
EIS/EZS ignition and steering lock modules
-
High-voltage system controllers on EQ-series — additionally require SOC commissioning (see Scenario B below)
For 2021-and-later vehicles — W206, W223, W167 facelift, W214, EQS, EQE — XENTRY additionally requires a Xentry diagnostic certificate (ZenZefi format) for offline guided diagnostics and adaptations behind the vehicle’s secure gateway. The certificate is held by you independently; eLinehub does not affect how XENTRY authenticates it. SCN coding runs through the live Mercedes Online session and is not blocked by the certificate requirement.
4. How eLinehub Works with ENET Cable
Screen sharing doesn’t work for the same fundamental reason it doesn’t work with SD Connect — XENTRY cannot discover a VCI through a screen relay. (Full technical breakdown on the SD Connect page.)
eLinehub bridges the ENET cable’s physical network adapter at Layer 2 across the internet. Your eLinehub virtual adapter (eLinehub Link or eLinehub vNet, depending on the bridging sub-mode you select) receives the same Ethernet frames — DoIP responses, ECU communication data and broadcast traffic — that XENTRY expects from a locally attached ENET connection.
Mechanic-side setup is minimal
Significantly simpler than SD Connect C6. The Mechanic plugs the ENET cable into the vehicle OBD port and the PC Ethernet port, opens eLinehub Mechanic, and shares the network adapter. There are no VCI management services to stop and no device-specific drivers to install.
IP configuration on your side
Once the bridge is established, open Windows Network Connections and locate the eLinehub Link or eLinehub vNet adapter matching your selected bridging mode. Configure it with the static IP that XENTRY requires for a direct ENET bench connection. The address must not conflict with any static IP already on the Mechanic’s physical NIC (if previously configured for local XENTRY use) or on your own physical NICs in the same range. Refer to your XENTRY documentation for the specific values.
Current limitation
DTS Monaco and Vediamo compatibility via ENET cable has not been validated. If you need DTS Monaco or Vediamo access, the workshop requires SD Connect C4/C6 — see the SD Connect guide.
Connection mode
ENET cable uses network adapter bridging, which runs in Relay mode only.
5. Real Job Workflows
Scenario A — TCM / SAM / MBUX Replacement with SCN Coding on W206 or W223
Applicable to any current DoIP-platform vehicle requiring standard module replacement coding.
A workshop replaces the MBUX head unit on a W223 S580. The replacement unit arrives without SCN coding — XENTRY cannot see it in the quick test, and vehicle functions tied to the head unit are inactive. The shop has no SD Connect.
-
Mechanic connects ENET cable to the W223 OBD port and to the workshop PC via RJ45 Ethernet port. Opens eLinehub Mechanic, creates a new order and shares the Passcode.
-
You enter the Passcode in eLinehub Technician to accept the order. Select Mechanic Network Adapter and eLinehub Link as the bridging mode.
-
Once the eLinehub adapter shows connected, open Windows Network Connections, locate the eLinehub Link adapter and set the IPv4 address to the static IP that XENTRY requires for a direct ENET connection. Verify it does not conflict with the Mechanic’s NIC IP or any physical NIC on your PC already in that range.
-
Launch XENTRY Diagnosis. XENTRY sends a DoIP broadcast and discovers the W223. Vehicle identification completes at normal speed.
-
Quick test identifies the MBUX unit as present but uncoded. Navigate to MBUX → control unit variant coding. Authenticate with your Mercedes Online credentials directly in XENTRY. SCN request returns the calibration number and writes it to the head unit.
-
Vehicle functions confirm as active. Faults cleared. Job complete.
Note for W223 and W206: these vehicles require a Xentry diagnostic certificate for offline guided diagnostic procedures. SCN coding runs through a live Mercedes Online session and is not blocked — confirm your certificate is current before booking.
Scenario B — SOC Commissioning After High-Voltage Component Replacement on EQS or EQE
Specific to EV and hybrid platforms with Secure Onboard Communication protection. You must hold high-voltage safety certification and confirm each physical safety prerequisite with the on-site Mechanic before advancing through any XENTRY-prompted step. The Mechanic handles all physical safety steps on-site; you manage the software side.
A workshop replaces the N83/1 DC/DC converter (DDW) on a W223-platform EQS 580 4MATIC. When XENTRY connects after the mechanical replacement, it detects that SOC commissioning is required. SOC is Mercedes-Benz’s security framework for ECU authentication on current-generation vehicles — when a SOC-protected unit is replaced, XENTRY runs an online registration process through the Mercedes-Benz backend, binding the new unit to the vehicle’s VIN. Skipping it leaves the replacement component unable to communicate on the vehicle network.
-
Mechanic confirms all high-voltage safety prerequisites are met: system deactivated, isolated and locked out per Mercedes service procedures. ENET cable connected to OBD port and workshop PC.
-
Mechanic publishes order and shares Passcode. You accept and connect through eLinehub Link. Configure the eLinehub adapter IP per Scenario A, Step 3.
-
Launch XENTRY. DoIP discovery completes. Quick test identifies the replacement DDW and flags SOC commissioning as required.
-
XENTRY opens the SOC commissioning guided procedure. Read through each safety acknowledgment step and confirm with the on-site Mechanic that the physical state of the vehicle matches each XENTRY requirement before proceeding.
-
XENTRY contacts the Mercedes-Benz backend for the SOC registration sequence. The commissioning process completes — the replacement DDW is now authorized on the vehicle network.
-
Charging system functionality verified via XENTRY actuator tests. Quick test confirms no active faults.
Scenario C — Post-Collision ADAS Initialization on W213 Facelift or W214 E-Class
Active after bumper repair, radar sensor replacement or windshield replacement on DoIP E-Class variants.
A collision repair center completes a rear bumper repair on a W213 E-Class (2020+ facelift). The rear short-range radar (SRR) sensors require post-repair initialization — without it, Blind Spot Assist and Active Brake Assist remain inactive and the vehicle cannot be returned to the customer in a safe operating state.
-
ENET cable connected to vehicle OBD port and workshop PC via RJ45. Mechanic publishes order and shares Passcode.
-
You accept, connect through eLinehub Link and configure the eLinehub adapter IP per Scenario A, Step 3.
-
XENTRY discovers the W213 over DoIP. Quick test identifies BSM and ESP fault codes related to rear SRR sensor communication.
-
Navigate to SRR module → adaptations → radar sensor initialization. The rear SRR teach-in on W213 facelift is dynamic — no physical calibration target required. The procedure runs entirely through XENTRY after confirming sensor mounting position is correct.
-
For windshield replacements: navigate to camera module → static calibration. The workshop floor must have the correct calibration target at the OEM-specified distance before starting this step.
-
Clear all ADAS fault codes. Road test above 30 km/h to confirm Blind Spot Assist mirror indicator activation.
6. Setup
System requirements
Windows 7 64-bit minimum; Windows 10 or 11 64-bit recommended. Not supported on Mac, Linux, Android or Windows ARM.
Mechanic Side — Workshop
-
Connect ENET cable to the vehicle OBD port and to the workshop PC via RJ45 Ethernet port. Verify Windows shows an active network link on that NIC.
-
Install eLinehub Mechanic on the workshop Windows PC.
-
Open eLinehub Mechanic, create a new order and share the Passcode. No XENTRY, Mercedes Online credentials or VCI management software required. The Mechanic software is free.
Technician Side — You
-
Install eLinehub Technician on the PC where XENTRY and Mercedes Online credentials are already configured.
-
Sign in and accept the order by entering the Passcode shared by the Mechanic. If the workshop uses a Custom Mechanic build, orders are auto-assigned.
-
Select Mechanic Network Adapter and choose eLinehub Link (or eLinehub vNet if required) as the bridging mode.
-
Once the bridge is established, open Windows Network Connections. Locate the eLinehub Link or eLinehub vNet adapter matching the mode selected in Step 3. Set the IPv4 address to the static IP that XENTRY requires for a direct ENET connection, avoiding conflicts with any static IP on the Mechanic’s physical NIC or your own physical NICs in the same range. Refer to your XENTRY documentation for the specific values.
-
Launch XENTRY Diagnosis. The vehicle appears as a locally connected DoIP target.
For step-by-step screenshots and configuration walkthroughs, see the Setup Guide links above.
7. Network Requirements
Both sides need a minimum 10 Mbps upload bandwidth. Wired connections are required on both sides for SCN coding and flash sessions.
Session type | RTT target |
|---|---|
Fault reading / quick test | Under 150 ms |
SCN online coding | Under 80 ms |
ECU flash | Under 80 ms |
DoIP topology scan (W223, W907, EQS) | Under 60 ms |
Check live latency in the eLinehub connection panel before starting any SCN coding. Do not proceed if latency is above threshold or packet loss is non-zero.
Before any SCN coding or online flash: connect a professional programming power supply delivering steady 13.5–14.2V at 100A+ to the vehicle.
DoIP internet continuity: when the ENET cable is bridged and the vehicle’s DoIP network has an active gateway, your internet connection may drop while the diagnostic session stays active. Use the Switch button to toggle between diagnostic priority mode and normal internet mode — only between sessions, never during SCN coding or active programming.
8. Mercedes-Benz DoIP Platform Compatibility
Vehicle series (DoIP generation):
C-Class (W206), E-Class (W213 facelift 2020+, W214), S-Class (W223), GLC (X254), GLE (W167 facelift), GLS, EQA, EQB, EQC, EQE, EQE SUV, EQS, EQS SUV, Sprinter W907, AMG and Maybach variants on MRA2/EVA2/EQ platforms
Architectures:
MRA2, EVA2, MMA, EQ series (full DoIP)
Online functions:
SCN coding, online programming, SOC commissioning, FDOK, seed-key authentication, EIS/EZS online pairing
Multi-brand support:
eLinehub also supports VW Group (VAS6154A, ODIS), BMW (ENET cable, ICOM), JLR (DoIP VCI, Pathfinder/SDD) — all from the same Technician PC.
9. Customer Protection
Orders require a Passcode to accept — no other specialist on the platform can pick up a workshop’s jobs without it. You can also distribute a Custom Mechanic build that permanently links a workshop to your account, with all orders auto-assigned by default. For complex multi-ECU jobs or SOC commissioning on EV platforms, you can share a specific order with a trusted colleague — external collaborators cannot see Mechanic contact information or claim the workshop relationship.
10. Frequently Asked Questions
Which Mercedes-Benz models work with ENET cable for remote XENTRY diagnostics?
All DoIP-generation vehicles supported by XENTRY: C-Class W206, E-Class W213 (2020+ facelift) and W214, S-Class W223, GLC X254, GLE W167 facelift, GLS, EQA, EQB, EQE, EQE SUV, EQS, EQS SUV, Sprinter W907, and AMG/Maybach variants on MRA2, EVA2, MMA and EQ platforms. Pre-DoIP vehicles — W204, W212, W222, pre-facelift W213 and W906 Sprinter — need SD Connect.
Can I do SOC commissioning remotely via ENET cable?
Yes. XENTRY’s SOC commissioning workflow runs the same way through the eLinehub bridge as it does locally. The on-site Mechanic handles all high-voltage safety procedures as prompted by XENTRY; you manage the software side. A confirmed example is the N83/1 DC/DC converter (DDW) on the EQS platform, where XENTRY prompts SOC commissioning after replacement before the unit can operate.
What about DTS Monaco and Vediamo — do they work via ENET cable?
Compatibility via ENET cable has not been validated for either tool. If you need DTS Monaco or Vediamo access, the workshop needs SD Connect C4/C6. You can handle both types of workshops from the same Technician PC — the same XENTRY installation works for both, and you switch between them across different orders.
How do I configure the IP address for XENTRY with ENET cable and eLinehub?
Open Windows Network Connections and locate the eLinehub Link or eLinehub vNet adapter matching your bridging mode. Set the IPv4 address to the static IP that XENTRY requires for a direct ENET bench connection — refer to your XENTRY documentation for the specific value. The address must not conflict with any static IP on the Mechanic’s physical NIC (if previously configured for local XENTRY use) or on your own physical NICs in the same range.
Do I need a Xentry diagnostic certificate for 2021-and-later DoIP vehicles?
Yes — for W206, W223, EQE, EQS and other vehicles with the secure gateway architecture, XENTRY requires a Xentry diagnostic certificate (ZenZefi format) for offline guided diagnostics and adaptations. You hold and manage the certificate independently. eLinehub does not affect certificate authentication. SCN coding runs through the live Mercedes Online session and is not blocked by the certificate requirement.
What if the workshop has both pre-DoIP and DoIP vehicles?
You handle both from the same Technician PC. Use SD Connect (covered in the SD Connect guide) for pre-DoIP vehicles — W204, W212, W906 Sprinter and others on CAN/K-Line. Use ENET cable through eLinehub for DoIP-generation vehicles. Both connect via eLinehub Link, switched between orders.
Start Your First Remote Session
Free trial starts automatically.
Free to use for workshops and field teams.
Questions or setup support: support@elinehub.com
-
Mercedes-Benz SD Connect Diagnostics & Programming