| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
| d=gmail.com; s=20120113; | |
| h=message-id:date:from:user-agent:mime-version:to:subject:references | |
| :in-reply-to:content-type:content-transfer-encoding; | |
| bh=QDqD8aSNTQ0JNrrCTYhvXwlEcuzu38I9jcIw4TJNog0=; | |
| b=FjzUKBqdO5wSlrtAg1aDTwTK+q4PnhG/dH0FdhYWr7JsycVVyLITb9WJG1h8MoHQru | |
| lRIFgx1AHL+QIWl8Hpf4NRG6howJD1SkqS2Kg8aZyXIZgnJiB7iWrJPHSilMH0jpaYbx | |
| p7C65Oc5pH/ubOOID2cBeKZWC+in4WhW+USh1ShWatXCOZVkf4H+Z7LbY3NE8gLiLlE0 | |
| KQKK42ag59XVWNGvWOWvKnBscske9gftu7kIPJNrIyQsEHZvA3OFVNqluF+Mqlxhxp9C | |
| 2UJK9Pi92VSUNabTZALTQq5/aipA18biglw4OHNzhBNUg0DLd5gFGAKbRisHBNdzBVDK | |
| yftA== | |
| X-Received: | by 10.194.191.131 with SMTP id gy3mr1154507wjc.108.1404634252815; |
| Sun, 06 Jul 2014 01:10:52 -0700 (PDT) | |
| Message-ID: | <53B90489.6030106@gmail.com> |
| Date: | Sun, 06 Jul 2014 10:10:49 +0200 |
| From: | onetmt <onetmt AT gmail DOT com> |
| User-Agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0 |
| MIME-Version: | 1.0 |
| To: | geda-user AT delorie DOT com |
| Subject: | Re: [geda-user] pour clearing around pads |
| References: | <53b8d46a DOT 04a8e00a DOT 7266 DOT 6600SMTPIN_ADDED_BROKEN AT mx DOT google DOT com> |
| In-Reply-To: | <53b8d46a.04a8e00a.7266.6600SMTPIN_ADDED_BROKEN@mx.google.com> |
| Reply-To: | geda-user AT delorie DOT com |
On 06/07/2014 06:41, Lilith Bryant wrote: > On 2014-07-06 04:11:18 PM, Dave Curtis wrote: >> I'm working on a footprint where if I follow the data-sheet geometry and >> my normal design rules, I end up with a footprint where very skinny >> copper peninsulas sneak between pads when it is placed in a polygon. >> The peninsulas neck down to less than the minimum copper width rule. >> >> So, first off, I'm surprised that the Cu polygon allows Cu to pour into >> a space less than the minimum width rule. >> >> Secondly, I'm wondering if fab houses might flag that as a DRC violation >> even if pcb doesn't. >> > > I have had a fab house complain about this. I ended up telling them to just > ignore it, and so far it hasn't been an issue but it does make me a little nervous, > particularly what might happen to fine slivers that get undercut during etching. > > Also, I don't do RF stuff, so ending up with unconnected islands is not a issue for > me. Also my fab used to complain about them; this is why now I carefully draw by hand polygons, deleting them and reshamping them when sub-DRC metals are created. > > I have been meaning to write a polygon "bake" tool that fixes this, but have > been put off by the lack of a workable polygon library. Pretty much just needs > to erode then dilate by the minimum clearance. Was going to use shapely/GEOS > in python, but it's erosion doesn't seem to work :( So it went into the too hard > basket for the time being. > > -- Hofstadter's Law: "It always takes longer than you expect, even when you take into account Hofstadter's Law."
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |