How to update HEX-NETs with a codeblock older than 0.42xx

   #1  

Santos

Administrator
Staff member
Joined
Jan 29, 2014
Messages
236
Reaction score
2,768
Location
Lansdale, PA, USA
How to update HEX-NETs with a codeblock older than 0.42xx



What's needed (click on the link if you need more information):

PC or MAC
Java
HEX-NET Java Configuration Utility
HEX-NET
USB Cable




Step 1:

Plug HEX-NET into the USB Port of the computer. It does not have to be plugged into the car.

Step 2:

Open the HEX-NET config utility. If it does not open, you do not have java. Click here to download java

If you receive the following error, see step 2.5.



If you do not receive the error, click the check for updates button, and proceed to update using the utility (step 4).



Step 2.5 - The Error:

You will need to configure the HEX-NET to a local router with internet connectivity.

In the HEX-NET Utility do the following:
1. Click the OK button to dismiss the error.
2. Click Configure Wifi.
3. Click [Scan for new Network]
4. Select your Network
5. Enter Password.


Step 3- Update via browser:

The latest update pushed out for 15.7 was a major update. We need to update first via the web browser. In step 2.5 we configured the internet connection to the HEX-NET. Your HEX-NET Configuration utility will now show a valid ip address:




3A. Open a browser and enter the ip number. Login with your HEX-NET password (default password is password):





3B: Click [Options]:



3C: Click [Check for Updates].



You may receive the following warning message. Click OK, you can create a cloud account at a later time:




3D: Updates found. Go ahead and click the [Download Update button]




Once completed you will be redirected to the login screen. Close the browser at this time.


4. Go back to the update utility. Click [Check for Updates] button :
The utility will now display a list of updates found . Click [Download Update]



During the update, you will see the following. Click [OK] to proceed.




Once the update is completed click [Go Back]




IMPORTANT: Check for updates several times, as your HEX-NET may be very out of date. Keep following Step 4 until you see:







Your HEX-NET is up to date. You can now use the latest release of VCDS
 
Last edited:
   #2  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
We have done as advised on MAC and then PC.

What happens is that the IP address from the VCDS Config is not opening
in the browser. It just gives webpage is not available. Tried it on
Chrome and Safari both on PC/Mac

Am I doing something wrong?
 
   #3  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,935
Reaction score
21,378
Location
USA
VCDS Serial number
HC100001
What's the IP address of your PC or Mac?

What's the IP address of your HEX-NET at that point?

Can you ping the HEX-NET's IP address from your computer?

Is it possible that your router is configured in such a manner as to prevent devices on the WiFi from talking to each other, or that it has isolated VLANs?

-Uwe-
 
   #4  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
101.187.206.102 - My IP address
IP of hex net via Hex Net Config shows 192.168.0.1
When I ping:
Martins-MacBook-Pro:~ User$
Martins-MacBook-Pro:~ User$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
The router is Cisco router and it normally works with printers and other IP operated devices including phone system etc.
 
   #5  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
When I connect the hex net with wi-fi then it opens the IP address 192.168.0.1 but its not updating it - Update check timed out.
 
   #6  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,935
Reaction score
21,378
Location
USA
VCDS Serial number
HC100001
101.187.206.102 - My IP address
That's your external/ public IP address. What is your computer's IP address on your LAN?

IP of hex net via Hex Net Config shows 192.168.0.1
Then your HEX-NET is still in Access Point mode and is not connected to your WiFi LAN, and the rest of your results are not at all surprising.

-Uwe-
 
   #7  

Santos

Administrator
Staff member
Joined
Jan 29, 2014
Messages
236
Reaction score
2,768
Location
Lansdale, PA, USA
in terminal enter: ifconfig

It will give us a snapshot of your current network configuration. Post the results.
 
   #8  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
Martins-MacBook-Pro:~ User$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 10:dd:b1:e2:8d:db
inet6 fe80::12dd:b1ff:fee2:8ddb%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.146 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fd56:79bc:c05e:1:12dd:b1ff:fee2:8ddb prefixlen 64 autoconf
inet6 fd56:79bc:c05e:1:3828:5bda:1845:55d3 prefixlen 64 autoconf temporary
nd6 options=1<PERFORMNUD>
media: autoselect (1000baseT <full-duplex,flow-control,energy-efficient-ethernet>)
status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether f4:f9:51:e5:06:be
nd6 options=1<PERFORMNUD>
media: autoselect (<unknown type>)
status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:17:bd:b2:00
media: autoselect <full-duplex>
status: inactive
en3: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:17:bd:b2:01
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 06:f9:51:e5:06:be
media: autoselect
status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
ether f2:9b:f3:f7:49:3c
nd6 options=1<PERFORMNUD>
media: autoselect
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 12:dd:b1:2e:03:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
member: en3 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 7 priority 0 path cost 0
nd6 options=1<PERFORMNUD>
media: <unknown type>
status: inactive
Martins-MacBook-Pro:~ User$
 
   #9  

Shaun

Ross-Tech Employee
Joined
Jan 29, 2014
Messages
962
Reaction score
1,549
Location
USA
inet 192.168.1.146 netmask 0xffffff00 broadcast 192.168.1.255
It looks like your main network is on the .1 subnet, but the hex-net is showing .0
This makes me think that your hex-net is in AP mode. In order to be able to contact our servers to update, the hex-net must be connected to your wifi router with internet access, this will not work with the hex-net in AP mode.

If you aren't sure how to setup your hex-net for infrastructure mode, in the config utility go to "Configure Wifi" -> "Scan for New Network" select your wifi there and enter the password when it asks you. When the hex-net is successfully connect in infrastructure mode, then the middle led should be green and it will probably have an ip address in the 192.168.1.* range. This is the ip address you need to open in a browser to perform the update.

--Shaun
 
  • Like
Reactions: Uwe
   #10  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
Thanks, this worked but:
The page at 192.168.1.119 says:
This interface is not registered with VCDS-Cloud.
Please connect to a vehicle, start a session with a controller,
and go to Cloud Functions to complete the registration process.
 
   #11  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
ok, I select the module and go to Functions -> i cloud functions and then register. I am getting a little circle but its not getting me into registration mode...
 
   #12  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
ok resolved now, worked on MacBook, Yupi I can finally get scanning and get all these nice cars onto Ross Tech database ;)
Fully awesome!
 
  • Like
Reactions: Uwe
   #13  

Santos

Administrator
Staff member
Joined
Jan 29, 2014
Messages
236
Reaction score
2,768
Location
Lansdale, PA, USA
ok, I select the module and go to Functions -> i cloud functions and then register. I am getting a little circle but its not getting me into registration mode...
That happens with the VCDS-Mobile viewer app on IOS. Use safari instead.
 
   #14  

liquidforce

Verified VCDS User
Verified
Joined
Oct 10, 2014
Messages
12
Reaction score
4
Location
Australia
VCDS Serial number
C?ID=175302
That happens with the VCDS-Mobile viewer app on IOS. Use safari instead.
This was Chrome,

All working like a dream now, really happy, thank you for your help guys!

Would be great if the database could be shared :)
 
   #15  

wwnext23

Verified VCDS User
Verified
Joined
Oct 31, 2015
Messages
4
Reaction score
0
Location
USA
VCDS Serial number
C?ID=239103
I am having the same issue as the initial poster. When I try to update my hex net after the configure it, it also times out. When I configure the Hex-net, the IP address i get is 192.168.0.5, but the IP address of my computer is 192.168.0.1. I have tried to re-configure the hex-net wifi connection multiple times, but can't get it to match my computer's IP which appears to be why the update times out. Any guidance on how to correct this?
 
   #16  

Zenerdiode

Verified VCDS User
Verified
Joined
Jun 26, 2014
Messages
1,007
Reaction score
1,559
Location
Newcastle, England
VCDS Serial number
C?ID=24330
...but can't get it to match my computer's IP which appears to be why the update times out. Any guidance on how to correct this?
It shouldn't match your computer's IP. All devices on the same subnet need to have different IPs. You need to have the HEX-NET in infrastructure mode connected to your wifi router. It effectively is a little computer just like your laptop. This also gives it access to the outside wold and therefore the Ross-Tech servers. You then connect to the HEX-NET via your computer to search for updates. It then contacts the RT servers and downloads the updates.

You may also connect the HEX-NET to a computer that has internet access via the USB cable and run the Java utility to update.
 
   #17  

wwnext23

Verified VCDS User
Verified
Joined
Oct 31, 2015
Messages
4
Reaction score
0
Location
USA
VCDS Serial number
C?ID=239103
Okay, so if the IP address isn't the issue, do you know why when I try to update the software it times out? I have the hex-net plugged into my computer using the USB. I configure the wifi and generate the IP address in Infrastructure mode. Then I put the IP address in my browser and and log in, and check for updates, but it keeps timing out on me and I can't get any further.
 
   #18  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,935
Reaction score
21,378
Location
USA
VCDS Serial number
HC100001
Please do:

[Options] -> [Self Test] -> [Advanced Network Test]

And let us know the results.

-Uwe-
 
   #19  

wwnext23

Verified VCDS User
Verified
Joined
Oct 31, 2015
Messages
4
Reaction score
0
Location
USA
VCDS Serial number
C?ID=239103
It won't finish the test. The Status reads "Pinging Server" and there are blue bars the light up in succession, but nothing more happens. I have tried this twice now and just let it run for over 20 minutes each time (the 2nd was probably closer to an hour) and it never gets past "pinging server."
 
   #20  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,935
Reaction score
21,378
Location
USA
VCDS Serial number
HC100001
Well, if it can't talk to the server, it's hardly a surprise that it can't download an upgrade, right? ;)

So now the question is, what's keeping it from being able to talk to the server?

-Uwe-
 
Top