-
Hi,
Does anyone know what the 'upgradeability' status is of SDS5000 series scopes, as of Dec 2021?
Looking at the optional software decoding and triggering.
Also, can anyone confirm that probe attenuation factor (x10 etc) is still configurable from the UI and is not set via the contacts surrounding the analogue inputs on the front? From the UI screenshots I've seen, it looks so, but the manual doesn't say.
Thanks.
-
AFAIK the py scripts still work just fine with the latest FW.
Nothing has changed with input attenuation menus, manual, custom and autosense work as they always have. -
You mean this thread for the 2k scopes:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/125/
Thanks. -
You mean this thread for the 2k scopes:
Yes, the same script.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/125/
Thanks.
When installing options for customers as a matter of interest we checked the online script produced the same results as the official option code and any we did always matched. -
Hello tautech,
Thanks for the reply.
A bit off topic, but do you know if those scripts work with the new 6k scopes from Siglent?
Regards. -
Hello tautech,
I don't think anyone does just yet however you can be sure I'll be checking the SDS6204X demo unit we get in February.
Thanks for the reply.
A bit off topic, but do you know if those scripts work with the new 6k scopes from Siglent?
Regards.
At this time we're confident they will as they do for all models that have been released since scripts were first published. Regardless, the smart cookies here will crack the 6kX in short order. -
I tested SDS6000 Pro with TV84, the "MD5_PRD?" command did not respond. We tried several model names, such as SDS6000PRO/P/H .etc, but the lic generated could not be used.
-
I tested SDS6000 Pro with TV84, the "MD5_PRD?" command did not respond. We tried several model names, such as SDS6000PRO/P/H .etc, but the lic generated could not be used.
Use "LICENSE_PR?" Command to query the machine model
Thanks to @TV84 for working on this thread!
-
I received an SDS5034X from Welectron today. An update to 500MHz is currently available free of charge, even with 500MHz probes.
I activated the option via the siglenteu.com website and got the key. It works.
But what doesn't work is the adapted Pythonscript for the SDS2000X+ to enable further options. My scope has the latest software version 0.9.5R1. For the script I used my scopeid and the model name SDS5000X, as returned by the scpi command license_pr? For the 500MHz bandwidth extension I have both used the official name 4BW05, but also the 500M for the SDS2000X+. Additionally, I have varied the model name to SDS-5000X and also the scopeid with and without hyphens, lower and upper case.
In no case did I get the same key as the one from Siglent.
After the changeover, the new software version no longer offers an extension to 1GHz.
Does anyone know how to do it with this version or do you have to go back to the previous version. But then the question arises as to whether the key for the already activated 500 MHz version still works.
Regards Dieter -
The keygenerator needs the serialnr not the scopid. I made the same mistake comming from a SDS1000.
MY MISTAKE: IT IS THE OPPOSITE. You need scopeid not serialnr. Must be the beer. -
Thanks for the tip, but with the serial number it does not work either. I have tried using lower and upper case letters. What is the correct designation for the 500MHz option, 4BW05 as stated in the scope or 500M as for the SDS2000X+?
Here are the tried and tested values of the variables:
# original script for SDS2000x+:
#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')
#SCOPEID = 'sds5xhex5r0184' # serialnbr
SCOPEID = 'SDS5XHEX5R0184' # serialnbr
#SCOPEID = '4da12ee5deb6ef67' # scope id
Model = 'SDS5000X'
bwopt = ('4BW05', '4BW10', '500M', '1000M')
#bwopt = ('4bw05', '4bw10', '500m', '1000m')
The rest of the script is unchanged.
Regards Dieter -
The option name for 1GHz is 1000M. ScopeID is the hex numbers of the scope id in the options dialogs, without dashes.
The current firmware doesn't allow upgrading a 350M scope to 1000M. A plausible workaround is to install an older firmware, install the bandwidth option, and upgrade the firmware back to the latest version. However, you may want to uninstall one of the other options first as there is a bug in older firmware that can cause the options screen to lock up when you have all options enabled (other than 1000M).
-
After the changeover, the new software version no longer offers an extension to 1GHz.
Imho it makes sense, the 500Mhz version got different hardware afaik, so upgrading to 1Ghz is only possible with this version, not yours.
So forget the 1Ghz thing.
What the rest of the possible options concerns, lately I´ve got the permanent licenses for manchester and sent decoding via the known procedre.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-hack/msg3829499/#msg3829499 -
Well, it's possible but it won't quite make it to 1GHz. But 900MHz is better than a sharp stick in the eye... so why not.
-
My problem is not first of all whether the 1GHz can be activated under the new software version. That is the second step.
First of all, I need to clarify whether the SDS2000x+ script is applicable for the SDS5000X at all. I can easily check this, because I have a stock one for 500MHz. You can get the key for it on the siglenteu.com site. The algorithm behind the webpage must give the same result as the Python script. The input parameters on the webpage are model (selection list), option name (selection list), serial number (input) and authorised code (the authorisation to select options).
The webpage then returns the key '89ge ywwy h7tu dphy' for SDS5000X, SDS-5000X-4BW05, SDS5XHEX5R0184, <autcode>. And it works.
Incidentally, the same key is delivered for the SDS-5000X-2BW05 option (for the 2-channel version). This indicates that the option name for the script with 500M is probably correct, because the web page, via which all devices and their options can be activated, naturally wants to make the programming of the page as simple as possible. Therefore, the options for the bandwidth are probably mapped to a uniform name. Entering the serial number does not mean that the scopeid does not enter into the algorithm of the webpage, because the context should be known via an internal database.
The following parameters go into the python script: the model name here SDS5000X, the scopeid (or the serial number as Techneut thinks) and the option name. If you look at the python script, you will notice that upper or lower case letters give different results.
The actual code of the python script consists of the hashkey and the function gen. I don't want to publish both here because I don't know if it's legal. I use the one from https://replit.com. There are several there for the SDS2000x+, but they are all the same and only cosmetically different from each other (in terms of the useless parameter of the gen function). I have also changed it a bit cosmetically, but of course tested whether my version and the original version give the same result. They do.
Now, to clarify what results are delivered for upper and lower case, as well as for the option names, I use the following code:Code: [Select]import hashlib
serial = 'SDS5XHEX5R0184' # serialnbr
scopeid = '4da12ee5deb6ef67' # scopeid
idnbr = ( serial, serial.lower(), scopeid, scopeid.upper())
Model = 'SDS5000X'
bwopt = ('4BW05', '500M') #, 4BW10, 1000M, 'MAX', 'AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'PWA', 'MANC', 'SENT')
"""
hashkey = ...
def gen(opt, idn):
...
#end gen
"""
print('{:6} {:16} {:16} {:16} {:16}'.format('option', 'SERIALNBR', 'serialnbr', 'scopeid', 'SCOPEID'))
for opt in bwopt:
keys = ''
for idn in idnbr:
keys += gen(opt, idn).ljust(17)
#end for
print('{:6} {}'.format(opt, keys))
#end for
The Output:
option SERIALNBR serialnbr scopeid SCOPEID
4BW05 6ngeqt5zk66jeahm 932zp3mymuvefa3y tfxpm5dakugx323w uvppjmbxt8ytbzg3
500M wh6g29uuhhpqh3sv fru78bmyfmmqmt9c vc4u3rk2xfpdefmz 2qg249wgwbe3gyht
As you can see, none of the 500MHz keys correspond to the one I received from Siglent.
That's the problem for now!
You can try to find out what keys you can get with the data published here.
Regards Dieter
-
Hi Dieter,
The syntax of the bwopt scentence looks incorrect. I expected bwopt = ('arg1', 'arg2', ...... 'arg3')
Eric -
The syntax is right: bwopt = ('4BW05', '500M'). The rest of the line, beginning with '#' is comment in Python. Out commented other possible options.
Regards Dieter -
The syntax is right: bwopt = ('4BW05', '500M'). The rest of the line, beginning with '#' is comment in Python. Out commented other possible options.
Regards Dieter
Try the SCPI command:
MCBD ABRMT3GU488DG62Y -
@tv84
no change. Bandwidth 590MHz as before. Systemstatus SDS5054X as before.
Regards Dieter -
@tv84
no change. Bandwidth 590MHz as before. Systemstatus SDS5054X as before.
Show us a picture of the System Info menu and a copy of the firmdata0/bandwidth.txt file. I think your ScopeID must be wrong. -
I don't know whether it is true that there is one and only one key which will activate an option. To see if the overall process used by the script will work with your scope, just run the script for all the available options and then try to install one--say a coding option--that you don't have. I ran your SCOPEID and I got the same 500M key you did and the same 1000M key TV84 got, so we're all on the same page there. Pick an option you don't have and post the results.
What is the code you got from Siglent for the 500M option?
Edit: You can PM if you don't want to post it publicly. I don't thinking a whole bunch of us all pinging Siglent separately for a code for the same s/n scope is helpful to any cause. -
I upgraded my SDS5034X today tthrough the MBCD command. 500MHz worked at once, bandwith expansion and Info menu showed SDS5054X. With the 1000MHz nothing happend. I remembered an earlier message from bson about this and installed V 0.9.3R3. Now the 1000M worked. Actual bandwith is now 750MHz.
Frequenty is from 0,1GHz to 1GHz. Frequenty markers for picture 1 and 2 is 300, 400, 500 and 600MHz. Last picture 500, 600 700 and 800MHz
-
@tv84 and bdunham7
1. Try MSO Option. Got the following keys:
scopeid (lower letters) 74yk s33s mu8w 463p
SCOPEID (upper letters) gezq gupy 32kx 24dd
Response for keys in upper and lower letters: data invalid
2. siglent key for 500M, as mentioned before, is 89ge ywwy h7tu dphy
3. Bandwith.txt contains only the siglent key for 500M in upper letters and no <nl>
4. systemstatus see picture
@techneut
and what happens if you now install the new version 0.9.5R1?
Regards Dieter
-
Response for keys in upper and lower letters: data invalid
Interesting...
Maybe new year's news...
Can you telnet to the scope and do a memdump? -
I went to 0.9.5R3 immidiately after the 1000M upgrade. the last picture shows the result