¿ªÔÆÌåÓý

How do I import the LMH6629 spice file into LTSpice IV?


 

Hi all,

I hope you can help with this as I'd like to try out an inspiration I got...

But to do so I need to import the LMH6629 opamp spice file into LTSpice. I've tried to do so using a regular opamp symbol as the model but LTSpice reports an error saying that the instances are not identical. So I reckon the LMH6629 functionality doesn't exactly match LTSpice's regular opamp model.

Could it be that one of you know how to do this? The LMH6629's spice model can be found here:



Best regards,

Jesper


 

--- In LTspice@..., "Jesper" <irpheus@...> wrote:

Hi all,

I hope you can help with this as I'd like to try out an inspiration I got...

But to do so I need to import the LMH6629 opamp spice file into LTSpice. I've tried to do so using a regular opamp symbol as the model but LTSpice reports an error saying that the instances are not identical. So I reckon the LMH6629 functionality doesn't exactly match LTSpice's regular opamp model.

Could it be that one of you know how to do this? The LMH6629's spice model can be found here:



Best regards,

Jesper

Hello Jesper,

You should always look into the model file (.mod) when you
start with a new model.

* PINOUT ORDER +IN -IN +V -V OUT COMP
* PINOUT ORDER 4 3 8 5 7 6
.SUBCKT LMH6629 4 3 8 5 7 6

It has the same pin-order as the "opamp2". The only difference
is the 6th pin. Simply add one pin to the "opamp2" symbol and
set the netlist order of this pin to 6. Save this modified
symbol with a new name in your design folder.

Best regards,
Helmut


 

--- In LTspice@..., "Helmut" <helmutsennewald@...> wrote:



--- In LTspice@..., "Jesper" <irpheus@> wrote:

Hi all,

I hope you can help with this as I'd like to try out an inspiration I got...

But to do so I need to import the LMH6629 opamp spice file into LTSpice. I've tried to do so using a regular opamp symbol as the model but LTSpice reports an error saying that the instances are not identical. So I reckon the LMH6629 functionality doesn't exactly match LTSpice's regular opamp model.

Could it be that one of you know how to do this? The LMH6629's spice model can be found here:



Best regards,

Jesper

Hello Jesper,

You should always look into the model file (.mod) when you
start with a new model.

* PINOUT ORDER +IN -IN +V -V OUT COMP
* PINOUT ORDER 4 3 8 5 7 6
.SUBCKT LMH6629 4 3 8 5 7 6

It has the same pin-order as the "opamp2". The only difference
is the 6th pin. Simply add one pin to the "opamp2" symbol and
set the netlist order of this pin to 6. Save this modified
symbol with a new name in your design folder.

Best regards,
Helmut
Hello Jesper,

There is already an example in our Files-section.

Files > Lib > LMH6629_test.zip



Best regards,
Helmut


 

Hi Helmut,

Thanks for such a swift reply and helpful reply ;-) I'll look into it and see if I can get it to work.

Greetings,

Jesper

--- In LTspice@..., "Helmut" <helmutsennewald@...> wrote:



--- In LTspice@..., "Helmut" <helmutsennewald@> wrote:



--- In LTspice@..., "Jesper" <irpheus@> wrote:

Hi all,

I hope you can help with this as I'd like to try out an inspiration I got...

But to do so I need to import the LMH6629 opamp spice file into LTSpice. I've tried to do so using a regular opamp symbol as the model but LTSpice reports an error saying that the instances are not identical. So I reckon the LMH6629 functionality doesn't exactly match LTSpice's regular opamp model.

Could it be that one of you know how to do this? The LMH6629's spice model can be found here:



Best regards,

Jesper

Hello Jesper,

You should always look into the model file (.mod) when you
start with a new model.

* PINOUT ORDER +IN -IN +V -V OUT COMP
* PINOUT ORDER 4 3 8 5 7 6
.SUBCKT LMH6629 4 3 8 5 7 6

It has the same pin-order as the "opamp2". The only difference
is the 6th pin. Simply add one pin to the "opamp2" symbol and
set the netlist order of this pin to 6. Save this modified
symbol with a new name in your design folder.

Best regards,
Helmut
Hello Jesper,

There is already an example in our Files-section.

Files > Lib > LMH6629_test.zip



Best regards,
Helmut


 

Hi again, Helmut.
I've now tried to download the files from the link you gave but I reckon
I need to step back a bit and understand more basically how I associate
a model (within LTSpice's schematic section) with a symbol - as I guess
that this is the issue.
What I have done is that I:
1. Have added a spice directive .include with the exact file name of the
lmh6629.mod file that I downloaded from this group's file directory.2. I
have saved the lmh6629.mod file in the same directory as the lmh6629.asc
file.3. I have also saved the symbol file xopamp_c1.asy in the same
directory as the lmh6629.asc file4. I have changed the "value" in the
"Component Attribute Editor" dialog to "LMH6629". The "Prefix" is "X".
Still, when I run the simulation I again get an "instance" message
saying: " The instance has fewer connection terminals than the
definition".
Can you help me with which steps I am missing and where/how to set them
up?
Many regards,
Jesper


--- In LTspice@..., "Jesper" wrote:>> Hi Helmut,> > Thanks
for such a swift reply and helpful reply ;-) I'll look into it and see
if I can get it to work.> > Greetings,> > Jesper > > --- In
LTspice@..., "Helmut" wrote:> >> > > > > > --- In
LTspice@..., "Helmut" wrote:> > >> > > > > > > > > --- In
LTspice@..., "Jesper" wrote:> > > >> > > > Hi all,> > > > >
I hope you can help with this as I'd like to try out an
inspiration I got... > > > > > > > > But to do so I need to import the
LMH6629 opamp spice file into LTSpice. I've tried to do so using a
regular opamp symbol as the model but LTSpice reports an error saying
that the instances are not identical. So I reckon the LMH6629
functionality doesn't exactly match LTSpice's regular opamp model.> > >
Could it be that one of you know how to do this? The LMH6629's
spice model can be found here:> > > > > > > >
;
om133&fileType=zip> > > > > > > > Best regards,> > > > > > > > Jesper> >
Hello Jesper,> > > > > > You should always look
into the model file (.mod) when you> > > start with a new model.> > > >
* PINOUT ORDER +IN -IN +V -V OUT COMP> > > * PINOUT ORDER 4 3 8
5 7 6> > > .SUBCKT LMH6629 4 3 8 5 7 6> > > > > > It has the same
pin-order as the "opamp2". The only difference> > > is the 6th pin.
Simply add one pin to the "opamp2" symbol and> > > set the netlist order
of this pin to 6. Save this modified > > > symbol with a new name in
your design folder.> > > > > > Best regards,> > > Helmut> > >> > > >
Hello Jesper,> > > > There is already an example in our Files-section.>
Files > Lib > LMH6629_test.zip> > > >
> > > > Best
regards,> > Helmut


 

--- In LTspice@..., "Jesper" <irpheus@...> wrote:

Hi again, Helmut.
I've now tried to download the files from the link you gave but I reckon
I need to step back a bit and understand more basically how I associate
a model (within LTSpice's schematic section) with a symbol - as I guess
that this is the issue.
What I have done is that I:
1. Have added a spice directive .include with the exact file name of the
lmh6629.mod file that I downloaded from this group's file directory.2. I
have saved the lmh6629.mod file in the same directory as the lmh6629.asc
file.3. I have also saved the symbol file xopamp_c1.asy in the same
directory as the lmh6629.asc file4. I have changed the "value" in the
"Component Attribute Editor" dialog to "LMH6629". The "Prefix" is "X".
Still, when I run the simulation I again get an "instance" message
saying: " The instance has fewer connection terminals than the
definition".
Can you help me with which steps I am missing and where/how to set them
up?
Many regards,
Jesper
Hello Jesper,

Sorry, I had forgotten to include a schematic in my original
file LMH6629_test.zip.

I have now uploaded a new zip-file with two examples.
1. Using symbol LMH6629.asy
2. Using symbol xopamp_c1.asy

The first example has the filename in the symbol attributes.
Thus it doesn't need a .lib or .inc command in the schematic.

Files > Lib > LMH6629_test.zip

Best regards,
Helmut


 

Hi again Helmut,

& thanks for uploading the new files :-) Incidentally, you've actually helped me with a challenge I've had on how to make a tiny circuitry to measure HF noise in DAC/ADC supply rails: With a few modifications it looks as if the circuitry you've drawn up can be used for this ... Thank you!

However, to be honest I still don't understand/know how the "complete" import of a component with a different pin layout and/or a new symbol is done. Might you be able to point me to a description of this - maybe here in this forum - that describes this for a sort of newbie, i.e. in an intuitive way and maybe step by step? I've been using LTSpice for some years now and know how to perform some setups and analyses but sometimes still need to take things step by step.

Also, I am looking for an LTspice/spice model of one of those lamps that are used in oscillator designs to adjust the AGC of the feedback loop. I've searched the files here and found some but am unsure which one to use. I'm considering building an oscillator similar to the one shown in the LT1007 spec sheet (ultrapure sinewave oscillator):



but at a higher frequency (1 - 10 MHz if possible). Would you off the bat know which of the lamp files to use?



Once again, thanks for your previous help, Helmut. And BTW if the simulations LMH6629 simulations are realistic it looks as if it's a quite well-designed component - not easy to make unstable. Impressive actually ...

Greetings,

Jesper

--- In LTspice@..., "Helmut" <helmutsennewald@...> wrote:



--- In LTspice@..., "Jesper" <irpheus@> wrote:

Hi again, Helmut.
I've now tried to download the files from the link you gave but I reckon
I need to step back a bit and understand more basically how I associate
a model (within LTSpice's schematic section) with a symbol - as I guess
that this is the issue.
What I have done is that I:
1. Have added a spice directive .include with the exact file name of the
lmh6629.mod file that I downloaded from this group's file directory.2. I
have saved the lmh6629.mod file in the same directory as the lmh6629.asc
file.3. I have also saved the symbol file xopamp_c1.asy in the same
directory as the lmh6629.asc file4. I have changed the "value" in the
"Component Attribute Editor" dialog to "LMH6629". The "Prefix" is "X".
Still, when I run the simulation I again get an "instance" message
saying: " The instance has fewer connection terminals than the
definition".
Can you help me with which steps I am missing and where/how to set them
up?
Many regards,
Jesper
Hello Jesper,

Sorry, I had forgotten to include a schematic in my original
file LMH6629_test.zip.

I have now uploaded a new zip-file with two examples.
1. Using symbol LMH6629.asy
2. Using symbol xopamp_c1.asy

The first example has the filename in the symbol attributes.
Thus it doesn't need a .lib or .inc command in the schematic.

Files > Lib > LMH6629_test.zip

Best regards,
Helmut


 

Hello Jesper,

However, to be honest I still don't understand/know how the
"complete" import of a component with a different pin layout
and/or a new symbol is done.
My examples are for a universal symbol and a specific symbol.
Please open the symbol files(.asy) with the symbol editor of
LTspice and view the obvious differences in the attributes of
both symbols.

Edit -> Attributes -> Edit Attributes


The netlist order in the pins start from 1 and ends with the
number of pins of the subcircuit definition. The netlist order
will be from 1 to 5 for a .subckt with 5 pins.

Best regards,
Helmut


 

Hi Helmut,

Thanks again. I'll take another look at it and see if this time the penny drops :-)

Greetings,

Jesper

--- In LTspice@..., "Helmut" <helmutsennewald@...> wrote:

Hello Jesper,

However, to be honest I still don't understand/know how the
"complete" import of a component with a different pin layout
and/or a new symbol is done.
My examples are for a universal symbol and a specific symbol.
Please open the symbol files(.asy) with the symbol editor of
LTspice and view the obvious differences in the attributes of
both symbols.

Edit -> Attributes -> Edit Attributes


The netlist order in the pins start from 1 and ends with the
number of pins of the subcircuit definition. The netlist order
will be from 1 to 5 for a .subckt with 5 pins.

Best regards,
Helmut