Jump to content

asdfex

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

asdfex's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. Hi @JColvin thanks for the tip, but unfortunately this doesn't work. The menu points to a local file (which exists) file:///usr/share/digilent/waveforms/doc/index.html But this doesn't work when the browser is installed via snap, which is (unfortunately) the default in several operating systems like Ubuntu or OpenSuse.
  2. Thanks! Mode: record seems to do what I need. The reference manual doesn't explain these modes. It seems to be quite outdated and referring to an older version of the GUI, e.g. the "mode" setting mentioned there is now the "trigger".
  3. Dear all, is there a way to have the settings for the next acquisition independent from zooming and scrolling in the waveform view? I often record a long sample of data (e.g. 16Mi samples) at medium rate (20 MHz) and then start scrolling and zooming around in the waveforms view to see details. Unfortunately this immediately changes the settings used for the next run (offset, sampling rate) so it's quite impossible to repeat the same measurement again. I would very much prefer to have the settings for sample rate and offset fixed, only edited manually. And have the zoom and scroll of the main window be independent from this. Is this possible and did I simply overlook the preference setting for it? Thanks!
  4. @JColvin Thanks for the extensive answer, but @attila hit the point: It's a bit unexpected, but indeed the transfer time was rather long. If I change from 4Mi to 2Mi samples or reduce the number of inputs from 32 to 16, the repeated mode works again. I'm looking for events happening seldomly, so the data transfer time doesn't matter in this case. Maybe one can replace the full stop by a short sleep between end of transmission and going to armed mode again? Then there should be enough time for the application to respond to user action, but it also eventually returns to data taking. Thank you!
  5. Hi, since some time I can't set the logic analyzer using a Digital Discovery to automatically keep running. Behavior is the same in 3.20.1 and the latest 3.20.28. As expected, a click on "Single" causes the LA to trigger once and return to "stop" mode. But using "Run" causes exactly the same behavior, although after a trigger it should go back to 'armed' mode. I can't find which wrong setting might cause this problem. Any ideas?
×
×
  • Create New...