Mail Archives: geda-user/2015/08/26/16:00:03
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.
> 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.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -