Pointless and non-functional mods are more affordable and can still satisfy one's passion for his/her cars. It's a good program to get us started on using their products.
When we want to fork over the extra $ for the full VCDS version and hardware, they will credit us $100 toward that since we paid for VCDS-lite. We are paying Ross-Tech $100 for software. Might want to give it a try.Īlso, I agree with John.
I took a shot at having Windows 7 do an automatic internet search for drivers for my "dumb" / eBay cable (blue, kkl 409.1) and sure enough, the cable works fine now. I know this is an old thread, but hopefully this might help someone. not sure if it's not lighting up because of the com port testing as 4 but actually being 2 or because of a loose connection or both. fairly major point, however it still doesn't explain the com port issue. the blue light doesn't come on any more either. it dose have a blue LED light on top and that part of the tutorial reminded me of another issue. it's blue, two rows of interface pin's etc. I tried to post a pic of it here but it didn't work out. The cable itself is from China I believe and I purchased it on ebay. despite having the tdfi plugged into 1 - 2 the only test that runs correctly is port 4.
I read the how to link posted here (thank-you for that) and I have gone through all that with the end result being that the XP cpu shows the com port as being 1 or 2 depending on where I have it plugged in and the only port that the VAG-COM recognizes is 4. No yellow marker, CPU recognizes the com port and the FTDI and I can change it around no problem (with the exception that a couple of ports are being used for VPN and what ever.). by the way I have searched a lot of sites on the net before making a posting and i have seen numerous people with similar problems but they all seem to be fixed using device manager and adjusting port settings or input rates etc. This has been a three week nightmare, ready to pack up the lap-top, throw it and the cable in the trunk and drive the entire package off a bridge! any help would be appreciated. One, the interface is actually plugged into com port 2, which the test mode does not find and when i plug into the car to try and get a reading it can't find the controller.
it runs the test and tells me that com port 4 is working and the interface is found however there are two problems from here out. Now I have the system back up and running, I have reinstalled the sw and drivers. I went to FTDI site and down loaded the latest driver, BIG MISTAKE, stuck my XP in a boot up loop and had to do a full factory setting recovery.
I could not read the codes a second time when I went to check again so I uninstantiated the sw and reinstalled the sw, drivers etc, still no go. However, now the windows 7 laptop will not recognize the e-bay cable during the com port "test" (never has mind you) and now my xp laptop has it's own set of issues. initially i was able to get the sw installed and it took a reading from the car (2003 A4 1.8T). I have tried running vag-com 409.1 on both windows xp and 7. it is fully windows 7 / 64-bit compatible. The windows 7/xp/ebay vag cable are sketchy at best, its better to run it under xp natively - ask me how I know.Įasiest route to use if you dont feel comfortable with installing operating systems and with the often cryptic instructions on how to do things would be to purchase the ross-tech cable and license. It all depends on how well you can read and figure out how to do the things that you need to do. then you will need a program called bcdedit to make it so you can boot either os when the computer starts.
Or.you can shrink your partition with a program called gparted, its free, then install windows xp/vag-com on the new empty part of the drive.
Or.you can get (whatever way you choose) vmware and install windows xp on a virtual machine, then install vag-com or vcds.
Or.you can download ms virtual pc and windows xp mode and install the driver for the cable in the virtual windows xp as well as the vag-com or vcds. youll also have to enable test mode which will get you a nice little watermark on the desktop that says 'test mode'. you would need to manually 'sign' the drivers with a utility called : driver signature enforcement overrider. If you have 64-bit windows, the driver will have trouble installing.