X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 173.48.170.196 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_F20DA5C9-D8D0-46BB-9C0D-4C21E0F02428" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [geda-user] why pinnumber in sym pins? Date: Tue, 26 Dec 2017 12:42:46 -0500 References: To: geda-user AT delorie DOT com In-Reply-To: Message-Id: <22B45B52-6B12-4985-A8AF-3010B6F709A4@noqsi.com> X-Mailer: Apple Mail (2.3273) 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 --Apple-Mail=_F20DA5C9-D8D0-46BB-9C0D-4C21E0F02428 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Dec 26, 2017, at 12:03 PM, DJ Delorie wrote: >=20 >=20 > It suffices to have only the minimum needed to describe what you want, > if the netlister knows how to deal with that info ;-) >=20 > simulators use pinseq >=20 Slotting also uses pinseq. This overloading can cause problems. In gnet-spice-noqsi there are several other ways to order pins. You can = put pin numbers in a spice-prototype for package oriented ordering, or = you can use pinlabel in a way that=E2=80=99s compatible with the way = gnetlist flattens hierarchy. These things are very handy when you=E2=80=99= re using the same schematic for layout and simulation. > layout uses pinnumber >=20 > I have a script that uses pinlabel to map to pinnumber depending on > package For big designs, what I really want is the ability to draw generic, = abstract schematics and then forward annotate them into concrete, = as-built schematics. >=20 > etc >=20 John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_F20DA5C9-D8D0-46BB-9C0D-4C21E0F02428 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Dec 26, 2017, at 12:03 PM, DJ Delorie <dj AT delorie DOT com> = wrote:


It suffices to have only the minimum needed to = describe what you want,
if the netlister knows how to deal = with that info ;-)

simulators use pinseq


Slotting also uses pinseq. This overloading can cause = problems.

In gnet-spice-noqsi there = are several other ways to order pins. You can put pin numbers in a = spice-prototype for package oriented ordering, or you can use pinlabel = in a way that=E2=80=99s compatible with the way gnetlist flattens = hierarchy. These things are very handy when you=E2=80=99re using the = same schematic for layout and simulation.

layout uses pinnumber

I have a = script that uses pinlabel to map to pinnumber depending on
package

For big designs, what I really want is the ability to = draw generic, abstract schematics and then forward annotate them into = concrete, as-built schematics.


etc


John Doty              Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_F20DA5C9-D8D0-46BB-9C0D-4C21E0F02428--