开云体育

Thanks Andy and Tony. Got it and appreciate the replies. All the best, Alan

alan, I don't think you can add more than what LTspice gives you already in those plots.? There is no option to change the "Quantity Plotted" on the right axis, so no, you can't "hack" it to add

Indeed, it is troubling to wonder exactly what is meant by asking when a signal is "< 2V".? That happens continuously, after the signal crosses below 2.0 V.? Surely you would not want the .MEAS

Only for Bode. If you choose the Cartesian format, you can get imaginary. what other options do you want? S-parameters of 1 and 2 port networks are automatically available as plot options if you use

Thanks Tony. Yes, I tried. All I get are selections on GD and phase. For example, in using the s parameter script it would be nice to plot transmission gain s21 and SWR (for which I have a simple

Yes, I did try setting the maximum timestep, and all the other things in the FAQ. I also tried tweaking the circuit (same function, different way of achieving it), but as eewiz has found that just

(This only applies to plots in the frequency domain.) Did you try to change it? If you bring the cursor close to the left axis, its appearance will change to a ruler. You can right-click and you will

Right side of plot window is assigned to phase. Anyway to "hack" and assign right side of plot window to another parameter? Thanks.

While c

I have also found that altering the start time of switching regulators can stop singular matrix (SM), time step (TS) and/or femtosecond crawl issues. The MC34036 switcher invariable causes problems if

Well after a day of fiddling about with the values in my .OPTIONS and different integration methods (including the suggestions in the FAQ), I finally got my circuit modelling with just: .OPTIONS

5pF is not unreasonable for the circuit I'm modelling, but I've changed this value over a wide range trying to model my circuit and the OP might also want to try that; pick a value (eg 0.5pF) and take

On Wed, Feb 26, 2025 at 12:19 AM, Andy wrote: FYI, that is not what I suggested. Leave the Start and Stop (or Left and Right) values alone. Let LTspice figure them out on its own. Change the text in

As of 24.1.4, it is still broken. I tried the original method, which failed, before adding the modification suggested by Matthias. An equally serious issue, IMHO, is that the new method is not

Thank you all for your detail information. I will check later. BR,

One small FYI -- It is not the AKO: syntax that enables .STEP'ing through MOSFETs or any other devices. The one key thing to remember is that you can only .STEP numbers.? As long as your MOSFET

What did you try? And when did you get that error (what were you doing when it happened)? Andy

Did you try some or all of the options listed in the LTspice FAQ (Frequently Asked Questions) file?? Please see the message # 158795 ( /g/LTspice/message/158795 ) that I sent earlier

Or alternative to: .model 1 ako: BSP89 .model 2 ako: BSS145 .STEP param M list 0 1 .param Model Select(M,"1","2") is to use: .STEP param M list 0 1 .param Model Select(M,"BSP89","BSS145")

Did you change your schematic and model references to NOT use the absolute locations? e.g. use ".include bunchOfModels.mod" rather than ".include \Home\Users\MyName\MyLibs\bunchOfModels.mod" A web