|
Peter Jaquiery |
Provide an analyser menu option to enable/disable analysers without having to create/delete them.
This allows process expensive analyzers to be turned off until they are needed avoiding creating and configuring analyzers frequently.
Mega bonus points for prioritizing processing of visible data for suitable analyzers (SPI and I2C for example).
Activity Newest / Oldest
Tim
(#84449)
"In a lot of cases, it would be useful to just do the capture and then turn on the analyzer that decodes the address. If that shows something interesting, then the read or write analyzers might be turned on too. Having enable/disable would really speed things along."
Tim
discuss.saleae.com/t/quick-poll-problems-you-try-to-solve-with-an-oscilloscope/995/4
"Ability to turn off CPU consuming things like contonious graph update, HLA’s and similar when not needed during the capture."
Tim
Merged with: Disable/pause HLA analyzers
Otzen
I often to relatively long captures waiting for some event. i.e. capture for 5 minutes, and upon trigger I only keep 200 ms.
And because all the HLA analyzers i have included is permanently running, they load my CPU hard, making the PC slow and all the fans roar at full speed during the whole capture.
Effectively making my HLA analyze 300.000 ms, where I only needed it to analyze the 200 ms, I am left with after the trigger triggers.
While I do see that sometimes you need to let the HLA run, like if you want to trigger on output of those, so I suggest some kind of on/off button on each analyzer.
NB: while this request is about the HLA, as they have most CPU impact, this would be nice for the low level/c based ones too.
Tim
discuss.saleae.com/t/high-speed-async-fills-buffer-quickly/2210/8
"I was not aware that you could load a preset on already sampled data, that helps a lot not having to configure 5 analysers every time after I have sampled, thank you :slight_smile: Maybe each analyser could have an enable/disable button, that would make it even easier :wink:"
Tim
(#79160)
"Hi, First of all, Logic 2 is a great tool. Easy to use and reliable. Thanks for that.
Is there an way to hide the analyser without deleting it?
If I use the scope for other signals that have nothing to do with the analyser then it still shows with lots of errors as expected. I need to hide it."
Tim
discuss.saleae.com/t/pause-analyzers-during-capture/1997
"I have quite a few analyzers enabled, including some HLAs, and during the capture process this exhausts buffer memory rather quickly, as well as using a lot of CPU.
Is there a way to avoid live-decoding the signals during capture?"
Tim
(#76228)
"Analyzer Disable option for each active analyzer. When the analyzer is disabled its will be greyed out and its results removed from channels/datatable. Similar to Delete option (already available) BUT the disabled analyzer configuration is kept and it could be restore by an Enable option. Useful when multiple Analyzers are active at the same time and one want to disable any of them to speed up the analyzers processing or tide up the visualization, without losing the configuration of the specific analyzer."
Peter
See ideas.saleae.com/b/feature-requests/allow-presets-to-load-on-saved-captures/ for related discussion - especially the idea of a global on/off switch for analyzers and (cramming in an idea between the lines) analyzer presets (named preset analyzer configurations that can be loaded and saved as configuration files).
tamas
Would be nice to see this in the upcoming release.
On slower pcs or notebooks this gives a huge performance improvement when buffer is 16-32gb long and the analyzers are not running always just when I really need it (long capture not always recording a bug that I'm looking for).
I have to delete/add analyzers constantly to have some CPU time.
Especially with looping real-time mode the analyzer running pretty much renders my PC unstable and non responsive.