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=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=QV6rnrX5unOfGypMYR3akhwG0Il7JrsMXGRq4MwrKWo=;
        b=uSQ1ZYlxaCddQsW3OoI+27qUyym29lq7yp2EUkHk79SE1B9dNx0nWftVr/cTCue1ef
         ik+A1Rst9ZB7pqb8lnTkE6RMrvQYTaOa190fKYZxf60pMDST4gyBiwhj0EsbFpdsBq4C
         kdVrPhP7bB+q+MOsMOpwM/PiBohUqPIU/3Q5oGwV+0xrK8YBQ996cYvnHc3oJsEWnNFo
         OFOhi1QWqmnM+hmYGZsLXnRCxRdgJiq3DPp+Bia1/CsePQV+8cod8eKPKvxXhYqfpjoC
         2Ep1LSXkHKBUuX3T4szj969VoAHJvzdlJ1+HJ82p6W8bEqGd/JaMmSDY4QzgCBIvgrVJ
         PMqg==
MIME-Version: 1.0
X-Received: by 10.112.62.133 with SMTP id y5mr250954lbr.120.1440620099687;
 Wed, 26 Aug 2015 13:14:59 -0700 (PDT)
In-Reply-To: <F798CD4A-E566-43E9-842F-F4EE35E49566@noqsi.com>
References: <20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org>
	<55DBA2B7 DOT 1080501 AT ecosensory DOT com>
	<CAHUm0tNAY8TY485-imFoTHJqRha=99bmO_3a9f_jjpWCU4x8Zg AT mail DOT gmail DOT com>
	<CACwWb3COWw41-L8dNw9qhfkYT2wF7=7oC1cEhRbKLV4pHdTMaA AT mail DOT gmail DOT com>
	<55DC31E0 DOT 9050606 AT jump-ing DOT de>
	<CACwWb3CYGx9hyTB5T-v=oCZd=Vs2VAGQ65h9vWhugt2COuVHUQ AT mail DOT gmail DOT com>
	<CAM2RGhQd1KHHmgd2qX5+rNzTDdzqFjbmurF8MFN2RwaE3E7ZTQ AT mail DOT gmail DOT com>
	<20150825215611 DOT 1794b153c4160dddb739b6d3 AT gmail DOT com>
	<55DDCF2E DOT 6070505 AT ecosensory DOT com>
	<6CBA9A3C-526A-4364-9E70-83A910349E14 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1508261843130 DOT 6849 AT lichen>
	<98C29CD9-40F4-4053-92C1-534531CD745F AT noqsi DOT com>
	<CAM2RGhRsUOWb+j24Np2myPDkA9o6L5+KVOrTH=zUJH4XF85zow AT mail DOT gmail DOT com>
	<F798CD4A-E566-43E9-842F-F4EE35E49566 AT noqsi DOT com>
Date: Wed, 26 Aug 2015 16:14:59 -0400
Message-ID: <CAM2RGhTk6KaYK=p_3O_68B9DVGxWAUH+MG+Y=OZMQw=JCYnLoQ@mail.gmail.com>
Subject: Re: [geda-user] netlisting libraries
From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t7QKF4up003345
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

On Wed, Aug 26, 2015 at 3:59 PM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Aug 26, 2015, at 3:31 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> On Wed, Aug 26, 2015 at 1:21 PM, John Doty <jpd AT noqsi DOT com> wrote:
>>>
>>> On Aug 26, 2015, at 12:58 PM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
>>>
>>>> On Wed, 26 Aug 2015, John Doty wrote:
>>>>> The overloading of pinseq is really the only one I’ve found troublesome, so gnet-spice-noqsi gives you other ways to handle slotted devices.
>>>>
>>>> I've never understood the motivation for the SPICE netlist backends to use pinseq= at all.  Is this just a hack to get the unslotted pinnumber?  Or is there some other mechanism involved?
>>>
>>> I believe it’s copied from the Viewlogic architecture. It never worked right there, either.
>>
>> I thought you use pinseq refer to spice models and pinnumber refers to
>> pins on a part as packaged.
>
> Yes, but the problem is that we also use pinseq to define pin mapping for slotting. The package presented to the gnetlist back end for a slotted component has more than one pin with the same pinseq. Which is which? And hidden pins have *no* pinseq. So, for slotted components I usually use pin numbers in spice-prototype attributes.

Slotting is another part of how we implemented light symbols that does
not quite work. Before people think I am re-igniting the heavy vs
light fight it must be said "I like light symbols" the problem is how
it was implemented. It only seems to work for 74xxx series digital
stuff.

>> The part that is screwy is how we pretend
>> that symbols are light (package & footprint agnostic) when changing
>> their footprint changes their pin numbers.
>
> DJ’s database idea has grown on me over the years. Draw light source schematics, forward-annotate reference designators, footprints, pin assignments, part numbers, etc. for the as-built drawings.

I only remember what part of that was supposed to be. I kind of wish
we had more of the blue sky ideas on the wiki so that we can refer
back to them in these moments.

> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com
>
>
>



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/