R6.0.9 seems to work very well in many areas, but I feel like I am pushing the envelope (or just pushing my luck) at a few points:
1) When I increase the horizontal time scale beyond 5mS/div, the numbers change but the waveforms still look like they span about 50mSec across the 10 divisions displayed. This happens when I have the number of samples set to 100MS. If I reduce the number of samples without changing the timebase, I see the waveform start to expand, even though the horizontal axis labels have not changed-- I am "zooming in" but the timescale isn't updating.
2) Starting at 5mS/div and 100MSamples, I see 3 video fields (which is correct). The "Properties" window shows 50 million samples at 1GSPS. When I increase the timescale to 10mS/div, "Properties" now shows 50 million samples at 0.5 GSPS, which is fitting, but does not agree with the display, which still shows 3 video fields. (In the US, each video field is 16.7mSec.) Zooming in, I find all features of the video shown with twice the correct timescale.
3) When I dump a text file, I find that the timestamp carries enough digits to give 1nSec resolution, but the last digit is always zero...
If I immediately switch to 5mS/div or more, the triggers don't work, the sampling is messed up, etc as described above. BUT if I set up trigger first, then gradually increase the time scale, it looks like it is working quite well.
Maybe I should capture the settings good versus bad for comparison?
Since I can't reproduce the error (which was very repeatable before), I have to assume something has changed. Perhaps the PicoScope module was not reinitialized after I upgraded the R6 software-- does the software download code into the scope module? (I have since cycled power.)