- #VCDS 12.12 CONNECTION PROBLEMS CRACKED#
- #VCDS 12.12 CONNECTION PROBLEMS INSTALL#
- #VCDS 12.12 CONNECTION PROBLEMS DRIVERS#
Maybe theyd replace it if its internally faulty.įeel free to PM me if you want more details on something. I've recovered many of our electronics by replacing blown capacitors. If your cable used to work intermittently but now it doesn't it could also be some electrolytic capacitor inside it that finally gave up. I had some timeouts on my vcds cable when I used a USB extension cable a while back to reach further than it would allow.
I would try a different USB port on the the mac (uugh, I do remember it being a pita to set up properly through VB), or perhaps keep the whole rig still while you are scanning it, in case there is a connection issue. I think it would be safe to assume that your ecu is most likely not the cause here. Since with your android setup you are bypassing both the USB connection and vcds cable completely, I'd look at those. I am guessing you didn't change anything on the VB or XP side - my VB is some old 4.x version, basically the one I managed to setup after repeated attempts. including models using a direct CAN connection fordiagnostics. Was it at some point timing out trying to connect to the ecu? VCDS Hex USB diagnostic cable for Audi VW OBD2 interface vcds cable 12.12 VAG Diagnostic. Wow, I have an almost identical set up (with an native xp desktop in the garage as a backup).
#VCDS 12.12 CONNECTION PROBLEMS DRIVERS#
I've already removed/reinstalled the VCDS software and drivers once, checked the car's floors to see that there's no water around, and functionally tested the usual offender (ABS module) by hammering the brakes a couple of times under safe but slippery conditions: I get the usual "driving on marbles" feeling without locking them up. What's throwing me about this is that my Android phone, with Torque and an OBDLink LX Bluetooth adapter (the $70 fairly reputable version), tells me there are no fault codes stored and will happily log any ECU parameter I want (fuel trims, boost, rpm, etc) forever. KWP2000 communication problems, also in a Passat B5 Euro, already a very long time.
#VCDS 12.12 CONNECTION PROBLEMS INSTALL#
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. Dac ai ultima versiune de vcds (12.12) in longcoding la experimental.
#VCDS 12.12 CONNECTION PROBLEMS CRACKED#
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 kommentar(er)
