Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 30

Thread: HEX-NET via NET vs USB experiences.

  1. #11
    Ross-Tech Employee Dana's Avatar
    Join Date
    Jan 2014
    Location
    United States
    Posts
    3,632
    Post Thanks / Like
    Quote Originally Posted by BaraJag View Post
    Now I seem to not have any issue going from NET to USB, however the other way around (USB->NET) usually requires me to unplug the HEX-NET from both the car and the cable, to reset it (I presume?).

    Aside from this I have yet to be able to get it to connect to my wifi network automatically after using it in AP mode, now my router is an Apple one so might have something to do with that, when I go into options through VCDS mobile and do it manually it connects right away.

    Anyhow let me know what you think about these things?
    Hello,

    This is something we are looking into and as Uwe mentioned the WiFi chipset may be the common factor. You aren't alone there with the Beta USB scan followed by -> Beta NET scan without a reboot - but I haven't been able to duplicate the issue with 100% consistency. I've used several PCs (ranging from XP to Windows 7) on a 2002 old-school Gti to my reasonably modern 2012 Tiguan and experienced that exact issue, but it worked properly a few times?!?

    In the meanwhile - you mentioned that VCDS Mobile connects right away. I had a 50/50% success rate with that immediately after experiencing the wired Beta scan -> AP mode issue. The next time you happen to try that can you confirm that when VCDS Beta cannot find the interface (Interface Not Found) -or- communicate properly that VCDS Mobile (via a web browser in AP mode | 192.168.0.1) works with consistency without rebooting the interface itself? I'm going to do the same on more than one car/PC and look into the Vign: 0.03V settings you mentioned as well. Likewise, I haven't tweaked any of my power settings in the HEX-NET either.

    -Dana

  2. #12
    Verified VCDS User
    Join Date
    Feb 2014
    Posts
    2
    Post Thanks / Like
    I am experiencing almost the same problem.
    Plug hex-net in wait for lights to go green. Open vcds 14 test connection all ok. When i attempt to auto scan or open any control modules i get "no response from controller"
    Sometimes I can wait it out and it starts to work, most of the time I unplug it and plug it back in to reset, I have much better luck connecting in vcds 14 on AP mode. If I get the no response message close vcds 14 and open vcds mobile it works flawlessly. I am running 8.1 on an asus k53e laptop. I'll throw vcds 14 on an xp machine and let you know if i have the same issues.

  3. #13
    Ross-Tech Employee Dana's Avatar
    Join Date
    Jan 2014
    Location
    United States
    Posts
    3,632
    Post Thanks / Like
    Quote Originally Posted by tmorgan View Post
    I am experiencing almost the same problem.
    Plug hex-net in wait for lights to go green. Open vcds 14 test connection all ok. When i attempt to auto scan or open any control modules i get "no response from controller"
    Sometimes I can wait it out and it starts to work, most of the time I unplug it and plug it back in to reset, I have much better luck connecting in vcds 14 on AP mode. If I get the no response message close vcds 14 and open vcds mobile it works flawlessly. I am running 8.1 on an asus k53e laptop. I'll throw vcds 14 on an xp machine and let you know if i have the same issues.
    Please do and if you have the time grab the WiFi Chipset details from each PC (even if one works and the other doesn't).

    Thanks,
    Dana


    Edit: Taylor, I just noticed you are from a shop (rather than an enthusiast with one or two cars). Please let us know what vehicle(s) you are testing on and if you have the time make sure the HEX-USB+CAN works flawlessly with the same VCDS Beta release on the same PC.
    Last edited by Dana; 03-18-2014 at 03:14 PM.

  4. #14
    Verified VCDS User
    Join Date
    Feb 2014
    Posts
    82
    Post Thanks / Like
    Quote Originally Posted by Dana View Post
    Hello,

    This is something we are looking into and as Uwe mentioned the WiFi chipset may be the common factor. You aren't alone there with the Beta USB scan followed by -> Beta NET scan without a reboot - but I haven't been able to duplicate the issue with 100% consistency. I've used several PCs (ranging from XP to Windows 7) on a 2002 old-school Gti to my reasonably modern 2012 Tiguan and experienced that exact issue, but it worked properly a few times?!?

    In the meanwhile - you mentioned that VCDS Mobile connects right away. I had a 50/50% success rate with that immediately after experiencing the wired Beta scan -> AP mode issue. The next time you happen to try that can you confirm that when VCDS Beta cannot find the interface (Interface Not Found) -or- communicate properly that VCDS Mobile (via a web browser in AP mode | 192.168.0.1) works with consistency without rebooting the interface itself? I'm going to do the same on more than one car/PC and look into the Vign: 0.03V settings you mentioned as well. Likewise, I haven't tweaked any of my power settings in the HEX-NET either.

    -Dana
    Ok so should we expect this chipset issue to be addressed or should I look for another computer?

    Well it's fairly common place to have to "reset" the hexnet period by removing it from the car and from any possible USB cable that's become commonplace already I almost do that automatically, with that in mind yes VCDS mobile works just about always.

    I have never seen VCDS beta not finding the device not on usb not wifi unless I'm doing it too quickly,that's the thing it always finds it but that's it that's when the issues start.

    Just to clarify I've only used the hexnet on one of my own cars so far all the other cars have been others' cars that I've worked on.

    Right now on a 2002 Jetta where even with USB it was having issues finding the modules.

    P.S what I refer to as "old-school" would not have any OBD port whatsoever!

  5. #15
    Ross-Tech Employee
    Join Date
    Jan 2014
    Location
    Lansdale, PA
    Posts
    78
    Post Thanks / Like
    Quote Originally Posted by BaraJag View Post
    Ok so should we expect this chipset issue to be addressed or should I look for another computer?
    We can reproduce the issue and are trying to locate the cause. The current workaround is to use a usb network card on the same machine.

  6. #16
    Verified VCDS User
    Join Date
    Feb 2014
    Posts
    82
    Post Thanks / Like
    Quote Originally Posted by Santos View Post
    We can reproduce the issue and are trying to locate the cause.
    Any progress?

  7. #17
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,512
    Post Thanks / Like
    Blog Entries
    1
    Yes.. Stand by...

    [time passes]

    Please try Beta 14.2.3..

    -Uwe-
    Last edited by Uwe; 03-25-2014 at 02:16 PM.

  8. #18
    Verified VCDS User
    Join Date
    Feb 2014
    Posts
    2
    Post Thanks / Like
    Great work!! I have only tested the update on an 05 a3 and a 98 passat but everything is working perfectly so far. Thank you for all the hard work I appreciate it.

  9. Likes Uwe, Eric, Dana liked this post
  10. #19
    Verified VCDS User
    Join Date
    Feb 2014
    Posts
    82
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post
    Yes.. Stand by...

    [time passes]

    Please try Beta 14.2.3..

    -Uwe-
    Unfortunately when I now finally had time and tried it on the same vehicle (EV 99) as I did when I started this thread all I get is no response from controller, restarted VCDS a number of time, even restarted the computer after the BETA update, and the HEX-NET of course also wanted it's SW updated so I did that too.

    Same thing happened on my 2002 Eurovan so I don't believe it is the vehicle.

    It did communicate with my 1998 TDI ECU (it's not in the 98 body any more) but did not once display any numbers in the fields at the top, where you have VAG number etc etc, only way I knew it was connected was I the fault codes and measure blocks became available to click on.

    Also an odd thing on the 98 TDI is that when using the WIN8.1 tablet and Hex-Net in NET mode the TDI timing will NOT show it shows just fine in USB mode.

    P.S. The little I tested VCDS mobile it however seemed faster after the sw update!

  11. #20
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,512
    Post Thanks / Like
    Blog Entries
    1
    Were you running this via USB or WiFi, and if WiFi, AP mode or Infrastructure mode?

    -Uwe-

Posting Permissions

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