开云体育

Vlad, That's what I was trying to achieve, perfect. Many thanks Neil

While we're missing points, you forgot to point to where S-parameters for the 2N3904 can be found. Of the thousands of different types of transistors in existence, probably fewer than 1% of them have

On 23/02/2021 06:36, Andy I wrote: > WHS wrote, "There were reports at one time that 2 or more rand() functions were random but very well correlated with each other. Has this been corrected?" > > What

WHS wrote, " There were reports at one time that 2 or more rand() functions were random but very well correlated with each other. Has this been corrected? " What is there to correct? The rand()

There were reports at one time that 2 or more rand() functions were random but very well correlated with each other. Has this been corrected?

Hi Tony, Thanks for the feedback. I am afraid you missed my point. First, I never said I would use s parameters to emulate a non linear aspect of the model. However, the point of the validation

Thank you, Vlad I have switched to the 0V voltage source, and all is working as expected, no matter the source of the model for the ?FET I choose. ? I appreciate the information on when model items

OTOH, we can't talk about Ft without treating it as a linear(ized) amplifying device. Andy

I'd be interested to know whose S-parameter data you've got for 2N3904? Overall, your suggestion isn't worth much because S-parameters only model linear devices. The whole point about SPICE models is

You need to use the numeric order of the pin, i.e. if the subcircuit was defined as: .subckt xxx a b c then using i(r:u1:a) will fail. -- Vlad ______________________ ltspicegoodies.ltwiki.org v2:

Hello Mike, himself, has said that the pin currents are not known before parsing, and since that implies parsing behavioural sources with their expressions, too, it's not possible to use the currents

Hello Neil If I understand correctly, you want something like this: .meas t1 param 6.3m .meas t2 param 7.3m .meas a avg v(x) from t1 to t2 .meas b rms i(v1) from t1 to t2 . . . Alternatively, you can

BB, thanks for the tip on capturing and viewing subcircuit parameters! When I add those 0V sources, I’ll do a side by side comparison with a version that uses the model currents. Appreciate the

Hi Jim, The approach I have taken is to gather the 2 port s parameters for a box full of say 3904. Then use the s data with a waveform arithmetic statement in LTSpice to get ft. As ft is an

If you want to view the .subcircuit values in the waveform viewer, you can (even though you cannot seem to use them in the circuit as you wanted) go to Tools-->Control Panel-->Save Defaults and click

Bad 'black market' parts even fall into the mainstream distribution channels.? You need to know your sources very well. Andy

This is as good an explanation as I could have hoped for. ?I really appreciate your insight on this... it makes sense. ?Perhaps it’s just a missing feature in LTspice, or perhaps it’s by design

You mean like those “grab bags” that can be gotten for a pittance at a swap meet? Got a bunch of those and now they are mixed in with good stock :=(( Wonder where those that are marked with the

And then there is the question of where your distributor got THEIR parts.? These days, some are rejects that fall off the datasheet.? Watch out for that. Andy

I think Helmut's recommendation in this case would be to use the PSpice docs.? Helmut used PSPCREF.pdf which can be downloaded from many places on the net.? Then turn to the chapter on BJTs and read