The third and fourth images show a weird effect I'm seeing in "Normal" sweep mode. I've seen it with both slope-trigger and edge-trigger. What's going on here? It's as if several traces have been drawn at once, during a single trigger. I have "Min" persistence set, so it's not that. I don't see this effect with Single or Auto sweep mode, and about half the time the trigger is a single trace. With the fourth image, I only see this for 1.00 us/div or less.
This is normal, watch this video.
https://youtu.be/ta096oBzSacHere's another odd example: the scope reports that the slope is 902MV/s (and from cursor measurements this seems to be about right) but the trigger condition is "> 15.0 ns" which at BY-AY=1.6V should be triggering for a rate less than 107MV/s. However at the trigger point, the signal is clearly much, much faster than this threshold, yet it triggered.
This one is easy to explain, trigger sampling rate is same as current oscilloscope sampling rate, but measurement and cursors are based on points on screen, which are 1200 points max, so you must zoom in to measure it precisely.
edit: sorry i didn't notice that you have 5ns/div and can't zoom in furtherl, but signal which you try to trigger is at limits of this scope, so it gets confused, even if your digital sampling is 1GSPS -> so 1ns between two points, your analog bandwith is only 100MHz (if hacked, if not it's even worse), so rise/fall time is limitted by front end, in thread "new rigol..." people made measurements of max rise/fall time in this scope, you can look at these, also in 3ns rise time your scope got only 3 points to make a decision...
- Is there a way to move the Cursor box (that shows AX, AY, BX, etc) when in Manual Mode? It sits in the top left hand corner and sometimes I'd prefer it was in the bottom half somewhere.
No.
- Is there a way to count the number of trigger events (other than using Measure>Counter and counting pulses on the Trigger Out BNC port on the back with a spare channel). For example, I want to leave the scope unattended for a period of time and count the number of triggers over, say, a 12 hour period (to get a feel for how commonly a triggering situation arises).
You can do it indirectly, using any measurement with statistic on in difference mode, there is Cnt , it is not precise but only option without trig out, it's cheap scope and lack some features...
Also use full screen on scope for waveform, because it's digital scope, half screen = half resolution of adc.