Ok, been using the scope 2 weeks - here is a current list of known firmware annoyances/problems/bugs (leaving out unimplemented features - or physical design issues):
1) The scope appears to first clear the display then restart the sweep whenever moving the waveform vertically, changing the vertical or horizontal scale, moving trigger position, turning on/off channels, etc. At faster timebase settings this isn't much of a problem, but when doing any of these things with divisions >=50ms, the scope can feel unresponsive. I'm wondering if this might be attributed to what I'll call the 'Owon effect' (having just one routine for something, no matter the memory size) - because the sample depth settings do not change the response time. It's as if the scope is always dealing with 56MPts in this regard. Maybe it has to act this way in case the memory is being used as history ('Record Open'); i.e. the memory is a third dimension to any sample size.
2) The way the scope handles intensity grading in delayed sweep mode needs some work - it doesn't appear to be the same as if you just stop the sweep and zoom in via the horizontal scale (I can't quite figure out why this would logically happen). Sometimes the grading is just too light to see well and you need to turn up the intensity settings.
3) When you turn on tracking cursors (if all cursors off), the measurement window doesn't appear. You can workaround this by cycling through (via the menu button) to manual cursors and back to tracking.
4) X-Y channels are reversed.
5) Self-calibration will automatically expire any trial options currently running.
6)
[Added 09/11] AUTO routine sometimes fails to latch onto signals. I'm not sure about the exact circumstances - member EV says that it has to do with 2 channels, but I'm fairly certain it has worked for me with 2 channels sometimes (and others not). Perhaps someone can test and figure out the parameters of this bug.
7)
[Edited 09/12] If you use the FINE horizontal scale adjust at scales >=20ms (Press -> [Horizontal] Menu -> ScaleAdjust -> Fine), the max/min horizontal trigger position becomes locked to the next lower major division*10/14 - instead of staying 10x/14x of whatever the actual setting is. This can cause the trigger position to jump and become frozen (with the 'Parameters overrange!' message) in the middle of the display. See
this message for more details.
Anyone reading this with a DS2000 or DS4000 that can point out something else, feel free to chime in.
Edit (09/11): According to Rigol, #1 is just because they happen to do the restarting of the sweep the opposite way (first clear - perform function - then redraw) from other manufacturers, who leave the old waveform on the display when you move it, change scale, etc. - which is how I expected they'd respond. Well, the other way is better I think (whether they are equivalent or not - it just
feels more responsive). Anyway, hopefully if enough owners complain about it, they'll change it eventually.
Edit (14/12): I'm moving this entire list to the first post of the thread to make it more easy to find.