HEX-COM and VCDS 19.6 crashing

As soon as I start VCDS, and go to test the HEX-COM connection (so I can save the settings and go back to the main screen) I click 'TEST' and VCDS freezes up. It freezes to the point where I have to restart the computer (Windows 7) to close VCDS. The computer continues functioning correctly, VCDS Lite has no issues connecting to the interface, but can't connect to the controller. I've tried a cheap KKL cable, and my HEX-COM cable from RossTech, and the issue is the same from both. I've tried running VCDS (full) in XP compatibility mode, but I get the same result. I have 'run as administrator' or whatever checked on both Lite and full VCDS, I've been through the power settings to be sure they say "disabled", everything is up to date. Can anyone help me out? I feel like I'm missing something.

Please post the details of your PC hardware, and which version of Windows you are running.

Windows 7 ultimate 64, AMD Athlon X2 CPU, VCDS 19.6.2, HEX-COM interface.

Since you say you have a HEX-COM, I have to ask: Does this computer have an actual RS-232 serial port?

-Uwe-

No, I've got an adapter that converts it to USB. I'm lost because my buddy that I bought the HEX-COM from used it in the same configuration for a couple years without issue.

Sounds like a problem with the driver for that USB<->Serial converter.

-Uwe-

Hmmm... I've uninstalled and reinstalled all the drivers for the main cable, but I didn't even check the drivers for that! I'll check that and report back.

Rail_Life_217 said:

Hmmm... I've uninstalled and reinstalled all the drivers for the main cable, but I didn't even check the drivers for that! I'll check that and report back.

Click to expand...

A HEX-COM uses no special drivers. It's an RS-232 serial port device. Windows provides the driver for a physical serial port.

-Uwe-

I had to install the FTDI drivers for the cheap KKL cable for Vag Commander 2.5.

I fixed the crashing issue, by uninstalling VCDS and reinstalled it without the 32 bit option. That box checks itself on install, and I guess when I previously installed it I didn't uncheck it.

Scratching head. I don't really see why "Install 32-bit EXE on 64-bit System" would check itself.

Can you please right-click the installer, select Properties, and post a screen-shot of the properties sheet?

-Uwe-

I'd be happy to! I'm at work right now, but I'll get it posted in the morning.