Author Topic: Siglent SDS2000X Plus (Read 739319 times)

miyagi · « **Reply #825 on:** April 09, 2020, 02:45:10 am »

@twizla, tv84 is right, the hardware is the same. I measured rise time with Picosecond 4015D, it is exactly 650ps. I also attached the frequency response plot, -3 dB point is roughly around 590MHz. If I have better attenuator and settings here, the result should be better, maybe can go up to 600-650 MHz.

miyagi · « **Reply #826 on:** April 09, 2020, 03:07:05 am »

@ TK, yes keep a copy is better. So for whom would want to try this. Here is a simple guide to upgrade SDS2104X Plus to 500 MHz.
1) Create a .txt file and input 'telnetd'
2) Save this file as 'siglent_device_startup.sh' . *** It must be this file name. And file format is .sh***
3) Copy file 'siglent_device_startup.sh' to the root directory of a USB drive.
4) Insert the USB drive to scope, and now turn on the power of scope. *** Must have the USB drive inserted before turn on the scope. And everytime you want to telnet to scope, you need to have the USB inserted before turn on it.***
5) After turn on scope with USB inserted, set scope LAN configuration as DHCP
6) Open a command window on PC, write 'telnet +IP address of your scope'
7) Now it requires user name and password.
User name: 'root'
Password: 'siglent_sds1000x_e'

After log in, write commands:
mount -o remount,rw,sync /usr/bin/siglent/firmdata0
rm /usr/bin/siglent/firmdata0/bandwidth.txt *** or as TK suggested, you can use another command to have a copy of this file just in case**

twizla · « **Reply #827 on:** April 09, 2020, 06:44:14 am »

Quote from: miyagi on April 09, 2020, 02:45:10 am

@twizla, tv84 is right, the hardware is the same. I measured rise time with Picosecond 4015D, it is exactly 650ps. I also attached the frequency response plot, -3 dB point is roughly around 590MHz. If I have better attenuator and settings here, the result should be better, maybe can go up to 600-650 MHz.

Many thanks miyagi. I have measured exactly same values of 650ps and 600MHz. This is than the frontend bandwidth, with all low-pass elements disabled.

I dont know how implemented, likely a set of RC lowpass, they limit the BW steps 100/200/350MHz.

miyagi · « **Reply #828 on:** April 09, 2020, 09:33:19 am »

You are welcome, twizla. I guess it's implemented in chips.

pga23 · « **Reply #829 on:** April 09, 2020, 11:18:28 am »

Maybe only probes are different?

I've bought SDS2104X Plus and I've four 200MHz probes, so I suppose it can be the only difference between 100MHz and 350/500MHz version.

douggoldberg · « **Reply #830 on:** April 09, 2020, 12:46:42 pm »

Thank you so much my friend. Your instructions are perfect. As soon as mine shows up I will make this improvement. Do you know the correct .txt file to reference to turn on the other options?

douggoldberg · « **Reply #831 on:** April 10, 2020, 10:52:36 pm »

I received my scope today. Three days after ordering from Germany. Excellent service. Sadly Miyagi's update method did not work. I get a refused connection when I try to TELNET in with Putty. The scope can see the startup.sh file that has the telnetd but I dont think its reading it on startup. Any thoughts?

TK · « **Reply #832 on:** April 10, 2020, 11:03:52 pm »

Are you using the full name siglent_device_startup.sh or just startup.sh?

douggoldberg · « **Reply #833 on:** April 10, 2020, 11:13:00 pm »

I used the full name as specified by Miyagi. I can hit the scope via a web browser so i know its on my network and I have the correct IP.

Martin72 · « **Reply #834 on:** April 10, 2020, 11:17:40 pm »

I would be glad to hear about your experiences with the scope itself, at the first time.

douggoldberg · « **Reply #835 on:** April 10, 2020, 11:24:52 pm »

I played with it for a few hours. Its a very impressive instrument. Coming from a non-touch screen (1202X+) its a revelation. I love the touch control and its very responsive. Its going to take me a bit to get used to the menu structure though. I do need the I2S decoding as I do a lot of digital audio work. The FFT is actually better than I thought. I have a dedicated audio interface for analog signal capture (RTX 6001) that runs FFT's on the PC. Overall Im very happy I just want to get it all the goodies working ...

Martin72 · « **Reply #836 on:** April 10, 2020, 11:33:00 pm »

"Problem" is, except the bandwith, you already have all the goodies in trial versions on board.

douggoldberg · « **Reply #837 on:** April 10, 2020, 11:38:32 pm »

Martin, Of course you are correct. The bandwidth is the big "prize".

TK · « **Reply #838 on:** April 10, 2020, 11:41:47 pm »

Quote from: douggoldberg on April 10, 2020, 11:13:00 pm

I used the full name as specified by Miyagi. I can hit the scope via a web browser so i know its on my network and I have the correct IP.

It might not be opening standard port 23 for telnet. @Miyagi, do you know the port number for telnet connection?

douggoldberg · « **Reply #839 on:** April 10, 2020, 11:42:20 pm »

Anybody able to make Miyagi's technique work?

TK · « **Reply #840 on:** April 10, 2020, 11:48:49 pm »

Quote from: douggoldberg on April 10, 2020, 11:42:20 pm

Anybody able to make Miyagi's technique work?

Try telnet to port 5024

douggoldberg · « **Reply #841 on:** April 11, 2020, 12:18:09 am »

That got me right in no password. Hmm. Should I try the scripts now?

douggoldberg · « **Reply #842 on:** April 11, 2020, 12:23:08 am »

tried his scripts, did not effect any change. Bummer.

douggoldberg · « **Reply #843 on:** April 11, 2020, 12:30:49 am »

Looks like this port is SCPI interface. Well at least I know I can telnet it to that.

douggoldberg · « **Reply #844 on:** April 11, 2020, 12:56:47 am »

Where's TV84 when you need him....

TK · « **Reply #845 on:** April 11, 2020, 01:57:59 am »

I think TV84 is in Europe and probably sleeping at this moment

TK · « **Reply #846 on:** April 11, 2020, 02:22:05 am »

Quote from: douggoldberg on April 11, 2020, 12:30:49 am

Looks like this port is SCPI interface. Well at least I know I can telnet it to that.

You can try running nmap on your PC/laptop to check which ports are opened on the scope

stafil · « **Reply #847 on:** April 11, 2020, 02:52:34 am »

Quote from: douggoldberg on April 10, 2020, 11:13:00 pm

I used the full name as specified by Miyagi. I can hit the scope via a web browser so i know its on my network and I have the correct IP.

What's your version? Maybe they closed the hole?

Are you using windows to create the file? Make sure that Windows doesn't add an extra file extension.

miyagi · « **Reply #848 on:** April 11, 2020, 02:56:41 am »

The port number for telnet is 23. Be sure the siglent_device_startup.sh file content is telnetd. The file must be in USB root directory, and USB should be inserted to scope, before turn on the scope.

Back2Volts · « **Reply #849 on:** April 11, 2020, 03:25:47 am »

Quote from: douggoldberg on April 10, 2020, 11:24:52 pm

... I do need the I2S decoding as I do a lot of digital audio work. ...

Can the four channels be used with the logic analyzer, without the special probe?


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Siglent SDS2000X Plus (Read 739319 times)

Share me