X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=KCLfnIDfzDaJ94/HXfIe+qF9T+JUQ4ifqHONZO6wl2Y=;
        b=uhIUuQDU3O3GIylaZpirzlUHpG0PnNwSubn53Pz0r01Wc1shbB3S/Bc4cUF/XqD2MS
         GCIqxkwx9Bupogz7wrT/YnJizUmlDbLukDYSl9y56StJ+eWJx7Tx/eMOL9xMbL9QOZWt
         V8byIb5vid1Kl0J2tfMDonMoo5zBiuVNemqP3CdRHbl5CkQjtkpkhYj21mLKEcYpchVO
         pzfcJxJLj5yxI7XYwrG9vXEpdoT3VTzSyMVW9zLtWzY1Ajx83NPnvdX9FDd3/oVXG3Q4
         sBzf46I0GEPRvBN2E/VHddjqvu6IR1BvknGPvojyoo7OjNcQAYUEQFxqBhaaBK+taAVi
         eOGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=KCLfnIDfzDaJ94/HXfIe+qF9T+JUQ4ifqHONZO6wl2Y=;
        b=S2JG2VvepIvFsdtx2h9MQh1WGhGd5iR26DymH8AERG3jVjt7KDBlCSFaqAiGCKKhzB
         tFkUs7IBy9lgLGmqb6XetoZgOqmPmWFkgfeGG2x71BNxhD9fZQKSdJgCbMXEvXm8ecdO
         CFGwOnCR/Dxe5k5KLv0CQbdWYXW0ddS7fI0rR/vQEL+YURCQcBfTSH0GAWOesdJwUak2
         L1H/CcHhxiU45bDFSEfOC3PdgeQylQGzUoZjxX6ZHyvERrbbRHA5RTHwtzD5uMr6bJ5u
         sga4KA8swmBePI5fQdHaQDvAbD341zNZbqcefgxwSQ1XZW/WYtiJOqRNDUKv+Yngmfng
         lA4Q==
X-Gm-Message-State: AIkVDXKMnwPCIE7xpdbrRC5YNYm09o5Av9/9cM5YHBL8lFqB8d84YvvlgmjmOJp9J97dX6/q7RRDIufiK09O1g==
X-Received: by 10.200.55.178 with SMTP id d47mr14780848qtc.60.1485640278003;
 Sat, 28 Jan 2017 13:51:18 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <20170128205338.826E381075C7@turkos.aspodata.se>
References: <1485607260 DOT 3072 DOT 77 DOT camel AT linetec> <20170128205338 DOT 826E381075C7 AT turkos DOT aspodata DOT se>
From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Sat, 28 Jan 2017 21:51:17 +0000
Message-ID: <CAJXU7q8EjAnNcrcT6uda9NX0u2Uvst=JBLUbgNg8wpYuk_0ipg@mail.gmail.com>
Subject: Re: [geda-user] PCB antenna question
To: gEDA User Mailing List <geda-user AT delorie DOT com>
Content-Type: multipart/alternative; boundary=001a1140dece08d87d05472e955a
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

--001a1140dece08d87d05472e955a
Content-Type: text/plain; charset=UTF-8

On 28 Jan 2017 21:06, <karl AT aspodata DOT se> wrote:

Richard Rasker:
> Lately, I started on projects involving Bluetooth and UHF RF, and for
> simplicity and cost, I'd like to use PCB antennas.
>
> While doing this, I ran into a question: how can I 'properly' define PCB
> antenna elements/footprints?
...

You can not, but one of theese might help:
 http://repo.hu/projects/pcb-rnd/features/nonetlist.html
 http://repo.hu/projects/pcb-rnd/features/intconn.html


Neat.

I'd probably not use intconn myself (without back annotation to the
schematic, it would be confusing) - but it is nice to have a way to capture
a simple circuit model of a component on the board.

DJ and I were discussing ideas about supporting netlists between
connectors. Doing so could enable following a circuit between two (or more)
ribbon headers on a board. Still potentially has back annotation issues,
plus it isn't clear where you would attach that information in the design -
but it's an interesting concept.

Peter

--001a1140dece08d87d05472e955a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On 28 Jan 2017 21:06,  &lt;<a href=3D"mailto:karl AT aspodata DOT se">karl AT a=
spodata.se</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Richard Rasker:<br>
<div class=3D"quoted-text">&gt; Lately, I started on projects involving Blu=
etooth and UHF RF, and for<br>
&gt; simplicity and cost, I&#39;d like to use PCB antennas.<br>
&gt;<br>
&gt; While doing this, I ran into a question: how can I &#39;properly&#39; =
define PCB<br>
&gt; antenna elements/footprints?<br>
</div>...<br>
<br>
You can not, but one of theese might help:<br>
=C2=A0<a href=3D"http://repo.hu/projects/pcb-rnd/features/nonetlist.html" r=
el=3D"noreferrer" target=3D"_blank">http://repo.hu/projects/pcb-<wbr>rnd/fe=
atures/nonetlist.html</a><br>
=C2=A0<a href=3D"http://repo.hu/projects/pcb-rnd/features/intconn.html" rel=
=3D"noreferrer" target=3D"_blank">http://repo.hu/projects/pcb-<wbr>rnd/feat=
ures/intconn.html</a></blockquote></div></div></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">Neat.</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">I&#39;d probably not use intconn myself (without back annotation to th=
e schematic, it would be confusing) - but it is nice to have a way to captu=
re a simple circuit model of a component on the board.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">DJ and I were discussing ideas about support=
ing netlists between connectors. Doing so could enable following a circuit =
between two (or more) ribbon headers on a board. Still potentially has back=
 annotation issues, plus it isn&#39;t clear where you would attach that inf=
ormation in the design - but it&#39;s an interesting concept.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Peter</div></div>

--001a1140dece08d87d05472e955a--