I purchased an upgrade from my HEX-CAN usb to HEX-NET WiFi figuring that eventually I'll need it and the thought of being able to use my Android tablet to go read codes w/ Mobile was appealing. It read fine, but I got some unknown codes (RODs missing) and since the tablet does not have a SIM (i.e. not a phone) and the WiFi was in Access Point since my car doesn't fit inside the house to get a signal from my house WiFi (something about a concrete house with rebar every 6" & Faraday cage). Not a problem thought I, putting the HEX-NET into infrastructure mode and attaching it to one of my 4 functional PC's in the house via USB to power it. Connected fine, PC recognized the USB device, loaded drivers, and in v19.6.2: Hit test:
Found
type Hex-Net
ver : 0.4508.4
0.256
WiFi: 310C
Status: Questionable
CAN Testing, K1: no power etc
Hit SAVE
In Options: Config - in User interface, it shows my info. Great. .... Then - oops
In Options: Config - in Port and protocol options: USB, click Config get blank Config v2.248 screen w/ text at bottom: "Unable to open interface, it may be in use by another program. " When hitting Refresh interface, nothing comes up.
The select interface dropdown is blank, I can't scan for wifi (not surprising), etc.
My wife's car is throwing code 019226 and the HEX-NET said it was an unknown fault code.
Try as I might, disabling firewall, uninstalling Norton 360 did nothing. However, I booted an old PC that had Win-10 Pro 32bit build 1607, and the HN1-022757 came up in the Interface via USB, and I updated the RODs and it's now at 0.4513.4 after update & it's the that is throwing the code. Figuring that I might as well patch the PC, I let it go overnight to build 1903. Still worked. However, pushing build 1909 onto it, broke it, and I'm now back to the blank Config v2.248 screen w/ text at bottom: "Unable to open interface, it may be in use by another program. "
I have a Win 7 Pro - 32bit set of backup disks for the same PC. Swapping them, ignoring the Activation notice, works fine and the HN1-022757 came up in the Interface via USB.
Ergo - Win10-64bit or 32bit build 1909 breaks the -config HEX-NET interface detection. Not sure how / what but I have another reason yet to hate Microsoft's direction. If you have any other ideas to figure out how to get 1909 to work, I'm all ears though I'm set to work for a couple of weeks in MO before heading off to work in Germany for a few weeks so time will be short.