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

Oscilloscope trigger stops working upon changing vertical range #233

Open
MrDerples opened this issue Dec 2, 2022 · 3 comments
Open

Oscilloscope trigger stops working upon changing vertical range #233

MrDerples opened this issue Dec 2, 2022 · 3 comments

Comments

@MrDerples
Copy link

MrDerples commented Dec 2, 2022

When using the oscilloscope trigger, the displayed waveform will stop updating if, first, the vertical range is expanded below -1.14 V or above +4.54 V, and then, the oscilloscope is paused and un-paused. (I noticed this because pausing and un-pausing the scope is how I work around issue #232.) This only seems to happen once per program session, the first time either of those range values is exceeded, and any of the following seems to resolve it:

  • Toggling any oscilloscope channel on and off;
  • Toggling the trigger on and off;
  • Jogging the trigger value up and back down;
  • Entering the trigger level textbox and pressing enter, re-entering the currently-displayed value.

It's almost like, when the range is changed past the thresholds mentioned, the trigger level gets changed within the program, but without updating the display.

For reference, I'm running on Windows 10 Enterprise 21H2, build 19044.2311. The Labrador software is git hash 2cc0678, downloaded from Github on 2022-12-02 (New York time). I've been able to replicate this on multiple Labrador boards.

@EspoTek
Copy link
Owner

EspoTek commented Dec 3, 2022

It's almost like, when the range is changed past the thresholds mentioned, the trigger level gets changed within the program

It does! Past those voltage thresholds, it'll update the PGA and therefore the map to convert digital samples to analog values (and vice-versa). I'll look into why this isn't updating in the post-Christmas break, and make sure to never again use retained mode GUIs for as long as I live!

@MrDerples
Copy link
Author

MrDerples commented Jan 7, 2023 via email

@EspoTek
Copy link
Owner

EspoTek commented Jan 9, 2023

Hi mate. I don't think they'll be fixed up soon. All of the post-Christmas downtime I had was eaten up by a COVID infection.

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

No branches or pull requests

2 participants