![]() The VCDS cable is about 7-10 years old (KEY-USB) software is current version (14.10) running on a MacBook Pro using a VirtualBox Windows XP install that has worked fine for at least 3 years. The car's a 2004 1.8T which runs well and has been fault free for the last 6 months (last big problem was rich fuel trims, fixed by replacing the cracked intercooler). Now, it's opted out of connecting to anything at all. Most recently, the software completed an autoscan of the engine controller but just froze on trying to access the ABS module. Initially, the software would read the ECU codes and engine measuring blocks fine but has gradually gotten flaky in connecting. The major issue is this: I've had increasingly greater difficulties running scans the last month or so. I'm wondering if anyone else has had a similar set of issues and thank you in advance for any help you might have. ![]() I'm trying to diagnose a problem connecting with VCDS, which I use to run fault scans and fuel trims every couple of months just to stay on top of things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |