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=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=ungd7DW8FxRlqx1x2FcHatL6rbviJLn4uL/mS5G0bmg=; b=ZLrf67UxrKPnsWGl/uXdGWBKdRXnoz5dLGIy0P3YTKMoa+D6ieL3HVWNn1BEo6Bd50 Rses3/nCsn1kDIvXKRDRBFQoUbN0ig0w7aBqCROfrvwO7Yt0rKRSkfSRLUD1kPz9ApcK nQbSmBTczKgtTOPkz+Llym5E3lhNp/G7HkHF/nyobtpgjORBnyjjs5NKh18xrEOlipvb /G+fZ/RtumR+zfFsCX2T46EfKtE+IKFYL0dzLVcU0mYIjJLaakjdQNZSv/wG8La7E4ry UraYum05C+LtuyepiNFsDhcnHPOxMUitgObctSZOWZIPmoNPbElZi+0UPYwqm9g9qfwy xw9Q== X-Received: by 10.25.20.32 with SMTP id k32mr20992084lfi.58.1452359626718; Sat, 09 Jan 2016 09:13:46 -0800 (PST) Date: Sat, 9 Jan 2016 18:13:45 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] (features: layers stack, padstack/vias) Message-Id: <20160109181345.d16da53419656d547e78dd28@gmail.com> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160106133049 DOT 5A0E9809D79B AT turkos DOT aspodata DOT se> <20160106143629 DOT 4D39D809D79B AT turkos DOT aspodata DOT se> <20160106164022 DOT D0D4E809D79B AT turkos DOT aspodata DOT se> <20160106180912 DOT 42ddf4079d91384f206b7c35 AT gmail DOT com> <20160106191433 DOT 5dc5cb59 AT jive DOT levalinux DOT org> <20160106202817 DOT 56197b2c539d426a1b724c9e AT gmail DOT com> <568E09ED DOT 1080508 AT m0n5t3r DOT info> <568E6354 DOT 80302 AT m0n5t3r DOT info> <20160108002640 DOT 03233b24 AT jive DOT levalinux DOT org> <20160108175259 DOT 127a3f073616758434f7edff AT gmail DOT com> <20160109020345 DOT 1e07cb84 AT jive> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > One of the things I find confusing about pcb is that layers have types. > > That’s not physics. Layers are made of materials. > > > > > Whilst I feel you are probably being pedantic on this point, I actually > agree with you. > > I think you would enjoy reading about the STEP AP210 board stack model. > (Actually, it is called a layered interconnect model). See this for the > basic concepts: > http://www.wikistep.org/index.php/AP210ed2_concept_of_operations > ... > All entirely physics and materials based, _including_ explicitly defining I can see no problem add this http://www.wikistep.org/images/3/37/Stratum.gif to the layer dialog although layer shown on left hand while drawing need to be limited for practical purposes. For ordinary circuit boards all insulation layers usually have exactly the same drawing primitives. I would say drawing primitives on layer "outline" for the most common circuit boards end up on all insulating layers. For an embedded component which I only recently heard about their need to be a cut out in the inner insulating layers. If it where possible to put drawing primitive on insulating layer this could be done. It would probably be better to draw a cut out with a certain height and put the cutout at the layers then using the footprint. The footprint could be placed at any layer facing upwards or downwards with only practical limitations, the manufacturer would probably complain for a component facing inwards on outer layer but the limit would not be with the software. This is probably a bit out but if the functionality to draw on any layer is there it should not be to hard to implement although this may not be the case now. I have started to look at clearance between any net and think about building pin/via/pad from ordinary drawing primitives possible by the old method as a macro for the most common cases. Basically I think about clearance for a line as drawing an enlarged line negative/cutout in polygons for the other nets although other objects have to be saved to the DRC check there instead intersections are calculated. Nicklas Karlsson