Ability to employ manufactures' models for components

[csrabak]

I tried to find about this in the present documentation, and except due a terminology mishap of mine, I did not find anything.

Since the qucs-s approach to employ engines which in their guts use Spice as a lingua franca for circuit simulation, I wonder how easy would it be to implemente and/or document the use of spice models of different manufacturers.

Even some more prosaic models could be useful as the ones exported by Coil 32 , for example, in the evaluation of circuits where the anoying imperfections of the coils make some responses lacking, etc.

Perhaps, due the use of more than a single engine (namely NG Spice, Xyce, and SpiceOpus) the instructions may need to be deferred to the specific engine?

However, I think having qucs-s as an unifying plattform for these chores would be a plus for this project!

--
Cesar Rabak

[ra3xdh]

I tried to find about this in the present documentation, and except due a terminology mishap of mine, I did not find anything.

This manual section explains how to attach a SPICE opamp model to Qucs-S https://qucs-s-help.readthedocs.io/en/latest/SubLib.html#using-manufacturers-component-data-libraries

There exists two devices that may be used for this purpose:

• File components->SPICE netlist
• File components->SpiceLibComp

It's need to kep in mind that SPICE models don't have an unified syntax. And for example LTSpice models may contain some unique syntax constructions that need to be rewritten to use this model with Ngspice. This task cannot be performed automatically.

[csrabak]

Yes I do understand in full these variations.

However, this comment of yours gives rise to another "opportunity": NG Spice has the feature of allowing to choose some compatibility option[s] so to swallow without need to further processing (i.e. IT does the preprocessing/conversion) to some more popular syntaxes, I'll try to look for in the docs if in present qucs-s it is possible to set this options via the variable ngbehavior¹.

Thanks

[1] The full set of available options is in Table 16.2 of present NG Spice manual.

[csrabak]

I'm still learning where best place to post some so small observations, and if convenient, pls move this from this thread.

In the above indicated link, in third paragraph of Libraries Blacklisting the directive in the star phrase has been written as ```*.balcklist````, whereas I assume the correct would have been blacklist.

HTH

[ra3xdh]

I'll try to look for in the docs if in present qucs-s it is possible to set this options via the variable

Qucs-S supports spiceinit scripts. And it's possible to define the compatibility options using the spiceinit. See here for more information: #26 This feature still be not documented.