USB To Serial

[Franck_fr]

Hi, I’ve finally managed to buy an Airview2 . I’m surprise to see that you're using a USB To Serial driver / method to communicate with the device which from my point of view is and will seriously limit the performance and evolutivity of the solution. You are using the same chipset as WI-SPY but not the same hardware / software architecture which probably explains the lack of resolution and refresh time. Do you agree ?

Best Regards

[WHT]

will seriously limit the performance and evolutivity of the solutionAirView - $50
WiSpyÿ - $800

[that chris kid]

AirView - $50
WiSpyÿ - $800
My thoughts exactly

[Franck_fr]

Airview 50$
WiSpy 199$

And actually it is much more expensive than 50$ in Europe but that's not the problem because I have both now. It's an architecture decsion that again will have an impact on the solution evolutivity. I have no problem with it just a matter of setting expectations when I will suggest it one or other solution to my customers. So your answer is useless I just want to know if yes or no I'm rigth...

[rmichael]

I just got one Airview2EXT also and I think that perhaps $200 for wispy is not that much :D

Airview has a lot of potential but for right now wispy with Chanalyzer software wins hands down.

[WHT]

Since we run only 5.8 Gig, we needed the WiSpy, when UBNT has a 5.8 model, we'll go with that as its sufficient for a first pass look at the RF environment.

[Franck_fr]

I just got one Airview2EXT also and I think that perhaps $200 for wispy is not that much :D

Airview has a lot of potential but for right now wispy with Chanalyzer software wins hands down.

That's what I'm trying to find out if indeed it has a lot of potential...
just a matter of setting expectations

[UBNT-Ramin]

Hi, I’ve finally managed to buy an Airview2 . I’m surprise to see that you're using a USB To Serial driver / method to communicate with the device which from my point of view is and will seriously limit the performance and evolutivity of the solution. You are using the same chipset as WI-SPY but not the same hardware / software architecture which probably explains the lack of resolution and refresh time. Do you agree ?
Hi Franck,

I'm not sure what you mean by "seriously limit performance and evolutivity"? A serial interface to the device allows for a very easy and very fast interface to the device's data. The fact that the scan rate is around 3.7 FPS @ 500 KHz steps is because of the capabilities of the CC2511 chip, not having to do anything with serial speed limitations.

AirView UI application may not currently be as feature-rich as Chanalyzer, but for $39 you're able to get a very stable and useful application on 3 major operating systems; something the MetaGeek folks can't claim with Chanalyzer, even with the reduced $200 price.

It's unfortunate that we had to release the product without the capability for the user to configure the scan range, rate, and steps, and those features are being considered for inclusion in a later release, but I guarantee you that the performance of the app and device isn't hindered one bit by its serial interface.

[WHT]

One word...waterfall.

[UBNT-Ramin]

One word...waterfall.
LOL :lol: Yes sir, already heard that one loud and clear. I promise, it's definitely on our plate. :wink:

[cablemonkey]

Hi Ramin,

Is there any possibilty of getting AP information into the Airview display? This mght help you see if ther are multiple APs on a single channel in an area. Kismet/netstumbler-type functionality?

Another desireable feature would be logging, and logging as a function of position. Correlating the Airview readings with some GPS data would be super sweet. Heat maps, the whole bit.

Regards,

-Cam.

[UBNT-Ramin]

Is there any possibilty of getting AP information into the Airview display? This mght help you see if ther are multiple APs on a single channel in an area. Kismet/netstumbler-type functionality?

The apps that currently provide AP/SSID info with spectrum analysis data have to utilize a 2nd radio that's not included with their own USB device. For example, Chanalyzer uses the machine's own WiFi card (and .NET APIs) to get the AP info. So that info doesn't come from their own USB device, and if you ran it on a desktop that information is unavailable unless the desktop has an active wifi card. But nonetheless, it's a great feature and if we can figure out a way to provide it consistently on all 3 supported platforms, it'd be a great addition.

Another desireable feature would be logging, and logging as a function of position.

I think I know what you're talking about here but I don't want to assume anything so maybe you can elaborate on this. Are you talking about archiving of RF spectrum readings and tagging them with "where" they were recorded? GPS location?

Correlating the Airview readings with some GPS data would be super sweet. Heat maps, the whole bit.

If this relates to your previous comment, then yes, this would be an excellent feature addition, one that I'll definitely suggest to the management team for inclusion in a future version of AirView. A heat map would require an operator to walk around with an AirView-equipped laptop and take readings in various locations that are either GPS locatable (outdoor) or the application would have to provide ability to the user to designate their own position on a supplied map of their own.

In any case, we thank you for all these great suggestions and I've logged them in our wish list.

Cheers,

[cablemonkey]

Hi Ramin,

Yes, I think we're talking about the same things and that you've understood what I was asking.

Your comment about problems with GPS indoors is a valid one. I suppose you could start with a map of the facility and click on it to indicate location and log the received data at that point.

I was more thinking about tagging the logged RF information with GPS position for outdoor coverage suveys, etc., but both would be great.

Regards,

-Cam.