You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ds1054z CLI tool should enable users to backup and restore settings related to the scope with a simple command. Having a backup of the settings would allow operators of the scope to play around with all the knobs and settings while being able to quickly going back to the old settings if needed. The backup should be written to a (human and machine friendly) local file and should contain the following information:
time axis
timebase
zero-offset
active channels:
Y-offset
Y-scale
coupling
acquisition
number of samples (auto, fixed number)
"measurements":
measurement kind
related channel
display (zoom?)
trigger
condition (channel, edge, level)
mode (auto, normal, single)
When it comes to the global scope status (running, stopped, single) I think it should not be restored. It would make more sense to stop the scope during the restore operation and leave it up to the user to press the start/single/whatever button (or send the corresponding command) after restoring.
Proposed CLI signature:
ds1054z settings --backup somefile
ds1054z settings --restore somefile
ds1054z settings --backup newfile --restore oldfile # first back up, then restore
The text was updated successfully, but these errors were encountered:
The
ds1054z
CLI tool should enable users to backup and restore settings related to the scope with a simple command. Having a backup of the settings would allow operators of the scope to play around with all the knobs and settings while being able to quickly going back to the old settings if needed. The backup should be written to a (human and machine friendly) local file and should contain the following information:When it comes to the global scope status (running, stopped, single) I think it should not be restored. It would make more sense to stop the scope during the restore operation and leave it up to the user to press the start/single/whatever button (or send the corresponding command) after restoring.
Proposed CLI signature:
The text was updated successfully, but these errors were encountered: