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: <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> In-Reply-To: From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Sun, 5 Mar 2023 10:38:37 -0500 Message-ID: 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 Content-Type: multipart/alternative; boundary="00000000000077c75c05f628f9ef" 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 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
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, 202= 3, 10:18 Roland Lutz <rlutz AT hedmen DOT o= rg> wrote:
On Sun, 5 Mar 202= 3, 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/9b74190843364861b9fc6841d927dc274= 7d63488
>
> 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 <= br> > polygon"? Lines can be connected to polygons using 'J(oin)= 9;, 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 outlin= e
> of e.g. TO252 tabs, using 'J' to connect them to the surroundi= ng
> polygon, but that feels like a bit of a messy kludge.
>
> Maybe it is possible to prevent this Design Rule from being applied wh= en
> 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.<= br>
I'm not too familiar with PCB.=C2=A0 Maybe Bert can help?

--00000000000077c75c05f628f9ef--