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 range clipping #232

Open
MrDerples opened this issue Dec 2, 2022 · 1 comment
Open

Oscilloscope range clipping #232

MrDerples opened this issue Dec 2, 2022 · 1 comment

Comments

@MrDerples
Copy link

The oscilloscope display will clip voltages past a certain level until channel 1 is paused and unpaused. The negative range seems to be clipped at -1.37 V and/or -4.65 V, while the positive channel seems to clip at +4.65 V. I've observed this behavior on both channels under a number of different operating conditions, and the steps below seem to be the bare minimum needed to replicate it:

  1. Open the Labrador software. Connect a signal source between oscilloscope channel 1 (DC) and ground, and feed it a signal that will exceed -1.37 V and/or +4.65 V. For purposes of illustration, I used a 1 kHz, 10 Vpp sine wave centered on zero, but the nature of the signal, or whether or not the Labrador's signal generator is being used to provide it, doesn't seem to matter. I also set the trigger level to zero, but you can observe this with an untriggered acquisition, too. Note the channel 1 max and min values.

clipping_1

  1. Change the vertical range to something that should show the whole waveform. In my example, -6 V to +6 V. You will observe that the waveform is clipped at the levels previously mentioned, like in the image below.

clipping_2

  1. Pause acquisition (click the "Paused" checkbox"), then un-pause it - the waveform will no longer be clipped.

clipping_3

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

Very clear report. I know exactly what would cause this and will get it fixed up after Christmas.

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