-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add specific SPICE evaluators / decoders #12
Comments
At the moment SpiceSharpParser is not able to parse PSpice specific netlist. I need to add following features to make it work:
I will work on that but I estimate that I can take at least 2 months of work. Kind regards |
@ewiebe1 I've started to work on that features. |
@ewiebe1 Following features have been implemented:
I will continue to work on ability to parse and run PSpice netlists. Marcin |
Hello Marcin, many thanks for your work! Today, I have made an other test: My code snippet: See attached files. |
@ewiebe1 I will work also on ability to parse ngspice28 netlists. Thank you for examples. Regarding the netlist you posted (MCP651.txt) it's quite close to successful parsing.
|
@ewiebe1 Do you have any other requests regarding SpiceSharpParser? |
I found out today that LTSpice uses also some special features in its SPICE netlists, like "A-Devices". Perhaps the SpiceSharpParser should also be able to parse such special LTSpice netlists ? |
@ewiebe1 |
I agree with @marcin-golebiowski . Supporting these custom models is difficult because they'd have to be reverse-engineered. Instead, it may be better to just roll out custom models. I currently have my hands full with Spice# and Spice#.Behavioral v3, so I don't see this implemented in the near future. |
Please add PSpice specific evaluator / decoder
If you add PSpice specific code, it will result in an error, e.g.:
V_V1 N14847 0
+PULSE 0V 5V 3.67us 40ns 40ns 3.255us 6.51us
V_V2 N14651 0 5Vdc
R_R1 N18055 N14538 2.2k TC=0,0
R_R2 N17129 N14555 2.2k TC=0,0
C_C1 N14538 N14569 1n TC=0,0
C_C2 N14555 N14581 330p TC=0,0
R_R3 N14677 N14651 1k TC=0,0
R_R4 N14677 0 1k TC=0,0
R_R5 N14538 N14569 68k TC=0,0
R_R6 N14555 N14581 120k TC=0,0
C_C3 N14569 N17129 10n TC=0,0
X_U6 N14677 N14538 N14651 0 N14569 MCP651
X_U7 N14677 N14555 N14651 0 N14581 MCP651
C_C4 N14847 N18055 100n TC=0,0
V_V3 M_UN0001 0 AC 0
+SIN 2.5V 2.06V 153600 0 0 0
...
MCP651.txt
The text was updated successfully, but these errors were encountered: