DTS Monaco — Daimler Diagnostic Engineering Suite

DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02

Sign in to download for free
DTS Monaco — Daimler Diagnostic Engineering Suite
DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02
Sign in to download for free
Overview Updates (2) Reviews (3) History Discussion
i tried to install but i cant understand the generator its in chinese then when i do i dont even know where i can upload on the dts
 
aj310 said:
i tried to install but i cant understand the generator its in chinese then when i do i dont even kno...
Click to expand...

It can be confusing because there are different versions of the "medicine," but the process is almost always the same.

1. The Chinese kеуgеn
You don't need to read the text. You just need to follow the standard order:
  • Top Box: This is usually for your "Name" (you can type anything, e.g., "Admin").
  • Middle/Long Box: This is where you paste your Hardware ID.
  • Button: Click the button (usually bottom right or next to the ID box) to generate the file.

2. Where to get the Hardware ID?
When you try to start DTS Monaco and it fails, it usually shows a small window with a long code (ID). Copy that code.

3. Where to put the liсеnsе File?
The kеуgеn will create a file (often named liсеnsе.txt, liсеnsе.lic, or similar). You do not "upload" this inside the software. You must move the file to a specific folder on your Windows drive.

For DTS Monaco 8.16 (most common), paste the liсеnsе file here:
Code: 
C:\ProgramData\Softing\Diagnostic Tool Set\8.16\liсеnsе\
(Note: ProgramData is a hidden folder. You might need to type it manually in the address bar at the top of the folder window).

For DTS Monaco 8.14, it is usually here:
Code: 
C:\ProgramData\Softing\Diagnostic Tool Set\8.14\liсеnsе\

Once the file is in that folder, restart DTS Monaco. It should open without asking for a key.
 
aj310 said:
this 902 there isnt a middle box
Click to expand...

DTS Monaco 9.02 uses a completely different licensing system (TLS) compared to the older 8.16 version. The "generator" you are looking at is likely not a simple ID-to-Key calculator.

If there is no box to paste a Hardware ID, it is probably a Patcher.

How to use it:
1. Instead of generating a code, it usually asks you to Select a Folder.
2. You need to point it to the installation directory of DTS Monaco (usually C:\Program Files (x86)\Softing\DTS 9.02\bin or similar).
3. Once selected, you click the button (often labeled in Chinese), and it will replace the original .dll files with "сrаскed" ones.

My Recommendation:
If you are struggling with the installation, uninstall 9.02 and install DTS Monaco 8.16 instead.

Here is why:
1. Stability: 8.16 is the "Gold Standard." It is extremely stable and widely used.
2. Compatibility: It fully supports the SMR-D files needed for your EQE (W295).
3. Ease of Use: The activation is the simple "Copy ID -> Paste into kеуgеn -> Get liсеnsе" method you were expecting.
4. ZenZefi: 9.02 has stricter security checks regarding certificates, which can make offline unlocking (what you are trying to do) much harder for a beginner.

For unlocking the HV battery on an EQE, DTS 8.16 is perfectly capable and much easier to set up.
 
aj310 said:
How would I get my vcx to work in xentry
Click to expand...

To get Xentry to recognize your VCX SE, you must install the correct driver inside the VX Manager software. You cannot just plug it in and expect Xentry to see it.

The exact step depends on which version of Xentry you installed: Xentry Passthru or Xentry OpenShell (XD).

Step 1: Identify your Xentry Version
Look at the Xentry icon on your desktop or the name of the release you downloaded.
  • Xentry Passthru: Usually has "Passthru" in the name. It is designed for 3rd party cables.
  • Xentry OpenShell / XD: This is the standard dealer version designed for C4/C5/C6 multiplexers.

Step 2: Install the Driver in VX Manager
1. Close Xentry completely.
2. Connect your VCX SE to the laptop via USB.
3. Open VX Manager.
4. Click on the "Diagnostic" tab.

If you have Xentry OpenShell (Most Common):
  • Find the icon labeled "BENZ C6".
  • Click it and press Install.
  • Note: This driver tricks Xentry into thinking your VCX is a genuine Mercedes VCI.

If you have Xentry Passthru:
  • Find the icon labeled "PASSTHRU".
  • Click it and press Install.

Step 3: Verify the Connection
1. Keep the VCX plugged in.
2. Open Xentry.
3. Look at the icons in the top right corner (or the voltage display).
* Battery Voltage: You should see the car's battery voltage (e.g., 12.5V) displayed. If it says "0.0V" or is greyed out, it is not connected.
* Lock Icon: If you see a padlock icon, it means the VCI is locked/connected.

Troubleshooting for EQE (DoIP)
Since you are working on an EQE, you need DoIP (Ethernet communication).
1. Go back to VX Manager.
2. Click on "Device Configuration" or settings.
3. Ensure "DoIP Switch" or "DoIP Update" is enabled/checked.
4. If the VCX SE firmware is old, click "Firmware" on the main screen and Update it. DoIP often fails on old firmware.
 
aj310 said:
It’s not detecting the car I was runing firmware 1.9.1.0 I upgrading to 1.9.6.0
Click to expand...

If the firmware update didn't fix it, the issue is likely one of three things: Ignition state, Xentry version, or the specific Driver setting.

Here is the checklist to get it talking to the EQE:

1. The "EV Ignition" State
This is the most common mistake on EVs.
  • The car must be in "Ignition ON" mode, not just "Accessory" mode.
  • Press the Start button twice without your foot on the brake.
  • The instrument cluster should light up fully with all the warning lights. If the cluster is dark or only shows the door open, Xentry cannot talk to the Gateway.

2. Update the liсеnsе in VX Manager
After you update the firmware (to 1.9.6.0), you must update the liсеnsе on the device, or the diagnostic functions will stay locked.
  • Open VX Manager.
  • Click the "Update liсеnsе" button (usually on the main screen or under the Device tab).
  • Wait for it to say "liсеnsе Updated."

3. Check Your Xentry Version
The EQE (W295) is a very new car.
  • If your Xentry version is older than 09/2022, it does not have the database files for the EQE. It will never detect it.
  • You need Xentry 2023 or 2024 for proper support of this chassis.

4. Try Manual Selection
If "Auto-Detect" fails, try to force the connection:
  • In Xentry, choose the "Mercedes-Benz" brand.
  • Select "Passenger Car".
  • Look for the "EQE" or "295" chassis code in the list.
  • Click it and try to connect.

5. The Driver Conflict (C6 vs Passthru)
Double-check which Xentry you have vs. which driver you installed in VX Manager.
  • If you have Xentry OpenShell (the standard icon), you MUST install the BENZ C6 driver in VX Manager. Uninstall the Passthru driver if it is there.
  • If you have Xentry Passthru (it says Passthru in the name), you MUST install the PASSTHRU driver in VX Manager.
Note: The "Benz C6" driver handles DoIP (Ethernet) much better for the EQE than the Passthru driver does.
 
aj310 said:
my car said device connected in diagnostics still not reaching
Click to expand...

That is actually good news. If the car screen says "Diagnostics Connected" (or shows the icon), it means the VCX SE is physically working and has successfully woken up the car's Gateway.

The problem is now purely between the VCX SE and your Laptop. The data is getting to the dongle, but it is not getting into Xentry.

Since this is an EQE (DoIP car), this is almost certainly a Network/IP Configuration issue.

Here is how to fix the link:

1. Check the DoIP Switch
The EQE communicates via Ethernet (DoIP), not the old CAN bus lines.
  • Open VX Manager.
  • Go to Device Configuration (or the Settings tab).
  • Look for a checkbox that says "DoIP" or "DoIP Switch".
  • Make sure it is CHECKED / ON.
  • If you change it, click "Save" and restart the device (unplug/replug).

2. Check the Windows Network Adapter
When you plug in the VCX SE, it creates a "Virtual Network Adapter" on your laptop. Xentry uses this to talk to the car.
  • On your laptop, go to Control Panel -> Network and Sharing Center -> Change Adapter Settings.
  • Plug in the VCX SE via USB.
  • You should see a new Local Area Connection appear (often labeled "Realtek USB GbE" or similar).
  • Right-click it -> Properties -> Internet Protocol Version 4 (TCP/IPv4).
  • Make sure it is set to "Obtain an IP address automatically" (DHCP).
  • If it is already automatic and failing, try setting it manually to:
    IP:
    Code: 
    172.29.127.120
    Subnet:
    Code: 
    255.255.0.0

3. Disable the Firewall
Windows Defender Firewall often blocks the DoIP connection because it looks like an "Unidentified Network."
  • Temporarily turn off ALL firewalls (Domain, Private, and Public).
  • Try to connect in Xentry again.

4. The "C6" Driver Check
If you are using Xentry OpenShell (XDOS), you must have the BENZ C6 driver installed in VX Manager.
  • If you installed the "Passthru" driver in VX Manager but you are running Xentry OpenShell, it will wake the car up but fail to read data.
  • Uninstall "Passthru" in VX Manager and install "BENZ C6".

Summary:
The car sees the tool, so the cable is fine. The issue is that Xentry is looking for data on a network port that is either blocked by a firewall or not configured correctly in Windows.
 
aj310 said:
it says device detected and diagnostic center see operator Manuel
Click to expand...

That message on your dashboard is actually good news.

It confirms that the car detects the VCX SE and has entered "Diagnostic Mode." The physical connection is working. The problem is that the data is stopping at the dongle and not reaching the Xentry software on your laptop.

This is almost always caused by a mismatch between your Xentry Version and the Driver you installed in VX Manager.

You need to match them exactly:

Step 1: Check your Xentry Icon
Look at the Xentry icon on your desktop.
  • Does it say Xentry Diagnosis (OpenShell) or XDOS?
  • Or does it say Xentry Passthru?

Step 2: Install the Correct Driver
Open VX Manager, go to the Diagnostic tab, and look at what is installed.

If you have Xentry OpenShell (XDOS):
  • You MUST install the driver named BENZ C6.
  • You MUST Uninstall the driver named "Passthru" (if it is installed).
  • The "Benz C6" driver allows the VCX SE to use the DoIP (Ethernet) protocol required for your EQE.

If you have Xentry Passthru:
  • You MUST install the driver named PASSTHRU.
  • You MUST Uninstall the "Benz C6" driver.

Step 3: The DoIP Switch
Since the EQE communicates via Ethernet (DoIP), you must ensure the VCX SE is broadcasting correctly.
  • Open VX Manager.
  • Go to Device Configuration (or Settings).
  • Make sure DoIP is checked/enabled.
  • If you change it, click Save and unplug/replug the device.

Summary:
The car is waiting for commands (that's why it shows the message). Xentry isn't sending them because it's looking for a "C6" unit but you might have the "Passthru" driver installed (or vice versa). Fix the driver in VX Manager, and Xentry should immediately see the voltage and connect.
 
aj310 said:
I have open shell
Click to expand...

Since you have Xentry OpenShell, you must configure the VCX SE to "pretend" to be a genuine Mercedes C6 Multiplexer.

Here is the exact fix:

1. The Driver Switch (Critical)
Open VX Manager.
Go to the Diagnostic tab.
  • UNINSTALL the driver named "PASSTHRU" (if it is installed).
  • INSTALL the driver named "BENZ C6" (sometimes just labeled "BENZ" or "XENTRY").

*Why?* OpenShell does not listen to "Passthru" drivers by default. It looks for a specific C6 connection. The "BENZ C6" driver creates that emulation.

2. Enable DoIP
Since your EQE requires Ethernet communication:
  • In VX Manager, go to Device Configuration.
  • Make sure DoIP is checked/enabled.
  • Click Save.

3. Do NOT use the Mercedes VCI Manager
Do not try to configure the device using the "ConfigAssist" or "VCI Manager" icons on your desktop. Those are for genuine tools. VX Manager handles everything in the background.

4. Restart and Connect
1. Unplug the VCX SE from the laptop.
2. Restart your laptop.
3. Plug the VCX SE back in.
4. Open Xentry OpenShell.

You should now see the voltage in the top right corner, and it should connect to the car.
 
aj310 said:
Still nothing
Click to expand...

If the car sees the device but Xentry does not, the "Bridge" (Driver) between the VCX and Windows is broken.

Here are the 3 most common reasons this happens with Xentry OpenShell + VCX SE:

1. The "VCI Manager" Test
We need to see if the driver is actually loaded.
  • Close Xentry and VX Manager.
  • Open the VCI Manager (The Mercedes-Benz icon on your desktop, NOT the VX Manager).
  • Look at the list on the left.
  • Do you see a VCI icon there?
Result:
  • If the list is EMPTY: The "Benz C6" driver from VX Manager did not install correctly. This is often blocked by Windows Security.
  • If you see the VCI but it has a Red X or says "Disconnect": It is a firewall/IP issue.

2. Secure Boot (BIOS) Blocking the Driver
The VCX SE drivers are not signed by Microsoft. If your laptop has "Secure Boot" enabled in the BIOS, Windows will silently block the driver from loading, even if VX Manager says "Installed."
  • Restart your laptop and enter BIOS (usually F2 or Del).
  • Find the "Secure Boot" setting.
  • Set it to DISABLED.
  • Save and Exit.

3. The IP Address (Critical for EQE/DoIP)
Since the EQE uses Ethernet, the network settings must be exact.
  • Plug in the VCX SE.
  • Go to Control Panel -> Network and Sharing Center -> Change Adapter Settings.
  • Find the new Network Adapter (it usually says "Realtek USB GbE" or just "Ethernet X").
  • Right-click -> Properties -> Internet Protocol Version 4 (TCP/IPv4).
  • Set it to Use the following IP address:
    Code: 
    IP Address: 172.29.127.119
Subnet Mask: 255.255.0.0
  • Click OK and try Xentry again.

Summary:
If VCI Manager is empty, disable Secure Boot and reinstall the "Benz C6" driver in VX Manager.
If VCI Manager sees it, fix the IP address as shown above.
 
aj310 said:
Yea it say no xentry Vci paired
Click to expand...

This is the most common confusion with the VCX SE.

You can IGNORE the "No VCI Paired" message in the Mercedes VCI Manager.

The VCX SE is an emulator. It does not "pair" like a genuine $2,000 Mercedes C6 Multiplexer. It will often show as disconnected or empty in the VCI Manager tool, but it will still work inside Xentry if the driver is loaded correctly.

Since Xentry is still not connecting, the issue is that the "Emulator Driver" is being blocked by Windows.

Here is the fix:

1. Disable Secure Boot (Crucial)
The VCX SE driver is not signed by Microsoft. If your laptop has "Secure Boot" enabled in the BIOS, Windows will silently block the driver, even if VX Manager says "Installed."
  • Restart your laptop and enter BIOS (F2, F10, or Del).
  • Find "Secure Boot" and set it to DISABLED.
  • Save and Exit.

2. Clean Reinstall of the Driver
Once Secure Boot is off, you must reload the driver files:
  • Open VX Manager -> Diagnostic Tab.
  • Uninstall the "BENZ C6" driver.
  • Restart the Laptop.
  • Open VX Manager -> Diagnostic Tab -> Install "BENZ C6" driver again.

3. Verify the "Virtual" Connection
Do not look at VCI Manager. Look at your Windows Taskbar (bottom right, near the clock).
  • Do you see a small icon that looks like a grey or white pyramid (VX Manager Agent)?
  • If not, open VX Manager and keep it open in the background.

4. The Final Test
  • Connect the VCX SE to the car (Ignition ON).
  • Connect the USB to the laptop.
  • Open Xentry OpenShell.
If the voltage (top right) still shows 0.0V or empty, close Xentry and try this specific IP setting for the EQE:

Manual IP Configuration (For DoIP/Ethernet):
  • Go to Control Panel -> Network Connections.
  • Find the "Realtek USB GbE" adapter (or the one created by the VCX).
  • Right-click -> Properties -> IPv4.
  • Set to Manual IP:
    Code: 
    IP Address: 172.29.127.119
Subnet Mask: 255.255.0.0
  • Click OK and try Xentry again.
 
Finally got it work where exactly should I go to turn the charging back on can you check these pics tell me what I should do ac charger and dc charging inoperative
 

Attachments

  • IMG_2C21A3F3-1408-4E76-9FE8-24C98CE8C79B.webp
    IMG_2C21A3F3-1408-4E76-9FE8-24C98CE8C79B.webp
    677.8 KB · Views: 3
  • IMG_330B6475-733B-4CD2-9791-A6BAEAF44639.webp
    IMG_330B6475-733B-4CD2-9791-A6BAEAF44639.webp
    714.1 KB · Views: 3
  • IMG_304522A8-953C-4A7B-A204-6366464CA2DB.webp
    IMG_304522A8-953C-4A7B-A204-6366464CA2DB.webp
    612.3 KB · Views: 3
aj310 said:
Finally got it work where exactly should I go to turn the charging back on can you check these pics ...
Click to expand...

Great job getting the connection working. Since you cannot upload images directly here, I will guide you based on the standard procedure for the EQE (W295) when it shows "Charging Inoperative."

This error usually means the BMS (Battery Management System) has locked the High Voltage system for safety, often due to a crash signal, insulation fault, or a detected surge.

Here is the exact path in Xentry to reset it:

Step 1: Go to the BMS ECU
1. Run a Quick Test (let it scan all modules).
2. On the left menu, go to Control Units.
3. Select Drive.
4. Look for N82/2 - Battery Management System (BMS) (sometimes labeled as SG-BMS).
5. Double-click to enter it.

Step 2: Check the Fault Codes
Before you try to unlock it, look at the Fault Codes tab.
  • If you see a code like "Crash signal detected" or "Interlock loop open", it is a safety lock.
  • If you see "Insulation resistance too low", do NOT force the system on. You have a physical short circuit (dangerous).

Step 3: The Unlock Procedure
If the fault is just a "Crash Data" lock or "Contactor Open" lock, follow this path:

1. Click on the Adaptations (or sometimes Special Procedures) tab at the top.
2. Look for a menu item named:
* Unlock high-voltage on-board electrical system
* OR Resetting of crash data
* OR Enable charging
3. Select it and follow the on-screen instructions.
* Note: You usually need the Ignition ON and the Engine OFF.

Step 4: Check the Pyrofuse
If Xentry says "Procedure Successful" but the charging is still inoperative, or if the fault code says "Open Circuit" in the HV path:
  • The Pyrofuse (Pyrotechnical Separator) inside the pre-fuse box might be blown.
  • On the EQE, this is a physical fuse that explodes to cut power during a crash. If it is blown, no amount of software coding will fix it; it must be replaced.

Important Note on ZenZefi (Security)
The EQE is a very new car (Gen 2023+ architecture).
  • If Xentry asks for a Certificate, User Login, or says "Access Denied" when you try to run the unlock function, it means the car is protected by Mercedes' new ZenZefi security cloud.
  • Offline Xentry (which you are likely using with the VCX SE) often cannot bураss this block on 2023+ models without a specific "Offline Certificate" installed.

If you get a "Certificate" error, let us know. You might need to use DTS Monaco (which you asked about earlier) to force the unlock, as it can sometimes bураss the Xentry security checks.
 
Back