Siglent SDS2000X Plus - Bugs / Missing Features / Feature Requests

[KungFuJosh]

This is a minor UI bug.

[hpw]

Small changes in FFT. Now log10/linear

Yes, this is nice

as it gets, was looking for any colors changing. Look at given pic's dark yellow text and lighter yellow line... so hard to see about the freq. axis values

[mathstudi]

New UI update seems to lack anti-aliasing and the padding is also off, buttons are harder to press with fingers now..
I hope this will be reverted to be in the style of 1.5.3 

Yes, I also noticed the anti-aliasing, but only when you pointed it out. It doesn't bother me, but it's an aesthetic thing that is perceived individually.

I like the serial decoders that I tested today. Too bad the documentation (Serial Signal Test for I2C and SPI) is not ready yet.

My bandwidth tests with the tinySA ULTRA were all positive.

Unfortunately there is no I3C decoder. This is probably a licensing problem, because there is no free I3C decoder for the saleae Logic Analyzer either, although many decoders are already included with the saleae.

What makes me happy is the fact that Siglent is still doing a great job of product maintenance. Especially that new gadgets are still being added.

Cheers

[tautech]

Small changes in FFT. Now log10/linear

Yes, this is nice

as it gets, was looking for any colors changing. Look at given pic's dark yellow text and lighter yellow line... so hard to see about the freq. axis values

Change your Scale or Ref level. 

[electronics hobbyist]

buttons are harder to press with fingers now.

Which button is more difficult to press? The size of the button looks the same. It would be even better if a picture could be attached.

[hpw]

Small changes in FFT. Now log10/linear

Yes, this is nice

as it gets, was looking for any colors changing. Look at given pic's dark yellow text and lighter yellow line... so hard to see about the freq. axis values

Change your Scale or Ref level. 

Sometimes it is prefered to keep the full scale as to track the progress.

As only 20dB/div maximum scale possible, not any 25...30..40..50 given O:((

Now on print png, the text gets now some white/blue collor while saving.

[smallfreak]

Now on print png, the text gets now some white/blue collor while saving.

Do you have an example? The PNG should look just as the screen. Happening with the "print" button, or via web interface?

[hpw]

Now on print png, the text gets now some white/blue collor while saving.

Do you have an example? The PNG should look just as the screen. Happening with the "print" button, or via web interface?

As I told you, the axis x/y text gets this color while saving in progress. Only at that time and then come back to normal.

In addition, you will see scope & FFT axis X/Y color as quasi nor readable while it is NOT POSSIBLE to alter those line or axis colors.

So the request is simple  :

- lets modify the colors as all SW allow this 
- add 25/30/40/50 dB/div 
- may as simple wish, to add scale dBV/rthz as a simple task 
 

[2N3055]

Small changes in FFT. Now log10/linear

Yes, this is nice

as it gets, was looking for any colors changing. Look at given pic's dark yellow text and lighter yellow line... so hard to see about the freq. axis values

Change your Scale or Ref level. 

Sometimes it is prefered to keep the full scale as to track the progress.

As only 20dB/div maximum scale possible, not any 25...30..40..50 given O:((

Now on print png, the text gets now some white/blue collor while saving.

What would be the purpose of 50dB/div ??

You think any system in the universe have 400dB instantaneous dynamic range?
On a 8 bit scope?

[hpw]

well, 50dB for a 4..5 x 50dB as 200..250dB full range as my pictures shows up.

[hpw]

One more wish:

- add the used FFT Window to the BIN file, so we know later on, what FFT Window has been used

- may add better performing FFT Window functions as BH7

[2N3055]

well, 50dB for a 4..5 x 50dB as 200..250dB full range as my pictures shows up.

FFT has 8 vertical divisions. 8*50=400

You can also use split window.

[KungFuJosh]

As I told you, the axis x/y text gets this color while saving in progress. Only at that time and then come back to normal.

Are you complaining about the colors in your screenshot being inverted? That's a setting.

[hpw]

well, 50dB for a 4..5 x 50dB as 200..250dB full range as my pictures shows up.

FFT has 8 vertical divisions. 8*50=400

You can also use split window.

Look, the probe gain supports +1E6 to -1E6 so we get +/- 120dB  ... so for 8 x 20dB Grid there is not much room left

[hpw]

About the color thing: this is possible and in the latest given documented.

To setup / change the colors:

[1] >> Display menu... then on the right go down until this settings sub menu entry is visible.

[2] only Math F1 or F2 as for line and axis text.

[hpw]

Three bug seen on V1.6.2:

[1] reboot and have setup as C2 & F1: you will see for a while the NOT enabled C1 input and than alters to C2 & F1

[2] using this setup: on the right side an 500Hz vertical line is drawn. See picture with red rectagle

[3] If you enable on C2 the axis text as level & time as I use right justify: the level Y axis text gets overwritten by the trace line

[mathstudi]

..
Haven't tested the new function yet. I'll wait for the adapted documentation.

These are what is called compliance tests.
They will automatically test number of critical parameters of protocol and compile a PASS/FAIL test report with data.

I actually wanted to wait for the updated documentation. But the interest in the new function was greater and so today I ran some tests with an I2C protocol.

I am impressed! I've been looking for something like this for a long time, especially for the popular I2C and SPI protocols.

This is exactly what I appreciate about Siglent, that even years after the market launch, new gadgets are still being added.

The "fail" with the "Clock Signal Frequency" is my mistake -> wrong configuration.

A report can also be generated (HTML/XML), which is quite impressive. I will do further tests.

[mon]

Did 1.6.2 get yanked? Everywhere I checked is still 1.5.2R3 (int.siglent.com, siglentna.com, and siglent.com)

[james38]

Yes, there were some problems (freezes) with the upgrade for some,
so the update has been withdrawn until further notice.

I think we have to wait here for now.

Regards Chris

[BitBangingBytes]

That’s a bummer! I discovered my VNC no longer works properly after upgrading to the latest 1.5 version and found this thread where others seemed to have the same issue.

Hopefully the 1.6 version goes public soon so I can see if that fixes it.

[KungFuJosh]

That’s a bummer! I discovered my VNC no longer works properly after upgrading to the latest 1.5 version and found this thread where others seemed to have the same issue.

Hopefully the 1.6 version goes public soon so I can see if that fixes it.

I never tried connecting through VNC before 1.6,  but it worked fine on 1.6.2R1 for me.

[BitBangingBytes]

Unplugging everything and doing the Math button repeated press upon boot seems to have fixed it for now.

I had tried that last night but didn’t unplug the Ethernet cable. Unplugging it today and doing it seems to have worked.

[KungFuJosh]

Unplugging everything and doing the Math button repeated press upon boot seems to have fixed it for now.

Is that a thing? I don't remember reading about that.

[BitBangingBytes]

Yea, I was closely reading Siglent’s directions last night…

[tautech]

Yea, I was closely reading Siglent’s directions last night…

Yes, for boot freeze recovery.
Did pressing Default not work for you ?