SDS800X HD issues and tips

[eTobey]

I just want to post my top list about the bugs/issues i found. I do this in this section, because certain individuals (mostly fanboys) will probably be offended or create a lot of "noise", if i post this in the other section.
I try to keep this, the links, and the linked posts updated.
Anyone is welcome to send me a message if one wants to add things to the list OR to confirm issues and send them to Siglent, if those are of particular importance.

New, or updated issues are at the end of each list.


Issues / bugs:

Ghost traces: (They do trigger the mask test!)
https://www.eevblog.com/forum/testgear/sds800-x-hd-persistence-mask-test-issue/msg5762649/#msg5762649

Cursor measures screenborder
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5766285/#msg5766285

Moving gate A, changes gate B unintentionally.
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5523604/#msg5523604

Changing sample rate changes timebase:
Decreasing sample rate (fixed setting) changes timebase, but does not set the timebase back to the initial value, after setting the sample rate to its initial setting.
(1us/div goes up to 500ms/div, but only back to 5ms/div, after the sample rate has been set back to its previous value)

Persistence traces dissappear when selecting only a channel to display its scale:
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5760405/#msg5760405

Measurement measures wrong edge:
https://www.eevblog.com/forum/testgear/sds800x-hd-featureimprovment-disscusions/msg5470300/#msg5470300

Measurement on less points than acquired (presumably), is not indicated.
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5527156/#msg5527156

Trigger rate decreases significantly when sample rate is decreased.
ALSO in sequence mode!
https://www.eevblog.com/forum/testgear/why-is-the-trigger-rate-of-my-scope-(sds814x-hd)-changing-in-an-unexpected-way/msg5659165/#msg5659165

Mask test save issue
It has internal memory, and LAN, but mask test will only write to a USB disk 

Color of math channels changes
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5744691/#msg5744691
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5770627/#msg5770627
Last too pictures:
https://www.eevblog.com/forum/beginners/measuring-the-same-signal-in-different-ways-result-in-different-waveforms/msg5755633/#msg5755633
Color changes on multiple timebase settings. Its a complete mess.
Workaround:
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5747345/#msg5747345

Math average lost
Math average is lost when changing timeposition (Yes, even in stop mode)
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5750033/#msg5750033

Mask mess
Creating a mask scales and moves trace vertically / Introduces errors in the scope that may require a reboot (scales messed up)
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5651161/#msg5651161
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5674527/#msg5674527

Trigger level indicator wrong in zoom mode
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5469121/#msg5469121

Vertical grid not aligned
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5527363/#msg5527363
https://youtu.be/ITbbYUFg6CU

History time wrong
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5660701/#msg5660701

Missleading accuracy of measurements (measure mode)
Digits of ns are shown, when accuracy is only +- 1us for example (not necessarily the case). (In stop mode it should measure all samples without reducing?)

Decode wrong data on low scale
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5742393/#msg5742393

Selecting math channel sometimes doesnt work
Although the click noise can be heard, and the mouse pointer is moved onto the button.

Save button setting
"Save to" setting for the "save button" is overwritten when saving some different values/waveforms/... with using the menu. ALSO: normal save menu setting (not for button) is overwritten by the save type of the button.

SCPI command clears scope
When retrieving data with :WAVeform:DATA?, the captured traces dissappears from the screen.

No fixed offset zooming on math channel aka non consitent settings
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5762331/#msg5762331

Decoding hidden
When there are only very view decode items, the list hides them, when the timebase was moved and there were more entries in the list before. ("two issues decode list.jpg")

Artefacst from SCPI usage
Trace artefacts appear, when SCPI is used. ("Artefacts when using SCPI.png")

Cursor measurment messed up after use with automated measurements
Curser value „nans“ after having used curser on measurement ("SDS824X_HD_PNG_218.png")

Scope crash on SCPI use
When using SCPI command on non activated features, the scope will crash.

Webinterface does not show disconnection from scope (does disconnect for unknown reason and without attempt to reconnect)
The webinterface just shows the last screenshot, and is thus missleading, as if a test is still working for example.

File letter case issue
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5818727/#msg5818727

Sorting issue (its a mess):
See last part of the following post, especially, if your native language is not german or english: https://www.eevblog.com/forum/testgear/how-common-is-this-sorting-order-in-scopes-and-linux/msg5819217/#msg5819217
- Screenshots have bad filename format, so "PNG_99" will always be the last one, even if there is a "PNG_500".
- "B" comes before"a" (notice the case) (See "Sorting issue 1.png")
- (if NTP sync fails, files have the wrong date, therefore you cant sort filenames for their date then)
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5813477/#msg5813477

Search event navigation issue (slow and omitting events)
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5820229/#msg5820229


General tips and workarounds:

Fine adjust for math channels:
It can NOT be set with the knob, but it CAN be set via the menu.

Saving lot of things? Beware of the save button!
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5776675/#msg5776675

Stop drops capture and measurement fails workaround:
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5783215/#msg5783215

Overlaying labels issue:
It can be somewhat overcome, by setting offsets, and then realign the trace vertically. In case you want to compare: all have to be the same scale, and the one without offset has to be activated in order to show the proper vertical scale (for all channels). One has to keep that always in mind, or otherwise one would be misslead.
(See picture attached "Labels with offset")

Rollmode Traces vanish after they filled the horizontal scale:
Use Auto trigger mode, and they will stay. (In normal mode, the screen is cleared on a trigger event.)

Mask test mess (its buggy, and the following tips may not work, or still have quirks):
- when manually creating a mask, and loading it, it may likely create errors, that will persist, and affect the trigger or level of traces. Its a good idea to restart the scope after using the mask test.
- Starting the mask test (only works in this particular order): Enable "operation", and then start run mode, or stop and start run mode.
- Moving the vertical or horizontal position will prevent any further detectiong of fail events (at least with a manual mask). Restart as above is needed.


Virtual feature scripts for SDS800X HD (and probably other scopes):
https://www.eevblog.com/forum/testgear/scpi-virtual-feature-fixed-measurement-gates-siglent-sds800x-hd-and-the-like/

Siglent SDS802X, SDS804X, SDS812X, SDS814X, SDS822X, SDS824X, Hack, 12-bit, Scope, oscilloscope, SDS 800 X HD

[exe]

checking forum attachments

[tyeth]

Hey, thanks for compiling this list.
Is there any chance these can be verified against different firmware versions, i.e. we can track which have been resolved and also which FW is needed for the fix (or at least "should be fixed in latest")?

Not an easy or instant thing, and maybe there is a better place for it, but this was where I stumbled upon first...