Multiple J2534 devices conflict?

XLR8T · **Joined:** Fri Oct 12, 2012 2:20 pm **Posts:** 52

Hi all,

I'm having some trouble getting RomRaider Logger to connect to my Openport 2.0.
The Debug log shows it's attempting to use my openport, but it doesn't connect, and when the "Device Explorer" opens, it shows all of the other J2534 devices as offline but never shows my Taxtrix OP2. Device Explorer also keeps popping up over and over and over again when it can't connect, this part is frustrating. it would be nice to just select J2534 devices from a dropdown like the COM ones on the top left. I digress...

What complicates this is likely that I've started using my laptop for a lot of other automotive diagnostics. GM, Ford, Subaru SSM, etc. and have these other drivers installed. But there must be a better way than having separate laptops for certain cars.

Only 32bit Java is installed. Windows 10 64bit. Ensured the right logger definitions being used - in this case SD 1.8 for Carberry 4.2.
Ecuflash is able to read and write, I've also reinstalled the latest J2534 drivers from Tactrix and verified with EcuFlash again so it seems to be RomRaider that's having the issue.
I did try on a different laptop and the same cable/tactrix worked with the same J2534 driver and logger works fine.

Log:

7550 DEBUG [Thread-6] - QueryManager started.
8037 DEBUG [Thread-6] - Found J2534 Vendor:Bosch - Ford-VCM-II | Library:C:\Program Files (x86)\Bosch\VTX-VCI\VCI Software (Ford)\Products\Ford-VCM-II\Dynamic Link Libraries\BVTX4J32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Bosch - MDI | Library:C:\Program Files (x86)\GM MDI Software\Products\MDI\Dynamic Link Libraries\BVTX4J32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Bosch - MDI 2 | Library:C:\Program Files (x86)\GM MDI Software\Products\MDI 2\Dynamic Link Libraries\BVTX4J32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Bosch - VCM3 | Library:C:\Program Files (x86)\Bosch\VTX-VCI\VCI Software (Ford-VCM3)\Products\VCM3\Dynamic Link Libraries\BVTX4J32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Bosch - VCMM | Library:C:\Program Files (x86)\Bosch\VTX-VCI\VCI Software (Ford)\Products\VCMM\Dynamic Link Libraries\BVTX4J32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:DENSO CORPORATION - DST-i | Library:C:\ProgramData\VCX\Apps\SUBARU\VCXSDI32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:GM - Tech2 | Library:C:\Program Files (x86)\GM\Tech2 J2534 DLL\Tech2_32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Hitachi Car Engineering Co., Ltd. - Pass-Thru NSMIF32 | Library:C:\ProgramData\VCX\Apps\SUBARU\VCXSDI32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:C:\WINDOWS\SysWOW64\op20pt32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:Teradyne - GNA600 | Library:C:\Program Files (x86)\Ford Motor Company\IDS\Runtime\DS253432-04.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:TOYOTA - J2534 | Library:C:\ProgramData\VCX\Apps\TOYOTA\VCXPT32.dll
8037 DEBUG [Thread-6] - Found J2534 Vendor:VXDIAG - J2534 | Library:C:\ProgramData\VCX\Apps\PASSTHRU\VCXPT32.dll
8037 INFO [Thread-6] - Re-trying previous J2534/ISO15765 connection: Bosch - MDI 2

dschultz · **Posted:** Mon Sep 06, 2021 8:41 pm

On my system I have multiple J2534 drivers. With none connected here's the connection attempt listing.

Code:

7915  DEBUG [Thread-5] - Found J2534 Vendor:ALLScanner - VCX | Library:C:\Program Files (x86)\ALLScanner\VCX32\VCX32.DLL
7916  DEBUG [Thread-5] - Found J2534 Vendor:DENSO CORPORATION - TIS Techstream VIM | Library:C:\Program Files (x86)\Toyota Diagnostics\Techstream\Bin\ComTol32.dll
7916  DEBUG [Thread-5] - Found J2534 Vendor:Drew Technologies Inc. - Mongoose ISO/CAN | Library:C:\WINDOWS\system32\MONGI432.dll
7916  DEBUG [Thread-5] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:C:\WINDOWS\SysWOW64\op20pt32.dll
7916  DEBUG [Thread-5] - Found J2534 Vendor:Teradyne - GNA600 | Library:c:\GenRad\DiagSystem\Runtime\DS253432-04.dll
7917  DEBUG [Thread-5] - Found J2534 Vendor:XHorse - MVCI | Library:C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS\MVCI32.dll
7917  INFO  [Thread-5] - Re-trying previous J2534/ISO14230 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
8009  INFO  [Thread-5] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
8009  INFO  [Thread-5] - null, trying serial connection...
8023  INFO  [Thread-5] - Connected to: COM1
11680 DEBUG [Thread-5] - Serial Bad Read response (read timeout): 
11810 INFO  [Thread-5] - Connection closed.
11814 DEBUG [Thread-5] - Error sending init
...
12826 DEBUG [Thread-5] - Found J2534 Vendor:ALLScanner - VCX | Library:C:\Program Files (x86)\ALLScanner\VCX32\VCX32.DLL
12827 DEBUG [Thread-5] - Found J2534 Vendor:DENSO CORPORATION - TIS Techstream VIM | Library:C:\Program Files (x86)\Toyota Diagnostics\Techstream\Bin\ComTol32.dll
12828 DEBUG [Thread-5] - Found J2534 Vendor:Drew Technologies Inc. - Mongoose ISO/CAN | Library:C:\WINDOWS\system32\MONGI432.dll
12829 DEBUG [Thread-5] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:C:\WINDOWS\SysWOW64\op20pt32.dll
12830 DEBUG [Thread-5] - Found J2534 Vendor:Teradyne - GNA600 | Library:c:\GenRad\DiagSystem\Runtime\DS253432-04.dll
12831 DEBUG [Thread-5] - Found J2534 Vendor:XHorse - MVCI | Library:C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS\MVCI32.dll
12831 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: XHorse - MVCI
12846 INFO  [Thread-5] - XHorse - MVCI is not available: J2534 initialization: Unable to load library 'C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS\MVCI32.dll': The specified module could not be found.
12846 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: Teradyne - GNA600
13771 INFO  [Thread-5] - Teradyne - GNA600 is not available: J2534 initialization: PassThruOpen error [26:ERR_INVALID_DEVICE_ID], 
13771 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
13776 INFO  [Thread-5] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
13776 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: ALLScanner - VCX
14713 INFO  [Thread-5] - ALLScanner - VCX is not available: J2534 initialization: PassThruOpen error [26:ERR_INVALID_DEVICE_ID], 
14713 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: DENSO CORPORATION - TIS Techstream VIM
16991 INFO  [Thread-5] - DENSO CORPORATION - TIS Techstream VIM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], 
16991 INFO  [Thread-5] - Trying new J2534/ISO14230 connection: Drew Technologies Inc. - Mongoose ISO/CAN
17003 INFO  [Thread-5] - Drew Technologies Inc. - Mongoose ISO/CAN is not available: J2534 initialization: Unable to load library 'C:\WINDOWS\system32\MONGI432.dll': The specified module could not be found.
17003 INFO  [Thread-5] - J2534 connection not available, trying serial connection...
17011 INFO  [Thread-5] - Connected to: COM1
...

When I plug the cable in, it repsonds with:

Code:

454603 INFO  [Thread-13] - Trying new J2534/ISO14230 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
454628 INFO  [Thread-13] - J2534 Version => firmware: 1.16.4769, dll: 1.01.4247 Apr 18 2014 16:14:11, api: 04.04

I'm using Win10 (64-bit) and Java 8.0.302.8 (32-bit), Device Manager shows the OP2 attached under "Vehicle PassThru Interfaces".

There must be an issued with your OP2 laptop installation.

XLR8T · **Joined:** Fri Oct 12, 2012 2:20 pm **Posts:** 52

Thanks for the feedback! it looks like you've discovered VXDiag.
My OpenPort is also showing under Vehicle Passthru Interfaces in device manager.

In at attempt to remove this driver, I've:
Uninstalled the device from Device manager, checking the option to remove driver.
Uninstalled the OP2-2534 software from programs list
Deleted HKLM\SOFTWARE\PassThruSupport.04.04\Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM]
Deleted C:\Windows\SysWOW64\op20pt32.dll

I'm still getting the same error on reinstall so far.
Running Java 8 v301 32bit

dschultz · **Posted:** Sun Sep 26, 2021 5:39 pm

The PassThrough entries on in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04\ of the Registry.

XLR8T · **Joined:** Fri Oct 12, 2012 2:20 pm **Posts:** 52

What version of Windows are you running?
My first problem machine is version 20H2.

My other laptop that was working was version 2004 and after upgrading to 21H1 and no other software or configuration changes, logger no longer connects.
Tried removing drivers so it shows as a COM port, as well as reinstalling the taxtrix J2534 drivers and no dice yet.

I'll make sure I remove that key as well when I troubleshoot tomorrow.

XLR8T · **Joined:** Fri Oct 12, 2012 2:20 pm **Posts:** 52

Well F*ck me, I had 2 issues! :lol:

Used the java uninstaller from the program files folder. Installed RR 0.7.2 (I think it was 0.7.0 before?)

And got this:

13502 INFO [Thread-6] - Re-trying previous J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
13538 INFO [Thread-6] - J2534 Version => firmware: 1.16.4819, dll: 1.02.4820 Jul 6 2016 17:20:04, api: 04.04
13549 DEBUG [Thread-6] - J2534/ISO9141 set connection properties: bits=8, parity=0
13551 DEBUG [Thread-6] - J2534/ISO9141 success: deviceId:3, channelId:5, msgId:0
13554 INFO [Thread-6] - J2534/ISO9141 connection initialised
13557 DEBUG [Thread-6] - ECU Init Request ---> 8010F001BF40
*multiple skipped lines*
15599 DEBUG [Thread-6] - Error sending init

Since the new error I looked further into the connections, I have one weak pin in my car's OBD2 port as well!

In hindsight though, it would be awesome to choose J2534 devices the same way we could COM ports

dschultz · **Posted:** Sat Oct 02, 2021 11:57 am

My version is: 21H1

XLR8T wrote:

In hindsight though, it would be awesome to choose J2534 devices the same way we could COM ports

Or maybe an option to select the preferred J2534 device to use after scanning the registry?
We still need to consult the registry as RomRaider needs to know all the driver and library info to access the J2534 device successfully.

RomRaider

Forum rules

Multiple J2534 devices conflict?

Who is online