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=1678054042; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=PBAv+MB7MYyjYZnRDXEN+pN+7rKNSYtxCxY5oJ5/AYM=; b=ZZXjn5r3wwr2GOANLh0GhZHqqy1mNxJyTT3tCKbURaDuJiCVnhM+FlXi4R9d9Fhh7G j9XdoVocBKZypuSQVQGyyOYGGRaTun1sb0erF70ipF/vfpDjFkLVTVMM80weM2fbBw0x 16CcWI+uWEs0N6NssMc+FTsHHShDfhI8NQFmTiTzF80Utci7Y7RAdxvKN2Djmfhxg8iH HqYn/KG+G3e+0j/qOjeW1CTFIntGB0E+woO43oBk2D+gTV19ROkBWNC+RFIfiA1iZ/oW AO3emb8VRS9RH/E8F+x1pfmtrenRfgD/kzUx/pwnHyWbCH5t/IeyNsA+srwAzEv22lst 36UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678054042; h=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=PBAv+MB7MYyjYZnRDXEN+pN+7rKNSYtxCxY5oJ5/AYM=; b=laCj0uMif/p338WMLVKqY+J1Xg+wg4/OgDf0EzkzP6CB9l9BQwZkOMGKPjKPSQJlsk yZUVuoNgTYf5xFSTl+rXyTwUe74+QRhh5FVJYa1K0RDQ3Um3gcuU6OqExlWbSbUycoqR czD0ciWy5uUQRNryerAYE/GBqfW+zgwC7ZMdiH9nnqzbUYbx9Sv6d8YxibqbhaNl93KU 8RLPHyaqmzWbdyxkdpwwQgInNV3p7CPvXOWQb0N1mUbM9/rXg/C8NCQ7dYbjfhNP/Xu5 GwAA5wTZDy7Ohcgsr0a+iTMi9OPQGlMJhMbXI55P9mdEMXISJ+mXzp4RYWvBJlmI98aH MMTw== X-Gm-Message-State: AO0yUKVpi5Pu+KR42Uh39rgN2yKEtG+sc5Pa+2mD3RNaxKUrDnIUfWie vksySPBswvvLGpUpDtao7RMxW510IS9XGdDIp2C8myjA X-Google-Smtp-Source: AK7set8tKMp+KXGhqfKA8T5ZMWLbNPKDmuzPN3dEUtQYygb1BySdoVFWbti8AfxkMYvw//CDQ9C/4pAlKm4wdmSwLb8= X-Received: by 2002:a05:6638:36ea:b0:3ec:46d4:e15 with SMTP id t42-20020a05663836ea00b003ec46d40e15mr5286205jau.3.1678054040838; Sun, 05 Mar 2023 14:07:20 -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> <9b18f396-7143-f181-38ca-54adf82436cc AT linetec DOT nl> In-Reply-To: <9b18f396-7143-f181-38ca-54adf82436cc@linetec.nl> From: "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Mon, 6 Mar 2023 08:37:08 +1030 Message-ID: Subject: Re: [geda-user] Connecting pads directly to polygons (was: Strange errors importing gschem into PCB) To: geda-user Content-Type: multipart/alternative; boundary="00000000000004a70005f62e671b" Reply-To: geda-user AT delorie DOT com --00000000000004a70005f62e671b Content-Type: text/plain; charset="UTF-8" You could load it and then add thermals in pcb-rnd, which supports thermals on smd pads. You would not be able to save it in gEDA PCB format afterwards and retain the thermals, as the pcb-rnd padstacks will not losslessly map onto gEDA PCB pin or pad objects. The native pcb-rnd format (.rp) also supports polygonal pad shapes, "roundrect" pad shapes and slots. http://repo.hu/cgi-bin/pool.cgi?project=pcb-rnd&cmd=show&node=thermals Regards, Erich On Mon, 6 Mar 2023 04:14 Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com], wrote: > Hi Chad, > > Op 05-03-2023 om 16:38 schreef Chad Parker (parker DOT charles AT gmail DOT com) > [via geda-user AT delorie DOT com]: > > The correct way to do it is to use thermals or traces to connect pads > > to planes, not to set the clearance to zero. > > AFAICT, pcb's thermal function only works for through-hole components > not pads. So if I want to fully embed for instance a TO252 tab in a > polygon for maximum thermal contact, I need to lay a wide enough > rectangular trace around the tab's pad, and then connect all four sides > to the polygon using the 'J' (join) function? Yes, that works, but it > seems rather clumsy. Isn't it an idea to extend the join function to > pads as well? > > It's mainly a problem at this moment because I'm updating an older, > rather elaborate board with almost a hundred such connections, created > some 5 years ago, when pcb's DRC didn't flag these as errors. Modifying > all those pads as described will take some time, and I was hoping that > there was a simpler way to embed the pads in polygons or else to > suppress those DRC errors. > > Anyway, thanks for the feedback, > > Regards, > > Richard > > --00000000000004a70005f62e671b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You could load it and then add thermals in pcb-rnd, which= supports thermals on smd pads.

You would not be able to save it in gEDA PCB format afterwards and retain= the thermals, as the pcb-rnd padstacks will not losslessly map onto gEDA P= CB pin or pad objects. The native pcb-rnd format (.rp) also supports polygo= nal pad shapes, "roundrect" pad shapes and slots.

=

Regards,

Erich

On Mon, 6 Mar 2023 04:14 Ri= chard Rasker (rasker AT linetec DOT nl) [= via geda-user AT delorie DOT com], &l= t;geda-user AT delorie DOT com> wr= ote:
Hi Chad,

Op 05-03-2023 om 16:38 schreef Chad Parker (parker DOT charles AT gmail DOT com<= /a>)
[via geda-user AT delorie DOT com]:
> The correct way to do it is to use thermals or traces to connect pads =
> to planes, not to set the clearance to zero.

AFAICT, pcb's thermal function only works for through-hole components <= br> not pads. So if I want to fully embed for instance a TO252 tab in a
polygon for maximum thermal contact, I need to lay a wide enough
rectangular trace around the tab's pad, and then connect all four sides=
to the polygon using the 'J' (join) function? Yes, that works, but = it
seems rather clumsy. Isn't it an idea to extend the join function to pads as well?

It's mainly a problem at this moment because I'm updating an older,=
rather elaborate board with almost a hundred such connections, created
some 5 years ago, when pcb's DRC didn't flag these as errors. Modif= ying
all those pads as described will take some time, and I was hoping that
there was a simpler way to embed the pads in polygons or else to
suppress those DRC errors.

Anyway, thanks for the feedback,

Regards,

Richard

--00000000000004a70005f62e671b--