Reply by Ricky March 8, 20232023-03-08
On Wednesday, March 8, 2023 at 6:54:42 PM UTC-5, John S wrote:
> On 3/8/2023 3:00 PM, Ricky wrote: > > On Tuesday, March 7, 2023 at 6:05:15 PM UTC-5, John S wrote: > >> On 3/6/2023 4:21 PM, Ricky wrote: > >>> On Monday, March 6, 2023 at 3:44:39 PM UTC-5, John S wrote: > >>>> On 3/4/2023 1:26 PM, Ricky wrote: > >>>>> On Saturday, March 4, 2023 at 11:18:09 AM UTC-5, John S wrote: > >>>>>> On 3/3/2023 8:34 PM, Ricky wrote: > >>>>>>> On Friday, March 3, 2023 at 7:06:11 AM UTC-5, John S wrote: > >>>>>>>> On 3/2/2023 7:38 PM, Ricky wrote: > >>>>>>>>> On Thursday, March 2, 2023 at 9:18:10 PM UTC-4, John S wrote: > >>>>>>>>>> On 3/2/2023 5:25 PM, Ricky wrote: > >>>>>>>>>>> Is there anyone here who thinks LTspice has a good UI? > >>>>>>>>>>> > >>>>>>>>>>> I've been working with it for a week or so, after not using for over a year. It's very hard to reacclimate to the zoom in and out being backwards from every UI I know under Windows. The Function keys will become familiar again, if I continue using it, but what an uphill climb. > >>>>>>>>>>> > >>>>>>>>>>> I saw in an LTspice post that Mike E. is writing a new simulator. I hope he makes it compatible with the existing models. But I suppose he would not be able to work with the company models that don't have accessible contents. I'm wondering how useful it will be to the engineering community as a whole. There are lots of models you just can't get other than as locked by ADI. I think TI has given up on the idea of TINA being their goto simulator. LTspice just has too much steam on the boiler. > >>>>>>>>>>> > >>>>>>>>>> Which version of LTSpice? > >>>>>>>>> > >>>>>>>>> Did the UI change? I must have missed that. This is 17.0.36 > >>>>>>>>> > >>>>>>>> Yes, it changed from IV to XVII. > >>>>>>>> > >>>>>>>> I don't use 17. > >>>>>>> > >>>>>>> Ok... Are you suggesting the UI has significantly changed between the two lineages??? Are they still updating IV? > >>>>>>> > >>>>>> I'm not sure about all the UI changes > >>>>> > >>>>> So it may not have changed? > >>>>> > >>>> Well, how could I know? I have already stated that I did not continue > >>>> using V17. Have I misinterpreted your question? > >>> > >>> Previously, you replied to my question... > >>> > >>>>> Did the UI change? I must have missed that. This is 17.0.36 > >>>>> > >>>> Yes, it changed from IV to XVII. > >>> > >>> This would imply you know something about it. But apparently not. > >>> > >> No, it implies that I know very little about V17 as mentioned above. If > >> I have not used it how can you ASSUME I know something more about it > >> than I mentioned? Are daft or just practicing to be so? Why are you > >> pressing me for more information than I have? What's wrong with you? > > > > I'm not pressing you for any information. What's wrong with your reading comprehension? I'm simply pointing out, very clearly with a quote, that you stated the UI changed between IV and XVII. If you don't know anything about it, how could you know that it changed? If you do know something that changed, you should be able to talk about it, instead of insisting you know nothing. > What, because I tried it superficially and didn't like it so I never > went further? All I knew is that the version and owner changed. You are > one stupid ass.
Ok, so now you are changing your statement again! You have tried it and there was something you didn't like. Based on your previous statement that the UI changed, I would have to assume what you didn't like was in the UI. But when I ask you what changed in the UI, you get all bent out of shape. Very strange.
> > I don't get you. Which of the words I'm using, do you not understand? > > > > Do you understand now? You said one thing, now you are saying something different. Can you at least acknowledge that? > > > How can anyone understand you with your flawed ability to communicate? I > acknowledge your lack of logic. Feel better? > > Go to hell, asshole.
https://www.pinterest.com/pin/87890630218951567/ -- Rick C. -++ Get 1,000 miles of free Supercharging -++ Tesla referral code - https://ts.la/richard11209
Reply by John S March 8, 20232023-03-08
On 3/8/2023 3:06 PM, Ricky wrote:
> On Tuesday, March 7, 2023 at 6:16:20 PM UTC-5, John S wrote: >> On 3/6/2023 9:20 PM, Ricky wrote: >>> On Monday, March 6, 2023 at 8:44:22 PM UTC-5, Simon S Aysdie wrote: >>>> On Monday, March 6, 2023 at 2:17:14 PM UTC-8, Ricky wrote: >>>>> On Monday, March 6, 2023 at 3:40:06 PM UTC-5, Simon S Aysdie wrote: >>>>>> On Thursday, March 2, 2023 at 3:25:38 PM UTC-8, Ricky wrote: >>>>>>> Is there anyone here who thinks LTspice has a good UI? >>>>>> It's okay. Not bad, for sure. All LTspice does is spice sims, so it doesn't need a lot. Because I've used Mentor means I've had much greater suffering in my life than using LTspice. >>>>>> >>>>>> I think the editor has a lineage somehow aligned with Cohesion Designer. But I am not sure. >>>>>>> I've been working with it for a week or so, after not using for over a year. It's very hard to reacclimate to the zoom in and out being backwards from every UI I know under Windows. The Function keys will become familiar again, if I continue using it, but what an uphill climb. >>>>>> Scroll wheel works the same as other progs for me. (Some other programs need the CTRL button pushed simultaneously with wheel scroll, but the direction is the same.) >>>>> Someone mentioned that the scroll wheel direction is a selection in the control panel, so that is now fixed. But it is still a hurky-jerky mess. Very sensitive to the speed. This results in aberrant zooms of much more speed than expected, while also being very insensitive to slow movements of the scroll wheel. Now, I need to get used to it being like other apps... lol. It doesn't take long to mess up decades of muscle memory. >>>> You probably have a funky mouse. Mine has never been sensitive w/LTspice. I've never changed the default. >>> >>> Nothing to do with the mouse. If it were the mouse, I would see it in every program I use and I would not see it with all the mice I've ever used with LTspice on four machines over the years. The only common element is LTspice. Or maybe it's poltergeist? >>> >>> >>>>>> Alt+backspace is still undo after 20+ years. It isn't documented anymore, I think. It is also F9. Rather odd. But you can change these. See >>>>>> >>>>>> C:\Users\%username%\AppData\Roaming\LTspiceXVII.ini >>>>> Yes, I've found the nearly impossible to view settings table for the keys. Fortunately I make few mistakes, so this one doesn't matter... lol As if! >>>>>>> I saw in an LTspice post that Mike E. is writing a new simulator. I hope he makes it compatible with the existing models. But I suppose he would not be able to work with the company models that don't have accessible contents. I'm wondering how useful it will be to the engineering community as a whole. ... >>>>>> >>>>>> I don't see the point, frankly, unless he's writing one for TI. >>>>>> >>>>>>> ...There are lots of models you just can't get other than as locked by ADI. I think TI has given up on the idea of TINA being their goto simulator. LTspice just has too much steam on the boiler. >>>>>> >>>>>> TI loses SMPS business because ADI/Linear have a simulator and fast SMPS sim models. I mean, that was the whole point. It was first called "SwitcherCAD." >>>>> Yes, and TI tried with their own. But LTspice has a lot of inertia. I believe it is used in schools a lot. >>>> TI "didn't try." Tina was always a joke. Just terrible. The PSpice version they are now trying to pawn is a crippled version, like the old EDU version of PSpice was. LTspice is not crippled. You can put as many parts in there and do as large a sim as your time and memory allow. >>>> >>>> LTspice should be used it schools because it is free. Just like they should use Octave instead of matlab. I am always shocked when talking to recent graduates that their Profs had them using the EDU version of PSpice. Crazy. >>>>> >>>>> Right now I'm fighting the PWL format. I need to measure the spectrum of an IRIG signal. The only way I can think to generate a realistic one is to use a PWL file to control the amplitude of a 1kHz sine wave. I expect there's a feature somewhere that lets you do this with some "simple" feature, but it's faster to work with what you know, than to always be trying to learn new things about LTspice. I don't use it that often and it's hard to remember the arcane details of how to use this tool. It would seem Mike didn't really consider users who are not professional simulator writers. Imagine if cars were made this way! But it works, mostly. We'll see how much more time I have to spend on getting the spectrum of this signal. >>>> I'm no expert either. I'm not sure if there is a more elegant way. Sorry. I haven't heard the term "IRIG signal" since I worked for Symmetricom. You can use behavioral elements to modulate--I made an ideal multiplier. But it is the same Q: where does the modulated signal come in to drive the multiplier? >>> >>> I thought Symmetricom made equipment that used the IRIG time code. I believe I used info from their web site back when I initially designed this unit in 2008. Yep, Google finds all sorts of IRIG gear with the name Symmetricom. Seems they were bought by Microsemi since then. >>> >>> >>>> Your complaint is largely the same for every professional tool. None are easy to figure out if use is infrequent. That's the way it always goes. >>> >>> No, there are many tools that have good user interfaces and are easy to pick up again with infrequent use. >>> >>> >>>> LTspice is a bit less documented and there is no paid support. But it is free. Because it is free there is a massive user group, informal support, and other user documentation (including nice utoob vids). You can take this tool with you from one employer to the next. While it is owned by ADI, it is essentially non-proprietary from the user's perspective. That is worth a lot. I have library parts I made a couple of decades ago that are still in my library. >>> >>> Yes, LTspice has many advantages, but the UI is not one of them. >> Why is it that you have so much more trouble with it than others? Your >> attitude, maybe? Are you one of those people who expect everything to be >> handed to them on the proverbial silver platter? Grow up! > > I don't expect anything, other than a civil tone in a discussion. You seem to be very frustrated that I'm not conforming to your ideas of appreciation of a tool. I don't believe that we should never speak ill of free tools. If the world were mute about crap software, it would never get any better. > > Sorry if I offend your fascist vies of software.
Well, here we agree. You are sorry.
> >>>>> Then tomorrow I'll find where someone already did this. >>>> You complain a lot about something very powerful, ubiquitous, and free. >>> >>> There's no small number of threads in this group that are complaining about something technical, in addition to the many threads that are just complaining about something. That is how we communicate problems and some people are happy to discuss the problems, with the hope of finding a solution. That's what I'm looking for. Are you trying to help? > > I see you ignored this. But that's expected in an ad hominem attack. I'm sorry you aren't mature enough to have a reasonable discussion of a tool. I guess some people get too emotional about inanimate things and software. >
If you are sorry, which was addressed above, then why carry on with the conversation? I don't get emotional about tools. I get emotional about people who bait others to get their jollies, like yourself. That is all you're doing in this conversation. Trolling. Get lost, D.H. -- Dogs make me happy. Humans make my head hurt.
Reply by John S March 8, 20232023-03-08
On 3/8/2023 3:00 PM, Ricky wrote:
> On Tuesday, March 7, 2023 at 6:05:15 PM UTC-5, John S wrote: >> On 3/6/2023 4:21 PM, Ricky wrote: >>> On Monday, March 6, 2023 at 3:44:39 PM UTC-5, John S wrote: >>>> On 3/4/2023 1:26 PM, Ricky wrote: >>>>> On Saturday, March 4, 2023 at 11:18:09 AM UTC-5, John S wrote: >>>>>> On 3/3/2023 8:34 PM, Ricky wrote: >>>>>>> On Friday, March 3, 2023 at 7:06:11 AM UTC-5, John S wrote: >>>>>>>> On 3/2/2023 7:38 PM, Ricky wrote: >>>>>>>>> On Thursday, March 2, 2023 at 9:18:10 PM UTC-4, John S wrote: >>>>>>>>>> On 3/2/2023 5:25 PM, Ricky wrote: >>>>>>>>>>> Is there anyone here who thinks LTspice has a good UI? >>>>>>>>>>> >>>>>>>>>>> I've been working with it for a week or so, after not using for over a year. It's very hard to reacclimate to the zoom in and out being backwards from every UI I know under Windows. The Function keys will become familiar again, if I continue using it, but what an uphill climb. >>>>>>>>>>> >>>>>>>>>>> I saw in an LTspice post that Mike E. is writing a new simulator. I hope he makes it compatible with the existing models. But I suppose he would not be able to work with the company models that don't have accessible contents. I'm wondering how useful it will be to the engineering community as a whole. There are lots of models you just can't get other than as locked by ADI. I think TI has given up on the idea of TINA being their goto simulator. LTspice just has too much steam on the boiler. >>>>>>>>>>> >>>>>>>>>> Which version of LTSpice? >>>>>>>>> >>>>>>>>> Did the UI change? I must have missed that. This is 17.0.36 >>>>>>>>> >>>>>>>> Yes, it changed from IV to XVII. >>>>>>>> >>>>>>>> I don't use 17. >>>>>>> >>>>>>> Ok... Are you suggesting the UI has significantly changed between the two lineages??? Are they still updating IV? >>>>>>> >>>>>> I'm not sure about all the UI changes >>>>> >>>>> So it may not have changed? >>>>> >>>> Well, how could I know? I have already stated that I did not continue >>>> using V17. Have I misinterpreted your question? >>> >>> Previously, you replied to my question... >>> >>>>> Did the UI change? I must have missed that. This is 17.0.36 >>>>> >>>> Yes, it changed from IV to XVII. >>> >>> This would imply you know something about it. But apparently not. >>> >> No, it implies that I know very little about V17 as mentioned above. If >> I have not used it how can you ASSUME I know something more about it >> than I mentioned? Are daft or just practicing to be so? Why are you >> pressing me for more information than I have? What's wrong with you? > > I'm not pressing you for any information. What's wrong with your reading comprehension? I'm simply pointing out, very clearly with a quote, that you stated the UI changed between IV and XVII. If you don't know anything about it, how could you know that it changed? If you do know something that changed, you should be able to talk about it, instead of insisting you know nothing.
What, because I tried it superficially and didn't like it so I never went further? All I knew is that the version and owner changed. You are one stupid ass.
> I don't get you. Which of the words I'm using, do you not understand? > > Do you understand now? You said one thing, now you are saying something different. Can you at least acknowledge that? >
How can anyone understand you with your flawed ability to communicate? I acknowledge your lack of logic. Feel better? Go to hell, asshole. -- Dogs make me happy. Humans make my head hurt.
Reply by John Larkin March 8, 20232023-03-08
On Wed, 8 Mar 2023 14:34:33 -0500, Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote:

>On 2023-03-08 12:59, John Larkin wrote: >> On Wed, 8 Mar 2023 11:23:50 -0500, Phil Hobbs >> <pcdhSpamMeSenseless@electrooptical.net> wrote: >> >>> On 2023-03-08 10:47, John Larkin wrote: >>>> On Tue, 7 Mar 2023 22:15:32 -0500, Phil Hobbs >>>> <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>> >>>>> >>>>> A bunch of my stuff wouldn't budge off the peg with those >>>>> settings. If you already know what it should look like, why >>>>> simulate? >>>> >>>> To play with ideas fast day or night, and to get the parts >>>> values right. >>> >>> I've been known to dork frequency compensation that way too, and to >>> look at tolerances for filters. >> >> Right. Any interesting control loop is nonlinear. >> >>> >>> The last thing I designed by poking at in SPICE was a collapsible >>> BJT cascode, where the top transistor had to take a bunch of >>> voltage. When the bottom transistor turned on, the top one >>> saturated, pulling down its relatively high-Z base bias string, so >>> the low level was just the sum of the V_CE(sat)s. >>> >>> I knew that part would work, but needed to figure out what the >>> turn-off transient would look like. The answer was, "Nothing too >>> pretty, but good enough for government work." It didn't look like >>> the top transistor would reliably come out of saturation fast >>> enough to avoid blowing up the bottom one, but a zener on its base >>> solved that. >>> >>>> It's often easier to sim, say, a voltage divider than to do a lot >>>> of math. >>> >>> Our ideas of "a lot of math" are a bit different, but doing that is >>> no worse than using a calculator. ;) (I try to keep in practice >>> doing mental arithmetic, because it makes me a much better >>> troubleshooter.) >> >> A non-trivial voltage divider, with more than two resistors, can be >> a pain to work out with a calculator, especially using the parts you >> already have in stock. >> >> And Spice sims, with comments, are easy to save in a design notes >> folder. > >Yup. They go in our git repos too (one repo per project). > >> >> I do a lot of mental arithmetic, but it's analog computing, >> guesswork and not manipulating digits in my head. I usually come in >> around 5 or 10% accuracy, which is handy enough in most cases. > > >I like to make it a game. It's memory more than anything--in 1 Hz, 3 uA >of photocurrent has 1 pA shot noise; for Johnson, 60.4 ohms has 1 nV and > 16k has 1 pA. > >Going up and down decibels is fun too: 1 dB is 12% voltage and 25% >power, pi = 10 dB (voltage), and so 2 pi = 16 dB. A noise contribution >that's 6 dB down raises the floor by 1 dB, and it goes down linearly (in >dB) for lower noise. > >> Doing this at a whiteboard, in a meeting, seems to annoy some people. >> This used to be called "Lightning Empiricism"; see Williams 1991. > >Whiteboards are great fun, when combined with an interesting problem and >one-to-three smart and good-natured colleagues. (And possibly a pitcher >of beer.) >
Heresy. Whiteboards run on chocolate.
Reply by Ricky March 8, 20232023-03-08
On Tuesday, March 7, 2023 at 6:16:20&#8239;PM UTC-5, John S wrote:
> On 3/6/2023 9:20 PM, Ricky wrote: > > On Monday, March 6, 2023 at 8:44:22&#8239;PM UTC-5, Simon S Aysdie wrote: > >> On Monday, March 6, 2023 at 2:17:14&#8239;PM UTC-8, Ricky wrote: > >>> On Monday, March 6, 2023 at 3:40:06&#8239;PM UTC-5, Simon S Aysdie wrote: > >>>> On Thursday, March 2, 2023 at 3:25:38&#8239;PM UTC-8, Ricky wrote: > >>>>> Is there anyone here who thinks LTspice has a good UI? > >>>> It's okay. Not bad, for sure. All LTspice does is spice sims, so it doesn't need a lot. Because I've used Mentor means I've had much greater suffering in my life than using LTspice. > >>>> > >>>> I think the editor has a lineage somehow aligned with Cohesion Designer. But I am not sure. > >>>>> I've been working with it for a week or so, after not using for over a year. It's very hard to reacclimate to the zoom in and out being backwards from every UI I know under Windows. The Function keys will become familiar again, if I continue using it, but what an uphill climb. > >>>> Scroll wheel works the same as other progs for me. (Some other programs need the CTRL button pushed simultaneously with wheel scroll, but the direction is the same.) > >>> Someone mentioned that the scroll wheel direction is a selection in the control panel, so that is now fixed. But it is still a hurky-jerky mess. Very sensitive to the speed. This results in aberrant zooms of much more speed than expected, while also being very insensitive to slow movements of the scroll wheel. Now, I need to get used to it being like other apps... lol. It doesn't take long to mess up decades of muscle memory. > >> You probably have a funky mouse. Mine has never been sensitive w/LTspice. I've never changed the default. > > > > Nothing to do with the mouse. If it were the mouse, I would see it in every program I use and I would not see it with all the mice I've ever used with LTspice on four machines over the years. The only common element is LTspice. Or maybe it's poltergeist? > > > > > >>>> Alt+backspace is still undo after 20+ years. It isn't documented anymore, I think. It is also F9. Rather odd. But you can change these. See > >>>> > >>>> C:\Users\%username%\AppData\Roaming\LTspiceXVII.ini > >>> Yes, I've found the nearly impossible to view settings table for the keys. Fortunately I make few mistakes, so this one doesn't matter... lol As if! > >>>>> I saw in an LTspice post that Mike E. is writing a new simulator. I hope he makes it compatible with the existing models. But I suppose he would not be able to work with the company models that don't have accessible contents. I'm wondering how useful it will be to the engineering community as a whole. ... > >>>> > >>>> I don't see the point, frankly, unless he's writing one for TI. > >>>> > >>>>> ...There are lots of models you just can't get other than as locked by ADI. I think TI has given up on the idea of TINA being their goto simulator. LTspice just has too much steam on the boiler. > >>>> > >>>> TI loses SMPS business because ADI/Linear have a simulator and fast SMPS sim models. I mean, that was the whole point. It was first called "SwitcherCAD." > >>> Yes, and TI tried with their own. But LTspice has a lot of inertia. I believe it is used in schools a lot. > >> TI "didn't try." Tina was always a joke. Just terrible. The PSpice version they are now trying to pawn is a crippled version, like the old EDU version of PSpice was. LTspice is not crippled. You can put as many parts in there and do as large a sim as your time and memory allow. > >> > >> LTspice should be used it schools because it is free. Just like they should use Octave instead of matlab. I am always shocked when talking to recent graduates that their Profs had them using the EDU version of PSpice. Crazy. > >>> > >>> Right now I'm fighting the PWL format. I need to measure the spectrum of an IRIG signal. The only way I can think to generate a realistic one is to use a PWL file to control the amplitude of a 1kHz sine wave. I expect there's a feature somewhere that lets you do this with some "simple" feature, but it's faster to work with what you know, than to always be trying to learn new things about LTspice. I don't use it that often and it's hard to remember the arcane details of how to use this tool. It would seem Mike didn't really consider users who are not professional simulator writers. Imagine if cars were made this way! But it works, mostly. We'll see how much more time I have to spend on getting the spectrum of this signal. > >> I'm no expert either. I'm not sure if there is a more elegant way. Sorry. I haven't heard the term "IRIG signal" since I worked for Symmetricom. You can use behavioral elements to modulate--I made an ideal multiplier. But it is the same Q: where does the modulated signal come in to drive the multiplier? > > > > I thought Symmetricom made equipment that used the IRIG time code. I believe I used info from their web site back when I initially designed this unit in 2008. Yep, Google finds all sorts of IRIG gear with the name Symmetricom. Seems they were bought by Microsemi since then. > > > > > >> Your complaint is largely the same for every professional tool. None are easy to figure out if use is infrequent. That's the way it always goes. > > > > No, there are many tools that have good user interfaces and are easy to pick up again with infrequent use. > > > > > >> LTspice is a bit less documented and there is no paid support. But it is free. Because it is free there is a massive user group, informal support, and other user documentation (including nice utoob vids). You can take this tool with you from one employer to the next. While it is owned by ADI, it is essentially non-proprietary from the user's perspective. That is worth a lot. I have library parts I made a couple of decades ago that are still in my library. > > > > Yes, LTspice has many advantages, but the UI is not one of them. > Why is it that you have so much more trouble with it than others? Your > attitude, maybe? Are you one of those people who expect everything to be > handed to them on the proverbial silver platter? Grow up!
I don't expect anything, other than a civil tone in a discussion. You seem to be very frustrated that I'm not conforming to your ideas of appreciation of a tool. I don't believe that we should never speak ill of free tools. If the world were mute about crap software, it would never get any better. Sorry if I offend your fascist vies of software.
> >>> Then tomorrow I'll find where someone already did this. > >> You complain a lot about something very powerful, ubiquitous, and free. > > > > There's no small number of threads in this group that are complaining about something technical, in addition to the many threads that are just complaining about something. That is how we communicate problems and some people are happy to discuss the problems, with the hope of finding a solution. That's what I'm looking for. Are you trying to help?
I see you ignored this. But that's expected in an ad hominem attack. I'm sorry you aren't mature enough to have a reasonable discussion of a tool. I guess some people get too emotional about inanimate things and software. -- Rick C. -+- Get 1,000 miles of free Supercharging -+- Tesla referral code - https://ts.la/richard11209
Reply by Ricky March 8, 20232023-03-08
On Tuesday, March 7, 2023 at 6:05:15&#8239;PM UTC-5, John S wrote:
> On 3/6/2023 4:21 PM, Ricky wrote: > > On Monday, March 6, 2023 at 3:44:39&#8239;PM UTC-5, John S wrote: > >> On 3/4/2023 1:26 PM, Ricky wrote: > >>> On Saturday, March 4, 2023 at 11:18:09&#8239;AM UTC-5, John S wrote: > >>>> On 3/3/2023 8:34 PM, Ricky wrote: > >>>>> On Friday, March 3, 2023 at 7:06:11&#8239;AM UTC-5, John S wrote: > >>>>>> On 3/2/2023 7:38 PM, Ricky wrote: > >>>>>>> On Thursday, March 2, 2023 at 9:18:10&#8239;PM UTC-4, John S wrote: > >>>>>>>> On 3/2/2023 5:25 PM, Ricky wrote: > >>>>>>>>> Is there anyone here who thinks LTspice has a good UI? > >>>>>>>>> > >>>>>>>>> I've been working with it for a week or so, after not using for over a year. It's very hard to reacclimate to the zoom in and out being backwards from every UI I know under Windows. The Function keys will become familiar again, if I continue using it, but what an uphill climb. > >>>>>>>>> > >>>>>>>>> I saw in an LTspice post that Mike E. is writing a new simulator. I hope he makes it compatible with the existing models. But I suppose he would not be able to work with the company models that don't have accessible contents. I'm wondering how useful it will be to the engineering community as a whole. There are lots of models you just can't get other than as locked by ADI. I think TI has given up on the idea of TINA being their goto simulator. LTspice just has too much steam on the boiler. > >>>>>>>>> > >>>>>>>> Which version of LTSpice? > >>>>>>> > >>>>>>> Did the UI change? I must have missed that. This is 17.0.36 > >>>>>>> > >>>>>> Yes, it changed from IV to XVII. > >>>>>> > >>>>>> I don't use 17. > >>>>> > >>>>> Ok... Are you suggesting the UI has significantly changed between the two lineages??? Are they still updating IV? > >>>>> > >>>> I'm not sure about all the UI changes > >>> > >>> So it may not have changed? > >>> > >> Well, how could I know? I have already stated that I did not continue > >> using V17. Have I misinterpreted your question? > > > > Previously, you replied to my question... > > > >>> Did the UI change? I must have missed that. This is 17.0.36 > >>> > >> Yes, it changed from IV to XVII. > > > > This would imply you know something about it. But apparently not. > > > No, it implies that I know very little about V17 as mentioned above. If > I have not used it how can you ASSUME I know something more about it > than I mentioned? Are daft or just practicing to be so? Why are you > pressing me for more information than I have? What's wrong with you?
I'm not pressing you for any information. What's wrong with your reading comprehension? I'm simply pointing out, very clearly with a quote, that you stated the UI changed between IV and XVII. If you don't know anything about it, how could you know that it changed? If you do know something that changed, you should be able to talk about it, instead of insisting you know nothing. I don't get you. Which of the words I'm using, do you not understand? Do you understand now? You said one thing, now you are saying something different. Can you at least acknowledge that? -- Rick C. --+ Get 1,000 miles of free Supercharging --+ Tesla referral code - https://ts.la/richard11209
Reply by Phil Hobbs March 8, 20232023-03-08
On 2023-03-08 12:59, John Larkin wrote:
> On Wed, 8 Mar 2023 11:23:50 -0500, Phil Hobbs > <pcdhSpamMeSenseless@electrooptical.net> wrote: > >> On 2023-03-08 10:47, John Larkin wrote: >>> On Tue, 7 Mar 2023 22:15:32 -0500, Phil Hobbs >>> <pcdhSpamMeSenseless@electrooptical.net> wrote: >>> >>>> >>>> A bunch of my stuff wouldn't budge off the peg with those >>>> settings. If you already know what it should look like, why >>>> simulate? >>> >>> To play with ideas fast day or night, and to get the parts >>> values right. >> >> I've been known to dork frequency compensation that way too, and to >> look at tolerances for filters. > > Right. Any interesting control loop is nonlinear. > >> >> The last thing I designed by poking at in SPICE was a collapsible >> BJT cascode, where the top transistor had to take a bunch of >> voltage. When the bottom transistor turned on, the top one >> saturated, pulling down its relatively high-Z base bias string, so >> the low level was just the sum of the V_CE(sat)s. >> >> I knew that part would work, but needed to figure out what the >> turn-off transient would look like. The answer was, "Nothing too >> pretty, but good enough for government work." It didn't look like >> the top transistor would reliably come out of saturation fast >> enough to avoid blowing up the bottom one, but a zener on its base >> solved that. >> >>> It's often easier to sim, say, a voltage divider than to do a lot >>> of math. >> >> Our ideas of "a lot of math" are a bit different, but doing that is >> no worse than using a calculator. ;) (I try to keep in practice >> doing mental arithmetic, because it makes me a much better >> troubleshooter.) > > A non-trivial voltage divider, with more than two resistors, can be > a pain to work out with a calculator, especially using the parts you > already have in stock. > > And Spice sims, with comments, are easy to save in a design notes > folder.
Yup. They go in our git repos too (one repo per project).
> > I do a lot of mental arithmetic, but it's analog computing, > guesswork and not manipulating digits in my head. I usually come in > around 5 or 10% accuracy, which is handy enough in most cases.
I like to make it a game. It's memory more than anything--in 1 Hz, 3 uA of photocurrent has 1 pA shot noise; for Johnson, 60.4 ohms has 1 nV and 16k has 1 pA. Going up and down decibels is fun too: 1 dB is 12% voltage and 25% power, pi = 10 dB (voltage), and so 2 pi = 16 dB. A noise contribution that's 6 dB down raises the floor by 1 dB, and it goes down linearly (in dB) for lower noise.
> Doing this at a whiteboard, in a meeting, seems to annoy some people. > This used to be called "Lightning Empiricism"; see Williams 1991.
Whiteboards are great fun, when combined with an interesting problem and one-to-three smart and good-natured colleagues. (And possibly a pitcher of beer.)
>>> I've invented some cool but improbable circuits by fiddling in >>> Spice. My ac/dc programmable dummy load was an unexpected >>> accident and is now a product. >>> >>> Doing the .opt tricks is safe if you are careful, which isn't >>> hard. Run a slow sim, note a few points, booger the sim until it >>> changes much, back off. I suppose that the options affect the >>> internals of imported models, so all you can do is try. >> >> I've done that in a pinch. I normally don't simulate big wodges >> of circuitry, so it doesn't come up much. >> >> Once in a great while I've needed to simulate the start-up or >> ring-down of an oscillator, which can take forever, but you do more >> of those, I expect. >> >>> >>>> >>>>> >>>>> I've done sims that take an hour to run a few milliseconds. >>>>> Feedback that slow doesn't train your instincts. >>>> >>>> Using universal opamps and VCVSes helps sometimes. >>> >>> I most always use one of the universal opamps, because LT Spice >>> seldom models mine, and it's too hard to research their list to >>> find one that's close to what I intend to use. >> >> Op amp models are such random-number generators anyway.... Once >> in awhile you get one that models asymmetrical slewing, but not >> very often. >> >> A depressing number even get the supply current all cattywampus. >> Even UniversalOpamp2 gets that right! > > Thank goodness for that! I sometimes use the supply rails as the > outputs of an opamp, to drive big power booster fets for example, > and I need that to be right, statically and dynamically.
It's a good trick, for sure, but not all amps like it. Old-timey 'single supply' amps often have very very poor PSR on V-, because of course the designer expects you to ground it, duh. Since CMR is input-referred, you can get _voltage gain_ between V- and the output, which makes life very exciting. UniversalOpamp2 will _not_ model that correctly. ;)
> As I noted recently, I found one ADI opamp that pulls 1e17 amps on > V+.
Very non-green, for sure.
> > Some will *output* free kilowatts from their power rails.
Still need a lot to make up for that 12V * 1e17 A. Cheers Phil Hobbs -- Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics Briarcliff Manor NY 10510 http://electrooptical.net http://hobbs-eo.com
Reply by John Larkin March 8, 20232023-03-08
On Wed, 8 Mar 2023 11:23:50 -0500, Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote:

>On 2023-03-08 10:47, John Larkin wrote: >> On Tue, 7 Mar 2023 22:15:32 -0500, Phil Hobbs >> <pcdhSpamMeSenseless@electrooptical.net> wrote: >> >>> >>> A bunch of my stuff wouldn't budge off the peg with those settings. >>> If you already know what it should look like, why simulate? >> >> To play with ideas fast day or night, and to get the parts values >> right. > >I've been known to dork frequency compensation that way too, and to look >at tolerances for filters.
Right. Any interesting control loop is nonlinear.
> >The last thing I designed by poking at in SPICE was a collapsible BJT >cascode, where the top transistor had to take a bunch of voltage. When >the bottom transistor turned on, the top one saturated, pulling down its >relatively high-Z base bias string, so the low level was just the sum of >the V_CE(sat)s. > >I knew that part would work, but needed to figure out what the turn-off >transient would look like. The answer was, "Nothing too pretty, but >good enough for government work." It didn't look like the top >transistor would reliably come out of saturation fast enough to avoid >blowing up the bottom one, but a zener on its base solved that. > >> It's often easier to sim, say, a voltage divider than to do a lot of >> math. > >Our ideas of "a lot of math" are a bit different, but doing that is no >worse than using a calculator. ;) (I try to keep in practice doing >mental arithmetic, because it makes me a much better troubleshooter.)
A non-trivial voltage divider, with more than two resistors, can be a pain to work out with a calculator, especially using the parts you already have in stock. And Spice sims, with comments, are easy to save in a design notes folder. I do a lot of mental arithmetic, but it's analog computing, guesswork and not manipulating digits in my head. I usually come in around 5 or 10% accuracy, which is handy enough in most cases. Doing this at a whiteboard, in a meeting, seems to annoy some people. This used to be called "Lightning Empiricism"; see Williams 1991.
> >> >> I've invented some cool but improbable circuits by fiddling in Spice. >> My ac/dc programmable dummy load was an unexpected accident and is >> now a product. >> >> Doing the .opt tricks is safe if you are careful, which isn't hard. >> Run a slow sim, note a few points, booger the sim until it changes >> much, back off. I suppose that the options affect the internals of >> imported models, so all you can do is try. > >I've done that in a pinch. I normally don't simulate big wodges of >circuitry, so it doesn't come up much. > >Once in a great while I've needed to simulate the start-up or ring-down >of an oscillator, which can take forever, but you do more of those, I >expect. > >> >>> >>>> >>>> I've done sims that take an hour to run a few milliseconds. >>>> Feedback that slow doesn't train your instincts. >>> >>> Using universal opamps and VCVSes helps sometimes. >> >> I most always use one of the universal opamps, because LT Spice >> seldom models mine, and it's too hard to research their list to find >> one that's close to what I intend to use. > >Op amp models are such random-number generators anyway.... Once in >awhile you get one that models asymmetrical slewing, but not very often. > >A depressing number even get the supply current all cattywampus. Even >UniversalOpamp2 gets that right!
Thank goodness for that! I sometimes use the supply rails as the outputs of an opamp, to drive big power booster fets for example, and I need that to be right, statically and dynamically. As I noted recently, I found one ADI opamp that pulls 1e17 amps on V+. Some will *output* free kilowatts from their power rails.
> >> The bv block can really simplify and speed up a sim, and is an easy >> way to compute things to plot. > >Yup. I usually compute efficiencies that way, for instance. > >Cheers > >Phil Hobbs
Reply by Phil Hobbs March 8, 20232023-03-08
On 2023-03-08 10:47, John Larkin wrote:
> On Tue, 7 Mar 2023 22:15:32 -0500, Phil Hobbs > <pcdhSpamMeSenseless@electrooptical.net> wrote: > >> On 2023-03-07 20:29, John Larkin wrote: >>> On Tue, 7 Mar 2023 20:05:16 -0500, Phil Hobbs >>> <pcdhSpamMeSenseless@electrooptical.net> wrote: >>> >>>> On 2023-03-07 18:21, John S wrote: >>>>> On 3/7/2023 9:45 AM, John Larkin wrote: >>>>>> On Tue, 7 Mar 2023 13:52:46 +0100, dalai lamah >>>>>> <antonio12358@hotmail.com> wrote: >>>>>> >>>>>>> Un bel giorno Clive Arthur digit&ograve;: >>>>>>> >>>>>>>> LTspice XVII >>>>>>>> >>>>>>>> If you have a group of .params, eg... >>>>>>>> >>>>>>>> .param Rlim 75 .param Clift 10n .param Cbp 180p >>>>>>>> >>>>>>>> ...and you right click on one of them on the >>>>>>>> schematic, edit its value and click 'ok', then nothing >>>>>>>> happens. Instead, you have to right click, then click >>>>>>>> 'cancel', then edit from the list and press 'ok'. >>>>>>> >>>>>>> I had that annoying problem too with LTspice XVII, but >>>>>>> it seems to be fixed on the new LTspice 17.1.x released >>>>>>> this year. >>>>>>> >>>>>>> Change log copied from a forum: >>>>>>> >>>>>>> * Transient Frequency Domain Analysis. LTspice 17.1 >>>>>>> includes a new frequency response analyzer component and >>>>>>> associate .fra spice directive. * Frequency domain >>>>>>> analysis has been reduced to a single component and >>>>>>> directive, greatly simplifying the generation of Bode >>>>>>> plots for non-linear circuits, including switched mode >>>>>>> power supplies * Both loop gain and output impedance are >>>>>>> supported by this feature * Improved Installation. >>>>>>> LTspice library files are stored in users&rsquo; >>>>>>> %LOCALAPPDATA% directories, instead of My Documents * >>>>>>> Waveform Viewer. Faster plotting speed for large datasets >>>>>>> * Keyboard Shortcuts. Keyboard shortcuts can be saved to >>>>>>> and loaded from text files * Schematic Capture. Numerous >>>>>>> schematic editor bugs have been eradicated * Simulator >>>>>>> Operation * Fixed a number of convergence problems * >>>>>>> Updated initial conditions behavior and documentation to >>>>>>> match behavior * Reduced multi-threaded CPU loading >>>>>>> >>>>>>> Another important feature for me is that you can now >>>>>>> specify relative paths for the models by manually >>>>>>> editing the .asy simbol files. In this way you can give >>>>>>> to anyone a complete package that just works, without the >>>>>>> need to manually copy the models in some obscure folder. >>>>>>> I think it should have been supported also on XVII in >>>>>>> some way, but I've never managed to make it work. >>>>>> >>>>>> I put each .param on its own line (not in a text box) and >>>>>> right-click edit works fine. >>>>>> >>>>>> Does putting them in a box control the order of execution? >>>>>> I can see how that might matter. >>>>>> >>>>>> Convergence fixes are welcome! I'd like a .sloppy >>>>>> directive to just do a fast sim at reduced accuracy. I >>>>>> don't need a switching supply to be parts-per-trillion >>>>>> accurate. >>>>> >>>>> Exactly!! >>>>> >>>> >>>> You can run the tolerances looser if you like. Occasionally >>>> it saves time. A custom dialog box giving some guidance on how >>>> to do that would be a nice feature. >>>> >>>> I've occasionally needed to do that, e.g. when doing >>>> photoreceiver sims at the 1-nA photocurrent level, you sort of >>>> need to tighten the abstol settings. I'm no SPICE guru, >>>> though. >>>> >>>> Cheers >>>> >>>> Phil Hobbs >>> >>> .opt abstol=2nA .opt chgtol=10pC .opt trtol=5 .opt reltol=0.002 >>> .opt method=trap >>>> >>> seems to help slow ones. I just slop things up until the sim >>> doesn't look believable, and back off some. >> >> A bunch of my stuff wouldn't budge off the peg with those settings. >> If you already know what it should look like, why simulate? > > To play with ideas fast day or night, and to get the parts values > right.
I've been known to dork frequency compensation that way too, and to look at tolerances for filters. The last thing I designed by poking at in SPICE was a collapsible BJT cascode, where the top transistor had to take a bunch of voltage. When the bottom transistor turned on, the top one saturated, pulling down its relatively high-Z base bias string, so the low level was just the sum of the V_CE(sat)s. I knew that part would work, but needed to figure out what the turn-off transient would look like. The answer was, "Nothing too pretty, but good enough for government work." It didn't look like the top transistor would reliably come out of saturation fast enough to avoid blowing up the bottom one, but a zener on its base solved that.
> It's often easier to sim, say, a voltage divider than to do a lot of > math.
Our ideas of "a lot of math" are a bit different, but doing that is no worse than using a calculator. ;) (I try to keep in practice doing mental arithmetic, because it makes me a much better troubleshooter.)
> > I've invented some cool but improbable circuits by fiddling in Spice. > My ac/dc programmable dummy load was an unexpected accident and is > now a product. > > Doing the .opt tricks is safe if you are careful, which isn't hard. > Run a slow sim, note a few points, booger the sim until it changes > much, back off. I suppose that the options affect the internals of > imported models, so all you can do is try.
I've done that in a pinch. I normally don't simulate big wodges of circuitry, so it doesn't come up much. Once in a great while I've needed to simulate the start-up or ring-down of an oscillator, which can take forever, but you do more of those, I expect.
> >> >>> >>> I've done sims that take an hour to run a few milliseconds. >>> Feedback that slow doesn't train your instincts. >> >> Using universal opamps and VCVSes helps sometimes. > > I most always use one of the universal opamps, because LT Spice > seldom models mine, and it's too hard to research their list to find > one that's close to what I intend to use.
Op amp models are such random-number generators anyway.... Once in awhile you get one that models asymmetrical slewing, but not very often. A depressing number even get the supply current all cattywampus. Even UniversalOpamp2 gets that right!
> The bv block can really simplify and speed up a sim, and is an easy > way to compute things to plot.
Yup. I usually compute efficiencies that way, for instance. Cheers Phil Hobbs -- Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics Briarcliff Manor NY 10510 http://electrooptical.net http://hobbs-eo.com
Reply by John Larkin March 8, 20232023-03-08
On Tue, 7 Mar 2023 22:15:32 -0500, Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote:

>On 2023-03-07 20:29, John Larkin wrote: >> On Tue, 7 Mar 2023 20:05:16 -0500, Phil Hobbs >> <pcdhSpamMeSenseless@electrooptical.net> wrote: >> >>> On 2023-03-07 18:21, John S wrote: >>>> On 3/7/2023 9:45 AM, John Larkin wrote: >>>>> On Tue, 7 Mar 2023 13:52:46 +0100, dalai lamah >>>>> <antonio12358@hotmail.com> wrote: >>>>> >>>>>> Un bel giorno Clive Arthur digit&#4294967295;: >>>>>> >>>>>>> LTspice XVII >>>>>>> >>>>>>> If you have a group of .params, eg... >>>>>>> >>>>>>> .param Rlim 75 >>>>>>> .param Clift 10n >>>>>>> .param Cbp 180p >>>>>>> >>>>>>> ...and you right click on one of them on the schematic, edit its value >>>>>>> and click 'ok', then nothing happens.&#4294967295; Instead, you have to right >>>>>>> click, >>>>>>> then click 'cancel', then edit from the list and press 'ok'. >>>>>> >>>>>> I had that annoying problem too with LTspice XVII, but it seems to be >>>>>> fixed >>>>>> on the new LTspice 17.1.x released this year. >>>>>> >>>>>> Change log copied from a forum: >>>>>> >>>>>> * Transient Frequency Domain Analysis. LTspice 17.1 includes a new >>>>>> frequency response analyzer component and associate .fra spice >>>>>> directive. >>>>>> * Frequency domain analysis has been reduced to a single component and >>>>>> directive, greatly simplifying the generation of Bode plots for >>>>>> non-linear >>>>>> circuits, including switched mode power supplies >>>>>> * Both loop gain and output impedance are supported by this feature >>>>>> * Improved Installation. LTspice library files are stored in users&#4294967295; >>>>>> %LOCALAPPDATA% directories, instead of My Documents >>>>>> * Waveform Viewer. Faster plotting speed for large datasets >>>>>> * Keyboard Shortcuts. Keyboard shortcuts can be saved to and loaded from >>>>>> text files >>>>>> * Schematic Capture. Numerous schematic editor bugs have been eradicated >>>>>> * Simulator Operation >>>>>> * Fixed a number of convergence problems >>>>>> * Updated initial conditions behavior and documentation to match >>>>>> behavior >>>>>> * Reduced multi-threaded CPU loading >>>>>> >>>>>> Another important feature for me is that you can now specify relative >>>>>> paths >>>>>> for the models by manually editing the .asy simbol files. In this way >>>>>> you >>>>>> can give to anyone a complete package that just works, without the >>>>>> need to >>>>>> manually copy the models in some obscure folder. I think it should have >>>>>> been supported also on XVII in some way, but I've never managed to >>>>>> make it >>>>>> work. >>>>> >>>>> I put each .param on its own line (not in a text box) and right-click >>>>> edit works fine. >>>>> >>>>> Does putting them in a box control the order of execution? I can see >>>>> how that might matter. >>>>> >>>>> Convergence fixes are welcome! I'd like a&#4294967295; .sloppy&#4294967295; directive to just >>>>> do a fast sim at reduced accuracy. I don't need a switching supply to >>>>> be parts-per-trillion accurate. >>>> >>>> Exactly!! >>>> >>> >>> You can run the tolerances looser if you like. Occasionally it saves >>> time. A custom dialog box giving some guidance on how to do that would >>> be a nice feature. >>> >>> I've occasionally needed to do that, e.g. when doing photoreceiver sims >>> at the 1-nA photocurrent level, you sort of need to tighten the abstol >>> settings. I'm no SPICE guru, though. >>> >>> Cheers >>> >>> Phil Hobbs >> >> .opt abstol=2nA >> .opt chgtol=10pC >> .opt trtol=5 >> .opt reltol=0.002 >> .opt method=trap >> > > > seems to help slow ones. I just slop things up until the sim doesn't > > look believable, and back off some. > >A bunch of my stuff wouldn't budge off the peg with those settings. >If you already know what it should look like, why simulate?
To play with ideas fast day or night, and to get the parts values right. It's often easier to sim, say, a voltage divider than to do a lot of math. I've invented some cool but improbable circuits by fiddling in Spice. My ac/dc programmable dummy load was an unexpected accident and is now a product. Doing the .opt tricks is safe if you are careful, which isn't hard. Run a slow sim, note a few points, booger the sim until it changes much, back off. I suppose that the options affect the internals of imported models, so all you can do is try.
> > > > > I've done sims that take an hour to run a few milliseconds. Feedback > > that slow doesn't train your instincts. > >Using universal opamps and VCVSes helps sometimes.
I most always use one of the universal opamps, because LT Spice seldom models mine, and it's too hard to research their list to find one that's close to what I intend to use. The bv block can really simplify and speed up a sim, and is an easy way to compute things to plot.
>Cheers > >Phil Hobbs