Siglent SDS2000X Plus Hack

[Martin72]

Hi,

Got a pm a few weeks ago:

I am very happy if you can guide me to whatever I need in order to upgrade my coming Siglent.

I think I do it better here, so people can correct me, if I´m wrong...

Taken some screenshots listed below, according to the "guide" step by step.

First you have to open the link mentioned in the very first post here.
Second you got the message like in pic 2, you have to login to continue.
Third I use my google-account for loggin in.
Fourth and fifth, you are now into the program, where you have to erase the "zeros" in SCOPE ID and fill in the ID of your scope.
Then press "Run"...
Sixth now you got a couple of license keys which you have to enter in the options menu.
The several bandwith license key are making no sense except the ones for 200,350 and 500Mhz.
This was it.
Or don´t you agree, gentlemen here ? 
Therefore I wrote it here...

Martin

[Anik]

If I applied the BW option code for 350 MHz and later find that 100 MHz are sufficient for my projects, I understand that I can go back by entering a 100 MHz license code. But would it be possible somehow to find out (e.g. by a repair technician), that I had applied another code before? What about the 500MHz code (which removes the BW option from the menu)?

Thanks again,
Anik

[Martin72]

Hi,

Maybe some other guy did the same mistake as I did a few minutes before, so this is a reminder...
Regarding to the keygen, scope id means scope id, NOT scope serial number....
I was wondering why the generated keys looked so different to the ones I´ve installed (and backing it up in a txt file)...
Problem was 30cm before the screen..
Wanted to install the 2 last open licenses, Sent and Manchester.
So I´ve edited 'SENT' and 'MANC' in the options with no problem.
Run it, install it and done.

Martin

[probe]

Hi all,

I was so impressed with the SSA3021X plus (now liberated to a SVA1032X) that I ordered the SDS2104X plus, also to make use of the Logic analyser probe offer and the Batterfly November extra 10% discount.

Anyway, I ran the Python script and the scope now thinks it's a 2504X, with all options permanent. Now the question, does it makse sense to enter the 750M or 1000M code? (I had to go 100M->350M->500M to have the keys accepted, with a reboot in between.)

More than happy to leave it at 500M it doesn't make any sense or the frontend can't handle it.

[tautech]

Hi all,

I was so impressed with the SSA3021X plus (now liberated to a SVA1032X) that I ordered the SDS2104X plus, also to make use of the Logic analyser probe offer and the Batterfly November extra 10% discount.

Anyway, I ran the Python script and the scope now thinks it's a 2504X, with all options permanent. Now the question, does it makes sense to enter the 750M or 1000M code? (I had to go 100M->350M->500M to have the keys accepted, with a reboot in between.)

More than happy to leave it at 500M it doesn't make any sense or the frontend can't handle it.

None at all as the X Plus is just a 500 MHz design whereas those codes are better suited to the 1 GHz design of SDS5000X.
Enjoy your new scope. 

[NaxFM]

Hi eveyrone and happy Christmas!

So, i wanted to gift myself an sds2104x plus this year, does anybody knows if the keys are valid with the new firmware 1.3.9R6?
Does the firmware version makes any difference? And if it does, is it possible to downgrade to a version which is hackable?

[Martin72]

Hi,

Wasn´t and shouldn´t be a problem, actually.
You entry "true" license keys and "permanent" means permanent, regardless of the fw.

[Testtech]

Hi eveyrone and happy Christmas!

So, i wanted to gift myself an sds2104x plus this year, does anybody knows if the keys are valid with the new firmware 1.3.9R6?
Does the firmware version makes any difference? And if it does, is it possible to downgrade to a version which is hackable?

Apparently the keygen doesn't work with the new firmware 1.3.9R6. I just tried it, and none of the keys generated work...

[Martin72]

I´ve done this here with the latest firmware...

[Testtech]

OK, I think I have it, I entered the HEX scope ID including the - marks, that generated wrong keys.

Thanks for the help.

[Martin72]

 

[ZicoRio]

Hi all.
How do I get keys for SDS2102X (without Plus) ?

[FranciscogGomez]

I´ve done this here with the latest firmware...

Hi all,

I've a simple question, It's possbile to downgrade oscilloscope's firmware e.g. 1.3.7R5 ?
Sure, It worked with latest firmware version. however, Could be ane extra option, first downgrade firmware, "do the trick" and then upgarde.

cheers!

[Pluscrafter]

https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg4018144/#msg4018144

[ozkarah]

My SDS2104X+ scope has just come with the firmware version is 1.3.9R10.
Release notes say that the difference is compatibility with the new hardware revision (04-05).

Does anyone know what is changed with this new hardware revision and if the hack is compatible with this firmware?

[blurpy]

My SDS2104X+ scope has just come with the firmware version is 1.3.9R10.

Interesting note for 1.3.9R10:

This release cannot be downgraded to former releases.

Could this be the enabling of dynamic key for SDS2k+?

Perhaps you could check, like in this discussion?

1.3.9R6

In your NSP_system_info.xml is there any reference to a "Dynamic Key"?

[ozkarah]

Seems like it does not contain any dynamic key

[blurpy]

Seems like it does not contain any dynamic key

Nice, guess the downgrade protection is just a failsafe to keep people with the new hardware from bricking their device then.

Wonder too what the difference is.

Anyway, can't see any reason why the existing python script wouldn't work for you.

[ozkarah]

Seems like it does not contain any dynamic key

Nice, guess the downgrade protection is just a failsafe to keep people with the new hardware from bricking their device then.

Wonder too what the difference is.

Anyway, can't see any reason why the existing python script wouldn't work for you.

Thanks. I will try and inform in a couple of days.

[SpacedCowboy]

Thanks. I will try and inform in a couple of days.

I would be very interested in your results - I'm leaning towards getting a "low end" SDS2000X scope and *cough* "upgrading" it, over buying a Rigol and doing the same, but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...

[Martin72]

but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...

You can avoid this by buying the upgrades, step by step.. 

(Or wait for the next "all options included" round)

[SpacedCowboy]

but I'm leery of splashing that much cash if it turns out not to be upgradeable any more...

You can avoid this by buying the upgrades, step by step.. 

(Or wait for the next "all options included" round)

Awww, you're no fun

[ozkarah]

Guys, using telnet I backed up the configuration folders from the scope into a USB stick before trying the hack.

Here you can find the procedure:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg4130797/#msg4130797

[ozkarah]

My SDS2104X+ scope has just come with the firmware version is .
Release notes say that the difference is compatibility with the new hardware revision (04-05).

Does anyone know what is changed with this new hardware revision and if the hack is compatible with this firmware?

I can confirm that the hack works flawlessly with the latest version ( 1.3.9R10 ) 

[Martin72]

Excellent