Siglent SDS2000X HD, 12bit, 2GSa/s high definition oscilloscope serie.

[2N3055]

Thank you both for your answers!

Then I guess the question is, if I can do Analysis -> Counter with statistics, is there any reason to bother with using the Measure Freq(C1) option?

Measure:Freq will follow the signal in capture.
Set awg for FM and do measurement on longer capture. Then set Track on Measurement:Freq.

Also with measurements you can measure on 4 channels at the same time...

[tv84]

PS: Why do I even bother? Performa already answered.... 

Essential for me. Performa's was beyond my understanding. 

[KungFuJosh]

Definitely both answers together were helpful for me. 😉

[Performa01]

Then I guess the question is, if I can do Analysis -> Counter with statistics, is there any reason to bother with using the Measure Freq(C1) option?

Well, there might be some reasons why you still use frequency measurements - here are a few:

• You can have as many frequency measurements in parallel as you like (up to the maximum in the respective measurement mode).
  
• You can measure the frequency not only of the input channels, but also in zoom, math, reference and memory channels as well.
  
• You can have a histogram in the measurement statistics.
  
• You can use Trend plots to observe the developement of the measurement value over time.
  
• You can have Track plots for showing the distribution of frequency (or any other time-related measurement) within a single record. You can do FM-demodulation with that.
  

[2N3055]

Then I guess the question is, if I can do Analysis -> Counter with statistics, is there any reason to bother with using the Measure Freq(C1) option?

Well, there might be some reasons why you still use frequency measurements - here are a few:

• You can have as many frequency measurements in parallel as you like (up to the maximum in the respective measurement mode).
  
• You can measure the frequency not only of the input channels, but also in zoom, math, reference and memory channels as well.
  
• You can have a histogram in the measurement statistics.
  
• You can use Trend plots to observe the developement of the measurement value over time.
  
• You can have Track plots for showing the distribution of frequency (or any other time-related measurement) within a single record. You can do FM-demodulation with that.
  

What he said...

Resistance is futile...

[p_mint]

Hello everyone,
thanks to the people here I became the owner of sds2kxhd. I will post the result from my unit in several posts. All channels, (1 of 3).

[p_mint]

Channels 1 and 3, (2 of 3).

[p_mint]

Channels 2 and 4, (3 of 3).

[Costas07]

Hi,
Finally, after one month and a half of waiting got delivered the order so I'm a new happy owner of SDS 2204X HD.
The build quality is indeed good. Still exploring it ...

[Bad_Driver]

I watched Dave's new video on the hyped 20k€++ HP.... sorry Keysight HD3 and was curious to see what the little SDS2000X HD will deliver with the same settings in the low signal test.

Dave's video at 37:17
https://youtu.be/amxBD2WzEA4?si=ce1IAdheSIsO_twb

Settings (from the video):
2 mV/Div, 2 us (I took 10 us to achieve same Pts/sec for FFT), 15uV, 50 MHz, -12 dBm Attenuator.

Also my first chance to present my new acquired Marconi/Aeroflex 2031 RF-generator.
Seems to come from the Bundeswehr (German Army), it has Pulse modulation for radar testing.
The Gen has only 300 power on hours  and was not expensive.

[Costas07]

Please could someone help with "unlocking" some options on SDS 2204X HD ?

[tv84]

Settings (from the video):
2 mV/Div, 2 us (I took 10 us to achieve same Pts/sec for FFT), 15uV, 50 MHz, -12 dBm Attenuator.

Could you repeat also with 10uV and/or 2uV, as Dave did (if I remember well...)?

[Bad_Driver]

Settings (from the video):
2 mV/Div, 2 us (I took 10 us to achieve same Pts/sec for FFT), 15uV, 50 MHz, -12 dBm Attenuator.

Could you repeat also with 10uV and/or 2uV, as Dave did (if I remember well...)?

Quick and dirty, must be checked. See attached. No additional attenuators.

#1 1 uV RMS (-107 dBm)
#2 -110dBm = 0.7 uV (RF Gen accepts only dBm when Vrms < 1 uV) but with 500 uV/Div

[tv84]

Choose the option:

1 - Your generator is good.
2 - Your scope is good.
3 - Both are good.

[Martin72]

1+2 = 3
I'm tempted to recreate that.
But I don't think I'll be able to do it because of the higher bandwidth, we'll see.

[Martin72]

Could you repeat also with 10uV and/or 2uV, as Dave did (if I remember well...)?

For the “Chapter” 37:10 - 14bit ADC TESTED
He had only used one setup.

[Bad_Driver]

I went thru the HP/KS HD3 datasheet (see first small picture) and tried to repeat measurements.
I used (nearly) the same settings and  it is interesting what I can achieve with the SDS2000 HD. Not bad!

Than I was looking for the limits what is possible.
RF Gen: 100 MHz, 1 uV RMS (2.8 uVpp)
SDS: 100mV/div (!!!), same FFT settings as before.

Now I need an explanation: 100 mV/div means about 1 V measurement range, 12 bit resolution means about 250 uV resolution. Why it is possible to find the 100 MHz peak of 3 uVpp in the FFT?

[gf]

Now I need an explanation: 100 mV/div means about 1 V measurement range, 12 bit resolution means about 250 uV resolution. Why it is possible to find the 100 MHz peak of 3 uVpp in the FFT?

1) There happens to be enough dithering noise, and 2) due to the large number of points, you get sufficient processing gain.

[Performa01]

Than I was looking for the limits what is possible.
RF Gen: 100 MHz, 1 uV RMS (2.8 uVpp)
SDS: 100mV/div (!!!), same FFT settings as before.

Now I need an explanation: 100 mV/div means about 1 V measurement range, 12 bit resolution means about 250 uV resolution. Why it is possible to find the 100 MHz peak of 3 uVpp in the FFT?

You're not really seeing it. The SDS2000X HD quite obviously happens to have a spurious response at exactly 100 MHz. This is why it often is a good idea to avoid such straight frequencies for critical tests. Even better: check in advance with a zero signal.

Dead giveaway: the level of a 1 µVrms signal should be -107 dBm, which is far below the noise floor, as expected.

You see -98 dBm, which corresponds to 2.8 µVrms. With a gross error like this, you should immediately get suspicious.

In principle, you could measure such low signals if you had a much longer FFT available - unfortunately, 2 Mpts won't be enough. For the 12-bit machines there is definitely enough (particularly LF) noise for dithering, so that you can exceed the 73 dB dynamic inherent to a 12-bit system even in the most insensitive 100 mV/div setting. It is differeent with just 8 bits.

[Bad_Driver]

You're not really seeing it. The SDS2000X HD quite obviously happens to have a spurious response at exactly 100 MHz. This is why it often is a good idea to avoid such straight frequencies for critical tests. Even better: check in advance with a zero signal.

Thanks Performa01, my doubts seems to be right!
I will look into this tomorrow again.

Do you have a solution for my question regarding the possibility to calculate rtHz power density from my post

https://www.eevblog.com/forum/testgear/siglent-sds3000x-hd-and-upgraded-sds1000x-hd/msg5633465/#msg5633465

?
Thanks!

[2N3055]

Do you have a solution for my question regarding the possibility to calculate rtHz power density from my post

https://www.eevblog.com/forum/testgear/siglent-sds3000x-hd-and-upgraded-sds1000x-hd/msg5633465/#msg5633465

?
Thanks!

Sorry, no way to do it on the scope at this moment.

[Bad_Driver]

With the advice of Performa01 in mind I did the measurement again at 97.7 MHz.
The limits seem to be around 3uV RMS for a signal to be found with the settings.
Below are spurious signals (yes, @100 MHz as well).
See pictures attached. Thanks again for the lesson learned.

[gf]

With the advice of Performa01 in mind I did the measurement again at 97.7 MHz.
The limits seem to be around 3uV RMS for a signal to be found with the settings.
Below are spurious signals (yes, @100 MHz as well).
See pictures attached. Thanks again for the lesson learned.

Since you have used only 500k FFT points, there should still be room for an improvement of about 2x .

[2N3055]

This is -50dBm from AWG, through 70dB of attenuation.
200Mhz BW limit to limit folding noise from higher frequencies.

[Bad_Driver]

Since you have used only 500k FFT points, there should still be room for an improvement of about 2x .

ok, here we go with 2MPts FFT.