开云体育

Hello All: .options numdgt=15. caused the plot window to crash at the end of simulation as it was rendering. That plot window crash took LTspice 24.0.12 down with it. I will restart and try again. On

Although that is true for voltages and currents, time values are always saved to the .raw file with double precision.? Time is special in that way. What probably happened here is that the Waveform

Because settings such as those can sometimes help simulations run better.? That is the simple explanation. Cshunt and Gshunt add a bit of capacitance and conductance from every circuit node to

There is nothing inconsistent about it.? You have misunderstood. "10f" always ALWAYS means 10 femto. "10F" always ALWAYS means 10 femto. It never ever means 10 Farads. Now, if you were to write "10

We are. U1 is the integrator with C1 in its feedback path.? For DC, C1 is an open circuit so it is open-loop at DC. Wow.? You got quite different component markers than I did, from the same

I say try it in a circuit. Yes, SPICE ignores case, but it doesn't ignore SPACES in this context. It ignores any character after the space. 10f is 10F is 10 femtofarads: 10 f is 10 F is 10 is 10

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

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]

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.

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.

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

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

No, that is not the case - wrong conclusion.

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

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

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

10f is recognized as 10 femtofarads. -- This email has been checked for viruses by AVG antivirus software. www.avg.com

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]

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.

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