Author Topic: Siglent SDG2042X Hack door closed (Read 86304 times)

hafrse · « **Reply #50 on:** May 28, 2019, 09:08:14 am »

Hello,

I have a 2042X with product code SDG2122X and have 2.01.01.22R6 frimware installed and I want to upgrade to 2.01.01.23R8. Do I need to worry for this upgrade to revert the unit back to 2042 using standard upgrade steps provided by siglent?
Thnaks

MRMILSTAR · « **Reply #51 on:** December 01, 2019, 05:42:37 am »

I just upgraded my SDG 2042X to the latest firmware release (2.01.01.35R3B1). I have not yet hacked my 2042 to enable the 120 MHz BW. I would like to do so now using the instructions listed previously in this post. Are these instructions compatible with the latest firmware release (2.01.01.35R3B1)?

xzswq21 · « **Reply #52 on:** December 09, 2019, 03:58:00 pm »

I need a 100MHz signal generator so I want to buy a siglent signal generator and I want to hack it. Do you recommend it? actually I can not afford to buy an expensive signal generator, our currency is useless

after 2 years I saved my money to buy a signal generator.

MRMILSTAR · « **Reply #53 on:** December 10, 2019, 04:11:16 am »

I've had my Siglent SDG2042X for about 2 years. I really like it. It is a quality piece of equipment. I highly recommend it. Now if I can just find out if the hack instructions work with the latest firmware, I can increase its bandwidth from 40 MHz to 120 MHz.

xzswq21 · « **Reply #54 on:** December 10, 2019, 08:15:46 am »

Quote from: MRMILSTAR on December 10, 2019, 04:11:16 am

I've had my Siglent SDG2042X for about 2 years. I really like it. It is a quality piece of equipment. I highly recommend it. Now if I can just find out if the hack instructions work with the latest firmware, I can increase its bandwidth from 40 MHz to 120 MHz.

some users said you should downgrade the FW and hack it, then you should upgrade the FW:
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg2409867/#msg2409867
have you tried it?
Thanks

MRMILSTAR · « **Reply #55 on:** December 10, 2019, 03:56:04 pm »

Quote from: xzswq21 on December 10, 2019, 08:15:46 am

Quote from: MRMILSTAR on December 10, 2019, 04:11:16 am
I've had my Siglent SDG2042X for about 2 years. I really like it. It is a quality piece of equipment. I highly recommend it. Now if I can just find out if the hack instructions work with the latest firmware, I can increase its bandwidth from 40 MHz to 120 MHz.
some users said you should downgrade the FW and hack it, then you should upgrade the FW:
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg2409867/#msg2409867
have you tried it?
Thanks

I tried that method about a year ago and it didn't work. The newer 14-step procedure listed in the May 14 post above seems to now include a new version of telnet that is loaded into the firmware. Perhaps that new telnet version eliminates the factory password which was the original problem with hacking. That is why I am asking about this new method.

hansibull · « **Reply #56 on:** December 13, 2019, 03:05:47 pm »

You can just upgrade to the latest FW and apply a patch that will temporarily enable telnet. I followed this guide a few weeks ago and it worked like a charm.

I was (easily) able to hack into an SDG2112X by following this guide.
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg2409867/#msg2409867

And by using the telnet_SDG2000X patch that can be downloaded from here.
https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1870091/#msg1870091

Calvin · « **Reply #57 on:** December 29, 2019, 08:54:07 am »

Hi,

I also finally ´freed´ my 2042 from its restrictions following John95´s instructions

Used putty as console and after solving some minor gui probs it worked well.
The probs I had appeared at step 6 and step10.
step6: first I couldn´t establish a connection with putty. I needed to realize that the 10101 instruction is the port number (putty preset was 23)
step10: couldn´t ´escape´ at first pressing ´ESC´ till I relaized that only after typing ´:´ something changed.
Updated the firmware from R3B1 to R3B2 and tested .... ok
Thanks alot for this great ´Howto´

regards
Calvin

65roadster · « **Reply #58 on:** January 07, 2020, 11:20:16 pm »

Bought my SDG2042X a few weeks ago. It's now upgraded to an SDG2122X. Thanks!

zybizg · « **Reply #59 on:** January 08, 2020, 01:15:55 am »

Bought my SDG2042X a two weeks ago. It's now upgraded to an SDG2122X. Thanks!

petert · « **Reply #60 on:** January 23, 2020, 04:18:23 am »

I followed the procedure as described in the post referenced by everyone: https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg2409867/#msg2409867

Before applying the hack my firmware version was: 2.01.01.23R8.

The model was upgraded and 120 MHz are available successfully, with the same version showing.

Later I updated to the latest firmware from https://siglentna.com/service-and-support/firmware-software/waveform-generators/#sdg2000x-series
which was 2.01.01.35R3B2 (Release Date 12.16.19 ) at the time of this writing.

Again, it worked successfully, although it restarted twice, and appeared to hang for a while, doing nothing. So don't be afraid if it does that, it's not a failure.

Small caveat:
Above and close to 40 MHz the voltage (peak to peak) measured on the 100MHz scope drops as the frequency increases. This was with proper 50 Ohm termination on the scope (suitable for DC-1GHz) and 50 Ohm output on the signal generator. Before doing the test, the scope was calibrated again.
For a 2Vpp output sine wave, it will drop roughly 100 mV (varies a bit) until it reaches 100 MHz, above that it slowly starts to drop a bit more, peaking at a loss of roughly 180 mV.

ebastler · « **Reply #61 on:** January 23, 2020, 02:05:24 pm »

Quote from: petert on January 23, 2020, 04:18:23 am

Small caveat:
Above and close to 40 MHz the voltage (peak to peak) measured on the 100MHz scope drops as the frequency increases. This was with proper 50 Ohm termination on the scope (suitable for DC-1GHz) and 50 Ohm output on the signal generator. Before doing the test, the scope was calibrated again.
For a 2Vpp output sine wave, it will drop roughly 100 mV (varies a bit) until it reaches 100 MHz, above that it slowly starts to drop a bit more, peaking at a loss of roughly 180 mV.

That might well be your oscilloscope's behavior, rather than the signal generator. Its sensitivity will roll off at higher frequencies, and should be down to half the amplitude at the nominal bandwidth. (If you have an "improved" DS1054Z, its real bandwidth was shown to be 130..150 MHz). So I would actually expect a more pronounced roll-off than what you describe here.

petert · « **Reply #62 on:** January 23, 2020, 02:21:26 pm »

Quote from: ebastler on January 23, 2020, 02:05:24 pm

(If you have an "improved" DS1054Z, its real bandwidth was shown to be 130..150 MHz). So I would actually expect a more pronounced roll-off than what you describe here.

I do have the DS1054Z modified to 100 MHz, yes. Do you have any reference (videos/graphs) for the real bandwidth being 130..150MHz?

Actually, you can see similar behavior in Dave's test: https://youtu.be/_Mup2VnXH_k?t=1276
The scope he uses seems to be a Tektronix MDO3104 which has a bandwidth of 1GHz.

ebastler · « **Reply #63 on:** January 23, 2020, 02:33:09 pm »

Quote from: petert on January 23, 2020, 02:21:26 pm

I do have the DS1054Z modified to 100 MHz, yes. Do you have any reference (videos/graphs) for the real bandwidth being 130..150MHz?

A couple of posts here. I think there was one with more comprehensive data, which I can't seem to find right now:
https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg2587188/#msg2587188
https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg2592816/#msg2592816
https://www.eevblog.com/forum/beginners/rogol-1054z-actual-bandwidth/msg1380072/#msg1380072

More data, but these were measured via the risetime. More optimistic numbers, but they are probably distorted by whatever trickery Rigol applies in the signal rendering:
https://www.eevblog.com/forum/testgear/rigol-ds1000z-now-comes-unlocked/msg1382907/#msg1382907

petert · « **Reply #64 on:** January 23, 2020, 02:37:52 pm »

Weird, now I noticed that I can't set the signal gen's output to higher than 5 Vpp if I go above 20 MHz. Up to 20 MHz I can set it up to 10 Vpp. I don't remember if that worked before the hack/firmware update. (Judging based on Dave's video linked above, it seemed to be possible...)

ebastler · « **Reply #65 on:** January 23, 2020, 02:53:12 pm »

Quote from: petert on January 23, 2020, 02:37:52 pm

Weird, now I noticed that I can't set the signal gen's output to higher than 5 Vpp if I go above 20 MHz. Up to 20 MHz I can set it up to 10 Vpp. I don't remember if that worked before the hack/firmware update. (Judging based on Dave's video linked above, it seemed to be possible...)

That's exactly what the spec sheets says, so should be alright.

https://www.batronix.com/files/Siglent/Funktionsgeneratoren/SDG2000X/SDG2000X_Datasheet_EN.pdf
(Page 8; stated values are cut in half if you use 50 Ohm termination, per footnote 1.)

petert · « **Reply #66 on:** January 23, 2020, 03:01:05 pm »

Right, under "Output Characterisics" it says

Quote

Max 20Vpp≤20MHz, HiZ load
Max 10Vpp>20MHz, HiZ load

And half the max voltages, for a 50 Ohm load, as you mentioned.

Measuring the output voltage on the scope is the same though, no matter if HiZ (10V) or 50 Ohm (5V) on the sig gen.

It still reads 10V on Dave's scope, so either they changed the max voltage since then or he had a 10x scaling for a 1Vpp input.

JohnG · « **Reply #67 on:** January 23, 2020, 06:06:52 pm »

Quote from: petert on January 23, 2020, 04:18:23 am

Small caveat:
Above and close to 40 MHz the voltage (peak to peak) measured on the 100MHz scope drops as the frequency increases. This was with proper 50 Ohm termination on the scope (suitable for DC-1GHz) and 50 Ohm output on the signal generator. Before doing the test, the scope was calibrated again.
For a 2Vpp output sine wave, it will drop roughly 100 mV (varies a bit) until it reaches 100 MHz, above that it slowly starts to drop a bit more, peaking at a loss of roughly 180 mV.

Are you using an external 50 terminator? If so, this will cause additional attenuation due to the RC network formed by the cable (50 ohm), the terminator (also 50 ohm), and the capacitance that appears in parallel with the 1 Mohm scope input. The pole frequency will be about (2*pi*25 ohm*Cin)^-1. It is probably enough to contribute significantly at 100 MHz.

Cheers,
John

RichHatch · « **Reply #68 on:** February 09, 2020, 01:17:08 am »

Hi Everyone,

Is the hack still available if my firmware is at 2.01.01.22R5?

Thanks

tautech · « **Reply #69 on:** February 09, 2020, 03:19:47 am »

Quote from: RichHatch on February 09, 2020, 01:17:08 am

Hi Everyone,

Is the hack still available if my firmware is at 2.01.01.22R5?

Thanks

Welcome to the forum.

Check the last couple of pages of this thread:
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/

agreen · « **Reply #70 on:** June 06, 2020, 03:25:11 pm »

I just applied it on 2.01.01.35R and it worked fine.

stefi01 · « **Reply #71 on:** July 08, 2020, 02:48:44 am »

Call me dumb or what ever but when I get to step 9 "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>"
can you explain or show me how exactly this looks after, i really do not want to mess this up.
like do i delete everything and every line between the license line and system info or?
i am using putty as thats what I use for Raspberry PI

Tjuurko · « **Reply #72 on:** July 08, 2020, 10:55:59 am »

For example SDG1000X:

Before
--------
<?xml version="1.0" encoding="UTF-8"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>SDG1YOURSERIAL</chip>
</serial_number>
<license><bandwidth_update_license>YOURLICENSEKEY11</bandwidth_update_license></license></system_information>
</device>
</nsp_system_info_root>

After
------
<?xml version="1.0" encoding="UTF-8"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>SDG1YOURSERIAL</chip>
</serial_number>
</system_information>
</device>
</nsp_system_info_root>

For SDG2042X should not be different.

stefi01 · « **Reply #73 on:** July 18, 2020, 05:27:18 pm »

thanks for your reply. a little more help please

using putty i made the changes but pressing the esc key followed by wq just displays 'q' is not implemented so how do i exit
i am using putty

Alex P · « **Reply #74 on:** July 19, 2020, 11:07:07 am »

Try :wq instead of wq


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

Author Topic: Siglent SDG2042X Hack door closed (Read 86304 times)

Share me