If there are any qucs (electrical circuit analyzer) experts viewing, here is my problem.
I have compiled qucs-s 0.23 on opensuse leap 15.3. Compilation went fine. All appears to run fine. In setting up the initial tutorial schematic (voltage divider), all goes well. Simulation seems to work but no results. Post simulation dialogue says:
But on the results page, after selecing “Tabular” , a table opens but there are no results shown for selection as is presented in the tutorial. All fields are blank. If I enter a name such as “divider” and click that to the right side, it still has no value associated with “divider” voltage.
Additionally, I tried the qucs 0…23 AppImage package. That again solved the schematic but displayed no results giving the same dialogue as above.
I have also set up qucs 0.19 – windows version into wine on my linux pc. The windows qucs runs the tutorial completely with the results showing up in the "Tabular’ as is shown in the tutorial.
Anyone have an idea of what’s wrong with linux compiled qucs-s 0.23 in displaying results.
That worked. qucs v0.19 worked from the sauerland repo with rpm files installed through yast software. Solved a sample problem and displayed results fine.
Since qucs v0.19 wndows works from wine and qucs also runs from linux, I have to conclude that the problem is with qucs 0.23 posted on their website. Will get on qucs people.
Since qucs v0.19 wndows works from wine and qucs also runs from linux, I have to conclude that the problem is with qucs 0.23 posted on their website. Will get on qucs people.
qucs-s does run and gives results using compilation of qucs-s 0.0.23. There was a change from qucs procedures in going to qucs-s. The tutorials have not been updated though. In qucs-s you need to label each simulation a “Transient” solution rather than a DC solution as in qucs. Even when you wish to run a DC solution. Apparently this is necessary for ngspice to work. Use of ngspice is the big improvement moving from qucs to qucs-s.
Received this info from qucs-s main developer on the github page.