|
Hi
I'd prefer a separate section in the status bar, at the right end, specifically to display this.
For example:
| other simulation information... | Solver: norm | Method: trap |
Or something like that. But no flashing please...that will just teach me to ignore it. :-)
|
On Sun, Nov 10, 2024 at 09:55 AM, Christopher Paul wrote:
I’m presently using LTspice 17.1.14. I am concerned that transitioning to a later version might disrupt files that I depend on for 17.1.14.
Can I install a newer version without disrupting the old?
Version 24.* will update the files in C:\Users\<user>\AppData\Local\LTspice, but nothing outside of that location. The first time you run any version 24.* it will make a copy of your standard.* libraries in Documents\LTspice, just in case you customized them and you need to get something back. TLDR: If you haven't changed or added any files in C:\Users\<user>\AppData\Local\LTspice, the transition from 17.1 to 24 should be smooth.
-Ben
|
переключити цитоване повідомлення
Показати цитований текст
From: LTspice@groups.io <LTspice@groups.io> On Behalf Of Voegeli, Benjamin via groups.io Sent: Monday, November 11, 2024 2:50 PM To: LTspice@groups.io Subject: Re: [LTspice] LTspice 24.1 Beta Available Now On Sun, Nov 10, 2024 at 09:55 AM, Christopher Paul wrote: I’m presently using LTspice 17.1.14. I am concerned that transitioning to a later version might disrupt files that I depend on for 17.1.14. Can I install a newer version without disrupting the old?
Version 24.* will update the files in C:\Users\<user>\AppData\Local\LTspice, but nothing outside of that location. The first time you run any version 24.* it will make a copy of your standard.* libraries in Documents\LTspice, just in case you customized them and you need to get something back.
TLDR: If you haven't changed or added any files in C:\Users\<user>\AppData\Local\LTspice, the transition from 17.1 to 24 should be smooth.
|
Hi Mathias,
Hopefully, you are still looking at this thread.
I executed 9 runs of a file” Switch_Slope_HYS_play.asc”
This file modifies both the slope and hysteresis of a switch “SW”.
The transient is Maximum Timestep = blank or 10 ns or 1 ns.
LTspice 24.0.12, .tran 0 6m 50u startup.
LTspice 24.0.12,.tran 0 6m 50u 10n startup.
LTspice 24.0.12,.tran 0 6m 50u 1n startup.
I then repeated the 3 runs with LTspice 24.0.12, but added the settings:
“.opt numdgt=10” and “.opt measdgt=10” ( invokes double precision )
I then executed the 3 runs under LTspice 24.1.0 beta.
I found that the output data from LTspice 24.1.0 beta produces more resolution than any of the settings in LTspice 24.0.12.
After looking at my data, it is obvious that the double precision is no longer required.
After some thought, I realized that eliminating the commands in LTspice 24.1.0 beta might cause issues for any anyone who has previously included these commands on their .asc file.
I would suggest that the LTspice 24.1.0 beta be modified to simply ignore the commands “.opt numdgt=10” and “.opt measdgt=10”.
I placed all of my testing results in an excel file. The file isn’t “publication quality”, but I will be happy to upload it if you want to see the data.
Thanks,
Mike Fraser
|
On Thu, Nov 14, 2024 at 09:18 AM, Mike Fraser wrote:
I would suggest that the LTspice 24.1.0 beta be modified to simply ignore the commands “.opt numdgt=10” and “.opt measdgt=10”.
I do not speak for anyone at Analog Devices - but, more likely, the bug that caused the problem will be fixed in Beta version 24.1.1. That's why they have incrementing revision numbers.
Hopefully it will not be fixed by back-tracking features. "Simply" ignoring settings is not a good idea.
In your case I think the problem was only NUMDGT=10 along with .STEP, since that affects the .STEP'ed RAW file. Since MEASDGT doesn't affect the RAW file, I think it would have no effect on the plotting problem.
Andy
|
Hi Andy,
Sorry for the confusion.
It appears my comment on “.opt numdgt=10” and “.opt measdgt=10” was not clear.
Ltspice 24.1.0 beta will not allow .opt numdgt but will allow .opt measdgt.
I basically ran the same type of file that you commented on in message 156330.
I ran this file twice, once with .opt measdgt=enabled and once with .opt measdgt=not enabled.
When I compare the measured results from the Spice Output Log, they are identical to 15 decimal places.
This is why I stated that .opt measdgt has no effect in LTspice 24.1.0 beta.
Please feel free to try the same test.
I definitely could be wrong, but I have repeated the simulation many times, always with the same results.
I suspect that the software people are simply delivering maximum resolution, with truncation left to the user.
My conclusion is that “.opt numdgt=10” and “.opt measdgt=10” are no longer used in LTspice 24.1.0 beta.
Thanks,
Mike
|
Hi. Just downloaded, looking forward to trying it out tomorrow.
Writing here as I noticed this beta includes better path support for libraries, right after writing about the use of environment variables (as suggested a couple years ago by somebody) in another post. It's probably too late for this release but maybe there is a better or at least parallel way that allows better portability. See my post, here.So glad to see that AD/LT are still giving LTspice some love with new releases. I'd be so dissapointed if it were canned in favor of the AD/SIMPLIS EE Oasis. As much as I do like SIMPLIS's speed (used it with TI and standalone) I always choose LTspice over it, the propretary models are so trustworthy.
|
The link to the beta release appers to be broken. Is this intentional or just an accident?
|
On Thu, Dec 19, 2024 at 05:15 PM, BRUCE108 wrote:
The link to the beta release appers to be broken. Is this intentional or just an accident?
I think the Beta version was taken down a couple of weeks ago, probably while Analog Devices works out the bugs.
I did not see any confirmation of that, but I think it is the most likely reason.
I have heard nothing about a newer Beta version yet, so I guess it's just wait and see until ADI has one ready for the masses.
Andy
|
Beta, Betta, Bettastill.
On 2024-12-19 22:28, Andy I via
groups.io wrote:
On Thu, Dec 19, 2024 at 05:15 PM, BRUCE108 wrote:
The link to the beta release appers to be broken. Is this
intentional or just an accident?
It is not precisely a broken link. I think the Beta
version was taken down a couple of weeks ago, probably while
Analog Devices works out the bugs.
I did not see any confirmation of that, but I think it is
the most likely reason why.
I have heard nothing about a newer Beta version yet, so I
guess it's just wait and see until ADI has one ready for the
masses.
Andy
--
OOO - Own Opinions Only
Best Wishes
John Woodgate
Keep trying
|
On 19/11/2024 03:32, j.a.morgan.gm via
groups.io wrote:
Hi. Just downloaded, looking forward to trying it out
tomorrow.
Writing here as I noticed this beta includes better path support
for libraries, right after writing about the use of environment
variables (as suggested a couple years ago by somebody) in
another post. It's probably too late for this release but maybe
there is a better or at least parallel way that allows better
portability. See my post, here.
So glad to see that AD/LT are still giving LTspice some love
with new releases. I'd be so dissapointed if it were canned in
favor of the AD/SIMPLIS EE Oasis. As much as I do like SIMPLIS's
speed (used it with TI and standalone) I always choose LTspice
over it, the propretary models are so trustworthy.
LTspice already supports environmental variables though the
operating system calls it uses. Unfortunately, though, it doesn't
acknowledge this if you try to view a model file linked by:
.lib ModelFileName.sub
.. when used with, for example, an environmental variable called
%MyModelLibs% that is listed in Settings > Search Paths >
Library Search Paths. However, in practice, LTspice still finds
ModelFileName.sub, provided it really does exist in the folder
pointed to by %MyModelLibs%, when an analysis is run.
Rather unhelpfully, LTspice tells you that %MyModelLibs% doesn't
exist when you add it to Settings > Search Paths > Library
Search Paths, but you can override this and tick "Add it anyway".
--
Regards,
Tony
|
They can work on the bugs to their hearts content, but it might be reasonable to leave the link there so more people can continue the search.
|
Hello,
Some additionals features : Some options for future releases. Christmas is over, but it will be for next year:)
- MultiTabs per plot setting could be very nice, especially when we changed simulation between .ac and .tran we do not necessarily want to draw the same curves.
- For hierarchical schemas: Option to automatically update the port between the schema (.asc) and the symbol (.sym)
Emilien
|
On Mon, Dec 30, 2024 at 09:49 AM, <emilien.sabard@...> wrote:
Some additionals features : Some options for future releases. Christmas is over, but it will be for next year:)
...
As you know, this group is not the place to officially make suggestions to the LTspice developers about recommendations or improvements. This group is people like you who use LTspice; we are not its developers. To make your recommendations known to Analog Devices, you must follow what it says under Help > About LTspice and use the EngineerZone.
Andy
|
On Mon, Dec 30, 2024 at 09:49 AM, <emilien.sabard@...> wrote:
- MultiTabs per plot setting could be very nice, especially when we changed simulation between .ac and .tran we do not necessarily want to draw the same curves.
The best way to handle different simulations, is to name the schematics differently. Say, MySim_Tran.asc and MySim_AC.asc, which might be identical except for their simulation commands. Then each has its own plot settings file, and you can switch back and forth without difficulty. Also this lets you keep both results available for later, since each .RAW file can contain one but not both simulations.
- For hierarchical schemas: Option to automatically update the port between the schema (.asc) and the symbol (.sym)
What is there that you can't already do? I am just trying to understand the thought.
In many cases, an automatically created symbol file from the lower-level schematic is sufficient. Therefore, just delete the old symbol file and ;let LTspice make a new one.
LTspice does not use ".sym" files. I'm assuming you meant to write ".asy".
Andy
|
John Woodgate
Tony Casey