It would be great if we could specify a preset as the Default preset, such that it automatically loads the same settings upon starting the Logic 2 app.
13-01-2023 -
Activity
Newest / Oldest
C
Chetana
Is this feature to load preset config in the beginning of automation, available yet?
We unfortunately don't have an update on this yet. Having said that, our software is supposed to remember the last settings that were used the next time you run it, assuming the same device model is attached when compared to the previous session.
Ah, I see what you mean. Our Automation API was designed to run in their own separate "virtual instance" of the software/capture tab. Once the automation is complete, this instance will be closed and the software will return to the previous configuration/instance of the software before the capture was run. This is to avoid any conflicts the existing/current session.
As such, we currently don't allow Automation scripts to run using any predefined default capture setting values. All required settings will need to be manually configured from within your Automation API script.
Activity Newest / Oldest
Chetana
Is this feature to load preset config in the beginning of automation, available yet?
Tim
Apologies this is not yet available. In case you are looking for preset loading functionality for the Automation API, we're tracking this here:
ideas.saleae.com/b/feature-requests/automation-api-load-presets/
Albert
Any update on this topic? As it would solve some of the limitations currently preset(Labels,
Tim
We unfortunately don't have an update on this yet. Having said that, our software is supposed to remember the last settings that were used the next time you run it, assuming the same device model is attached when compared to the previous session.
Albert
When starting capturing via API all settings are cleared, like the Labels and so on, so it is not as you mention
Tim
Ah, I see what you mean. Our Automation API was designed to run in their own separate "virtual instance" of the software/capture tab. Once the automation is complete, this instance will be closed and the software will return to the previous configuration/instance of the software before the capture was run. This is to avoid any conflicts the existing/current session.
As such, we currently don't allow Automation scripts to run using any predefined default capture setting values. All required settings will need to be manually configured from within your Automation API script.
We find that users who need to run their automation script on existing capture sessions (i.e. use the currently configured settings), typically want to run in a "semi-automated" fashion as described in a separate feature request below:
ideas.saleae.com/b/feature-requests/automation-api-start-capture-on-pre-existing-session/
Tim
Original request in Ticket #77386