Siglent SDS2000X Plus Hack

[KeBeNe]

with me there is the possibility to enter "SENT and MANCH" with key.
Unfortunately the keygens do not work for me anymore

https://repl.it/@wxq849034624/PrettyAbleGuiltware-1#main.py

i have saved my old keys these still work, the script returns completely different keys

edit:

i tried something else, added the phy-code in the appendix (thanks to the creator), here -> https://repl.it/languages/python3, ScopeID is clear and the created keys were correct again.
So I could activate the new options.

[Johnny B Good]

The problem is explained here:

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244

 I've never run any python scripts locally and I've now embarked upon a search for tutorials on the subject.

John

[KeBeNe]

The problem is explained here:

https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244

John

I did not see that, of course that explains everything...

[ehagerty]

I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.

Pretty please?

Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?

I ask because I get an error dialog saying 'Invalid Data' every time.

My data is as follows, with the last four digits obfuscated for obvious reasons.

scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"

Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.

[Johnny B Good]

I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.

Pretty please?

Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?

I ask because I get an error dialog saying 'Invalid Data' every time.

My data is as follows, with the last four digits obfuscated for obvious reasons.

scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"

Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.

 That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.

 I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt.

 BTW, you might want to switch the digits 5 and 7 round in the software version you just posted.

John

[ehagerty]

I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.

Pretty please?

Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?

I ask because I get an error dialog saying 'Invalid Data' every time.

My data is as follows, with the last four digits obfuscated for obvious reasons.

scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"

Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.

 That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.

 I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt.

 BTW, you might want to switch the digits 5 and 7 round in the software version you just posted.

John

Thank you SO very much for taking the time to reply John. I'm a software developer actually, so the python is cool for me. 

At present, the options menu item 'SDS_2000XP_4BW02' which is last on the list has no value - just 'optional'.  Is that what your's had - what you expect me to see before I enter any keys?

I have tried starting with 100M and 200M to no avail.  Can you/anyone confirm that I should not be using my 'real' product model with the code, but only 'SDS2000X+' exactly as typed there?

Thank you again so very much indeed!

ed

[Elasia]

Copy and paste the following code here, you must not be logged in for the page to work

https://repl.it/languages/python3

To find your scope id, use scpi command SCOPEID?

To enter keys, use scpi command LCISL optioncode,hexkey

To change bandwidth, use scpi command MCBD hexkey

-------

import hashlib

SCOPEID = '0000000000000000'
Model   = 'SDS2000X+'

bwopt = ('25M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')

hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'

def gen(x):
   h = hashlib.md5((
      hashkey +
      (Model+'\n').ljust(32, '\x00') +
      opt.ljust(5, '\x00') +
      2*((SCOPEID + '\n').ljust(32, '\x00')) +
      '\x00'*16).encode('ascii')
   ).digest()
   key = ''
   for b in h:
      if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
         m = b % 0x24
         b = m + (0x57 if m > 9 else 0x30)
      if b == 0x30: b = 0x32
      if b == 0x31: b = 0x33
      if b == 0x6c: b = 0x6d
      if b == 0x6f: b = 0x70
      key += chr(b)
   return key.upper()
   
for opt in bwopt:
   print('{:5} {}'.format(opt, gen(SCOPEID)))

--------

[ehagerty]

@elasia you are amazing, thank you!  I think what I was missing is that I was trying to work through the touch screen - I have not yet used scpi.  I will do my homework and endeavour to understand that approach and will follow your very kind instructions.  Thanks so much!

[Johnny B Good]

I'm hoping someone will help an old Aspie with what is probably an over literal interpretation of what is required for using the python script.

Pretty please?

Am I correct in understanding that upon turning on the scope:
1) I get my Scope ID from Utility -> System Setting -> System Status
2) I use those 16 characters, sans '-' dashes, using only lower case, and enter them into the python hashing script - replacing the value of the SCOPEID variable
3) I do /NOT/ put in my /ACTUAL/ model (SDS2104X+) but instead use the base model id of 'SDS2000X+' in the appropriate variable again in the python script
4) On the scope, under Utility -> Options I select the option 'SDS_2000XP_4BW02' and enter - first - the key value for 100M, all in lower case, then hit 'Install'?

I ask because I get an error dialog saying 'Invalid Data' every time.

My data is as follows, with the last four digits obfuscated for obvious reasons.

scope_id = "0040-001b-3da1-...."
serial_no = "SDS2PCBQ4R...."
model_no = "SDS2104X+"
software_version = "1.3.5R7"
uboot_versio = "5.0"
fpga_version = "2020-04-26"
cpld_version = "03"
hardware_version = "02-00"

Thank you to anyone willing to read this for your time, my apologies but I have read through the different threads in what I believe is a careful manner but I'm clearly being an idiot.

 That's pretty well correct. The only thing you need to edit in that script is the scope-id exactly as you described. Unfortunately, that script has been set to read only so any edits are simply ignored when you hit the run button. The only way now is to copy the content of that script file to another locally stored empty *.py file on your system and run it from a locally installed python interpreter. I'm not sure whether the imported hashlib on line 1 is a special library or just a standard one included with all recent versions of the Python interpreter.

 I'm running Linux Mint 17.1 and, in common with most Linux distros, Python is one of the many programming packages pre-installed on the system. Unfortunately for me, I've never knowingly run any python scripts (perl, yes since I use get_iplayer) so I landed up floundering around, trying to get my copy of that script to run. I even thought to redirect any output to a text file but it remained stubbornly empty after it ran with a ton of errors displayed on the console. TBH, it was late in my day (4:30 am!) so I wasn't too surprised with only an hour's worth of 'learning python' under my belt.

 BTW, you might want to switch the digits 5 and 7 round in the software version you just posted.

John

Thank you SO very much for taking the time to reply John. I'm a software developer actually, so the python is cool for me. 

At present, the options menu item 'SDS_2000XP_4BW02' which is last on the list has no value - just 'optional'.  Is that what your's had - what you expect me to see before I enter any keys?

I have tried starting with 100M and 200M to no avail.  Can you/anyone confirm that I should not be using my 'real' product model with the code, but only 'SDS2000X+' exactly as typed there?

I'm sorry but I also didn't follow your suggestion to swap the 5 and the 7 - the system status screen definitely says 1.3.5R7 but I assume I'm being thick?

Thank you again so very much indeed!

ed

 Here's a complete list of all the firmware versions to date. As you can see, ver  1.3.5R7 is not in that list, hence my assumption of a transcription error in your post.

Version Compatibility
Source Version
 Object Version
 Compatibility
1.3.5R10
 1.3.7R5
 Tested
1.3.5R5
 1.3.7R5
 Tested
1.3.5R3
 1.3.7R5
 Tested
1.3.5R5
 1.3.5R10
 Tested
1.3.5R3
 1.3.5R10
 Tested
1.3.5R3
 1.3.5R5
 Tested

 When I applied the keygen hacks the first time round (whilst the script could still be edited and run), that was a month or two back and I wasn't taking notes so my recollection is now a little hazy. However, having worked backwards from the 500MHz option before hitting the, afaicr, 200MHz option which would actually accept a licence key, the next BW option was the 350MHz one which I applied the licence key to, followed finally by the 500MHz option, at which point, the BW option disappears from the list. The current BW state now being identified by the change of model number to SDS2504X plus.

 My own options list now includes the two new options, "SENT" and "MANC" listed as Temporary with remaining times set to 30. All the other applied options, except the BW one, are listed as applied with XX in the remaining times column.

 The "4BW02"  looks like the 200MHz option to me (ISTR having to infer which of the BW options in the generated licence keys list was required for the displayed BW option and apply it to change the displayed BW option to the next higher one and "Rinse and repeat" until no more BW options were displayed after applying the 500MHz licence key.

 It looks to me as though it's still waiting to accept a valid license key to upgrade from the existing 100MHz BW to the next available BW option of 200MHz. If you're doing this for the first time with that script, you'll just keep seeing "Invalid Licence key" every time you use the 200MHz licence key on that generated list since it's simply the result of the preset 0000000000000000 value already displayed for the scope-id variable.

 The only way round the blockage is to copy and paste the contents of that script file into an empty *.py file stored on a local disk drive which will let you edit the scope-id variable with your actual scope-id. Actually, that's not strictly true. It seems you can get the script to run remotely by signing up (apparently, you can get away with using a fake email address) but if you can run run a correctly edited copy on your own machine, why give them the satisfaction of forcing you to sign up, even if it is with a fake email address?

 Keep the model number as shown in the script. It's only the scope-id that needs to be entered to generate a set of valid license keys for your scope.

 BTW, if you do manage to successfully run that script locally, please let us know. I'd appreciate an "Idiot's Guide" to doing likewise. However, I've already asked this favour from steve1515 in response to his posting here:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3323244/#msg3323244

 Just let me know first before launching into producing an idiot's guide.

[EDIT 2020-11-13 15:38 UTC] Don't bother, Elasia kindly provided the solution. I merely copied and pasted my already prepared local copy of the original script over the hello world example script and copied and pasted the results straight back to my empty report.txt file. I only wanted the last two items and the license keys worked!

John

[Johnny B Good]

@elasia you are amazing, thank you!  I think what I was missing is that I was trying to work through the touch screen - I have not yet used scpi.  I will do my homework and endeavour to understand that approach and will follow your very kind instructions.  Thanks so much!

 I've copied and pasted Elasia's excellent post into a text file for future reference.

 In my case, when it came to copying and pasting, I used my own already edited copy of the licence hack script and then pasted the results into an empty report.txt file I'd set up to redirect the output of my local python script run which had failed (hence the empty report.txt file so conveniently waiting to accept the results from the remote script run  ).

 You can get the scope-id from the System Setting > System Status screen info - no need to use any SCPI commands. Also, you can just use the on screen licence key entry in the options window in the Utility menu. It's only when you want to revert BW settings or try the oddball ones both below and above the 500MHz limit that don't appear in the on screen licence key entry system that you'll need to use SCPI commands.

 Getting this latest license hack script to run using your actual scope-id rather than the pre-loaded 0000000000000000, is the key to success. That and making a full copy of the script's output list of keys for safe keeping.

 Thanks to Elasia, it seems I don't need to learn Python after all (at least not yet)! 

John

[ehagerty]

Thank you again John, Elasia et al for so much kindness!

In scratching my head about that firmware numbering question, I went ahead and installed latest (1.3.7R5 at time of this writing).  Lo and behold, now things like the web interface 'magically' became available to me.  I should have heeded my own mantra - upgrade to latest before you get cross!

I took the web interface 'Instrument Control' approach for the UI, and upon doing so /carefully/, I found a single digit transposition error in my scope_id - which I imagine did the trick.

Bandwidth in the order of 100M-> 200M ->350M ->500M worked fine, as did the full list of software option keys.

In case it helps you or someone else, here is my final python script https://github.com/ehagerty/sds2000xplus.  I was not sure if this would constitute a legal liability in making the repo public - if anyone believes so do let me know.

All the best,

Ed

PS - now properly anonymised!

[Johnny B Good]

Thank you again John, Elasia et al for so much kindness!

In scratching my head about that firmware numbering question, I went ahead and installed latest (1.3.7R5 at time of this writing).  Lo and behold, now things like the web interface 'magically' became available to me.  I should have heeded my own mantra - upgrade to latest before you get cross!

I took the web interface 'Instrument Control' approach for the UI, and upon doing so /carefully/, I found a single digit transposition error in my scope_id - which I imagine did the trick.

Bandwidth in the order of 100M-> 200M ->350M ->500M worked fine, as did the full list of software option keys.

In case it helps you or someone else, here is my final python script https://github.com/ehagerty/sds2000xplus.  I was not sure if this would constitute a legal liability in making the repo public - if anyone believes so do let me know.

All the best,

Ed

 I don't know about the legal ramifications but I do hope the scope-id and serial number have been obfuscated. TBH, they look very real to me. I'd obfuscate or otherwise anonymise them quick smart if they are real numbers if I were you.

John

[Bravo]

Thanks for this. Worked a treat. I started with a 100 Mhz 4 channel & ended with a 500 Mhz 4 channel with AWG & MSO.

[tautech]

Thanks for this. Worked a treat. I started with a 100 Mhz 4 channel & ended with a 500 Mhz 4 channel with AWG & MSO.

Plus all the other options I hope !

Yeah you got yours just before the option package was offered for free with any model in the SDS2000X Plus range.

[mawyatt]

Had some free time and decided to try and up the SDS2102X Plus BW to 500MHz, it's previously been "enabled" to 350MHz. Ran the mentioned Python script to create the keys for various functions, which I enabled two that hadn't been enabled, these are SENT and Manch. This went fine from the "Options" menu, but as noted by others there is no BW Option Type shown in the Options table.

Followed the scope Operations Manual to telnet in and checked the ID with SCPI and command SCOPEID? and got the proper returned information. Now I'm stumped on how to enter the exact proper syntax for the SCPI command MCBD with the proper info for enabling the 500MHz BW. Tried MCBD key, MCBD <key>, or MCBD "key", these didn't work, so asking for help with the exact syntax with the SCPI command MCBD to enable the BW to 500MHz from 350MHz.

Best & Thanks in advance,

[tv84]

MCBD key (in uppercase)

PS: I hope you are not issuing SCPI commands on a telnet prompt...   

[mawyatt]

Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).

I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.

Maybe this is one of those that can't be upgraded beyond 350MHz??

Best,

[Elasia]

Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).

I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.

Maybe this is one of those that can't be upgraded beyond 350MHz??

Best,

I forget off the top of my head but there is a reason for it... the 350MHz only ones are a myth, check the main thread for the scope when I opened mine up and tv84 and I went forth hacking it.. reason is buried in there somewhere and how to deal with it

[tautech]

Tried MCBD KEY in upper case from the SCPI >> prompt (after open IP address 5024 from telnet prompt and getting the Welcome to the SCPI greeting).

I've tried this a couple times, and shut the scope down also. Still no luck, Model: still indicates SDS2353X Plus after rebooting.

Maybe this is one of those that can't be upgraded beyond 350MHz??

Best,

For the 2ch Plus, SDS2102X+ only the 100 to 350 MHz BW upgrade is officially offered: SDS2000XP-2BW03
Whereas the 4ch models have the full BW upgrade path, 100-200, 200-350, 350-500.

Therefore it may not be possible to bump the 2ch version to 500 MHz, IDK.
https://int.siglent.com/products-ware/sds2000xp/

[tv84]

 

Of course your scope still says SDS235X...  To change the model, you have to change the .CFG!

One thing is the model reference, the other is the BW. The scope should be at 500 MHz by now.

Arghhh.... You owe me a beer for finding this one again: here

[mawyatt]

Ok I've done a quick test and the scope BW has been extended to ~615MHz

I had thought the name would change as well, I recall it changed when I initially upgraded the scope from the Options section??

Later I'll try and get the proper model name changed by editing the .CFG file as mentioned.

BTW I owe you way more than a brew

Best,

[tv84]

Later I'll try and get the proper model name changed by editing the .CFG file as mentioned.

Simply copy the file I attached (the other thread) and overwrite yours. Sync and reboot.

[tubularnut]

Ok, I'm confused or being stupid?

Just taken delivery of an SDS2104X+ direct from Siglent, and a number of the options are showing as permanent, straight out of the box.

FG, FlexRay, CANFD, I2S, 1553B and PA are all showing "Permanent".

I though all these were paid options?

[tv84]

It's called "Promotion".

[tubularnut]

It's called "Promotion".

LOL, yes.

It wasn't showing on the web site when I ordered, but now I've gone back there, the promotion is showing, and because the order actually came direct from Siglent, it seems I automatically got the promotion upgrade 

Really only need to do the BW upgrade and I'll be very happy.