Bug - High COM ports

[rhodger]

I use a netbook for on-site work, and due to the number of devices I have to be able to talk to I have quite a number of serial ports (both real and software) on it.

When I initially connected the Airview2 dongle, it configured itself as COM7. However, the software was unable to find the Airview2 and would not work. After I reconfigured the Airview2 down to COM1, the software now works.

It would be useful if the software could have an option to manually set the Airview2's COM port instead of only auto-searching a limited range.

[UBNT-Mike.Ford]

Hello,

I forwarded this to the AirView team.

Thanks,

Mike

[UBNT-Ramin]

I use a netbook for on-site work, and due to the number of devices I have to be able to talk to I have quite a number of serial ports (both real and software) on it.

When I initially connected the Airview2 dongle, it configured itself as COM7. However, the software was unable to find the Airview2 and would not work. After I reconfigured the Airview2 down to COM1, the software now works.

It would be useful if the software could have an option to manually set the Airview2's COM port instead of only auto-searching a limited range.

What O/S? Windows? What version? SP? Please post exact O/S details.

I used WinXP SP3 to develop AirView and the installation packages were tested on latest SP releases of Vista (both 32 & 64 bit). In our testing AirView was associated with COM ports as high as COM23 and COM24 and in all cases the app was able to open and communicate with it.

In your case, when it was auto configured as COM7, did you check Device Manager to see if a little Yellow warning sign was next to the AirView device record? Any sign that Windows didn't successfully identify and/or load the device and its usbser.sys driver? That's usually where the issue(s) are.

Please provide more info so we can help you out.

Thanks,

[rhodger]

I use a netbook for on-site work, and due to the number of devices I have to be able to talk to I have quite a number of serial ports (both real and software) on it.

When I initially connected the Airview2 dongle, it configured itself as COM7. However, the software was unable to find the Airview2 and would not work. After I reconfigured the Airview2 down to COM1, the software now works.

It would be useful if the software could have an option to manually set the Airview2's COM port instead of only auto-searching a limited range.

What O/S? Windows? What version? SP? Please post exact O/S details.

I used WinXP SP3 to develop AirView and the installation packages were tested on latest SP releases of Vista (both 32 & 64 bit). In our testing AirView was associated with COM ports as high as COM23 and COM24 and in all cases the app was able to open and communicate with it.

In your case, when it was auto configured as COM7, did you check Device Manager to see if a little Yellow warning sign was next to the AirView device record? Any sign that Windows didn't successfully identify and/or load the device and its usbser.sys driver? That's usually where the issue(s) are.

Please provide more info so we can help you out.

Thanks,

Windows Vista Ultimate 32bit, SP1. I did not see any errors associated with the Airview device. Ths spectrum analyzer would search and then announce it could not find the device. After doing this several times I changed it to COM1, and it found it straight away.

Next time I've got it open, I'll change it back to COM7 and see what happens.