Lots of inspiration in this forum, such as demonstrating deep memory measurements by using the pulse count function. As further refinement, gated measurements can be used in order to ignore unwanted portions of the record.
First the basic pulse measurement without any bells and whistles; a 100 MHz square wave with 1 ns rise time and 50% duty cycle is fed into Ch.4
/?action=dlattach;attach=1978194;image)
SDS2504X_HD_Pulses
At a timebase of 2 ms/div the total screen width corresponds to 20 ms and we get close to 2 million pulses in either direction accordingly.
Let’s add a measurement gate. We define it to start at the trigger point at 0.0 ms and to be 1 ms wide:
/?action=dlattach;attach=1978200;image)
SDS2504X_HD_Pulses_Gate
We now get a count of ~100k (100 MHz x 0.001 sec.) as expected.
We can engage the zoom view for a closer inspection of the waveform:
/?action=dlattach;attach=1978206;image)
SDS2504X_HD_Pulses_Gate_Zoom
We can still see the gating cursors in the main window, but the detailed view with time data is in the zoom window. Since the “B” cursor is outside the zoom window, it is drawn at the right border and the time specification of 1.00 ms is another hint that it is outside the zoom window, which only reaches up to 50 ns.
The gating cursors are fully independent, consequently we can still add the regular cursors (manual/tracking/measurement):
/?action=dlattach;attach=1978212;image)
SDS2504X_HD_Pulses_Gate_Zoom_Cursors
With all these information, screen gets a bit busy, but we could also use the traditional info block for the regular cursors and place it at a less disturbing spot.
Home
Help
Search
Login
Register
