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-transfer-encoding;
	bh=sakK0kJ87PSpwe1CiLqI38exzTMlPBcsE0VmF35v/HY=;
	b=j1/iqd+51R2pmoH+cMpChuaOKEwJ+Ck2M8n5a9ouKpBpWxOFnNHYVfLCoWI0iY6bFD
	ltdMaLnIeOI4PvOM+nxCvdlhVzUTp9xJoUR4MDUggY4Qli+lV0Ve5Uob2hXcjGN++B+J
	RDJAnReBUwvlyzStkMYJJaBTUfbv3ckCXdDqy/cki4hsa1uIMfkC+DnLAKgCkDtEO8GM
	KUEk9X/fz83UCf+Arsf0m+xIqB6Mfe6uxzmy9SwvxW5xyzdOKXWrCmVr39ZdRLdtmL9v
	D4BaCqYo4JZxAOmEn5VX8wjZb9FfETzX7q/YMq2+icxVl5TqwTSYYqCGPHAXCGVnTi/v
	XNLA==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-transfer-encoding;
	bh=sakK0kJ87PSpwe1CiLqI38exzTMlPBcsE0VmF35v/HY=;
	b=RVa4Ws2pM07yjdX4EWBsA2Mdd/PRs4+SfvcGBdcwaM/R8pB3PPE/TLwc4L273awQZl
	0dzgRfX9hF7wJDg4sjEXbldatvWAqZFsZRURKCWssK8/5ZkkUm6lLWcf0NTZRgaphTeL
	Wegx5jBi09G/do7FHLSnrQk0Zq7Hs/FQ9/36hsaBZnbnsaK3ajT53DYLRQqE6Z0zJB+J
	q+7q8CEGN4sE7SHwSQJCAOPdjx7/qUvjHJzBPqpU5swgYGLmwCZykG/4uuUkWtGfzJTT
	rrtPIgxBWhhf/tjAaZOQSNa7Gxo+vKUqThtcHCGUsx08WxPTI5I1hjJNrfaFPnR7dR3s
	CyKw==
X-Gm-Message-State:	AEkooutqF7PaRldmfK/+yLH0N2wyFNpUB+u5MkyxO66tCkAkogQ0il+TXbKb6P2rXASJ0Q==
X-Received:	by 10.194.65.230 with SMTP id a6mr9707245wjt.73.1469343491671;
	Sat, 23 Jul 2016 23:58:11 -0700 (PDT)
Date:	Sun, 24 Jul 2016 08:58:10 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Stay or go? --> Pin mapping
Message-Id:	<20160724085810.bb33c73b9806d2b2e7d78558@gmail.com>
In-Reply-To:	<CAM2RGhQ3abb50gz5JtuzX8QOYf0WU0K9LUb4XhU_AirYDC9eiA@mail.gmail.com>
References:	<98D1C4E4-581D-4A03-94E4-E0330960EADF AT wellesley DOT edu>
	<CAM2RGhS+cHu3g_D21uW-=dB8pUOKcCxEb_+V6LyQhfvi+ep8GQ AT mail DOT gmail DOT com>
	<20160723224811 DOT 2e9f59de5a5898c59003ff85 AT gmail DOT com>
	<CAM2RGhQJozEEoH45xD8fndA+8XyrHJ2r0sW9QAESn6m4Y-qf6Q AT mail DOT gmail DOT com>
	<20160724020053 DOT a598f73dcc0773aa43f2bf6a AT gmail DOT com>
	<CAM2RGhQ3abb50gz5JtuzX8QOYf0WU0K9LUb4XhU_AirYDC9eiA AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> >> > With attribute handling I mean pin mapping, BOM generation and similar which is handled thru attached attributes. I think gschem use non of the attributes itself, just assign and display which work great.
> >>
> >> Yes but to be fair slotting has it's issues.
> >
> > Attribute for pin may be changed from layout in pcb or assigned later in workflow. This is a feedback issue and attribute is not interpreted by gschem.
> >
> > If gschem assign pinnumber which I think slotting mechansim do, it must interpret the attributes and define rules for them. There is a problem because same symbol may be used at different positions for different packages and package may not be known or changed afterwards. I think point to mapping with attribute or embedded would or have solved it. Not all circuits end up on a circuit board and for these package pin numbers may not make any sense and better removed.
> >
> > This pin mapping selection is also a problem for some circuits available in different packages.
> 
> To be fair most of the time when you change the parts symbol for
> something like an fpga there is no good way to make the new extra pins
> fit in the space that was there.

Then changing symbol gschem provide no help, it must fit there it was before. If slots are used for example one pin slot it would be possible. Add more pins, change footprint and it is a matter of getting pin mapping correct.

> Have you ever used a suite that supported changing packages which
> actually handled it correctly more than 90% of the time? I have used a
> few and the 10% when it failed drove me nuts.

Yes you nailed the problem. Pin mapping must be stored somewhere and changed then changing footprint or slot. Mapping may happen then transferring to pcb or not at all if using other back end there no footprint exist.

Gschem is a symbolic graphical representation of the circuit there labels usually are used for the pins although labels in the form of a number may make sense for connector pins. Footprints usually have numbered pins but no labels.

- Raw text -