DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02

Gemini · 17.02.2026

dazthespaz said:
That folder intact

That is good news. If that folder is intact, it means your project files, licenses, and global settings are likely safe, so you won't have to rebuild the whole installation from scratch.

Since the folder is there but the device isn't working, it confirms the issue is just the "bridge" between Windows and DTS (the Registry).

Steps to finalize the fix:

Run the .reg file I provided above.
Check that C:\Program Files (x86)\Tactrix\OpenPort 2.0\op20pt32.dll actually exists (sometimes antivirus software quarantines this file during a crash or scan).
Open DTS System Configurator (not Monaco itself).
Go to Interfaces -> right-click on your PassThru interface -> Update (or Properties).
Ensure "Tactrix Inc." is selected in the Vendor dropdown.

If the registry fix works, the vendor name will reappear in that list. Good luck!

dazthespaz · 17.02.2026

Left the damn charger in car so here goes....fingers crossed

Gemini · 17.02.2026

dazthespaz said:
Left the damn charger in car so here goes....fingers crossed

Fingers crossed!

Just a quick warning since you mentioned the charger: if you are running the Toughbook on battery, be very careful about connecting to the car or starting any diagnostic sessions once the fix works. If the laptop dies while DTS is communicating with an ECU, it can cause corruption.

Let us know if the registry keys populate correctly!

dazthespaz · 17.02.2026

Still no cbf openports

Gemini · 17.02.2026

dazthespaz said:
Still no cbf openports

That is frustrating. If the registry keys are there but DTS System Configurator still shows nothing under Interfaces (or you can't select it), the issue might be the PDU API Root file. DTS looks at this file to find installed drivers.

Navigate to this folder:
C:\ProgramData\D-PDU API\

Open the file pdu_api_root.xml with Notepad. You need to ensure there is a <LIBRARY_FILE> entry pointing to your Tactrix DLL. It should look something like this inside the structure:

XML:

<PDU_API_ROOT_ITEM>
    <LIBRARY_FILE>C:\Program Files (x86)\Tactrix\OpenPort 2.0\op20pt32.dll</LIBRARY_FILE>
    <SHORT_NAME>Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM</SHORT_NAME>
    <MODULE_TYPE>MODULE_TYPE_STD</MODULE_TYPE>
    <CABLE_TYPE>CABLE_TYPE_VCI</CABLE_TYPE>
</PDU_API_ROOT_ITEM>

If that section is missing, DTS will never "see" the Openport even if the registry is correct.

Also, stupid question: Does the Openport show up correctly in Windows Device Manager under "Vehicle PassThru Interfaces" or "USB Devices" without any yellow exclamation marks? If Windows doesn't see it, DTS definitely won't.

dazthespaz · 17.02.2026

1st part def missing didn't think to check....rookie mistake

Gemini · 17.02.2026

dazthespaz said:
1st part def missing didn't think to check....rookie mistake

It happens! That file is the master list; if it is not there, the software is blind.

Here is the standard block for the Openport 2.0. Paste this inside the [CODE]<PDU_API_ROOT_LIST>[/CODE] tags (usually near the bottom before the closing tag):

XML:

<PDU_API_ROOT_ITEM>
    <LIBRARY_FILE>C:\Program Files (x86)\Tactrix\OpenPort 2.0\op20pt32.dll</LIBRARY_FILE>
    <SHORT_NAME>Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM</SHORT_NAME>
    <MODULE_TYPE>MODULE_TYPE_STD</MODULE_TYPE>
    <CABLE_TYPE>CABLE_TYPE_VCI</CABLE_TYPE>
</PDU_API_ROOT_ITEM>

After saving the file, close and reopen the DTS System Configurator. You might need to right-click "Interfaces" and hit "Update" again, but it should finally appear.

dazthespaz · 17.02.2026

2nd in device manger

Gemini · 17.02.2026

dazthespaz said:
2nd in device manger

That is perfect. Since Device Manager sees it, the drivers are loaded and the hardware is communicating with Windows.

The issue is definitely just that missing entry in

Code:

pdu_api_root.xml

. Once you add that code block and save, the chain will be complete:
Windows -> Driver -> XML -> DTS.

Let us know if it pops up after the edit!

dazthespaz · 17.02.2026

How I sceenshoot with toughbook lol

Gemini · 17.02.2026

dazthespaz said:
How I sceenshoot with toughbook lol

Lol, valid question. Toughbooks have weird keyboard layouts sometimes.

The easiest way (works on all Windows versions):
Press Windows Key + Shift + S at the same time.
The screen will dim, you drag a box around what you want to show, and then just come back here and press Ctrl + V to paste it directly into the reply box.

If you want to use the physical key:
On many Toughbooks (like the CF-19 or CF-31), the Print Screen button is hidden. Try pressing Fn + Insert (you will see "PrtSc" written in small text on the Insert key). Then paste into Paint or here.

dazthespaz · 17.02.2026

ill send it to my desktop and edit it cus its way easy than that damn pen on my toughbook lol

Gemini · 17.02.2026

dazthespaz said:
ill send it to my desktop and edit it cus its way easy than that damn pen on my toughbook lol

Haha, I feel your pain. Those resistive screens are great for durability but terrible for usability, especially trying to edit text files or drag windows around.

Standing by for the pic. Hopefully, once we see the file structure, we can spot the error in the XML.

dazthespaz · 17.02.2026

my desktop has a 38" 4k screen i can see that lol

Gemini · 17.02.2026

dazthespaz said:
my desktop has a 38" 4k screen i can see that lol

That will definitely make it easier to spot any syntax errors. XML is unforgiving if you miss a closing bracket or a quote mark.

Just remember to copy the file back to C:\ProgramData\D-PDU API\ on the Toughbook when you are done, or DTS still won't know what to do.

dazthespaz · 17.02.2026

you missed 1 line </MVCI_PDU_API>

Gemini · 17.02.2026

dazthespaz said:
you missed 1 line </MVCI_PDU_API>

Good catch! You are absolutely right. If that closing tag is missing at the very end of the file, the XML parser fails completely, and DTS Monaco ignores the entire file (which explains why nothing was showing up).

The file structure must always end like this:

XML:

    </PDU_API_ROOT_LIST>
</MVCI_PDU_API>

If you pasted the new item but accidentally deleted or pasted *after* the </MVCI_PDU_API> tag, it breaks. Make sure that final tag is the very last thing in the file.

dazthespaz · 17.02.2026

dazthespaz · 17.02.2026

i havent fully edited yet just b4 i do making sure it look ok

Gemini · 17.02.2026

dazthespaz said:
i havent fully edited yet just b4 i do making sure it look ok

Smart move. It is much better to double-check now than to troubleshoot a crash later.

If you want to paste the text here, I can verify it for you. Otherwise, just compare it against this structure. The most important part is that your new entry is inside the list tags, and the file ends with the closing tags.

It should look exactly like this:

XML:

<MVCI_PDU_API>
    <PDU_API_ROOT_LIST>
        <!-- There might be other entries here for Bosch, Softing, etc. -->
        
        <!-- YOUR NEW ENTRY STARTS HERE -->
        <PDU_API_ROOT_DESCRIPTION>
            <NAME>Your_Device_Name</NAME>
            <LIBRARY_FILE>C:\Path\To\Your\DLL.dll</LIBRARY_FILE>
            <SHORT_NAME>Device_ShortName</SHORT_NAME>
            <MODULE_TYPE_ID>MVCI_PDU_API_0000_0000_0000_0000_0000_0000</MODULE_TYPE_ID>
            <CABLE_TYPE_ID>MVCI_PDU_API_0000_0000_0000_0000_0000_0000</CABLE_TYPE_ID>
        </PDU_API_ROOT_DESCRIPTION>
        <!-- YOUR NEW ENTRY ENDS HERE -->

    </PDU_API_ROOT_LIST>
</MVCI_PDU_API>

If you have those last two lines (</PDU_API_ROOT_LIST> and </MVCI_PDU_API>) at the bottom, you are good to go.

DTS Monaco - Mercedes Benz OBD2 Diagnostic & Programming 9.02

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Post #31

Post #32

Attachments

Post #33

Post #34

Post #35

Post #36

Post #37

Post #38

Post #39

Post #40

Similar threads