DTS Monaco v9.02.001

  •  Activation Download 
  • Thread starterR00TR0w
  • Start date
For a cheap Passthru device like OP 2.0, you need to copy the following to a *.reg file and double click it to import into the Windows Registry.
You'll see this Passthru device as an option in Monaco 9 later.

Code:
Windows Registry Editor Version 5.00

"Name"="OpenPort 2.0 J2534 ISO/CAN/VPW/PWM"
"Vendor"="Tactrix Inc."
"ConfigApplication"=""
"DeviceId"=dword:00000000
"CAN"=dword:00000001
"ISO9141"=dword:00000001
"ISO9141_CH1"=dword:00000001
"ISO9141_CH2"=dword:00000001
"ISO9141_CH3"=dword:00000001
"ISO14230"=dword:00000001
"ISO14230_CH1"=dword:00000001
"ISO14230_CH2"=dword:00000001
"ISO14230_CH3"=dword:00000001
"ISO15765"=dword:00000001
"J1850PWM"=dword:00000000
"J1850VPW"=dword:00000000
"FunctionLibrary"="C:\\Windows\\SysWOW64\\op20pt32.dll"

Device settings:

D-PDU API -> Softing AG EDIC_D_PDU_API_11_28_25
Module Type -> J2534
Cable -> J1962_CARB
Vendor Module Name -> Taxtrix Inc.
ISO_11898 -> CAN1
ISO_9141_2_UART -> KLINE7
 
  • Like [+1]
Reactions:goberr, mbvitebsk, adrianek69 and 4 others
I have a problem with connecting VCI to DTS 9. In DTS 8.14, VCI connects OK, but VCI cannot connect to DTS 9.

I am also struggling with this problem.
DTS 9 doesn't see VCI C6 OEM.

Pdu_api_root_x64:

Code:
<MVCI_PDU_API>
<SHORT_NAME>D_PDU_API_Bosch_MTS6532</SHORT_NAME>
<DESCRIPTION>Daimler - MTS6532, D-PDU API by Bosch</DESCRIPTION>
<SUPPLIER_NAME>Bosch</SUPPLIER_NAME>
<LIBRARY_FILE URI="file://C:\Program Files (x86)\Mercedes-Benz\Bosch\VCI Software (Daimler)_x64\Products\MTS6532\Dynamic Link Libraries\BVTX-VCI-PDU.dll" />
<MODULE_DESCRIPTION_FILE URI="file://C:\Program Files (x86)\Mercedes-Benz\Bosch\VCI Software (Daimler)\Products\MTS6532\SupportFiles\MDF_Bosch_MTS6532.xml" />
<CABLE_DESCRIPTION_FILE URI="file://C:\Program Files (x86)\Mercedes-Benz\Bosch\VCI Software (Daimler)\Products\MTS6532\SupportFiles\CDF_Bosch_Daimler.xml" />
</MVCI_PDU_API>

Does anyone have any ideas?

Edit: Solved, probably due to an incorrect file "cpprest141_2_10.dll" in the "System32" folder.
 
Download attachments
  • 1.PNG
    1.PNG
    31.1 KB · Views: 857
  • DLL.rar
    External link · Views: 18
  • 2.PNG
    2.PNG
    22.6 KB · Views: 794
  • Like [+1]
Reactions:Ajkaro, momosam, gunflex and 2 others
Hi guys, I'm new here. I was wondering if anyone has a video tutorial or instruction file to learn how to use Monaco and Vediamo correctly?
 
  • Like [+1]
Reactions:Alpmedica
I have DTS Monaco 9 and Openport 2.0. When configuring the adapter, the vendor module name field remains blank and I cannot select a name. Could you help me or give me a tip?
 
Download attachments
  • IMG_4149.png
    IMG_4149.png
    1.2 MB · Views: 729
I have just submitted a registry entry solution for this (its awaiting approval from the mods/admins).
I have just sent you a PM with a link to download in the meantime.
 
  • Like [+1]
Reactions:goberr, SW Solution and geo12
The "Vendor Module Name" does not actually need to be specified, it appears after the MUX is initialized in the system and does not affect anything.
 
  • Like [+1]
Reactions:mbvitebsk and SW Solution
DTS 9 does not connect to SDconnect. It find it in the system settings. Any help?
 
Download attachments
  • 1704315656674.png
    1704315656674.png
    250.9 KB · Views: 705
This version works with SDconnect without any problems by default.
Access to the multiplexer may be blocked by a firewall.
There is no other reasonable explanation.
 
Thanks for the answer, the problem was in the firewall.
 
Can anyone post the DTS 9.02 configuration for eCOM please?
 
  • Like [+1]
Reactions:wolf38

Similar threads

R00TR0w
  • Sticky
  • R00TR0w
  • Marketplace
Replies
0
Views
984
R00TR0w
R00TR0w
F
  • Question
  • Fotom
  • Questions and answers
2 3
Replies
21
Views
5K
Bigovic
B
R00TR0w
  • Sticky
  • R00TR0w
  • DTS Monaco
2
Replies
15
Views
26K
hafsa
H
Back
Top Bottom