Siglent SDS2000X Plus

[Markus2801A]

Sort of ticking noise here too. It has something to do with brushless controller, i think.

Mee too! Some kind of ticking (annoying) noise.

... I fear as well that sending it back will just get me another unit or fan with the same ticking. Maybe the improvement tautech mentioned some time ago where they lowered the fan noise was due to lowering the voltage to the fan, and as a result it makes that ticking sound?

If it really has to do with the  voltage fo the fan, maybe the next Firmware update will fix this?

[oz2cpu]

do i have a hearing problem ? i dont hear any bad, or wierd sounds from the fan.

happycustomer++;

[blurpy]

New stock SDS2104X Plus SN# range SDS2PDDD4R1*** are somewhat quieter than earlier units and it seems a slower fan has now been fitted.

do i have a hearing problem ? i dont hear any bad, or wierd sounds from the fan.

Maybe you have the previous generation fan setup? Or maybe you are lucky with your fan

If it really has to do with the  voltage fo the fan, maybe the next Firmware update will fix this?

Sounds a bit like a hardware mod, so not sure.

[tautech]

blurpy
All noted.
Have a fresh new stock unit to PD soon so will take note of its fan behavior and bring your and others observations to the attention of Siglent whom have just knocked off for the weekend.

Handling a few units I see minor differences in the SN# coding in each batch we get in so going forward if this is a reoccurring problem we need see if there is commonality in the SN#'s.
Eg. SDS2PDDX5R##** We wouldn't need the last 2 or 3 #'s.

[blurpy]

Handling a few units I see minor differences in the SN# coding in each batch we get in so going forward if this is a reoccurring problem we need see if there is commonality in the SN#'s.
Eg. SDS2PDDX5R##** We wouldn't need the last 2 or 3 #'s.

Thanks for following up tautech
My SDS2104X+ is in that SN range you wrote there.

[H.O]

FWIW: Mine is SDS2PDDX5R15xx, it sounds exactly as in the audio file posted by blurpy.

[IAmBack]

When I got this scope I was playing with it to check if everything is OK. AFAIR I was able to "catch" a plot of pulses, that were corresponding to that ticking when probe end was close to the scope's housing.

[profanum429]

blurpy
All noted.
Have a fresh new stock unit to PD soon so will take note of its fan behavior and bring your and others observations to the attention of Siglent whom have just knocked off for the weekend.

Handling a few units I see minor differences in the SN# coding in each batch we get in so going forward if this is a reoccurring problem we need see if there is commonality in the SN#'s.
Eg. SDS2PDDX5R##** We wouldn't need the last 2 or 3 #'s.

Mine is SDS2PDDC5R**** and it had the same ticking noise in the posted audio. I replaced the fan though with a Noctua NF-A9 and it's much better now though!

[Angus]

My very first post here :-)
I've just purchased a SDS2104x+. The summer promotion finally got me.
The bundled keys for FNG and MSO did not work for some reason. The url did not give a key. I then simply used a python script from git (I think that is the key generator you aure talking about) as the key generator instead. No problem so far.

The fan is not silent, nor is it extremely loud. It resonates with my bench, but I can deal with that.
The SDS2104x+ froze two times while trying out things. 


Playing with the scope for two days I came across something I did not expect: math channels. It is hard to understand (for me) why Siglent did it the way it is. Eres is located under math. Ok that is understandable. Averaging is also located there. I can follow that philosophy - you can average more than a scope input. However in -all- scopes that I know averaging would be found under 'aquire'. If you know it, no problem.
BUT I find it really annoying that I have to waste place on the screen to show the original waveform! Looking at the FFT Siglent seems to have noticed that sometimes the source for the FFT is unwanted and you can choose not to show the time-domain signal. WHY is that not possible if doing ERES or averaging? If I come across a signal that makes me kick in averaging, THAT Signal is likely to be irrelevant for me. So, please, can someone point out f I am just too blind and show me how to keep the machine from plotting the sources of ERES or averaging? Thanks.
If there is no way to achieve this, I really hope for a firmware release to deal with that. I watched some videos about this scope. Sometimes I realized complains about the memory managment or such, but I  can't remember people pointed this issue out or felt annoyed by the math solution.

[2N3055]

My very first post here :-)
I've just purchased a SDS2104x+. The summer promotion finally got me.
The bundled keys for FNG and MSO did not work for some reason. The url did not give a key. I then simply used a python script from git (I think that is the key generator you aure talking about) as the key generator instead. No problem so far.

The fan is not silent, nor is it extremely loud. It resonates with my bench, but I can deal with that.
The SDS2104x+ froze two times while trying out things. 


Playing with the scope for two days I came across something I did not expect: math channels. It is hard to understand (for me) why Siglent did it the way it is. Eres is located under math. Ok that is understandable. Averaging is also located there. I can follow that philosophy - you can average more than a scope input. However in -all- scopes that I know averaging would be found under 'aquire'. If you know it, no problem.
BUT I find it really annoying that I have to waste place on the screen to show the original waveform! Looking at the FFT Siglent seems to have noticed that sometimes the source for the FFT is unwanted and you can choose not to show the time-domain signal. WHY is that not possible if doing ERES or averaging? If I come across a signal that makes me kick in averaging, THAT Signal is likely to be irrelevant for me. So, please, can someone point out f I am just too blind and show me how to keep the machine from plotting the sources of ERES or averaging? Thanks.
If there is no way to achieve this, I really hope for a firmware release to deal with that. I watched some videos about this scope. Sometimes I realized complains about the memory managment or such, but I  can't remember people pointed this issue out or felt annoyed by the math solution.

You mean you have CH1 and then create math channell F1 from that one ( ERES or whatever really). And you don't want to have original source channel visible on the screen?

User manual, page 65:    (J) HIDE Channel button.

Manuals ARE our friends... 

Enjoy your new scope!

[Angus]

Manuals ARE our friends... indeed! Thank you for solving this. I did study the manual prior to the purchase (of course). No idea why I missed that part.

[bdunham7]

ERES and averaging are MATH channels?  Does that mean you can't use ERES or averaging on all channels at once?

[2N3055]

Manuals ARE our friends... indeed! Thank you for solving this. I did study the manual prior to the purchase (of course). No idea why I missed that part.

Don't worry. It is a lot of information to be absorbed at once..

[Martin72]

Does that mean you can't use ERES or averaging on all channels at once?

Correct calculated 
For performance reasons, the sds2k+ got two mathchannels only(the sds5K too, by the way..), so avg and eres can be used on two channles at once.
If you got the 2-ch version of the scope, it´s enough.

[2N3055]

Well, you do have 10bit acquisition mode. Which is same as a global hires mode on other scopes...

[echo99]

New Firmware  V1.3.9R4 released today  ... changelog not yet updated..

https://siglentna.com/service-and-support/firmware-software/digital-oscilloscopes/#sds2000xp

[tubularnut]

New Firmware  V1.3.9R4 released today  ... changelog not yet updated..

https://siglentna.com/service-and-support/firmware-software/digital-oscilloscopes/#sds2000xp

Sept 2nd 2021

1.3.9R4
1. Measurement enhancement:
  a) Supported cursors for measurement
  b) Supported Track plot
  c) Added parameters: Positive Slope and Negative Slope
2. Display:
  a) Supported to display axis label
  b) Auto hide menu setting increased to 10 seconds
  c) Added “Hide” button in the fast menu of channel for quickly hiding trace
3. Save/Recall:
  a) Supported network storage
  b) Supported to Print only grid area
  c) Supported to save FFT result
  d) Updated the File Manager
4. Bode
  a) The maximum generator amplitude changed from 6Vp-p to 24Vp-p
  b) Supported single sweep
5. Horizontal: Time Zero strategy updated – time zero changed from center display to trigger position.
6. Acquisition: Deleted some unnecessary clear operations on the history buffer
7. Updated Russian menu
8. Supported setting Cursors by virtual keypad
9. Fixed several bugs
  a) Decode failure occurs on last nibble or byte
  b) The “STL?” query issue in AWG function
  c) If persistence is enabled, and you change the trigger setting, persistence
  will be switched off
  d) Decode list can't go higher than item #2
  e) Decode format is reset to "binary" when recalling stored settings
  f) Sequence capture does not work with serial trigger from digital channel
  g) ERES 0.5-bit works for ERES(C1), but not for ERES(F1)
  h) The icons for rise and fall time in the Measure Select screen are reversed
  i) When switching the attenuator, the message “Zone is too small” appears
  j) After shutting-down the scope and rebooting not all settings are restored
  k) Bode plot abnormal when Sequence is enabled
  l) SENT decode: tolerance not functional
  m) SENT decode: only display CRC segment but no calculation on the CRC
  checksum
  n) SENT decode: The Short Serial data is NOT decoded if only 16 frames
  are sent. If a 17th frame follows, the data is decoded
  o) SENT decode: Changing the horizontal time/div affects the ability to
  decode.
  p) Save/recall: Number of digits of time stamp is not enough in the long period
  q) Infinite persistence not works after switching between 8-bit and 10-bit
  r) Tolerance of UART decode too strict
  s) FFT max. scale is unrealistic

[Markus2801A]

New Firmware  V1.3.9R4 released today 

https://siglentna.com/service-and-support/firmware-software/digital-oscilloscopes/#sds2000xp

[Markus2801A]

I did it:

Screenshots order:
before
during
after

upgrade :-)

[echo99]

I did it:

Me too. Went well also on the "improved" Version of the Scope ...

[Martin72]

Bode:
b) Supported single sweep

YES 

Siglent as ever, bugfixes and enhancedments....Great stuff, can´t await for updating my scope.

[dibro]

I've also updated my 'enhanced' scope to 1.3.9R4
Update with memory stick went without problems.
Only issue I have is that when I select the option screen the scope hangs and can only be restarted by pressing the power button for 5 second.
If I roll back to 1.3.7R5 then the option screen works again.

[tubularnut]

Only issue I have is that when I select the option screen the scope hangs and can only be restarted by pressing the power button for 5 second.

Works ok here.

[kcbrown]

Only issue I have is that when I select the option screen the scope hangs and can only be restarted by pressing the power button for 5 second.

Mine has the same problem.

If I roll back to 1.3.7R5 then the option screen works again.

Same here.

Note that what it's killing is the UI.  The traces continue to be updated.

EDIT: I figured out what the problem is.  It's the Manchester decoder option (SDS_2000XP_Manch on the options page, or MANC in SCPI).  If you delete that option, the options page will work, and it'll show as having a temporary license for it.

EDIT 2: Actually, it's not any option in particular.  The deal is that if you have all non-bandwidth options enabled, it'll hang.  If any one of them is disabled or temporary, such that you can select it in the dropdown for installation, it'll work.  I also found that if you enable the last non-bandwidth option via SCPI, it'll hang the scope right then and there.  Interesting behavior...

[famalex]

Nice work, SIGLENT!
From next firmware upgrading I expect the sample rate raising from 2 to 5 GSa/s and 12bit mode capability.