pcmhacking.net

Well, I installed VX Manager ... And it shits like my geriatric 17 year old dog, all over the place!

I mean it shit everywhere ... In the Windows tree, in the Programs files tree, in the ProgramData tree, in the User tree and of course the registry!
[edit] Forgot, Start menu and Desktop as well ...
[edit2] Whoops, missed a pile in C ROOT!

And still doesn't work, VX Manager says "No Device(AUTO)"!

It also installed a "TAP-Windows Adapter v9" device under "Network adapters" in Device Manager! ... A Spyware VPN.

BTW, the VX Manager is called AllScanner, and it is complaining about an expired license ...

Sounds like someone had fun with that installer... darn chineese clones of clones of clones......

license expired needs to click on update license once the program connects to the tool.

That's because many people today can't (or are lazy and won't) do their own work, so they steal from others and glue it altogether in some hoaky fashion!
I don't have enough hair to count all the tiny little apps I've seen that install a huge library just for one simple function ... The ultimate in today's LAZY!

As this software apparently is ...

When I try to install PassThru drivers from within VX Manager (AllScanner), it cries about an expired license.

Sure wish the MFG would respond to email so I can get the newer software and PassThru only installation instructions ... The instructions that came with it are for the Ford/Mazda IDS software. And they are inaccurate even for that!

Gampy wrote: 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 ...

Hi all;
Gampy,
IF the device truly has an FTDI interface chip, then the Prolific driver is incorrect.
You need to install the driver from the FTDI website.
Android has a driver built in for the FTDI chip, so you may be able to try an old phone or tablet with a Terminal app.
Just my 2c

Mike

Even the instructions for the GM version of the tool are long winded and full of hacked software links. And the latest VX driver, installs crap everywhere as well but works, never had an issue.
http://www.vxdiag.net/managecenter/download/vxdiag.zip

if you want to inspect the drivers download the drewtech tool. It should show you your DLL and API versions for the cable and what protocols the driver supports.

J2534-1 Bus Analysis Tool

http://drewtech.com/downloads/index.html

I use the VX nano daily. The only file which it drops which causes some antivirus to complain about is the one it uses for its main licensing of the tool which is in the systems folder... hence AV freaks out. It does not do anything malicous and works fine. All other files is drops are either J2534 DLL or DPU DLL. Other thigns are the manager EXE and its tool box exe.

AllScanner are pushing for the new 'over the web' programming, allow for connecting devices over the web for remote programming. This explains any network adaptors installed also.

Thanks The1, I'll definitely give it a try ...

MudDuck, Windows detects the USB->Serial as FTDI, it's actually a Prolific 23xx (2303 I believe), my apologies.

So, I've made some progress.

This device came with two CD's, one looks professionally done (the red one in the first post), the other is definitely DIY, the DIY disk is the infected one with files listed in previous post.

The Second CD (the red one) has the following files,

IDS ford download address.txt
IDS-Operate-Manual.pdf
MazdaIDS-119.00.exe
SVCI_J2534_Ford_Setup_v1.1.9.1.exe
SVCI_J2534_Mazda_Setup_v1.1.9.1.exe
VCI_Software_1.0.0.10.exe
VCI_Software_windows-x32_1.0.0.10_error.log

So, I reset the system back to base and started over, the first thing I installed was "SVCI_J2534_Ford_Setup_v1.1.9.1.exe".

That 67MB Install expanded to ~135MB ... Including, And created the following registry entries,

[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\STIC - SVCI]
"Vendor"="STIC Technology"
"FunctionLibrary"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\SVDIPT32.dll"
"FirmwarePath"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\Firmware"
"Name"="STIC - SVCI"
"ISO15765_PS"=dword:00000001
"ISO15765"=dword:00000001
"ISO9141"=dword:00000001
"ISO14230"=dword:00000001
"CAN"=dword:00000001
"CAN_PS"=dword:00000001
"LogFilePath"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\Log"
"LogLevel"=dword:00000001
"AppType"=dword:00000000

Whoo Hoo! it worked, well kinda, I got the following from PcmHammer,

[03:20:09:359] PCM Hammer 015
[03:20:09:359] Initializing J2534 Device
[03:20:09:359] Loaded DLL
[03:20:10:421] Connected to the device.
[03:20:10:437] Battery Voltage is: 16.878
[03:20:10:437] Failed to set protocol, J2534 error code: 0x00000003
[03:20:10:437] Unable to initialize J2534 Device

At least it connected to the device ... Unfortunately the driver appears to not have J1850VPW capability, or so it seems, I have not investigated that further, yet! (I will, The1)

So I copied the installed files elsewhere and saved the registry settings ...

Reset the system back to base, added the registry settings and the one 8MB DLL pointed to by the registry settings!

It works, and without the ~127MB of bloat!

I did hack PcmHammer and got it to set protocol with a supported protocol, but not J1850VPW ...

The technical information about the device, clearly states it is capable of what I'm asking of it ... J1850VPW PassThru.

[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\STIC - SVCI]
"Vendor"="STIC Technology"
"FunctionLibrary"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\SVDIPT32.dll"
"FirmwarePath"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\Firmware"
"Name"="STIC - SVCI"
"ISO15765_PS"=dword:00000001
"ISO15765"=dword:00000001
"ISO9141"=dword:00000001
"ISO14230"=dword:00000001
"CAN"=dword:00000001
"CAN_PS"=dword:00000001
"LogFilePath"="C:\\Program Files\\STIC\\SVCI Passthru Driver\\Log"
"LogLevel"=dword:00000001
"AppType"=dword:00000000

if this is what the registry has for your driver then it's basically only compatible with those protocols, getting a return 3 with pcmhammer means it doesn't do VPW?

Yup ...

Gampy wrote:I did hack PcmHammer and got it to set protocol with a supported protocol, but not J1850VPW ...

And it seems the manufacture is not as cooperative as they state they are all over their web site.

The email I have received so far is evasive, contradictory and helpless.
However, it appears they have given my account on their site limited download access.

I did see in a update log, a comment about optimizing the J1850VPW code ...

My last email to them was; How to make work J1850VPW PassThru ??