My scope updated just nice with the latest version, including the self-calibration afterwards. The calibration result was so far the best; earlier the offsets and gains were clearly "about there", now "almost or exactly there". Could be just lucky case this time. (I didn't assume that scopes would be precision instruments anyway, except on timing.)
--
In general, some questions/comments/things I've been collecting (for way too long)...
Is the scope supposed to remember all previous settings after reboot? It seems to mostly do so (i.e. most settings and most of the time), but randomly some settings are "randomized". So far I have noticed occasional randomizations on at least trigger type and various trigger parameters (like levels), and wavegen's waveform. Wavegen's freq has twice now been 750Hz after reboot (when I left it at 1kHz). These happen seemingly on almost every reboot, not every parameter, but at least one on each reboot. It might depend on how much of things I changed during the operation, and uncertainty on if I can remember what the setting was before reboot (e.g. did I really leave the trigger level at some value that makes no sense with what I was measuring). One thing happens I guess always: if I have overridden channel probe factor(s) (i.e. not using auto-detect), after a reboot those settings seem to always reset to auto-detect. Bugs? Undocumented features?
Would be nice (at least for me) if a menu
selection that uses the adjustment knob would keep that knob active the same way as menu (numeric)
value adjustments do. That is, value adjustments seem to not "time out" the knob (one can wait a minute and still adjust the value), but selections time out quite quickly. At least I use the default action of intensity (or whatever) adjustment pretty much never, but I am constantly making a selection change, looking at the view for a moment, and try to select another choice... only to end up tweaking the intensity instead
However, this would then benefit from some way to deselect the current menu item (return the knob back to intensity adjust) without causing changes in the selection. The current way of clicking the menu button first to select/activate it, then to step through the values makes it not possible to have another push for deselect. (I have more to say about this, but I need to check / massage the ideas a bit more first...)
On wavegen, when selecting an arbitrary waveform that has not been loaded (e.g. accidentally turning the knob the wrong way), the wavegen gets otherwise disabled, but the waveform selection stays active. The latter is good, the former is not. Once the selection is adjusted back to something that works (say, sine wave), the wavegen is still kept disabled, and it has to be manually turned back on. IMHO, it should just stay (logically) on (even if not driving anything), so that when a working waveform is selected again, it will automatically start also driving again etc., as if that visit to the "bad" waveform never happened.
10:1 probe, normal modes (default stuff), trigger at normal (and 0V), probe shorted, 10mV/div, showing about 10mV of noise (as expected). Adjusting position of the channel moves the offset pointer/trigger line smoothly (like 1 pixel at a time, 0.20mV per step), but the shown signal does NOT move up/down at all (it is still updating the data otherwise as expected), until about 11/12th step, when it jumps to the new height on the display. However, if trigger is set to single, showing the one span of noise, that signal view does move smoothly with the position adjustment. I would have expected that normal mode view to move smoothly with the position adjustment, too. Sure, it is mostly noise, but e.g. the average level of the "signal" could be looked at, but with that effect it is not always shown correctly. Explanations? Bug?
(EDIT: for easier and clearer version of this:
https://www.eevblog.com/forum/testgear/siglent_s-new-product-sds2000x-series/msg1891271/#msg1891271)
I did manage to get the scope into a state where showed wavegen's sine output with pretty darn horrible stepped view (like 4 bit ADC/DAC or something). Adjusting things on the wavegen side seemed to solve this (after another short glitch with stuck waveform type), so I guess it was some sort of temporary glitch, and I was not able to get it like that again. Attached a screenshot for giggling (normally it would look a nice smooth curve)... (EDIT: and ignore that filename "16bit-", brainfart on mixing 16 levels and 4 bits.)
--
Referring to the earlier comment of mine about the really crappy adjustment knob behavior ("acceleration" effect):
The behavior ("acceleration") has indeed improved a lot. It still has some minor issues left, e.g. adjusting to lower value seems to happen (in certain value ranges) faster than to higher value. But when it still makes an unexpected fast/large change, the change isn't that drastic, and it is a matter of a second or two to get back on track, instead of the old version's exercise in frustration. At least I didn't bump into old style of behavior during the short testing I made, which included some cases I had specifically made notes of for repeating/testing.
My other earlier comment about some minor trigger problems.. I could not find my notes about those (perhaps I wrote them to the paper related to the project at hand, instead of the notes about the scope), so, will have to return to this triggering topic when/if I either find the notes or bump to the issues again.