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=Apu7IUUglCONQHP4XGLd0toNOAfBtPHrmmG0YAhQ0+I=;
	b=IMSNR/TcBZ9FchuXqPvK2krXoIOWhnyGTpWHOyr7eFhFwI7TEjjgidvRH+6Z09CnAU
	zplV4XZgG6Ve3T6xhU5IJ83NU9aMLYT5xtwhXeaDjfnuSIVnGZcjz/idlHmqNOPyydtQ
	wTxoi0Stp/gbg5QCuXFvLlPKtnXwRzjdstuRN+p9Z834q26Zf8SAa506oJpaHe3NCmZI
	NdrQh/zJu+fW5G+GnsaufSgRA3mKcst98xucwAfODN1GCgDGttPW4g8zV2auEfDAC9mI
	nyq37XuTZYiG4lVe9kwVBsOAGKSrZzwcjrnaOzWuMyNDwbTplEElwHOqy8eHsULLrv6S
	yo4Q==
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=Apu7IUUglCONQHP4XGLd0toNOAfBtPHrmmG0YAhQ0+I=;
	b=dKsAKIZoGg3uYg70FzAmLHTzeV4XIrrVo40nNxtXcLuNDTb3biPBctHw0iryyiWFCM
	pllsGpRZqy0LycYwyCd1CyDya80p7O8Wno/W5Adw02LnxakVdepX6UmFZkEG6577qvG1
	c0uno/RBK0FMBk0t0GZnbJWSGEd/PKP6sKPCBvOQ7Ow/77zW6n9zBAG+vCvJq1x8qAqZ
	M+4Q+cE+xH5kpKgc5cMjYGux4JuPDNiD+nZTejFVnNXvkmjSyjS23WuPjZ9qwwLVDi8O
	BOPZp9q6zwWOvQTEU1RKrgUF6N7y5neOg8rZwJisPxuYx0EKgYsEg5Kd17ExPbBRsXD+
	GZNQ==
X-Gm-Message-State:	AKGB3mKZzAosFMkRC9h195OkmS74lbTIXH6q5+HXx/hjBjsDa0e6gaNI
	gn5i7RbaqYF955yGdpoVg0o0Lg==
X-Google-Smtp-Source:	ACJfBotgKYxs4MmVZodbQXZfWhF38knHsiisbIcBsU/1ILrD59vucidMUTffosDjS5rk5slxabp+Ig==
X-Received:	by 10.46.29.215 with SMTP id w84mr3456596lje.78.1515255302526;
	Sat, 06 Jan 2018 08:15:02 -0800 (PST)
Date:	Sat, 6 Jan 2018 17:14:55 +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:	<20180106171455.2518ffeb48c5079339697e0b@gmail.com>
In-Reply-To:	<20180106155314.38132804CECC@turkos.aspodata.se>
References:	<20171226122009 DOT 366BF804CEDE AT turkos DOT aspodata DOT se>
	<alpine DOT DEB DOT 2 DOT 20 DOT 1801022021340 DOT 14184 AT nimbus>
	<20180106155314 DOT 38132804CECC 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

> Ok, I get it and done some testing in http://turkos.aspodata.se/tmp/gEDA/pinnumber/
> 
> So, in a sym file (dcdc_isol.sym), a:
> 
> P 300 200 0 200 1 0 1
> {
> T 275 225 5 6 1 1 0 6 1
> pinnumber=-Vin
> }
> 
> gives the correct net:
> 
> $ fgrep -e -Vin test.net 
> 0V      U1--Vin X1-1 U2--Vin 
> $
> 
> where U1--Vin is matched by pcb to the second "-Vin" (the pins "number")
> in the fp:
> 
>   Pin [   0.000mm   0.000mm    2.000mm   0.500mm   2.400mm   1.000mm "-Vin" "-Vin" "" ]
> 
> giving me the correct ratsnet in test.pcb.
> 
> ///
> 
> That implies that I potentially need two fp for the same thing:
> , one with numbers, if I use numbers in the sym file

I think the pinseq attribute is used to map to footprint pin?

> . one with names, if I use names in the sym file

To use labels on pins in footprint might be a solution to the mapping problem.


Mapping is the only hard thing with schematic symbols otherwise it is simple regardless of type: electric circuit, hydraulic circuit, simulink/xcos style blocks, ...


Nicklas Karlsson

- Raw text -