RE: how to lock 1 antenna conn to RX and 2nd antenna conn to TX


From: Trevor Man (tman_at_laser.com)
Date: 2002-09-12 00:18:58 UTC



I thought the point in having a separate RX and TX antenna was so that you have a very high gain one for the RX one whilst having a normal one for the TX. This way you could get maximum receive signal whilst still staying within the legal transmit power limits.

-----Original Message-----
From: Jeff Meden [mailto:blade_at_ncweb.com] Sent: 12 September 2002 01:06
To: hostap
Subject: Re: how to lock 1 antenna conn to RX and 2nd antenna conn to TX

This is OT to hostap but... you don't *really* want one antenna RX and one antenna TX do you? 802.11b is half duplex, that is it never talks and listens at the same time... because it would hear itself no matter what. In addition, the point of diversity antennas is to reduce multipath distortion, with the principle that two antennas a distance apart will together have complete signal coverage considering multipath distortion from any point. Just my $0.02

Jeff Meden
QuickNet, Inc. Columbus

Jim Thompson wrote:

> OK, color me shocked.
>
> On Wednesday, September 11, 2002, at 10:10 AM, Michael Codanti wrote:
> >> Interesting.. From the testing that Jerritt reported on with the Senao >> cards, he was able to switch diversity to either of the 2 antenna >> connectors. >> >> Michael >> >> ----- Original Message ----- >> From: "Jim Thompson" <jim_at_netgate.com> >> To: "Michael Codanti" <michael_at_civis.com> >> Cc: <hostap_at_lists.ssh.com> >> Sent: Wednesday, September 11, 2002 7:48 AM >> Subject: Re: how to lock 1 antenna conn to RX and 2nd antenna conn to TX >> >> >>> because no prism2.5 design that I know of has a diversity switch that >>> you can

control from software.  >>>  >>> You *can* disable diversity, (and just
run one antenna).  >>>  >>> On Tuesday, September 10, 2002, at 07:09 PM,
Michael Codanti wrote:  >>>  >>>> Why do you say no? From what I can
tell it is possible just not >>>> supported >>>> in the driver yet. >>> >> >> > >

This archive was generated by hypermail 2.1.4.