开云体育

I have just spent a few hours playing around with the ngspice Simulator in KiCad 7. I am already a fan. Some very initial impressions...

Positive

1. The UI, starting from the same schematic entry tool as KiCad uses, is a winner. There is no comparison at all with LTSpice's UI, which is frankly awful.
2. Fairly short learning curve if you come (as I do) from an LTSpice background
3. Much easier process to integrate third-party models (again, in comparison to LTSpice). I had some potentially show-stopping questions that I was able to resolve by experimenting with the UI and finding how it worked

4. SPICE_LIB_DIR - thank goodness for this

5. Was able to import models from Texas Instruments, Infineon, ONSEMI... and have them actually work in simulations without a fight. Winner.
6. Simulation UI is pretty simple and straightforward for this stage of development. And it does work!
7. Things generally 'do what you expect' - a plus.
8. 'Workbook' concept is nice
9. 'Tune' tool, using a slider to manipulate a simulation component's value, is an absolute winner. What a great tool.
10. Lots and lots of potential here. I went in cold, but will be using this a lot more. Great work KiCad team!

Negative

1. A few niggles with the UI; some small fonts that cannot be read easily
   

Wishes

1. So many, but I fully understand this tool is a work-in-progress (and as I said, great work so far)
2. Would like the ability to place Operating Point labels on the schematic (LTSpice .op directive)
3. Rename/label 'signals'?
4. Cursors, measurement tools etc.

Again, a huge amount of potential, great tool, I am a fan thanks just to a short time experimenting.

Thank you for your impressions. I'm yet to start using the simulator.

Do you know of any python-package like pyltspice which allows to work with e.g. stepped result data nicely?

I'm afraid I don't. I'm not familiar with Python.