Siglent SDG2042X Hack door closed

[JOFlaherty]

This Works Simple Simple...

1. Establish a Telnet connection with the device, e.g. with PuTTy or MobaXterm (xxx.xxx.xxx.xxx:5024). Username and password are not required
2. Query the device serial number with 'MD5_SRLN?'
3. Query the device model with 'MD5_PR?'
4. Query the current code with 'MCBD?'
5. Enter the displayed serial number and device model in the script
6. Add option '120M' in the script or replace an existing e.g. '150M'
7. Run script
8. Compare the requested code with the one from the script ('40M' or '80M'). Must be correct otherwise the serial number or the model was not entered correctly
9. Send the displayed '120M' code to the device with the command 'MCBD xxxxxxxxxxxxxxxx'

Sorry for not following, exactly. I thought the 14-step procedure was a way to get around the disabled telnet access. Yet this "simple simple" starts with "establish a telnet connection". Is that possible to do some other way?

[blurpy]

Sorry for not following, exactly. I thought the 14-step procedure was a way to get around the disabled telnet access. Yet this "simple simple" starts with "establish a telnet connection". Is that possible to do some other way?

You are not connecting to the telnet interface (which is disabled), you are just using a telnet client to connect to the scpi interface so you can run the specified scpi commands. You can use a scpi client as well if you prefer.

[JOFlaherty]

Thank you, Blurpy, and the others who made this work. This is way simple, after figuring out how to get Putty to connect.

[mushroom]

SDG2042X
hardware 02-02-00-40-00
firmware 2.01.01.35R3B2
method : the magic script
using Visa Test Panel from the NI MAX utility : NI Measurement & Automation Explorer (copy/paste easier than with Telnet, and no tinkering with IPs and ports for connection)

became a SDG2122X

A waveform with multiple sines, triangles or whatever also works because it needs a 100 MHz BW in order to output a not too distorded square wave @ 20MHz (H5 = 100 Mhz).

Thanks !

[passedpawn]

SDG2042X
hardware 02-02-00-40-00
firmware 2.01.01.35R3B2
method : the magic script
using Visa Test Panel from the NI MAX utility : NI Measurement & Automation Explorer (copy/paste easier than with Telnet, and no tinkering with IPs and ports for connection)

became a SDG2122X

A waveform with multiple sines, triangles or whatever also works because it needs a 100 MHz BW in order to output a not too distorded square wave @ 20MHz (H5 = 100 Mhz).

Thanks !

I happened to have this software on my PC (I really hate NI software and I can't imagine how it got on there).  Anyway, the NI software could query the device properly, but it was impossible to write because the NI software refused to send a command with a space in it.  It insisted on inserting stuff.

Anyway, I reverted to Putty, was really easy with that.  I also had to download the python compiler on my pc,  but that not an issue.  My sig generator is now upgraded.  Thanks all, especially the guy that made that keygen. 

[21KUZY073]

Hi. I found a link to a script where is written  "SDS2000X+" and it generates a BW 100 or 150MHz. 120MHz is not there. Do I need to rewrite the model and frequency or do I have a bad script? [ Specified attachment is not available ]

[Roger Need]

Hi. I found a link to a script where is written  "SDS2000X+" and it generates a BW 100 or 150MHz. 120MHz is not there. Do I need to rewrite the model and frequency or do I have a bad script? (Attachment Link)

1. Establish a Telnet connection with the device, e.g. with PuTTy or MobaXterm (xxx.xxx.xxx.xxx:5024). Username and password are not required
2. Query the device serial number with 'MD5_SRLN?'
3. Query the device model with 'MD5_PR?'
4. Query the current code with 'MCBD?'

5. Enter the displayed serial number and device model in the script
6. Add option '120M' in the script or replace an existing e.g. '150M'

7. Run script
8. Compare the requested code with the one from the script ('40M' or '80M'). Must be correct otherwise the serial number or the model was not entered correctly
9. Send the displayed '120M' code to the device with the command 'MCBD xxxxxxxxxxxxxxxx'

[21KUZY073]

Bit a problem to establish telnet connection via  puTTy but I finally succeed, I works!  Thank you all.

[RoV]

I hope someone can help, I wasn't able to find an answer in the thread.
I own an SDG2042X that I hacked several years ago, I think it was end of 2017, using the old hack; I believe no other method was available then.
Today, before applying the most recent FW version, I wanted to restore the original configuration and apply the keygen script. The serial was "0123456789" and wasn't changeable with an SCPI command like MD5_SRLN <sn>, so I entered "telnet 10101" using tv84 special firmware. I had a backup of the original /usr/bin/siglent/firmdata0/NSP_system_info.xml file and I restored it (and checked after sync and making the fs ro, I repeated the whole procedure several times...).
However, after instrument reboot, the serial read by MD5_SRLN? was again "0123456789". Reentering telnet and checking the file, the serial number was actually changed to "0123456789", while the license section was still there, so it was modified by the application code. The instrument was still recognized as a 2122X by the system software. I tried to insert an upgrade keygen to "120M" using MCBD and appearently it worked, because I found the string replicated in file NSP_system_info.xml.
At this point, I decided to upgrade to 37R3. The upgrade was successful, but still it was impossible to restore the serial. On an isolated boot case, the system returned to SDG2042X, while normally it boots as an SDG2122X. The serial now is no more "0123456789", but rather an empty string and I can't change it. It seems that the serial must be hidden elsewhere, not (or at least not only) in NSP_system_info.xml.
Any hint?
Ok, I could leave it as it is, since warranty has long expired. But an upgrade requiring the sn could always arrive...

[tautech]

But an upgrade requiring the sn could always arrive...

After how many years and it still hasn't ? 
I wouldn't hold my breath expecting it anytime soon.

[Martin72]

1. Establish a Telnet connection with the device, e.g. with PuTTy or MobaXterm (xxx.xxx.xxx.xxx:5024). Username and password are not required
2. Query the device serial number with 'MD5_SRLN?'
3. Query the device model with 'MD5_PR?'
4. Query the current code with 'MCBD?'
5. Enter the displayed serial number and device model in the script
6. Add option '120M' in the script or replace an existing e.g. '150M'
7. Run script
8. Compare the requested code with the one from the script ('40M' or '80M'). Must be correct otherwise the serial number or the model was not entered correctly
9. Send the displayed '120M' code to the device with the command 'MCBD xxxxxxxxxxxxxxxx'

Simply a perfect instruction 
Now I got 120Mhz...

The script I´ve used from the link in this post:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3082536/#msg3082536
Signed in with my google account and change the 150M to 120 M and that was it...
And of course model and ID.

Martin

Edit: pics are shuffled..

[Icom-man]

How to establish connection via puTTY?, it always disconnect me after entering IP adress > "connection refused"
Thanks in advance for support

[Martin72]

it always disconnect me after entering IP adress

This here perhaps forgotten:

xxx.xxx.xxx.xxx:5024

?

[Icom-man]

I wrote in putty 192.168.1.103:5024 and port 23
no luck, still "connection refused"
SDG2042x and computer are connected to the same router

[mushroom]

The port has to be in the port edit box, not in the IP address box.
Host name = 192.168.1.103
Port = 5024

[Icom-man]

it's magic, it works !!
Thank you very much to Martin72 and mushroom

[Exosia]

1. Establish a Telnet connection with the device, e.g. with PuTTy or MobaXterm (xxx.xxx.xxx.xxx:5024). Username and password are not required
2. Query the device serial number with 'MD5_SRLN?'
3. Query the device model with 'MD5_PR?'
4. Query the current code with 'MCBD?'
5. Enter the displayed serial number and device model in the script
6. Add option '120M' in the script or replace an existing e.g. '150M'
7. Run script
8. Compare the requested code with the one from the script ('40M' or '80M'). Must be correct otherwise the serial number or the model was not entered correctly
9. Send the displayed '120M' code to the device with the command 'MCBD xxxxxxxxxxxxxxxx'

Upgraded, no issues.

Software version: 2.01.01.37R6
Hardware version: 05-00-00-46-00

[gustavo61]

Hello people, I have a problem, I load the firmware, everything is fine, it fails as expected, I go to putty, I connect to the ip without putting 10101, I enter, it asks for a username and password, I write root, enter and paswor does not write me anything and I go to the wrong login, help please.

[gustavo61]

Fixed, I had to put 10101 instead of port 23, happy with my sdg

[phecap]

I hope someone can help, I wasn't able to find an answer in the thread.
I own an SDG2042X that I hacked several years ago, I think it was end of 2017, using the old hack; I believe no other method was available then.
Today, before applying the most recent FW version, I wanted to restore the original configuration and apply the keygen script. The serial was "0123456789" and wasn't changeable with an SCPI command like MD5_SRLN <sn>, so I entered "telnet 10101" using tv84 special firmware. I had a backup of the original /usr/bin/siglent/firmdata0/NSP_system_info.xml file and I restored it (and checked after sync and making the fs ro, I repeated the whole procedure several times...).
However, after instrument reboot, the serial read by MD5_SRLN? was again "0123456789". Reentering telnet and checking the file, the serial number was actually changed to "0123456789", while the license section was still there, so it was modified by the application code. The instrument was still recognized as a 2122X by the system software. I tried to insert an upgrade keygen to "120M" using MCBD and appearently it worked, because I found the string replicated in file NSP_system_info.xml.
At this point, I decided to upgrade to 37R3. The upgrade was successful, but still it was impossible to restore the serial. On an isolated boot case, the system returned to SDG2042X, while normally it boots as an SDG2122X. The serial now is no more "0123456789", but rather an empty string and I can't change it. It seems that the serial must be hidden elsewhere, not (or at least not only) in NSP_system_info.xml.
Any hint?
Ok, I could leave it as it is, since warranty has long expired. But an upgrade requiring the sn could always arrive...

Do you already have a solution for the problem?
I have exactly the same problem, made several attempts with the port 10101 root access.
Serial number 0123456789 returns again and again. However, I still haven't managed to update to version 37R3.

[RoV]

Do you already have a solution for the problem?
I have exactly the same problem, made several attempts with the port 10101 root access.
Serial number 0123456789 returns again and again. However, I still haven't managed to update to version 37R3.

Unfortunately not. But 37R3 works.

[mastershake]

so i am having zero luck here. i have now modded 5 other siglent models without any issues at all this is the first one bring a pain in the neck. what am i missing here.

just got the 2 in today i ordered price was just to good to pass on (250 each brand new) and i def want the 120 but are there other things that can be enabled safely and that are useable i.e. accurate?? i appreciate the help i got the scops both done easy with your all help. now i need to do these waveform gen's

i use putty all the time def know how to use it (in IT and web design) got the ethernet hooked up. tried multiple firmwares even ones people above said they had it work with just to be sure. turn on dhcp. got ip. run putty get to the scpi screen where it lists the siglent scpi and the correct model number. run the commands, input them into the script (same one i used for the previos sig's ive upgraded so i am to assume this script works?) tried without the scope id, tried to put the mc# intp the scope id just to try it. did change the 150m to 120m before running the script, put the resulting mcbd into putty for 120m and re started unit. still stuck at 40. tried this more then 20 times now and for the life of me i must be missing something. i did just get eye shots in both eyes so im a bit foggy but i had my daughter verify the numbers for me to make sure i was putting them in right she said all was good. using this script which worked perfect for the other models https://pastebin.com/fygAJy6y

any thoughts or ideas on what i could be doing wrong. i see the message in putty showing the connection to the siglent 2024 so it appears to be connecting right. currently on firmware 2.01.01.35R3B2 because previous poster said they had it work fine with that one. so i figured why not.

this is driving me insane. i ALMOST bought hantek's instead but when he offered these to me for less money and i knew they could do 120 i said ill def take those over the hanteks. but im stuck at 40 now and the hanteks at least stock are 100. can someone help me out. so much appreciated. one of these is going to a younger student who had cancer like i do and i wanted to do something nice to brighten his day up (im teaching him what i know and we connect because we both are dealing with terminal cancer) so i really want to get it working for him. you would def be helping make him smile a ton. this is one of the last pieces he needed. i gave him my old scope and one of my microscopes so he is over the moon and this would just top it off.

thank you so much in advance if you can help me out. i just cant figure this out and watch its prob something really dumb and im going to be like omg duh. sometimes all the cancer meds dont help my thinking they have me on actinium now which is def causing some brain fog.

[mastershake]

okay so i dont know if this was mentioned and i missed it or it was me being dumb tonight with my chemo brain as we call it but when running the script for the keygen you have to put the serial number in the scope id line NOT in the serial number line. once i did that worked like a charm.


now can i upgrade to the newest firmware or will that wipe out the 120m. these seem to be more basic then i thought but the hantek quality scared me and their comparable unit did go to 150 BUT the square for example only went to 10 and triangle only to 1 etc. the only wave that was "better" was the sine. but it did have a ton more overall features then these.

i also asked tautech but ill ask here also in case it may help someone else can any of the other features on the kegen list be unlocked on the 2024 units?

[KungFuJosh]

now can i upgrade to the newest firmware or will that wipe out the 120m.

i also asked tautech but ill ask here also in case it may help someone else can any of the other features on the kegen list be unlocked on the 2024 units?

AFAIK, firmware updates should likely never be an issue. Typically, when "improving" Siglent gear, you're unlocking features, not actually hacking anything. If a firmware update downgraded the "improvement" it would also do that to paying users as well. That free upgrade on your scope? Oops. Gone. That would obviously cause unwanted trouble.

You don't have a 2042 anymore, it's a 2122 now. 😉 What other features are you looking to unlock?

[mastershake]

i was mainly wondering if anything option wise was available like with the scopes. where you can add wifi etc with the codes. i dont see anything for these though