I am new using Qspice. I am overall amazed about the capabilities of the software, specially regarding the c++/ verilog behavioral blocks.
What I’ve found is that the waveform viewer is very “buggy” and tends to crash. If I do anything while simulating (zoom in, zoom out, add waveforms, etc), will crash 100% of the times. While if the simulation has finished it performs slow but it’s more or less usable, although for long simulations ~200ms sometimes crashes.
This is something happening with my schematics but also with the demos provided by the software. I have tested “PracticalSMPS.qsch” and the same performance is observed. Is there a solution for it? Is anyone facing the same issues?
Just ran a test but cannot observe any buggy symptoms. Did you change anything in that schematic that could trigger a buggy condition? Alternatively, upgrade your trust level to a basic user and upload the schematic that might be causing the issue. Qspice Forum - New User to Basic User (File Upload) - QSPICE - Qorvo Tech Forum
I personally have reported several cases where the waveform viewer crashes. Typically, these reports are sent via email to Mike Engelhardt, which can be found in Qspice > Help > About. My approach is to include the schematic (.qsch) that can replicate the problem and record a short video to demonstrate to Mike what the crash process looks like.
Based on your description, you are running a long simulation. How large is your .qraw data file after the simulation is completed? Is there a possibility that you are working with a file that is up to tens or hundreds of gigabytes in size?
Thank you for your reply. The .qsch file has a size of 58GB after simulation. Does the waveform viewer struggle to process large data files? What I said that happens with the demo file is if I simulate for a longer time and the .qraw data file is large too. If i simulate shorter times, the issue doesn’t happen.
The circuit is quite complex mixing digital and analog with several c++ blocks. The simulation runs quite fast but it’s generating a lot of data. I will try to just save some waveforms and not all the data. Let’s see if it improves the performance.
Just for you to know, by increasing the timestep (less data points being calculated an stored) and saving only the waveforms that I care about, the performance of the waveform viewer is way better.
Maybe it would be interesting to improve the waveform viewer in order to manage all this data more efficiently, since the simulator is capable of calculating it very fast. But I know that it’s something very complex.