jks19714
08-17-2009, 01:57 PM
I have two modules (a 900 MHz and a 2.4 GHz) plugged into a PC over a common USB port. WindowsXP detected both of them and the installation worked OK -- the AirView9 is COM3 and the AirView2 is COM4.
When I start AirView, it sees the 900 MHz unit on COM3 and fires up just fine. I would like to run a second instance of AirView to utilize the COM4 unit -- can you tell me how to set the COM port within the application?
I'll put some pictures up once I get it running properly -- I've mounted them with a generic USB hub in a WrapBox with USB-over-Cat5 gizmos as a remote spectrum monitor in a mobile application. Pretty cool if I can just get two of them to run at once!
73s,
john W3JKS
UBNT-Ramin
08-25-2009, 01:19 PM
I have two modules (a 900 MHz and a 2.4 GHz) plugged into a PC over a common USB port. WindowsXP detected both of them and the installation worked OK -- the AirView9 is COM3 and the AirView2 is COM4.
Hmmm... a "common USB port"? Do you mean a hub? Did Windows detect and list both AirView devices in Device Manager under "Ports (COM & LPT)"?
The real test of whether or not they've been properly registered under Windows is to check the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbser\Enum
If under this key you see 2 separate "REG_SZ" entries named "0" and "1" with their "Data" field that starts with "USB\Vid_....", then you know Windows has properly registered both devices. Otherwise your configuration isn't supported.
When I start AirView, it sees the 900 MHz unit on COM3 and fires up just fine. I would like to run a second instance of AirView to utilize the COM4 unit -- can you tell me how to set the COM port within the application?
The AirView application was designed to have multiple instances running on the same machine with no issues. Each instance that starts up looks for a single UNUSED AirView device plugged into its own USB port. It doesn't care if those USB ports are provided/extended by a USB hub, but it must be a true, individual USB port of its own registered with Device Manager.
Because of this the application doesn't worry about setting COM ports and what-not. As long as the devices appear as individual devices on the USB bus (even via a hub), it's able to locate them and connect to them.
If you have a setup where somehow 2 devices are plugged into something other than a real USB hub, then I'm afraid that's not a supported hardware configuration. But I'm not sure if I got that right. You might want to elaborate.
