Replies: 1 comment 1 reply
-
|
First of all, you're right about holdoff. I've added that to v30 firmware now, in the v30_test branch, with associated software in that branch to use it. Then you can go back to single channel mode and get the full sample rate. I've added a release v30.02-beta that incorporates these. About the trigger delay, you basically have it right. Set the trigger time slider all the way to the left and then you have maximum data taken after the trigger, i.e. most of the record depth. Then you can use pan and zoom to look more closely at whatever region of the data you want. But, I've now also added an actual trigger delay, which will wait an adjustable time before actually firing the trigger. This is in the new v30 as well. Hopefully this helps! Do let me know how it goes and if you have more questions or suggestions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm kind of struggling with the way time base operates/have some basic questions. Apologies in advance if I missed this in the video. OTOH maybe the answer will be to use ngscopeclient as I'm looking at that for eye diagrams. For now I'm looking at the native interface. Here's a typical waveform capture where the data (from a differential probe) on ch 0 (ok, zero is weird too) and trigger on ch 1.
I could not get the scope to reliably trigger on ch 0 as there doesn't seem to be a hold off; if looking inside of a packet I do not want to retrigger until the 2nd next packet comes along (this is a bidirectional LVDS like line, one is upstream and the other is downstream). I worked around that using a master frame clock (48 kHz) as trigger.
What I can't figure out is at a faster horizontal (time) access, how can I scroll through the waveform. Basically trigger delay. For example if I zoom in more than this:

I can't find a way to look at the last few bits. There's a grey'd out Delay control, is that what I need?
If I do pan and zoom the data is cut off:

Or do I make depth bigger and let it collect more data and then the pan and zoom does what I want?

Seems like there should be a "knob" to explicitly set a trigger delay?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions