HEX-NET Troubleshooting Steps

[Andy]

If you encounter difficulty connecting to a car, this can be a general list of things to try:

1) Windows PC using VCDS to connect a HEX-USB+CAN over USB to the car.

2) Windows PC using VCDS to connect a HEX-NET over USB to the car.

3) Windows PC using VCDS to connect a HEX-NET over NET to the car in Infrastructure Mode

4) Windows PC using VCDS to connect a HEX-NET over NET to the car in Access Point Mode

5) Windows PC using VCDS-Mobile to connect a HEX-NET over NET to the car in Infrastructure Mode

6) Windows PC using VCDS-Mobile to connect a HEX-NET over NET to the car in Access Point Mode

7) Other Device using VCDS-Mobile to connect a HEX-NET over NET to the car in Infrastructure Mode

8) Other Device using VCDS-Mobile to connect a HEX-NET over NET to the car in Access Point Mode

 

[Andy]

I'm adding these as we come across them:

Q: Why isn't my password for VCDS-Mobile working?

A: The default password is printed on the instructions that come with your HEX-NET. Make sure it is all lower case and that your device isn't automatically capitalizing the first letter. While the HEX-NET is connected to the car (or USB power) you can hold the red button for 20 seconds. Upon releasing it, you should hear a beep and the password should be reset to the default one, in case it was changed.

 

[Andy]

I just did a quick test of sample rates with a single measuring block on a CAN-Bus ECU on my test stand in samples per second:

VCDS-HN-AP-turbo 12.16
VCDS-HN-AP-nonturbo 6.74
VCDS-HN-IF-turbo 11.96
VCDS-HN-IF-nonturbo 6.41
VCDS-HN-USB-turbo 12.03
VCDS-HN-USB-nonturbo 6.05
VCDS-HUC-turbo 12.28
VCDS-HUC-nonturbo 6.65

 

[PanEuropean]

...While the HEX-NET is connected to the car (or USB power) you can hold the red button for 20 seconds. Upon releasing it, you should hear a beep and the password should be reset to the default one, in case it was changed.

Hello Andy:

That suggests (to me, anyway) that the password is stored within the actual HEX-NET device. If that is the case, then it begs the question "Why would most users even want to have a password?" I honestly can't see any benefit to me (the user) arising from having a password. The password just adds an extra layer of complexity to using the device, especially during the first few days when the new user is coping with getting the thing connected to various Wi-Fi networks, updating firmware, registering for use on VCDS Mobile, etc.

If the rationale behind the password has anything to do with protection against theft of the device (or theft of VCDS-Mobile service, if the device itself is lost or stolen), I think a much simpler way of dealing with that would be to simply blacklist the serial number of the device. In other words, if an owner loses a device or if a device has been stolen, the owner advises Ross-Tech, and Ross-Tech enters the serial number of the device onto a blacklist. The next time the device attempts to connect to VCDS-Mobile, or to download a firmware update, you can send a command to it instructing it to blow up like a Syrian barrel bomb and destroy everything within a 30 foot radius. Or, if you are concerned about any possible liability arising from that strategy, you could simply disable the device so that it would never be able to work again (this via a firmware update), and/or disqualify that serial number device from logging into VCDS-Mobile.

Failing all of that, would you consider giving users an option to completely disable the password (do away with that whole layer of security) if the users wish to do so?

Michael

 

[jakematic]

If that is the case, then it begs the question "Why would most users even want to have a password?l

Michael-

Apologies for my out of turn answer, but please see this thread.
It'a a realistic scenario.

Firmware updates.... yes we've seen our fair share of that not happening sadly.

-Jake

Edit: Any reason not to use the remember me tick box ?
As an aside for me doing that is akin to setting a child on fire..... I like multi-level 'security'

 

[Uwe]

That suggests (to me, anyway) that the password is stored within the actual HEX-NET device.

Or at least a hash thereof.

If that is the case, then it begs the question "Why would most users even want to have a password?"

I envision plenty of people leaving HEX-NETs in their cars on a semi-permanent basis. When the HEX-NET is in AP mode it's an OPEN WiFi -- no security -- and any passerby can see it and connect to it. Even if it's on an infrastructure network, anyone who can connect to your network can connect to your HEX-NET and start poking around in your car. I don't think that's particularly desirable.

Failing all of that, would you consider giving users an option to completely disable the password (do away with that whole layer of security) if the users wish to do so?

Why? I enter my password once and check "Remember me"; after that I'm good to go with that browser on that device.

-Uwe-

 

[PanEuropean]

Thanks Uwe, you did a good job of explaining the concepts and rationale behind the password. Now I understand why a password is used.

Michael

 

[dc240969]

are the passwords different per user? l seem to have discarded the instructions that came with it. havent used the unit except via cable and now want to use it mobile.

 

[Boki Ar]

Default password is just: password

 

[dc240969]

thanks