5 bugs at once:
These are the only known bugs left in the current FW?
1. Measurement freeze - I have not seen this. Is there a robust way to facilitate the issue or some precondition?
2. Math offset - check, with 500 ns period and trace averaging enabled; otherwise, OK.
3. RMS measurement incorrect - check, with multiple channels on. I think Ch1 is always correct, and all other channels are correct individually. Someone mentioned something like SW cross-talk as possible cause?
4. Pluses spelling - is this feature entirely new in the latest FW version? That's the way it seems from the release notes.
5. Pulses miscounted - check, I forget if this is related to 500 ns rate or if there are any preconditions. Again, a new feature?
Thanks!
No, these aren't the only bugs left.
It's not easy to display the slow control response in a still image, but many people who have loaded the SP2 firmware have noticed this.
It also can take a _long_ time to save a screen image to a USB stick, especially if the scope is not Stopped before saving. The more channels and functions in use, the longer it can take to save the image (but this does not seem to be the case when using DSRemote over a LAN connection to save a screenshot.)
Something that really is annoying to me is that the FFT function display resets the Center Frequency, Hz/Div, etc. when switching Mode from Memory to Trace (or the other way around.) The new firmware added the Memory option to the FFT which is nice, but they forgot to have it keep its display settings when switching back and forth between Memory and Trace.
Sometimes the Hardware Frequency Counter delivers strange results like double or half actual frequency, depending on Trigger Level setting, for certain waveforms where it really shouldn't have any trouble.
I don't know if CH1 RMS is "always correct" when other channels without inputs are showing large RMS values. I need to research this bug further.
To reproduce the Measurements failing, use two channels and activate a Math trace, like A+B etc. Then turn on some measurements. To keep track of how many updates happen before they stop working, select the Statistics ON and in Stat. Sel. choose "Difference" which will show the update count. I have seen the measurements stop in just a few updates, or sometimes it takes thousands of updates; as far as I can tell the time is completely random. Yes, I reported this bug to Rigol USA back when I first encountered it and they were immediately able to reproduce it on their test scopes, so they know it's really a bug, not just in my unit. Once the displayed Measurements stop updating, then _all_ H or V measurements no longer work and the only way to get them working again is to power-cycle the instrument. The "workaround" which is hardly satisfactory is to keep the Math trace set up but turned OFF except for brief periods when you want to look at it. Still, this doesn't always work and if you're unlucky the Measurements will freeze during the time you have the Math trace turned On.
Yes, the "Pluses" spelling error and indeed the Pulse and Edge counters came along with the latest firmware. No, the miscounting doesn't seem to be related to the 500 ns horizontal rate and doesn't always happen.
There may be more bugs, or "features", that I've not listed or encountered yet.
My scope has Boot Version 0.0.1.3 and I see that current scopes are being shipped with a Boot Version 0.0.1.4. I don't know whether this change in Boot Version affects any of these bugs, or if the Boot Version actually does anything besides starting up the instrument. Somehow I think that it does have some additional effects but I can't prove it.