X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Mailer: exmh version 2.8.0 04/21/2012 (debian 1:2.8.0~rc1-2) with nmh-1.5
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: inbox
From: karl AT aspodata DOT se
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] why pinnumber in sym pins?
In-reply-to: <20180106183020.d07a529ba8108dafa4c64e9e@gmail.com>
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> <20180106171455 DOT 2518ffeb48c5079339697e0b AT gmail DOT com> <20180106165242 DOT D5C1A804CEEF AT turkos DOT aspodata DOT se> <20180106183020 DOT d07a529ba8108dafa4c64e9e AT gmail DOT com>
Comments: In-reply-to "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
   message dated "Sat, 06 Jan 2018 18:30:20 +0100."
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Message-Id: <20180106190939.D712A804CEEF@turkos.aspodata.se>
Date: Sat,  6 Jan 2018 20:09:39 +0100 (CET)
X-Virus-Scanned: ClamAV using ClamSMTP
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
Precedence: bulk

Niklas:
...
> I understand the mapping and use gschem and pcb often though. Even
> though current mechanism work I think about if it could be improved.

Ok.

Using some text in the pinnumber attribute works well enough:
like in 

P 300 200 0 200 1 0 1
{
T 275 225 5 6 1 1 0 6 1
pinnumber=-Vin
}

which gives me a sane netlist like:

0V      U1--Vin X1-1 U2--Vin 

What could be improved is that pcb could map the -Vin from the netlist
to this pin in the footprint:

a:  Pin [   0.000mm   0.000mm    2.000mm   0.500mm   2.400mm   1.000mm "-Vin" "1" "" ]

so I don't have the edit it to look like:

b:  Pin [   0.000mm   0.000mm    2.000mm   0.500mm   2.400mm   1.000mm "-Vin" "-Vin" "" ]

I.e., if not fount the "pinnumber" in the "number" field, look at the
"name" field.

Another way to do the same thing is to have two fp, one with pin
definitions like a above, and one like b.

///

What improvement did you think of ?

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57