Siglent SDS2000X Plus Hack

[tv84]

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

What is your SCPI answer to?

:syst:board?

[ozkarah]

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

What is your SCPI answer to?

:syst:board?

600bps_LIC-V1

Is it same with previous batches?

[tv84]

600bps_LIC-V1

Is it same with previous batches?

Correct. LIC-V1 means that you have the "classic" option licenses version.

[Martin72]

600bps_LIC-V1

After complete hacking, including bandwith to 500Mhz ?

[tv84]

600bps_LIC-V1

After complete hacking, including bandwith to 500Mhz ?

I think so because, as I've shown you, Siglent didn't code the thing correctly OR didn't expect anyone with a SDS2k+ to issue the command. So the FW is not prepared with the 2k+ designation for 500MHz.

[Martin72]

OK, I thought it was because of the missing bandwith upgrade.

[tv84]

OK, I thought it was because of the missing bandwith upgrade.

  And you thought well. I wrote from memory and was wrong... Let's see if ozkarah has upgraded to 500M and if his response was after upgrade.

[ozkarah]

OK, I thought it was because of the missing bandwith upgrade.

  And you thought well. I wrote from memory and was wrong... Let's see if ozkarah has upgraded to 500M and if his response was after upgrade.

Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?

Could you pls explain what is wrong with the response ?

[Martin72]

Maybe nothing, I got the response "4CH_500M" from my scope at home, one of the first sds2k+ and completely hacked.
Then I did the SCPI request on one of our brandnew 100Mhz SDS2k+ at work with no hack at all and get the same response like you got.
But that´s tv84´s playground, he will knows it better.

[ozkarah]

Maybe nothing, I got the response "4CH_500M" from my scope at home, one of the first sds2k+ and completely hacked.
Then I did the SCPI request on one of our brandnew 100Mhz SDS2k+ at work with no hack at all and get the same response like you got.
But that´s tv84´s playground, he will knows it better.

Did you do the bw hack using the keygen or removing the bandwidth file?

And  FYI: scope model is shown as SDS2504X Plus after the hack.

[Martin72]

Did you do the bw hack using the keygen or removing the bandwidth file?

It was "so long" time ago, I don´t know it anymore...
But it wasn´t with the license generator, except the (later added)Manchester and Sent decoding options I´ve used the known gen for.

[ozkarah]

Did you do the bw hack using the keygen or removing the bandwidth file?

It was "so long" time ago, I don´t know it anymore...
But it wasn´t with the license generator, except the (later added)Manchester and Sent decoding options I´ve used the known gen for.

That might be the cause of the difference.
I used the keygen for all. And I did the bandwidth upgrade following the 100->200->350->500 MHz path with rebooting after each.

[tv84]

Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?

Could you pls explain what is wrong with the response ?

Your SCPI response was obtained after you do the BW licensing up to 500MHz?

[ozkarah]

Yes, I did the bw update in 200->350-->500 MHz order. And the response was after the update?

Could you pls explain what is wrong with the response ?

Your SCPI response was obtained after you do the BW licensing up to 500MHz?

Yes

[MathWizard]

Hopefully next year I'll get a 2104Xplus, and if I can still upgrade it (for free), it should be the best scope for the money, I can get, and it should last me for years, as long as the chips last.

[jscm2000]

I just bought the SDS2074X+, the Chinese market is $930, the crack is still valid, the latest firmware version 1.3.9R12

[Helix70]

I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.

*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.

Any thoughts? I am using Keysight Interactive IO for the SCPI commands.

[ozkarah]

I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.

*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.

Any thoughts? I am using Keysight Interactive IO for the SCPI commands.

I have the same scope and FW. I get response on both commands without any lock up.
*IDN?:
Siglent Technologies,SDS2504X Plus,SDS2PEEC6Rxxx5,5.3.1.3.9R12
:syst:board?:
600bps_LIC-V1


1- Try using SCPI control interface of scope's web interface.
2- My device's hw version is 04-05 (new hw revision of Siglent) Please check if it is same with yours.
3- You can compare other system information :

•   Uboot OS Version: 5.3
•   FPGA Verison: 2022-02-08
•   CPLD Version: 05

4- In the Utility Menu, "Tek Mode" is off. Please check yours.

[tubularnut]

I just upgraded to R12 firmware, but when I connect via SCPI and issue :syst:board? my scope locks up, TCP/IP connection is lost, UI frozen and needs a hard power off to restart.

*IDN? works fine, gives Siglent Technologies,SDS2504X Plus,SDS2PDDQ5R2444,5.0.1.3.9R12.

Any thoughts? I am using Keysight Interactive IO for the SCPI commands.

I have the same scope and FW. I get response on both commands without any lock up.
*IDN?:
Siglent Technologies,SDS2504X Plus,SDS2PEEC6Rxxx5,5.3.1.3.9R12
:syst:board?:
600bps_LIC-V1

1- Try using SCPI control interface of scope's web interface.
2- My device's hw version is 04-05 (new hw revision of Siglent) Please check if it is same with yours.
3- You can compare other system information :

•   Uboot OS Version: 5.3
•   FPGA Verison: 2022-02-08
•   CPLD Version: 05

4- In the Utility Menu, "Tek Mode" is off. Please check yours.

Mine also locks up. Has done since the command was first published and I was on R6, now on R12

TEK mode off. Command sent through scope web interface.

•   Uboot OS Version: 5.0
•   FPGA Verison: 2021-07-16
•   CPLD Version: 03
•   HW: 02-04

[Martin72]

Hmm.....

The new owner of my sds2k+ reported me, he had a freeze while booting - This I´ve never got before in the 2.5yrs of using the scope.
One of the last things I´ve done was to upgrade the firmware from R6 to R12....
Maybe that was not a good idea.

[tv84]

It should be a bug but, just in case, I ask the guys with lock ups to check the file NSP_system_info.xml and see if there is any reference to a "Dynamic Key"?

[Domitronic]

Thanks to everyone who contributed to provide a keygen and also for foolproof instructions how to use it.

Also good to read the info about new firmware. Mine is still running 1.3.7R5 and i wanted to update soon. So reading the changelog the best option might be to update to 1.3.9R6 since the newer ones are mostly for compatibility with new hardware.

[Martin72]

R6 is a "must" as the FFT bug was fixed with it, the other ones don´t have an effect when the scope got the "old" hardware (as far I could test it before selling my scope).

[tubularnut]

I’ve not had any lock ups on R12 (running for a few weeks now), and on the older hardware.

Only locks on running the :syst:board? command.

No Dynamic Key in NSP file.

[FlPr]

Hack works.

V1.3.9R12

:syst:board?

600bps_LIC-V1