linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "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 15:34:53 -0700	[thread overview]
Message-ID: <5090560D.1090708@candelatech.com> (raw)
In-Reply-To: <CAGRGNgWGfL+_u4fHEfqZAcFHb1H4Z4jFkiE4qKLU6i9XEWzZ6w@mail.gmail.com>

On 10/30/2012 03:22 PM, Julian Calaby wrote:
> Hi Ben,
>
> On Tue, Oct 30, 2012 at 4:06 AM, Ben Greear <greearb@candelatech.com> wrote:
>> It appears hard to get well-shielded u.fl (IPEX) to SMA pigtails, and all of
>> the
>> modern ath9k NICs I've seen use u.fl connectors on the NIC.
>>
>> I have found a vendor that will do double-shielded 1.32mm cable, and I have
>> some of those
>> on order, but the way u.fl connectors are made it seems there is always a
>> bit of un-shielded
>> cable where the connector is crimped onto the cable.
>>
>> I am curious if anyone has any suggestions or experience with connecting
>> u.fl NICs to
>> SMA cables in a highly shielded manner...
>
> I have an awful feeling that it's simply not going to happen - I would
> guess from what you've described that the u.fl connector is designed
> to be cheap, small and easy and not really designed for "real" work
> like what you're doing with it. I'm guessing that the signal leakage
> through the connector is probably not a problem for the manufacturers
> as they're always shielded inside a computer case - i.e. it complies
> with the FCC rules.

I think it must be able to leak quite a bit before the FCC cares...  Standard
single-shielded pigtails are quite noisy, nevermind the connectors...

But anyway...I was thinking something like this (but with different
gender u.fl side) and some sort of physical attachment option to keep
it on the NIC might be interesting:

http://www.pimfg.com/Product-Detail/000-SMA-UFL

For all I know, the NIC itself may leak worse than the u.fl pigtail connector,
however...

Thanks,
Ben

>
> Thanks,
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2012-10-30 22:34 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 [this message]
2012-10-30 23:45     ` Julian Calaby
2012-10-31  5:16       ` Adrian Chadd
2012-10-31  5:28         ` Ben Greear
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=5090560D.1090708@candelatech.com \
    --to=greearb@candelatech.com \
    --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).