Timeline for Why do I see multiple waveforms on my oscilloscope in normal trigger mode?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 23 at 15:18 | history | suggested | MarianD | CC BY-SA 4.0 | Link assigned directly to appropriate text, some fixes. |
| Apr 23 at 15:10 | review | Suggested edits | |||
| S Apr 23 at 15:18 | |||||
| Jul 11, 2017 at 16:35 | vote | accept | AndreKR | ||
| Jul 11, 2017 at 16:13 | comment | added | Daniel Bogdanoff - Keysight | In general, yes, that's a fair assumption. | |
| Jul 10, 2017 at 21:14 | comment | added | AndreKR | That makes sense. I always wondered how can those InfiniiVision scopes refresh their screen a million times per second. Simple answer: They don't. Which is probably a good thing, otherwise you wouldn't be able to see anything. Anyway, so I can assume that if both triggers happen within about 1/120th of a second, they'll both be painted. | |
| Jul 10, 2017 at 19:55 | comment | added | Daniel Bogdanoff - Keysight | Yes, this is by design. We sometimes talk about oscilloscope waveform update rate, which hundreds of thousands or over a million waveform captures per second, but a screen only refreshes something like 120 times per second, so multiple captures are overlaid on top of each other in run mode. The spec to look for is "waveform update rate." But, you can also check the frequency of the oscilloscope's trigger out (if it has one) and that will let you know how fast your scope is triggering. | |
| Jul 7, 2017 at 22:51 | comment | added | AndreKR | "When in "Run" mode you're potentially seeing the waveforms for multiple trigger events." So that is by design? All DSOs work that way? Is there a number in the manual that tells me how long it takes for the screen to be cleared? | |
| Jul 7, 2017 at 22:36 | history | answered | Daniel Bogdanoff - Keysight | CC BY-SA 3.0 |