Mail Archives: geda-help/2020/09/08/14:02:01
--00000000000044429605aed0ef85
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Okay, so in terms of urgency here, these warnings are not interfering with
the design you're trying to build. pcb isn't preventing you from drawing
the circuit you need to draw, it's just throwing these warnings. Correct?
The first one worries me a little, but the second two I actually think are
appropriate. You may be doing it deliberately in a controlled way, but you
are shorting two nets together and I think it's appropriate for pcb to
throw a warning there. If for no other reason then to remind you to check
that it is actually being done the way you think it is.
The first warning about not finding pin 2 is surprising to me. Even if the
pin is shorted to something else, it should still be found. I have a hunch
about this, but I think it's worth filing a bug report.
If you need microcontroller lab ideas, I've got a slew of them :)
Cheers,
--Chad
On Mon, Sep 7, 2020 at 5:02 PM Roger Traylor (traylor AT engr DOT orst DOT edu) [via
geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
> Chad,
> Sorry for the late reply. Its been a busy season for me.
>
> Yes, the message I see is in the log window. When I do make the
> connection,
> matching L and C to antenna input pin 1, and ground pin 2 on the antenna,
> the log window says:
>
> Can't find U11 pin 2 called for in netlist.
> Warning! Net "GND" is shorted to net "unnamed_net75"
> Warning! Net "unnamed_net75" is shorted to net "GND"
>
> Pin 2 is the one I wanted to ground as it is the matching stub.
>
> I will try your attached .pcb file and see how that looks.
>
> One other thing I was going to try was to (in gschem) ground the input to
> the
> antenna, and also connect it to antenna pin 1. Then, grounding pin 2 shou=
ld
> cause no conflicts.
>
> I will try to get back to this soon. Trying to set up a lab-based
> micro-controller
> class for 100% remote learning. Its kicking my backside.
>
> Thanks again,
> Roger
>
> On Sep 4, 2020, at 8:47 AM, Chad
>
>
> (parker DOT charles AT gmail DOT com) [via geda-help AT delorie DOT com] <
> geda-help AT delorie DOT com> wrote:
>
> Rodger-
>
> Sorry for the delay in responding.
>
> I don't think pcb actually checks to see if the pads are overlapping, but
> maybe I just haven't found that corner of the code yet. It should let you
> do more or less whatever you want.
>
> The error message your getting is in the log window? When do you get it?
>
> An alternative, albeit a little less convenient might be the attached. I
> made the footprint to contain the outline and pads one and two, and then
> left the other segments as lines. You can go File > Load layout to buffer=
,
> and then paste it in. It's less convenient because if you want to move it
> you have to select all the pieces, but you can box select, so, maybe it's
> not that annoying. Since the segments are traces now, they have rounded e=
nd
> caps, but don't you usually want that for RF applications anyway?
>
> If this doesn't work for you, please let me know. If you can send a
> minimal complete example (schematic, commands and scripts used, etc.) I c=
an
> try to dig in and see what I can do.
>
> Thanks,
> --Chad
>
> On Thu, Sep 3, 2020 at 3:13 AM Erich Heinzle (a1039181 AT gmail DOT com) [via
> geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
>
>> There are two other things to know for these sorts of applications
>>
>> 1) inkscape2pcb now exports (v0.92 inkscape) simple polygons to pcb-rnd
>> footprints, as well as paths, allowing application note designs like thi=
s
>> to be converted fairly easily from source documents to copper polygons.
>> Footprints can then be scaled in x, y or both directions in pcb-rnd too.
>>
>> https://github.com/erichVK5/inkscape2pcb
>>
>> 2) pstoedit can do similar exports of postscript features to pcb layouts=
,
>> and the next release should include code for a plugin that exports polyg=
ons
>> to pcb-rnd footprints.
>>
>> http://www.calvina.de/pstoedit/pstoedit.htm
>>
>>
>> The look and feel is much the same for pcb-rnd vs PCB, but keyboard
>> shortcuts have had to evolve to keep up with the features.
>>
>> Regards,
>>
>> Erich
>>
>>
>> On Thu, 3 Sep 2020 15:16 Roger Traylor (traylor AT engr DOT orst DOT edu) [via
>> geda-help AT delorie DOT com], <geda-help AT delorie DOT com> wrote:
>>
>>> Erich,
>>>
>>> Thanks for the info. I figured pcb-rnd could probably handle this
>>> situation.
>>>
>>> Right now however, I need to get a job done. I=E2=80=99d like to try p=
cb-rnd as
>>> I've
>>> followed the development for a while but it feels like the =E2=80=9Ctra=
in has
>>> left the
>>> station=E2=80=9D as far as I=E2=80=99m concerned. It looks daunting to =
get started with
>>> and I
>>> see no on-ramp for beginners. Maybe for the next project.
>>>
>>> Thanks again,
>>> Roger
>>>
>>> On Sep 2, 2020, at 4:37 PM, Erich Heinzle (a1039181 AT gmail DOT com) [via
>>> geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
>>>
>>> pcb-rnd allows polygons within footprint elements, as well as lines and
>>> arcs, which, in combination with terminals, can produce the sorts of
>>> structures you are playing with more easily.
>>>
>>> Importantly, there is also an "intnoconn" attribute that can be used on
>>> copper features within the footprint
>>>
>>> http://repo.hu/cgi-bin/pool.cgi?cmd=3Dshow&node=3Dintnoconn
>>>
>>> That can be used, for example within a pcb spiral inductor, so that the
>>> copper does not look like a short across the terminals.
>>>
>>> With the gEDA PCB footprint data model, you will have to paint the
>>> features with pads, will end up with a short with DRC, and will have a
>>> limited ability to manipulate the solder mask over the features, if nee=
ded.
>>>
>>>
>>> Regards,
>>>
>>> Erich
>>>
>>> On Thu, 3 Sep 2020 08:43 Roger Traylor (traylor AT engr DOT orst DOT edu) [via
>>> geda-help AT delorie DOT com], <geda-help AT delorie DOT com> wrote:
>>>
>>>> Gang,
>>>> A quick question for PCB gurus:
>>>>
>>>> I have a =E2=80=9Cfolded F=E2=80=9D antenna for 2.4Ghz. It has one op=
en end, one input
>>>> for the signal
>>>> and one matching stub that is to be connected to ground.
>>>>
>>>> I drew this in PCB as a series of =E2=80=9Cpads=E2=80=9D. I attempted =
to make one pad
>>>> =E2=80=9C1=E2=80=9D the input,
>>>> and pad =E2=80=9C2=E2=80=9D as ground. gschem did not complain about =
the symbol, but
>>>> PCB complains
>>>> about not being able to find pad "2" (the ground pin).
>>>>
>>>> Could this be because PCB sees all the pads overlapping as one pad? I=
f
>>>> so, how can
>>>> I overcome this problem?
>>>>
>>>> Thanks,
>>>> Roger Traylor
>>>>
>>>> Footprint file is below:
>>>>
>>>> Element[0x00000000 "" "" "" 0 0 0 0 0 100 0x00000000]
>>>> #Flipped Meander antenna for CC2500
>>>> #R. Traylor 7.27.2020
>>>> #50 ohm feed point is at end of segment 10
>>>> #requires via to ground plane at bottom of segment 11
>>>> #silk at bottom marks the edge of the ground plane
>>>> #see TI/Chipcon Application Note AN043
>>>> #This is the flipped version of the original meander antenna
>>>> #
>>>> (
>>>> # X1 Y1 X2 Y2 thick clear mask name
>>>> numb flag
>>>> # right side from origin
>>>> Pad[ 0 0 8661 0 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 0
>>>> Pad[ 8661 0 8661 -10394 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 1
>>>> Pad[ 8661 -10394 18504 -10394 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 2
>>>> Pad[ 18504 -10394 18504 0 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 3
>>>> Pad[ 18504 0 27165 0 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 4
>>>> Pad[ 27165 0 27165 -15512 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 5
>>>> # left side from origin
>>>> Pad[ 0 0 0 -10394 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 6
>>>> Pad[ 0 -10394 -9843 -10394 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 7
>>>> Pad[-9843 -10394 -9843 0 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 8
>>>> Pad[-9843 0 -27559 0 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 9
>>>> Pad[-18504 -787 -18504 -19281 1969 0 10000 "1"
>>>> "1" 0x00000100] #segment 10
>>>> Pad[-26772 -787 -26772 -18504 3543 0 10000 "2"
>>>> "2" 0x00000100] #segment 11
>>>> #silk lines
>>>> ElementLine[-30197 2559 29725 2559 700] #top
>>>> ElementLine[ 29725 2559 29725 -18307 700] #right
>>>> ElementLine[-30118 2559 -30118 -18307 700] #left
>>>> ElementLine[-30118 -18307 -29724 -18307 700] #bottom starting
>>>> from left
>>>> ElementLine[-23798 -18307 -20678 -18307 700] #segment between
>>>> vertical pieces
>>>> ElementLine[-16318 -18307 29564 -18307 700] #right-most
>>>> segement
>>>> )
>>>> # antenna layout
>>>> #
>>>> # * =3D origin
>>>> # -------s9-- *--s0--- ----s4--|
>>>> # | | | | | | |
>>>> # | | s8 s6 s1 s3 |
>>>> # | | | | | | s5
>>>> # s11 | |---s7---| |---s2--- |
>>>> # | | |
>>>> # | s10 |
>>>> # | | |
>>>> # | |
>>>> #
>>>>
>>>>
>>>>
>>> <antennalayout.pcb>
>
>
>
--00000000000044429605aed0ef85
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Okay, so in terms of urgency here, these warnings are=
not interfering with the design you're trying to build. pcb isn't =
preventing you from drawing the circuit you need to draw, it's just thr=
owing these warnings. Correct?</div><div><br></div><div>The first one worri=
es me a little, but the second two I actually think are appropriate. You ma=
y be doing it deliberately in a controlled way, but you are shorting two ne=
ts together and I think it's appropriate for pcb to throw a warning the=
re. If for no other reason then to remind you to check that it is actually =
being done the way you think it is.</div><div><br></div><div>The first warn=
ing about not finding pin 2 is surprising to me. Even if the pin is shorted=
to something else, it should still be found. I have a hunch about this, bu=
t I think it's worth filing a bug report.<br></div><div><br></div><div>=
</div><div>If you need microcontroller lab ideas, I've got a slew of th=
em :) </div><div><br></div><div>Cheers,</div><div>--Chad<br></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, S=
ep 7, 2020 at 5:02 PM Roger Traylor (<a href=3D"mailto:traylor AT engr DOT orst DOT ed=
u">traylor AT engr DOT orst DOT edu</a>) [via <a href=3D"mailto:geda-help AT delorie DOT com"=
>geda-help AT delorie DOT com</a>] <<a href=3D"mailto:geda-help AT delorie DOT com">ge=
da-help AT delorie DOT com</a>> wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div style=3D"overflow-wrap: break-word;">Chad,<div>Sorr=
y for the late reply.=C2=A0 Its been a busy season for me.</div><div><br></=
div><div>Yes, the message I see is in the log window.=C2=A0 When I do make =
the connection,</div><div>matching L and C to antenna input pin 1, and grou=
nd pin 2 on the antenna,=C2=A0</div><div>the log window says:</div><div><br=
></div><div><font style=3D"font-size:14px" face=3D"Courier">Can't find =
U11 pin 2 called for in netlist.</font></div><div><div><font style=3D"font-=
size:14px" face=3D"Courier">Warning! Net "GND" is shorted to net =
"unnamed_net75"</font></div><div><font style=3D"font-size:14px" f=
ace=3D"Courier">Warning! Net "unnamed_net75" is shorted to net &q=
uot;GND"</font></div></div><div><br></div><div>Pin 2 is the one I want=
ed to ground as it is the matching stub.</div><div><br></div><div>I will tr=
y your attached .pcb file and see how that looks.</div><div><br></div><div>=
One other thing I was going to try was to (in gschem) ground the input to t=
he</div><div>antenna, and also connect it to antenna pin 1. Then, grounding=
pin 2 should</div><div>cause no conflicts.=C2=A0</div><div><br></div><div>=
I will try to get back to this soon. Trying to set up a lab-based micro-con=
troller</div><div>class for 100% remote learning.=C2=A0 Its kicking my back=
side.</div><div><br></div><div>Thanks again,</div><div>Roger<br><div><br><b=
lockquote type=3D"cite"><div>On Sep 4, 2020, at 8:47 AM, Chad</div></blockq=
uote><div><br></div><blockquote type=3D"cite"><div>=C2=A0(<a href=3D"mailto=
:parker DOT charles AT gmail DOT com" target=3D"_blank">parker DOT charles AT gmail DOT com</a>) =
[via <a href=3D"mailto:geda-help AT delorie DOT com" target=3D"_blank">geda-help AT d=
elorie.com</a>] <<a href=3D"mailto:geda-help AT delorie DOT com" target=3D"_bla=
nk">geda-help AT delorie DOT com</a>> wrote:</div><br><div><div dir=3D"ltr"><di=
v>Rodger-</div><div><br></div><div>Sorry for the delay in responding. <br><=
/div><div><br></div><div>I don't think pcb actually checks to see if th=
e pads are overlapping, but maybe I just haven't found that corner of t=
he code yet. It should let you do more or less whatever you want. <br></div=
><div><br></div><div>The error message your getting is in the log window? W=
hen do you get it?</div><div><br></div><div>An alternative, albeit a little=
less convenient might be the attached. I made the footprint to contain the=
outline and pads one and two, and then left the other segments as lines. Y=
ou can go File > Load layout to buffer, and then paste it in. It's l=
ess convenient because if you want to move it you have to select all the pi=
eces, but you can box select, so, maybe it's not that annoying. Since t=
he segments are traces now, they have rounded end caps, but don't you u=
sually want that for RF applications anyway?</div><div><br></div><div>If th=
is doesn't work for you, please let me know. If you can send a minimal =
complete example (schematic, commands and scripts used, etc.) I can try to =
dig in and see what I can do.</div><div><br></div><div>Thanks,</div><div>--=
Chad<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, Sep 3, 2020 at 3:13 AM Erich Heinzle (<a href=3D"ma=
ilto:a1039181 AT gmail DOT com" target=3D"_blank">a1039181 AT gmail DOT com</a>) [via <a =
href=3D"mailto:geda-help AT delorie DOT com" target=3D"_blank">geda-help AT delorie DOT c=
om</a>] <<a href=3D"mailto:geda-help AT delorie DOT com" target=3D"_blank">geda=
-help AT delorie DOT com</a>> wrote:<br></div><blockquote class=3D"gmail_quote"=
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"auto">There are two other things to know for t=
hese sorts of applications<div dir=3D"auto"><br></div><div dir=3D"auto">1) =
inkscape2pcb now exports (v0.92 inkscape) simple polygons to pcb-rnd footpr=
ints, as well as paths, allowing application note designs like this to be c=
onverted fairly easily from source documents to copper polygons. Footprints=
can then be scaled in x, y or both directions in pcb-rnd too.</div><div di=
r=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://github.com/erichV=
K5/inkscape2pcb" target=3D"_blank">https://github.com/erichVK5/inkscape2pcb=
</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">2) pstoedit can do =
similar exports of postscript features to pcb layouts, and the next release=
should include code for a plugin that exports polygons to pcb-rnd footprin=
ts.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"http://ww=
w.calvina.de/pstoedit/pstoedit.htm" target=3D"_blank">http://www.calvina.de=
/pstoedit/pstoedit.htm</a><br></div><div dir=3D"auto"><br></div><div dir=3D=
"auto"><br></div><div dir=3D"auto">The look and feel is much the same for p=
cb-rnd vs PCB, but keyboard shortcuts have had to evolve to keep up with th=
e features.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Regards,</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">Erich</div><div dir=3D"auto=
"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Thu, 3 Sep 2020 15:16 Roger Traylor (<a href=3D"mailto:trayl=
or AT engr DOT orst DOT edu" rel=3D"noreferrer" target=3D"_blank">traylor AT engr DOT orst DOT ed=
u</a>) [via <a href=3D"mailto:geda-help AT delorie DOT com" rel=3D"noreferrer" tar=
get=3D"_blank">geda-help AT delorie DOT com</a>], <<a href=3D"mailto:geda-help@=
delorie.com" rel=3D"noreferrer" target=3D"_blank">geda-help AT delorie DOT com</a>=
> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
>Erich,<div><br><div>Thanks for the info. I figured pcb-rnd could probably =
handle this situation.</div><div><br></div><div>Right now however, I need t=
o get a job done.=C2=A0 I=E2=80=99d like to try pcb-rnd as I've</div><d=
iv>followed the development for a while but it feels like the =E2=80=9Ctrai=
n has left the=C2=A0</div><div>station=E2=80=9D as far as I=E2=80=99m conce=
rned. It looks daunting to get started with and I</div><div>see no on-ramp =
for beginners. Maybe for the next project.</div><div><br></div><div>Thanks =
again,</div><div>Roger<br><div><br><blockquote type=3D"cite"><div>On Sep 2,=
2020, at 4:37 PM, Erich Heinzle (<a href=3D"mailto:a1039181 AT gmail DOT com" rel=
=3D"noreferrer noreferrer" target=3D"_blank">a1039181 AT gmail DOT com</a>) [via <=
a href=3D"mailto:geda-help AT delorie DOT com" rel=3D"noreferrer noreferrer" targe=
t=3D"_blank">geda-help AT delorie DOT com</a>] <<a href=3D"mailto:geda-help AT del=
orie.com" rel=3D"noreferrer noreferrer" target=3D"_blank">geda-help AT delorie=
.com</a>> wrote:</div><br><div><div dir=3D"auto"><div>pcb-rnd allows pol=
ygons within footprint elements, as well as lines and arcs, which, in combi=
nation with terminals, can produce the sorts of structures you are playing =
with more easily.<div dir=3D"auto"><br></div><div dir=3D"auto">Importantly,=
there is also an "intnoconn" attribute that can be used on coppe=
r features within the footprint</div><div dir=3D"auto"><br></div><div dir=
=3D"auto"><a href=3D"http://repo.hu/cgi-bin/pool.cgi?cmd=3Dshow&node=3D=
intnoconn" rel=3D"noreferrer noreferrer" target=3D"_blank">http://repo.hu/c=
gi-bin/pool.cgi?cmd=3Dshow&node=3Dintnoconn</a><br></div><div dir=3D"au=
to"><br></div><div dir=3D"auto">That can be used, for example within a pcb =
spiral inductor, so that the copper does not look like a short across the t=
erminals.</div><div dir=3D"auto"><br></div><div dir=3D"auto">With the gEDA =
PCB footprint data model, you will have to paint the features with pads, wi=
ll end up with a short with DRC, and will have a limited ability to manipul=
ate the solder mask over the features, if needed.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto"><br></div>Regards,</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">Erich<br><br><div class=3D"gmail_quote" dir=3D"auto"><=
div dir=3D"ltr" class=3D"gmail_attr">On Thu, 3 Sep 2020 08:43 Roger Traylor=
(<a href=3D"mailto:traylor AT engr DOT orst DOT edu" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">traylor AT engr DOT orst DOT edu</a>) [via <a href=3D"mailto:geda-help=
@delorie.com" rel=3D"noreferrer noreferrer" target=3D"_blank">geda-help AT del=
orie.com</a>], <<a href=3D"mailto:geda-help AT delorie DOT com" rel=3D"noreferr=
er noreferrer" target=3D"_blank">geda-help AT delorie DOT com</a>> wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Gang,<div>A quic=
k question for PCB gurus:</div><div><br></div><div>I have a =E2=80=9Cfolded=
F=E2=80=9D antenna for 2.4Ghz.=C2=A0 It has one open end, one input for th=
e signal</div><div>and one matching stub that is to be connected to ground.=
</div><div><br></div><div>I drew this in PCB as a series of =E2=80=9Cpads=
=E2=80=9D. I attempted to make one pad =E2=80=9C1=E2=80=9D =C2=A0the input,=
</div><div>and pad =E2=80=9C2=E2=80=9D as ground. =C2=A0gschem did not comp=
lain about the symbol, but PCB complains=C2=A0</div><div>about not being ab=
le to find pad "2" (the ground pin).=C2=A0</div><div><br></div><d=
iv>Could this be because PCB sees all the pads overlapping as one pad?=C2=
=A0 If so, how can</div><div>I overcome this problem?</div><div><br></div><=
div>Thanks,</div><div>Roger Traylor</div><div><br></div><div>Footprint file=
is below:</div><div><br></div><div><div><font style=3D"font-size:12px" fac=
e=3D"Courier">Element[0x00000000 "" "" "" 0 0=
0 0 0 100 0x00000000]</font></div><div><font style=3D"font-size:12px" face=
=3D"Courier">#Flipped Meander antenna for CC2500 =C2=A0</font></div><div><f=
ont style=3D"font-size:12px" face=3D"Courier">#R. Traylor 7.27.2020</font><=
/div><div><font style=3D"font-size:12px" face=3D"Courier">#50 ohm feed poin=
t is at end of segment 10</font></div><div><font style=3D"font-size:12px" f=
ace=3D"Courier">#requires via to ground plane at bottom of segment 11</font=
></div><div><font style=3D"font-size:12px" face=3D"Courier">#silk at bottom=
marks the edge of the ground plane</font></div><div><font style=3D"font-si=
ze:12px" face=3D"Courier">#see TI/Chipcon Application Note AN043</font></di=
v><div><font style=3D"font-size:12px" face=3D"Courier">#This is the flipped=
version of the original meander antenna</font></div><div><font style=3D"fo=
nt-size:12px" face=3D"Courier">#</font></div><div><font style=3D"font-size:=
12px" face=3D"Courier">(</font></div><div><font style=3D"font-size:12px" fa=
ce=3D"Courier"># =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0X1 =C2=A0 =
=C2=A0 =C2=A0Y1 =C2=A0 =C2=A0 X2 =C2=A0 =C2=A0 =C2=A0 Y2 =C2=A0 =C2=A0thick=
=C2=A0clear =C2=A0mask =C2=A0name numb =C2=A0 =C2=A0 =C2=A0 flag</font></d=
iv><div><font style=3D"font-size:12px" face=3D"Courier"># right side from o=
rigin</font></div><div><font style=3D"font-size:12px" face=3D"Courier">=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ =C2=A0 =C2=A00 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =
=C2=A08661 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A01969 =C2=A0 =C2=A0 0 =C2=A0 =
10000 =C2=A0 "1" =C2=A0"1" 0x00000100] =C2=A0#segment 0=
</font></div><div><font style=3D"font-size:12px" face=3D"Courier">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Pad[ 8661 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A08661 =C2=
=A0 -10394 =C2=A0 1969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "1" =
=C2=A0"1" 0x00000100] =C2=A0#segment 1</font></div><div><font sty=
le=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ 866=
1 =C2=A0 -10394 =C2=A018504 =C2=A0 -10394 =C2=A0 1969 =C2=A0 =C2=A0 0 =C2=
=A0 10000 =C2=A0 "1" =C2=A0"1" 0x00000100] =C2=A0#segme=
nt 2</font></div><div><font style=3D"font-size:12px" face=3D"Courier">=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ 18504 =C2=A0-10394 =C2=A018504 =C2=A0 =C2=A0 =
=C2=A0 0 =C2=A0 =C2=A01969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "1"=
; =C2=A0"1" 0x00000100] =C2=A0#segment 3</font></div><div><font s=
tyle=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ 1=
8504 =C2=A0 =C2=A0 =C2=A00 =C2=A0 27165 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=
=A01969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "1" =C2=A0"1&quo=
t; 0x00000100] =C2=A0#segment 4</font></div><div><font style=3D"font-size:1=
2px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ 27165 =C2=A0 =C2=A0 =
=C2=A00 =C2=A0 27165 =C2=A0 -15512 =C2=A0 1969 =C2=A0 =C2=A0 0 =C2=A0 10000=
=C2=A0 "1" =C2=A0"1" 0x00000100] =C2=A0#segment 5</fon=
t></div><div><font style=3D"font-size:12px" face=3D"Courier"># left side fr=
om origin =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0</font></div><=
div><font style=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Pad[ =C2=A0 =C2=A00 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 0 =
=C2=A0 -10394 =C2=A0 1969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "1"=
=C2=A0"1" 0x00000100] =C2=A0#segment 6</font></div><div><font st=
yle=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[ =
=C2=A0 =C2=A00 =C2=A0 -10394 =C2=A0-9843 =C2=A0 -10394 =C2=A0 1969 =C2=A0 =
=C2=A0 0 =C2=A0 10000 =C2=A0 "1" =C2=A0"1" 0x00000100] =
=C2=A0#segment 7</font></div><div><font style=3D"font-size:12px" face=3D"Co=
urier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[-9843 =C2=A0 -10394 =C2=A0-9843 =C2=
=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A01969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 &=
quot;1" =C2=A0"1" 0x00000100] =C2=A0#segment 8</font></div><=
div><font style=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Pad[-9843 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0-27559 =C2=A0 =C2=A0 =C2=A0 0=
=C2=A0 =C2=A01969 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "1" =C2=A0=
"1" 0x00000100] =C2=A0#segment 9</font></div><div><font style=3D"=
font-size:12px" face=3D"Courier">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pad[-18504 =C2=
=A0 =C2=A0-787 -18504 =C2=A0 -19281 =C2=A0 1969 =C2=A0 =C2=A0 0 =C2=A0 1000=
0 =C2=A0 "1" =C2=A0"1" 0x00000100] =C2=A0#segment 10</f=
ont></div><div><font style=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Pad[-26772 =C2=A0 =C2=A0-787 -26772 =C2=A0 -18504 =C2=A0 =
3543 =C2=A0 =C2=A0 0 =C2=A0 10000 =C2=A0 "2" =C2=A0"2" =
0x00000100] =C2=A0#segment 11</font></div><div><font style=3D"font-size:12p=
x" face=3D"Courier">#silk lines</font></div><div><font style=3D"font-size:1=
2px" face=3D"Courier">=C2=A0 =C2=A0ElementLine[-30197 =C2=A02559 =C2=A02972=
5 =C2=A0 2559 =C2=A0700] =C2=A0 =C2=A0 =C2=A0 #top</font></div><div><font s=
tyle=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0ElementLine[ 29725 =
=C2=A02559 =C2=A029725 =C2=A0-18307 =C2=A0700] =C2=A0 =C2=A0 =C2=A0#right</=
font></div><div><font style=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=
=A0ElementLine[-30118 =C2=A02559 -30118 =C2=A0-18307 =C2=A0700] =C2=A0 =C2=
=A0 =C2=A0#left</font></div><div><font style=3D"font-size:12px" face=3D"Cou=
rier">=C2=A0 =C2=A0ElementLine[-30118 =C2=A0-18307 -29724 =C2=A0-18307 =C2=
=A0700] =C2=A0 =C2=A0#bottom starting from left</font></div><div><font styl=
e=3D"font-size:12px" face=3D"Courier">=C2=A0 =C2=A0ElementLine[-23798 =C2=
=A0-18307 -20678 =C2=A0-18307 =C2=A0700] =C2=A0 =C2=A0#segment between vert=
ical pieces</font></div><div><font style=3D"font-size:12px" face=3D"Courier=
">=C2=A0 =C2=A0ElementLine[-16318 =C2=A0-18307 =C2=A029564 =C2=A0-18307 =C2=
=A0700] =C2=A0 =C2=A0#right-most segement</font></div><div><font style=3D"f=
ont-size:12px" face=3D"Courier">)</font></div><div><font style=3D"font-size=
:12px" face=3D"Courier"># antenna layout</font></div><div><font style=3D"fo=
nt-size:12px" face=3D"Courier">#</font></div><div><font style=3D"font-size:=
12px" face=3D"Courier"># * =3D origin</font></div><div><font style=3D"font-=
size:12px" face=3D"Courier"># =C2=A0 =C2=A0 -------s9-- =C2=A0 =C2=A0 =C2=
=A0 =C2=A0*--s0--- =C2=A0 =C2=A0 =C2=A0 ----s4--|</font></div><div><font st=
yle=3D"font-size:12px" face=3D"Courier"># =C2=A0 =C2=A0 | =C2=A0 =C2=A0| =
=C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0| =C2=A0 =
=C2=A0 =C2=A0 | =C2=A0 =C2=A0 =C2=A0 |</font></div><div><font style=3D"font=
-size:12px" face=3D"Courier"># =C2=A0 =C2=A0 | =C2=A0 =C2=A0| =C2=A0 s8 =C2=
=A0 =C2=A0 =C2=A0 s6 =C2=A0 =C2=A0 =C2=A0s1 =C2=A0 =C2=A0 s3 =C2=A0 =C2=A0 =
=C2=A0 |</font></div><div><font style=3D"font-size:12px" face=3D"Courier">#=
=C2=A0 =C2=A0 | =C2=A0 =C2=A0| =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0|=
=C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 =C2=A0s5</font>=
</div><div><font style=3D"font-size:12px" face=3D"Courier"># =C2=A0 =C2=A0s=
11 =C2=A0 | =C2=A0 =C2=A0|---s7---| =C2=A0 =C2=A0 =C2=A0|---s2--- =C2=A0 =
=C2=A0 =C2=A0 |</font></div><div><font style=3D"font-size:12px" face=3D"Cou=
rier"># =C2=A0 =C2=A0 | =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0|</font></div><div><font style=3D"font-size:12px" face=3D"=
Courier"># =C2=A0 =C2=A0 | =C2=A0 s10 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 |</font></div><div><font style=3D"font-size:12px" face=3D"Courie=
r"># =C2=A0 =C2=A0 | =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0|</font></div><div><font style=3D"font-size:12px" face=3D"Cour=
ier"># =C2=A0 =C2=A0 | =C2=A0 =C2=A0|</font></div><div><font style=3D"font-=
size:12px" face=3D"Courier">#</font></div></div><div><span style=3D"font-si=
ze:12px"><br></span></div><div><div><br></div></div></div></blockquote></di=
v></div></div>
</div></blockquote></div><br></div></div></div></blockquote></div>
</blockquote></div>
<span id=3D"gmail-m_-8726207070756073142cid:f_keoeo1770"><antennalayout.=
pcb></span></div></blockquote></div><br></div></div></blockquote></div>
--00000000000044429605aed0ef85--
- Raw text -