The configuration guide Mercedes DIYers search for: connect XENTRY to any DoIP Mercedes with a $29.99 ENET adapter instead of a four-figure MUX.
Step 1 — Plug the ENET adapter into the OBD2 port and connect it to your laptop (USB-C direct, or Ethernet port with the RJ45 cable). Windows will identify a new network interface.
Step 2 — Set the adapter to obtain an IP automatically (DHCP/APIPA). The Mercedes DoIP gateway hands out link-local addresses in the 169.254.x.x range. Verify with ipconfig: you should see a 169.254 address on the ENET interface within 30 seconds of ignition on.
Step 3 — In XENTRY configuration, select the Ethernet/DoIP VCI (often listed as 'Ethernet VCI' or 'DoIP interface') rather than SDconnect or eCOM. Save and restart the XENTRY session.
Step 4 — Start a new session. XENTRY should discover the DoIP gateway, read the VIN automatically, and populate the vehicle data card. If the VIN appears, your ENET configuration is complete — quick test, control units and guided functions are now available.
| Symptom | Cause | Fix |
|---|---|---|
| No 169.254 address | Firewall or wrong adapter profile | Disable firewall on the ENET interface; set network profile to Private |
| VIN not read | VCI type set to SDconnect | Switch VCI to Ethernet/DoIP in XENTRY config |
| Drops mid-session | Battery sag | Attach maintainer, confirm 13V+ on volt display |
| Works on one car, not another | Target car is pre-DoIP (CAN) | Older chassis need a MUX — ENET cannot connect |
Once XENTRY connects, the same ENET link serves DTS Monaco (with the correct CBF/SMR-D project for your chassis) and Vediamo for variant coding. The interface configuration is analogous — select DoIP/Ethernet and let the tool discover the gateway.
Project files, DoIP interface selection and the first ECU session.
Learn more