Updating HEX-NET version via "web interface"

While HEX-NET works fine when connected to the car, when connected in Infrastructure via the updater, it's asking to be updated via a "web interface" when using the updater v.1.963. There is no interface listed in the updater apart from the HEX-NET unit itself. Wondering what is meant by the "web interface?"

Log:

Checking for updates...
Update found!

Changelog:
CB: 0.4222
The update to CB V0.4201 must be done through the web interface.
The USB update process has changed behind the scenes,
V0.4201 supports functions for the new V2.001 update utility.

Hello John,

Been here? Ross-Tech has a walkthrough of the process:

http://forums.ross-tech.com/showthread.php?3757-How-to-update-HEX-NET-for-use-with-15-7

You should also register your interface so that you can post in the HEX-NET Beta Support forum:

http://forums.ross-tech.com/showthread.php?2601-How-to-get-Verified

Jason

I want to thank you again for the link to the thread about updating. I think it identified my problem, even if it didn't provide a solution. There appears to be an ongoing issue with the ability of Ross-Tech's server to perform multiple updates. I'm getting the same 'internal server error' message as some others, and evidently a fix is not yet forthcoming. Oh, well, at least I know it's nothing I've done or don't understand at this point.

Yeah, that interface is WAY behind the times and we suspect an issue with the dependency chain on the server. I'm it will get resolved next week.

-Uwe-

This morning I was successful in initiating the update process via my web browser (Chrome). After a number of update cycles (too numerous to list, it would probably be easier to list what wasn't updated than what was) I finally got a "You are up to date" message. When I get the time, I will hook up the HEX-NET to the car again and see if the full range of function in VCDS is now accessible.

The "About" button on the VCDS-Mobile menu yielded:

VCDS-Mobile
Codebase: Mar 11 2016 - 19:36:26

CodeBlock V0.4309
FW version: 0.238
Dataset: 10000039

LSN: 000100-00014E-525D30-930000-648603-6C848A-06
VSN: 0010D5-00EE04-011000-003900-180008-0100FF-FF0000-1F8E

VINs: 1/10
Faultcodes Cleared: 0

I had a little time, so I hooked up the updated HEX-NET to our car ('13 VW Passat TDI) and activated in infrastructure mode. As far as I can determine, it's able to access the "extended" functions that are not supported in the HEX-NET device itself. I was unable to determine any more (what I would like to do is run a procedure, activating the fuel pump for starters seems simple enough), but may be able to accomplish that later today. So far, so good.

I can now state that the HEX-NET is working, as I managed to do a complete procedure this morning. I successfully connected, selected 01 (Engine) —> 04 (Basic Settings) —> 035 (Test transfer pump, number not given, this was from a drop-down list of what are evidently regarded as common procedures). The pump activated (and was audible). Ran pump for about 30 seconds, stopped, and backed out of the HEX-NET menu system. (I can now change my fuel filter. Yay!)
The catch to using HEX-NET is to have a good wi-fi signal in the area, and at range (it's probably 100 feet from our detached garage to the router in the house) wi-fi can be notoriously fickle from day to day. Two days ago when I first tested the system, I had a full-strength signal. Today, it was marginal, causing everything to run slowly. In fact, I had to walk partway back to the house to get my tablet to connect to the network. Fortunately, the HEX-NET was able to access the network from within the car, sufficient to get the job done. I may dig out a spare router and configure it as a WAP for the garage, but this only points out how those HEX-NET users without a modicum of knowledge of wi-fi networks and Internet knowledge generally can find themselves at sea trying to accomplish this.

Ran an Auto-Scan, and decided that the next step is to try to extend better Internet coverage into the garage. I'll wait to post that until I become "verified," that way I can post my network machinations under the HEX-NET category.

Looks like you're Verified to me...

-Uwe-

PS: Moved to HEX-NET Beta support.