I am good with computers but no programmer by any means. Not sure what happened, can only speculate that the update didn't fully program properly, or another program slightly modified the cable's data causing it to be seen as a possible clone with the update, causing it to be red flagged by VCDS. Mind you I attempted all of this before the updates, and everything was happy even after those use attempts, but before the updates. Later I find out that the cable doesn't emulate a COM port which is why it didn't work with that reader, and I left it at that as I didn't want to risk the cable. I have done both via Ross tech and vcds loader but after this vcds will not see the interface.
When I tried to use it for the Nefmoto EEPROM reader I didn't do anything with the drivers, simply attempted to connect using all the available COM port settings as I couldn't get a definitive answer as to which COM port the cable uses. Hi all I know there are a lot of post about VCDS showing message of interface not found, the one problem I have is that when the interface is using firmware 1.94, vcds sees it and tells me it’s status, including to update the firmware to 1.96. I tried installing VCDS on my desktop computer, same results.Īlso did a full driver delete (delete drivers, unplug it, plug back in and allow windows to install different drivers, deleted those drivers, repeated until it prompted me to direct it where the drivers are), results are the same.
