bitseeker -
I do not see any setting, other than choice to apply measurement to "screen"
or "cursors", to control sample set. I have it set to screen, and cursor measurement
looks correct. Stats does not.
Go to Measure -> Statistic -> Stat.Sel. -> Difference to display Cnt (instead of Min/Max), which is the number of samples collected for the currently displayed statistics. Then, you'll be able to confirm that it's sampling during the entire display persistence period and that it hasn't reset for some reason.
If the statistics were not examining all sweeps, even if this were true, over time it would,
all things being equal, get a sample for all possible values. Eg. the jitter would produce
multiple samples for same point in time, over long acquisition periods. I have done hours
to see see if the measurement would converge, does not.
Agreed. With a sufficient number of samples, the stats should be closer to the cursor measurements. Turning on the sample counts display will help confirm that you're getting lots of samples.
Also, you can go to Measure -> History -> DispHistory to turn on the measurement history followed by Measure -> History -> Disp Type -> Table to see the values that have been collected. That will enable you to confirm, for example, that the scope got at least one of the Min and Max values that you measure with cursors.
These are not a solution, but they may be helpful in determining if the data is being captured as expected.