Siglent SDS2000X Plus

[tautech]

My scope is next to my PC, but the only ethernet port is used for my incoming internet from the modem. And I don't have another cable long enough to go from scope to modem.

Get a cheap switch to have near the bench for all your LAN capable gear.

SDS2kX Plus Web connectivity is quite similar to 4ch X-E but much more powerful.

Set it up in much the same way and Save the IP address and just navigate to the scope Home page in a webrowser.

[Martin72]

My scope is next to my PC, but the only ethernet port is used for my incoming internet from the modem. And I don't have another cable long enough to go from scope to modem.

A switch doesn´t cost much:

https://www.amazon.de/-/en/TL-SG105-shielded-optimized-snooping-unmanaged/dp/B00A128S24/ref=sr_1_1?crid=24O5KGMYMU8EN&keywords=TP-Link+TL+SG105&qid=1690488015&sprefix=tp-link+tl+sg105%2Caps%2C89&sr=8-1

edit tautech was faster..

[MathWizard]

Ok I see EasyScope is not the same as Easywave, is I have Easyscope installed now, but I'm running the self-cal, and so far I can't see what's displayed on the scope screen.

[tautech]

Ok I see EasyScope is not the same as Easywave, is I have Easyscope installed now, but I'm running the self-cal, and so far I can't see what's displayed on the scope screen.

It's in the ES menus but not a patch on real webrowser control. 

Take your pick, a cheap switch or the TP-Link WiFi WiFi to LAN adapter used in Client mode I mentioned a few posts back.
Also linked in the OP if you hunt through the POI list.

[MathWizard]

Well I have EasyScope running, but when I click add scope, it's listed there under USB, but it says failed to connect ??

OK I rebooted the scope, and now here's a pic from Easyscope, I made a common-base Colpitt's oscillator.

Later I'll see what my 120MHz AGW gen looks like on this. I guess 1 of the next things I'll want, is a faster AGW,  .

[tautech]

Hoping you're running EasyScopeX.....

USB connection is very straightforward and then select the Virtual Panel for scope control as shown below with SDS1204X HD.

[MathWizard]

Yup ESX

The traces seem to have more aliasing then I remember from my 1204xe, IDK if that's just the bigger screen, or some settings. So far the menu's are pretty easy to use. I read that a lot of options are unlocked for the 1st while or some many uses. I should try the internal AWG, see if I can use it to do a bode plot of the CB amp I made.

I thought so, there's some issue with me trying to upload the PNG file the ESX saves. It's only ~2MB but the form says there's an error or it fails some security check, and to check with admins.

So like the 1st pic, I'll have to use snipping tool to take the screenshot.

[tautech]

The traces seem to have more aliasing then I remember from my 1204xe, IDK if that's just the bigger screen......

And double the sampling rate. 

You can engage 10 Bit mode but it tops out @100 MHz....don't get caught out like DJ when he did a teardown.

All options are free to use for 30 trial uses.....use them sparingly. 

[MathWizard]

I seem to have a legit issue, I'm using the internal AWG set to 20mVpp @2MHz, and channel's 3/4. And with CH3 on the common base input, I see the input trace at 10mV/div and 1mV/div settings, but it almost goes away on 2 and 5mV/div

Any idea what that's about ? It's SW version 1.5.2R2, FPGA ver 2022-05-23

[tautech]

Some is local RFI/EMI from somewhere. 
Cabling/connection ?

These modern sensitive DSO's will test all your probing/connections and the 20 MHz BW limit will help some when in a noisy environment.
Me, I'd rather have the sensitivity and then manage how the DSO displays the waveform and any associated noise as most often it is not actually in the DUT.

Trigger level is set too high and too near the top of the waveform, reduce it some.

[MathWizard]

Oh boy, it does it on Ch4 also, I changed trigger level, timebase, I was on 10bit res. The green trace is on the CB collector/output, and it was a lot bigger than the input, and it gets reduced quite a bit but not to near zero.

Now on Ch1/2 only, it's the same, the traces gets shrunken down, but not all the way, on 2mV and 5mV/div, on any timescale I tried, on 8bit or 10bit

[ Specified attachment is not available ]

The pic for 1mV/div was like for 10mV/div, but now the scope or ESX has stopped capturing, restarting ESX won't connect again !!

I did the full self-cal, took like 30minutes it seemed, right before I got ESX working.


With no probes attached, i can still see the noise getting reduced, on 2 and 5mV/div


I bought it new, from a legit retailer, not open box or used, not that I was told anyways. It had the protector still on the screen.

[tautech]

And when inputs are Ground coupled ?

[MathWizard]

Yeah I just updated to 1.5.2R3, and the problem is the same. And with coupling to GND, the Vpp that the measure displays, is ~200uVpp on 500u/1mV/div, and ~60uVpp on 2mV/d, ~130uV on 5mV/d, and 333uVpp on 10mV/div, so it's there too.

I'm guessing this will take a RMA to fix.

I'll try self-cal again.

[tautech]

Yeah I just updated to 1.5.2R3, and the problem is the same.
I'll try self-cal again.

[MathWizard]

Ok thank god that seemed to fix it, now it looks about right, when on 2/5mV. I unhooked the USB as well when I did the self-cal, so no ESX inference either. And it went about 5x quicker than before.

I'll have to get out my AWG and run some other checks. Thanks TauTech.

[KungFuJosh]

Don't forget, they recommend at least 30 minutes warm up time before self cal.

[MathWizard]

Yeah it wasn't that, I had on a few hours. Did anyone else ever have that problem ? That built in AWG is pretty handy, I hope it stays after the trial period. IDK what the return policy is from the place I bought it, so I'm not going to hack it for a couple of weeks at least, but I better put it to use, make sure there's no more bad surprises.

I have plenty of projects I could working on.

[Performa01]

I'm connected over USB, in utilities, I don't see any mention of USB, like in the manual, but it's doing something over it. In the LAN settings, I see an IP address, but IDK if that can work over USB. I tried it in firefox and it just times out. Can it be done over USB ?

No. Web interface only works over LAN (ethernet).

[smallfreak]

IDK what the return policy is from the place I bought it, so I'm not going to hack it for a couple of weeks at least

Adding a license key to enable a feature is a legit procedure, not a hack. If you decide to prolong your tests by calculating the needed numbers by yourself instead of paying someone to do this for you - rest assured, they are identical.

In case of a return, the added licenses or uses try count must get reset to factory defaults anyway.

But if you really think about returning the scope, you probably might not want to argue why you obviously bought a non refundable license key before deciding to keep the device. 

[MathWizard]

Yeah there's no rush on the hack.

I'm just going through the DC accuracy with my hacked SPD33003X and sdm3065X. The PSU is holding up well. A few of the scope channels are maybe a bit over the 3% of range setting, but maybe not if it's averaged. Like on 2V/div, no offset, currently 101mV on PSU, the mean value on ch2, the average is around 165mV, and it's jumping between say 140mV to 180.

A moment ago, ch3 was average ~160mV mean value, but now it's settled ~140mV, but I still see 170mV pop up on the mean value. It's been on ~2hrs.

Still on 2V/div, no offset, 652mV PSU, ch2 is ~700mV average, so just under the 60mV=3%.

At 6.101V, ch2 looks like ~6.18V average of the displayed mean, but I see 6.19xxx popping in. The other channels have ~6.10, 6.04, 6.06V

Now ~5-10min later, ch2 is ~6.16V average of the displayed mean. They're are all on 20MBW, 1x probes, 2us/div, 10bit, 50Mpts.

IDK how typical all this is, but like someone said on here, scopes aren't meant to be "precision" instruments. I've swapped probes around, and that made no real difference.

The lower ranges seemed in spec, most being no worse than 1.5-2%.

[H.O]

Remember that this has an 8bit ADC in it (as most scopes still do). It's not a DMM with 24 (or more) bits of resoultion.

You have 8 vertical divisions on the screen, you set the scope so each division represents 2V meaning there's 16V from bottom to top of the screen. Those 16V is digitized with that 8bit ADC.

16V/256=62.5mV per bit.

In reality is likely slighly "worse" than that. Your 100mV signal basically causes the ADC to flicker between a value of 1 and 2.

[MathWizard]

Yeah I should try the same thing with my sds1204x-e, I've had no issues with that, but it's probably way more accurate in my mind, than it really is.

[carlberg]

it would be nice to be able to link the oscilloscope to the sigrok / salae logic analyzer software. but unfortunately i cannot see any of these scope(s) on the wiki's supported hardware list

https://sigrok.org/wiki/Supported_hardware#Oscilloscopes

If you are using Linux (specifically Fedora 35) you can try out my build here: https://github.com/gralco/libsigrok/releases/tag/sds2000x_plus

Downloaded your build of libsigrok.so...
Should the list in Pulseview (Step 1: Choose the driver) now show a SDS2000X Plus device or should I use the existing SDS1000/SDS2000 device?
Havent got a SDS2104X Plus (but maybe soon), so I cant test it myself.

[gralco]

it would be nice to be able to link the oscilloscope to the sigrok / salae logic analyzer software. but unfortunately i cannot see any of these scope(s) on the wiki's supported hardware list

https://sigrok.org/wiki/Supported_hardware#Oscilloscopes

If you are using Linux (specifically Fedora 35) you can try out my build here: https://github.com/gralco/libsigrok/releases/tag/sds2000x_plus

Downloaded your build of libsigrok.so...
Should the list in Pulseview (Step 1: Choose the driver) now show a SDS2000X Plus device or should I use the existing SDS1000/SDS2000 device?
Havent got a SDS2104X Plus (but maybe soon), so I cant test it myself.

You would use the existing "Siglent SDS1000/SDS2000 (siglent-sds)" option.

[phecap]

I measured the noise floor of my SDS2140X plus at the full bandwidth (500 MHz).
At the vertical setting of 1mV/div this is 74uV, which is even better than the spec of 80uV.
But if I set the vertical to 5mV and higher, the floor noise also increases, while the gain decreases. At 10V/div this is even 131mV. See the attached screen dumps.
Can someone explain why this is so?

Oh, I forgot to mention that I terminated the input with an external 50 Ohm resistor.