开云体育

Thank you for uploading the file, but when I try to open the .zip file I get an message saying "Assert Error (WZTStamp.c@556)" The parameter is incorrect." . Would you be able to re upload the file or if there is a work around for this error as well.?

As far as I can see, there's nothing wrong with the uploaded zip, but I updated the upload with just the .lib file.

Can you normally open zip files in Explorer?

--

开云体育

I have just uploaded the update on the 74LVC1G.lib here:

/g/LTspice/files/Temp/74LVC1G.lib

Thanks for this. However, I just tried the old model library, and no syntax errors are reported in V24.1.4.

Parentheses in the .model statements have always been ignored anyway, so it shouldn't matter whether they are unbalanced. The other "errors" with VCC & VCC3 aren't strictly errors either, because parameters should recurse down the hierarchy provided they are not redefined somewhere. I think we can regard previous versions of V24.1 as being a little overzealous.

As a purist, though, I appreciate the corrections, which I will incorporate in any future versions of the library.

--
Regards
Tony

开云体育

Did you use the MAX44241 model that comes with LTspice?? Or did you download the Macro Model from ADI's website?

?

They are probably not the same.? (I didn't check this, but you could.)? You might find that the model that comes with LTspice, works a little better than the other one.

They're not the same. I have already uploaded the current model file to Files > Temp.

--

开云体育

This is a good example in support of the file management strategy of including all symbols (and models and whatnot) that are not part of the LTspice installation in the same directory (folder) as the schematic which uses/invokes them. Doing so ensures that all files that the simulation needs are available to whichever user (or other entity) is going to use the simulation.

Donald.

开云体育

I had downloaded the MAX44241 Spice model and Ltspice schematic from Analog's website. For some reason I get the following error message. " Analysis: Time step too small; initial timepoint; trouble with u1: desd-instance d:u1:3 " I didn't change anything within the model or schematic itself so I'm not too sure why is occurred. Please note I am limited to use Ltspice XVII and can't update my software to LTspice 24, due to my company not approving that version of the software. I was wondering if there is a work around to get that error to not show up anymore and run without any issues within LTspice XVII.

The MAX44241 model is now supplied with LTspice, as from 02/15/22. Have you been able to update your components since since that date? There is a line in the changelog suggesting this a corrected model, which implies the previous one might have been problematic.

The model supplied with LTspice is different from the one on the ADI website.

I have version LTspiceXVII 17.1.15 and the MAX44241 example circuit runs fine with the current supplied model. I have uploaded this model to Files > Temp as MAX44241.lib.zip. Try that.

--
Regards,
Tony

开云体育

Such errors are difficult to resolve. In this particular case, where an ADI schematic won't run. I suggest a report to ADI's Engineer Zone. It should run in XVII, unless ADI say it won't.

I had downloaded the MAX44241 Spice model and Ltspice schematic from Analog's website. For some reason I get the following error message. " Analysis: Time step too small; initial timepoint; trouble with u1: desd-instance d:u1:3 " I didn't change anything within the model or schematic itself so I'm not too sure why is occurred. Please note I am limited to use Ltspice XVII and can't update my software to LTspice 24, due to my company not approving that version of the software. I was wondering if there is a work around to get that error to not show up anymore and run without any issues within LTspice XVII.

Link:?

From (complete_reference):

Bxxx n1 n2 V=<expression>
Bxxx n1 n2 I=<expression> [Rpar=<value>] *[Cpar=<value>]
+ [[ic=<value>] tripdv=<value>] [tripdt=<value>]
+ [Laplace=<func(s)> [window=] [nfft=<num>] [mtol=<num>]]
* + [[units] Freq=<valuelist> [delay=<value>]] <=================
* + [NoJacob]
* Bxxx n1 n2 R=<expression>
* Bxxx n1 n2 P=<expression> [VprXover=<value>]

-marcel

开云体育

I guess so. LTspice comes with lots of models for them from Schaffner and Würth. Do you have a part number for yours?

F2 > [Contrib] > Schaffner > EMI
F2 > [Contrib] > Wurth > EMC-Components > CommonMode_Chokes

Or you could try to make one from two coupled inductors. It's easier than you probably thought.

Not quite so easy to tune it to exactly fit your table though, but there's usually significant tolerance on EMC chokes, anyway.

开云体育

Yes, as a piece of circuit or a subcircuit. But the data you have is all expressed in series component terms, whereas the circuit needs, at least,? parallel resistance and capacitance elements, which possibly could be calculated from your data. Obviously, the inductor does not have a physical series capacitor. Have you asked the manufacturer for a SPICE (not 'LTspice') model?

is it possible to build a "Frequency dependent common mode inductor" in LTspice?

?

f	Ls	Cs	Rs
[HZ]	[uH]	[pF]	[ohm]
50	2040.3	4966800000	0.11861
100	2023.6	1251600000	0.13833
500	1997.3	50727000	0.47052
1000	1962.3	12905000	1.2977
5000	1636	619260	15.796
10000	1320.2	191850	36.245
50000	710.19	14266	144.23
100000	520.68	4864.9	247.12
500000	212.64	476.5	958.8
1000000	15.536	1631.6	1963.6
5000000	6.5795	154.02	79.92

1. SPICE/LTspice is a discrete time simulator.? There is no continuous time.
2. .MEASURE is a POST-processing step.? All .MEAS commands are processed AFTER the simulation is over and done with.? It does not command the simulator to re-simulate until it finds the exact point where the voltage was 2.00000000000.? It interpolates between the closest simulated points that straddle it.? The chance that one of those simulated points hits 2.00000000000 volts exactly is astronomically small.? It will 'never' happen.