开云体育

Inside each .model there will definitely be default values stored somewhere, which could be returned if one is not provided explicitly in the .model statement, so I don't see why this couldn't be done. LTSpice is great for how it handles arbitrary expressions and behavioural devices, so I'm sure it would be possible to do such a thing if the developers wanted to.

Many things are possible. Default parameter values for LTspice, at least, are listed in the Help, so you could create your own default intrinsic models if you wished - put them into the standard.xxx libraries. I think LTspice uses the last same-named model it encounters. In any event, I petty sure they cannot be accessed programmatically internally, although it would straightforward to do externally. Unfortunately, LTspice cannot invoke arbitrary external code. Many years ago, long before its acquisition by ADI, LTspice had features that were used internally by LTC, but not documented or even acknowledged. Some were completely removed after being "discovered", or at least hidden more deeply, similar to the binary format of proprietary models that are supplied, but cannot be read. You need to remember that LTspice is proprietary software. If you want a SPICE that you can customise, Ngspice is open source - you could add features of your own to your heart's content. Similarly, the original SPICE code from Berkeley is public domain and freely available - an "up to date" buildable version for Linux can be found here:

I've no doubt it could be done in LTspice, but unless it's facilitated by one of the other ongoing enhancements to V24.1.x, good luck wishing for it. AFAIK, no one has ever requested it.

At least for now, you're stuck with a workaround.

--
Regards,
Tony