Siglent SDS2000X Plus

[douggoldberg]

Frex, Are you the same Frex as an DIY Audio? If so I have been following your audio analyzer build. Awesome work.

I did receive my LA probe set from Saelig. They are quite nice but not $300.00 nice. Would have nice to get a little storage pouch.

[tautech]

Hi Rob,

Reboot DSO, does the setting Inverted remain as default for the Print button ?

Just trying it out now - The setting "Image Style" in the save/recall menu was changed back to normal, after reboot.

EDIT:

Other menu settings ( acquire, trigger for example (tried them)) remains after reboot.

As expected however I was asking about setting Inverted Print outputs as a User Default.

Maybe you haven't found that functionality yet. 

To be honest, I don´t know what you mean with this exactly. 
There´s no print menu or settings for the print button explicit available.

Save/Recall>Save>Type = Default (button) = Current (scope) settings.

This sets all scope settings currently used to the Default button rather than the normal factory defaults. (yet they can also be returned to Default)
Very convenient for your most used favourite scope setup and must include Print output settings such as inverted and/or other image file types AND they must be returned when the user set Default is next used, with or without power cycling.

As mentioned, this is not the case with current X-E FW and I expect 2kX Plus to be the same and it needs be fixed.
Currently Print output settings are not saved to user Default OR reboot when they should be.

This needs carefully checking in 2kX Plus by another owner as I have sold my 2104X Plus and won't have any more for a few weeks. 

[Martin72]

Save/Recall>Save>Type = Default (button) = Current (scope) settings.

Ah, page 290 in the user manual....RTFM...

And you´re right, tried this a minute ago, everything will be stored - except the print button.

[Martin72]

Another strange thing:

As I played around with the image style thing, turning it to invert, and press reboot - after the reboot all usb connectivity got lost.
No flashdrive detection, no mouse detection…
Reboot again, nothing changes.
Shut it down, then turning on again - Ports will be detected…..

That happens to the usb root hub if you have a power fault, they dont turn back on until you hard cycle, look for ground loops but if not maybe faulty?  I'd assume they would have one anyway like other products and especially considering its nature.. if not x_x

This was not the first time happen, I´m quiet sure.
And another strange thing concerning saving screenshots on stick:
Example, you took the stick into the port, taking a screenshot, it will be "named" with 1, what makes sense, because it is the first.
Next shots will be 2,3,4, etc...
So far so good.
But this will going only when you leave the stick connected.
If you put the stick out ( because you want to transfer the pic to pc) and then back, the first pic will be overwrite without a request.
Tomorrow I´ll examine it more exactly.
Hmm...Maybe it´s time for a dedicated bug and missing features thread.

[Frex]

Frex, Are you the same Frex as an DIY Audio? If so I have been following your audio analyzer build. Awesome work.

I did receive my LA probe set from Saelig. They are quite nice but not $300.00 nice. Would have nice to get a little storage pouch.

Hello,

Yes it's me from DIYaudio, I'm unmasked ! 
The logic probe is very expensive for what is it, i agree.
Anyway, i will probably order it soon, no time to make this by myself...

Did you have play with ?
I would be curious to show how it perform with fast clock like 100MHz.
Comparing the Digital channel with analog channel if there is some skew or
it both signal are very well synchronous.
Regards.

Frex

(And thank you for your comment about the analyzer project  )

[Elasia]

I think I discovered the rule (or the symptom) of an upgraded SDS2000X+ becoming a 2354X+ (w/ 500MHz) or a 2504X+ model:

It's all in the S/N:     

SDS2Pxxx3Rxxxx  will turn into a 2354
SDS2Pxxx4Rxxxx  will turn into a 2504

Mine is a 4R but turned into 2354, not 2504.

There goes the neighborhood.  My hunch was wrong! 

Mine is a 4R and became a 2504 on simple bandwidth.txt rename

[chris009]

I think I discovered the rule (or the symptom) of an upgraded SDS2000X+ becoming a 2354X+ (w/ 500MHz) or a 2504X+ model:

It's all in the S/N:     

SDS2Pxxx3Rxxxx  will turn into a 2354
SDS2Pxxx4Rxxxx  will turn into a 2504

Mine is a 4R but turned into 2354, not 2504.

There goes the neighborhood.  My hunch was wrong! 

Mine is a 4R and became a 2504 on simple bandwidth.txt rename

The name depends on the bandwidth.
200M 2204
350M 2354
500M 2504

[tv84]

The name depends on the bandwidth.
200M 2204
350M 2354
500M 2504

In this model, not so!

[Elasia]

This was not the first time happen, I´m quiet sure.
And another strange thing concerning saving screenshots on stick:
Example, you took the stick into the port, taking a screenshot, it will be "named" with 1, what makes sense, because it is the first.
Next shots will be 2,3,4, etc...
So far so good.
But this will going only when you leave the stick connected.
If you put the stick out ( because you want to transfer the pic to pc) and then back, the first pic will be overwrite without a request.
Tomorrow I´ll examine it more exactly.
Hmm...Maybe it´s time for a dedicated bug and missing features thread.

I can confirm this happens if you reboot the scope, so i think its clear its keeping the value in ram and not looking at the usb stick at all before writing

[Elasia]

The name depends on the bandwidth.
200M 2204
350M 2354
500M 2504

In this model, not so!

Ever look at the calibration files?  Maybe they are binning scopes and just didnt have enough to fill the base model so they used higher rated parts to backfill and its pot luck whatcha get?

[Martin72]

I can confirm this happens if you reboot the scope, so i think its clear its keeping the value in ram and not looking at the usb stick at all before writing

So this should be corrected….

[thinkfat]

By the way - as I now apparently own a 500MHz scope, what's the conclusion on which probes to get to match the bandwidth? Bang for buck, which do you guys recommend?

[Martin72]

Hi,

Same question here, there are some cheap 500Mhz probes on the market- but they are what they are, cheap….

This could be interesting but until now, I didn´t find any offer like his description:

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2999752/?topicseen#msg2999752

[tautech]

By the way - as I now apparently own a 500MHz scope, what's the conclusion on which probes to get to match the bandwidth? Bang for buck, which do you guys recommend?

Some discussion in Reply #772 and later.

[thinkfat]

Hi,

Same question here, there are some cheap 500Mhz probes on the market- but they are what they are, cheap….

This could be interesting but until now, I didn´t find any offer like his description:

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2999752/?topicseen#msg2999752

Right, a few offers for used probes of unclear origin. If I were to buy new, I think R&S RT-ZP05 could be a good deal. About €250 for a two-piece set.

[2N3055]

My advice is not to bother with it.

I have a 1GHz scope and there is no practical difference between expensive 500Mhz Keysight probes and 350 MHz Testec probes (at 37 € per piece, TT-HF 212 13,5pF 10x).
In real life, most important parameter is probe tip capacitance.. And that will be large (10-14 pF) even for 500 MHz probes...
Passive probes bandwidth is measured by measuring terminated siggen, with effective source impedance of 25 Ohm.
It makes passive probes look "too optimistic".
Probing real life circuits (with higher impedance) will make your bandwidth defined with probe tip capacitance, not probe bandwidth.

If you want, save money and get active low capacitance probe. Testec TT-AF-1200 is 500-600€ new. And it has  1 MΩ, 3 pF input.
Many other active old used probes can be found too, with better specs.... Or use 50 Ohm coax and 10x 500/50Ohm passive probe for low impedance circuits..

Also, probes get damaged. If you really wish to buy "nicer" probes, use ones that came with scope initially, and with time, when they get damaged, buy other better ones if you feel need for upgrade..

It is easy to spend half of scope price for "better" probes and to get practically nothing in return...
Over 150-200 MHz even most expensive passive probes will be really bad...

Of course that's just my opinion.

[Martin72]

In this case I must give Rigol a thumb up, even the 70Mhz scope got probes with 350Mhz BW.
Although it´s significant cheaper as the siglent.
You bought the 100Mhz model, so you get only cheapy probes with it, is somekind of weak as an argument.
What will happen, if you buy the official BW upgrade, do you also get new probes with it...
I guess no.
So in fact you will be punished when you first buy a "cheap" one from the siglent sds2K+ series and upgrading it later.
Rigols way is more better.
Yes, your scope is an 70Mhz BW one - But it could be, you´ll upgrade this thing up to the top of 350Mhz.
So we including 350Mhz probes for every scope type.

[Elasia]

My advice is not to bother with it.

I have a 1GHz scope and there is no practical difference between expensive 500Mhz Keysight probes and 350 MHz Testec probes (at 37 € per piece, TT-HF 212 13,5pF 10x).
In real life, most important parameter is probe tip capacitance.. And that will be large (10-14 pF) even for 500 MHz probes...
Passive probes bandwidth is measured by measuring terminated siggen, with effective source impedance of 25 Ohm.
It makes passive probes look "too optimistic".
Probing real life circuits (with higher impedance) will make your bandwidth defined with probe tip capacitance, not probe bandwidth.

If you want, save money and get active low capacitance probe. Testec TT-AF-1200 is 500-600€ new. And it has  1 MΩ, 3 pF input.
Many other active old used probes can be found too, with better specs.... Or use 50 Ohm coax and 10x 500/50Ohm passive probe for low impedance circuits..

Also, probes get damaged. If you really wish to buy "nicer" probes, use ones that came with scope initially, and with time, when they get damaged, buy other better ones if you feel need for upgrade..

It is easy to spend half of scope price for "better" probes and to get practically nothing in return...
Over 150-200 MHz even most expensive passive probes will be really bad...

Of course that's just my opinion.

I completely agree.. in most cases its not warranted and if you are doing ghz and up you are dealing with a whole other beast and might be making your own

Those probes are only worth it if you need full calibrated specs for business purposes


My main probes im about to switch to are only rated for 100mhz but are constructed as helping hands ... utility much greater than the bw required .. no more fucking around trying to clip or actively holding something or soldering on flying leads

[drwho9437]

Tek does have a 3.9 pF 10 Meg passive 10x probe but I don't know if it mates to scopes other than Teks. I believe the 500 MHz and 1 GHz probes are 3.9 pF. 2 pF is available for "1-1.5 GHz" passive probes 500/50 10:1 ohm typically.

[Elasia]

License key extraction for scope bandwidth

1. Login via telnet (pick your method)
2. Rename bandwidth.txt file to make it go into Pro mode, this will make it load all of its bandwidth keys into the heap
3. Reboot
4. Login via telnet (pick your method)

Run this shell script command

cat /proc/$(pidof main.app)/maps | grep heap | while read line; do start=0x$(echo $line | cut -c 0-8); end=0x$(echo $line | cut -c 10-18); dd if=/proc/$(pidof main.app)/mem bs=4096 skip=$(($start/4096)) count=$( echo $((($end-$start)/4096))) | grep -ohE "[A-Z0-9]{16}" | while read line; do echo "$line"; done; done

At the top of the heap will be keys for the following speeds, only some are recognized

50M*
70M
100M
150M*
200M
250M*
300M
350M
500M
750M*
1000M*

Yes that's right kiddies... there are keys for a 750Mhz and 1Ghz option

Someone want to kick their scope into 750/1000 mode and go fish?  Can the front end even handle those speeds?

And for tv84, with the right keys the name follows just like other siglents.. what we need to find out is if a 500M key does kick a 350M into 500M and does the front end hold up?


Edit:  After more looking around I saw that 750/1000 seems to be a generic thing they have going on.. but it did return as being in those modes so?

Also.. ran into this in another thread and it matches all my keys, this should full unlock anyone

https://repl.it/repls/DirectProbableTwintext

[tautech]

what we need to find out is if a 500M key does kick a 350M into 500M and does the front end hold up?

Why shouldn't it ? 
Earlier in this thread the -3dB point has already been established as ~570 MHz for the 500 MHz option however at best on 2 channels only, one from each ADC.

[chris009]

Edit:  After more looking around I saw that 750/1000 seems to be a generic thing they have going on.. but it did return as being in those modes so?

Also.. ran into this in another thread and it matches all my keys, this should full unlock anyone

https://repl.it/repls/GainsboroAlienatedText

If you move stuff in otheropt up into bwopt, you can get keys for options.

[Elasia]

what we need to find out is if a 500M key does kick a 350M into 500M and does the front end hold up?

Why shouldn't it ? 
Earlier in this thread the -3dB point has already been established as ~570 MHz for the 500 MHz option however at best on 2 channels only, one from each ADC.

Thats for the odd mystery of why there are a mix of 350 and 500s when pulling the bandwidth.txt file

I'd assume anyone that has a 500 marked one would go full on but does a 350?

[2N3055]

what we need to find out is if a 500M key does kick a 350M into 500M and does the front end hold up?

Why shouldn't it ? 
Earlier in this thread the -3dB point has already been established as ~570 MHz for the 500 MHz option however at best on 2 channels only, one from each ADC.

Thats for the odd mystery of why there are a mix of 350 and 500s when pulling the bandwidth.txt file

I'd assume anyone that has a 500 marked one would go full on but does a 350?

That is THE confusion. When file is pulled, they ALL got (electricaly) to 500 MHz, but some show 2354 and some show 2504 as model number.

By the way, 750 and 1000 MHz in license is there for sds5000 I presume. There is no chance that 2000X+ has front end capable of 1 GHz. Actually, even 5000X has two hardware versions: one that is 350/500 Mhz and other that is 500MHz/1GHz. If you want to unlock 5000X to 1 GHz you need to buy 500MHz ver.

[tv84]

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

Maybe not anymore...    Yet to confirm.