So what is the current status of the Freeze Bug and the Math Bug ?
Did Rigol acknowledge them?
Did the latest software update fix them?
If "not" - when is the next version due ?
Freeze Bug: As far as I can tell this bug is associated with Boot Version 0.0.1.2. Perhaps not all scopes with that version will freeze. The newer Boot Version 0.0.1.3 does not seem to have this particular bug. If you have the earlier Boot Version and the bug, the rest of the firmware doesn't matter, it will still freeze when the conditions are met even with the latest SP2 firmware update. There does not appear to be any way for the user to update the Boot Version -- that I know of. I have asked Rigol USA several times about this but never got a real answer. I returned my old scope with the Freeze Bug to Rigol USA in return for a newer one with Boot Version 0.0.1.3 but have not heard anything from them about it. As far as I can tell all scopes that have the Freeze Bug are using Boot Version 0.0.1.2. I had both scopes (BV 0.0.1.2 and BV 0.0.1.3) for about three days and tested them side-by-side under identical setups and conditions.
At the beginning of this thread we did not know how to display the full System Information screen which shows the Boot Version and other scope data, so we didn't collect that data for most of the people who reported freezing. The procedure to do this is to press _very fast_ the keys in the Trigger section: Menu, Menu, Force, Menu, and then Utility>System>System Info. This should bring up a complete System Information screen. If it doesn't work at first, press the key sequence faster.
Math Bug at 500 ns/div: I've heard nothing from Rigol about this bug, and it is not fixed by the latest software update. At 500 ns/div with a Math trace displayed that uses two-trace math like A+B, A*B, etc. the Math result is offset horizontally from the input traces and appears to be at a slightly different horizontal scale.
Measurements Fail bug: I reported this to Rigol USA as soon as I found it, and they were able to reproduce it immediately on their scopes. This one seems to have been introduced by the update to latest firmware SP2; at least I never noticed it on earlier versions. It may also be related to Boot Version 0.0.1.3. If you have a Math trace running, all Measurements will simply stop working at some random time, and cannot be restarted. You have to power-cycle the scope to get Measurements back. The "work-around" is to not display the Math trace continuously but only have it up for a few seconds while needed. Still, the Measurements may stop working in those few seconds since the time-to-failure is random. All Measurements stop working (except Hardware Freq. Counter), not just the ones you may have displayed at the time, and power-cycling is the only way I've found to get them back working again.
All these bugs are there whether the scope is "unlocked" to 100 MHz with all options, or "virgin" stock 50 MHz with no extra options.
When is the next firmware version due? I don't know. Maybe Rigol knows.... certainly there are plenty of things that need fixing. The SP2 firmware introduced the Measurements Fail bug, the Pluses spelling error, the occasional pulses miscounting, and the really bad slowing down of certain control responses like Vertical Positioning and others. And it did not fix the Math horizontal error at 500 ns/div. It did fix a few other things that were annoying to me, and that's good.
Rigol really should make it possible to easily roll back to earlier firmware versions, so that people can try new firmware releases and if they don't like the effects they can go back to earlier versions. I think many people are unhappy about the slowing down caused by the latest SP2 firmware. That doesn't bother me as much as the Measurements Fail bug though. Not being able to roll back to earlier updates is a real "fail" on Rigol's part, as is not providing current Boot Versions in update files.