Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subcircuit name conflicts #1060

Open
tomhajjar opened this issue Nov 13, 2024 · 0 comments
Open

Subcircuit name conflicts #1060

tomhajjar opened this issue Nov 13, 2024 · 0 comments

Comments

@tomhajjar
Copy link

tomhajjar commented Nov 13, 2024

I have a Subcircuit conflict issue that is my fault. I know you always tell me to not use the same name for a Subcircuit schematic as the Spice model but ngspice normally just flags it with a warning. You always say to rename the .SUBCKT in the model. This is not practical in large Spice libraries and if making a Qucs-S library, the subcircuit schematic name should be how you want it to appear in the Library like "AD822" not "AD822x".

  1. Holger pointed out the Subcircuit name conflicts in the netlists I sent him. Holger points to two solutions in the link below. I made "x" versions and and the simulations worked.
    https://sourceforge.net/p/ngspice/discussion/133842/thread/c7329202e1/?limit=25#6184

  2. My question is couldn't Qucs-S use Subcircuit names that don't cause conflicts? I assume the "fatal" issue was I used Spice library instead of Spice netlist. Normally ngspice would flag a warning,

  3. I had some projects fail because I tried to extract a complicated Spice model and all it's subcircuits from a large Library, edit them and make a new individual Spice model that works in Spice netlist. I hope using Spice library instead will solve some of my issues.

  4. You mentioned in SPICE Library device limitation #944 that Spice Library device might get updated to allow making Qucs-S Libraries. This would ease making new Digital Libraries.

MOSFET_thermal_prj.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant