STiC Technology SVCI J2534 Tool

Programs / Tools / Scripts
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

STiC Technology SVCI J2534 Tool

Post by Gampy »

Yesterday when we got back from my pulmonologists, we found a box on the porch, I grabbed some gloves (I don't touch anything outside my bubble, and nothing comes into my bubble without a 24 hour quarantine) and opened the box, this is what was inside,
STiC-J2534-35%.png
STiC-J2534-35%.png (1.34 MiB) Viewed 5384 times
It says it's for Ford/Mazda, it also says it supports J1850VPW (among others).
So, I figured what the hey, lets try it, so I popped the first of two CD's into a drive and Whammo!
The file
sp312 VCI Manager(JLR) 19.09.09.exe
is infected with the
Win32/Sality.AT
virus so says MSE.

No biggie, I'm on a isolated and protected machine so I dig through the hacked Proprietary Ford and Mazda software included on the CD and find just the drivers for the device.

They test clean on multiple machines and online so I moved them to a test system and installed them!

Whoo Hoo, all went fine, I now have a HKLM registry entry; "Software\\PassThruSupport.04.04" with the following keys and values,

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\Diagnostic Associates Ltd - DA-Dongle]
"Name"="DA-Dongle"
"Vendor"="Diagnostic Associates Ltd"
"ISO15765"=dword:00000002
"ISO15765_PS"=dword:00000002
"CAN"=dword:00000002
"CAN_PS"=dword:00000002
"ISO9141"=dword:00000001
"ISO9141_PS"=dword:00000001
"FunctionLibrary"="C:\\Program Files\\Diagnostic Associates Ltd\\DA J2534 Software\\DA1253432.DLL"
"LogfilePath"="C:\\Program Files\\Diagnostic Associates Ltd\\DA J2534 Software\\DAJ2534.log"
"LogEnabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\Diagnostic Associates Ltd - DAVINA2]
"Name"="DAVINA2"
"Vendor"="Diagnostic Associates Ltd"
"ISO9141"=dword:00000001
"ISO9141_PS"=dword:00000001
"J1850PWM"=dword:00000001
"ISO15765"=dword:00000002
"ISO15765_PS"=dword:00000002
"CAN"=dword:00000002
"CAN_PS"=dword:00000002
"FunctionLibrary"="C:\\Program Files\\Diagnostic Associates Ltd\\DA J2534 Software\\DA2253432.DLL"
"LogfilePath"="C:\\Program Files\\Diagnostic Associates Ltd\\DA J2534 Software\\DAJ2534.log"
"LogEnabled"=dword:00000000
And the files
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DA1253432.dll
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DA2253432.dll
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DACAN Driver
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DAJ2534Installer.dll
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DAJ2534Installer.InstallState
C:\Program Files\Diagnostic Associates Ltd\DA J2534 Software\DACAN Driver\CDM20600.exe
Right off I notice there is no J1850VPW registry entry ... Bah Humbug!
O-wells, PcmHammer should at least load the DLL, it's just not going to communicate ...

Unfortunately PcmHammer returns false from LoadLibrary, line 295 in J2534Device.cs,

Code: Select all

            if (J2534Port.Functions.LoadLibrary(J2534Port.LoadedDevice))
[10:28:22:149] PCM Hammer (3/12/2021, 10:19 AM)
[10:28:22:158] Initializing J2534 Device
[10:28:22:171] Unable to load the J2534 DLL.
[10:28:22:176] Unable to initialize J2534 Device
Any brainiac diagnostic tips/ideas for diagnosing this LoadLibrary failure ??
Last edited by Gampy on Fri Mar 19, 2021 2:04 am, edited 3 times in total.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
Charlescrown
Posts: 1831
Joined: Sat Aug 06, 2011 7:58 am
cars: V8 VR Commodore BT1
LB Lancer 2L turbo & Delco
Starion TBI with Delco
Mitsubishi Lancer EVO4 track car
NA MX5
3 vintage motor bikes
Location: Padstow NSW

Re: STiC Technology SVCI J2534 Tool

Post by Charlescrown »

I'll be interested in know just what you can do with that unit.
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: STiC Technology SVCI J2534 Tool

Post by Gampy »

Yea, Me too ...

So, it appears the dll's have dependencies not found ... At least I'm assuming that, due to the following,
> dumpbin /imports da1253432.dll
. FTD2XX.DLL
. MFC80.DLL
. MSVCR80.DLL
. KERNEL32.DLL
. ADVAPI32.DLL

Files not found ...
MFC80.DLL
MSVCR80.DLL

I can only assume they will also have dependencies I'll not have!

So off scrounging I go ...
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: STiC Technology SVCI J2534 Tool

Post by Gampy »

Woo Hoo!

Went from
[10:28:22:149] PCM Hammer (3/12/2021, 10:19 AM)
[10:28:22:158] Initializing J2534 Device
[10:28:22:171] Unable to load the J2534 DLL.
[10:28:22:176] Unable to initialize J2534 Device
to
[10:31:51:420] PCM Hammer (3/12/2021, 10:19 AM)
[10:31:51:429] Initializing J2534 Device
[10:31:51:476] Loaded DLL
[10:31:51:488] Unable to connect to the device.
[10:31:51:492] Unable to initialize J2534 Device
With the installation of: Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update that installs the missing mfc80.dll and msvcr80.dll.

The official web site for this tool flyobd.com has newer software and drivers, but you have to jump through hoops to get them ... I have an e-mail off to the developer, we'll see.

It appears this tool also has a ScanTool STN1170 chip in it or at least emulates one ... It has a button to flip between the two.
[10:54:26:553] PCM Hammer (3/12/2021, 10:19 AM)
[10:54:28:350] Voltage: 20.6V
[10:54:28:350] Elm ID: ELM327 v1.3a
[10:54:28:366] ScanTool device ID: STN1170 v3.3.1
[10:54:28:397] Unable to initialize ObdLink ScanTool on COM5
It does install a FTDI device in Device Manager ...
Prolific USB-to-Serial Comm Port (COM5)
However, as you can see it doesn't connect, It may be the STN firmware version.

Time to get back at it ...
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: STiC Technology SVCI J2534 Tool

Post by Gampy »

Does a J2534 Tool install a device in device manager ??

How does the DLL know where the tool is, what is the connection/port/etc... ??
Obviously it's via USB, how does the dll know that!

Now that the DLL is loaded, line 329 in J2534Device.cs,

Code: Select all

J2534Port.Functions.PassThruOpen(IntPtr.Zero, ref DeviceID)
errors with
ERR_DEVICE_NOT_CONNECTED
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
The1
Posts: 4694
Joined: Mon Jan 04, 2010 10:23 am

Re: STiC Technology SVCI J2534 Tool

Post by The1 »

usually you have a com port for the device.

The program searchs the registry for the cables dll to load then sends the passthrou commands to it.

So sounds like the cable driver isn't installed.
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: STiC Technology SVCI J2534 Tool

Post by Gampy »

It does create a COM port ... Recognized as an FTDI USB-Serial, see post #4.

The Tools J2534 DLL's are installed ... Including the registry entries, see post #1.
PcmHammer successfully loads the DLL's ... Unfortunately it cannot open the port, see post #5.

It's like something is missing between the J2534 DLL's and the tool.

And the damn manufacture is ignoring email communication attempts.
You not only have to create an account on the manufactures site, you also have to have a password to download updated software and drivers.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
jxx
Posts: 153
Joined: Tue Oct 25, 2011 7:47 pm
cars: To many
Location: Vic

Re: STiC Technology SVCI J2534 Tool

Post by jxx »

Possibly a clone VCM II

Does it come with an early VX driver (VX Driver VCMII 1.X.X.XXXX)?

Does VX Manager detect and show any info on it?
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: STiC Technology SVCI J2534 Tool

Post by Gampy »

Obviously I'm not just willy nilly installing everything on the CD ... And I have never installed nor seen an installed J2534!

I'm trying to install the minimums for PassThru operations, not the whole shitload of Ford/Mazda specific crap that I don't need nor want!

It does state that it can also be used as a stand alone J2534 PassThru device compatible with other J2534 software ...

This is the file list on the infected CD ...
DA J2534 Device Setup V4.0
FORDZ_VCMII drivers
MAZDA_VCMII drivers
MongoosePro_JLR.msi
sp312 VCI Manager(JLR) 19.09.09.exe
T6 wiScan V3.11.exe
VX Manager 1.6.2.0902.exe
The only thing I have installed is the "DA J2534 Device Setup V4.0".

"sp312 VCI Manager(JLR) 19.09.09.exe" ... It is infected with Sality virus according to multiple different tests, I will not execute it.
This may very well be the problem, unfortunately support fails to respond for a replacement.

I could install "VX Manager 1.6.2.0902.exe", it tests clean ... Do I really need it ??
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
jxx
Posts: 153
Joined: Tue Oct 25, 2011 7:47 pm
cars: To many
Location: Vic

Re: STiC Technology SVCI J2534 Tool

Post by jxx »

Yeah it's a VX Diag VCM II clone.
Basically a VCXNano for ford/mazda.

Guessing it'll have a serial like "N52FMxxxxx"

I have a much older VCM II clone that I use for ford stuff, I haven't had much luck getting it to work on some of these programs, iirc I did get it to work with tech2win but only on can (like the vx nano no gm lan)

Maybe someone else can chip in if there's a work around to get these working without installing vx manager.
If not install vx manager and just the pass thru driver, or you could get the latest driver from vx diag website.
Post Reply