Page 1 of 4 123 ... LastLast
Results 1 to 10 of 38

Thread: Hex+Can interface not found by VCDS

  1. #1
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like

    Hex+Can interface not found by VCDS

    As the title states, ever since updating to VCDS 14.10, and its associated firmware update, my cable cannot be found by VCDS. It appears in the device manager and is stated to be working properly. I am able to use it with other programs so the cable itself is functional, it seems to have lost its identifier during the update.


    Here is what I get when I test the connection in the options tab.


    Here is a screen shot of the device manager along with the interface's serial number info.

    Is there a source to download and attempt to reflash the firmware on the cable to try to restore connectivity with VCDS? I have an airbag light that is ready to be cleared, but can't do so without access.

  2. #2
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    26,911
    Post Thanks / Like
    Blog Entries
    1
    I am able to use it with other programs
    What other programs have you used with it? The most likely explanation here is that one of them reprogrammed it for its purposes, something which is quite rude.

    -Uwe-
    Last edited by Uwe; 11-23-2014 at 10:12 AM.

  3. Likes Eric liked this post
  4. #3
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like
    I have used it with the Nefmoto flasher/logger program, which isn't supposed to make any changes, just requiring the cable to be in dumb mode. I haven't heard of anybody having issues using a genuine Ross-Tech cable with it.

    Will I have to send the cable back in to be reprogrammed?
    Mk4 GTI GLS 1.8T

  5. #4
    Verified VCDS User golfi_vend's Avatar
    Join Date
    Apr 2014
    Location
    Tartu, Estonia
    Posts
    2,065
    Post Thanks / Like
    How about reinstall of VCDS?
    I am a VW Freak - Le WV Freaks OR Come visit me at my work with ODIS concerns - FORSS ODIS GeKo/FaZit access for VW/AUDI/Škoda
    The world is my oyster...

  6. #5
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like
    I tried reinstalling VCDS multiple times. Still the same error.

    I also attempted to connect to the ECU with an EEPROM reader available on the Nefmoto site, to make a copy of my immo data, but it could never connect, until I found out the Hex+Can cable doesn't make an 'official' COM port so it would never work with this cable anyway. It runs off of basic command lines, none which involve changing any of the COM port parameters, so I doubt it reprogrammed the cable.
    Mk4 GTI GLS 1.8T

  7. #6
    Verified VCDS User NZDubNurd's Avatar
    Join Date
    Nov 2014
    Location
    New Zealand
    Posts
    1,078
    Post Thanks / Like
    I thought to get the "nefmoto" EEPROM reader (not the tuning software) to work with it, you have to use a different driver (for the com port issue), which it may have installed, instead of the Ross-Tech driver (though the tiny EXE that does it shouldn't be capable of doing it itslef)

    I've not tried to use the VCDS cable for anything, just in case thins happened Though I actually thought it would be pretty unlikely to happen - maybe you're the prrof it can

    If you install VCDS on another PC, it should determine whether the cable or the PC has a problem. Perhaps the driver has been changed on the PC, and it's not updating the driver, hence it still not working??? Or maybe a registry entry that stays after uninstall is still there, upsetting it?

  8. #7
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like
    I tried installing VCDS on my desktop computer, same results.

    Also 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.

    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. 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.
    Mind you I attempted all of this before the updates, and everything was happy even after those use attempts, but before the updates.

    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. I am good with computers but no programmer by any means.
    Last edited by MoparFreak69; 11-23-2014 at 05:44 PM. Reason: Forgot some info
    Mk4 GTI GLS 1.8T

  9. #8
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    26,911
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by MoparFreak69 View Post
    Will I have to send the cable back in to be reprogrammed?
    Not sure. We can try some stuff, but I'd like to do that via e-mail. Please send an e-mail to Support@... and include a link to this thread.

    -Uwe-

  10. #9
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like
    Done, thanks!

    Hopefully we can figure out what happened to prevent possible future user error if I caused it.
    Mk4 GTI GLS 1.8T

  11. Likes Uwe, Eric liked this post
  12. #10
    Verified VCDS User
    Join Date
    Nov 2014
    Location
    Boise ID
    Posts
    10
    Post Thanks / Like
    Well, still unsure what caused my issue, but the problem has been remedied. I ended up finding a similar program to the one you pointed me to, Uwe, as it wouldn't program the info correctly for some unknown reason. Anyway, everything is back to how it should be and I have full functionality again. Thanks a ton for your assistance!
    Mk4 GTI GLS 1.8T

  13. Likes Uwe liked this post

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •