delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2023/03/05/10:58:42

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=20210112; t=1678030729;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:from:to:cc:subject:date:message-id:reply-to;
bh=pDoKBd1eVoQN1Cu5jyx9vFwqyRLsB9fVeymjVC4GOTU=;
b=CRdC5zxrkWBloe7WXamBPfyBXyu5i1PQvYMyFDy5TH43CsDK1jPnUQth4dUG5j3nh7
fiIJd8fdKDDbjNGTdYVGH6eE17gWgQ6pLAhsR4/ExTtab681RtwFxGJ3jjF4RqbHGm8x
pkyUwJP23xeobIWVanQZ3TQBMztB27u+nhirVj3mL4//f2xpjlIP1RbgobmlC/MQ5jI6
5Rx0cfeN4ikc5wzneORIIoNJmvmgEtFsOzIucRhblc6XY8fXd1sFLJEBeL9QDlzTXC5Q
h0yjugoVI440ya6kFCe/uwTOT5a4VkvMbNJEn6BZ68TrvaKosv92UiPobm8fmXI841Py
LZyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112; t=1678030729;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
:reply-to;
bh=pDoKBd1eVoQN1Cu5jyx9vFwqyRLsB9fVeymjVC4GOTU=;
b=qczLn1+wAup4I92sF++Ab5IHpbGhanL0zQGT+i5en0oXYyUFP3FTnh0B67UtSTDnWH
+Sb6QX+liTuf7/pEh9cJReLA4j1ZtwK+BSDrBtvwOARtZghBiVmxUQKGlts9yPs5ys3A
cX069c7SBFChSI1xLDS1KbQYCqyN4qS0EXNZ+ZHranl7wRuGZOO6dltOr7bmdTvbv0OF
HXU33sLRyPWmQnRnBzjjxfj4Y5aW0W8FY+u60VA1goWL1cEeWjCAljPkPeVLc71cgEKn
wKZoDX1ZPUjm4nypRkAAlRjh4qiveepEFGNJ4m47Y9u8PzG+atum4bpw9M668riVJpKl
iZOw==
X-Gm-Message-State: AO0yUKWDDaMD06qYzNd2HeaNM9rf/yannoFL5FNPFLfshZNcWR9qKRUA
A/TyHgrlbupMTv0tJTP0PrER7ckswQ9Eq0OgeoJ1n0ac
X-Google-Smtp-Source: AK7set+huXvh3U1Mnd73badAanhSzNP7Pns6flvUNASXiVfZ9JcNMkD9gHy6G5cI6CjmHXtprtjS4fPCImejS8mu6dc=
X-Received: by 2002:a63:931e:0:b0:503:2561:6fed with SMTP id
b30-20020a63931e000000b0050325616fedmr2693093pge.1.1678030728053; Sun, 05 Mar
2023 07:38:48 -0800 (PST)
MIME-Version: 1.0
References: <e142bdaf-597f-6219-5653-993cf530a50a AT linetec DOT nl>
<40bb8153-a4f9-b79c-b4db-d5ed94516e67 AT grinsen-ohne-katze DOT de>
<8edec3dd-d6d1-c94c-3fcf-cd634b7e214e AT linetec DOT nl> <92b8456a-9852-1b10-90de-fa29211ce6e3 AT grinsen-ohne-katze DOT de>
<10d1f03e-fb47-1489-8d45-c412ecfd9e5a AT linetec DOT nl> <c17dea9-d2a8-6e4a-34c9-b47aa36c39b8 AT grinsen-ohne-katze DOT de>
In-Reply-To: <c17dea9-d2a8-6e4a-34c9-b47aa36c39b8@grinsen-ohne-katze.de>
From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Sun, 5 Mar 2023 10:38:37 -0500
Message-ID: <CAJZxidDyCdTaMP6DKwzGfynDyy8iNmbywy71NHFh5KocRApPhg@mail.gmail.com>
Subject: Re: [geda-user] Connecting pads directly to polygons (was: Strange
errors importing gschem into PCB)
To: geda-user AT delorie DOT com
Cc: Bert Timmerman <ljh4timm AT xs4all DOT nl>
Reply-To: geda-user AT delorie DOT com

--00000000000077c75c05f628f9ef
Content-Type: text/plain; charset="UTF-8"

The correct way to do it is to use thermals or traces to connect pads to
planes, not to set the clearance to zero.

On Sun, Mar 5, 2023, 10:18 Roland Lutz <rlutz AT hedmen DOT org> wrote:

> On Sun, 5 Mar 2023, Richard Rasker (rasker AT linetec DOT nl) [via
> geda-user AT delorie DOT com] wrote:
> > Op 04-03-2023 om 23:24 schreef Roland Lutz:
> >> This patch should fix the issue:
> >>
> https://github.com/rlutz/geda-gaf/commit/9b74190843364861b9fc6841d927dc2747d63488
> >
> > Thank you for this quick fix! This indeed solves the problems with
> > unconnected duplicate pins.
>
> Thank you for testing the patch!
>
>
> > Final question: is there a way to connect pads directly to polygons
> > without the DRC warning "Pad with insufficient clearance inside
> > polygon"? Lines can be connected to polygons using 'J(oin)', but that
> > doesn't work for pads.
> >
> > In some older designs with lots of thermal and high-current pads I now
> > get almost a hundred of these DRC warnings, increasing the risk of
> > overlooking any new, real DRC issues. I guess I could trace the outline
> > of e.g. TO252 tabs, using 'J' to connect them to the surrounding
> > polygon, but that feels like a bit of a messy kludge.
> >
> > Maybe it is possible to prevent this Design Rule from being applied when
> > the clearance is actually zero? Because I'd say that unintentional
> > shorts are already caught by the connection check, and that this rule
> > check is only needed to locate non-zero distances that are too small.
>
> I'm not too familiar with PCB.  Maybe Bert can help?
>
>

--00000000000077c75c05f628f9ef
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">The correct way to do it is to use thermals or traces to =
connect pads to planes, not to set the clearance to zero.</div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 5, 202=
3, 10:18 Roland Lutz &lt;<a href=3D"mailto:rlutz AT hedmen DOT org">rlutz AT hedmen DOT o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, 5 Mar 202=
3, Richard Rasker (<a href=3D"mailto:rasker AT linetec DOT nl" target=3D"_blank" r=
el=3D"noreferrer">rasker AT linetec DOT nl</a>) [via <br>
<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank" rel=3D"noreferre=
r">geda-user AT delorie DOT com</a>] wrote:<br>
&gt; Op 04-03-2023 om 23:24 schreef Roland Lutz:<br>
&gt;&gt; This patch should fix the issue:<br>
&gt;&gt; <a href=3D"https://github.com/rlutz/geda-gaf/commit/9b741908433648=
61b9fc6841d927dc2747d63488" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>https://github.com/rlutz/geda-gaf/commit/9b74190843364861b9fc6841d927dc274=
7d63488</a> <br>
&gt;<br>
&gt; Thank you for this quick fix! This indeed solves the problems with <br=
>
&gt; unconnected duplicate pins.<br>
<br>
Thank you for testing the patch!<br>
<br>
<br>
&gt; Final question: is there a way to connect pads directly to polygons <b=
r>
&gt; without the DRC warning &quot;Pad with insufficient clearance inside <=
br>
&gt; polygon&quot;? Lines can be connected to polygons using &#39;J(oin)&#3=
9;, but that <br>
&gt; doesn&#39;t work for pads.<br>
&gt;<br>
&gt; In some older designs with lots of thermal and high-current pads I now=
 <br>
&gt; get almost a hundred of these DRC warnings, increasing the risk of <br=
>
&gt; overlooking any new, real DRC issues. I guess I could trace the outlin=
e <br>
&gt; of e.g. TO252 tabs, using &#39;J&#39; to connect them to the surroundi=
ng <br>
&gt; polygon, but that feels like a bit of a messy kludge.<br>
&gt;<br>
&gt; Maybe it is possible to prevent this Design Rule from being applied wh=
en <br>
&gt; the clearance is actually zero? Because I&#39;d say that unintentional=
 <br>
&gt; shorts are already caught by the connection check, and that this rule =
<br>
&gt; check is only needed to locate non-zero distances that are too small.<=
br>
<br>
I&#39;m not too familiar with PCB.=C2=A0 Maybe Bert can help?<br>
<br>
</blockquote></div>

--00000000000077c75c05f628f9ef--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019