I am using the default settings for Port and Protocol Options. Once it has gone back to red, a few seconds later I get the error message. When I hit the test button, the LED on the interface cable goes from steady red to green for 1 second, red for 1 second, then flashes back and forth rapidly for 3 seconds, then returns to red. With these drivers I have attempted the Test with COM ports 1 to 5 with the same results. Between each attempt at new drivers I made sure to fully uninstall the drivers via the Device Manager to make sure there were no lingering drivers. On trying these drivers, I made sure to go into Device Manager and into the USB device and tried with the 'Load VCP' checkbox both unchecked. I most recently found the link to the virtual COM port drivers located here ( ) hence the out-of-date versions on the drivers noted above. I made many attempts at this including re-installing VCDS once, re-installing the drivers three times, rebooting my computer (Windows 10 on Microsoft Surface 2 computer), trying with car off/accessory mode/on. From the documentation, it seems like this should all work from a compatibility standpoint. The device shows up in Device Manager, noted to be working properly and with what looks to be the correct drivers installed.

When I got it I installed newest version of VCDS 19.6.2 and the newest drivers. This is my first time using the device, I got it used in the mail the other day. There is a little sticker on the connect part that says I am using the HEX+CAN cable with the following writing on it: I just thought that I would mention it since I know Ross-Tech is following this thread.When attempting to Test the device in VCDS, I get the following error message: This issue might cause more problems for new users. This is a minor issue, and since it has happened to me before, it didn't really cause me a problem. In other words, it would have been nice if it actually told me that I needed to update the cable's firmware and told me to test the cable again.

My comment is: When I first tried to do the autoscan, it would have been nice if the error message was more useful. I tested the interface again and it said I needed to update the cable firmware and everything worked correctly. When I first plugged into a car and tried to do an autoscan, I got an error message about not being able to connect (I don't remember the exact message). I upgraded to 11.11.4 when not connected to my car, tested the interface,and saved the configuration (no problem here). Click to expand.The update worked flawlessly on my cable, just as Jef described.

Why vcds 19.6 says interface not found