Using VCDS Lite with Windows 10 and cheap cable

[nesshead6]

Does anyone know how to get VCDS Lite working on windows 10 with one of these ebay special cables? http://www.ebay.co.uk/itm/USB-Cable-...sAAOSwB09YGzQD

I've configured the com port to match up but VCDS won't recognise the interface. When trying to install the cable drivers from the provided CD I get an error message. I've tried installing the drivers in windows 7/8 mode and by copying the files over to the computer first but still no joy. The ebay seller says it should work but doesn't know how... anyone know the secret?

[HPsauce]

I have VCDS-Lite working with a cheap(ish) cable with Windows 10. Didn't install any drivers at all, it just used the standard W10 ones.
(I think it ends up as COM3 by default)
My copy of VCDS is a purchased registered one (upgraded from VAGCOM), not that I think that makes any difference.

[nesshead6]

My understanding is that I need drivers for the interface/cable itself? Could be wrong though.

[HPsauce]

It will need drivers, but if it's a half-decent cable using a sensible serial interface Windows will have or find them.
Just plugged my cable into a W10 64-bit desktop and the driver (version 2.12.16.0) is signed by "Microsoft Windows Hardware Compatibility Publisher" provided by FTDI and dated 09/03/2016.
It came up as COM3.

[RichLV]

Only old VAG-COM cables need separate drivers as they are working as a COM port emulator. If the cable (& software) is capable of natively interfacing via USB, the drivers are found automatically. I have a China VCDS 12.12 cable & software for that version. Works flawlessly plug & play.

[nesshead6]

Only old VAG-COM cables need separate drivers as they are working as a COM port emulator. If the cable (& software) is capable of natively interfacing via USB, the drivers are found automatically. I have a China VCDS 12.12 cable & software for that version. Works flawlessly plug & play.

Could you post a link to where you bought yours please as I can't get VCDS lite to recognise the cable I have.

[Colesy]

Have you tried it in each USB port? I remember mine would only work in one of them.

[HPsauce]

Open up Device Manager and observe the Port appear as you plug it in. Then configure VCDS to use that port.
I too have had issues where not all USB sockets work. Not 100% sure why.

[nesshead6]

I've configured the cable to use port COM2 and have selected port COM2 in VCDS. Upon pressing the 'Test' button in VCDS it comes up with "Port Status: OK. Interface: Not Found!"

I've now tried downloading the drivers from FTDI as mentioned by HPsauce above, not having much luck with that either though. Although I'm not sure if Windows has installed them as it keeps saying that the currently installed drivers are up to date.

[HPsauce]

Is it connected to the car (ignition on) when you test it?

And how/why configure to COM2?

You really shouldn't need to download or install any drivers yourself (W10 does it) and your cable may use different ones to mine.

[nesshead6]

I configured through the device manager as shown on the Ross Tech website. You have to choose from port COM1 to COM4 as those are the ones that you can choose from in VCDS. I chose COM2 as the others were shown by the device manager as being in use, although I have tried configuring it to all the others for arguments sake but it was just the same. I've also tried it plugged into the car.

I'm thinking that maybe the cable I got is for an older version of VCDS. Could you tell me where you got your cable from please?

[RichLV]

It seems you all have the old COM based cables. Just get a newer, USB based one. You'll just need to source a VCDS for it somewhere as the software supplied with it usually sucks.

https://www.aliexpress.com/af/hex-can-usb.html?ltype=wholesale&d=y&origin=n&isViewCP=y&catId=0&initiative_id=SB_20170117005005&SearchText=hex+can+usb&blanktest=0&isAfChannel=y

I have the 12.12, which is fairly old now. You can also see that 16.8 is available.

Also remember that these are hacked cables, meaning you CANNOT run VCDS newer than the cable is meant to be for (if cable is 12.12, you can't run VCDS higher than that, even by minor incremental version, meaning that 12.12.1 is not allowed), otherwise it burns/blocks the hacked chip on the cable and you can throw it in the bin.

[nesshead6]

Thanks for that, I only downloaded VCDS a couple of days ago so that probably explains it.

[HPsauce]

I think you may be being led in the wrong direction by the comments about hacked cables.
The eBay listing is quite clear that it works (in a limited way) with VCDS-Lite (not full VCDS) and ADVISES that you download the latest copy from Ross-Tech.
It also points out (correctly) that an upgrade to full functionality has a cost. Without that you are using the shareware version, which is nonetheless useful.
As such, it just looks like a "vanilla" 3rd-party cable that will (should) work fine on older cars (e.g. S2) but with some restrictions on functionality.

I'd be contacting the seller to tell them what you have done and say it doesn't work. They may know why, or it may just be a faulty cable.

[RichLV]

I think you may be being led in the wrong direction by the comments about hacked cables.
The eBay listing is quite clear that it works (in a limited way) with VCDS-Lite (not full VCDS) and ADVISES that you download the latest copy from Ross-Tech.
It also points out (correctly) that an upgrade to full functionality has a cost. Without that you are using the shareware version, which is nonetheless useful.
As such, it just looks like a "vanilla" 3rd-party cable that will (should) work fine on older cars (e.g. S2) but with some restrictions on functionality.

I'd be contacting the seller to tell them what you have done and say it doesn't work. They may know why, or it may just be a faulty cable.

I've seen these advices before and killed 2 cables in my ignorance. And I'm also running full VCDS without any restrictions, at least I haven't encountered any. Have been connecting cars up to 2011 m.y., doing adaptations, etc.

Just sharing my own experience.