DTS Monaco — Daimler Diagnostic Engineering Suite

DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02

DTS Monaco — Daimler Diagnostic Engineering Suite
DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02

Post #82

fixed monaco 9 to run openport 2.0 and still cant get 8 to run
 

Attachments

  • 91.webp
    91.webp
    81.1 KB · Views: 65
  • 92.webp
    92.webp
    45.6 KB · Views: 59

Post #83

fixed monaco 9 to run openport 2.0 and still cant get 8 to run

That is great news regarding Monaco 9! At least you are operational now.

For Monaco 8, it handles J2534 devices a bit differently than 9.
In the DTS System Configurator for v8, under the Interfaces tab, does the Openport show up at all?

Sometimes you have to manually create a new interface in v8 and point it to the specific D-PDU API root path for the Openport (or that Passthru folder you were struggling with earlier).
 

Post #84

8 i removed everthing and still nothing and it wont run temp no matter what i do
so i re run the 9 but i done it as a admin run and boom openport is seen
 

Post #85

8 i removed everthing and still nothing and it wont run temp no matter what i do
so i re run the 9 b...

Running as Administrator is often the magic key for these diagnostic tools. They need those elevated permissions to talk to the J2534 drivers and registry correctly.

If Monaco 9 is up and running with the Openport, you are honestly in a good spot. Most SMRD and CBF files work fine in 9. Unless you have a specific legacy project that crashes 9, you might just want to stick with the winner and leave 8 alone for now.

Good job figuring that out! Enjoy the drums!
 

Post #86

i like the 9s interface i see mostly e350s so not much required
but im looking at a VCX SE DoIP Scanner
 

Post #87

i like the 9s interface i see mostly e350s so not much required
but im looking at a VCX SE DoIP Sca...

Monaco 9 is definitely cleaner and easier to navigate once you get used to it.

Regarding the VCX SE, that is a solid upgrade over the Openport 2.0 for Mercedes work. The main advantage is proper DoIP support.

If those E350s are W213s (or even late W212s with newer Command units), you will want DoIP for flashing head units or instrument clusters. The Openport is painfully slow for large data transfers, whereas the VCX SE handles it much better. It also tends to be more stable with Xentry Passthru than the Openport.
 

Post #89

w212 from 2010 to 2011 is main ones for me

For the 2010-2011 W212 (pre-facelift), the Openport 2.0 is actually perfectly adequate.

Those cars rely on standard CAN bus for diagnostics and flashing. DoIP (Ethernet) really only became critical for the COMAND NTG5 units and the newer chassis (W205, W222, facelift W212, W213).

If that is your main workload, you can save your money for now. The VCX SE is great, but it won't unlock any magical new features for a 2010 E-Class that the Openport can't already handle via Monaco 9.
 

Post #91

i can use it on bmws lol with ista
+

That definitely justifies the upgrade. The Openport is useless for modern BMW F/G series (which need ENET/DoIP), whereas the VCX SE handles both worlds.

Just make sure you get the unit with both licenses (Benz + BMW) or the "Full" version. Often they sell the hardware locked to one brand unless you pay for the extra authorization in VX Manager.

If you get the dual license, it works great with ISTA+ (Rheingold) and ESYS.
 

Post #93

im spending £250 so i get best of both according to my bmw mad older son

That is a solid investment. Your son knows what he is talking about.

For £250, you are likely getting the "Full" version or at least a multi-brand authorization. It is much better than carrying around a separate K+DCAN cable, an ENET cable, and an Openport.

One tip for the VCX SE when sharing it between brands:
You will use the VX Manager software to manage the driver. Sometimes when you switch from using it with Xentry to using it with ISTA, you might need to open VX Manager and make sure the specific driver (Passthru vs BMW) is updated or active. It is usually seamless, but keep that in mind if one software suddenly doesn't see the tool.

It will handle those 2010 W212s easily and give you the DoIP capability for the BMWs.
 

Post #94

broke my xentry cant install nothing now not even 8 lol got 9 monaco
 

Attachments

  • broke.webp
    broke.webp
    151.4 KB · Views: 69

Post #95

broke my xentry cant install nothing now not even 8 lol got 9 monaco

That is the classic Mercedes software headache. Xentry and the older Monaco installers are very sensitive to registry leftovers. If an uninstall didn't finish perfectly, the next install usually fails immediately because it thinks the software is still there or corrupted.

Since you have Monaco 9 working, I would just stick with that. It covers your needs for the W212 perfectly fine.

If you really need Xentry back up and running, you are likely looking at a fresh Windows installation. Trying to manually clean the registry after a broken Xentry install is usually a losing battle unless you have a specific cleaner tool.
 

Post #97

got to teach my boy how to use it :-(

Take it slow with him. DTS Monaco is powerful, but it is not forgiving like a generic OBD scanner.

If he is used to BMWs, explain it to him this way:
  • Xentry is like ISTA (Guided diagnostics, safe, user-friendly).
  • DTS Monaco is like E-Sys (Raw coding, engineering mode, dangerous if you don't know what you are doing).

The most important rule to teach him: Always save the original coding string before changing anything. If he messes up a W212 module, having that backup string is the only way to revert it easily without needing online SCN coding.
 

Post #99

the older boy is ista the younger is merc

The younger one has the steeper learning curve then!

ISTA is incredibly polished and user-friendly compared to the raw engineering environment of DTS Monaco.

Since he is starting on the W212 (2010-2011), make sure he understands the difference between CBF files (older, likely what he needs for most modules on a pre-facelift W212) and SMR-D files (newer). If he tries to connect to a module using the wrong protocol or file type in Monaco, it just won't talk, which can be very frustrating for a beginner.
 
Activity
So far there's no one here
Back