"Fred Abse" wrote in message
news:pan.2013.04.16....@invalid.invalid...
> On Tue, 16 Apr 2013 00:57:42 -0700, josephkk wrote:
>> Maximum time step is on the .options card.
> I knew that, it was *minimum* timestep we were discussing.
I thought that the Max Timestep may be a misnomer, and actually means
minimum timestep. The actual directive in LTSpice is as follows:
.tran 0 400m 10m 5u startup uic
Which is defined as:
.tran <Tprint> <Tstop> <Tstart> <Tmaxstep> <start from zero> <skip initial
operating point>
There is a parameter in the transient analysis directive for timestep from
http://ltwiki.org/index.php5?title=Simulation_Command:
.tran <Tstep> <Tstop> [Tstart [dTmax]] [modifiers]
or
.tran <Tstop> [modifiers]
It says:
"Tstep is the plotting increment for the waveforms but is also used as an
initial step-size guess. LTspice uses waveform compression, so this
parameter is of little value and can be omitted or set to zero."
Here is something I found in
http://www.intusoft.com/articles/converg.pdf:
1. Gminsteps (DC Convergence)
Example: .OPTIONS GMINSTEPS=200
The Gminsteps option adjusts the number of Gmin increments
that will be used during the DC analysis. Gmin stepping is
invoked automatically when there is a convergence problem.
Gmin stepping is a new algorithm in SPICE 3 that greatly
improves DC convergence.
I tried various values of GMINSTEPS in LTspice but there seemed to be no
effect on simulation time.
Some other discussions of timestep:
http://www.aboutspice.com/details-208
I have confirmed that the simulation can be slowed down and made more
accurate by reducing the maxstimestep, while setting the Tstep or Tprint
value seems to have little or no effect.
Paul