On Thu, 2 Feb 2012 00:43:42 +0000 (UTC), Chuck Banshee
<
chuckb...@private.com> wrote:
>On Wed, 01 Feb 2012 07:55:33 -0800, Jeff Liebermann wrote:
>
>You're going to be sorry you asked. :)
Nope. I'm already sorry that I asked. No need to wait.
>What I'm trying to understand is much more than just the Lenovo X61t
>native antenna dBi so that's why I was hoping to just ask about that
>small missing piece of the puzzle in this post.
It's still backwards. Questions like yours (and answers like mine)
make little sense without the proper context.
>The bigger picture is I'm trying to figure out what real-world equipment
>I need to communicate with various access points that my outdoor radio
>+antenna sees (but it can't connect to them all) - and that my laptop
>radio+antenna does not see (but I hope to see with a USB WiFi extender).
Ok, but first a short lecture. If you understand how things work, you
can usually work out the details of how to make things work for your
specific application. I like to supply theory and rules-of-thumb,
rather than suggest you go out and buy some specific device.
In this case, the reason you can see more AP's than you can connect to
is because it takes exactly one packet for the computah to announce
that it can hear an AP. It takes far more packets, going in both
directions, to associate with an AP, negotiate an encryption key,
obtain a DHCP assigned IP address, and setup a route to the internet.
Hearing one packet requires just luck. Making a connection, requires
a good signal.
For Wi-Fi, the signal has two specifications. Signal level and signal
quality, also known as SNR (signal to noise ratio). You could have a
situation, where the signal level is adequate, but because of
interference from other stations on the same channel, the signal
quality sucks. This might be why you can't connect to the distant
stations. You may be experiencing interference at either or both
ends. A clue is to sniff the management packets going in both
directions. The connection speed does *NOT* need to be the same in
both directions. If there's a large difference in connection speed,
in both directions, the end receiving the slow speed, probably has an
interference problem.
So, now that you understand what it takes to get a decent connection,
how is it calculated. Welcome to link calculations:
<
http://wireless.navas.us/index.php?title=Wi-Fi#Link_Calculations>
Plug in the numbers for the remote AP with which you want to
communicate, assume a 20dB minimum fade margin, and see how close you
get. If you have problems, post the numbers, and I'll use them as an
example.
The basic idea is to have a sufficiently good SNR to insure reliable
communications. So, what's reliable? See the SOM to % reliability to
downtime table in the above URL. For a 20dB SOM (same as fade
margin), you'll get 99% reliability, which will produce about 88 hrs
per year of outage. If you can live with 15 minutes per day outage,
you're done. If not, you'll need to add more gain somewhere in the
system. Usually, the antennas are the easiest.
Enough on Wi-Fi calculations for now.
>In addition, I'd like to add a TV antenna to the top of my WISP antenna,
Bad idea. If they're too close, they'll affect each others antenna
pattern. Keep them apart. I don't want to get into TV antennas in a
wireless newsgroup.
>I'm amazed that the dBi spec for the antenna on the Lenovo X61t is so
>hard to find!
That's because there is no single number that clearly describes the
antennas. You could specify maximum gain, average gain, gain range,
directivity, bandwidth for VSWR<2:1, and other important info. None
of these are particularly useful because the mounting method and
location has a HUGE effect on the gain and pattern. The antenna may
look reasonable in free space, but crammed into a laptop, the pattern
is probably an embarrassment.