Regarding Restore Defaults in the Pre Boot Menu, I believe this is a pretty important step when downgrading firmware as the stored settings are not necessarily backwards compatible and could cause weird behaviour.
- After my testing, i disagree (i was off that opinion 2 days ago as well, I'm off a new opinion now)
[snip]
I wouldn't worry about it, I did this several times
Sure. You may not see any problems between those two recent firmware releases you tested with, but that is quite a limited test especially if you aren't using the scope feature between versions in such a way that defaults get changed.
There have definitely been issues in the past when going between various releases without defaulting the settings. So a user who has an unit that they've been actively using with older firmware is more likely to have a problem.
Not a big deal, it just wasted some of my time when I encountered it and had to got back to that menu. And in my case I was upgrading not downgrading - I believe from 0A.01.03.00.01 to 00.01.03.03.00.
Similarly, it is pretty important to run the self cal after an upgrade (and warm up). The scope will work without it, but may not meet specifications. I haven't watched all your videos, but I expect you cover that.
This is what i suspect, about the MSO500, However it's also NOT supported on the MSO7000, it starts to be supported on the MSO8000.
I thought I saw it was available for the MSO7000, but just looking now at Rigol site & datasheets I can only see it listed as option "MSO8000-JITTER".
Clearly they tried to get it working on the 7k platform, but gave up. They just left the common code in there as it is effectively disabled without a license (unless hacked).
I doubt it is worth wasting any time on it - others have already tried with limited success.
See
https://www.eevblog.com/forum/testgear/mso5000-jitter-and-eye-diagrams/And
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2656659/#msg2656659