Error .print No Dc Analysis Found
Contents |
into a gtkwave tcl script Next message: [free-electronic-lab] ngspice .PRINT I(
Ngspice Example
Also, I cannot specify the name of a circuit component in a .PRINT or .PLOT statement. Only the ngspice tutorial node numbers seem to work. Here is an example: Ohm' Law Vin 1 0 5 R1 0 1 10K .DC Vin 1 5 1 .PRINT DC V(R1) .END ngspice doesn't seem to recognize R1 in the .PRINT statement. I get the following error: $ngspice -b diff.net Circuit: ohm's law Doing analysis at TEMP = 27.000000 and TNOM = 27.000000 Warning: can't parse 'r1': ignored Error: no data saved for D.C. Transfer curve analysis; analysis not run doAnalyses: not found run simulation(s) aborted Error: .print: no dc analysis found. elapsed time since last call: 0.011 seconds. Total elapsed time: 0.011 seconds. Total DRAM available = 2008.300781 MB. DRAM currently available = 423.984375 MB. Total ngspice program size = 18.778320 MB. Resident set size = 732.000 kB. Shared ngspice pages = 551.000 kB. Text (code) pages = 1.958008 MB. Stack = 0 bytes. Library pages = 5.961914 MB. ------------------------------------------------------------------------------------------------- The simulation however works if I replace it with .PRINT DC V(0,1) Secondly, I can't seem to print current. Using .PRINT DC I(R1) or .PRINT DC I(0,1) gives me this error: $ngspice -b diff.net Circuit: ohm's law Doing analysis at TEMP = 27.000000 and TNOM = 27.000000 Warning: can't parse '0#branch': ignored Error: no data saved for D.C. Transfer curve analysis; analysis not run doAnalyses: not found run simulation(s) aborted Error: .print: no dc analysis found. elapsed time since last call: 0.013 seconds. Total elapsed time: 0.013 seconds. Total DRAM available = 2008.300781 MB. DRAM currently available = 423.871094 MB. Total ngspice program size = 18.778320 MB. Resident set size = 733.000 kB. Shared ngspice pages = 551.000 kB. Text (code) pages = 1.958
linux in batch mode. I get an error which says dc analysis not done because doAnalyses not found. .ac et al seem to be OK. Any ideas? Ian Ian Bell, Jan 8, 2004 #1 Advertisements Stuart Brorson Guest Ian Bell <> wrote: : I am having a problem with dc analysis with spice 3f5 under linux in batch : mode. I get an error which says dc analysis not done because doAnalyses : not found. .ac et al seem to be OK. Any ideas? Download tclspice-0.2.15 and try again. Tclspice is the best supported port of SPICE 3f5 to Linux. http://tclspice.sourceforge.net/ Although tclspice has its issues, it does do .dc, .ac, and .tran analyses without any problem. https://lists.fedoraproject.org/pipermail/electronic-lab/2010-September/000942.html It incorporates the command-line SPICE program ngspice, which is probably what you want to use. Stuart Stuart Brorson, Jan 8, 2004 #2 Advertisements Ian Bell Guest Stuart Brorson wrote: > Ian Bell <> wrote: > : I am having a problem with dc analysis with spice 3f5 under linux in > : batch > : mode. I get an error which says dc analysis not done because doAnalyses > : not found. .ac et al seem to be OK. http://www.electronicspoint.com/threads/spice3f5-under-linux.42582/ Any ideas? > > Download tclspice-0.2.15 and try again. Tclspice is the best > supported port of SPICE 3f5 to Linux. > > http://tclspice.sourceforge.net/ > > Although tclspice has its issues, it does do .dc, .ac, and .tran > analyses without any problem. It incorporates the command-line SPICE > program ngspice, which is probably what you want to use. > > Stuart THanks for that. I have downloaded it and will give it a try. Ian -- UKFS Ian Bell, Jan 9, 2004 #3 Stuart Brorson Guest Ian Bell <> wrote: : Stuart Brorson wrote: :> Download tclspice-0.2.15 and try again. Tclspice is the best :> supported port of SPICE 3f5 to Linux. :> :> http://tclspice.sourceforge.net/ :> : THanks for that. I have downloaded it and will give it a try. Let us know how you make out! I am keeping a (long and growing) list of tclspice bugs; I also occasionally submit patches to the keepers of the code, so if you have a problem I would like to hear about it. I won't promise that I'll fix anything, or commit to any bugfix schedule however . . . . :-S Stuart Stuart Brorson, Jan 10, 2004 #4 Ian Bell Guest Stuart Brorson wrote: > Ian Bell <> wrote: > : Stuart Brorson wrote: > :> Download tclspice-0.2.15 and try again. Tclspice is the best > :> supported port of SPICE 3f5 to Linux. > :>
All DC analyses with factory-default settings are expected to converge to the correct solution with near-optimal speed. This means that it is http://cp.literature.agilent.com/litweb/pdf/ads2008/cktsimdc/ads2008/Troubleshooting_a_DC_Simulation.html extremely unlikely that any of the following advanced simulation parameters must be altered: ConvMode ArcMaxStep MaxDeltaV ArcLevelMaxStep MaxIters ArcMinValue MaxStepRatio ArcMaxValue MaxShrinkage LimitingMode NoteAs a result of the improvements made to the DC simulation algorithm, it is extremely unlikely that the factory-default values for the advanced simulation parameters need to be modified. You are strongly encouraged error .print to leave these parameters set to their default values. If you encounter a circuit for which a DC analysis does not converge using the default values, or you find it necessary to change the value of any of these parameters, please contact Agilent EEsof Technical Support. See Defining Advanced Simulation Parameters for details about these parameters. Use error .print no the following checklist to locate and fix problems. For details about specific problems, see the sections that follow. Use the simulator Options to turn on Issue warnings ( GiveAllWarnings=yes ) and increase Maximum number of warnings ( MaxWarnings=10 by default). To set these parameters in ADS, place the Options component on your schematic from the Simulation-DC palette. For details about simulator options, see Using the Simulator Options Component. Read all error and warning messages from the Simulation/Synthesis Messages window and make corrections accordingly. Read all status information from the Status/Summary window (select Show Complete Status Message under Window tab) and make corrections accordingly. Check your setup for common errors (see Common Setup Errors). Loosen the simulation Options parameters for absolute and/or relative simulation tolerances (see Adjusting Tolerance Parameters). Turn on/off the Topology Checker (on by default) using the simulation Options parameters (see Topology Check and Correction). Check if you have created a circuit with no solution (see Impossible Circuits). Check if Imax should be increased (see Mode