← Back to team overview

kicad-developers team mailing list archive

Re: [PATCH] SPICE .option confused with .op simulation



Thanks for pointing that. Maybe I'll try to prepare some tests in boost for symulation to test my changes better.

However, I'd like to share my opinion during this occasion. I think that parsing SPICE commands in KiCad is too much effort. Holger Vogt said once that this is very difficult because SPICE language was designed before lex&yacc become popular. I believe optimal way for simulation would be following:
- strive to handle all types of simulations on DIALOG_SIM_SETTINGS tabs
- get rid of user command in schematic sheet
- two additional text fields on simulation options: pre- and post-sim user directives
- passing these user directives directly to output netlist
- pre-sim can be for example specific .options, post-sim could be .meas
either of them can be .control ... .endc
- ideally if all these settings could be saved in file and loaded from menu

Sure, that's a lot of work but hopefully I can help with some of this.

Best regards,

On 23/10/2019 15:39, Seth Hillbrand wrote:
On 2019-10-22 23:35, Maciej Suminski wrote:
Hi Sylwester,

I admit I have not checked your patch in action, but it seems that it
will not accept ".op" command, unless it is followed by a space. Since
".op" does not take any parameters, I presume it is a rare case when one
adds an extra space after the command.


Thanks Orson!  You are right, it was skipping the unpadded .op.  I missed this as the .tran command does print the DC operating point and I was checking in a multi-command circuit.  Good catch.  I've fixed up the command parsing to ensure we pad the command lines.

This does bring up, however, that our simulator does not handle .op well.  It won't probe the values or print them easily.  LTSpice prints the DC Operating Point table for all nets after running in this mode. Not that LTSpice is the model of usability but there may be something to this.


Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp