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=20161025;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-transfer-encoding;
	bh=NlccDXTiz0vYia5hGhaYZ4MP7gya/jnrohbV79ARHRQ=;
	b=oD/wwHYxZHK+bI1tZqiQb+An0YbGd4VCxPIj7ZJBpnGr07rw3/KU1hhYZqRbK0h2/o
	/SqWlmSodzNTnrD3/wm10gWfM1U2olA76Viw1ClheLYu9dnr5dheuTOk4wzzBlFHU45d
	LfeVp5xOiITj+8jxSQwpQxMMEHbYTp7LVAi9bQUDBjrO6X9XK9u5ctkDfJj49f2q34tj
	D6D4v5gyMILnYzmvzMKRujih8GQTQdST/TYm4W+oxA4IIBjOP1FV1h62w+lYfzacL1tb
	VUfYCVHsCdvQtHSWtjMpSg+CraGVSorYtVYeG4IwYNtcbCxcYcD7QJ9fK55uH5NxSehs
	Ozpw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-transfer-encoding;
	bh=NlccDXTiz0vYia5hGhaYZ4MP7gya/jnrohbV79ARHRQ=;
	b=Uap8gP/eNr9EnrmT7x5uclnBfQyqHN3mpImkqiOKJ4y9jOBN46Hq9xERxW/LtgUBMs
	xeRBh9OsNbk5/aP5BwqzPtwHSUcQxv0lwYy7WCVMwfkQVtYWdKwux4tjg/9y4BoZyfH1
	5H9sAQ9pg8YPgSb/6a++IOEMrK09850GEHrz15MooLeL6JPOfwzgSSpyaCrIsJel+fmS
	IghEElFJ8Bt7KR8VIOjPAUuFEcYk3ih2WZ0XFLRXd+r1T1thdbYNTz/CiS/QiN61HK/t
	4FVhfA5LNVwOPJrO3h5cSid0HzeJmc7xecQshbmMlTPhYF4seshMYM/wn6YssNWnCjzI
	0XYw==
X-Gm-Message-State:	AKGB3mI1vSV+L3NjuvJtOWEJj5aySyyFGqOlQzlOhMvT6oiF2nfunXGe
	/fkzZ7Nkn/80Ub8hqHurvzyq9g==
X-Google-Smtp-Source:	ACJfBoufBDBOes84W44JanrWCq51ajtvQEvUBY4SMj7blonb5bEHBiSwxYfYofPkjEf6vcHiSaxB5A==
X-Received:	by 10.25.81.141 with SMTP id g13mr12753188lfl.58.1514295660284;
	Tue, 26 Dec 2017 05:41:00 -0800 (PST)
Date:	Tue, 26 Dec 2017 14:40:57 +0100
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] why pinnumber in sym pins?
Message-Id:	<20171226144057.9ee596760a7026fd8f4622d0@gmail.com>
In-Reply-To:	<20171226122009.366BF804CEDE@turkos.aspodata.se>
References:	<20171226122009 DOT 366BF804CEDE AT turkos DOT aspodata DOT se>
X-Mailer:	Sylpheed 3.5.1 (GTK+ 2.24.31; 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

On Tue, 26 Dec 2017 13:20:09 +0100 (CET)
karl AT aspodata DOT se wrote:

>  Why must one have a pinnumber attribute for each pin i a sym file:
> http://wiki.geda-project.org/geda:master_attributes_list#pinnumber
> 
> Wouldn't it suffice to have pinseq and pinlabel ?

I think pinlabel would suffice. pinseq is needed for footprint and if I got it correct in cschem they use some kind of mapping mechanism for this so it's not part of the symbol.

> Wouldn't it be useful to allow  to have just a function (pinlabel)
> attached to the pin without knowing which pinnumber it will end up on ?

Yes it would if there is a mapping mechanism.

I think I only use pinlabel fo hierachical drawings. It's hard to distinguish between two pins with same label and different pin numbers. The visible label is essentially a rather good identifier for pin since schematics are read by humans.

Pinlabel as default identifier and pinnumber for the unusual case then there is a need to distinguish between pins with same label might be useful but I do not know about any case.

>  E.g. dc/dc converters with single output usually have four pins
> +/-Vin and +/-Vout in all sorts of packages where the pinnumber (from
> the datasheet) can be anything but 1,2,3,4, but their pin names are
> +/-Vin/Vout. So, it would be nice if one could map sym -> fp with
> just the "pinlabel" (gschem) -> pin "Name" (pcb). But pcb doesn't seem
> to support that idea.

Agree.

> Any suggestions or pointers ?

Look at cschem or write your own mapping mechanism.

> Regards,
> /Karl Hammar

- Raw text -