20R3 is still the current version as I got a copy just recently.
Thank you for your answer, tautech.
Good to know that 20R3 is still the current version, but why don't they publish it? If they distribute it, it must be tested and official.
20R3 is still the current version as I got a copy just recently.
Thank you for your answer, tautech.
Good to know that 20R3 is still the current version, but why don't they publish it? If they distribute it, it must be tested and official.
Probably as they're still working on it as I believe R3 was built to fix this issue:
https://www.eevblog.com/forum/testgear/sds2202x-e-calibrate-signal-problems-on-ch1/It seems a firmware upgrade put the scope out of whack although I have not experienced in any of the firmware installs we often do.
Hi RoV,
I wouldn't worry too much.
I guess that our chinese friends are working hard on a major fw release wich may well surprise us.
I hope you enjoy your "liberated" scope.
All the best,
Francis
Successfully applied hack to transform the SDS2202X-E to 2352X-E, thanks to information in the blog!
After PM from one user, I realized that a detailed upgrade procedure wasn't available. So I am attaching a suitable Python 3 script, containing instructions.
I used only '300' option.
Successfully applied hack to transform the SDS2202X-E to 2352X-E, thanks to information in the blog!
After PM from one user, I realized that a detailed upgrade procedure wasn't available. So I am attaching a suitable Python 3 script, containing instructions.
I used only '300' option.
Hi, thanks for the script.
So you used the "300M" option to get the upgrade to 2352X-E with 350MHz bandwidth?
If possible, could you check what your scope is displaying as "Product Type" in (press Utility button) > "System Status" menu after applying this patch?
What is the model reported by
*IDN? SCPI command?
Thank you!
Thank you, that's very helpful. I made a silly mistake of using the code for "350M"
and now the scope has a blank field in place of its Product Type. Huh.... I wonder if it's possible to remove a license code...
Thank you, that's very helpful. I made a silly mistake of using the code for "350M" and now the scope has a blank field in place of its Product Type. Huh.... I wonder if it's possible to remove a license code...
No need, just insert the correct code. Only one remains enabled.
Thank you very much!
Submitting a new code indeed worked and now my scope also reports SDS2352X-E - the upgrade seems to be successful.
For potential future readers of this thread, my config was:
Software Version: 1.1.19 R5
Uboot-OS version: 2.1
FPGA Version: 2019-08-12
Hardware version: 00-01
2202>2352
Software Version 1.1.20R3
UBoot-OS Version 2.1
FPGA Version 2021-03-17
Hardware Version 08-01
Spotted an update for these today.....finally the mystical version 20R3 !
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS2000X-E_V1.1.20R3_EN.zip
8.4MB
The release notes only mention compatibility for later HW versions.
I saw it a couple weeks ago. Downloaded, it is binary identical to the unofficial 20R3 found one year ago thanks to user rea here on eevblog.
Not really HW compatibility only: it has several improvements respect to 19R5. In particular, it solved a problem I had (see my post of sep 25 in this thread).