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 (7) History Discussion
aj310 said:
sorry 2023 eqe Mercedes
Click to expand...

For a 2023 EQE (W295), the files you need are likely already on your laptop IF you have a recent version of Xentry (e.g., 09/2023 or newer).

However, it is important to distinguish between the two types of files:

1. Diagnostic Files (SMR-D) - YOU NEED THIS
To clear the crash codes (P2E3262 / P1C8000) and unlock the charger, you need the SMR-D file to load into DTS Monaco. You do not need to flash the unit.

Check this folder on your drive:
C:\ProgramData\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_COMMON\dbr
(Sometimes it is in C:\Program Files (x86)\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_COMMON\dbr)

Look for these specific files for the W295:
  • Charger (OBC): OBC223.smr-d (The EQE shares the charger with the W223 S-Class).
  • Battery (BMS): BMS_GEN5.smr-d or SG_BMS.smr-d.

2. Flash Files (SMR-F) - YOU LIKELY DO NOT NEED THIS
If you are trying to "Flash" the module to fix the crash code, it will not work. The crash status is stored in the memory (EEPROM), not the firmware. Flashing a locked module will usually fail or leave the code active.

If you still need the flash files for a 2023 model, they are stored here:
C:\ProgramData\Mercedes-Benz\Xentry\Flash
C:\Program Files (x86)\Mercedes-Benz\SDFlash\Release

If the files are missing:
Since the car is a 2023 model, if your Xentry version is older (e.g., 2021 or 2022), you will not have these files. You must download a newer SDFlash database or install Xentry 12/2023 or 03/2024.

Critical Warning for 2023 EQE:
The W295 uses ZenZefi certificates for security. Even if you have the files, DTS Monaco might give you a "Security Access Denied" or "Negative Response" when you try to unlock the crash data because you don't have the online certificate.
  • If you get "Access Denied" on Security Level 37, you will need a Seed/Key Calculator specifically for the W295/W223 architecture, or a paid remote coding service to unlock it.
 
aj310 said:
Can I program with 8.16 Monaco or do I need the new one
Click to expand...

Yes, you can use DTS Monaco 8.16 for the 2023 EQE (W295), but there is a major catch regarding Security.

Here is the technical breakdown:

1. Communication & Protocol (Works)
DTS Monaco 8.16 fully supports the SMR-D files and the DoIP (Ethernet) protocol used by the W295. It can load the projects, read codes, and send commands perfectly fine. You do not strictly "need" DTS 9.02 just for the connection.

2. The Problem: Security Access (ZenZefi)
The 2023 EQE uses a new security architecture called ZenZefi (Certificate-based security) for critical functions like:
  • Unlocking the ECU for Coding (Variant Coding)
  • Reseting Crash Data (Level 37)
  • Disabling the High Voltage Lock

DTS Monaco 8.16 does not support ZenZefi natively. It relies on the old "Seed & Key" DLL method.
  • If you try to unlock Level 37 in DTS 8.16, it will ask for a Key.
  • The standard "Unlock" button will likely fail with "Negative Response 35: Invalid Key" because the internal calculator in 8.16 is too old for a 2023 car.

3. The Solution for DTS 8.16
You can still use 8.16, but you must have an external Seed/Key Calculator that supports the W295/W223 algorithms.
  • You click "Request Seed" in DTS 8.16.
  • You copy the bytes (e.g., 12 34 56 78) into the external calculator.
  • The calculator gives you the Key.
  • You manually enter the Key into DTS 8.16 and click "Send".

Summary
If you have a working Seed/Key Calculator for W295: Keep using DTS 8.16. It is more stable and easier to use than 9.02.
If you do not have a calculator: You are stuck. DTS 9.02 won't help you either unless you have valid ZenZefi certificates installed (which are hard to get offline).

Recommendation: Stick with 8.16 and find a service or tool that can calculate the key for you remotely.
 
aj310 said:
Do I need to be online I have a zen certificate
Click to expand...

No, you do not need to be online (connected to the internet).

If you have a valid ZenZefi certificate installed on your laptop, it is stored locally on your hard drive. The unlocking process happens entirely between your laptop and the car.

However, there is a critical compatibility issue:

DTS Monaco 8.16 does NOT natively support ZenZefi certificates.
If you just open DTS 8.16 and try to unlock the ECU, it will ignore your certificate and ask for a standard "Seed & Key" (which will fail).

To use your ZenZefi certificate, you have two options:

1. Use DTS Monaco 9.02: This version was built to read ZenZefi certificates automatically. It will see the certificate and unlock the ECU immediately.
2. Use a "Wrapper" for 8.16: If you must use DTS 8.16, you need a special add-on tool (often called a "ZenZefi Wrapper" or "SMR-D Patcher") that tricks the software into using the certificate. Without this extra tool, DTS 8.16 cannot see the certificate.

Summary:
  • Internet: Not required.
  • Software: You likely need to switch to DTS 9.02 to make the certificate work easily.
 
So if I upload the files I wouldn’t just be able to activate my car charging if I clear codes stoping the car from charging I need a certificate? And how exactly do I upload my specific files from my vehicle to Monaco or I’m just uploading every car that’s like mine and inputting the new software I can’t run Monaco an just tell it to scan the car
 
aj310 said:
So if I upload the files I wouldn’t just be able to activate my car charging if I clear codes stopin...
Click to expand...

You are mixing up "Flashing" (changing software) with "Coding/Reseting" (sending commands).

Here is the correction to your understanding:

1. DTS Monaco does NOT "Scan" like Xentry
DTS Monaco is an engineering tool. It does not have an "Auto Scan" button that detects your car and fixes it.
  • You must manually tell it *exactly* which ECU you are talking to.
  • You do this by loading a Project File (.smr-d) from your laptop's hard drive.
  • You are not uploading files *from* your car. You are opening a definition file on your laptop that acts as a "driver" so the software understands the car.

2. Why you cannot just "Clear Codes"
The code P2E3262 (Crash Detected) is Hard Locked.
  • If you click "Clear DTCs" right now, the ECU will ignore you. It will say "Negative Response" or the code will come back instantly.
  • The ECU is in a "Safety State." It will not accept a "Clear" command until you perform a specific Unlock Routine.

3. The Certificate is the Key
This is where the ZenZefi Certificate comes in.
  • To run the "Unlock Routine," the ECU demands a password (Security Access).
  • On the 2023 EQE, this password is extremely complex.
  • The Certificate on your laptop automatically provides this password.
  • Without the Certificate (or a Key Calculator), you cannot unlock the ECU.
  • If you cannot unlock the ECU, you cannot clear the crash code.

4. Do NOT "Input New Software" (Flash)
  • Do not try to flash/program the ECU with new files.
  • Flashing a crashed ECU often fails because it is locked. You could brick the module.
  • You only need to send the Reset Command, not change the software.

Summary of what you must do:
1. Load the File: Open DTS Monaco and load OBC223.smr-d (from your laptop's database).
2. Connect: Click "Connect" to talk to the Charger.
3. Unlock: Use your Certificate to pass "Security Access Level 37".
4. Reset: Run the "RoutineCrashReset" (this is a command, not a file upload).
5. Clear: Now you can finally click "Clear DTCs" and the car will charge.
 
aj310 said:
How do I clear the codes from Monaco ?
Click to expand...

To clear diagnostic trouble codes (DTCs) in DTS Monaco, there are two ways to do it.

Important Warning:
For your specific crash codes (P2E3262 in Charger and P1C8000 in Battery), simply clicking "Clear" will not work initially. The ECU is locked. You must run the Unlock Routine (explained below) *before* the clear command will be accepted.

Here is the exact procedure:

Method 1: The Standard "DTC" Tab (Easiest)
1. Open your workspace and Start the interface (Connect).
2. Select the ECU tab at the top (e.g., OBC223 or BMS_GEN5).
3. Look for the tab named "DTC", "Fault Memory", or "Quick Test" (depending on your layout).
4. Click Read DTCs to confirm the codes are there.
5. Click the Clear DTCs button (often looks like a trash can icon or says "Clear").
* *If the codes disappear and come back immediately:* You have not performed the Crash Reset Routine yet.
* *If you get "Negative Response":* The ECU is Security Locked (Level 37).

---

Method 2: Manual Service (If the button fails)
If the button doesn't work, you can send the raw command manually.

1. Go to the Diagnostic Services tab.
2. Find the service named Clear_DTC or Clear_Diagnostic_Information (Service ID 14).
* Usually listed as: [14] Clear Diagnostic Information.
3. In the parameters (if asked), select "All Groups" or enter FF FF FF.
4. Click Transmit.
5. Look at the bottom log. You want to see a Positive Response (usually blue or green text starting with 54).

---

The Correct Sequence for Your Crash Codes
Since you have a crashed 2023 EQE, you must follow this exact order or the codes will never clear:

1. Connect to OBC223 (Charger).
2. Unlock Security (Level 37) using your ZenZefi certificate or Key Calculator.
3. Run Routine: Go to "Routine Control" -> Select Routine_Crash_Reset (or Unlock_Component) -> Start.
4. Hard Reset: Go to "ECU Reset" -> [11] Hard Reset. Wait 10 seconds.
5. Clear Codes: NOW go to the DTC tab and click Clear DTCs.

If you skip step 3, the "Clear DTCs" button in step 5 will do nothing.
 
aj310 said:
My scanners need to be connected to the car ?
Click to expand...

Yes, absolutely.

You cannot clear codes, unlock the ECU, or reset the crash data unless your laptop is physically connected to the vehicle through your scanner (VCI).

Here is why:
1. The Codes are Inside the Car: The error codes (P1C8000, etc.) are stored in the memory chips of the car's modules (BMS and OBC). They are not files on your computer. You need a live connection to send the command "Erase Memory" to those chips.
2. The Unlock Process: To use your ZenZefi certificate or calculate a key, the software (DTS Monaco) must "handshake" with the car's ECU in real-time. It sends a request to the car, the car sends a challenge back, and the laptop sends the answer. This cannot happen if you are not connected.

Required Setup:
  • Laptop running DTS Monaco.
  • Scanner (VCI) (e.g., C6, Xentry VCI, SD Connect C4) connected to the laptop via USB or WiFi.
  • OBDII Cable plugged into the car.
  • Ignition ON: The car's dashboard must be lit up (Ignition position 2) so the ECUs are powered and listening.

You can *configure* DTS Monaco (load projects, arrange windows) while sitting on your couch, but to actually execute the reset, you must be plugged into the car.
 
I’m saying who does the manaco knows that it’s doing my car how do I upload the files back to my car ?
 
aj310 said:
I’m saying who does the manaco knows that it’s doing my car how do I upload the files back to my car...
Click to expand...

You are misunderstanding how the software works. You do not upload files to your car to fix this.

Here is the simplest way to understand it:

1. DTS Monaco does not need to "know" your car
DTS Monaco is like a universal remote control. It does not care if the car belongs to you, your neighbor, or a dealership.
  • It does not check your VIN to "register" the car.
  • It simply talks to whatever Mercedes is plugged into the cable.
  • If you plug it into a 2023 EQE, it talks to the EQE. If you plug it into an S-Class, it talks to the S-Class.

2. You are NOT uploading files
You are thinking of this like a smartphone update where you download a file and install it. That is wrong for this situation.

  • The software inside your car's computer (ECU) is fine. It is not missing.
  • The problem is that a "switch" inside the computer is flipped to "CRASH DETECTED = YES".
  • You do not need to upload a new file to fix this. You just need to send a command that flips the switch back to "NO".

3. What are the SMR-D files for then?
The files on your laptop (like OBC223.smr-d) are just a Dictionary or Translator.
  • Your laptop speaks English/German.
  • The car speaks binary code (010101).
  • The SMR-D file tells DTS Monaco: "When the user clicks 'Unlock', send the code '31 01 AA' to the car."
You load this file into Monaco so the laptop knows how to talk. You do not send this file to the car.

Summary of the Process
1. Plug in: You connect your laptop to the car's OBD port.
2. Load Dictionary: You open DTS Monaco and select the OBC223 file (so the laptop knows the commands).
3. Send Command: You click the button RoutineCrashReset.
4. Action: The laptop sends a signal through the wire. The car receives it, unlocks the battery, and says "Done."
5. Finished: You unplug. Nothing was "uploaded." You just flipped a switch remotely.
 
aj310 said:
How long should this take me
Click to expand...

If you have everything set up correctly, the actual process takes less than 5 minutes.

However, since you are new to DTS Monaco, the setup will take much longer.

Here is the realistic breakdown:

1. The Setup (1 - 2 Hours)
  • Finding the correct SMR-D files on your laptop.
  • Creating a "Project" and "Workspace" in DTS Monaco (you have to configure the buttons and layout manually).
  • Getting your VCI (Scanner) to connect to the car without errors.

2. The Execution (2 Minutes)
Once you are connected and have the buttons on the screen:
  • Unlock Security: 10 seconds.
  • Run Crash Reset Routine: 5 seconds.
  • Hard Reset ECU: 10 seconds.
  • Clear Codes: 5 seconds.

3. The "Stuck" Factor (Indefinite)
The only thing that will stop you completely is the Security Access (ZenZefi).
  • If your certificate works automatically: You are done in minutes.
  • If you get "Access Denied" or "Negative Response 35": You will be stuck until you find a working Seed/Key calculator or a remote support service. You cannot "guess" or "wait out" this step.

Summary:
Plan for an afternoon to learn the software interface. Once you know which button to press, the car is fixed instantly.
 
Step by step detailed how to do everything after I connect my Vcx each step detailed
 
aj310 said:
Step by step detailed how to do everything after I connect my Vcx each step detailed
Click to expand...

Here is the exact step-by-step guide to setting up DTS Monaco and resetting your crash data.

Prerequisites:
  • Laptop with DTS Monaco installed.
  • VCX Scanner connected to Laptop via USB.
  • VCX Scanner connected to Car OBDII port.
  • Ignition ON (Cluster lights on).

Phase 1: Locate Your Files
Before opening Monaco, ensure you know where these files are on your laptop.
Go to:
Code: 
C:\ProgramData\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_COMMON\dbr
Find and copy these two files to your Desktop (so they are easy to find):
1. OBC223.smr-d (On-Board Charger)
2. BMS_GEN5.smr-d (Battery Management System - might be named SG_BMS.smr-d)

Phase 2: Create the Project (Do this once)
1. Open DTS Monaco System Configuration (Icon usually says "System Config" or "Administration").
2. Go to the Project Administration tab.
3. Right-click in the empty white space and select New Project.
4. Name it W295_Crash_Fix.
5. In the "Import" tab of the new window, click the Folder Icon (Import database file).
6. Navigate to your Desktop and select the OBC223.smr-d file. Click Open.
7. Repeat for BMS_GEN5.smr-d.
8. Now you will see the two modules listed. Click Save or OK.

Phase 3: Create the Workspace
1. Go to the Workspace tab in the same window.
2. Right-click and select New Workspace.
3. Name it EQE_Reset.
4. Select the Project you just made (W295_Crash_Fix).
5. In the list of ECUs, check the boxes for both OBC223 and BMS_GEN5.
6. Click Finish / Save.
7. Close the System Configuration window.

Phase 4: The Reset Procedure (In the Car)
1. Open DTS Monaco (The main application).
2. Select your workspace EQE_Reset and click Start.
3. The screen will load. Look at the top left for a button named Start or Connect. Click it.
* If the connection is successful, the "ECU" names will turn Green or you will see voltage numbers.

Step A: Unlock Security (The Critical Step)
1. Select the OBC223 tab at the top.
2. Go to the Diagnostic Services tab (or "Security Access" if you have a specific layout).
3. Find Security Access (Level 37) or SecurityAccessEntriegelung.
4. Click Transmit / Unlock.
* If you have a working ZenZefi setup: It will say "Positive Response".
* If it fails: It will say "Negative Response 35". This means your certificate is not being read by Monaco 8.16, or you need a Seed/Key calculator. You cannot proceed if this fails.

Step B: Execute the Crash Reset
1. Once unlосkеd, go to the Routine Control tab.
2. In the list of routines, look for:
* Routine_Crash_Reset
* OR Routine_Enable_HV_System
* OR Routine_Clear_Crash_Data
3. Select it and click Start Routine.
4. Watch the bottom log. You want to see Positive Response or Done.

Step C: Hard Reset
1. Go to the Diagnostic Services tab.
2. Find ECU_Reset (Service ID 11).
3. Select Hard Reset (01) in the dropdown.
4. Click Transmit.
5. Wait 10 seconds.

Step D: Clear Codes
1. Go to the DTC or Fault Memory tab.
2. Click Read DTCs.
3. Click Clear DTCs.
4. If the crash code is gone, the car should now accept a charge.

Repeat Steps A-D for the BMS_GEN5 module if the battery also has a crash code.
 
I only found pie_common where is the other files how do I find them
 
aj310 said:
I only found pie_common where is the other files how do I find them
Click to expand...

It sounds like you are looking in the wrong folder or your Xentry installation path is slightly different. "piecommon" is likely a typo for PKWCOMMON.

Here is how to find the files on your drive:

Method 1: The Search (Best Way)
Since the folders can be hidden or moved, the easiest way is to let Windows find them for you.

1. Open File Explorer (My Computer).
2. Click on Local Disk (C:).
3. In the top right search bar, type exactly:
OBC223.smr-d
4. Wait for the search to finish. It might take a few minutes.
5. When it finds the file, right-click it and choose "Open File Location".
6. Copy that file to your Desktop.

Repeat the search for: BMS_GEN5.smr-d (or try SG_BMS.smr-d if that finds nothing).

Method 2: Manual Navigation
If the search fails, check these specific paths. Note that ProgramData is a hidden folder.

1. In File Explorer, click View at the top and check the box "Hidden items".
2. Now navigate here:
C:\ProgramData\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_COMMON\dbr
3. If not there, try:
C:\Program Files (x86)\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_COMMON\dbr

Method 3: Look for the Chassis Folder
Sometimes newer cars have their own folder instead of "Common".
Look in:
C:\ProgramData\Mercedes-Benz\Xentry\Kontexte\ODXProjekte\PKW_295 (or PKW_297 / PKW_223).

Important:
If you search your whole computer and cannot find *.smr-d files, it means you do not have the Xentry Diagnostic Software installed. DTS Monaco is just an empty shell; it needs the database files from Xentry to work. If you don't have Xentry installed, you will need to download a "Mercedes SMR-D Database" separately.
 
Activity
So far there's no one here

Similar threads

Bin
  • Article Article
DTS Monaco Super Engineer System Training – MOE Diatronik PDF
    • Like
    • Love
Replies
0
Views
759
Reactions
7
Bin
Bin
Bin
  • Article Article
DTS Monaco & Vediamo Startup Coding Guide
    • Like
Replies
3
Views
2K
Reactions
9
autocoding
A
Bin
XENTRY FullFix By Samik - Mercedes OBD2 Diagnostic Suite
    • Like
    • Love
2 3
Replies
56
Views
8K
Reactions
36
snake83
snake83
Bin
Mercedes-Benz Coding - Professional OBD2 Diagnostic Suite
    • Like
    • Love
Replies
0
Views
740
Reactions
5
Bin
Bin
Bin
Mercedes Daimler Truck - Heavy Duty OBD2 Diagnostic
Replies
2
Views
1K
Reactions
0
Gemini
Gemini
Back