Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
OK, I tried it, and well, it¡¯s weird and not as I expected. I stand corrected! Dave Sent: Monday, February 24, 2025 3:23 PM To: [email protected] Subject: EXTERNAL: Re: [LTspice] intuition behind a
By
Bell, Dave
·
#158735
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
NOT if you type ¡°10f¡±! That¡¯s the same as ¡°10F¡±, isn¡¯t it? For time, resistance, etc.10m = 10M <> 10meg or 10Meg, etc. Sent: Monday, February 24, 2025 3:23 PM To: [email protected]
By
Bell, Dave
·
#158734
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
But, if that's the case, can it possibly mean 10 FARADS in ".options cshunt 10f" ? All of the other options default to values that make nearly no difference.
By
Bell, Dave
·
#158733
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
I think you have misunderstood. You can put a 10f (femtofarad) cap in an .ASC by writing that value in the component property pane. Try it: feed a 10f cap via 1meg and the -3dB point is at 16MHz.
By
John Woodgate
·
#158732
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
Farads being the only possible unit for capacitance, there is no need to specify it. -- http://davesrocketworks.com David Schultz "The cheeper the crook, the gaudier the patter." - Sam Spade
By
David Schultz
·
#158731
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
Yes, I agree, on all counts. It means Farads, in lower OR upper case. But in the .options context, it appears to accept 10f as 10 femtofarads. That¡¯s logical, because who would want a 10F parasitic
By
Bell, Dave
·
#158730
·
|
Re: .MEAS Failure
No, that is not the case - wrong conclusion.
By
Tony Casey
·
#158729
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
I think that 10 means 10 farads, 10m means 10 millifarads etc, but, with a space in between, 10 f or 10 F or 10 m means 10 farads and the following letter is disregarded, or throws an error in some
By
John Woodgate
·
#158728
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
In *this case*, I see that. Seems like a bit inconsistent¡ Sent: Monday, February 24, 2025 1:36 PM To: [email protected] Subject: EXTERNAL: Re: [LTspice] intuition behind a solution to crashing time
By
Bell, Dave
·
#158727
·
|
Re: .MEAS Failure
Hello All: .meas TooLow1 FIND V(XSW11:X1:Qc,XSW11:X1:Qe) WHEN V(XSW11:X1:Qc,XSW11:X1:Qe)=2 FALL=1 works and produces; toolow1: v(xsw11:x1:qc,xsw11:x1:qe)=2 at 0.00804696 Zooming in the plot window to
By
eewiz
·
#158726
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
10f is recognized as 10 femtofarads. -- This email has been checked for viruses by AVG antivirus software. www.avg.com
By
John Woodgate
·
#158725
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
Is ¡°10f¡± a special case in the parasitics settings? For a regular cap, it would mean 10 Farads! Sent: Monday, February 24, 2025 12:29 PM To: [email protected] Subject: EXTERNAL: Re: [LTspice]
By
Bell, Dave
·
#158724
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
The following line solved the problem.Is there some manual or intution regarding why these might help? .options cshunt =10f gshunt=10n abstol=10n vntol=1m Thanks.
By
john23
·
#158723
·
|
Re: Monitor simulation percent completion from python
There is no way of knowing how large the .raw file will be.? Indeed, it might not be the same even for similar simulations.? It depends on how many time points LTspice actually used, which is not
By
Andy I
·
#158722
·
|
Re: Initial conditions for inductor current in .TRAN UIC analysis - follow up
Apologize, I just wanted to make sure I understood it correctly :-)
By
Carlo
·
#158721
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
I don't know what's going on here. U1 isn't open-loop. Are we looking at the same .ASC, PID_section_united_AC_separate?? U3 is open-loop at DC. U1 and U2 have unity gain, U4 has 100 times gain at DC.
By
John Woodgate
·
#158720
·
|
Re: Monitor simulation percent completion from python
Thanks Tony, I have a callback function for when the simulation finishes so the user gets notified via email. They are asking for percent completion because they are running simulations that take 3
By
Jeff Kayzerman
·
#158719
·
|
Re: Initial conditions for inductor current in .TRAN UIC analysis - follow up
You appear to be extremely insistent by asking this question *over and over* , as if asking it every few minutes will twist my arm and force me to answer you immediately. I don't work that way. Go
By
Andy I
·
#158718
·
|
Re: .MEAS Failure
Yeah - that is a different problem, caused by misusing operators. Helmut's concern was over the lack of exact equality.? I guess it applied only in specific situations, which did not include this
By
Andy I
·
#158717
·
|
Re: intuition behind a solution to crashing time domain simulation
#Time-step-too-small
Why not? Does expensive silicon imply an equally expensive SPICE model?? Shouldn't every SPICE model ever made, whether for cheap or expensive silicon, not produce time step too small errors?? And
By
Andy I
·
#158716
·
|