Siglent SDS2000X Plus

[stafil]

Sorry to divert the conversation from Bode Plotting, but is anyone else annoyed by the "Sequence" a.k.a segmented memory mode?

If one configures it to capture X amount of frames, and then receive X+1 frames, it just wipes out the previous memory and starts from scratch.

I would expect it to either stop at X frames and go into History mode, or just use a circular buffer. Not wipe out ALL the old frames.

It should stop after acquiring  X frames.

That's what I was expecting too, but it doesn't:

What happens if you press single instead of run?

Works exactly as expected

 I am too stupid to be allowed to operate these instruments   

[Elasia]

I found the culprit for my unit at least on the bode issue

Auto channel gain

[thinkfat]

Nice. So it's not the settling time of the AWG, it's the settling time of the input switching between ranges.

[2N3055]

Nice. So it's not the settling time of the AWG, it's the settling time of the input switching between ranges.

I mentioned this some time ago, but was told that Frex tried in hold mode and also got error...
So what is right?

[thinkfat]

Nice. So it's not the settling time of the AWG, it's the settling time of the input switching between ranges.

I mentioned this some time ago, but was told that Frex tried in hold mode and also got error...
So what is right?

Frex should be able to tell. I might have misunderstood what he said.

[2N3055]

If you want to unlock 5000X to 1 GHz you need to buy 500MHz ver.

Maybe not anymore...    Yet to confirm.

That would be VERY nice..

Indeed. More or less the only thing stopping me from ordering the SDS5034X is that it can't be upgraded to 1GHz. There are some hints (spec wise) that the frontend in the 500MHz model is different though, so even if the SW could be tricked into believing it's the 500MHz model that can be upgraded to 1GHz, I have some reservations that it will reach the full bandwidth. Still.

I'll just leave this picture here...

What pulse gen you used?
Sorry to disappoint you, but  if you are using pulse generator that is faster than 200 ps risetime, this proves that your 350MHz version doesn' have same front end as 1GHz version. 
Let me explain. Siglent made 1st version of 1GHz front end (that's the one you have) but it wasn't as good as they wanted it to be. To their credit, they made ver 2 with improved front end (with better bandwidth, but more importantly better linearity and phase across the range). That one should have 400ps risetime..

Dont get me wrong. What you have is one fantastic 750-800 MHz scope... Since you paid for 350 MHz you are winner anyway.
But real 1 GHz version (and officially upgradeable 500 MHz one upgraded to 1GHZ) are even better in upper end.
On the other hand, your should have better bandwidth at 1 mv/div..

[0xdeadbeef]

Looks like Bodnar 40ps. Still, 750MHz doesn't sound so bad to me.
Anyway: does the 1000M or MAXjust work or is additional trickery needed?
Besides: how would this look like with just the 500M option?

[Martin72]

Looks like Bodnar 40ps.

It IS the Bodnar, I got it too and know the PCB look.

[Martin72]

We´re still talking about the sds2000X+ ?

[Elasia]

We´re still talking about the sds2000X+ ?

They went on a tangent about the 5k series

[2N3055]

We´re still talking about the sds2000X+ ?

They went on a tangent about the 5k series

Sooory, I didn't notice the title... Just answered...
Yes that should be continued in sds5000X topic..

[Frex]

Nice. So it's not the settling time of the AWG, it's the settling time of the input switching between ranges.

I mentioned this some time ago, but was told that Frex tried in hold mode and also got error...
So what is right?

Frex should be able to tell. I might have misunderstood what he said.

Hello,

I had tested Normal and Vary Level sweep type,  but not Auto/Hold Gain . I will try this also this weekend.
Note that even if it's ok without the auto gain, that stay a bug that need to be solved !

Frex

[Elasia]

Hello,

I had tested Normal and Vary Level sweep type,  but not Auto/Hold Gain . I will try this also this weekend.
Note that even if it's ok without the auto gain, that stay a bug that need to be solved !

Frex

Listen for the relay click.. thats the dead give away

[DL2XY]

Had a short test with external AWG (SDG6000X via USB).
No glitches, even with Auto Gain.

Ran some more tests, 1 out of 12 passes showed 3 glitches.

[maginnovision]

Your original post definitely made me think you just didn't run long enough so glad you tried a little longer.

[thinkfat]

Nice. So it's not the settling time of the AWG, it's the settling time of the input switching between ranges.

I mentioned this some time ago, but was told that Frex tried in hold mode and also got error...
So what is right?

Frex should be able to tell. I might have misunderstood what he said.

Hello,

I had tested Normal and Vary Level sweep type,  but not Auto/Hold Gain . I will try this also this weekend.
Note that even if it's ok without the auto gain, that stay a bug that need to be solved !

Frex

Without the auto gain, dynamic range will be reduced by quite some amount.

[famalex]

Hi!
I'm sorry to have to change again the discussion, but I have very brief question for experienced and knowledgeable members. I bought SDS2104X Plus from Welectron and am waiting for it to arrive (delayed by the known virus).  Of course, 100 MHz BW is rather good and enough in many cases for an average hobbyist as I am, but sometimes somebody wants something more.  So, I decided to upgrade the BW to 200 MHz in the future. Batronix promotes this option for only €1500 as “hardware upgrade”. Is there really “hardware” difference between these two models?  I mean SDS2104 and SDS2204.

[tautech]

Hi!
I'm sorry to have to change again the discussion, but I have very brief question for experienced and knowledgeable members. I bought SDS2104X Plus from Welectron and am waiting for it to arrive (delayed by the known virus).  Of course, 100 MHz BW is rather good and enough in many cases for an average hobbyist as I am, but sometimes somebody wants something more.  So, I decided to upgrade the BW to 200 MHz in the future. Batronix promotes this option for only €1500 as “hardware upgrade”. Is there really “hardware” difference between these two models?  I mean SDS2104 and SDS2204.

No difference and the 100 MHz model has already been found to have ~185 MHz -3dB point so rightly is shipped with 200 MHz probes.

[famalex]

Thank you. Your answer is brief and encouraging.

[famalex]

New firmware version for SDS2000X Plus 1.3.5R5 is ready.  Coincidentally, my oscilloscope came to me today. Obviously I won't be able to sleep tonight.

[TK]

Is there a good practice to calculate the effective waveform updates per second on the Siglent scopes?  I cannot get anything near the 120,000wfm/s claimed by Siglent marketing. 

I tested the minimum timebase, dot mode.  Reference trace in orange is without measurements, yellow trace is with 2-3 basic measurements.  With no measurement there is a 3ms dead time between triggers, with measurement active the dead time increases to 13ms.  I did not capture the frequency but it was something like 1KHz...



Please ignore the wrong scale due to having the probe in 10:1 and using a BNC to BNC cable.

On Keysight 1000X, you just put minimum timebase and you get the published 200,000wfm/s

[tautech]

New firmware for SDS2000X Plus models

Version V1.3.5R5
29.6 MB

https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS2000X_Plus_1.3.5R5_EN.zip

Release notes
1. Supported to hide analog traces
2. Added function expression information to the math box
3. Optimized AWG DC output accuracy at +/-3V
4. Frequency counter supported to count serial trigger events
5. Fixed several bugs
     a) Incorrect cursor horizontal label for FFT traces
     b) 2-channel 100MHz model cannot be upgraded to 350MHz
     c) FRFR measure invalid from Roll to Stop
     d) Unexpected behaviors when probe attenuation factor is not 1x
     e) Some bugs in PA

[Martin72]

Good news, can´t await to test it.
Thank god, this (working) week is short...

[TK]

I could not find averaging in the acquisition menu.  In this scope, it seems to be a math function.  Does it mean that you can only average 2 traces out of 4, as math has capacity for only 2 functions?

[Martin72]

Therefore I suggest to enhanced the math traces up to four...Shouldn´t be a big problem to realize.
(See my signature, bugs and wishlist)