A signal that does not use the entire screen height does not use 8 bits. 8bit is the entire vertical visible area in best case. They can be stretched to more than the entire screen, but you cannot use all 8 bits on a limited area of the screen.
The problem is that Siglent uses a very primitive anti-aliasing algorithm (smoothing oblique lines), so the signals appear so stepped. And this does not depend on the number bits of ADC, but only on the visualization algorithms. It is quite possible to fix this by software, and I am almost sure that the processor performance is sufficient for this fix. But will Siglent do this?
I agree about the user interface. This is the most annoying thing of this scope. Perhaps, if I had the opportunity to work with the device for a couple of days (just work, not play ) - I'm not sure if I would buy it. I have to rotate the knobs constantly, and I personally use history quite rarely. Like most of us probably.
There are also complaints about the quality of rendered waveforms. Despite the rather large screen resolution (1024x600), the waveforms are rendered with the quality inherent in a 320x200 screen. Looking at the screenshots at high magnification, you can see that this is the case. There is a maximum of 16 gradations of brightness, but most likely 8. Antialiasing is very primitive. Therefore, even a pure sine wave appears to be "jagged" on the screen, as it is rendered at very low pixel and brightness resolution. In addition, Siglent for some reason, uses white color mixing with the channel colors to "increase brightness", which makes it a "dirty color" effect and impairs the already not best visibility of the waveforms.
For comparison, the waveform rendering of Siglent SDS2000X+ and the old Rigol DS2072. Guess where who is? )))
It can see that Rigol have more artists and Siglent have more engineers.
But digital scopes work differently. If your signal is not stretched to full screen, it does not use all 8 bits, but less. For example, if the signal has a span of 4 div. out of 8, then it uses only 7 bits. If 2 divisions - 6 bits. Etc.
About these images.
It can see that Rigol have more artists and Siglent have more engineers.
One ADC data value is 8 bit. One step on screen is exactly 2 pixels If there is data value 9F there is data value 9F and not data value between 9F and 9E. Siglent is test and measurement image, not picture artists camera or movie display. Even if it is bit rough for eyes but truth must not hide. Siglent is mapping every sample to display and every sample need be exatly visible. So that do npty need guess if there is true data byte or if it is image rendering artist produced or hided because it is not nice to look.
Sorry but if data is rough it need also show it is rough and not hide truth.
About these images.
It can see that Rigol have more artists and Siglent have more engineers.
One ADC data value is 8 bit. One step on screen is exactly 2 pixels If there is data value 9F there is data value 9F and not data value between 9F and 9E. Siglent is test and measurement image, not picture artists camera or movie display. Even if it is bit rough for eyes but truth must not hide. Siglent is mapping every sample to display and every sample need be exatly visible. So that do npty need guess if there is true data byte or if it is image rendering artist produced or hided because it is not nice to look.
Sorry but if data is rough it need also show it is rough and not hide truth.
I have to disagree here, rf-loop -- this is what dot mode is for. If you want to see the raw data in that manner then dot mode is what you need to be using.
For interpolated data the results should be as smooth as the display will allow, as long as the resulting smoothing is not itself incorrect relative to the selected interpolation method.
In fact, done right, the resulting smoothed curve could even give you a visual representation of the uncertainty in the data, since smoothing (antialiasing) of a curve generally will also use lower intensity pixels as part of the process. After all, scaling the actual value in order to place it on the screen is not guaranteed to land it at an exact (non-fractional) location on the screen, and save for specific circumstances, it's incorrect to claim that each point in the waveform will always land squarely on a corresponding location on the screen.
And we disagree with you.
Pixel anti aliasing would serve no purpose except eye candy and would yield visually much higher displayed noise (thick trace).
Also, when display is running, you get exactly that pixel anti aliasing effect, by virtue of display intensity gradation in persistence. Only stopped it shows only last (single) capture that is single pixel wide.
Signal with 256 discrete values is never displayed in 64 pixels height in normal (fullscreen) mode.
Not sure if this applies to the SDS 2XXX series as well, but the SDS12XX is missing a feature for alternate triggering across the channels.
e.g.: I want to trigger from CH1, sample and draw, the trigger from CH2 (or 3,4), sample and draw.
This is very useful when you want to compare signals that are related but not time synced. Think delay lines, phase shifts, that kind of stuff.
Hell, my old PM3070 CRO can do that, and you can even select a different timebase for CH2. A dual time base/trigger should be relatively easy to implement in a digital scope.
After spreading it on several threads, I´m try to make a summary of what "our" two new siglent owners here concerns and their "issues" with the scope, because they aren´t bugs.
But it turns out do as if the scope has serious quirks, which is definitely not true.
So we should use this thread here only for wanting nice to haves....
Wanted features (because it´s no bug):
- Faster response of the knobs in general.
- Doing whatever you want with the scope settings without nuking the history.
The aliasing thing is no bug also, we shouldn´t use magnifying glasses for looking at the scope screen..
Not sure if this applies to the SDS 2XXX series as well, but the SDS12XX is missing a feature for alternate triggering across the channels.
e.g.: I want to trigger from CH1, sample and draw, the trigger from CH2 (or 3,4), sample and draw.
This is very useful when you want to compare signals that are related but not time synced. Think delay lines, phase shifts, that kind of stuff.
Hell, my old PM3070 CRO can do that, and you can even select a different timebase for CH2. A dual time base/trigger should be relatively easy to implement in a digital scope.