Siglent SDS2000X Plus

[jundar]

Just wanna to confirm. The Telnet connection is still working on new devices.

Device: SDS2104X Plus
SW: 5.0.1.3.9R12
CPLD version: 3
Hardware version: 02.04

Port: 23
Login: root
Pswd: siglent_sds1000x_e

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.

[BillyO]

Just wanna to confirm. The Telnet connection is still working on new devices.

Device: SDS2104X Plus
SW: 5.0.1.3.9R12
CPLD version: 3
Hardware version: 02.04

Port: 23
Login: root
Pswd: siglent_sds1000x_e

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.

Hmmm...  I just get "Connection Refused" even before getting a login prompt.

[jundar]

Just wanna to confirm. The Telnet connection is still working on new devices.

Device: SDS2104X Plus
SW: 5.0.1.3.9R12
CPLD version: 3
Hardware version: 02.04

Port: 23
Login: root
Pswd: siglent_sds1000x_e

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.

Hmmm...  I just get "Connection Refused" even before getting a login prompt.

Make sure:
1. USB stick is formated as FAT32 (I've used old 1GB USB2 stick formated as FAT32)
2. File "siglent_device_startup.sh" created and placed in USB root directory of USB flash drive.
(Ensure your windows system is configured to show file extension and you DID NOT create file like "siglent_device_startup.sh.txt")
3. File contains just one single word - "telnetd"
4. USB is connected before oscilloscope is powered on.
5. You connect using plain Telnet protocol, correct IP address, and use a port 23. Putty in Telnet mode or regular Windows
"telnet" command is perfectly fine.
You should get prompt to enter user name.

[tautech]

Don't get it. 
What's the need for this ?

[BillyO]

Don't get it. 
What's the need for this ?

None.  Just had some idle time and wanted to look around.

[tautech]

Don't get it. 
What's the need for this ?

None.  Just had some idle time and wanted to look around.

Please do nothing more.

[jundar]

Don't get it. 
What's the need for this ?

I'm going to use telnet connection to make backups of firmware/config files before doing something else. It would be interesting to find where the information about usage of trial options is kept. Maybe, after "upgrades" in the case of warranty repair/replace it would be useful to restore the oscilloscope back to it original state.

[tautech]

Don't get it. 
What's the need for this ?

I'm going to use telnet connection to make backups of firmware/config files before doing something else. It would be interesting to find where the information about usage of trial options is kept. Maybe, after "upgrades" in the case of warranty repair/replace it would be useful to restore the oscilloscope back to it original state.

Please don't and instead have someone guide you through using the Python script. Much much safer.

[BillyO]

Please do nothing more.

No worries .. no longer have the time and probably won't remember next time I do.

[ozkarah]

Hi. Last week I received my second SDS2104X Plus.
Today, I upgraded the bandwidth option up to 500 MHz.

This time I created frequency response graphs of 200 MHz, 350 MHz, and 500 MHz options using the FFT function. (Sorry no 100 MHz, because this idea came after upgrading it to 200 Mhz.)
I used a sweep signal generated by TPI 1001-B synthesizer which is fairly flat (I assume since I don't have a spectrum analyzer) between 35-1000 MHz. 

[tautech]

Nice work, thanks.
FYI we already know a stock standard SDS2104X Plus has a -3dB point of ~185 MHz.
Maybe if you'd used multiple FFT markers and placed them each at the -3dB points we would have all that info in just one image. 

[ozkarah]

I did actually, but only for 350 MHz and 500 MHz options.
Here is 350 MHz. Looks like bandwidth is pretty generous. Measured 469 MHz. 




Also, for the 200 MHz option, I did some calculations on the graph and found something around 270 MHz.

[gf]

I used a sweep signal generated by TPI 1001-B synthesizer which is fairly flat (I assume since I don't have a spectrum analyzer) between 35-1000 MHz.
(Attachment Link)

I searched for the TPI 1001-B, and obviously it is based on the ADF4351. This synthesizer chip does not generate a sine wave. See figure 4 here.

[ozkarah]

That's right. During the sweep, harmonics are clearly visible.
But, it shouldn't affect the results since the sine wave is the fundamental component of the square wave. The rest are the harmonics at much higher frequencies.

[ozkarah]

Just wanna to confirm. The Telnet connection is still working on new devices.

Device: SDS2104X Plus
SW: 5.0.1.3.9R12
CPLD version: 3
Hardware version: 02.04

Port: 23
Login: root
Pswd: siglent_sds1000x_e

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.

As I know, telnet support is removed with  V1.5.2R1. So it should normally work with previous versions.  

[jundar]

Just wanna to confirm. The Telnet connection is still working on new devices.

Device: SDS2104X Plus
SW: 5.0.1.3.9R12
CPLD version: 3
Hardware version: 02.04

Port: 23
Login: root
Pswd: siglent_sds1000x_e

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.

As I know, telnet support is removed with  V1.5.2R1. So it should normally work with previous versions. 

Sad to hear...  Knowing Linux the telnet connection is very useful in some specific cases.

Is it safe to upgrade if the 100MHz scope is "cured" to be SDS2504XP ? Maybe someone tried and know for sure? In the case of issue, can the 1.5 firmware still be downgraded back to 1.3.9R12 version? I did not notice any warning about that.

[Martin72]

My former SDS2104Xplus was hacked from the beginning and in this time until I´ve sold it, I could do every firmware upgrade without a problem.
The reason is simple, the license keys generated are "true" ones.

[Peter_O]

+1. Same experience as Martin72 in all points mentioned.

[ozkarah]

+1
Don't know about downgradability of the v1.5. I wonder about it too. 

[tautech]

+1
Don't know about downgradability of the v1.5. I wonder about it too.

Never have I seen an upgrade effect licensing, official or otherwise, it just don't as Martin says.

[balnazzar]

@Tautech

Would you please ask Siglent to get telnet (or ssh) back with future firmware releases? As said by others, it can be useful.

Thanks.

[tautech]

@Tautech

Would you please ask Siglent to get telnet (or ssh) back with future firmware releases? As said by others, it can be useful.

Thanks.

What for ? 

[balnazzar]

@Tautech

Would you please ask Siglent to get telnet (or ssh) back with future firmware releases? As said by others, it can be useful.

Thanks.

What for ? 

Cannot think about any usage case, right now. But isn't it cool by itself having a full-fledged unix shell on your scope? 

[tautech]

@Tautech

Would you please ask Siglent to get telnet (or ssh) back with future firmware releases? As said by others, it can be useful.

Thanks.

What for ? 

Cannot think about any usage case, right now.

Good, please keep it that way as there is absolutely no need to venture into the innards of the DSO !
That's been all done before and there are no further answers any of us need.

[balnazzar]

@Tautech

Would you please ask Siglent to get telnet (or ssh) back with future firmware releases? As said by others, it can be useful.

Thanks.

What for ? 

Cannot think about any usage case, right now.

Good, please keep it that way as there is absolutely no need to venture into the innards of the DSO !
That's been all done before and there are no further answers any of us need.

If you are passionate about electronics, I'd say you should feel a compelling force that drives you toward tinkering with stuff, regardless of the actual benefit