From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Julian Calaby <julian.calaby@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Any thoughts on how to best shield u.fl connectors on NICs?
Date: Tue, 30 Oct 2012 22:28:49 -0700 [thread overview]
Message-ID: <5090B711.70808@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmoky+46E71wQbF1-J-xEnHdWeMMXf=Yo+SGkqALjvjrJrg@mail.gmail.com>
On 10/30/2012 10:16 PM, Adrian Chadd wrote:
> On 30 October 2012 16:45, Julian Calaby <julian.calaby@gmail.com> wrote:
>
>> That's a good point, all the NICs I've looked at closely (e.g. the
>> rt2500usb cards on my desk at the moment) have an antenna or u.fl
>> connector with some passive components around it and usually the
>> antenna trace runs exposed on the board for a couple of millimetres
>> before it disappears under the shielding around the RF chip. I'll
>> check my collection at home tonight, but I'm pretty sure that all the
>> PCI cards have a couple of cm of exposed antenna trace between the SMA
>> connector and the RF shield.
>
> I've even seen ${COMMERCIAL} kit do this internally.
From what I can tell, the WPEA-127n has a 1cm or so unshielded
run from the u.fl mounts to the RF chip logic. I'm guessing this
acts as a mini-antenna, and maybe it was done that way on purpose,
but it's all guessing at this point.
>
> Ben, what are you worried about in particular?
Two things come to mind:
First, I'd like to put 2+ NICs close together in the same chassis.
Would be nice if they were as isolated from each other as possible
so that each NIC could work independently of the other (once I can
get to SMA connectors, there are > 90db shielded cable options,
but of course it could just go to antenna where it all mixes again
anyway).
Second: If one wants to use an attenuator and coax cables to connect
AP and Station systems together, the AP and Station need to NOT also
be transmitting through the air. Anything I can do to keep that
over-the-air communication minimal should help.
Truth is, I'm not sure how much it really matters, but after a few weeks
of poking at cabling and such, I've gotten kind of curious :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-10-31 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 17:06 Any thoughts on how to best shield u.fl connectors on NICs? Ben Greear
2012-10-30 19:14 ` Don deJuan
2012-10-30 22:22 ` Julian Calaby
2012-10-30 22:34 ` Ben Greear
2012-10-30 23:45 ` Julian Calaby
2012-10-31 5:16 ` Adrian Chadd
2012-10-31 5:28 ` Ben Greear [this message]
2012-10-31 6:21 ` Julian Calaby
2012-10-31 18:05 ` Adrian Chadd
2012-11-04 11:10 ` Nick Kossifidis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5090B711.70808@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).