开云体育

No, the first very basic mockup was done in a bash script, simply to get an idea how it should work. But anything for the masses has to be multi-platform. I'd not even considered Powershell. I don't

I have a folder named "Components", where I put the basic sims of individual devices. Each one has a folder with the .asc, .sym and model in it. When I want to sim a circuit that usees one of these

Isn't the normal way of doing this to create a 'Project' folder that automatically contains folders for each data type (i.e. each .extension) that can all 'see' each other? Like a PCB design project.

Hmm. interestingly, I happen to be working on a powershell script to do just that (although, I'm guessing yours would probably be designed for linux OS). I imagine, however, that there would have to

I just did a simulation of a simple active filter, to look at distortion of the filtered signal, and after LTspice has closed, it has left a file called 'Filter.imp' in the schematic folder. It's 4097

Yes, I write and tell them sometimes. But my voice isn't loud enough. Anyone that's been here long enough will remember Helmut saying all this over and over again. Another way that this issue could be

Against stupidity, the gods themselves contend in vain. ====================================================================================== Best wishes John Woodgate OOO-Own Opinions Only

I fully agree. It's what I do since you have recommanded it years ago. The only drawback is that one has to copy the necessary model and symbol in a separate operation. It would be nice if copying a

Agreed, and doing that doesn't stop you ALSO having personal library files for symbols and models, which avoids having to remember which schematic folder to look into for a given .ASY and/or .MOD or

If you have those folders, it's because you have added them. They are not in the distribution. I'm also fairly sure you don't mean 2n7002.sym, because LTspice symbol files are .asy. I highly recommend

Personally, that make no sense to me, as normally I select a device on the basis of one of the other parameters, like voltage, Rdson or gate charge. I prefer not to touch the standard libraries in any

I've reported it as a bug. Let's hope they do something about the grid control warning (it is indeed necessary to hide the B-source text in some way when '+' is not supported) Properly showing the

On 02/07/2023 12:53, mhx@... wrote: > The following B source definition (all on one line, it is a mere 600 characters) is no problem in LTspiceIV: > ~~~ > Bxx S_junction_1 0 I=V(n1 ) * 9.3993002816

Hello All

It is a bit better/weirder than I thought. My circuit with the added "+" character to extend the B-source line *did* in fact run. The warning that is reported (by popping up the expanded listing) is

I have uploaded a simple

re:? "The original point in dispute was the existence, or otherwise, of an entry in standard.mos for a 2N7002." No, the original point in dispute was whether one could hit "F2" and type "2N7002" and

On 02/07/2023 13:28, Andy I wrote: > When you hit F2, and type a part name or number, you are *not* looking in your "standard.mos" listing.? You are looking in "lib\sym", which is *not* the same as

marcel, It is a known fact that the line length is limited in LTspice's attribute editor.? That was discovered way back when Mike Engelhardt was still working for ADI or LTC. If I remember right

Tony and eewiz, When you hit F2, and type a part name or number, you are *not* looking in your "standard.mos" listing.? You are looking in "lib\sym", which is *not* the same as "lib\cmp" which is