Bob Cordell said:
According to my measurements, LT1166 with vertical MOSFETs SF's has major distortion issues at 20k if the internal Gm stage is used. Otherwise it's relatively ok (that is, meeting my expectation which was around 50-100ppm THD20). As I've already mentioned, it was the clipping I had significant issues with.
Good luck and have fun:
.subckt LT1166 1 2 3 4 5 6 7 8
Q4 N001 N005 N002 PN
Q3 N049 N005 3 PN 5
Q1 N003 N007 N004 NP
Q2 N007 N013 3 NP 5
R1 2 N004 200
R2 N002 2 200
Q5 3 N001 4 NP 40
Q6 N002 N001 4 NP
Q7 N005 N008 N006 NP
R3 4 N006 1k
Q8 N008 N008 N009 NP 2
R4 4 N009 500
R5 N008 N012 425
Q9 N010 N008 N011 NP
R6 4 N011 1k
Q10 1 N024 4 NP 20
Q40 3 N003 1 PN 40
Q39 N004 N003 1 PN
Q11 N022 N014 N023 NP
Q12 N017 N014 4 NP
Q13 N014 N015 4 NP
Q14 N015 N015 4 NP
Q15 N019 N008 N021 NP
Q16 1 N048 N001 NP
Q17 N048 N020 N019 PN
R7 4 N024 1.2k
R8 4 N023 160
R9 N022 N025 120
R10 4 N021 1k
R11 N018 5 5k
R12 N019 3 6k
R13 N017 3 1k
Q18 N015 N017 N016 PN
Q19 N014 N018 N016 PN
R28 N020 6 200
Q20 N025 N022 3 PN
Q21 4 N025 N026 PN 10
Q22 N037 N027 N026 NP 10
Q23 N027 N029 3 NP
C3 N018 N014 5p
Q24 N046 N028 N010 NP
Q25 N047 N031 N010 NP
Q26 N032 N034 N033 NP
Q27 4 N032 N003 PN
Q28 N033 N040 N035 PN
R14 3 N031 1k
R15 3 N033 6k
R16 N028 8 5k
R17 N035 1 1k
R18 N036 1 160
R19 N027 N029 120
R20 N030 1 1k
R21 N038 1 10
R22 N045 1 1k
R23 N044 1 1k
R24 N040 1 2k
R25 N041 1 1k
R26 N039 1 1k
R27 N034 7 200
Q29 N047 N047 1 PN
Q30 N046 N047 1 PN
Q31 N031 N046 1 PN
Q32 N029 N046 N036 PN
Q33 N037 N040 N030 PN
Q34 N024 N037 N038 PN
Q35 N016 N040 N045 PN
Q36 N043 N040 N044 PN
Q37 N042 N040 N041 PN
Q38 N013 N040 N039 PN
Q41 4 N042 N040 PN
Q42 N042 N043 N012 NP 10
Q43 N043 N043 N008 NP
C2 N046 N028 5p
C1 N037 N024 20p
R29 N007 N013 200
R30 N005 N049 200
D1 3 N050 DZ
D2 4 N051 DZ
D3 1 N050 DD
D4 3 N051 DD
R31 1 N032 200k
R32 N048 4 200k
R33 N042 N008 10Meg
.model DD D(Is=2.52n Rs=0.568 N=1.752 Cjo=4p M=.4 Tt=20n)
.model DZ D(Is=0.6u Rs=.5 Cjo=150p nbv=5 bv=12 Ibv=1m)
.model NP NPN(BF=125 Cje=.5p Cjc=.5p Rb=500)
.model PN PNP(BF=125 Cje=.5p Cjc=.5p Rb=500)
.ends LT1166
*$
Re: off topic
LOL! When I saw the first picture, I thought it was something from a playground. My first thought was, "Boy, I wouldn't want to be crawling inside that thing if it were hit by lightning!".
estuart said:You don't like my coil, do you? because there's a lot of oxygen inside the hollow windings.
So, that limits its application to only this:
LOL! When I saw the first picture, I thought it was something from a playground. My first thought was, "Boy, I wouldn't want to be crawling inside that thing if it were hit by lightning!".
Bob Cordell said:
I've used PSPICE, where you had to enter a net list in a text file. That sucked. MicroCap has a graphical user interface so you can just draw a schematic. It's a million times better than PSPICE. Plus the post processing was separate in PSPICE. With MicroCap you just push a button and get graphical results.
I downloaded LTSPICE a year or two ago because it was free. I didn't find a single thing about it that was better than MicroCap. While it's not perfect, MicroCap is the best I've used.
MicroCap has a free eval version that is limited to 100 nodes. This is enough to do most audio circuits. The real version cost around $3,000 I think. It may be that LTSPICE doesn't have a circuit-size limitation. That would be the only reason to use it compared to the eval version of MicroCap in my experience.
Charles and Bob, I first got an early version of Microcap about 20 years ago. It worked with my Mac and the company supported it at the time along with PC's. Later, they came up with a better version, BUT they included a physical 'key' with the program, and I could not afford to update at the time. Later, they dropped Mac support entirely.
I first got Intusoft Spice about 15 years ago, hoping to do some simulation. However, I found it to be difficult to use, even with schematic input, like Microcap. I finally gave up.
A few years ago, I got Bspice for my later Mac machines, but I have found it about as difficult as early Spice programs.
I was told about LT Spice, but it will only work in a PC environment. I tried to put in an emulator, but it messed up my Mac operating system and I am still having to do a 'ballet' of physical action every morning in order to get the Mac to work.
I am hoping that the PC that Nelson sent me, which contains both Microcap and LT Spice will be up and running soon. Then, I too, can join in.
I always liked Microcap, and though it is Spice based, it always seems to work for me. It doesn't lock up, like normal Spice does for me. It prompts me better, as well.
Now, I hope that you, Bob (especially) now understand my position on Spice better, and you will not further speculate on my position with it.
I first got Intusoft Spice about 15 years ago, hoping to do some simulation. However, I found it to be difficult to use, even with schematic input, like Microcap. I finally gave up.
A few years ago, I got Bspice for my later Mac machines, but I have found it about as difficult as early Spice programs.
I was told about LT Spice, but it will only work in a PC environment. I tried to put in an emulator, but it messed up my Mac operating system and I am still having to do a 'ballet' of physical action every morning in order to get the Mac to work.
I am hoping that the PC that Nelson sent me, which contains both Microcap and LT Spice will be up and running soon. Then, I too, can join in.
I always liked Microcap, and though it is Spice based, it always seems to work for me. It doesn't lock up, like normal Spice does for me. It prompts me better, as well.
Now, I hope that you, Bob (especially) now understand my position on Spice better, and you will not further speculate on my position with it.
Re: Re: Re: Re: Re: Re: autobias of mosfets
The student version only includes models for a very limited number of devices. However, they are some of the more commonly used parts.
As for the validity of them, Andy_C will tell you that they aren't that great. But NOBODY'S are....
The thing about Micro-Cap is that adding models to the library is a somewhat non-intuitive process. I figured it out once and wrote it down. I only use it once or twice a year and hated re-inventing the wheel. Here it is -- hope it helps someone:
~~~~~~~~~~~~~~~~~~~~
The Component Library (DEMO.CMP) is located in the MicroCap program root directory and cannot be relocated.
- IMPORTANT! Save a copy of the Component Library to the user data directory! Otherwise when you install a new version, your updated Component Library will be overwritten!
The other library and model files can be located at will by using the Files - Paths... command.
There are three steps required to add components to MicroCap so that they can be easily used:
1) Add the part to the Component Library (DEMO.CMP) using the Component Editor (Windows - Component Editor...).
- IMPORTANT! Save a copy of the Component Library to the user data directory!
- Most parts are already listed, but need to be 'activated'.
- Change the Definition from "Null" to the same as listed under Shape.
- Check the box that says "Assign Component Name to MODEL".
- If a new schematic symbol is required (unlikely), use the Shape Editor to add to the Shape Library (STANDARD.SHP).
- IMPORTANT! Save a copy of the Shape Library to the user data directory!
2) Add the model to a library.
- There are two types of part libraries:
.LIB = text file model library containing model statements
.LBR = binary model library
- The Model Editor (File - Open...) is used to edit binary model libraries (.LBR).
To add models to a LIB file, just cut and paste from a .MOD file.
To add models to a LBR file, fill in all the fields for the device.
3) Add the name of the new library to the NOM.LIB file.
- IMPORTANT! Save a copy of NOM.LIB to the user data directory!
- The default libraries and models used by MicroCap are specified by the file NOM.LIB.
- While it is possible to add model statements (.MOD) directly to the NOM.LIB file,
it is preferable to include them in a part library instead. Then the new part library
(e.g., CHAS.LBR) can be saved separately and used with new versions of MicroCap.
Please note that the default paths are specified under File - Paths....
~~~~~~~~~~~~~~~~~~~~
Some of this may be out of date, as I think I made these note during version 6 or 7.
PB2 said:
The student version only includes models for a very limited number of devices. However, they are some of the more commonly used parts.
As for the validity of them, Andy_C will tell you that they aren't that great. But NOBODY'S are....
The thing about Micro-Cap is that adding models to the library is a somewhat non-intuitive process. I figured it out once and wrote it down. I only use it once or twice a year and hated re-inventing the wheel. Here it is -- hope it helps someone:
~~~~~~~~~~~~~~~~~~~~
The Component Library (DEMO.CMP) is located in the MicroCap program root directory and cannot be relocated.
- IMPORTANT! Save a copy of the Component Library to the user data directory! Otherwise when you install a new version, your updated Component Library will be overwritten!
The other library and model files can be located at will by using the Files - Paths... command.
There are three steps required to add components to MicroCap so that they can be easily used:
1) Add the part to the Component Library (DEMO.CMP) using the Component Editor (Windows - Component Editor...).
- IMPORTANT! Save a copy of the Component Library to the user data directory!
- Most parts are already listed, but need to be 'activated'.
- Change the Definition from "Null" to the same as listed under Shape.
- Check the box that says "Assign Component Name to MODEL".
- If a new schematic symbol is required (unlikely), use the Shape Editor to add to the Shape Library (STANDARD.SHP).
- IMPORTANT! Save a copy of the Shape Library to the user data directory!
2) Add the model to a library.
- There are two types of part libraries:
.LIB = text file model library containing model statements
.LBR = binary model library
- The Model Editor (File - Open...) is used to edit binary model libraries (.LBR).
To add models to a LIB file, just cut and paste from a .MOD file.
To add models to a LBR file, fill in all the fields for the device.
3) Add the name of the new library to the NOM.LIB file.
- IMPORTANT! Save a copy of NOM.LIB to the user data directory!
- The default libraries and models used by MicroCap are specified by the file NOM.LIB.
- While it is possible to add model statements (.MOD) directly to the NOM.LIB file,
it is preferable to include them in a part library instead. Then the new part library
(e.g., CHAS.LBR) can be saved separately and used with new versions of MicroCap.
Please note that the default paths are specified under File - Paths....
~~~~~~~~~~~~~~~~~~~~
Some of this may be out of date, as I think I made these note during version 6 or 7.
Bob Cordell said:
Hi Bob,
Although I have a copy of LTspice, I have little experience with it. So I can't give you a satisfactory answer, but I hope Charles Hanson did that already.
A couple of years ago I also played with Multisim. The graphical interface was a horrible experience. As far as I can remember, the most striking bug, sorry "feature", was that it did not recognize the connection between components which were directly tied together. You had to take a "piece of wire", yes, of zero length!, to make the connection effective. Compared to Micro-Cap, it needed about twice the number of actions to capture a schematic. This alone was enough reason to send the package back immediately.
Cheers, Edmond.
Re: Re: Re: Re: Re: Re: Re: autobias of mosfets
Hi Charles,
In stead of adding models to the library, you also can add them to the schematic file itself. Doing this with all nonstandard models ensures the portability between users with different libraries, and, compared to LTspice, you have to deal with just one file.
Cheers, Edmond.
Charles Hansen said:
Hi Charles,
In stead of adding models to the library, you also can add them to the schematic file itself. Doing this with all nonstandard models ensures the portability between users with different libraries, and, compared to LTspice, you have to deal with just one file.
Cheers, Edmond.