The link http://beyondmeasure.rigoltech.com/acton/fs/blocks/showLandingPage/a/1579/p/p-0019/t/page/fm/0 still contains the old 00.04.04.04.03 version and a release memo of a version 00.04.03.02.03 of 2015...that's why I haven't tried that one.
The upgraded firmware for a DS1Z Series Scope can be downloaded from here
DS1ZUpdate.ZIP
What was actually fixed? I haven't updated in a couple years (maybe 04.04.04.03), so any reason to do so?
Same here. Updated to 00.04.05.02.02 (aka 00.04.05.SP2) and everything looks fine.
ie. Rigol has just given everybody the options for free. Anybody who installs this firmware will get them, even the oldest customers.
Figured... Never saw it explicitly stated in my reading around, but was starting to get the idea. Kind of expected that setting the DSER would overwrite the original, but that's what happens when you expect vs experiment...
I take it that having the 500uV feature on doesn't cause any problems, other than unreliable vertical readings when you use it? I'll still clear it out, of course. Probably recal again too, so it doesn't try to cal the "500uV" setting.
Off to do some Telnetting...
500uV/div is very handy, especially when the scope is in high resolution mode, same for the averaging mode ("Acquire" -> "Mode" set to "Average") when the signal is very small but repetitive.
As an example measuring very small resistances with the oscilloscope, milliohms range, for a contact resistance, or the internal resistance of a battery, etc):
https://www.eevblog.com/forum/projects/oscilloscope-with-trace-averaging-as-a-lock-in-amplifier-(rigol-ds1054z)/
I have the 500uV/div option since the very beginning, and it works very well, despite the urban legend that it's bad. It's a software option. It brings no damage and no inconvenience to any other options. Can be removed later if not wanted.
Is anybody up for a definitive test? Can you apply a small voltage to one of the inputs then do a self-cal and see if the 500uV range changes?
(I don't have my DS1054Z any more so I can't do it)
Is anybody up for a definitive test? Can you apply a small voltage to one of the inputs then do a self-cal and see if the 500uV range changes?
I'm not curious to find that
500uV/div is very handy, especially when the scope is inhigh resolution mode, same for theaveraging mode ("Acquire" -> "Mode" set to "Average") when the signal is very small but repetitive.
As an example measuring very small resistances (millioms range) with the oscilloscope, like measuring a contact resistance, or the internal resistance of a battery, etc:
https://www.eevblog.com/forum/projects/oscilloscope-with-trace-averaging-as-a-lock-in-amplifier-(rigol-ds1054z)/
I have the 500uV/div option since the very beginning, and it works very well, despite the urban legend that it would be bad. It's a software option. It brings no damage and no inconvenience to any other options. Can be removed later if not wanted.
Does the v00.04.05.02.00 2021/07/24 update affect the 100MHz limit?
Yes, this is normal. you are triggering on channel 1, so all the rising edges get shown on top of each other. If you switch to any other channel and switch the trigger source to the same channel, you will see the same exact thing.