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=6Kd1pTUxZJbmY2lbFxKN0IZngxMc4oYXBpVAXEr3xbM=;
	b=Jk1T3t/o6QtaZLIPi7M1fIFHtdRT9Ls4+6oxdTg2qsEwv+v12aG03PVUHcVgOUiQkV
	IllyJs1But5lSW/2FXeyDEHjsD58A/fCA06zM1lt9xmj7xWlewgWhNaY9ULcqYXe+d11
	LtNF0GCKQcmgiDDTd4ASRuq9ZUtJGomBPztQ9BNKrcfitJSyTFLZg40Eb17JAmqTK+/T
	Sc/CuQMzwtaucdIxFFmNFY6nBJzarY5Vs/BQgjf/GNftJwqLXrd2U3+GoQ/B/eXzBlyZ
	sK3vd49QB+ow/k3lzWtkzXVchYfxA3PvTsf9KYY4Xcc3H6MrRrrqFA0F0/+KhJV2gil5
	FOaw==
X-Received:	by 10.180.11.37 with SMTP id n5mr17992908wib.20.1445239561543;
	Mon, 19 Oct 2015 00:26:01 -0700 (PDT)
Date:	Mon, 19 Oct 2015 09:25:55 +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] Pin mapping (separate symbols from mappings)
Message-Id:	<20151019092555.46eed4540c2d2044bbeab878@gmail.com>
In-Reply-To:	<201510190242.t9J2gl7w009345@envy.delorie.com>
References:	<20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com>
	<201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com>
	<20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com>
	<36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com>
	<201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com>
	<20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com>
	<BED51F9A-F6FF-4A23-B18B-C2EC8BB9DAB6 AT noqsi DOT com>
	<201510190242 DOT t9J2gl7w009345 AT envy DOT delorie 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

> > One geda-gaf issue is that the fundamental pin ID is
> > refdes/pinnumber, confused a bit by slotting. That would be very
> > hard to change, but I think mapping (original refdes)/(original
> > pinnumber) to (as-built refdes)/(as-built pinnumber) is possible.
> 
> This fails if we switch to symbolic pins, which won't have "original
> pinnumber" any more.  Consider:
> 
> http://www.delorie.com/pcb/symsym.html
> 
> Which gate is "U1/pin-A" ?

Symbol pinnumber will not help either unless there are as many symbols as slots. A mapping between symbol pins and footprint pin number will solve the problem either as is now with pinseq or external mapping. For external mapping there must be a method to uniqely identify each symbol. A method to uniqely identify a symbol is by refdes and slot number, slot number would number the instance of this symbol within the same refdes.

As is now there is pinseq for mapping to footprint but with this solution it is not possible change mapping in the schematic. Value, slot number and footprint may also work as pin mapping selector and by this method it would be possible to store mapping information externally if a different footprint library is used.

I would probably think about if it would be possible to use value, slot number and footprint as a pin mapping selector because this would give a rather natural workflow, pin mapping could wait until layout should be done.


Nicklas Karlsson

- Raw text -