Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Symbols for spice simulation need different pin numbering than used for connecting to footprints #189

Closed
poeschlr opened this issue Jan 20, 2018 · 6 comments
Labels
Enhancement Improves existing symbol in the library

Comments

@poeschlr
Copy link
Collaborator

poeschlr commented Jan 20, 2018

Sadly there is (at the time of writing) no way to define different pin numbers for spice simulation and footprint connection. As ngspice seems to be inflexible with regard to pin numbering we might need to add specialiced symbols for simulation purposes.

Original discussion with more details: KiCad/kicad-library#182

Edit: Ideally this is fixed by introducing a new abstraction layer between symbols and simulation models. But this will have to wait till version 6. (Or even later)

@poeschlr poeschlr added the Enhancement Improves existing symbol in the library label Jan 20, 2018
@stambaughw
Copy link
Contributor

stambaughw commented Jan 20, 2018 via email

@poeschlr
Copy link
Collaborator Author

@astroelectronica have a look at the information provided by @stambaughw. There is a symbol field that allows defining a different pin order for the spice export then used in the symbol.

@astroelectronica
Copy link

@stambaughw With some model files that is not possible because it's encrypted. In other cases, model file have not all pins, i.e., a MOSFET in SOIC-8 package, with several drain or source pins. The model just shows one connection for that.

Passives and semiconductors loss with a subcircuit (.subckt) associated. Circuit reference can't be C, L, Q, D, .... and all them turn to U.

I'm not sure if to modify simulation models is a good idea, because these files are verified by manufacturer.

Thanks.

@stambaughw
Copy link
Contributor

stambaughw commented Jan 21, 2018 via email

@evanshultz
Copy link
Collaborator

@poeschlr
Can this be closed? If so, please close it.

@poeschlr poeschlr closed this as completed Feb 8, 2019
@poeschlr
Copy link
Collaborator Author

poeschlr commented Feb 8, 2019

I think so.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement Improves existing symbol in the library
Projects
None yet
Development

No branches or pull requests

4 participants