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=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=FJafpMZ817oHpgAXOQcgVS5v8m3Dm3hWUNidMFSiQ0c=;
b=HlCJG1SIDh2YXT2bkgyqn/Lp4wJEtg20xEj/UjqSTPTd9De0ExIsKbrAcCHeHi/IZ+
c1Yv4QSHnfsVkzj0ufpo0+c/r+DePZdqKacIpq4PWt7qfRdGvHdHIgHRmU2WddkcGFec
n6Fm7EoNW+hTGBKOjA4qRms3gfPnd+P07CwU0n5Zv4/dL1Y/3af/WCKH9HhvnBkoyr2S
xq4CjMqHqwG+8SF3POcsVaPJ3hxzLljP90hYFEqYwKCJX+aPOYUNKZq3pclNpybQi3pw
U9igTUw42CYRwCRK4UpVrk4h5U70JpG22Gvsu2QSGdG/ogSS565wik4hPE1g5k+jQnD7
C++g==
MIME-Version: 1.0
X-Received: by 10.152.9.9 with SMTP id v9mr6144136laa.111.1441416953689; Fri,
04 Sep 2015 18:35:53 -0700 (PDT)
In-Reply-To: <55E9EEEE.5020804@jump-ing.de>
References: <CAFx0xxi7tMzwv_cN6pUcATz3vQLQ5ugkFcGegNLtCcQuJOxnsA AT mail DOT gmail DOT com>
<55E9EEEE DOT 5020804 AT jump-ing DOT de>
Date: Fri, 4 Sep 2015 19:35:53 -0600
Message-ID: <CAFx0xxi1hL2=qA2n8JH+TjJo_znzj6N8sUoemBiRypPLj1fE3w@mail.gmail.com>
Subject: Re: [geda-user] clearances for auto-routed traces with copper pours
From: "Dave Williams (dave DOT williams DOT lists AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e014951267f7ba3051ef609cc
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
--089e014951267f7ba3051ef609cc
Content-Type: text/plain; charset=UTF-8
Markus
Yes, I will upload a demo PCB to bug tracker that shows the issue.
Meanwhile, when I '> grep Line xxx.pcb' I get 4 different "Line" type
outputs.
Here are 4 examples.
1) Line[5.6700mm 7.7300mm 5.6700mm 8.8500mm 10.00mil 20.00mil "clearline"]
2) Line[16.3500mm 30.2100mm 16.2650mm 30.2950mm 10.00mil 20.00mil ""]
3) Line[11.0000mm 45.0180mm 11.0000mm 49.8255mm 10.00mil 20.00mil "auto"]
4) Line[36.0000mm 0.0000 36.0000mm 55.9700mm 10.00mil 20.00mil
"clearline,selected"]
Are you saying that I will not get plane clearance for the 3) example above
because
the attribute "clearline" is not set? IOW, if 3) was
"LIne[......,"auto,clearline"] then I would have obtained DRC clearance
from the copper plane?
Thanks,
Dave
On Fri, Sep 4, 2015 at 1:20 PM, Markus Hitter (mah AT jump-ing DOT de) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Am 04.09.2015 um 21:03 schrieb Dave Williams
> (dave DOT williams DOT lists AT gmail DOT com) [via geda-user AT delorie DOT com]:
> > I have been assuming that the
> > auto-router enforces the same DRC clearance settings, as with manual
> > routing.
>
> This is a reasonable expectation. Can you create a demonstation PCB and
> upload it together with the text of your mail to the bug tracker?
>
> https://bugs.launchpad.net/pcb
>
> First check I'd do is to look into the .pcb file with a text editor
> wether the "clearline" flag is set for these autorouted tracks.
>
>
> Thanks,
> Markus
>
> --
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. (FH) Markus Hitter
> http://www.jump-ing.de/
>
--089e014951267f7ba3051ef609cc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Markus<br><br>Yes, I will upload a demo PCB to bug tr=
acker that shows the issue.<br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">Meanwhile, when I '> grep Line=C2=A0 xxx.p=
cb' I get 4 different "Line" type outputs.=C2=A0 <br>Here are=
4 examples. <br><br>1) Line[5.6700mm 7.7300mm 5.6700mm 8.8500mm 10.00mil 2=
0.00mil "clearline"]<br>2) Line[16.3500mm 30.2100mm 16.2650mm 30.=
2950mm 10.00mil 20.00mil ""]<br>3) Line[11.0000mm 45.0180mm 11.00=
00mm 49.8255mm 10.00mil 20.00mil "auto"]<br>4) Line[36.0000mm 0.0=
000 36.0000mm 55.9700mm 10.00mil 20.00mil "clearline,selected"]<b=
r><br></div><div class=3D"gmail_extra">Are you saying that I will not get p=
lane clearance for the 3) example above because<br></div><div class=3D"gmai=
l_extra">the attribute "clearline" is not set?=C2=A0 IOW, if 3) w=
as "LIne[......,"auto,clearline"] then I would have obtained=
DRC clearance from the copper plane?<br><br></div><div class=3D"gmail_extr=
a">Thanks,<br>Dave =C2=A0 <br></div><div class=3D"gmail_extra"><br></div><d=
iv class=3D"gmail_extra"><div class=3D"gmail_quote">On Fri, Sep 4, 2015 at =
1:20 PM, Markus Hitter (<a href=3D"mailto:mah AT jump-ing DOT de">mah AT jump-ing DOT de<=
/a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a=
>] <span dir=3D"ltr"><<a href=3D"mailto:geda-user AT delorie DOT com" target=3D=
"_blank">geda-user AT delorie DOT com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Am 04.09.2015 um 21:03 schrieb Dave Willia=
ms<br>
(<a href=3D"mailto:dave DOT williams DOT lists AT gmail DOT com">dave DOT williams DOT lists AT gmail=
.com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT c=
om</a>]:<br>
<span class=3D"">> I have been assuming that the<br>
> auto-router enforces the same DRC clearance settings, as with manual<b=
r>
> routing.<br>
<br>
</span>This is a reasonable expectation. Can you create a demonstation PCB =
and<br>
upload it together with the text of your mail to the bug tracker?<br>
<br>
=C2=A0<a href=3D"https://bugs.launchpad.net/pcb" rel=3D"noreferrer" target=
=3D"_blank">https://bugs.launchpad.net/pcb</a><br>
<br>
First check I'd do is to look into the .pcb file with a text editor<br>
wether the "clearline" flag is set for these autorouted tracks.<b=
r>
<br>
<br>
Thanks,<br>
Markus<br>
<span class=3D""><font color=3D"#888888"><br>
--<br>
- - - - - - - - - - - - - - - - - - -<br>
Dipl. Ing. (FH) Markus Hitter<br>
<a href=3D"http://www.jump-ing.de/" rel=3D"noreferrer" target=3D"_blank">ht=
tp://www.jump-ing.de/</a><br>
</font></span></blockquote></div><br></div></div>
--089e014951267f7ba3051ef609cc--