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=optonline.net;
	s=dkim-001; t=1603587744;
	bh=Phk6h+6VAkHvw/0g9vMXS8EHxT76E3UQTBATgOA69go=;
	h=From:Date:Message-ID:Subject:To;
	b=QT8IvEP0f2ilsq+JVVmE/zSLF5kBqRonxwqmH2ny8eTzmoymltK545xu4SGm0Xttn
	MQ38NXKsZHC4iIJH2HJ7+PTtvUfW4BgsGGSQC4Ll8D0zbbprliCei86n8M/V9lt+RM
	0joje0zJ2T3MB9wohGRBbCUmtNjImEtRP3fzl7t9/Wr0PCm3mFnfRmCgs56cIw5SX/
	drvgP0JBDnAPexVCChe0p+db29dk52IoPTx4yRPTPJucTrVe62aTmQDmCYqoAtF3A6
	R1CQoeIdz7sV82gbWvJ5cfiuk0ALVDVwFKJB+QHgdZlwbLl9cJzzZdyNEqtu/Uw/bE
	fRoKXhEgLW06Q==
Authentication-Results:	mta1.srv.hcvlny.cv.net smtp.user=geneglick; auth=pass (LOGIN)
Authentication-Results:	mta1.srv.hcvlny.cv.net x-tls.subject="/C=US/ST=California/L=Mountain View/O=Google LLC/CN=smtp.gmail.com"; auth=pass (cipher=AES128-GCM-SHA256)
X-Content-Analysis:	v=2.3 cv=OIq8IRSB c=1 sm=1 tr=0 a=Dan8yT3GjQgZekbd7xHNVg==:117 a=afefHYAZSVUA:10 a=NDnlM-vojKC16I2nWlQA:9 a=QEXdDO2ut3YA:10 a=UMFyxwUevKS4O1SklBoA:9
X-Gm-Message-State:	AOAM5310ME/vPNEIsA++/YIFSMDuicSNqluFnkpIJceQbfbhmppRQPRa
	0YlrM6rndhwj72ntaq2CXfLeziVFNaDPfhyQVlU=
X-Google-Smtp-Source:	ABdhPJxsTSVvGTG4UxS+/IogYebLqIhB4yMQHCOdaBwSkY19HI2pJ47430bTn6jZ7r2MduQ2bshpVX6Bv+yHjaVOlZk=
X-Received:	by 2002:a25:5709:: with SMTP id l9mr11553782ybb.488.1603587738543;
	Sat, 24 Oct 2020 18:02:18 -0700 (PDT)
MIME-Version:	1.0
From:	"gene glick (geneglick AT optonline DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Sat, 24 Oct 2020 21:04:15 -0400
X-Gmail-Original-Message-ID:	<CAGBFkM1vXVKman8TP0eVE2=T8bPA-ao50xQ+VfFVuyTMaeh9RA AT mail DOT gmail DOT com>
Message-ID:	<CAGBFkM1vXVKman8TP0eVE2=T8bPA-ao50xQ+VfFVuyTMaeh9RA@mail.gmail.com>
Subject:	[geda-user] PCB, 2 parts physically in the same place
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

--00000000000085ac7305b2745d5c
Content-Type: text/plain; charset="UTF-8"

I want to do this on purpose. One part, a 2X16 character display has 10
connections to the PCB. Problem is, they are just holes. It is meant to
have a 10 pin header on the PCB, and then the display gets positioned over
the header and soldered in place. So I placed a 10-pin header in the same
location that the display holes. They line up perfectly but the sizes are
slightly different (a little more or less annulus for example).

I could simply get rid of the 10-pin header (yeah, I think that's the way
to go in the short term), and remember to order it. If it's in the
schematic though, it gets into the BOM...which is good.

Anyway, PCB doesn't allow a couple of things - I cannot make a thermal
connection to the plane on either top or bottom of board. Instead, I made
some traces to the plane. Now DRC reports a problem with too little overlap.

Is this a bug?

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

<div dir=3D"ltr"><div>I want to do this on purpose. One part, a 2X16 charac=
ter display has 10 connections to the PCB. Problem is, they are just holes.=
 It is meant to have a 10 pin header on the PCB, and then the display gets =
positioned over the header and soldered in place. So I placed a 10-pin head=
er in the same location that the display holes. They line up perfectly but =
the sizes are slightly different (a little more or less annulus for example=
).</div><div><br></div><div>I could simply get rid of the 10-pin header (ye=
ah, I think that&#39;s the way to go in the short term), and remember to or=
der it. If it&#39;s in the schematic though, it gets into the BOM...which i=
s good.</div><div><br></div><div>Anyway, PCB doesn&#39;t allow a couple of =
things - I cannot make a thermal connection to the plane on either top or b=
ottom of board. Instead, I made some traces to the plane. Now DRC reports a=
 problem with too little overlap.</div><div><br></div><div>Is this a bug?=
=C2=A0<br></div></div>

--00000000000085ac7305b2745d5c--

- Raw text -