Siglent SDS2000X HD, missing Features and Bugs

[tautech]

Maybe there are sporadic problems with the autodetection of the probe.

Or the probe is faulty.
Have you checked by using other probes on the same channel ?

[Martin72]

Hi Rob,

No, because the freeze thing was a one-time thing - before and after that I didn't have such a crash.
The thing with the 1x/10x, I had however more often, mostly if the Bodeplot mode was terminated, then one channel remained on 10x, the other on 1x - although both were before on 10x.
Maybe this will be resolved when the firmware update is released at some point.
In principle, you have an "old" scope with a firmware version from almost a year ago.

[Martin72]

Here is a current example regarding the error of not being able to remember the thresholds.
"Yesterday" the scope was set to 1.70V, today directly after power on the thresholds are at 7.1V and 4.1V.
Which makes no sense at all, at logic levels.

[teddychn]

"Yesterday" the scope was set to 1.70V, today directly after power on the thresholds are at 7.1V and 4.1V.
Which makes no sense at all, at logic levels.

This should be corrected. No one would want to readjust the logic level every day before using the logic analyzer.

[JPortici]

Here is a current example regarding the error of not being able to remember the thresholds.
"Yesterday" the scope was set to 1.70V, today directly after power on the thresholds are at 7.1V and 4.1V.
Which makes no sense at all, at logic levels.

That is probably the same problem that is present in the SDS5000X.
Disconnect the probe, see if defaults to 1:1 (or to anything else than what the probe is)
If this is the case, there's your problem.
Something bizarre happens during initialization: I don't know how the thresholds are saved internally, but the data gets mangled when the probe type changes during boot.

The scope will start with a preset probe ratio for the channel (and all the values that are tied to that channel will be applied with that scale). Then the autodetect will detect the probe and adapt all the values to the new scale.

scope saves thresholds in FORMAT B (because probe is connected) then on boot loads FORMAT B into FORMAT A because channel is in its default state then autodetect and FORMAT A goes into FORMAT B

The problem here is that autodetect overrides the probe format, but doesn't store it

[rf-loop]

Here is a current example regarding the error of not being able to remember the thresholds.
"Yesterday" the scope was set to 1.70V, today directly after power on the thresholds are at 7.1V and 4.1V.
Which makes no sense at all, at logic levels.

I can not repeat this. (SDS2504X HD   FW: 1.2.1.1)

1st image. Setup as it looks like in your image.

Shutdown. 

Power on again.

2nd image.

I have repeated this many times, always result is same.




 1.


 2.



ETA:  When I write this msg  I have not read @JPortici.  His observations and suspicions may be significant also here.

[teddychn]

Here are my wishes for the SDS2000X HD:

1. Add an option for a comments field when printing or taking screenshots.

2. Channel labels can become difficult to distinguish when they overlap with each other. It would be great to either stagger the overlapped labels or display them elsewhere, perhaps in a side pop-up box or anywhere else on the screen.

3. Include bandwidth information alongside the ERES message.

4. Enable customization of XY chart colors. The dark blue is hard to read in screen captures.

[2N3055]

Here are my wishes for the SDS2000X HD:

4. Enable customization of XY chart colors. The dark blue is hard to read in screen captures.

Can you explain this, please?

[rf-loop]

picture link from:
https://github.com/microsoft/WSL/issues/930

I believe that everyone who has, for example, designed important cockpits / control rooms in industry, knows the basics of visual ergonomics (and other human ergonomics and how body and how all the senses, sight, hearing, touch, muscle control and position sense and fine motor skills work as well as one have to know a little about behavior as well. It would be good for measuring device manufacturers to know these things too...including Siglent also,  least the basics of these things.
But who would teach these things if they themselves don't feel like studying. In the short term, stock prices on the stock exchange are more important...

RGB  B alone on Black background is problematic in many situations..

[teddychn]

Here are my wishes for the SDS2000X HD:

4. Enable customization of XY chart colors. The dark blue is hard to read in screen captures.

Can you explain this, please?

This is a screenshot from the SDS2104X Plus, but I believe the HD should be similar. I find it challenging to me to distinguish the vertical blue line in the picture. The SDS2000X HD allows you to assign trace colors, and I wish the XY chart could be customized in the same way.

By the way, Siglent should include bookmarks in their PDF manuals; it would make them easier to use.

[rf-loop]

Also same for digital (LA) input signals.

[tautech]

Also same for digital (LA) input signals.

Should chance as I proposed. 

[2N3055]

Here are my wishes for the SDS2000X HD:

4. Enable customization of XY chart colors. The dark blue is hard to read in screen captures.

Can you explain this, please?

This is a screenshot from the SDS2104X Plus, but I believe the HD should be similar. I find it challenging to me to distinguish the vertical blue line in the picture. The SDS2000X HD allows you to assign trace colors, and I wish the XY chart could be customized in the same way.

By the way, Siglent should include bookmarks in their PDF manuals; it would make them easier to use.

Here is a snapshot from my scope. On screen blue trace is much brighter, lighter blue than on this image. That is why I was confused, I have no trouble seeing it.
But I think your request is good one, it should be user configurable..

As a side note, to make it easier to read (if you have problem with blue) enable Color grading in Display menu... Maybe that helps a bit..

[Martin72]

Hi,
Here a clip about the threshold thing:
https://drive.google.com/file/d/1srETzAoYwZZwdh1fOC-6uWFfBZE9bN9M/view?usp=sharing

(Meh, why is the video quality so bad...(EDIT: Because it´s 360p,can be changed to 1080))

Thresholds changing also when you re-boot the scope.
Threshold-Level is different from channel to channel, for example Ch 1 is falling back to 8.2V, Ch2 something between 800...833mV, Ch3 14.2V, Ch4 I didn´t test so far.

I can not repeat this. (SDS2504X HD   FW: 1.2.1.1)

Got the same FW...
I will test it again tomorrow, but then without the probes - Possibly the autosense function messes the whole thing up.
(For example, I currently have all probes on the scope and after each start it "tells" me that it has detected a probe on channel 4, although I had not disconnected and reconnected them).

[JPortici]

Hi,
Here a clip about the threshold thing:
https://drive.google.com/file/d/1srETzAoYwZZwdh1fOC-6uWFfBZE9bN9M/view?usp=sharing

(Meh, why is the video quality so bad...(EDIT: Because it´s 360p,can be changed to 1080))

Thresholds changing also when you re-boot the scope.
Threshold-Level is different from channel to channel, for example Ch 1 is falling back to 8.2V, Ch2 something between 800...833mV, Ch3 14.2V, Ch4 I didn´t test so far.

I can not repeat this. (SDS2504X HD   FW: 1.2.1.1)

Got the same FW...
I will test it again tomorrow, but then without the probes - Possibly the autosense function messes the whole thing up.
(For example, I currently have all probes on the scope and after each start it "tells" me that it has detected a probe on channel 4, although I had not disconnected and reconnected them).

Disconnect probes. set channels mode to 1:10, then retry you are describing exactly the issue i have with the SDS5000X

[Martin72]

Makes me so curious, I´ll test it in the next minutes..

[Martin72]

Bingo...

Disconnecting the probes, setting all the channels manually to 1:10, then adjusting the decoder threshold-levels.
Re-booting the scope, now the threshold values remain.
Siglent, we have a bug in the autosense circuit (programm?)...
And this seems to affect not only the level setting for the decoding, because I had already told early that when fall back from the bodeplot mode a channel is set back to 1:1, although a 1:10 autosense probe was connected and recognized as such before starting the bodeplot.
Or how the scope froze for me for the first time a few weeks ago, with the message that it had detected a probe on channel 3, although the probe was already connected.
So it seems to influence many things, a rather serious bug.

[teddychn]

Here is a snapshot from my scope. On screen blue trace is much brighter, lighter blue than on this image. That is why I was confused, I have no trouble seeing it.
But I think your request is good one, it should be user configurable..

As a side note, to make it easier to read (if you have problem with blue) enable Color grading in Display menu... Maybe that helps a bit..

Thanks 2N3055,

I tried your idea, and it seems a bit better.

Actually, I can see the dark blue details on the oscilloscope screen, but they appeared too dark to be seen on my laptop.

Here are the new captures.

[Ulrich.G]

Firmware update V1.2.2.5 is available!

https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS2000X_HD_V1.2.2.5_EN.zip

Its not just a software update of the OS, but also reprogramming the FPGA to version 2023-05-30 

[Martin72]

YES 

[Ulrich.G]

With the new firmware version 1.2.2.5, we not only got 4 math channels, but also 4 memory channels. The possibilities seem to be almost endless. Import data from other channels, files, math functions...

I'm a little overwhelmed with it, but great feature.

Found the decription in the SDS6000A manual - page 260-262

[kladit]

The description of what?

I  looked at the "SDS6000A User Manual" and at page 260 found a description of "Mask Setup".

Neither "memory channel" nor "memory trace" can be found in this pdf.

So please give link to the pdf you are talking of.

[tautech]

The description of what?

I  looked at the "SDS6000A User Manual" and at page 260 found a description of "Mask Setup".

Neither "memory channel" nor "memory trace" can be found in this pdf.

So please give link to the pdf you are talking of.

Try this manual version:
https://int.siglent.com/u_file/download/22_10_24/SDS6000A_UserManual_EN01B.pdf

Chapter 21 Memory P260

[Martin72]

To the beta testers active here:
Do any of you have a 2kHD at home ?
Then please send me a PM.

As for the new firmware:
The datum thing works..
Window font size I also found and set to "small", I haven't noticed a direct difference yet.
And a bugfix not listed in the revision I also discovered:
The save message now disappears by itself again....

[kripton2035]

I've posted it in the other 2000HD thread, but this one on the bug is a better place
with last firmware, if you press default, the 10x probe is still not detected. you must unplug and plug it to be detected as 10x