Quantcast
Viewing all articles
Browse latest Browse all 5525

Can I rebuild the pspice netlist from scratch?

I have a mixed-signal design with both simulated and non-simulated parts (marked with spsnetlist_ignore=true properties) . It was simulating fine, but at some point it stopped working - I would just get "no simulation data for marker" errors on many of the nets. Frustratingly, it would even show me the sort of glitching warnings I'm simulating to find (at times that make sense) but when I ask it to plot those warnings I get the same errors. It seems like it is simulating, but that there is a net name mismatch between the schematic and simulation. Similarly, some nets plot fine when I probe a pin, but not when I probe the wire. If I cut-and-paste a part out and back into the design it sometimes starts working better, sometimes worse.

I've tried re-annotating and re-netlisting with various options, as well as pushing tools > sync netgroup, cutting and pasting large portions of the design, and starting new simulation profiles. The data collection options in the simulation profile are set to collect everything but the internal sub-circuits. All this serves to make it work differently, but not necessarily better or worse - some nets start working, some stop working, whether I can access the information by probing the wire vs. pin changes, etc. It all seems really strange.

Here's a little example from the schematic, grey probes give the "no data" error, black probes work fine:

Image may be NSFW.
Clik here to view.

The whole schematic is like that.

I found this thread online:

https://forum.allaboutcircuits.com/threads/orcad-pspice-probing-issue-no-simulation-data-for-marker.78461/

which indicates I need to start from scratch, but I really hope that's not the case. Certainly there must be a way to just rebuild the pspice netlist from scratch?

Image may be NSFW.
Clik here to view.

Viewing all articles
Browse latest Browse all 5525

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>