Maybe we should make a script for the sdg only (just remove all things except 120Mhz bandwith (and 40Mhz for selfcontrol)) to avoid misunderstandment.
Maybe we should make a script for the sdg only (just remove all things except 120Mhz bandwith (and 40Mhz for selfcontrol)) to avoid misunderstandment.
Don't go that way as there's plenty of garbage around already. Those that can't solve that by themselves don't deserve to "hack" the thing.
Thanks for the "Guide for Dummies" @ghulands, I can confirm that an "improved" SDG2042X does indeed produce a clean 120MHz signal (checked on a 500MHz scope). Folks doing this with generators running newer firmware should note that the hack requires downgrading the firmware to 17R5 and then back up to 23R8 and then 37R6 in steps. It's also worth noting that new/larger USB flash drives don't seem to work; I had to dig up an old 128MB flash stick.
Perhaps the hardest thing about the hack these days is finding the actual instructions because the threads have become so long (68 pages)! The link of interest is here: https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg928681/#msg928681
Thanks for the "Guide for Dummies" @ghulands, I can confirm that an "improved" SDG2042X does indeed produce a clean 120MHz signal (checked on a 500MHz scope). Folks doing this with generators running newer firmware should note that the hack requires downgrading the firmware to 17R5 and then back up to 23R8 and then 37R6 in steps. It's also worth noting that new/larger USB flash drives don't seem to work; I had to dig up an old 128MB flash stick.
Perhaps the hardest thing about the hack these days is finding the actual instructions because the threads have become so long (68 pages)! The link of interest is here: https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg928681/#msg928681
Did you miss the much more recent process and just use one from 2016 ?
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg4599439/#msg4599439
Much much safer than mucking with OS code.
Hack report
I just get the unit today.
The keygen method still working
Minki misnamed his licence upgrade as a "hacking" exercise which carries no risk of turning his brand new SDG 2042X into a "brick", hence his "plunging straight into 'upgrading it'" straight out of the box.
The worst that can happen when using the keygen is that it simply rejects invalid licence keys with no harm done. I guess he must have thoughly researched the topic perhaps even to the point of having the keygen script ready to roll the minute he'd unpacked and checked it out.
Hackupdate report
I just get the unit today.
The keygen method still working
Without reading the full thread:
Is the -40- in the HW version info a hint, that there is some bandwidth specific HW involved and that the 120 HW might be different?
Edit: reading some of the thread: NO, the -40- is some kind of HW version counter, there are -35- or -46- devices in this thread.
But nevertheless: Any HW or performance differences known?
HW 06-00-00-46-00
Product type : SDG2042X
software unlock/upgrade script did not work for me. None of the options matched code in the device.
Thank you,
it sure can be I am doing something wrong, for the script is product name should be as on screenshot? should SCOPEID be padded with something to certain length?
😼 python3.11 ./SiglentKeygen.py
INFO: CHECK YOUR GENERATED KEY BEFOR ENTER A NEW ONE !!!
You get your bandwidth key by running "MCBD?" at the SCIP prompt
Compare your key with the generated key
INFO: IT HAVE TO BE SAME !!!
--------------------------------
Here are the bandwidth codes
Enter these codes over SCIP prompt
...
bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '120M','150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA')