I just received an order of 8 VEXnet keys.
I used VEXnet MAC utility v 1.0.1 to try to collect their MACID, but all show “Not present”
Other older VEXnet keys are still recognized immediately.
I have run through the installation and reboot process twice, but still no luck.
The new VEXnet keys seem to sync between Cortex and Joystick, but not work with the VEXnet MAC utility on either of two computers, either win7 or xp.
I’m hosting Dallas BEST kickoff on Saturday at Hockaday HS, and I believe they have a Cisco ad-hoc network blocker, so it would be nice to be able to collect the MACID soon.
Update:
win7 cmd: getmac
shows C8-3A-35-CE-A3-D0 for one Vexnet key (didn’t bring others to try)
Previous MAC utility replies were always in 00 : B0 : 8C : E1 : (var) : (var) range?
Hypothesis that Vexnet MAC utility doesn’t expect values in vastly different ranges?
Thanks for bringing this matter into our attention.
One of our software partners just fixed the issue, we will post the upgraded version in the VEX website as soon as possible.
Thanks.
I tried to install it, but I get a popup:
“The VEXnet MAC Utility is still running. Please close the program before continuing.”
But this is after a restart on an XP machine, so it shouldn’t be running.
Process list doesn’t show anything that looks like “VEXnet MAC Utility”,
so I don’t know what I can kill to get this loaded.
I checked Uninstall programs, but I didn’t recognize anything relevant.
What do you suggest?
What is it looking for, to see “still running”?
Ok, sorry about the conflict you are seeing. We will make a change to the way the system works and we should post a new file tomorrow. Until then, a workaround for this is to just rename the folder after it is extracted (change the folder name to something besides the default “VEXnet MAC Utility”) or to move the Setup.exe file somewhere else on your computer and close the “VEXnet MAC Utility” window before running the it.
I tried that for a new install and it worked and installed correctly for me on a Win7 platform.
It even works after doing “remove programs” on the W54 tenda drivers.
Thanks,