Interesting..

So you got a bad download. Installing takes about 3 minutes, why not just remove and reinstall?

Cheers

Phil Hobbs

joke

Yes, you are..

Jamie

Last time I had a problem with LTspice, I skipped the remove step and went straight to reinstall - it worked fine.

If you've added to the standard.* library files; either rename them or move them to a spare folder or they will be overwritten by the clean install.

Has it escaped into public domain yet?

They are sometimes uploaded to the files area on the LTspice Yahoo group - it would be nice to have a util that can merge a collection of standard.* files into a single big one, preferably without duplication of models.

Well that does seem to be a problem. I managed to figure out how to do that however, updating it over writes the standard files.

I can whipped up a data base insertion tool to re'inject a list of models for those and have it do a check point before over writing a model that maybe in there already..

Most likely there is a way to do this already in scad3, I just haven't found it, yet. If not, no big deal writing the tool to manage collections.

Jamie

I see no reason why I would want to do anything otherwise with it.

well that is what I can do. Like I said, it's a trivial task to finger bang one out :)

Jamie

message

message

EXE

not

or

do

models

that

haven't

collections.

standard.*

One thing is for damn sure. I really need a better selection of parts than comes with stock LTSpice. The complete LT line would be a nice start. Better ability to integrate other manufactuer's publicly available models would be a really good thing.

?-)

The big problem with updating the supplied standard.* files; if you share a schematic you also have to share your updated standard.* file or the recipient gets simulation errors.

It never hurts to make a backup folder and copy the standard.* files from a fresh install, but it would be really handy if there was a public domain util for merging standard.* files so anyone can grow their "inventory".

ge

EXE

not

or

o do

at

ven't

p -

.*

lable

you can just put the .model line in the schematic

a nice variation is ako:

you can make a model a version of another model with only some parameters changed

.model 2N7002bv ako:2N7002 BV=60

cat? ;)

how would you want it to work?

should the new models replace old?

-Lasse

The last couple of times I updated (I do a fresh install over the top, and rarely at that), files have automatically merged, I run a fresh version in a sandbox before I commit to it.

If I share a schematic, I always include significant models.

If LTspice finds an existing installation, it makes a backup of existing files. At least it has done for me, YMMV.

I'm migrating over to Jim's idea of one directory per manufacturer

I avoid using LTspice-supplied models wherever possible, and go to the manufacturer's models. The difference can be significant.

I roll my own behavioral stuff, based on actual measurements and datasheet data.

Running LT's capacitor models against (say) Kemet's own can be revealing.

Remember, LTspice is provided free, in order to enhance, and financed by, Linear's device sales. Not only that, but the supplied models are crafted to run fast in LTspice. Maybe there's a tradeoff.

share

and

in

public

I would gladly do that if i could figure out how to twist scad3's arm to make it tolerate that. That part of the documentation is less than clear to me.

?-)

datasheet

revealing.

by,

crafted

I can't argue with anything you said here. Maybe a little hand holding to use other manufacturer's models would be helpful for me and some others. I am not up to doing my own behavioral models.

?-)