Siglent SDG2042X Hack door closed

[tv84]

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why do people continue to mess with the inner works of these SDG's when they can simply generate the BW license and insert it with the MCBD SCPI command? Why?? 

This method is old, riskier and should be abandoned. It's just a matter of doing a little more homework.

[dorkshoei]

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Well that was not clear to me.

Many people approach this via searching.  Doing that I found https://www.eevblog.com/forum/testgear/current-status-of-siglent-hacks/

It pointed me to: https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/

I found nothing recent in that thread and don't recall seeing any mention of "the SDS threads" (whatever they are; URL?) but I did find a reference to this thread.

The thread titled "current status of siglent hacks" sounds like a really good place to keep track of the current status ;-)

[ebastler]

Gentlemen,
Let me try close this old thread once and for all:
The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why not include an actual link to the information you are referring alluding to? 

[BmaxTom]

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'

[ebastler]

5. Enter the displayed serial number and device model in the script

Thanks! But where does "the script" come from?

[BmaxTom]

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3585507/#msg3585507

Google is your friend 

[ebastler]

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3585507/#msg3585507

Google is your friend 

Are you doing this on purpose, to set up a little treasure hunt?  
The post which you link to only mentions "the Github page" without any further details; not all that helpful.

[BmaxTom]

Google --> Lauszus/main.py

[dorkshoei]

Google --> Lauszus/main.py

Why can't you just paste the URL!. Good grief.

Google is your friend 

This is ignoring the fact that Google also brings up lots of threads here with stale info.

This forum is comical about arranging info.  If you've been on a thread since it's inception you know where "all the bodies are buried" but there is little appreciation for someone who's new to the discussion.

[bdunham7]

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why do people continue to mess with the inner works of these SDG's when they can simply generate the BW license and insert it with the MCBD SCPI command? Why?? 

This method is old, riskier and should be abandoned. It's just a matter of doing a little more homework.

OK, so I have an SDG2042122X that was hacked using old methods and now has a serial number of 0123456789 or somesuch.  Any thoughts on undoing that and using the more modern methods?  Or should I just back away slowly and leave it alone, since it works?

[dorkshoei]

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why do people continue to mess with the inner works of these SDG's when they can simply generate the BW license and insert it with the MCBD SCPI command? Why?? 

This method is old, riskier and should be abandoned. It's just a matter of doing a little more homework.

OK, so I have an SDG2042122X that was hacked using old methods and now has a serial number of 0123456789 or somesuch.  Any thoughts on undoing that and using the more modern methods?  Or should I just back away slowly and leave it alone, since it works?

One of the steps was to backup the file

/usr/bin/siglent/firmdata0/NSP_system_info.xml -> /usr/bin/siglent/firmdata0/NSP_system_info.xml.orig

I would imagine you could just restore but I've not tried it, nor do I know if the new method causes the same.

[n3mmr]

The first link here is sort of a manual for the keygen python script, the second is, I believe, the correct link to find the script.

Read the manual first, or you may get confused.

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3822731/#msg3822731

https://repl.it/repls/DirectProbableTwintext

[Hearingaids]

I hate to beat a dead horse, but. I ran the keygen script and compared the 40M key generated to the key returned when I executed an MCBD?  command on my stock 2042x.
My machine’s stock 40M key is identical to the keygen generated key’s last 14 digits. There’s my question. Keygen generates a 16digit key, but the queried key on my stock 2042 is only 14 digits.
Is there something wrong here?
Do I enter the keygen generated key for 120M with all 16 digits?
Thx for any help!

[tv84]

Enter the generated key.

[Hearingaids]

Thx much. That worked.

[RichHatch]

I have a SDG2042x and would like to upgrade it to 120MHZ, could you tell where the step by step guide would be to upgrade my generator?

Thanks for your help!

[ozkarah]

Use the following procedure. Works like a charm.

recap the steps scattered around to here.

----------------------------------------------------------------------------------------
1) SDG2042X: utility->system->system info, note down your Serial number and Software version. for example: 2.01.01.23R8
2) USB drive: format USB drive to FAT format, with MBR (master boot record) scheme. If you use GUID scheme, SDG2402X will not recognize it. It tells you it is removing media drive even you are inserting it in.
3) Firmware: goto https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1870091/#msg1870091, and download telnet_SDG2000X.zip, unzip to telnet_SDG2000X.ADS, put it on USB drive
4) SDG2042X: hook Ethernet cable, turn on SDG2042X, utility->interface->LAN Setup->DHCP on, write down IP address, for example: 192.168.1.20
5) SDG2042X: Insert USB Stick into front panel USB socket, put SDG2042X to utility->/System/Firmware Upgrade->USB0->find file: telnet_SDG2000X.ADS->Recall, updating starts and fails after a while. Yes, it fails. So your version is never changed.
6) SDG2042X: LEAVE POWER ON SDG
7) computer console: access to SDG2042X file. type: telnet <SDG IP address> <SPACE> 10101 <RETURN>, for example: telnet 192.168.1.20 10101
6) computer console, mount driver as writable. type: mount -o remount,rw ubi2_0 /usr/bin/siglent/firmdata0
7) computer console, make a backup. type: cp /usr/bin/siglent/firmdata0/NSP_system_info.xml /usr/bin/siglent/firmdata0/NSP_system_info.xml.orig
computer console, use "vi" editor to edit one file. type: vi /usr/bin/siglent/firmdata0/NSP_system_info.xml
9) computer console, move cursor down by typing "j", and right by "l" to the very first letter "<" of the line <license> and press "x" to delete anything between and including "<license>" and "</license>". After deletion, this line becomes only has "</system_information>". if anything goes wrong, you could exit "vi" editor by "esc" and ":", and "q!", and redo it again.
10) computer console, press the ESC key, then type: "wq" and <RETURN> to save the file
11) remote computer console, type: "sync"
12) SDG2042X: remove USB stick
13) SDG2042X: turn power OFF
14) SDG2042X: check utility->system->system info, and check product type and Serial Number

[Johnny B Good]

 I was comparing my copy of those instructions to make sure I hadn't missed a more recent version and noticed I had copied the exact same set quoted by @Aqunity who'd noticed a couple of minor typos as mentioned here:

===========================================================================================
Offline Aqunity
Newbie
Posts: 2
Country: ca
View Profile Email Personal Message (Offline)

Re: Siglent SDG2042X Hack door closed
« Reply #89 on: October 03, 2020, 04:55:57 pm »
Say ThanksReplyQuote
Thanks so much John this process worked for me.
I had software version 2.01.01.23R8

Two small things:
When you click the firmware link it doesn't work so copy and paste it into your web browser address bar and remove the comma at the end.

Step 10 should read:
             10) computer console, press the ESC key, then type: ":wq" and <RETURN> to save the file

The : in front of the wq is important as it does not work otherwise.

Quote from: john95 on May 14, 2019, 04:44:47 am
recap the steps scattered around to here.
===========================================================================================

 with the rest of his post being as per those very same instructions.

 Hopefully, this will help avoid the pitfalls of john95's otherwise perfect recapping of the process he'd gathered into one concise instruction set from the many and separate sources within this (and possibly other) thread(s) - it is a long time ago now!

[EDIT] Actually, it was July 2020 when I downloaded the collection of telnet ads files and, iirc, this was in anticipation of making an actual purchase of either an SDG1000X or SDG2000X series function generator (I hadn't quite made up my mind over which to go for).

 In the end, I went for an SDG1000X and returned it as "Not fit for purpose" by reason of it suffering a rather subtle oscillator fault (flicker noise like phase modulation) that I'd had great difficulty in convincing my supplier and the 'so called' Siglent tech support (including their head of European Marketing!) of the seriousness of this glaring (to me at least) defect, hence my returning it for a full refund and my purchasing an SDG2000X from another of Siglent's authorised UK agents.

 The original quoted instructions are now over 3 years old and john95's update just over 2 1/2 years old which is what led me check out my own copy

[blurpy]

I agree with tv84 regarding these "old" instructions that keep popping up.

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why do people continue to mess with the inner works of these SDG's when they can simply generate the BW license and insert it with the MCBD SCPI command? Why?? 

This method is old, riskier and should be abandoned. It's just a matter of doing a little more homework.

[gl738]

I bought my SDG2042X in 2022/04 with Firmware - 2.01.01.35R3B2. I used Python script and I have SDG2122X now. Working like a sharm. Thank you mr. tv84 for kicking me in the right direction.

[mawyatt]

I bought my SDG2042X in 2022/04 with Firmware - 2.01.01.35R3B2. I used Python script and I have SDG2122X now. Working like a sharm. Thank you mr. tv84 for kicking me in the right direction.

Same here regarding tv84

Best,

[Roger Need]

Some general questions... 

1. Did you find anything else changed (for the worse) after doing the hack or did it all work as before except for the higher frequency limit?

2. What do you do about future Siglent firmware updates?  Do you use the 2042X  or the 2122X  version?

Roger

[KG7AMV]

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'

[rf-loop]

Gentlemen,

Let me try close this old thread once and for all:

The method explained in this thread has been publicly superseded by the release of the python Siglent keygen (in the SDS threads) . 

Why do people continue to mess with the inner works of these SDG's when they can simply generate the BW license and insert it with the MCBD SCPI command? Why?? 

This method is old, riskier and should be abandoned. It's just a matter of doing a little more homework.

It should also be understood and taken into account, even if you buy a 120MHz model from a store, you may want / need changes to some functions, such as some parameter limits of some functions.
It is not possible with any license key. Instead, it could be said that if your fingers are faster than your brain and don’t really need anything other than frequency, using a license key is safer.

Example. I was not initially interested in the frequency of the SDG1032X model at all. The original real need was to get the Sweep pretty much longer than the short 500s limit set by the factory for which there is no real reason.  Of course I did it and now upper limit is 100ks (and modify some other limits also, example modulation) because I didn’t want to go buy another manufacturer’s device just because.

Summary: I do not fully agree with you. Both methods are useful. You can also buy a higher frequency model but instead, other modifications cannot even be purchased unless you choose a product from another manufacturer.
It’s far too simple to think that just the upper limit frequency would be that important thing - even though it seems to many to be the only object of thought.

[tv84]

Summary: I do not fully agree with you. Both methods are useful. You can also buy a higher frequency model but instead, other modifications cannot even be purchased unless you choose a product from another manufacturer.
It’s far too simple to think that just the upper limit frequency would be that important thing - even though it seems to many to be the only object of thought.

I was not referring to "your method" of extending the device boundaries. UNFORTUNATELY, AFAIK, no one in this thread was as that is a true hack.

"Your method" is an addon to any generated license and, as such, irreplaceable.