Siglent SDS2000X Plus - Bugs / Missing Features / Feature Requests

[2N3055]

Has no one noticed the last "anomaly" I mentioned?  Perhaps no one cares. 

Well, looks like I found another "anomaly".  Have a look at the capture attached.  Notice the counts on the statistics.  For some really odd reason, the count on the fall time is twice the others even though they were all started at teh same time. 

Not an anomaly.

Some measurements are performed once per screen, some will be done as many times as possible.


For instance, RMS is once per screen (one triggered acquisition), period or frequency can be 100 or 1000 times if there are 1000 pulses on screen.
Combine this with track on measurements for seeing how it changes with time.

In measurements Statistics menu you can setup how it works.

There are Count Limit and AIM limit params.

AIM limit controls how much maximum measurements will be performed per screen (for measurements that support it).
IF you set it to 1 you will get only one measurement per screen for every measurement

Count limit is max number of running length of data used for statistics.. If you set it to anything else than unlimited, than that number will be max of measurements used for stats, and there will be no multi measurements either.

Play with that a bit to get an idea..

[Performa01]

Has no one noticed the last "anomaly" I mentioned?  Perhaps no one cares. 

Well, looks like I found another "anomaly".  Have a look at the capture attached.  Notice the counts on the statistics.  For some really odd reason, the count on the fall time is twice the others even though they were all started at teh same time. 

An "anomaly" ?

How many rising edges do you see? And how many falling?

Change the timebase and watch the statistics, then you will understand the implications of deep measurements (over the full record length) with regard to speed and accuracy of measurement statistics.

[BillyO]

Ahh ..., I see!  Said the blind man to the deaf mute.

Okay, will give that a try.

[knudch]

Flash upgrade does not work via WEB interface

When I try to upgrade from the WEB interface, the file (*.ADS) is uploaded and a message is given back
"Fail:File type not supported"
(Firefox web browser, Linux Platform)

When I do the upgrade by USB stick with the same file no problem.

SDS2104x plus with "option" to SDS2504x plus.

Firmware pack 1.5.2R2
(did the upgrade from 1.3.9R10, if I re-try the 1.5.2R2 I get this failure)
Not a big issue but strange

[rf-loop]

Flash upgrade does not work via WEB interface

When I try to upgrade from the WEB interface, the file (*.ADS) is uploaded and a message is given back
"Fail:File type not supported"
(Firefox web browser, Linux Platform)

When I do the upgrade by USB stick with the same file no problem.

SDS2104x plus with "option" to SDS2504x plus.

Firmware pack 1.5.2R2
(did the upgrade from 1.3.9R10, if I re-try the 1.5.2R2 I get this failure)
Not a big issue but strange

Just tested (Windows). Just mouse click..click..click and ok.
I use "isolated" Opera (do not ask),  for only instruments and for www other browsers in same computer. But imho this do not matter anything.


SDS2000XP_V1.5.2R2.ADS   (SDS2000X Plus FW update file)
MD5 checksum is: D74B28B943463918B4365A89612BC80F
If this match your .ADS file is ok. 
When oscilloscope get this file ok,  it can not result as: "Fail:File type not supported"


But why you update to V1.5.2R2. Do you have 06-xx   hardware version?

[knudch]

Checksum is the same as yours
The same file updated perfect via USB-stick method

I will test with different browser/platforms

[knudch]

Strange !

Browser update.

If I try web update with the same version of firefox browser but on windows7 platform it works as expected

3 different web browser on Linux/Fedora...it fails at end of upload "Fail:File type not supported"

[Martin72]

New scope(04/2023) at work, latest firmware, "old" bug ?
Timesetting:
Choosing the correct timezone (EU/Berlin), enter the correct time, leaving the menu after pressing OK, time will be shown correct in the lower right corner as expected.
Then switch off the scope, switch it on again - Time is incorrect..
Timezone stays, but time itself is increased to +2h.

Martin

[knudch]

@Martin72

Mine is even more stranges

Dont have the LAN tab in that window
In the TIME tab the Time zone is blank and I can not chose any timezone

Firmware 5.0.1.5.2R2 and 2R3  (2104X plus => all options)
Connected to LAN with DHCP or Fixed IP

Knud

[KungFuJosh]

@Martin72

Mine is even more stranges

Dont have the LAN tab in that window
In the TIME tab the Time zone is blank and I can not chose any timezone

Firmware 5.0.1.5.2R2 and 2R3  (2104X plus => all options)
Connected to LAN with DHCP or Fixed IP

Knud

Go to Utility -> I/O Setting, and you should see LAN config there.

I also have the latest firmware, and cannot select Timezone at all. Time works fine anyway though.

[knudch]

I just wonder why a brand new scope behave different
And time setting does not work here only, manual is ok

I will say BUG !

Knud

@Martin72

Mine is even more stranges

Dont have the LAN tab in that window
In the TIME tab the Time zone is blank and I can not chose any timezone

Firmware 5.0.1.5.2R2 and 2R3  (2104X plus => all options)
Connected to LAN with DHCP or Fixed IP

Knud

Go to Utility -> I/O Setting, and you should see LAN config there.

I also have the latest firmware, and cannot select Timezone at all. Time works fine anyway though.

[blurpy]

Siglent does not provide the time zone files in firmware upgrades, so those who bought the scope before the feature was added can not set a time zone. New scopes have those files in place from the factory. Still hope Siglent will provide those files in the future, but we have been waiting a while now.

[KungFuJosh]

Siglent does not provide the time zone files in firmware upgrades, so those who bought the scope before the feature was added can not set a time zone. New scopes have those files in place from the factory. Still hope Siglent will provide those files in the future, but we have been waiting a while now.

That's interesting. If that's the case, then maybe somebody with the time zone files can copy them off of their scopes to make them available to the rest of us.

[blurpy]

That's interesting. If that's the case, then maybe somebody with the time zone files can copy them off of their scopes to make them available to the rest of us.

They also disabled the usual telnet trick that would have made that "easy" in newer firmware versions, so that's a bit unfortunate.
It's better if they finish the rollout of the feature in a supported proper way.

Looking at you tautech

[KungFuJosh]

I guess this is a feature request, since I can't find a way to do it (and I don't want to RTFM again).

I want to be able to compare two frequencies on a bode plot. For example, I'd like one marker at 200Hz, and the 2nd marker at the peak. I'm running 80/dec for the resolution I need, and they don't both fit in the list on screen.

It would also be nice if there were more measurement options in bode plots. For example...comparing the peak to a specific frequency. 😉

[Martin72]

For example, I'd like one marker at 200Hz, and the 2nd marker at the peak.

The cursor function won´t help ?

[KungFuJosh]

For example, I'd like one marker at 200Hz, and the 2nd marker at the peak.

The cursor function won´t help ?

It seems like it only allows me to select one point at a time:




Is there already a way to add multiple points at once?

Thanks,
Josh

[Martin72]

Could check it "tomorrow", but here´s what the FM says:

Cursors
SDS2000X Plus can use the cursor to measure the bode plot curve. The
cursor of the bode plot is similar to the ordinary cursor, see the chapter
"Cursors" for details. Touch Display>Cursors to recall the cursor setting
dialog box

[KungFuJosh]

Could check it "tomorrow", but here´s what the FM says:

Cursors
SDS2000X Plus can use the cursor to measure the bode plot curve. The
cursor of the bode plot is similar to the ordinary cursor, see the chapter
"Cursors" for details. Touch Display>Cursors to recall the cursor setting
dialog box

Hmm, I guess I better hook everything back up and try again lol.

Thanks,
Josh

[KungFuJosh]

It doesn't work. I did a bode plot with lower resolution to go faster:


The top menu disappears during bode plot, so it certainly can't be done remotely. Pressing the physical display, cursor, or measure buttons on the scope itself doesn't do anything either. It appears the only physical button that works is the Print button.

Did the FM lie?? 🤣

[Martin72]

When you touch the "Display" button in the bode menu, nothing will happen ?

[KungFuJosh]

When you touch the "Display" button in the bode menu, nothing will happen ?

Ohhh, thaaat Display button. 🤣



That's pretty cool! Except I guess it wasn't helping that I was trying to do everything from the web console. It seems like you have to use Fungus' favorite universal scroll button to adjust the measurement points.

So then my feature requests are:
1. Make the cursors adjustable from the web console
2. Remember load and sweep settings (everything else seems to be remembered).

[Martin72]

Well....Bingo, I guess...

[KungFuJosh]

Well....Bingo, I guess...

Pretty close, I edited in my new requests. 😉

Thanks!

Edit: Why can't I select 200Hz with the stupid select knob?? That's annoying. It skips by 2, and there's no adjustment for it (199 or 201 are the only options). They need to update the UI so I can use it from the web console and enter the exact frequency I want without that dumb knob.

[Martin72]

It´s way too late for me to play with my HD scope (which bode feature is the same), but let´s say in the "afternoon" I´ll play around with it, especially the web thing.