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=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=2ueSzoFb1VFERYB58TLdbNfof7vGqjgJoFne0exUmfE=;
	b=s/0rGU2L/Jm7CMGSB0qvmYnRIbhG7YuUCjtwgbM7fiSPYyZ48umiymYqOT9q28MVVe
	b2KHviciV2iJhZwiyE4/lBZw2Xrs1i9aBnG1M+fM5vDLMV4ViZE/OuuUN1bxc6smG7DW
	Xz6VUHejhuTNDN2LRa21NC155YoxT25i4ZU4eWZ2CdiSn+AbhHBMdjLsgdcks9WT0EbU
	+dT8SEQ2qUbNBydsUVRa3ys3gctVSgeXozoTA+/4EOIgwHvuA7o0Vrw27M71NFRPmbEM
	E5LchP51d9HGulRz6wyQOP7I2PE/iUcIvShwbAhwqbBzqYrXIAjd9rSklErKWjjte2xs
	kXfA==
MIME-Version:	1.0
X-Received:	by 10.202.193.214 with SMTP id r205mr13048117oif.63.1423019231168;
	Tue, 03 Feb 2015 19:07:11 -0800 (PST)
In-Reply-To:	<mas0aa$ngv$1@ger.gmane.org>
References:	<C00DE067-87C2-4F44-B225-2EF53B4C22D9 AT sbcglobal DOT net>
	<mamudg$ou4$1 AT ger DOT gmane DOT org>
	<1345A71A-1F70-4FCD-B738-883EA3C833E5 AT sbcglobal DOT net>
	<marhgq$kkl$1 AT ger DOT gmane DOT org>
	<CAOFvGD7VKhSTFEHHpSTUr4yLzP95=y8nTsx_y7WBnyjfZOXyKA AT mail DOT gmail DOT com>
	<mas0aa$ngv$1 AT ger DOT gmane DOT org>
Date:	Tue, 3 Feb 2015 22:07:11 -0500
Message-ID:	<CAOFvGD5_w7zqGzNtY5JEN7tgcamcdZt4Z+ZPTjHgr1s7vdTqNQ@mail.gmail.com>
Subject:	Re: [geda-user] Footprint Generator
From:	Jason White <whitewaterssoftwareinfo AT gmail DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t1437Eto022583
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

How nontrivial would it be to add support for a multi line pin where
the size and clearance of the copper can be defined by layer?

 Perhaps the behavior could be for each semicolon detected after
SFlags the interpreter would look for Layer specifiers which would set
the pad thickness and clearance for each layer. Layers which aren't
specified would fall back to the default value specified in the
"normal" part of the pin statement.

Pin [rX rY Thickness Clearance Mask Drill "Name" "Number" SFlags;
Layer LayerNumber Thickness Clearance ;
Layer LayerNumber Thickness Clearance ;
Layer LayerNumber Thickness Clearance ;
...
]

On Tue, Feb 3, 2015 at 9:38 PM, Kai-Martin Knaak
<knaak AT iqo DOT uni-hannover DOT de> wrote:
> Jason White wrote:
>
>>> That said, I'd love to define this kind of oblate pins in pcb in a
>>> proper way. But it is not possible due to format restrictions.
>>
>> Kai-Martin, can you elaborate on this?
>
> The pin statement of pcb does not know anything about layers.
>     Pin [rX rY Thickness Clearance Mask Drill "Name" "Number" SFlags]
> Its geometry is the same on every copper layer. Its shape in mask is
> derived on the fly with the parameter mask_clearance. The default pin
> shape in pcb is "round" with a hole in the center. This can be changed
> into "square" with a flag. There is no way to make a pin statement refer
> to anything else but these two shapes.
>
> The syntax of the pad statement defines a pad as the outline of a single
> straight line segment:
>     Pad [rX1 rY1 rX2 rY2 Thickness Clearance Mask "Name" "Number" SFlags]
> The first four parameters represent the coordinates of start and end of
> the segment relative to the origin of the footprint.
>
> Pads are restricted to either top or bottom layer. There is no way to put
> pads on inner layers. There is also no way to make asymmetrical pins or
> pads.
>
> ---<)kaimartin(>---
>
> PS: The naming scheme of the pcb manual irritates me time and again. A
> "footprint" or an "element" are not quite the same as in common languages.
> The notion of "solder side", "solder layer" and "component side" coexists
> with "top side" and "bottom side".
>
> --
> Kai-Martin Knaak                                  tel: +49-511-762-2895
> Universität Hannover, Inst. für Quantenoptik      fax: +49-511-762-2211
> Welfengarten 1, 30167 Hannover           http://www.iqo.uni-hannover.de
> GPG key:    http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get
>
>
>



-- 
Jason White

- Raw text -