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=HUvRf1lhV77MDZjCQG+eJIeXfmowlA2vZN44zDxp/kI=;
        b=ABSmNZTuPgy5OYu3vbc88L92oj/85ahwQuldNGfSTVVqHPM1qAiFkIvMJ7EXT2ILky
         KYZxTbqN8Byzd8K/xhiRPAHZmzgO8fK7bzGMwoX+QNevkN7ctGl7mIaw9xqvMPl1vShm
         Y63rHrntwP12NsoZOIH/8HHtJXSLilzBlIr4CTFuvETwLCnMst8RQDsVWZHappz5CUk6
         aRdQYMQXmyn+AFPY8x6I2U4QeCMh7BggdYDG1P9tuWsFnMj/Y16nZ9CwclTx5V9T/pya
         5FtMautt9WO8T/ySEAfFt8QFs9hNlcgQxhe2gBN3vt9I64pigxRp13noY+b3PVuAQrsl
         Fofg==
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=HUvRf1lhV77MDZjCQG+eJIeXfmowlA2vZN44zDxp/kI=;
        b=I6Z2vw+OoeKOjeOIcUSPifgjQ38hBoQUcwV4Q7udGEc8/hdW0w8GUHnVGp6VTeLlnC
         zwTtGacr0z+wncEC48Ff2zaoFODEUMoIkL2ogP3+MzHWtu6VDwCwrw09BlOcnTAiXjuF
         AmMhyaFFgW8hY3JIaS7o690IdUMiCvSzPGaD7yAcjTyZLauCedw1ZRRGtNg7levJfzux
         3zvRf4GXDPt81sq5+KckQAnLrt+XXXlIJyELZsq2JkbQJly9RuaiYYftQmd4I33BF2wg
         YYSis8+3bbFDP8tng7pYaBmHsflJsp/g8oacw/UJGK3VB+hJFn099B1xO7LsNYR8/fnh
         vrrA==
X-Gm-Message-State: AIkVDXLqO1jStqj4/QTGqCZ2gQ0xfoZAlUkk2j2u/M4pzEdafFb74Yki0bvW0gex/JrNqRqtBK7mvSTq/dMjng==
X-Received: by 10.55.104.136 with SMTP id d130mr2786937qkc.9.1485622692230;
 Sat, 28 Jan 2017 08:58:12 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <1485607260.3072.77.camel@linetec>
References: <1485607260 DOT 3072 DOT 77 DOT camel AT linetec>
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 16:58:11 +0000
Message-ID: <CAJXU7q8k4synABy2rOSbjmcarmZ_TONwKxG7ED9f4mP6jAiwJw@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=94eb2c05612ad73a3405472a7ccd
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

--94eb2c05612ad73a3405472a7ccd
Content-Type: text/plain; charset=UTF-8

I'm not at my computer to check, but does it treat it as shorted if you
overlap three pads?

[  1  [ ]    [ ]   2  ]   (middle pad not named)

I don't recall whether the connection checking code considers the
possibility of connections between pads with different names, but I do
(vaguely) recall there being a work around for the kind of thing your
trying to do. As you learnt though, it isn't something we support in any
easy or elegant way.


Peter



On 28 Jan 2017 12:45, "Richard Rasker (rasker AT linetec DOT nl) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

> Hello,
>
> 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? When I draw a loop antenna and convert it
> into an element, things get problematic: each line segment is designated
> a separate pad number, which produces error messages as soon as the
> element is entered in a netlist (also see attached example).
>
> I tried redefining these lines in several ways using a text editor (by
> changing the pad numbers(*)), but PCB insists on treating the whole
> thing as a collection of shorted nets -- which of course is technically
> correct, but not what is desired.
>
> Simply said: Is there a way to create a 'shorted' element that isn't
> treated as a short circuit by PCB?
>
>
> *: A related question: when defining connector footprints, I usually
> define all mechanical metal parts as pin/pad 0. Would it be possible in
> principle to modify PCB's behaviour to treat these zero pins/pads as
> 'floating', so that they don't produce error messages when connected to
> an arbitrary net, or, alternatively, are left unconnected? Or would that
> raise other problems?
>
> Thanks already,
>
> Best regards,
>
> Richard Rasker
>
> Linetec
> --
> Linetec Translation and Technology Services
> Vleerkottelanden 14
> 7542 MJ  Enschede
> The Netherlands
>
> +31-53-4350834
>
> http://www.linetec.nl/
> e-mail: rasker AT linetec DOT nl
>
>

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

<div dir=3D"auto">I&#39;m not at my computer to check, but does it treat it=
 as shorted if you overlap three pads?<div dir=3D"auto"><br></div><div dir=
=3D"auto">[ =C2=A01 =C2=A0[ ] =C2=A0 =C2=A0[ ] =C2=A0 2 =C2=A0] =C2=A0 (mid=
dle pad not named)</div><div dir=3D"auto"><br></div><div dir=3D"auto">I don=
&#39;t recall whether the connection checking code considers the possibilit=
y of connections between pads with different names, but I do (vaguely) reca=
ll there being a work around for the kind of thing your trying to do. As yo=
u learnt though, it isn&#39;t something we support in any easy or elegant w=
ay.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Peter</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 28 Jan=
 2017 12:45, &quot;Richard Rasker (<a href=3D"mailto:rasker AT linetec DOT nl">ras=
ker AT linetec DOT nl</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user=
@delorie.com</a>]&quot; &lt;<a href=3D"mailto:geda-user AT delorie DOT com">geda-u=
ser AT delorie DOT com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Hello,<br>
<br>
Lately, I started on projects involving Bluetooth and UHF RF, and for<br>
simplicity and cost, I&#39;d like to use PCB antennas.<br>
<br>
While doing this, I ran into a question: how can I &#39;properly&#39; defin=
e PCB<br>
antenna elements/footprints? When I draw a loop antenna and convert it<br>
into an element, things get problematic: each line segment is designated<br=
>
a separate pad number, which produces error messages as soon as the<br>
element is entered in a netlist (also see attached example).<br>
<br>
I tried redefining these lines in several ways using a text editor (by<br>
changing the pad numbers(*)), but PCB insists on treating the whole<br>
thing as a collection of shorted nets -- which of course is technically<br>
correct, but not what is desired.<br>
<br>
Simply said: Is there a way to create a &#39;shorted&#39; element that isn&=
#39;t<br>
treated as a short circuit by PCB?<br>
<br>
<br>
*: A related question: when defining connector footprints, I usually<br>
define all mechanical metal parts as pin/pad 0. Would it be possible in<br>
principle to modify PCB&#39;s behaviour to treat these zero pins/pads as<br=
>
&#39;floating&#39;, so that they don&#39;t produce error messages when conn=
ected to<br>
an arbitrary net, or, alternatively, are left unconnected? Or would that<br=
>
raise other problems?<br>
<br>
Thanks already,<br>
<br>
Best regards,<br>
<br>
Richard Rasker<br>
<br>
Linetec<br>
--<br>
Linetec Translation and Technology Services<br>
Vleerkottelanden 14<br>
7542 MJ=C2=A0 Enschede<br>
The Netherlands<br>
<br>
<a href=3D"tel:%2B31-53-4350834" value=3D"+31534350834">+31-53-4350834</a><=
br>
<br>
<a href=3D"http://www.linetec.nl/" rel=3D"noreferrer" target=3D"_blank">htt=
p://www.linetec.nl/</a><br>
e-mail: <a href=3D"mailto:rasker AT linetec DOT nl">rasker AT linetec DOT nl</a><br>
<br>
</blockquote></div></div>

--94eb2c05612ad73a3405472a7ccd--