Is changes Vbe, but it also interacts with Ise and the junction capacitance parameters, so you may have to change those as well. I don't know if there is a simple formulaic way to change Vbe without upsetting the model in other ways.
If you really just want to make your Vbe's agree at some given current, you can change Is, and there's really no ripple effect thru the rest of the model.
In my experience Is affects Ise which will change Hfe behavior at low currents. Not by much though. Unless you are counting on high Hfe accuracy it probably won't be an issue. It could significantly affect Vcesat.
I bought the book as an ebook, the fastest way to get it over here.
I can't thank you enough mr 🙂
My understanding of what I'm doing has trippled from just some skimming through the pages. The hows and whys of the things I get/see when testing idéas in LTSpice are starting to become more clear to me.
It's very very good.
This will no doubt take my humble efforts at designing my own discrete circuits to a higher level. And there's alot of headroom for improvement lol
I am the same, I did find a few small mistakes in the tutorial. maybe it was my initial confusion.
Can offer a few of the circuits that are in the book. Also incorporated ideas that others presented in this forum.
Bought an old Pioneer QX-9900 quad of late to play with. It is a beauty but needs a bit of work. Wanted to sim the old power amp, a bootstrap design that I do not think Bob even considered to cover, due it's poor performance 🙂 Might re-design it, we'll see.
For the models I just lumped all of them into the default file that ltspice uses.
Last edited:
That's good 
I'm sure many will find those files useful. I never seem to delete old simulation files, you never know when you might need one, or to adapt one to prove a point or other.
I'm sure many will find those files useful. I never seem to delete old simulation files, you never know when you might need one, or to adapt one to prove a point or other.
I've got tons of sims for lots of designs, many from this site. like a few of Apex (Mile's) designs
back to 🙂 where is my place on this site for me to dump my whole directory worth of Ltspice?
Would it not be nice to have a place where everyone contributes/puts ltspice models/libraries, designs? and can improve on them with rudimentary version control. Sorry, brought up in a HP culture of organized EE 🙂
back to 🙂 where is my place on this site for me to dump my whole directory worth of Ltspice?
Would it not be nice to have a place where everyone contributes/puts ltspice models/libraries, designs? and can improve on them with rudimentary version control. Sorry, brought up in a HP culture of organized EE 🙂
I don't see why not. The files take up little room when put in a zipped folder. Perhaps an accompanying text file indicating the contents would be useful. Lets say optional...
Are any users of LT XVII on Windows 10 suddenly finding it crashing out or not responding ?
Both my systems (one x86, the other x64) are doing this and I'm suspecting a silent Windows Update could be the culprit. Restoring to a previous disk image does not fix the issue. Restoring to the same disk image but this time with no internet connection available does fix the issue.
Re-establish the connection and LT is broken again. LT IV is not affected on either system.
Both my systems (one x86, the other x64) are doing this and I'm suspecting a silent Windows Update could be the culprit. Restoring to a previous disk image does not fix the issue. Restoring to the same disk image but this time with no internet connection available does fix the issue.
Re-establish the connection and LT is broken again. LT IV is not affected on either system.
LTspice XVII(x64)
Version of Oct/5/2016 09:37:33 US Pacific
Seems to work fine (I not using it daily, I'm still on LT IV)
Windows 10 with latest update's
Version of Oct/5/2016 09:37:33 US Pacific
Seems to work fine (I not using it daily, I'm still on LT IV)
Windows 10 with latest update's
Very very odd. I've just tried it again and still the same. A .op command seems OK, its the transient run that screws up. The only way out of the above screens is to use task manager to close LT.
My second system (old Acer laptop running W10 X86) doesn't give the same broken graphic screens, it just freezes with a 'not responding' message. Again task manager is the only way out.
The x64 install which is used daily was fine until yesterday, the x86 has been OK whenever used (not regularly).
My second system (old Acer laptop running W10 X86) doesn't give the same broken graphic screens, it just freezes with a 'not responding' message. Again task manager is the only way out.
The x64 install which is used daily was fine until yesterday, the x86 has been OK whenever used (not regularly).
On yet another machine, I'm running LTSpice 17 with Win7...no problems there also.
I'm assuming you've already just done a download and over-write of the latest version?
I'm assuming you've already just done a download and over-write of the latest version?
Yes, I tried reinstalling (uninstalled LT first and then re-installed). Exactly the same behaviour.
I take system images daily (and keep month end backups) and these are OK when restored as long as the PC has no internet connection. As soon as it does, then the working restored image then breaks (I'm guessing as W10 phones home and installs something).
Maybe the problem is also related to other software I have installed and in that regards both machines are pretty much identical.
I take system images daily (and keep month end backups) and these are OK when restored as long as the PC has no internet connection. As soon as it does, then the working restored image then breaks (I'm guessing as W10 phones home and installs something).
Maybe the problem is also related to other software I have installed and in that regards both machines are pretty much identical.
I think I've come up with a fix for this, and have proved again by means of system images that all was OK until the 1st December. Something has changed with W10 but just what seems to depend on the exact software configuration of the machines (and maybe such things as graphics card and so on).
I'll give more detail later.
I'll give more detail later.
You should uninstall/remove the drivers for your video card, by using the 'uninstall' option from the control panel first, and then (most likely) use the video-card device properties box to remove any remaining driver(s).
After that, let windows (in the normal update process) find new drivers and see if the problems are gone. If not then repeat same above and install the video-card supplier his drivers (I do not like these in general, all kinds of ad-on's, extras and nasty's (most of the time) get installed together with these manufacturer packages.
^ Thanks 🙂
OK, so I wanted be 100% sure of the facts and so I recovered to my November month end disk image. The problems started late on the 1st December and so the image made on the 30th should be good. I'd done this once already but this time I wanted to take things slowly and see what was what.
These images probably show the issue better than any description. Be sure to look at the system tray and the time and internet connectivity.
1/ I restored the image and made sure I killed the internet connection before Windows could phone home. LT worked perfectly.
2/ I left the PC running and tried LT again. All good.
3 and 4/ I re-establish the internet connection. Windows Update has given no user info that anything has happened at this point, however after a couple of minutes LT is now 'broken.
5/ When I installed LT XVII I made the choice of choosing the combined 32/64bit package. That is why you can see two executable files here, one is x86 and one x64. Curiously on this PC the x86 version appears to still run correctly. The x64 does not.
This is the point I right clicked the executable file and tried Windows own compatibility trouble-shooter. Setting the Windows version to anything but W10 appeared to instantly fix the issue.
6/ After applying a change Windows asks for confirmation that it is OK.
7/ LT XVII now appears to run faultlessly once again.
My 32 bit W10 install also seems to have responded to the same fix even though the symptoms were different. This set up just froze with a 'not responding' message.
Conclusions... I am forced to believe on the evidence that some Windows processhas been altered or updated silently causing the issue. The two PC's affected are pretty much identical in configuration and 3rd party software but years apart in hardware terms.
OK, so I wanted be 100% sure of the facts and so I recovered to my November month end disk image. The problems started late on the 1st December and so the image made on the 30th should be good. I'd done this once already but this time I wanted to take things slowly and see what was what.
These images probably show the issue better than any description. Be sure to look at the system tray and the time and internet connectivity.
1/ I restored the image and made sure I killed the internet connection before Windows could phone home. LT worked perfectly.
2/ I left the PC running and tried LT again. All good.
3 and 4/ I re-establish the internet connection. Windows Update has given no user info that anything has happened at this point, however after a couple of minutes LT is now 'broken.
5/ When I installed LT XVII I made the choice of choosing the combined 32/64bit package. That is why you can see two executable files here, one is x86 and one x64. Curiously on this PC the x86 version appears to still run correctly. The x64 does not.
This is the point I right clicked the executable file and tried Windows own compatibility trouble-shooter. Setting the Windows version to anything but W10 appeared to instantly fix the issue.
6/ After applying a change Windows asks for confirmation that it is OK.
7/ LT XVII now appears to run faultlessly once again.
My 32 bit W10 install also seems to have responded to the same fix even though the symptoms were different. This set up just froze with a 'not responding' message.
Conclusions... I am forced to believe on the evidence that some Windows processhas been altered or updated silently causing the issue. The two PC's affected are pretty much identical in configuration and 3rd party software but years apart in hardware terms.
