Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Backup and Restore Settings #3

Open
pklaus opened this issue Jul 16, 2016 · 1 comment
Open

Feature Request: Backup and Restore Settings #3

pklaus opened this issue Jul 16, 2016 · 1 comment

Comments

@pklaus
Copy link
Owner

pklaus commented Jul 16, 2016

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 
@andmarti1424
Copy link

This would be great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants