Hacking the Rigol MSO5000 - Dr Mefisto Licensing Method

[BTO]

HACKING THE RIGOL MSO5000 - Dr Mefisto's Fully Automatic License Activator

BACKGROUND :
This post exists because of the main rigol MSO5000 Post and specifically because of the python scripting method reverse engineered by Dr Mefisto (This is the VERSION 2 of the script)
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/2671/

Also because SMAS laid out their path to activation in a very easy to understand way.
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/2840/

But also because a few members have stated that there should be one simple place to come to instead of having to dig though almost 60 pages of discussion and then it's a matter of finding the files.
The unavoidable fact of these posts is that they will be long and will have many pages.

THE PROBLEM SUMMARIZED :
- As always it starts with us wanting to unlock all the features of the MSO5000 (or whatever scope it is at the time)

- as the method progressed it was quickly realized that rigol (Unlike the DS2000A) were not using "Symmetrical Encryption" but instead "Asymmetrical Encryption" which meant that since we didn't have Rigol's encryption key, we were not able to approach the solution in the same way. At this stage the "PATCH METHOD" was put into place. And it worked, but it had 1 problem... It would not survive a firmware upgrade. So in the future when the next upgrade came out and you installed it you would lose all your unlocked options.
 Same thing if you downgraded. But don't get me wrong... If you stayed on the same version you were totally fine and everything worked.

- Then in Post #2671 Dr Mefisto had a eureka moment and worked out a python script that would CORRECTLY LICENSE THE SCOPE. (Actually the original script was in an earlier post and Post 2671 is the version 2 / aka The Automated Script.

- However a lot of people found this challenging and difficult to perform. it became the case that faced with "Patch Method" vs "Python Licensing Method" it was seen much easier to do the former.

WE NOW HAVE A FULLY WORKING SOLUTION...

FIRST LET ME THROW SOME FEARS OUT OF THE WAY
It has become obvious also that even though everyone should upgrade to this method as it means.... when further upgrades come out you will have nothing to worry about and you'll just download the official upgrade from the Rigol website (No further hack or patching required). But even though everyone SHOULD, They are not doing it.

Why not ?

- one reason may be you're afraid of change and what may happen, because if it's working now with the patch why change ?
Answer : Because you'll have to anyway

- You've heard rumours of the scope being bricked

- You've heard people having problems with it

- You've heard that the script can damage your scope

LET ME PUT ALL THAT TO REST

- My scope started on V 1.3.0.3  (00.01.03.00.03) , i used the patch method and went up to 1.3.3.0 (Latest Version). All Options Unlocked
  I then Downgraded to 1.3.2.2 (During the downgrade all options are lost). I then used Dr Mefisto's script to license the scope and All Options were unlocked successfully.
  I then upgraded to version 1.3.3.0 ALL OPTIONS SURVIVED,  I then downgraded just to push my luck , to 1.3.0.3 ALL OPTIONS SURVIVED,  i even went as low as 1.1.4.4  ALL OPTIONS SURVIVED.

So Upgrading and downgrading is not a problem , But there's a catch, You can't downgrade via the operating system you have to do it in the Pre Boot Menu

- A Note on the Pre Boot Menu.  There are 2 Options   "Firmware Upgrade", "Restore Defaults" .  FIRMWARE UPGRADE both upgrades and downgrades your scope in a Pre O/S Environment.
  However RESTORE DEFAULTS Just restores your defaults,
IT DOES NOT Lower you to a lower version of firmware
IT DOES NOT take your scope back to it's original version (After you upgraded)
All it does is.. if you changed the settings in your scope, it restores them to stock settings.  This step is NOT necessary in order to upgrading, Nor does it avoid you bricking your scope if you don't do it.
it is a good step to do, but let there be no illusion, it's not a necessary step.

- I have , at the time of writing this post upgraded and downgraded my scope over 30 times just to see if i could brick it and around 3 of those times i used restore defaults, the rest i didn't. Nothing happened.  I have gone between the patch and back to the script method over and over.  THIS METHOD IS A VERY RELIABLE METHOD

- A WORD ON BRICKING YOUR SCOPE
1. You're probably not going to
2. IF YOU LOSE POWER during the FRAM copy process YES.. YOU'LL BRICK YOUR SCOPE
3. IF YOUR LOSE ETHERNET CONNECTION during the FRAM copy process... YES, YOU'LL BRICK YOUR SCOPE
Because the data stream cannot be interrupted until it gets to 100%  (this only applies to the .. maybe 2mins that the FRAM is actually being written to)

If this method doesn't work for you you can always revert back to the Patch Method if you wish.

- I have observed that most of the problems arise either from fear or lack of knowledge how to do this method  so......

HERE IS WHAT YOU NEED TO DO
(This post has been put up so that if you can get through it you won't need to watch the video) but i have included a video that will take you through it step by step.
and you can also ask me for help and i'll be happy to help you


STEP 1.
DOWNLOAD THE FOLLOWING
Rufus
https://rufus.ie/en/

Python
https://www.python.org/downloads/

THEN. GO TO MY MEGA CLOUD SERVER
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

Here you will find a few things that you'll need

1. Scope Firmware Version 1.3.2.2
2. Scope Firmware Version 1.3.3.0

3. Rigol_kg2.py   (Dr Mefisto's Script Version 2) ------ NOW OBSOLETE
3. Rigol_MSO_LicensingUtility_2.10b  -- CURRENT SCRIPT (as of 20th July 2024)

4. STEP BY STEP INSTRUCTIONAL PDF FILE (MSO5000 DrMefisto Licensing Method) (Also Attached)

OPTIONAL
- Downgrading to 1.3.2.2  Video (this video shows you how to get into the Pre Boot Menu)


THE ACTUAL UPGRADE PROCESS

I'm going to give you 2 options

OPTION 1 - I will BRIEFLY detail the steps in this post , You can take a crack at it if you feel competent, However i personally feel if you are competent enough you wouldn't be here in the first place.

OPTION 2 - There will be a DETAILED pdf of the steps at my MEGA cloud location , Download the pdf and follow that

NOW...
HERE ARE THE BRIEFLY OUTLINED STEPS that you'll have to do

(THESE STEPS ASSUME THAT YOU HAVE A DECENT DEGREE OF NETWORKING EXPERIENCE AND BASIC PROGRAMMING EXPERIENCE - Python is preferred but not necessary, But you MUST have had some experience actually programming from scratch, not just uploading sketches into arduino for example. you must be familiar with C.L.I. if you don't know what C.L.I. is then don't do this method. you must be familiar with flashing EEPROM Basics.)

Now, i'm not saying Dr Mefisto's method is hard, i'm just saying, if you want to take the quick road and just read this post and jump in the deep end, IT DOES REQUIRE TECHNICAL KNOWLEDGE.
The other option is the PDF walkthrough. But the method is easy, it's just very particular.

so...
- Get a USB Stick (up to 16GB)
- Download Rufus and format the USB stick to FAT32 File System (or... You can just use windows format if you like, but SOMETIMES this causes problems) Rufus is more reliable.
- Establish which firmware version your scope is on.

To do this upgrade you will need to start on Version 1.3.2.2 
The latest version as of today is 1.3.3.0
if your scope is not on the latest version, You will be upgrading to  1.3.3.0
But you must first do your backups. 

(NOTE : I AM ASSUMING A WINDOWS 10 PRO ENVIRONMENT - If you have Linux of Mac Make the appropriate Adjustments.

- if you are on 1.3.3.0 and patched , Put the 1.3.2.2 software version on your USB stick
(First use Step 1 and do your backups) , Then Use the STEP 2 GEL file and put it on your USB stick.

- if you are on 1.3.2.2 with no options installed (You're fine), You just need to download the 1.3.3.0 firmware, Use Step 1, Do your backups , Then use STEP 2 GEL file and put it on USB Stick  (Min. 2GB)

- Now you need to turn off your scope, Insert the USB stick into the scope, and Enter the PRE Boot menu and do the firmware ugprade
 (You can feel free to select RESTORE DEFAULTS if you want, it doesn't hurt anything )

- After that , Regardless of what version you started on, you will now be on Ver. 1.3.2.2
- If at this point you are on 1.3.2.2 and completed your Backups. NOW UPGRADE TO 1.3.3.0

- Now download the rigol_kg2.py script
THE CURRENT SCRIPT IS Rigol_MSO_LicensingUtility_2.10b.py

- Open your command shell  YOU HAVE THE CHOICE TO USE WINDOWS cmd.exe OR  WINDOWS POWERSHELL  (Powershell is recommended), it has had a higher success rate.
Start in Powershell though if not sure.

- now whatever directory your command prompt or Powershell is starting in, Copy your script to that location .

- NOW SET UP YOUR NETWORK
You need a router (Internet is not required) (But the downloaded files are)
You need a PC
The PC needs to be connected to a LAN Port in the back of your router
You need an MSO5000
the MSO5000 needs to be connected to a LAN Port in the back of your router
(This is a basic Star Toplogy Configuration)

MAKE SURE THE POWER IS RELIABLE
MAKE SURE THE ETHERNET CABLES ARE PLUGGED IN PROPERLY
Make sure you don't have a lightning storm going on or power outtages
Make sure you don't have shit power boards and that everything is securely plugged in and can't fall out
 (YOU'VE BEEN WARNED... IF YOU BRICK YOUR SCOPE IT'S BECAUSE YOU IGNORED THIS)

Now that everything is connected

- Download Python
_ Install Python (this is the part where ... if you're not sure... Read the PDF or watch the video)
If you install python and run it and you can't connect to the scope (Uninstall Python and do not proceed with this method, but instead do the PDF or Video method). i'm assuming here you know
how to install python correctly and run it and have basic programming experience.

- Now take that USB stick out of your scope

- Obtain the scopes IP Address and Use Command prompt or powershell to run a ping command to see if your PC is communicating with it.
IF YES... Proceed
IF NO... Troubleshoot the network
Stay on AUTO and DHCP (Try to avoid using STATIC IP)

- TYPE   

Code: [Select]

pythonInto the command shell or powershell to see if it connects to the python interpreter
if it does
- TYPE 

Code: [Select]

exit()  and press enter   (do not enter the commands directly from the python interpreter) Use cmd or Powershell only to interface with the interpreter
Now you want to see what options you have before you proceed  (ASSUME MY RIGOL SCOPE IP ADDRESS IS 10.1.1.666) 
TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -h 10.1.1.666Press ENTER
this will bring up the help menu (you can do no harm to your scope by doing this)
The options we are interested in  the SWITCHES that we are interested in are
-h HELP   --------------------------------- (THIS CANNOT HARM YOUR SCOPE)
-i INFORMATION ------------------------ (THIS CANNOT HARM YOUR SCOPE)
-r REGENERATE PRIVATE KEY--------- (THIS GENERATE THE PRIVATE KEY (Priv Prem) needed before activation)
-u UNINSTALL THE OPTIONS--------- (THIS Uninstalls all options and bundles) so if you are on 1.3.2.2 with installed patched options, you use this option to uninstall them
--reboot -------------------------------(Reboots the scope without having to press the OFF button)

Note the version of the scope
Note if the options are FOREVER or -
if you are on 1.3.2.2 and it says FOREVER because you used the patched version  do this now
if you are on the patched version

TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -u 10.1.1.666Press ENTER
Make sure to restart your scope after this
Restart now happens Automatically


NOW LET'S PULL UP THE SCOPE INFORMATION
TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -i 10.1.1.666Press ENTER

If you now have
- All Options Uninstalled
(if you don't restart your scope )

WE ARE NOW READY TO GENERATE THE PRIVATE KEY.... 
(Ensure you do not lose network or power connection at this stage)

TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -r 10.1.1.666Press ENTER

EXPECT THIS...

- the information table will appear
- A progress bar will appear that says "READING CFRAM"  ... Let it get to 100%
- Then "APPLYING NEW CFRAM"  Let it get to 100%
(if it seems to stall for longer than 1 min, it means you clicked on the screen,   RIGHT CLICK to un pause, then leave it alone)

- Then you will see multiple lines of ACTIVATING
- at the end of it you'll get an information window.   The options will still NOT BE ACTIVATED (that's normal)

-------------------------EDIT : THIS STEP IS OBSOLETE-----------------------------------------------
NOW WE RUN THE SCRIPT
TYPE
python rigol_kg2.py 10.1.1.666
Press ENTER
------------------------------------------------------------------------------------------------------------
After this you will expect all options to be activated (They won't be), That's also normal

UPDATE :
- The scope will reboot on it's own if needed
- After REGENERATE the scope will AUTOMATICALLY go into activation, which is this command

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -a 10.1.1.666BUT YOU WON'T NEED TO ENTER THIS
The scope will then restart again on it's own.

-------------------------EDIT : THIS STEP IS OBSOLETE-----------------------------------------------
Now REINSTALL 1.3.2.2  even though the current version is 1.3.2.2  DO IT AGAIN,  put the USB in the scope with that firmware version on it and run Firmware upgrade again.
(Sounds stupid.. Just do it)

- Then follow the steps again
Get the python INFORMATION up again
NO NEED TO REGENERATE THE KEY THIS TIME
Then just run the script again
TYPE
python rigol_kg2.py 10.1.1.666
Press ENTER
-------------------------------------------------------------------------------------------------------------
THIS TIME YOU WILL BE ACTIVATED

BUT WAIT , YOU'RE NOT DONE JUST YET

- Now erase the USB stick and load 1.3.3.0 onto it

do the Pre Boot Menu UPGRADE FIRMWARE to 1.3.3.0
or you can do this straight from the operating system

NOW YOU WILL NOTICE A FEW THINGS

YOU WILL NOW BE CORRECTLY LICENSED

1. You're now on 1.3.3.0
2. ALL YOUR OPTIONS HAVE SURVIVED A FIRMWARE UPGRADE
3. You're now good to go

REMEMBER THOUGH

1. Do a self check (3 tests)
2. Do a self calibration
3. RUN YOUR BACKUPS AGAIN (Always remember to backup)

NOW YOU'RE ALL DONE , that's it


Lastly, if you have any further concerns, Let me know and i'll test it and post the results.
My goal here is to get everyone comfortable with Dr Mefisto's script, and to upgrade their scopes confidently.



EDIT : New pdf uploaded to include the step that shows you how to install the modules.
EDIT : This Method also supports Activation of  MSO5000, MSO7000, DSO7000, MSO8000  up to their Max. Respective settings.

[BTO]

UPDATE : The Step by Step Instructional PDF is now available (it's detailed)

Also if possible (Because i'm interested to know) could you please leave comments if this worked for you or if it didn't , i think this will start working for everyone.

[Sergey_21]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

Definitely.....

DO THIS FIRST

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
THEN THIS..

Code: [Select]

python d:/rigol_kg2.py -u 192.168.1.37RESTART YOUR SCOPE.

THEN THIS...
DELETE THE PRIV PREM FILE from it's current location
(it should be on the d Drive where you put your python script
then

Code: [Select]

python d:/rigol_kg2.py -r 192.168.1.37RESTART YOUR SCOPE.

then..

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37RESTART YOUR SCOPE

Do you now have all options unlocked "FOREVER" ?
You might, but i don't think so..
IF NOT
DO THIS

 - Put the 1.3.2.2  Firmware GEL File on the USB Stick and even though you are already on 1.3.2.2 ...... DO THE UPGRADE AGAIN
- Go into the PRE BOOT menu by pressing Power button then repeatedly the SINGLE button and Select  FIRMWARE UPGRADE
(Whether you select Defaults, is completely up to you,  some people feel more comfortable doing this... Your call)

After the upgrade

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
then..  You don't need to do -r anymore, Just jump straight into

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37
AND VOILA... 
RESTART YOUR SCOPE

THEN YOU NEED TO UPGRADE TO 1.3.3.0
Grab the GEL file for 1.3.3.0  and you can now do this from the PRE Boot Menu or from the scope in Local Upgrade, it's up to you.

then Restart your scope
Check if it's all good,  IF IT IS...

GET THE 1.3.3.0 BACKUP FILES AND DO YOUR BACKUPS
Do a Self Check
Do Self Cal
and there you go

If you need help, i'm still up, Let me know

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

NOTE TO EVERYONE RE THE UPGRADE PATH

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
Notice the d:/

LET'S TRY TO AVOID USING USB STICKS WHEN DOING THE UPGRADE

WARNING : if the USB Stick fails (as they tend to do ) and it happens during the write process of

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37YOU.... WILL...... BRICK YOUR SCOPE

I only advised you to go ahead with it because you already had the python path installed and i didn't want to mess with it (to keep things simple)
but in the future, i do not advise that you keep your python scripts on a USB, I WOULD ADVISE

1. Open your shell   Probably go for Powershell first
2. Whatever directory location it starts with..   
3. Copy your script to that location  (IT'S MUCH EASIER THAT WAY)

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

Also, Re The Assertion Error, 
if it fails to do it again

TAKE YOUR SCRIPT OFF D DRIVE AND PUT IT IN YOUR C DRIVE AT THE LOCATION THAT THE COMMAND SHELL OPENS IN
Usually it will be
C:\Users\User
and retry all the steps

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

So.. How did you go ?

[Sergey_21]

So:
1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;
2) the PRIV PREM file could not be deleted, because there is nothing to delete (there is no file);
3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;
4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;
5) drive "D" is a local drive;
6) moving the file to C:\Users\User did not bring any results;

[BTO]

So:
1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;
2) the PRIV.PEM file could not be deleted, because there is nothing to delete (there is no file);
3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;
4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;
5) drive "D" is a local drive;
6) moving the file to C:\Users\User did not bring any results;

ok

LET'S DO THIS STEP BY STEP

1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options.

2) the PRIV PREM file could not be deleted, because there is nothing to delete (there is no file);

EXCELLENT, So in the location where you have the rigol_kg2.py script there is no PRIV.PEM file.......GREAT !!!

3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;

OK, SO THIS IS WHERE YOU ARE STUCK

Before you can run

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37and expect it to work, The PRIV.PEM file with the key needs to be generated.  Your attempts are failing because that file is not there

WATCH....
After -r  To REGENERATE the key
You do this (To Run the Script)

Code: [Select]

python d:/rigol_kg2.py -u 192.168.1.37IT FAILS - Because there is no PRIV.PEM File to read from (The Script requires the PRIV.PEM File)

then..

4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;

EXCELLENT - But this will still lead you to a point where NO PRIV.PEM file is generated thus resulting in a fail to upgrade  (DON'T WORRY, I'LL GET YOU THERE)  Just follow me on this . Don't stress

5) drive "D" is a local drive;

WHY IS D DRIVE THE LOCAL DRIVE ?
I have installed and repaired computers for 35 years or more, I have NEVER seen a Primary Hard drive with Operating system on it (Assuming no Dual Boot configuration) that did not call
the Main Hard drive C:\
Ever since computers started,   A and B Are for floppy drives, C is the first primary Drive, D was used for Optical drives. Now  OF COURSE we can re assign them, But
C IS ALWAYS THE PRIMARY DRIVE
the point being (For many reasons)  DO NOT USE OTHER VOLUMES AND DRIVES WHEN DOING THIS, Use the Primary C Hard drive

6) moving the file to C:\Users\User did not bring any results;

OK, I WANT YOU TO DO THIS

1. Go in your computer to windows Explorer and select  THIS PC and give me a screenshot of the window

2. Open Powershell and give me a screenshot of Powershell (Close enough so i can see the directory in use)

3. Give me a screenshot of the location where you have the rigol_kg2.py script

do that ...

[Sergey_21]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

After the last attempt, the file priv.pem appeared, but the result remained the same.

[BTO]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

Good, Well done

so your primary drive is C and the D Drive is a secondary drive.
so LET'S USE THE  C Drive

You've obviously copied the script to the C:\User\Admin Location   
that's good

Now

to check you have communication with the scope

Code: [Select]

python rigol_kg2.py -i 192.168.1.37
followed by

REGENERATE THE PRIV.PEM file

Code: [Select]

python rigol_kg2.py -r 192.168.1.37
CONFIRM THAT YOU NOW HAVE AN ADDITIONAL FILE IN THE C:\Users\Admin   folder  called priv.pem
IF YOU DO

then..

Code: [Select]

python rigol_kg2.py 192.168.1.37
RESTART THE SCOPE
at this point it's normal to not have it activated.... no problem

then
Relaod the 1.3.2.2 GEL FILE and do the FIRMWARE UPGARDE process via PRE BOOT menu

After that's done

again

Code: [Select]

python rigol_kg2.py -i 192.168.1.37
then RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 192.168.1.37
and now you should be activated with all options unlocked

then
Update to 1.3.3.0

LET ME KNOW IF THAT WORKS

You're almost there, once that priv.pem file generates , it's gonna work

[BTO]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

After the last attempt, the file priv.pem appeared, but the result remained the same.

sorry didn't see that last photo

NO.. THIS IS OK

Now you just need to get that 1.3.2.2 GEL file
wipe the USB, 
put the GEL file in the root of the USB
and run it again VIA Pre Boot menu

after that restart your scope

run the INFORMATION  -i  command

then run the script

Code: [Select]

python rigol_kg2.py 192.168.1.37
and it'll be activated
then.. Give me the good news

[Sergey_21]

I did everything according to your advice, but the options remained unactivated.

[BTO]

I did everything according to your advice, but the options remained unactivated.

ok and
- After you did the upgrade of 1.3.2.2  FOR THE 2ND TIME
1. Did you make sure it was the correct GEL file

2. When you ran the Script,  did you get 2 progress Bars ? 
or was it just the READING CFRAM

also did you get that error from before again ?

[BTO]

hi mate, how are you going with it , if you need me to do a zoom with you , let me know, Glad to help.
You're really close we just need to figure out what's going on. I'm happy to do a 1 on 1 with you if you like.

EDIT :
I'm free this evening, if you want to jump on

[Sergey_21]

1. Did you make sure it was the correct GEL file

I used the file from the folder "Step 2. GEL File - Scope Firmware - 00.01.03.02.02"

2. When you ran the Script,  did you get 2 progress Bars ?

No, the script, as before, did not work to completion, I only had 1 progress bar and an error after that, but the PRIV.PEM file appeared


Probably the problem is that the script reads memory (this is done without errors) and tries to do something with it,
then an error occurs and the data that the script was supposed to generate/rewrite is not generated.

[BTO]

1. Did you make sure it was the correct GEL file

I used the file from the folder "Step 2. GEL File - Scope Firmware - 00.01.03.02.02"
(Attachment Link)

2. When you ran the Script,  did you get 2 progress Bars ?

No, the script, as before, did not work to completion, I only had 1 progress bar and an error after that, but the PRIV.PEM file appeared
[ Attachment Invalid Or Does Not Exist ]

Probably the problem is that the script reads memory (this is done without errors) and tries to do something with it,
then an error occurs and the data that the script was supposed to generate/rewrite is not generated.

Possibly...
TRY THIS

1. Delete the old script and download another one from the link i supplied in this topic
2. it's good that you used the 1.3.2.2 from the link in this topic

NOW... Just try this, ok

- Download 1.3.3.0  and Upgrade to it (don't worry about the options) Just do an upgrade.

-Then.. Go to PreBoot Menu and hist Restore Defaults

- Then.. Get that 1.3.2.2 and via Pre Boot Menu downgrade the scope to 1.3.2.2

- Then repeat the process
it's important to remember you need to do this TWICE

so....  After your back down on 1.3.2.2

put the script in the location of the command shell
run the -i command

run the -r command

then run the script without the switch

THEN.. (this is now 2nd Time Round)
Power down the scope

Load 1.3.2.2 into it again

Run the -i command

Then just run the script

and then you should be activated

I WOULD ALSO BE CHECKING AND DISABLING ANY ANTIVIRUS OR FIREWALL THAT MAY.. POSSIBLY BE MESSING WITH THIS

so try the upgrade then the downgrade and do it over again.
We are really close mate, we are almost there,

the script is supposed to read the Pri.pem file,  it's as simple as that .
so so far you have not done any damage to your scope, don't worry about that.
it's just about getting those 2 to talk to each other
Let me know how that goes

[Sergey_21]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

[BTO]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

No that's not correct. if anything the script supports Multiple scopes, my suspicion is that it even supports the MSO7000 and possibly the 8000
as the Option Bundle JITTER is there which is not available in the 5000 and 7000

Simply put
The Script Generates the Priv.pem
then uses that file to right to the CFRAM
but before doing so it searches for AVAILABLE OPTIONS
as well as INSTALLED Options
and then the one's that are not installed,.... it installs


it supports all MSO5000 Models,  it has nothing to do with that .  if it didn't support it it would even run and it would spit out an error.
I've seen that post as well

REMEMBER THIS...
A Large part of what i'm doing here is.. TO DISPELL THE MYTHS Because this is a good upgrade, and it does work.
but since the topic started , people have jumped to a lot of conclusions and we need to sort out a few of these incorrect assumptions

like one of them is.. the need to hit that Restore Defaults option
which then morphed to....  RESTORE DEFAULTS takes your scope off the current firmware and back to the firmware version that you bought it with.

As a result of all this a lot of people are scared and freaking out.
I have upgraded my scope over 30 times, i've tried to brick it (with the exception of pulling the power or network cable) i wasn't about to.

I tried to fault the script,  i couldn't,  I've had a look through it, it's a pretty straight forward script.

Mate, do what i requested before and let me know how it goes... Buti  YOUR SCOPE IS COMPATIBLE TO THE SCRIPT.  that's not the issue.

[Sergey_21]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

Thanks for trying to help.

[BTO]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

I Disagree,
Now we can always revert back to the patched method, There's no problem there.
and it's your scope so it is totally up to you .
But, we are really close to a permanent solution.

1. This is proving unusually difficult, which tells me we just need to find the issue and we'll be good
2. The first problem was that you had the file on a different directory
Sinc then we've made progress

3. Now the issue is that the script is not speaking to the Priv.Prem

Do you want to jump on a 1 on 1 support with you this evening ?
i'm confident we can work it out

Also @DrMeFistO
Mate do you have any ideas...

- He's trying to licence the scope
- He has the script in the same directory that Poweshell opens in
- He is able to regenerate Priv.Prem
- when whe runs the srcript it only get to the READING CFRAM but doesn't write to it

the is currently on 1.3.2.2 (the GEL is a known working file)
the script is a known working file

I'm thinking some software is blocking it or firewall, i see nothing in the script that would not allow his model MSO5000 to not write to FRAM.

we have also tried 2 times
running regenerate -r
running script
then running GEL 1.3.2.2 AGAIN
then ran the script again
should have licenced at this point, but didn't

for some reason the script doesn't seem to proceed to the writing of the CFRAM
in the code, i think he gets to line 127  but doesn't proceed past line 141

ANY IDEAS ...

[BTO]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

Thanks for trying to help.

Try this for me
Do a SELF CAL

and Uninstall Python for me
then REINSTALL PYTHON  But make sure to do the following

STEP 1 . on the first screen
- SELECT..... CUSTOMIZE INSTALLATION    Not Install Now

- on the same screen CHECK THE BOXES 
- Use Admin Priviledges When Install Py.exe
- Add Python.exe to PATH

STEP 2 - Advanced Options
- Check the top 5 boxes  from Install Python for all users to Precompile Standard Library

STEP 3 -  Install it

STEP 4 - Open command shell  and enter the  -i command and see if it communicates with your scope, if it does
try the process again

[BTO]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

What Model do you have anyway ?

[Sergey_21]

What Model do you have anyway ?

MSO5074

[Swap_File]

Directions and script worked perfectly on my MSO5074.  Thanks.

It might be useful to add a reminder to use a USB stick at least 2GB in size when doing the backups.  I have a little old 64MB stick I use for updates, and that was not big enough.

[BTO]

What Model do you have anyway ?

MSO5074

Oh well then.. it's 100% compatible with your scope as i also have a MSO5074.

Mate, my gut is saying things like....

something blocking the script from reading the Priv.pem file

This could include things like this

- Folder Permissions
THIS TOOL CAN HELP YOU
https://www.majorgeeks.com/mg/getmirror/take_full_ownership_of_files_folders_registry_hack,1.html
After you extract the file you'll have 2 registry files. click on the one that says
"Add Take Ownership to Context menu" and run it, Accept both options

then go over to the folder that the script is in and right click ON THE FOLDER and select TAKE OWNERSHIP.
You'll see a command shell open and do some stuff, don't worry about it, it's just setting permissions globally so you own the folder.

- You're not using an account that is Admin
(i imagine you likely are Admin but it's good to check)

- Your PC MIGHT be having a problem
this can be weeded out by opening cmd.exe and running

Code: [Select]

sfc/scannowThis takes a while

- Perhaps Python is having trouble with the folder or you selected INSTALL when you installed it instead of CUSTOMIZE INSTALLATION.

- it's unlikely the folder itself is having issues as the script was able to write to the folder and that same folder has both the script
and Priv.pem, the problem is about or has something to do with python reading the Priv.pem file

this isn't a scope issue, this is a computer software issue, permissions or firewall related

Run the Takeownership registry patch on the file and try it again.

[BTO]

Directions and script worked perfectly on my MSO5074.  Thanks.

It might be useful to add a reminder to use a USB stick at least 2GB in size when doing the backups.  I have a little old 64MB stick I use for updates, and that was not big enough.

1 GREAT TO HEAR - I'm curious  which directions did you use
- The one's in this topic
- The PDF


2. Now.. A quick check
YOU LICENCED SUCCESSFULLY -  CHECK

Did you
- Upgrade after the licensing to 1.3.3.0   (you can do this from the operating system or from PRE BOOT menu)

- DO YOUR BACKUPS (by going into STEP 1. of the 1.3.3.0 file that i attached)     Do not forget to do your backups.
  in all the excitement of activation you can be forgiven for forgetting.. but don't !

- DO SELF CHECK - 3 Tests

- DO SELF CAL

Lastly Re the USB STICK.... Interesting.
I was telling people not to exceed 16GB as it's what i used and it is a reasonable size to use.  But You reckon 2GB min huh,  OK
I'll add that step.

WELL DONE CONGRATULATIONS

[Sergey_21]

I think firewall, access, etc. things have nothing to do with it. The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.
I have unlocked some debugging information, but it may only be useful to the developer of this script.
That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created, access is not needed here.

[BTO]

I think firewall, access, etc. things have nothing to do with it. The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.
I have unlocked some debugging information, but it may only be useful to the developer of this script.
That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created, access is not needed here.

HOLD ON.. !!
1. So are you still getting the Assertion Error ?

2. Why are you using the regenerate command , My understanding is, you already generated the key
Now, you need to run the sript at

Code: [Select]

python rigo_kg2.py [Your I.P. Address here]there is no switch here.

if you keep running the script as

Code: [Select]

python rigo_kg2.py -r [Your I.P. Address here]it's never going to activate, You need to delete the -r

so what's the last thing that you tried , Did you try the Take Ownership thing that i suggested ?

Also, do you want me to jump on zoom with you or something, i feel we are really close to getting it.

[BTO]

I think firewall, access, etc. things have nothing to do with it. The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.
I have unlocked some debugging information, but it may only be useful to the developer of this script.
That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created, access is not needed here.

I think firewall, access, etc. things have nothing to do with it.

But.. Given the situation you are in, WE NEED TO TEST IT AND PROVE IT
Something is stopping it from reading the Priv.pem file,   Now if you were running the command each time with the -r in there.
THAT WOULD BE THE CAUSE.

The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.

Correct , it does read the FRAM and it does then write to it,  but re "it doesn't receive what it expects" , The script asks the scope to provide
it the information, Now there are commands like "len" for example where the Hex key needs to be the exact length that is expected (this is true)
but.. THAT WOULD MEAN THAT YOUR SCOPE IS DIFFERENT TO ALL OF OUR SCOPES in some foundational way,  I can't see that happening
if you have an MSO5074

That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created,

but... By running the regenerate command, You did create it .

and after that, You run the script (without switches)

DO THIS...
RUN THE SCRIPT without switches, and shoot me a screenshot if you could
or........ZOOM

[RemB]

Hi! I have an MSO5074 and had installed options (MSO5000-BND). I did everything according to the instructions and now I have all installed licenses. The method is working. I suggest adding a description of installing modules for python. Thanks!

[BTO]

Hi! I have an MSO5074 and had installed options (MSO5000-BND). I did everything according to the instructions and now I have all installed licenses. The method is working. I suggest adding a description of installing modules for python. Thanks!

THAT'S AWESOME.. GOOD WORK

Now,
1. Don't forget to upgrade to 1.3.3.0

2. DON'T FORGET TO DO YOUR BACKUPS (By going to STEP1 ) of the 1.3.3.0 download and running the 2 backups

3. Then Do your SELF TEST

4. Then do your SELF CAL

then you're good to go.


RE THE MODULES....
Ahhh Yes, You are correct, i meant to do that, My wife interrupted me to give me dinner and when i returned it slipped my mind.
it is in the video that i have not finished editing, but i will edit the PDF

[BTO]

ModuleNotFoundError

Hi Guys, a bit of an oversight on my part but keep this in mind

1. After you install Python

2. The first thing you want to do is INSTALL THE REQUIRED MODULES, if you don't have them you will get an error like   

Code: [Select]

ModuleNotFoundErrorand it will have something on the end... Like this

Code: [Select]

ModuleNotFoundError: No Module named 'requests'This means that you do not have the "REQUESTS" Module installed,   to install the module you do this...

pip intstall requests

Press ENTER
I personally had to install the following modules but if you get any others , just go ahead and install them, Just alter the name between the parenthesis.

pip intstall tqdm

pip intstall tabulate

pip intstall xxtea

pip intstall ecdsa

When you have all options installed and you run

python rigol_kg2.py -i 00.00.00.00

[/color]
where 00.00.00.00  is your I.P. Address, You will a table of installed options

[BTO]

I think firewall, access, etc. things have nothing to do with it. The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.
I have unlocked some debugging information, but it may only be useful to the developer of this script.
That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created, access is not needed here.

Hey Sergey, Read my recent post on MODULE ERRORS, Perhaps this is as simple as you didn't install all the modules.

The entire list of modules is

Code: [Select]

pip intstall argparse

Code: [Select]

pip intstall base64

Code: [Select]

pip intstall binascii

Code: [Select]

pip intstall os.path

Code: [Select]

pip intstall re

Code: [Select]

pip intstall socket

Code: [Select]

pip intstall struct

Code: [Select]

pip intstall time

Code: [Select]

pip intstall zlib

Code: [Select]

pip intstall requests

Code: [Select]

pip intstall tqdm

Code: [Select]

pip intstall hashlib

Code: [Select]

pip intstall tabulate

Code: [Select]

pip intstall xxtea

Code: [Select]

pip intstall struct import pack

Code: [Select]

pip intstall ecdsa
YOU CAN RUN THIS COMMAND TO SEE THE INSTALLED MODULES

Code: [Select]

pip list

[BTO]

Hi! I have an MSO5074 and had installed options (MSO5000-BND). I did everything according to the instructions and now I have all installed licenses. The method is working. I suggest adding a description of installing modules for python. Thanks!

PDF has been updated, thanks for letting me know that,  That was KINDA An important step huh ? 

[Michal Mytnik]

Hi,

for me all have worked very well. Job well done with PDF @BTO
The only small misalignment I have had was at point 16, where it says that script without parameters will run same way, meaning two progress bar should appear. In my case I have just got info that CFRAM is OK and then got the activation list screen, no progress bars. I have just went down the PDF file and at the end all worked super good.

But it's true that I have had to import some libraries via pip

All in all it works, and excelent work with providing all the details @BTO

[BTO]

Hi,

for me all have worked very well. Job well done with PDF @BTO
The only small misalignment I have had was at point 16, where it says that script without parameters will run same way, meaning two progress bar should appear. In my case I have just got info that CFRAM is OK and then got the activation list screen, no progress bars. I have just went down the PDF file and at the end all worked super good.

But it's true that I have had to import some libraries via pip

All in all it works, and excelent work with providing all the details @BTO

for me all have worked very well. Job well done with PDF @BTO

Thankyou and Excellent work WELL DONE

The only small misalignment I have had was at point 16, where it says that script without parameters will run same way, meaning two progress bar should appear. In my case I have just got info that CFRAM is OK and then got the activation list screen, no progress bars. I have just went down the PDF file and at the end all worked super good.

Hmmm???  well what i would say to that is...
1. At step 16 THERE ARE PARAMETERS, Step 16 is where you REGENERATE THE PRIVATE KEY and use the -r switch .
This is where the progress bars should happen

2. STEP 17 is where you take away the switch (aka Parameters) and you run the script

3. I would say .. if you were at Step 16 and the progress bars didn't start,  it means you already had the Priv.pem file generated
and as such it didn't generate it anymore.
then when you got to Step 17, without the switch, it just worked.
Well , it wouldn't have worked if you didn't have the priv.pem file in place so you must have had it there and attempted to regenerated again.

but all in all Good work.

Now.. .GO AND READ POST #31  (So i don't have to keep retyping it)
and follow those steps and then you're all good

[BTO]

I think firewall, access, etc. things have nothing to do with it. The script reads the contents of memory and tries to change it. But the script cannot do this, since it does not receive what it expects.
I have unlocked some debugging information, but it may only be useful to the developer of this script.
That is, the stage of transferring the changed information (key) to the oscilloscope does not occur, since a new key has not been created, access is not needed here.

Surgey, Just so i know, What's the deal with you mate ?
- I'm happy to get on a zoom chat with you and get you over the line, But
- Are you still proceeding with this ?
- have you given up
- have you reverted to just patching the scope,

Where are you at ?

[Sergey_21]

Surgey, Just so i know, What's the deal with you mate ?
- I'm happy to get on a zoom chat with you and get you over the line, But
- Are you still proceeding with this ?
- have you given up
- have you reverted to just patching the scope,

Hello!
I tried it, but the result is the same.


As I said earlier, or rather wrote, my script gives an error (and I tried to continue as you advised, but it didn’t give anything) and until I can sort this out, I don’t think anything will work out.
I think it’s worth writing to the script developer or to the main forum thread.

[BTO]

Surgey, Just so i know, What's the deal with you mate ?
- I'm happy to get on a zoom chat with you and get you over the line, But
- Are you still proceeding with this ?
- have you given up
- have you reverted to just patching the scope,

Hello!
I tried it, but the result is the same.
(Attachment Link)

As I said earlier, or rather wrote, my script gives an error (and I tried to continue as you advised, but it didn’t give anything) and until I can sort this out, I don’t think anything will work out.
I think it’s worth writing to the script developer or to the main forum thread.

ATTENTION SERGEY
THIS POST IS DUPLICATED HERE FROM THE MAIN THREAD FOR THE BENEFIT OF THOSE THAT DON'T SEE THE MAIN THREAD

Mate, You may be in some luck here.
Recently i had a member who had your exact same problem

- After following the standard procedure and then re applying the update and then running the script, it still didn't work.
- We did a bit of troubleshooting and we got there and activated and licensed

CREDIT GOES TO SEPPLETRONICS

I have attached  A NEW PYTHON SCRIPT

I would like you to do the following (No need for screenshots, Just do this)

STEP 1- Download the script called

Code: [Select]

rigol_kg2_3_000 in the attachment

Ensure your scope is on 1.3.2.2

STEP 1 - Delete your priv.pem key from it's location
STEP 2 - Delete the old script from it's location
STEP 3 - Open your command prompt or Powershell and copy the NEW SCRIPT into the location of the directory that the shell opens in
             (I'm assuming here that you still have python correctly installed with all the modules)

STEP 4 - Run the -i command like this

Code: [Select]

python rigol_kg2_3_000 -i 10.1.1.666   replace 10.1.1.666 for your I.P. Address

STEP 5 - Run the -r command

Code: [Select]

python rigol_kg2_3_000 -r 10.1.1.666

STEP 6 - CONFIRM THAT YOU DON'T HAVE ANY ERRORS
             CONFIRM THAT THE priv.pem FILE IS IN THE SAME LOCATION AS THE SCRIPT
             CONFIRM THAT YOU GOT 2 PROGRESS BARS INSTEAD OF ONE
STEP 7 - Run the script without the switch

Code: [Select]

python rigol_kg2_3_000 10.1.1.666
             CONFIRM THAT YOU GOT 2 PROGRESS BARS INSTEAD OF ONE
When this completes, it will NOT have activated Options

STEP 8 - SHUTDOWN YOUR SCOPE

STEP 9 - Put the 1.3.2.2 GEL File on USB and as before , go to PRE BOOT and select Upgrade Firmware , to load over 1.3.2.2 again
Take the USB Stick out and Restart your Scope

STEP 10 -  Run the -i command like this

Code: [Select]

python rigol_kg2_3_000 -i 10.1.1.666 

STEP 11 - Run the script without the switch

Code: [Select]

python rigol_kg2_3_000 10.1.1.666

NOW ..... PLEASE TELL ME THAT YOU ARE SUCCESSFULLY ACTIVATED AND LICENCED WITH "FOREVER"


Give that a go.

If it works.... Do not forget

Step 12 - Upgrade to 1.3.3.0
Step 13 - DO YOUR BACKUP from the 1.3.3.0 Backup files
then..
Step 14- Do Self Check - 3 Tests
Step 15 - Do Self Cal

Mate if this works,  Also do me a favour, can you please send me a list of WHICH OPTIONS YOU HAD INSTALLED AT THE TIME OF PURCHASE.

[BTO]

Directions and script worked perfectly on my MSO5074.  Thanks.

It might be useful to add a reminder to use a USB stick at least 2GB in size when doing the backups.  I have a little old 64MB stick I use for updates, and that was not big enough.

Hi mate,
First, Hope your scope is going well for you .

Secondly, Want to ask you a favour about your scope, (i'm gathering some information for the sake of helping others)

Now.. You mentioned your scope was a MSO5074
However... DID YOU BUY IT STANDARD or  DID YOU HAVE OTHER OPTIONS INSTALLED FROM THE TIME OF PURCHASE ?

FYI - This is a new script file called rigol_kg2_3_00.py 
For the record, this file will not apply to you , you just keep the one that you activated with if you need to do anything.
But the original file has been modified and other users have successfully activated that couldn't before, so now i need to gather
some information to see which models are effected by this change and to find the common factor between them and this will
help me understand if i need to modify the script further.

thanks mate

[BTO]

Hi,

for me all have worked very well. Job well done with PDF @BTO
The only small misalignment I have had was at point 16, where it says that script without parameters will run same way, meaning two progress bar should appear. In my case I have just got info that CFRAM is OK and then got the activation list screen, no progress bars. I have just went down the PDF file and at the end all worked super good.

But it's true that I have had to import some libraries via pip

All in all it works, and excelent work with providing all the details @BTO

Hi Michal, Hope your scope is going well.
Can i ask something  PRIOR TO FULL ACTIVATION
What Model was your scope ?
Did it have any installed options from the factory ?

I'm making a record of who activated and the specifics of the meters, i'm trying to find a correlation between a few things
in the script as i feel i can edit the script to activate more scopes

[dxl]

Thanks BTO,

that worked like a charm. I had an old Firmware version several years old on my MSO5072, i disassembled the scope binary at that time and patched the option code to get all the options. Now i thought it's time to update the Firmware. All what's required was:

- flash DS5000Update.GEL via USB (from MSO5000(ARM)Update_v00.01.03.03.00.zip)
- python rigol_kg2_3_000.py -r 192.168.0.158
- powercycle DSO
- python rigol_kg2_3_000.py 192.168.0.158

voila, all options there - awesome, thanks!

[BTO]

Thanks BTO,

that worked like a charm. I had an old Firmware version several years old on my MSO5072, i disassembled the scope binary at that time and patched the option code to get all the options. Now i thought it's time to update the Firmware. All what's required was:

- flash DS5000Update.GEL via USB (from MSO5000(ARM)Update_v00.01.03.03.00.zip)
- python rigol_kg2_3_000.py -r 192.168.0.158
- powercycle DSO
- python rigol_kg2_3_000.py 192.168.0.158

voila, all options there - awesome, thanks!

THAT'S AWESOME.. Well Done
You're Welcome

it is interesting however that , You have an MSO5074 and yet you used the

Code: [Select]

python rigol_kg2_3_000.py script
and it worked. Generally this is used only if you have a MS5100 series or.. in rare cases when you have a MSO5074 with MSO5000BND Options.

I haven't worked out why yet, but when they load options into a MSO5074 it seems to somehow recognize it as an MSO5100.

Oh Well.. NOTED,
In any case, You're all good, so well done

[SuperD]

Hi all, I have been reading and gathering all the details. First, thank you for all of the instructions and hard work!

Now, I was a lucky one to get the Rigol Bundle free when I got my 5104. I found the patch well after installing that. I used the scope & patch with everything unlocked for a couple of years and was on 1.3.0.3. I updated the scope to 1.3.3.0 today and lost the bandwidth, back at 100 mhz (expected).

I downgraded to 1.3.2.2 to hopefully to lose all that (per instructions "If your scope is on Version 1.3.2.2 and has upgraded software on it you will need to uninstall those options") but nothing uninstalled. I still have the bundle options saying "Forever", and still on 100 mhz.

My ask is, how important is it to get everything removed? Is the concern only to remove the patch? If not, and all options need to be removed, how would I uninstall licensed options? ( I did GTS quickly and could not find a way to uninstall options)

I know the "Patch" is probably gone as the options I see, I would expect to remain. Just wondering how important it is to make those disappear. I have my back ups and holding off for now. I can always go back to the patch method, but I would like to get this perminent if possible, like the other options.

Thanks for any help you can give.

[BTO]

Hi all, I have been reading and gathering all the details. First, thank you for all of the instructions and hard work!

Now, I was a lucky one to get the Rigol Bundle free when I got my 5104. I found the patch well after installing that. I used the scope & patch with everything unlocked for a couple of years and was on 1.3.0.3. I updated the scope to 1.3.3.0 today and lost the bandwidth, back at 100 mhz (expected).

I downgraded to 1.3.2.2 to hopefully to lose all that (per instructions "If your scope is on Version 1.3.2.2 and has upgraded software on it you will need to uninstall those options") but nothing uninstalled. I still have the bundle options saying "Forever", and still on 100 mhz.

My ask is, how important is it to get everything removed? Is the concern only to remove the patch? If not, and all options need to be removed, how would I uninstall licensed options? ( I did GTS quickly and could not find a way to uninstall options)

I know the "Patch" is probably gone as the options I see, I would expect to remain. Just wondering how important it is to make those disappear. I have my back ups and holding off for now. I can always go back to the patch method, but I would like to get this perminent if possible, like the other options.

Thanks for any help you can give.

First, thank you for all of the instructions and hard work!

You're Welcome

I used the scope & patch with everything unlocked for a couple of years and was on 1.3.0.3. I updated the scope to 1.3.3.0 today and lost the bandwidth, back at 100 mhz

Yep THAT'S NOT A PROBLEM

I downgraded to 1.3.2.2 to hopefully to lose all that (per instructions "If your scope is on Version 1.3.2.2 and has upgraded software on it you will need to uninstall those options") but nothing uninstalled. I still have the bundle options saying "Forever", and still on 100 mhz.

Not a problem, You just go into Python and use the -u command to uninstall the options

My ask is, how important is it to get everything removed?

Not Highly Important, We are just following a protocol that works
You are free to try the python licensing method as is if you like, by all means,  it can't hurt,
worst case, we start over and uninstall it

Is the concern only to remove the patch?

yes, the main concern is to remove the patch

If not, and all options need to be removed, how would I uninstall licensed options?
OK, in the same way that would run the information switch with -i
Example

Code: [Select]

python rigol_kg2_3_000.py -i 192.168.0.158TO UNINSTALL YOU RUN

Code: [Select]

python rigol_kg2_3_000.py -u 192.168.0.158

I know the "Patch" is probably gone

it likely is, it's likely the installed options as you bought it are still there
i would just try upgrading without uninstalling personally

Use the rigol_kg2_3_000.py  script because you have an MSO5100 series
other than that

just follow

Code: [Select]

python rigol_kg2_3_000.py -i 192.168.0.158

Code: [Select]

python rigol_kg2_3_000.py -r 192.168.0.158

Code: [Select]

python rigol_kg2_3_000.py 192.168.0.158
then load 1.3.2.2 again via pre boot menu

then -i again
then

Code: [Select]

python rigol_kg2_3_000.py 192.168.0.158
with your IP of course
and you should be good.
Let me know how it goes

EDIT : then of course after that update to 1.3.3.0
follow the procedure on the pdf

sorry, had to run out to get the phone

so.. After you active on 1.3.2.2
Upgrade to 1.3.3.0 as per the pdf you can do this via Pre Boot Menu or from the O/S

Lastly before you celebrate

Follow the PDF to do
Backup again
Self Check
Self Cal

then to set your scope up (this is optional)
Visit this link
https://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive/

You have instructions (Video) on how to setup your scope
as well as around 13 videos to teach you how to use every part of your scope in depth.

after that.. ENJOY

Let me know if you activated and let me know if you did so by uninstalling everything first or did you just activate
with bundle options installed ?

[dinosaur_rob]

BTO

Your summary of the diverse posts re the methods made it all so clear.  Great work.  Would these methods work on other Rigol instruments? I have an old Rigol DS1104B.  I understand it may have the same board. It has Firmware 012.01.00.04.01.00.01 HW DB53 build 00.59.  Is this upgradeable to 200mzh by any of the described methods.   I also have a SA - DSA815 TG with Firmware 00.01.19 Boot 00.01.04.  Despite searching I could not see any clear method to get either of these units upgraded.  BTW I wanted to order (pay for) the DS1104B upgrade and was told by Rigol further licences are not available for that model.

I am also having difficulty locating earlier versions of software.  Is there a repository for these?

[SuperD]

We have success! Here is what I saw (for reference). I trusted the process and didn't uninstall the bundle. I did the -i then the -r, then the full command. All the way though, the OEM bundle lasted (just bandwidth was still OEM 100 mhz)

When I did the 1.3.2.2 reload through pre-boot, then booted up the scope after, now all options were uninstalled. Without me doing the -u at all.

Instructions went according to plan otherwise. The scope is now on 1.3.3.0 and fully licensed. Thank you again for the help, all who contributed!

[BTO]

We have success! Here is what I saw (for reference). I trusted the process and didn't uninstall the bundle. I did the -i then the -r, then the full command. All the way though, the OEM bundle lasted (just bandwidth was still OEM 100 mhz)

When I did the 1.3.2.2 reload through pre-boot, then booted up the scope after, now all options were uninstalled. Without me doing the -u at all.

Instructions went according to plan otherwise. The scope is now on 1.3.3.0 and fully licensed. Thank you again for the help, all who contributed!

THERE YOU GO, that's Awesome

Now don't forget to follow those last few steps in my last post in the EDIT section
the are important,  but.. WELL DONE

[BTO]

Dear BTO

I am new to this forum (and a newbie).  I am in awe of the work you do. The world would be a much better place if there were more Dave and BTOs in the world.

Your summary of the diverse posts re the methods made it all so clear.  Great work.  Would these methods work on other Rigol instruments? I have an old Rigol DS1104B.  I understand it may have the same board. It has Firmware 012.01.00.04.01.00.01 HW DB53 build 00.59.  Is this upgradeable to 200mzh by any of the described methods.   I also have a SA - DSA815 TG with Firmware 00.01.19 Boot 00.01.04.  Despite searching I could not see any clear method to get either of these units upgraded.  BTW I wanted to order (pay for) the DS1104B upgrade and was told by Rigol further licences are not available for that model.

I am also having difficulty locating earlier versions of software.  Is there a repository for these?

Cheers dinosaur_rob

Hi mate
firstly

I am new to this forum (and a newbie).

That's ok, no problem

I am in awe of the work you do. The world would be a much better place if there were more Dave and BTOs in the world.

Thanks a a lot i really appreciate that
Dave however is  THE LEGEND, Without Dave none of us are here

i have put in my contribution here , but I THINK A FEW OTHER DESERVE CREDIT

As the title states, DRMEFIST0
this is the guy that created the python script (at least finalized the first version)
there were others at the beginning i don't know all their names
and then finally me and SEPPLETRONICS work out the version _3_00 thing of the script to allow the other models to be activated.
so credit goes to SEPPLETRONICS for that one

As for me (and if you're a beginner) this will be good for you,
1. I'm helping people get off the patch method and activated properly and simplifying the process

2. GO TO THIS LINK
https://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive

THERE IS A VIDEO SERIES THAT WILL SHOW YOU HOW TO USE EVERY FEATURE OF YOUR SCOPE.

now as for this

Your summary of the diverse posts re the methods made it all so clear.  Great work.

THANKS i appreciate that.

 

Would these methods work on other Rigol instruments?

NO, THIS PYTHON SCRIPT IS ONLY SPECIFICALLY FOR MSO5000 scopes

Now, You being a newbie, this is the part where someone would say to you
- See that search bar up the top
- USE IT !!
 

DON'T WORRY , I'LL HELP YOU OUT

but for the sake of continuity of this post let's not get other scopes mixed up into it as it will confuse future people reading this.

I'm going to PM You with some instructions. but for now just to finish this.

I have an old Rigol DS1104B.

WOW... Not that is old
GOOD NEWS THOUGH, i have been monitoring this hardware hacking thing since Rigol DS1052E , then all the way through the
DS2000A and onwards, at the time your scope came out i had an option DS2000A or DS1052E,    I chose the former, Never regretted it.
 But lucky for you i do remember this stuff and there are posts on it.
I'll email you with instructions

I understand it may have the same board.

No, the MSO5000 and the DS1100B have different boards, i'ts not even the same process.

It has Firmware 012.01.00.04.01.00.01 HW DB53 build 00.59.  Is this upgradeable to 200mzh by any of the described methods. 

Not by the methods on this post, BUT IT IS UPGRADEABLE... YES

I also have a SA - DSA815 TG with Firmware 00.01.19 Boot 00.01.04.

hmm Interesting , A Spectrum Analyzer,   I LIke challenges,
Let me look that up for you, Again i'll PM you with this as we don't go into all that on this forum, But again, i will help you so don't worry.

Despite searching I could not see any clear method to get either of these units upgraded.

Don't worry, we'll get at least the scope upgraded

BTW I wanted to order (pay for) the DS1104B upgrade and was told by Rigol further licences are not available for that model.

EXACTLY,   that scope is DISCONTINUED
it's interesting that rigol recommends the MSO5104 as the closest scope,   I'd say this is an upsell.
I would say at this time if someone wanted an entry level cheapy, you're better going for the DHO1074, 12BIT SCOPES.
the specs are basically on par with what the DS1052E Was,  now this recommendation is a 70MHz option,but again.. Upgradeable
to 200MHz

I am also having difficulty locating earlier versions of software.  Is there a repository for these?

I'll PM you and explain everything, Let's do everything with PM from here on in or email

[SuperD]

Thank you again for the guidance and putting it all in one place! I did do the 1.3.3.0 update, all 3 self-tests & the self-cal. As well as the new backups too. Ready for Scope-a-geddon!

[BTO]

Thank you again for the guidance and putting it all in one place! I did do the 1.3.3.0 update, all 3 self-tests & the self-cal. As well as the new backups too. Ready for Scope-a-geddon!

Ohh yeah....
Now before the chalice of power is passed unto you , YOU HAVE 1 MORE TASK
before unleashing SCOPE-A-GEDDON


YOU MUST LISTEN TO THIS

 

and remember

THERE CAN BE ONLY ONE

[strahd_von_zarovich]

Has anyone tried it with MSO8000 series. 

I have MSO8064 with all the options but, upgrading 600MHz to 2Ghz would be wonderful. 

[BTO]

Has anyone tried it with MSO8000 series. 

I have MSO8064 with all the options but, upgrading 600MHz to 2Ghz would be wonderful. 

LOL... Man i love it when this happens
You don't get many (Actually there have been NONE) LOL that own an MSO8000 to put up their hand and say i want this unlocked.

but yeah i'm pretty sure we can most definitely do it.
I think it's best we tee up a time to get on a zoom session so it all goes properly, there's a few changes that need to be made in the script,
but i'm pretty sure i can get you to 2GHz because it's plain to see in the script that the option is there.

Has anyone tried it with MSO8000 series.

well on the MSO8000 post there is only 1 guy, and i reached out to him and he has not responded.

But as i said, this script should be good for
MSO5000
MSO7000
MSO8000

and also, No one has approached me for MSO7000 either, You just don't get a lot of that, it's not popular
But my confidence level on this working is very high, I reckon we give it a go

[tv84]

This method works for all MSO 5000, 7000 and 8000 series. Nonetheless, given how this script works, it's not risk-free because of how the different FRAM areas are addressed.

I advise all to do a FRAM backup before doing it, as a last option to fully restore the scope.

FWIW, all this was tested when the 8000 came out. Here. Months earlier it had been done with the 7000.

[BTO]

This method works for all MSO 5000, 7000 and 8000 series. Nonetheless, given how this script works, it's not risk-free because of how the different FRAM areas are addressed.

I advise all to do a FRAM backup before doing it, as a last option to fully restore the scope.

given how this script works, it's not risk-free because of how the different FRAM areas are addressed.

No mate, Most definitely. I wasn't just going to run the script as is.
Even though it's not risk free, I've done extensive research on the Software Items that are included and they all seem to span across the 3 Models.

I was actually going to reach out to you or DrMefist0 LOL, I suppose it's good timing that you chimed in.. Thanks.

I advise all to do a FRAM backup before doing it, as a last option to fully restore the scope.

No.. by all means , THAT WOULD BE NON NEGOTIABLE.

I would of course go through and change the parts of the script that label the scope or require the name MSO5074 to the model of the MSO8000  that we are targeting

Now.. I did actually look at Line 19

Code: [Select]

FRAM_MD5 = 'aadc292fe4063a7ac392e3c3dde51e84'and was wondering will this still work and if not, How to obtain a checksum that would
as for Line 20

Code: [Select]

FRAM_OFFSETS = [3120, 3204, 3206, 3207]I do understand what these do, however i have not opened and interrogated the scope to the degree where i would understand which values needed to be insert to accommodate the offsets for
MSO7000 and MSO8000

I'm planning over the weekend to go through the script with a fine tooth comb and see what's what.
also.. IF YOU KNOW   things like lines 39 - 42 (as an example) they are commented out which leads me to sort of think that DrMefist0 kept this as an ace up his sleeve to enable
should we require it. Or... it could just be stuff that he tried then didn't work so he commented it out, Not sure to be honest.

I do understand what all the modules do.
I am going to go through the script carefully
and we are DEFINITELY going to do a full backup

Personally i think with a bit of tweaking and a bit of help from you perhaps and DrMefist0 (Since he wrote the thing) we should be able to pull it off.
it definitely shouldn't work as it is, Although i was going to try it that way just to be sure it didn't (What are you thoughts, do you think it'll work as is ?)

Also Line 421

Code: [Select]

    model = model[:-2] + '00'
is going to be interesting as to what the value should be.
so far we've got
2  00  for MSO5000
3 000 for MSO5100
i haven't gone to MSO5200 but i assume 4  0000   and not that it'll be relevant but MSO5300 i assume 5  00000

anyway, i think it's worth a crack, even though the MSO7000 and MSO8000 community are not a big one, why should they miss out ?

ANY THOUGHTS MATE ?

[BTO]

This method works for all MSO 5000, 7000 and 8000 series. Nonetheless, given how this script works, it's not risk-free because of how the different FRAM areas are addressed.

I advise all to do a FRAM backup before doing it, as a last option to fully restore the scope.

FWIW, all this was tested when the 8000 came out. Here. Months earlier it had been done with the 7000.

Thanks for that, I'll check that out VERY CAREFULLY
I would try this on my own scope, however i don't have an MSO7000 or 8000, don't have a need for one.
anyway, thanks for the update, saves me looking for it,
I have gone through all the hacking posts and each page, Hundreds of pages,  but it's easier if i don't have to look for it, thanks mate

[tv84]

If there is no evolution meanwhile, by year's end I'll release the SCPI command that does all the magic of writing to the FRAM.

What started at Xmas 2018 will end then, and afterwards someone will be able to update Mefisto's script making it bullet proof.

Until then the whole community still has time to solve the quest.

No more replies for now...

[dinosaur_rob]

BTO
Images as requested. 
Cheers
dinosaur_rob

[BTO]

If there is no evolution meanwhile, by year's end I'll release the SCPI command that does all the magic of writing to the FRAM.

What started at Xmas 2018 will end then, and afterwards someone will be able to update Mefisto's script making it bullet proof.

Until then the whole community still has time to solve the quest.

No more replies for now...

If there is no evolution meanwhile, by year's end I'll release the SCPI command that does all the magic of writing to the FRAM.

Sounds good, I'll see if i can beat you to the punch.

What started at Xmas 2018 will end then,

AND IT SHALL RESTORE BALANCE TO THE UNIVERSE....... ONCE AND FOR ALL   

Until then the whole community still has time to solve the quest.

...... AND WIN......
THE MEDAL OF HEROES

[BTO]

Thanks for the pictures.

[BTO]

Has anyone tried it with MSO8000 series. 

I have MSO8064 with all the options but, upgrading 600MHz to 2Ghz would be wonderful. 

Hi mate, just touching base,
1. I now realize that you are in fact the guy from the other post, I was hoping you'd see my comment.

2. I just had a really really good look through the Python Script.
hmmm 
I SUSPECT THIS MAY BE ... A LOT EASIER THAN I ORIGINALLY THOUGHT
I also think a certain someone (Who shall remain nameless) is playing games with us  LOL
Not necessarily bad games , but more like....   Let's force the lower life forms to learn something.

However... I also think this conversation needs to take place on this thread
https://www.eevblog.com/forum/testgear/rigol-mso8000-series-hack/
THE MSO8000 HACKING THREAD

So.. Let's jump back onto that shall we
Also, Even though i understand Python to a good degree, i think it may be helpful if you round up some others
that are more experienced at python as well , if you can manage it.
I do believe i can get through this on my own, but.... JUST IN CASE.. Ya Know.
sometimes it's good to get another point of view.

Anyway, I'll repost this on the other thread and we'll continue testing it there.
Also get some people who have MSO8000 and even MSO7000  as i reckon i can make both of them happen.

[electricMN]

My scope has old firmware. Can I use this process to upgrade it to the latest version while adding all options?

[BTO]

My scope has old firmware. Can I use this process to upgrade it to the latest version while adding all options?
(Attachment Link)

yeah, Absolutely. it's not even a problem.
you are on 1.1.4..8, the lowest version that i went to
to test it was 1.1.4.4

SO, YOU'LL DO IT LIKE THIS

- From version 1.1.4.8

- UPGRADE AS NORMAL TO 1.3.2.2

- After that, Follow the pdf using the python script method,
  Since your scope is MSO5074  You're going to use the script called
 

Code: [Select]

rigol_kg2.py

[electricMN]

I have the options shown in the image. They came bundled with the scope. Is there anything special I need to do during the process of hacking to get all of the options? I thought I saw something about if you have the bundled options you'll have to delete them first prior to doing the hacking process.

[BTO]

I have the options shown in the image. They came bundled with the scope. Is there anything special I need to do during the process of hacking to get all of the options? I thought I saw something about if you have the bundled options you'll have to delete them first prior to doing the hacking process.

(Attachment Link)

That's fine, don't worry too much about it.

1. Just follow the PDF, it outlines the process of Uninstalling as well.

2. Now, as for the options,   The script actually checks what you have installed and what you don't.
   Since your options are correctly licenced from Rigol, Chances are they'll survive the upgrade.
   I would suggest you just do the process without uninstalling BECAUSE WE CAN KILL 2 BIRDS WITH 1 STONE HERE

3. Then after doing it WITHOUT UNINSTALLING, Let me know if it all went through properly, My gut feeling is.. it will.
    Now if it doesn't, it doesn't matter, it'll just fail and then you go back and uninstall the options and do it again.

but i reckon it'll go through just fine.

Just go ahead with it mate,  don't worry,
Follow the PDF and let me now if you have any issues

YOUR BIGGEST CONCERN IS...
DO NOT LOSE POWER DURING THE PYTHON SCRIPT PROCESS
DO NOT UNPLUG OR LOSE NETWORK CONNECTION DURING THE PROCESS

as for the rest of it,  You should be fine.

[electricMN]

Thanks, I'll give it a shot tomorrow. 

[BTO]

Thanks, I'll give it a shot tomorrow. 

No worries mate, YOU'LL BE RIGHT, Just follow the PDF.
I'm here if you need me

But since you have an older version 1.1.4.8
- I have no questions or concerns that you'll be able to upgrade to 1.3.2.2 , None at all.
- But since you have 1.1.4.8  WITH OPTIONS, do me a favour and the upgrade first WITHOUT Uninstalling Options

As for what that chatter was about the options.
IN CERTAIN SITUATIONS, Usually on the 100MHz Models, the other script was required the one ending in 3_000.py

Now...there has only been 1 person who had a MSO5074 that needed (what i call, the version 3) of the script.
Now.. it is possible that you'll need it.... Sure,  it's a REMOTE Possibility

but start on the first script that i mentioned and start without uninstalling options.
Nothing bad can happen if it fails

it's either
(Most likely) - Just gonna work and install all the other options you don't have
or
- You uninstall the options then do it again and it then works
or..
(Very unlikely) LOL - it didn't work on the first script so..  You use the 3_000.py  script and then it'll work without options uninstalled
or..
(Extremely Unlikely) - You then also need to uninstall the options and then it'll work

but in any of those cases, your scope isn't in any danger
if it fails you may get an ASSERTION ERROR
that's fine, it just means , use the other script  (i won't go into the detail of it)


BUT IN ALL LIKELIHOOD, IT'S JUST GONNA WORK THE FIRST TIME
Because the rigol_kg2.py is for MSO5074
the one ending in 3_000.py is for the MSO5100 (100MHz Series)
that's how it works,  As you increase to 100MHz, then 200MHz  then 350MHz  , Changes in the script need to be made to accomodate
what the scope is doing, But most people have MSO0574 and only SOME have MSO5100
I am yet to see a MSO5200  and i don't know why a person with a MSO5300 Would be here, since it's all unlocked anyway.

so that's what it's all about

JUST GO AHEAD AND DO IT, YOU'LL BE FINE

[electricMN]

Version 1.3.2.2 isn't available on Rigol's web site. Can I just go to 1.3.3.0 and skip 1.3.2.2?

[BTO]

Version 1.3.2.2 isn't available on Rigol's web site. Can I just go to 1.3.3.0 and skip 1.3.2.2?

LOL,,,,   I KNOW THAT

That's why i put everything into this 1 post

GO TO POST 1
GO TO THE LINK
DOWNLOAD WHAT YOU NEED
it's all there

all the versions that you need
the PDF
then a link to the training video's afterwards

but No don't go to 1.3.3.0 off the bat

go from 1.1.4.8    t0  1.3.2.2    then to 1.3.3.0
All the files are in the link
ALL THE FILES ARE ORIGINALS FROM RIGOL 100% Genuine Rigol files (Because, i keep these things when they come out)

[electricMN]

Sorry, I didn't realize the GEL file was in the zip file in your link. I won't bother you anymore. 

[BTO]

Sorry, I didn't realize the GEL file was in the zip file in your link. I won't bother you anymore. 

LOL, That's ok,
it's not a bother and ... Feel free to bother me anytime, it's not a problem for me.
but, EVERYTHING that you need is in that link, Just follow the PDF and you'll be ok, Everyone else has been so i'm confident you will as well.

Give me the good news when it's done

[electricMN]

Good news delivered. All is well with just a few minor hiccups, mostly my fault.
I didn't delete the options and just went on through the PDF document and in the end I've got an upgraded scope. Thanks so much for documenting this process in a manner most can understand. 

[BTO]

Good news delivered. All is well with just a few minor hiccups, mostly my fault.
I didn't delete the options and just went on through the PDF document and in the end I've got an upgraded scope. Thanks so much for documenting this process in a manner most can understand. 

THAT'S COOL...  GOOD WORK 

Also thanks for letting me know that you went from  FOR THE BENEFIT OF FUTURE READERS
From  1.1.4.8 (with Options Installed)
To       1.3.2.2
Then.. Running the script
Successfully Installing the other options
Then up to 1.3.3.0
and everything worked


NOW DON'T FORGET THE POST STUFF

- DO YOUR BACKUP
- SELF CHECK
- SELF CALIBRATION

Then, if you're not totally familiar with the scope, head over to the
https://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive
And you'll have a bunch of videos that will give you tutorial through the entire scope and it's features

You'll get some cool basic electronics troubleshooting

ENJOY YOUR SCOPE

[electricMN]

Did the post stuff as part of the process so I basically went from page 1 to the end and did it all. 

I'm fairly familiar with using an oscilloscope since I worked in electrical engineering but I'm not all that familiar with the capabilities of the MSO5000 so I'll be going to the thread you linked to and taking a look.

[BTO]

Did the post stuff as part of the process so I basically went from page 1 to the end and did it all. 

I'm fairly familiar with using an oscilloscope since I worked in electrical engineering but I'm not all that familiar with the capabilities of the MSO5000 so I'll be going to the thread you linked to and taking a look.

Did the post stuff as part of the process so I basically went from page 1 to the end and did it all. 

That's great, I always make a habit of reminding everyone because the checks, cal and backup are very important.
and peopole generally get caught up in the excitement of finally get all the options that they forget to backup

As for the rest, if you're familiar with scopes and you're an engineer, then you're probably ok.
I just did those videos mainly for the beginners and intermediate who want to understand their scopes and to help them
to understand how to test things properly with the scope

it has things like (if i remember)....    Calculating inductance with a scope by building a simple Tank Circuit , and explaining
how a square wave with a given duty cycle can be used on certain inductors to derive it's value
i think there's some transistor stuff in there . as well as some PWM stuff
there there's a tutorial on cursors',  Pass Fail mask , Etc etc
there's a lot there, chances are you'll find something interesting

Have fun with it

[Dorian_Kaf]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

first of all, amazing work you are doing!

Thank you , i appreciate it,  Although i'm not the only one doing the work,  But , thank you in any case.

I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade.

OK, That's not a problem.

Is this constellation possible?

CONSTELLATION ??,  Not sure what you mean .

However if you're asking
"Martin, i have a MSO5104 With all options licensed EXCEPT Sampling Memory and Bandwidth to 350MHz,  is it possible to upgrade
the features that i don't have to licenced status ?"
YES IT IS

Go to Post #1
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-dr-mefisto-licensing-method/

USE THIS LINK to get to the cloud
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

When you are there  YOU WANT TO DOWNLOAD THE FOLLOWING

- Downgrading to 1.3.2.2   Video  to show you how to get into the Pre Boot menu
- MSO5000 DrMefisto Licencing Method   PDF WITH DETAILED INSTRUCTIONS (Follow this step by step)
- rigol_kg2_3_000.py   This is the script you will use for MSO5100 SERIES
- Upgrading to 350MHz (1.3.2.2)  You will use this zip file for the 1.3.2.2  GEL FILE to downgrade to 1.3.2.2
- Upgrading to 350MHz (1.3.3.0)  You will use this zip file for the 1.3.3.0  GEL FILE and the backup files

download all that
1. Follow the PDF
2. Use the Script stated above for your particular scope
3. After you do all that, don't forget to backup the scope BEFORE and AFTER (this is all in the PDF)

and then you'll be fine

let me know if you have any issues.
Most people have said it's pretty easy to follow along

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

So.. How are you mate
How did you go with the licensing of your scope,   Any Drama's ?

[BTO]

And i already tried to hardcode the serial number and Model number in the code to get it to run.... It runs trough completely but no matter what i do, the outcome is never ... activated but either unavailable or not activated...

I would be so happy if you could help to get it to work...

Mate, it sounds like you're not doing something correctly Because...

LET'S GO THROUGH YOUR COMMENT STEP BY STEP

today i got my 5072 and right away i tried to upgrade it

OK with 5072 it's likely you'll need to use the script 

Code: [Select]

rigol_kg2.py

All the USB - Scripts ran fine and then i started with the Python script

ALL THE SCRIPTS ?  What do you mean "ALL" , There is only 1 script.

DID YOU FOLLOW THE INSTRUCTIONS IN THE PDF THAT I SUPPLIED AND DID YOU DOWNLOAD THE FILES FROM THE LINK THAT I SUPPLIED IN COMMNET 1 OF THIS THREAD ?

I installed all the modules ran the script with -i and then: (see picture).

the -i Switch DOES NOT INSTALL ANYTHING, the -i Switch just brings up the INFORMATION of the scope

And i already tried to hardcode the serial number and Model number in the code to get it to run

You did What   WHY ?   What exactly did you do ?


before you do this though , because i don't know what you've done, but it sounds really wrong.
I would DEFAULT THE SCOPE TO FACTORY SETTINGS

then..
Roughly stated the process is as follows
(You should really read the PDF as it is details everything)

- You connect your scope to power and network
- You install Python on your computer
- You download the content that you need from the link in Post 1
- You do your backups

- You get yourself on version 1.3.2.2

you run the INFORMATION script

You run the REGEN Script

You then run the script on it's own WITHOUT ANY SWITCH

then, You'll need to  run 1.3.2.2   again

You then run the INFORMATION SCRIPT AGAIN

This time NO NEED to run regen

You just then run the normal script again without the switch
and then it works


There's no need to hardcode or change anything


so..
HAVE YOU DOWNLOADED THE CONTENT FROM THE URL IN POST 1

HAVE YOU FOLLOWED THE INSTRUCTIONS IN THE PDF

[BTO]

And i already tried to hardcode the serial number and Model number in the code to get it to run.... It runs trough completely but no matter what i do, the outcome is never ... activated but either unavailable or not activated...

I would be so happy if you could help to get it to work...

I wouldn't worry too much, at this point it has worked for many people that there isn't much risk.

you should just need to follow the instructions in the pdf

if you can't get it, i'm happy to jump on a zoom with you or something and help you out. but .... it cirrently seems like you are doing some weird and incorrect stuff.
let me know how it goes

[BTO]

Hi BTO,
today i got my 5072 and right away i tried to upgrade it. All the USB - Scripts ran fine and then i started with the Python script. I installed all the modules ran the script with -i and then: (see picture).

It throws an error and terminates the script. Has it something to do with that the LA modules are limited time activated? I tried deactivating them with the script but it shows the same screen and terminates with same error and at the same point.

I really hope that you or somebody else can help me.

Thanks a lot already.

Best regards!

Sorry i had to run out there for a second.
I was going to say 
RE :
TYPE ERROR : CANNOT UNPLACK NON ITERABLE NON TYPE OBJECT

Basically the script was not able to unpack an object because it encountered incorrect values

CHECK THE FOLLOWING
- Download and read the PDF
- Ensure you have installed ALL THE MODULES
- Use your backup that you created (Please tell me you created a backup before you did this................right )  to restore the scope it's original settings

- See.. when you mentioned you hardcoded the serial and the model number,   this error may be happening because you did that .

we need to start your scope from a factory state
all those scripts you say you ran, whatever you did, you need to bring it back to factory again

then download the PDF and just follow it , No need to do anything fancy here, Just follow the PDF

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

Hi mate, what happened to your comments ? They disappeared, this you delete them ?

Look
WHAT OPERATING SYSTEM ARE YOU USING ?

so based on the message i got on my phone (that is no longer here on the forum)

- You're on 1.3.2.2 now    GOOD
- You've factory reset it    GOOD


- You said

I then tried the connection to the scope via pinging it

THEN.... NOTHING ?
so... What happened, When you send the ICMP Request (Communication Test) to the scope, What happened ?
Did the Scope ACK (Acknowledge) the request for more than 4 cycles or did it not ACK ?

then you said

Then i ran the script (rigol_kg2.py.) with -i

THAT'S INCORRECT !!

it's not

Code: [Select]

rigol_kg2.py.it's

Code: [Select]

rigol_kg2.py

it's very important that you followed PAGES 12 and 13 of the PDF and selected all those stated options during installation

also how are you running python ?
is it from Powershell
Windows Command Prompt
or
Python CLI

Now you're supposed to be doing this....

STEP 1.  (Assuming scope IP is 10.1.1.666)
Bring up INFORMATION

Code: [Select]

python rigol_kg2.py –i 10.1.1.666PRESS ENTER

STEP 2. REGENERATE THE PRIVATE KEY

Code: [Select]

python rigol_kg2.py –r 10.1.1.666PRESS ENTER

STEP 3. RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 10.1.1.666PRESS ENTER

now, Restart your scope
Reload 1.3.2.2 again via pre boot menu
Startup your scope

STEP 4.  (Assuming scope IP is 10.1.1.666)
Bring up INFORMATION

Code: [Select]

python rigol_kg2.py –i 10.1.1.666PRESS ENTER

STEP 5. RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 10.1.1.666PRESS ENTER

follow those steps and copy and paste my code in and see what happens

[Slats]

Please help.

I have Rigol MSO5074. I have followed the instructions exactly, but get an "AssertionError" when I do the -r step.

[BTO]

Please help.

I have Rigol MSO5074. I have followed the instructions exactly, but get an "AssertionError" when I do the -r step.

Sure no problem, it's not the first time it's happened. Usually it happens when it's an MSO5000 with BND Options.
or when it's MSO5100 series.
In any case, instead of using the following script

Code: [Select]

rigol_kg2.pydownload and use this one...

Code: [Select]

rigo_kg2_3_000.pyRun it again, As per the response in my previous comment to Dorian_kaf

Try it again and let me know if it works.

[Slats]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

[BTO]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

thanks for the quick responce.

No problem

HERE ARE MY THOUGHTS...
1. No, the hardware version isn't relevant,   You're on Version 1.3.2.2 According to the INFORMATION script.

2. Something fundamental isn't correct, Either
 - you got the wrong I.P. address for the scope
 - The Data stream is disconnecting
 - I doubt it's a python based issue
 - could be that there is an issue with your regen file

3. If you like and have some time we can jump on zoom now and sort this out a lot quicker than what it would be to go and forth with typing.
Would you like to do that ?

I feel, Just a few things need to be checked and i'm confident i'll find the issue and we'll have the scope licenced pretty quickly.

What are your thoughts ?

Also, Are you actually following the PDF or just the quick notes in the forum ?

[BTO]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

Here is a bit of a checklist

don't just skip through this and say   yeah yeah... Actually confirm each step, ok

- When you installed Python did you  do a CUSTOM INSTALLATION ?
- Did you also check the box that says  PATH ?
- then after installing python, did you open cmd.exe or  powershell and typed in

Code: [Select]

python
then press ENTER  to get the compiler screen,
Did you successfully get the screen ?
You can then type

Code: [Select]

exit()  and ENTER   to get out of it

- did you connect your scope to your PC Correctly and with Non Faulty Cables ?
- did you go into the scopes LAN settings and confirm DHCP is on and that the I.P. Address range, Matches the I.P. Address range in your router
when you open cmd.exe and type in

Code: [Select]

ipconfig  then ENTER

- then...   Open cmd.exe   or Powershell, (whichever you like)  DID YOU NOTE THE WORKING DIRECTORY ?
Meaning  if you open it and the path is

Code: [Select]

C:\Users\UserDid you place the script in that location ?   IF NOT.......... DO THAT !

- then when you created the regen file
-- was there another regen file or script in that location ?   if there was.. DELETE IT !

both the script and the regen file need to be in the same location as the working directory path that shows up in Python.
You must also use ONLY
cmd.exe    OR
Powershell

Do not use the Python CLI that comes with the installation.

- After that , You are supposed to ensure that you remove the patch method,  this is done by dropping from version 1.3.3.0  to 1.3.2.2 (you've done this)

- it's then just a question of

Load the -i command
Load the -r command
Load the script without any switch
then shutdown and reinstall 1.3.2.2
then restart and again
Load the -i command
DO NOT DO THE -r again
then load the script without any switch again

At this point it will activate

You seem to be falling over at the regen priv.pem stage
Check the folder locations
and also when redoing all this,  i would use the first script again  not the _3_000.py  one

Let me know if you want to jump on zoom
I'm off to bed now

[Slats]

Hey BTO, thank you for trying. However, I have given up and just used the patch method, which worked perfectly.

I went through your checklist again on my and my wifes computers.

- When you installed Python did you  do a CUSTOM INSTALLATION ?
- Did you also check the box that says  PATH ?

Yes, uninstalled and reinstalled Python.

- then after installing python, did you open cmd.exe or  powershell and typed in "python"
then press ENTER  to get the compiler screen,
Did you successfully get the screen ?

Yes, the Python interpretor loaded.

You can then type "Exit()"   and ENTER   to get out of it

Yes.

- did you connect your scope to your PC Correctly and with Non Faulty Cables ?

Yes. Validated cable was good by coping large files between devices.

- did you go into the scopes LAN settings and confirm DHCP is on and that the I.P. Address range, Matches the I.P. Address range in your router
when you open cmd.exe and type in "ipconfig" then ENTER

Yes, checked the IP and pinged successfully.

- then...   Open cmd.exe   or Powershell, (whichever you like)  DID YOU NOTE THE WORKING DIRECTORY ?
Meaning  if you open it and the path is "C:\Users\User"
Did you place the script in that location ?   IF NOT.......... DO THAT !

Yes.

- then when you created the regen file
-- was there another regen file or script in that location ?   if there was.. DELETE IT !

both the script and the regen file need to be in the same location as the working directory path that shows up in Python.

Yes. Location is corect, with script file in that location. Tried with and without deleting the regen file. Made no difference.

You must also use ONLY
cmd.exe    OR
Powershell

Do not use the Python CLI that comes with the installation.

Used both CMD and PowerShell. Made no difference.

- After that , You are supposed to ensure that you remove the patch method,  this is done by dropping from version 1.3.3.0  to 1.3.2.2 (you've done this)

Yes, did that.

Load the -i command
Load the -r command
Load the script without any switch
then shutdown and reinstall 1.3.2.2
then restart and again
Load the -i command
DO NOT DO THE -r again
then load the script without any switch again

At this point it will activate

Same "AssertionError". Nothing activated.

Thanks for trying, appreciate the effort.

[BTO]

Hey BTO, thank you for trying. However, I have given up and just used the patch method, which worked perfectly.

Sure no problem, i mean , i'm happy to jump on zoom but if you don't want to , then,  ok
as for the patch method,   Yes it does work, the only thing is you'll have to upgrade and repatch manually when the time comes.

in saying that,  I have a DS2000A that when i bought it was on version 1.1.0.0  or something like that
and i literally didn't upgrade for 11 Firmware versions and EVERYTHING WAS FINE

so i reckon you'll be ok with the patch.
so.. You're Welcome for the effort.

[BTO]

UPDATE
ASSERTION ERROR SOLVED

The first thing i want to say here is this....
If you got this error while activating
- You're probably scared
- You're probably discouraged
- You probably don't want to risk bricking your scope
- You're probably saying "You know... JUST IN CASE"

DO ME A FAVOUR.........FORGET ALL THAT OK
Because it's not relevant

Now that being said
I've created another script , it's at the same location.

https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

The script you need is named :   rigol_kg2_KEY2.py
The PDF File has been updated to include new information relating to the Assertion Error.

Follow the same process as you did before
and you should then find that you get 2 progress bars and no assertion error
and then the scope will be activated with all the options

WE HAVE PROVEN THIS WORKS

Also let me know which scope you have, as this worked on a MSO5072 with no bundles installed.
if you have a MS5100 i do still have another modification i can use on the script, but for now lets' try this one, i reckon it'll work.

NOW ....WHAT IS DIFFERENT IN THIS SCRIPT

An Assertion Error occurs
- When an Assertion is made
- And the Assertion returns FALSE
- Then an ASSERTION ERROR gets put up
- And the entire program HALTS

The reason it returns false is due to a "len" Statement.  which means... The program tested the LENGTH of the HEX Key
in your scope and compared it to the HEX key it was using.
Since the one the script is using is going to replace the one in your scope they need to be the same length.
In your case they were not and as such you get the error

The new script called  KEY2 (as the name suggests) Uses a different key or a different length
and when the challenge assertion is issued it returns  TRUE

SO.. GOOD NEWS GUYS,   WE HAVE A SOLUTION FOR YOU

Do let me know how it goes ok

[BTO]

MSO8000 HAS NOW BEEN HACKED SUCCESSFULLY

I'm putting this post here only because the MSO8000 and MSO7000 Guys are inevitably going to arrive here.

I don't want MSO8000 Discussions to happen on this thread so please PROCEED TO THIS LINK
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso8204-mso8000/msg5555455/#msg5555455

But yeah... Heads up.  THE MSO8000 HAS NOW BEEN FULLY LICENSED and unlocked with all options and up to 2GHz Bandwidth.
I'm not going to say i'm not jealous 
I mean... I helped the guys get to the goal, while i'm on my pityful MSO5000 with my pityful 350MHz   LOL

But yeah, it was cool.. CHECK IT OUT
and i reckon if we have any MSO7000 Guys out there we should be able to help them out as well.

That being said... Let's get back to MSO5000

[jujug28]

I'm getting the AssertionError even with the rigol_kg2_KEY2.py script. So far I've tried upgrading from 1.3.2.2 to 1.3.3.0, patching on 1.3.3.0, and "upgrading" back to 1.3.2.2. I have a brand new MSO5074 with no options other than some trial options that remain even after patching 1.3.3.0 and rolling back to 1.3.2.2. I'm not sure if that is normal, as I haven't found any information about it in other threads.

I'm willing to poke around some more with you if you want.

[BTO]

I'm getting the AssertionError even with the rigol_kg2_KEY2.py script. So far I've tried upgrading from 1.3.2.2 to 1.3.3.0, patching on 1.3.3.0, and "upgrading" back to 1.3.2.2. I have a brand new MSO5074 with no options other than some trial options that remain even after patching 1.3.3.0 and rolling back to 1.3.2.2. I'm not sure if that is normal, as I haven't found any information about it in other threads.

I'm willing to poke around some more with you if you want.

Hi mate
1., You don't need to poke around,  I'll help you
2. You're not gonna find anything anyway if you do poke around
3. in the last few days we've had some big progresses happening

so i reckon we'll do this.
As well as getting the 5000's activated, we can now do 7000's and 8000's as well

Do me a favour...PM ME and we'll make a time to get on skype and i'll help you out

[BTO]

Hi mate
ASSERTION ERROR IS SOLVED
WE HAVE A NEW SCRIPT

1. The script has been Re-Written
2. There is a new Script

Same location
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ
it's called

Code: [Select]

rigol_kg_LicensingUtility.py
Grab it

NOW READ THIS CAREFULLY
(SOME COMMANDS HAVE BEEN CHANGED)

1. it doesn't really matter what version your scope is on

2. Delete and discard of all other scripts that you have and use this one moving forward
   (it will work for ANY MSO5000, MSO7000 and MSO8000)

3. Ensure your working directory has the script copied into it
   and delete all Priv.pem files from it

4. Assume your I.P. Address is  10.1.1.666
RUN -i  INFORMATION

Code: [Select]

python rigol_kg_LicensingUtility.py -i 10.1.1.666
5. RUN -r REGENERATE PRIV.PEM

Code: [Select]

python rigol_kg_LicensingUtility.py -r 10.1.1.666
6. RUN -a ACTIVATION

Code: [Select]

python rigol_kg_LicensingUtility.py -a 10.1.1.666
7. RESTART THE SCOPE

8. RUN -a ACTIVATION........AGAIN

Now your scope will be activated and No Assertion Errors

After this

- Upgrade your scope to the latest version 1.3.3.0  if not already on it
- Do a Self Test
- Do a Self Cal

ENJOY

[BTO]

IF ANYONE IS STILL GETTING ASSERTION ERROR

ASSERTION ERROR IS SOLVED
WE HAVE A NEW SCRIPT
EDIT : This Post has been edited to include the latest script
- it's Faster
- Easier to use
- No need for you to know when to restart

1. The script has been Re-Written
2. There is a new Script

Same location
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ
it's called

Code: [Select]

Rigol_MSO_LicensingUtility_2.10b.pyGrab it

NOTE : It's Based on the 2.10b script by asp, I've made a few changes so it's easier to read and understand what's happening at each stage.
           But all in all asp did the heavy lifting.

NOW READ THIS CAREFULLY
(SOME COMMANDS HAVE BEEN CHANGED)

1. it doesn't really matter what version your scope is on

2. Delete and discard of all other scripts that you have and use this one moving forward
   (it will work for ANY MSO5000, MSO7000 and MSO8000)

3. Ensure your working directory has the script copied into it
   and delete all Priv.pem files from it

4. Assume your I.P. Address is  10.1.1.666
RUN -h  HELP and CREDITS and to familiarize yourself with the commands you will be using.

Code: [Select]

Rigol_MSO_LicensingUtility_2.10b.py -h 10.1.1.666
5. Assume your I.P. Address is  10.1.1.666
RUN -i  INFORMATION

Code: [Select]

Rigol_MSO_LicensingUtility_2.10b.py -i 10.1.1.666
6. RUN -r REGENERATE PRIV.PEM

Code: [Select]

Rigol_MSO_LicensingUtility_2.10b.py -r 10.1.1.666
NOTE : RESTART WILL HAPPEN AUTOMATICALLY
NOTE : ACTIVATION AND LICENSING WILL HAPPEN AUTOMATICALLY
NOTE : RESTART WILL HAPPEN AUTOMATICALLY
NOTE : YOU WILL BE ADVISED WHEN YOUR SCOPE IS RESTARTED AND READY AGAIN

NEW FEATURE ADDED ... REBOOT  (From Command Line) - No Need to press the button

Code: [Select]

Rigol_MSO_LicensingUtility_2.10b.py --reboot 10.1.1.666
ALSO, The Script runs much faster now,  Approx 1min for activation (not 15mins)

Now your scope will be activated and No Assertion Errors

After this

- Upgrade your scope to the latest version 1.3.3.0  if not already on it
- Do a Self Test
- Do a Self Cal

ENJOY

[Dude McGee]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script can be used later in case I need to restore the scope. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

[BTO]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script o restore the scope can be used later in case I need t. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

ALL GOOD QUESTIONS....

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot!

- You're Very Welcome, ENJOY IT
Now.. Don't forget a few things

- Do your backups (i'll address that in a second)
- Do your 3 Self Tests
- Do your Self Calibration

Then if you wish to learn how to use your scope in depth, i have around 13 Tutorial videos for you to learn from.  here..
https://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive

OK.. Now..

I used the PDF as the basis for the procedure

- Well Done
I'm in the process of updating the PDF, But hey, these things take time, it should be done in a few days.

See.... That PDF was created around the time when DrMefist0 and tv84 came out with the rigol_kg2.py script (Basically, the second script)
and the PDF was relevant for the 2nd script
then.. We had  a few modifications as a result of... someone had a 70MHz Scope with BUNDLES or they had a 100MHz scope etc etc
and there were slight modifications which resulted in around 4 or 5 scripts in total, but that pdf was still relevant

Then when we got the Assertion Errors and Rigol started playing with the Private Key again with scope models up to around 3months ago....
we altered the script again

THE SCRIPT HAS NOW HAD A COMPLETE OVERHAUL
It's Faster
and as you have seen
it's More Automated
No More Assertion Errors

See... Your scope activated BECAUSE, The script looks at the Private key and the padding and the Length of allocated FRAM
then it does a bunch of stuff that i won't go into detail with ... Basically, we've added more stuff into it that will audit your scope
and check what key length is needed , instead of using the same key length for all (Because that's how Rigol Triggers the Assertion Errors)

Then.. We made the script so..
1. When you select  -r  for Regen of Priv.pem   You don't need to reboot
2. Reboot is now Automatic, if required
3. You also don't need to -a  for Activation,   the script goes ahead and activates Automatically after the generation of the priv.pem file

Basically it does everything for you , You just need to put in   -i   and then  -r
it's kinda hard to get it wrong 

So.. Good work for using the PDF as a basis, at this point
SHORTLY I WILL UPDATE THAT PDF
We are also going to see a lot more people activating MSO5000, MSO and DSO7000 and MSO8000
Because this script looks at your scope and determines which one it is and applies the correct key length

We were looking at having it activate the DHO Series as well, Although at this point, i don't think they work the same way.
but.. WE ARE LOOKING INTO THAT AS WELL.

I just have one question: Maybe it's my fault

- OF COURSE IT'S YOUR FAULT :p  WHY WOULD YOU ASK SUCH A STUPID QUESTION... IT'S ALL YOUR FAULT MATE ... EVERYTHING !!!   

but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA.

- YES IT IS..!!
it's in Steps 6 , 7 and 8 of the pdf
Here is the link to the cloud

https://mega.nz/folder/OsJyFY5A#8uS0fmepgBdNrXqvnxmFfg

and I HAVE ATTACHED THE PDF FOR YOUR CONVENIENCE

1. Since you're activated, UPGRADE TO 1.3.3.0 Firmware Version,  If you are on that version, it doesn't matter, Get the same file anyway
2. You're supposed to get the UPGRADING TO 350MHZ (1.3.3.0)  Zip File and Extract it
3. After Extraction, you're going to have 3 folders
BACKUP
GEL FILE
FIRMWARE

No Points for guessing which one you're supposed to get   (BACKUP FOLDER)

do that and follow the PDF

So, Since your scope is now fully licensed and Activated, You want to back it all up, JUST IN CASE, something happens.

Furthermore I don't understand how the backup data which is generated by your script

OK...  A BIT OF TECHNICAL JARGON COMING UP
I don't wish to confuse matters, But....

1. For simple backup, You don't use the script, in the first place.... You use the zip file that i provided
2. You put that bugger on a USB stick and stick it in the scope in the pre start menu and hit UPGRADE and it adds the backup files to your USB,
    Then, You copy those files to your computer and save them

NOW, IF YOU WANT TO GO BEYOND THAT.....

3. OK, The script in total, HAS THE FOLLOWING OPTIONS
Which you can achieve by running the script with the -h Switch as follows

Code: [Select]

python Rigol_MSO_LicensingUtility_2.09b.py -h 10.1.1.666
but the switches are as follows

Code: [Select]


INFORMATION (Brings up Basic Information)
python Rigol_MSO_LicensingUtility_2.09b.py -i 10.1.1.666

REGENERATE PRIVATE KEY (Creates the Priv.pem file and places it in the current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -r 10.1.1.666
(this will in turn trigger the Activation)

ACTIVATION (If you need to do it manually, Only if Priv.pem already exists)
python Rigol_MSO_LicensingUtility_2.09b.py -a 10.1.1.666

Now... All of that is standard stuff
BUT LET'S NOW GET INTO USEFUL STUFF

Code: [Select]

REBOOT THE SCOPE (No Need to press the power button, Restart the Scope from the C.L.I.)
python Rigol_MSO_LicensingUtility_2.09b.py --reboot 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

DEBUGGING MODE (adds Extra Useful information if a problem exists)
python Rigol_MSO_LicensingUtility_2.09b.py -d 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

Now.. if for any reason we need to debug your scope further and someone gets another Assertion Error
we are going to ask for
1. A DUMP of your FRAM
2. A DUMP of your PUBLIC KEY
so...

FRAM DUMP (Copies your FRAM to a file in your Current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -f 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

PRIVATE KEY DUMP (Copies your Private key to a file in your Current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -p 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

There are other switches such as
-k = Manually Change the Key in Use
-m = Manually change the Model Name in Use
-s = Manually change the Serial Number in Use

it's highly likely we will never need to use these, However, it's just a provision IN CASE the script doesn't Automatically detect the key in use
or Model Name or Serial number, (These options are here JUST IN CASE), it's not even worth explaining it , at this stage.

NOW..... IF YOU WISH TO SSH INTO YOUR SCOPE

Code: [Select]

SSH (Allows you to connect via SSH to your scope)
python Rigol_MSO_LicensingUtility_2.09b.py -e 10.1.1.666

NOW TAKE NOTE
1. This option is put here so you IF YOU NEED TO, You can go in and change certain things or that i can , It's unlikely you'll need it.
2. HOWEVER IT IS FUN TO PLAY WITH IF YOU HAVE NEVER DONE IT BEFORE
3. but TAKE CAUTION
4. So.. If you want to poke around a little,  You can do this....

5. Run the Above command and it will say
"****SSH ACTIVATED****"
"Now..Open PuTTY."

If you don't have it already, Download PuTTY, it's a serial Console that allows you to interface with the scope via a  C.L.I.

6. Open PuTTY
- Enter the IP Address of your scope (Make sure your scope is turn on of course and connected to the network)
- leave the port as 22
Press connect and you'll see a console window pop up

7. You want to now login as root  Your Username and password are either going to be
Username :  rigol
Password  :  rigol
or
Username :  root
Password  :  Rigol201

You won't see the cursor progressing,  Just type it in and press enter  DO NOT PRESS BACKSPACE

if it lets you in, You'll see some more directories, You're going to access the root directory first, it'll be weird

NOW LET'S BRUSH UP ON SOME INSTRUCTIONS

Code: [Select]

cd = Change Directory , But this will fail if you don't specify WHICH directory you want to go to

cd[SPACE][DIRECTORY NAME]
Example :
cd data = This will change the directory location to the "data" folder

cd .. = This takes you BACK one step

cd / = This takes you back to the HOME Directory

ls = List the folders and files in THE CURRENT DIRECTORY

ls la = List ALL the folders and files in the current directory and add a few extra details

so here is what you want to do
AS SOON AS YOU GET THE SHELL AND GET PAST LOGIN

Code: [Select]

cd ..BECAUSE, You're going to be in the root folder and you want to be in the HOME DIRECTORY

Now

Code: [Select]

ls laPRESS ENTER

You might want to look around a little, so.. To see the contents of the home DIRECTORY you use "dir"

Code: [Select]

dirPRESS ENTER, You will see the folders in that directory

Now..
You might want to go to, Let's say...... "data" or  "user" if you want to go to user folder

Code: [Select]

cd userPRESS ENTER

and.. that's how you navigate through the folders
Remember

Code: [Select]

cd ..is to go back to the previous folder

and if you come across a file , you can open the file with

Code: [Select]

od [filename]PRESS ENTER

So if you're game....   Be Cautious and have some fun poking around a bit

to get out, You just type
exit
press enter

NOW...

restore the scope can be used later in case I need it

- I Purposely didn't include that as i didn't want to confuse people, it's also very unlikely to occur
- FOR NOW........BACKUP YOUR SCOPE,   if it happens.... Send me a PM
if it never happens, You'll never need to use it
But it's handy if you brick your scope (which almost never happens)

And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

The PDF Explains it
But...
You're going to do 2 Backups
BACKUP 1,  You'll create a folder in your computer called BACKUP SCRIPT
and when you run the backup script,  it's gonna add files to your USB
You place those extra files into the BACKUP SCRIPT on your PC

BACKUP 2, You do the same thing, except the folder is now called NAND SCRIPT.
same thing, Run the NAND SCRIPT and copy the files from the USB to the folder

What are the files good for.
You'll thank yourself when you brick your scope or if the scope fails for some reason.

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

OK, SO... EVERYONE ASKS THIS....

We have included two switches that are relevant

Code: [Select]

UNINSTALL OPTIONS (Uninstalls all options in the scope)
python Rigol_MSO_LicensingUtility_2.09b.py -u 10.1.1.666

if however you want to just Uninstall 1 option at a time you use

Code: [Select]

UNINSTALL OPTIONS (Uninstalls all options in the scope)
python Rigol_MSO_LicensingUtility_2.09b.py -o [Option Name]10.1.1.666

Now, if you purchased the scope from Rigol WITHOUT OPTIONS, then you can use

Code: [Select]

python Rigol_MSO_LicensingUtility_2.09b.py -u 10.1.1.666
This will Uninstall ALL OPTIONS and then it will Automatically REBOOT the scope to finish the process.
when you restart you can run  -i to confirm that they are all gone

AS FOR RESETTING FIRMWARE VERSIONS

1. it's not a RESET,  do not view it that way .
it's an UPGRADE or  DOWNGRADE of Firmware Versions

2. So.... if you are on a lower version, Say... 1.3.2.2   and you want to upgrade
    YOU CAN DO THAT DIRECTLY FROM THE SCOPE'S OPERATING SYSTEM
     or
    You can enter the PRE BOOT Menu and select  FIRMWARE UPGRADE.
    To do this you must have a USB Stick with the Higher Firmware Version loaded (Let's say 1.3.3.0)
    This process takes you from 1.3.2.2  to 1.3.3.0

3. You don't need to upgrade or downgrade Sequentially, You can jump from any version to any version, But not the same version

4. Now... if you need to downgrade,   Say from  1.3.3.0  to   1.3.2.2
    YOU PREPARE THE GEL FILE (1.3.2.2)  , it's at the link
     in this case, you cannot do it via the operating system, it won't allow downgrading
     HOWEVER... The preboot menu option that says UPGRADE FIRMWARE   can do it

     You see.... UPGRADE FIRMWARE doesn't mean UPGRADE firmware....... it means   LOAD FIRMWARE

SO YES.... YOU CAN DOWNGRADE THE FIRMWARE

But..
- Since your scope is fully licensed (unlike the Patched version, that would lose the options during upgrade or downgrade)  YOU WON'T LOSE THE OPTIONS
  in the downgrade

- You then need to Uninstall the options

- it doesn't matter if you uninstall them , Before or After the downgrade or upgrade


NOW WHEN YOU GET THE SCOPE BACK FROM RIGOL
Run the script again -r
and it'll just activate the scope as it did before
You then upgrade to the latest version
and confirm that your scope is licensed and activated

and do your Self Checks and Self Cal

LASTLY..........
You are now fully licensed so.....
ANY FUTURE FIRMWARE VERSIONS THAT COME OUT
You can just go to the Rigol Website and get the .GEL file and load it either via the operating system or Pre Boot Menu

AND.......THAT'S PRETTY MUCH IT

ANY QUESTIONS ?

[Dude McGee]

ANY QUESTIONS ?

  At least not at this very moment! Your dedication is awesome, a thousand thanks go out to you for these answers!

I've found the BACKUP DUMP reference in STEP 8 of the PDF, and I'll work further with your latest post and the PDF to understand more of all this. And then I'll be watching the 13 videos you've prepared 

[BTO]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script can be used later in case I need to restore the scope. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

NOTE : THE PDF FILE HAS BEEN UPDATED

It can be obtained from here
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

[BTO]

ANY QUESTIONS ?

  At least not at this very moment! Your dedication is awesome, a thousand thanks go out to you for these answers!

I've found the BACKUP DUMP reference in STEP 8 of the PDF, and I'll work further with your latest post and the PDF to understand more of all this. And then I'll be watching the 13 videos you've prepared 

The PDF HAS BEEN UPDATED....
I have attached the updated version for you , Discard the old one.

At least not at this very moment!

- Cool

Your dedication is awesome, a thousand thanks go out to you for these answers!

- You're welcome, it's not a problem, I Enjoy doing this .

I've found the BACKUP DUMP reference in STEP 8 of the PDF,

- it's actually STEP 6,  STEP 7  and STEP 8 Combined,   Don't just skip to Step 8

and I'll work further with your latest post and the PDF to understand more of all this.

- No Problem, In your own time.

And then I'll be watching the 13 videos you've prepared 

- Cool, i hope you enjoy them, there's a lot of cool stuff there about your scope, and there's some useful electronics troubleshooting as well,
  Real world practical examples on how to use your scope when measuring things, Timings, Calculating inductor values and things as such.

if you have any questions, Ask me !

Be cool

[BTO]

QUICK UPDATE

PAGE 1 POST OF THIS THREAD HAS BEEN UPDATED

- To Reflect The Correct CURRENT procedure for Correct Licensing of the scope
- To make obsolete the "Hacking Method" that does not survive firmware upgrade - it is still useable, Just not advised
- Firmware File has been upgraded to the latest 2.10b version
- Firmware and instructional pdf has been added to the attachment on post 1
- All outdated steps have been striked out

[sdouble]

I would like to thanks all of you guys for the effort you put into that work.
I ordered some MSO5074s and plan to upgrade them.
A stupid question though  : is the router absolutely needed ? A direct ethernet connection would not work ?
Best

[BTO]

I would like to thanks all of you guys for the effort you put into that work.
I ordered some MSO5074s and plan to upgrade them.
A stupid question though  : is the router absolutely needed ? A direct ethernet connection would not work ?
Best

I would like to thanks all of you guys for the effort you put into that work.

- You're Welcome, Much appreciated

I ordered some MSO5074s and plan to upgrade them.

- Cool

A stupid question though

- THERE ARE NO STUPID QUESTIONS....
well... I mean... LOL
Unless you ask then i repeat then you ask and i repeat and we do that 15times
That would be stupid 
But.... As you were  LOL

is the router absolutely needed ? A direct ethernet connection would not work ?

This is a catch-22 question and answer.
You see (Before i give you the answer)...
What you're talking about required a "Cross over Cable" which works on a Peer To Peer Topology.
This is basics of Networking.
Now.. if you were familiar with the basics of Networking YOU WOULDN'T BE ASKING THIS QUESTION.

If you were familiar with Crossover Cables and the OSI Model, this question wouldn't exist

SO FOR YOU
FOR THE SAKE OF NOT BRICKING YOUR SCOPE
FOR THE SAKE OF STUPID CRAP NOT HAPPENING

MY OFFICIAL POSITION IS............ YES FOR YOU A ROUTER IS ABSOLUTELY NECESSARY
The I.P. Address is required, Because of how the script works.

INTERNET CONNECTION HOWEVER... IS NOT REQUIRED
So, to be clear, You can pull some shitty router out of the garage and all you need is
ROUTER
POWER SUPPLY
ETHERNET CABLE
Router cannot be in Bridge mode (Must be in Router Mode with DHCP Enabled)

But, Internet is not required
LAN Connection is required,   don't go down the WiFi Road

You can find routers on gumtree for Free if you don't have one, but i'd be asking...
How the hell are you on this forum if you don't have a router ?

Hope that helps

[sdouble]

Dear BTO,

Thanks for your thorough response.
As you kindly noted, my experience with networking is limited. I frequently use high speed ethernet switches to connect various equipment (including relatively fast digitizers), but clearly, network technology is far from my area of expertise (which is primarily experimental nuclear physics).
Is it a problem if I don't have a internet connection ?
Don't jump on me, just kidding.
I mentioned that fact that i'll be getting MSO5074s very soon. Actually I'll get a set of 4 with the current option bundle at work.
Big lab, no available router there. Or, to be more precise, not allowed to connect to any of the routers there.
I may bring a router from home for the very purpose of upgrading the scopes though.

[BTO]

Dear BTO,

Thanks for your thorough response.
As you kindly noted, my experience with networking is limited. I frequently use high speed ethernet switches to connect various equipment (including relatively fast digitizers), but clearly, network technology is far from my area of expertise (which is primarily experimental nuclear physics).
Is it a problem if I don't have a internet connection ?
Don't jump on me, just kidding.
I mentioned that fact that i'll be getting MSO5074s very soon. Actually I'll get a set of 4 with the current option bundle at work.
Big lab, no available router there. Or, to be more precise, not allowed to connect to any of the routers there.
I may bring a router from home for the very purpose of upgrading the scopes though.

Thanks for your thorough response.

- You're Welcome

As you kindly noted, my experience with networking is limited.

- Indeed, and i assure you the comment was made with all the best intentions

I frequently use high speed ethernet switches to connect various equipment (including relatively fast digitizers), but clearly, network technology is far from my area of expertise

- Fair enough, we all start somewhere

(which is primarily experimental nuclear physics).

- Soooo.... You're saying..... You don't really have that much experience   

Is it a problem if I don't have a internet connection ?

- if it's a question pertaining to activating your scope......NO PROBLEM AT ALL, NOT IN THE SLIGHTEST

Don't jump on me, just kidding.

- I was going to applaud you for learning 

I mentioned that fact that i'll be getting MSO5074s very soon. Actually I'll get a set of 4 with the current option bundle at work.
Big lab, no available router there. Or, to be more precise, not allowed to connect to any of the routers there.

- OK,  AND... OSCILLOSCOPES ARE NOT ALLLOWED TO BE HACKED...........................................WHAT'S YOUR POINT 

2. If you merely connect to the ethernet port , WHO'S GONNA KNOW and... What if you do , You literally need to be connected for 2 - 5mins
    If i were you, i'd connect and upgrade it like you stole it

3. if you must wimp out and "FOLLOW THE ROOLZ" then... Yes you can bring a router from home,
   After all it just needs power and ethernet cable.   No internet required.

[sdouble]

I frequently use high speed ethernet switches to connect various equipment (including relatively fast digitizers), but clearly, network technology is far from my area of expertise

- Fair enough, we all start somewhere

(which is primarily experimental nuclear physics).

- Soooo.... You're saying..... You don't really have that much experience   

==>>  I would love to be less "experienced"

OK,  AND... OSCILLOSCOPES ARE NOT ALLLOWED TO BE HACKED...........................................WHAT'S YOUR POINT 

==>> Yep, being in the grey  zone I guess....

2. If you merely connect to the ethernet port , WHO'S GONNA KNOW and... What if you do , You literally need to be connected for 2 - 5mins
    If i were you, i'd connect and upgrade it like you stole it

==>> I caught you being very wrong here. I would not do that knowing , that I don't want to be fired within hours... My lab is pretty closed...

3. if you must wimp out and "FOLLOW THE ROOLZ" then... Yes you can bring a router from home,
   After all it just needs power and ethernet cable.   No internet required.

==>> No internet required, for sure 

[BTO]

I frequently use high speed ethernet switches to connect various equipment (including relatively fast digitizers), but clearly, network technology is far from my area of expertise

- Fair enough, we all start somewhere

(which is primarily experimental nuclear physics).

- Soooo.... You're saying..... You don't really have that much experience   

==>>  I would love to be less "experienced"

OK,  AND... OSCILLOSCOPES ARE NOT ALLLOWED TO BE HACKED...........................................WHAT'S YOUR POINT 

==>> Yep, being in the grey  zone I guess....

2. If you merely connect to the ethernet port , WHO'S GONNA KNOW and... What if you do , You literally need to be connected for 2 - 5mins
    If i were you, i'd connect and upgrade it like you stole it

==>> I caught you being very wrong here. I would not do that knowing , that I don't want to be fired within hours... My lab is pretty closed...

3. if you must wimp out and "FOLLOW THE ROOLZ" then... Yes you can bring a router from home,
   After all it just needs power and ethernet cable.   No internet required.

==>> No internet required, for sure 

==>>  I would love to be less "experienced"

I Understand what you mean

==>> Yep, being in the grey  zone I guess....

Fair enough

==>> I caught you being very wrong here. I would not do that knowing , that I don't want to be fired within hours... My lab is pretty closed...

ahh yes, the corporate grip on the employee   LOL
You gotta love the world we live in don't ya

[Ralfyny]

MSO5074, Worked like a charm, initially started with the network / python version. Then opened up the PDF, took about 20 minutes after that. Used a 2Gb thumb drive from 12 years ago. In the end works perfectly… almost no computer skills required…
Date 10/12/2024

[el314]

Hello,
I don't understand where lies the problem.
My python setup is ok, all the modules are ok as well.
I'm on the MacOS Swquoia 15.0
py --version
Python 3.11.2

-h argument works well, but the -i doesn't

I have problems running the script:
py Rigol_MSO_LicensingUtility_2.10b.py –i 192.168.1.89
usage: Rigol_MSO_LicensingUtility_2.10b.py [-h] [-d] (-i | -e | -r | -a | -f | -p | -u | --reboot | --cfram-file rigol_fram_XXXXXXXXXXXX.data) [-k {1,2}] [-m MSO5074] [-s MS5A123456789] [-o AUTO,AERO,AUDIO]
                                           [--sys-vendor-file rigol_vendor_XXXXXXXXXXXX.data] [--no-reboot] [--with-config] [--no-color]
                                           ip_addr
Rigol_MSO_LicensingUtility_2.10b.py: error: one of the arguments -i/--info -e/--ssh -r/--regen -a/--activate -f/--save-fram -p/--save-pk -u/--uninstall --reboot --cfram-file is required

[serguletti]

Hello!
Thank you for your work. Successfully updated my MSO5072 according to your instructions. Used the PyCharm terminal on MacOS with downgraded to V 1.3.2.2 and updated to V 1.3.3.0. I can't find what is included in self test ( 3 test ) ? Is this Key, Screen, Touch test? Thanks again.

[BTO]

Hello!
Thank you for your work. Successfully updated my MSO5072 according to your instructions. Used the PyCharm terminal on MacOS with downgraded to V 1.3.2.2 and updated to V 1.3.3.0. I can't find what is included in self test ( 3 test ) ? Is this Key, Screen, Touch test? Thanks again.

Correct, the 3 tests are  Key tests, Screen Colours, Touch Test
and do a self calibration

[BTO]

Hello,
I don't understand where lies the problem.
My python setup is ok, all the modules are ok as well.
I'm on the MacOS Swquoia 15.0
py --version
Python 3.11.2

-h argument works well, but the -i doesn't

I have problems running the script:
py Rigol_MSO_LicensingUtility_2.10b.py –i 192.168.1.89
usage: Rigol_MSO_LicensingUtility_2.10b.py [-h] [-d] (-i | -e | -r | -a | -f | -p | -u | --reboot | --cfram-file rigol_fram_XXXXXXXXXXXX.data) [-k {1,2}] [-m MSO5074] [-s MS5A123456789] [-o AUTO,AERO,AUDIO]
                                           [--sys-vendor-file rigol_vendor_XXXXXXXXXXXX.data] [--no-reboot] [--with-config] [--no-color]
                                           ip_addr
Rigol_MSO_LicensingUtility_2.10b.py: error: one of the arguments -i/--info -e/--ssh -r/--regen -a/--activate -f/--save-fram -p/--save-pk -u/--uninstall --reboot --cfram-file is required

If you are not successfully executing the -i switch then you have a networking issue.
Mac is notorious for security and blocking things

if you can't -i then it's likely it won't activate either
i would suggest checking the security features of your mac and the network as something is blocking the python program

did you also install python as per the instructions i gave in the pdf or did you already have it installed ?

[rteodor]

Hello,
I don't understand where lies the problem.
My python setup is ok, all the modules are ok as well.
I'm on the MacOS Swquoia 15.0
py --version
Python 3.11.2

-h argument works well, but the -i doesn't

I have problems running the script:
py Rigol_MSO_LicensingUtility_2.10b.py –i 192.168.1.89
usage: Rigol_MSO_LicensingUtility_2.10b.py [-h] [-d] (-i | -e | -r | -a | -f | -p | -u | --reboot | --cfram-file rigol_fram_XXXXXXXXXXXX.data) [-k {1,2}] [-m MSO5074] [-s MS5A123456789] [-o AUTO,AERO,AUDIO]
                                           [--sys-vendor-file rigol_vendor_XXXXXXXXXXXX.data] [--no-reboot] [--with-config] [--no-color]
                                           ip_addr
Rigol_MSO_LicensingUtility_2.10b.py: error: one of the arguments -i/--info -e/--ssh -r/--regen -a/--activate -f/--save-fram -p/--save-pk -u/--uninstall --reboot --cfram-file is required

If you are not successfully executing the -i switch then you have a networking issue.
Mac is notorious for security and blocking things

if you can't -i then it's likely it won't activate either
i would suggest checking the security features of your mac and the network as something is blocking the python program

did you also install python as per the instructions i gave in the pdf or did you already have it installed ?

The problem is that the "minus" sign is not realy minus but a Uicode char. Just replace it.

[BTO]

Hello,
I don't understand where lies the problem.
My python setup is ok, all the modules are ok as well.
I'm on the MacOS Swquoia 15.0
py --version
Python 3.11.2

-h argument works well, but the -i doesn't

I have problems running the script:
py Rigol_MSO_LicensingUtility_2.10b.py –i 192.168.1.89
usage: Rigol_MSO_LicensingUtility_2.10b.py [-h] [-d] (-i | -e | -r | -a | -f | -p | -u | --reboot | --cfram-file rigol_fram_XXXXXXXXXXXX.data) [-k {1,2}] [-m MSO5074] [-s MS5A123456789] [-o AUTO,AERO,AUDIO]
                                           [--sys-vendor-file rigol_vendor_XXXXXXXXXXXX.data] [--no-reboot] [--with-config] [--no-color]
                                           ip_addr
Rigol_MSO_LicensingUtility_2.10b.py: error: one of the arguments -i/--info -e/--ssh -r/--regen -a/--activate -f/--save-fram -p/--save-pk -u/--uninstall --reboot --cfram-file is required

If you are not successfully executing the -i switch then you have a networking issue.
Mac is notorious for security and blocking things

if you can't -i then it's likely it won't activate either
i would suggest checking the security features of your mac and the network as something is blocking the python program

did you also install python as per the instructions i gave in the pdf or did you already have it installed ?

The problem is that the "minus" sign is not realy minus but a Uicode char. Just replace it.

OK, if you want to do that then
the problem is that the Unicode char is not really a Unicode Char but a sequence of electrical impulses turning on or off

The switch doesn't need to be changed, it has been tested and worked for hundreds of people thus far.
There is a problem on your end , which is why you can't even bring up the information table
as i said... Mac is notorious for blocking things as a result of it's security
and also i would check the networking.
Did you follow the instructions in the pdf or not ?

[rteodor]

I mean the problem is in el314 command and not in the script. "–i" is not the same as "-i" even if some fonts make it look the same.
I won't look up what unicode chars are each. Its not worth that effort.

[BTO]

I mean the problem is in el314 command and not in the script. "–i" is not the same as "-i" even if some fonts make it look the same.
I won't look up what unicode chars are each. Its not worth that effort.

I didn't ask you to look all that up, But i still don't understand your problem

1. What is el314

2. if the problem is in this el314 thing and not in the script then.. that's good

3. You're simply just supposed to
Install Python
Get the script
Open a terminal
Call the python interpreter to run the script

what part of this are you not doing ?

[Kean]

I copied and pasted the "-i" text from the error posted by user el314 into a text editor, and looked at it in hex view

A minus sign is 0x2D in ASCII
The long-dash/hyphen in the command/error posted by el314 is utf-8 0xE28093 - this is a unicode en-dash https://decodeunicode.org/en/u+2013
Thus it is not properly recognised by python command parsing

This is a common issue when copy/pasting command lines from a word processing document (or PDF created from one) as the word processor "helpfully" converts to nice unicode symbols.
Other than minus/hyphen symbols, it often also happens to double quotes - changing to unicode opening and closing quotes.

BTO, you need to spend more time reading/comprehending posts and less time replying.  Please... as you are someone who talks about others disrespect...

[BTO]

I copied and pasted the "-i" text from the error posted by user el314 into a text editor, and looked at it in hex view

A minus sign is 0x2D in ASCII
The long-dash/hyphen in the command/error posted by el314 is utf-8 0xE28093 - this is a unicode en-dash https://decodeunicode.org/en/u+2013
Thus it is not properly recognised by python command parsing

This is a common issue when copy/pasting command lines from a word processing document (or PDF created from one) as the word processor "helpfully" converts to nice unicode symbols.
Other than minus/hyphen symbols, it often also happens to double quotes - changing to unicode opening and closing quotes.

BTO, you need to spend more time reading/comprehending posts and less time replying.  Please... as you are someone who talks about others disrespect...

Ok mate
1. thanks for clarifying that el314 is a user on the forum

2. so the beginner doesn't know , then, if he is copying and pasting from a word doc that they need to copy and paste that into a text document
    to remove the formatting that word docs add.   OK

3. At the end of the day ... HUNDREDS of people have activated and unlocked their scopes, Experts, Beginners , all of them.  Not 1 has had this problem.
    so we need to ask, what is this user doing different that everyone else did not do ?
    Also if the problem is with copy and paste, why then don't they just enter the command manually.

it's still unclear why this issue is happening with this user, I mean, i want to help this person but they are not being clear,
i asked them did they follow the PDF i supplied, that was asked twice, i still have no received an answer to that question so that i could then ask them
at what step they stuffed up at.

This isn't rocket science mate, They just need a terminal and python and to enter the command and run the script.
so why is it happening to this one user and not everyone else, do you think ?

as for the rest of your advice, i'll take it onboard, but sometimes (just as you are busy with work) I don't have a lot of time to read through all the comments,
sometimes i grab a coffee and do have the time and other times i can only respond quickly.  the last few times were a quick response.

but again, it's just the running of a script.  why are they struggling with it ?

so the question at the end of the day is... HOW DO WE GET THIS  BEGINNER USER ACTIVATED ?
What are your thoughts ?
i'm thinking they should try and jump on another computer, Possibly a windows based system and just use cmd or powershell
even though people have activated via Mac, they tend to have issues, but they did get there in the end.
But this guy is having an issue that no one else had.

what are your thoughts ?

[Kean]

so we need to ask, what is this user doing different that everyone else did not do ?

The problem is that it is visually hard to spot, and the programs/scripts don't give helpful errors when parsing unicode parameters.
I haven't checked, but I suspect this (unicode paste) may be more of an issue on Linux and Mac terminal than Windows command line.

I know I've seen this issue on Linux when writing up documents with step-by-step instructions for clients.  I make an effort to revert any changes that Word makes to quote and hyphen symbols so that copy/paste still works.

Edit to add: Also, for short commands not everyone will use copy & paste.  And I suspect some users when they get an error, will try again by manually retyping the command, not knowing about command history.

[BTO]

so we need to ask, what is this user doing different that everyone else did not do ?

The problem is that it is visually hard to spot, and the programs/scripts don't give helpful errors when parsing unicode parameters.
I haven't checked, but I suspect this (unicode paste) may be more of an issue on Linux and Mac terminal than Windows command line.

I know I've seen this issue on Linux when writing up documents with step-by-step instructions for clients.  I make an effort to revert any changes that Word makes to quote and hyphen symbols so that copy/paste still works.

Edit to add: Also, for short commands not everyone will use copy & paste.  And I suspect some users when they get an error, will try again by manually retyping the command, not knowing about command history.

The problem is that it is visually hard to spot, and the programs/scripts don't give helpful errors when parsing unicode parameters.
I haven't checked, but I suspect this (unicode paste) may be more of an issue on Linux and Mac terminal than Windows command line.

- OK so it appears to be a thing with Terminal. I suspected it had to be something like that. Although other mac users have not had the same issue.
  I guess.. is there another terminal they could download and use in place of Terminal, Perhaps if they used a windows based terminal in Wine or something.
  I know wine isn't the most reliable thing but hey if it'll get past this step perhaps it's a viable option.

I know I've seen this issue on Linux when writing up documents with step-by-step instructions for clients.  I make an effort to revert any changes that Word makes to quote and hyphen symbols so that copy/paste still works.

- I make an effort whenever copying things from word to put it in a text editor like Notepad or Notepad++ before pasting

Edit to add: Also, for short commands not everyone will use copy & paste.  And I suspect some users when they get an error, will try again by manually retyping the command, not knowing about command history.

-  I Agree

[BTO]

I mean the problem is in el314 command and not in the script. "–i" is not the same as "-i" even if some fonts make it look the same.
I won't look up what unicode chars are each. Its not worth that effort.

Hi mate, so if the problem is Mac Terminal
Are you able to jump onto a windows system just for the sake of activating your scope
or.. Perhaps are you able to utilize Wine or another terminal, At the end of the day we just need to get past this command don't we ?
If you can issue the command correctly then your scope will be activated

what are your thoughts on this?

[rteodor]

The problem is that it is visually hard to spot, and the programs/scripts don't give helpful errors when parsing unicode parameters.
I haven't checked, but I suspect this (unicode paste) may be more of an issue on Linux and Mac terminal than Windows command line.

- OK so it appears to be a thing with Terminal. I suspected it had to be something like that. Although other mac users have not had the same issue.
  I guess.. is there another terminal they could download and use in place of Terminal, Perhaps if they used a windows based terminal in Wine or something.
  I know wine isn't the most reliable thing but hey if it'll get past this step perhaps it's a viable option.

I know I've seen this issue on Linux when writing up documents with step-by-step instructions for clients.  I make an effort to revert any changes that Word makes to quote and hyphen symbols so that copy/paste still works.

- I make an effort whenever copying things from word to put it in a text editor like Notepad or Notepad++ before pasting

The user el314 might have copied the command from your pdf, page 14 step 13.
There is a simple fix for this but it requires discipline from the documentation producer: use a proper font/text style for commands and code snippets.
MS Word 2010 that produced that pdf has, if I remember correctly, such style already defined with a monospace font. It is practical and aesthetically pleasing and avoids that dreaded "helpful flufishness" entirely.

As for me I am not unlocking any scope. Just noticed the error in a moment of procrastination.

[BTO]

The problem is that it is visually hard to spot, and the programs/scripts don't give helpful errors when parsing unicode parameters.
I haven't checked, but I suspect this (unicode paste) may be more of an issue on Linux and Mac terminal than Windows command line.

- OK so it appears to be a thing with Terminal. I suspected it had to be something like that. Although other mac users have not had the same issue.
  I guess.. is there another terminal they could download and use in place of Terminal, Perhaps if they used a windows based terminal in Wine or something.
  I know wine isn't the most reliable thing but hey if it'll get past this step perhaps it's a viable option.

I know I've seen this issue on Linux when writing up documents with step-by-step instructions for clients.  I make an effort to revert any changes that Word makes to quote and hyphen symbols so that copy/paste still works.

- I make an effort whenever copying things from word to put it in a text editor like Notepad or Notepad++ before pasting

The user el314 might have copied the command from your pdf, page 14 step 13.
There is a simple fix for this but it requires discipline from the documentation producer: use a proper font/text style for commands and code snippets.
MS Word 2010 that produced that pdf has, if I remember correctly, such style already defined with a monospace font. It is practical and aesthetically pleasing and avoids that dreaded "helpful flufishness" entirely.

As for me I am not unlocking any scope. Just noticed the error in a moment of procrastination.

As for me I am not unlocking any scope. Just noticed the error in a moment of procrastination

OH, ok

The user el314 might have copied the command from your pdf, page 14 step 13.

Fair enough.. In saying that... Many other users have likely done the same thing and had no issues.

There is a simple fix for this but it requires discipline from the documentation producer: use a proper font/text style for commands and code snippets.
MS Word 2010 that produced that pdf has, if I remember correctly, such style already defined with a monospace font. It is practical and aesthetically pleasing and avoids that dreaded "helpful flufishness" entirely.

Fair enough, i'll have a look at that and redo it

[Kean]

- I make an effort whenever copying things from word to put it in a text editor like Notepad or Notepad++ before pasting

This isn't really a workable solution as even simple text editors these days support (and generally default to) Unicode.  You often have to go out of your way to get plain ASCII, and this can result in data loss as most Unicode symbols have no ASCII equivalent.

FYI, I originally copied and pasted the bad command line posted earlier into Visual Studio Code on Win10 and saved it as a text file.  I could then see the character data as Unicode in hex view, which I posted above.

Just now, I did the same on my Mac using textEdit - the native text editor app on MacOS.  By default it saves in RTF format, but I changed preferences to use plain text.  I then confirmed that it also saved that hyphen/en-dash as Unicode by using the Hex Fiend app.  For some reason Visual Studio Code on Mac isn't displaying anything for me in Hex Editor view.  I can of course also see the hex data using od or xxd command line tools.

As far as I know there is no Notepad++ for Mac.  The equivalent was probably TextWrangler, now replaced by BBEdit, but I don't have those as I have standardized to VS Code across all my machines these days.

[BTO]

- I make an effort whenever copying things from word to put it in a text editor like Notepad or Notepad++ before pasting

This isn't really a workable solution as even simple text editors these days support (and generally default to) Unicode.  You often have to go out of your way to get plain ASCII, and this can result in data loss as most Unicode symbols have no ASCII equivalent.

FYI, I originally copied and pasted the bad command line posted earlier into Visual Studio Code on Win10 and saved it as a text file.  I could then see the character data as Unicode in hex view, which I posted above.

Just now, I did the same on my Mac using textEdit - the native text editor app on MacOS.  By default it saves in RTF format, but I changed preferences to use plain text.  I then confirmed that it also saved that hyphen/en-dash as Unicode by using the Hex Fiend app.  For some reason Visual Studio Code on Mac isn't displaying anything for me in Hex Editor view.  I can of course also see the hex data using od or xxd command line tools.

As far as I know there is no Notepad++ for Mac.  The equivalent was probably TextWrangler, now replaced by BBEdit, but I don't have those as I have standardized to VS Code across all my machines these days.

This isn't really a workable solution as even simple text editors these days support (and generally default to) Unicode. 

- Well, putting all scope activation matters aside.
  I work on Linux (Zorin and Parrot) as well as Windows (7, 10, 11).
  I rarely jump on Mac but i do have one but the wife uses it more than i do.
  Now in the past whenever i've had to remove formatting i always threw it in notepad or notepad++ and it has ALWAYS Worked, Without Fail !

I've never personally had that problem with Mac, then again i haven't done a majority of coding in Mac only Windows and Linux really.

As far as I know there is no Notepad++ for Mac

- You're Correct... To my knowledge Notepad++ doesn't support Mac, although.. How hard is it really to find a text editor or source code editor ?

If Mac users are having these issues they can just throw the code into a text editor then copy it out of it can't they.
I can also (if it'll work) Create a Notepad document with the raw codes needed without the formatting

NB.  The formatting was put there in the first place (since you mentioned it earlier) to "Newbie Proof" the process so they don't brick their scopes or get confused as to what code to use. That's why i edited the text and colourized it.

So Instead of me changing the original document i suppose they have these 3 options

1. Copy it as is from the document and likely in most cases it will work
2. If it doesn't, Type it in Manually
3. I could make a text document and put a reference to it in the pdf and the txt document on the cloud so they can copy straight out of it

This also doesn't seem like it's a big problem
1. I've only heard of it happening once (now) over hundreds of successful activations
2. I mean... They can type it in manually can't they ? and it'll work
3. In any case, it's going to be occurring in a very very small number of cases so couldn't i then handle that on a case by case basis

But hey, i'm willing to put in a bit of effort if it'll help people, So far the PDF has been successful with many many activations so on those grounds
i'm inclined to keep it as is.
As i said, Maybe i could include a .txt doc    What do you think ?

[clefranc]

Hi,
Thanks a lot for the easy patch! I really appreciate it—I couldn’t afford all those options on my Rigol.

I did run into a small issue when using the script. After manually installing Python on my Windows 11 system, the "python" command wasn't recognized; only "py" was. Since the script uses "python" as the command, I resolved this by adding the following PowerShell alias so both "py" and "python" would work:

Code: [Select]

Set-Alias -Name python -Value py
Alternatively, installing Python from the Microsoft Store ensures "python" is recognized right away (who knew!).

[Kangfu]

Hi all,

first of all thank you for the great effort and tutorials on the MSO Series.

I just wanted to info about a fix I did for me in the python script, sorry if this was already covered and I didn't read the correct page.

I had to exchange the Regex from:
#SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES\$(.+?)\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)\$(.+?)\$(.+?)$')
to this:
SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES\$(.+?)\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)$')

as there was a second new line in my response instead of a $, i have 4 times 3 digit ip adress.
so maybe these new lines can happen on different systems depending on string size?

So here is a general new Regex with matching $ or Newline and not interfering with the group numbers
SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(?:\n|\$)(.+?)(?:\n|\$)(.+?)$')

best regards and thanks again!

[andser]

Hi, BTO!
Thanks a lot for your great work!
I've successfully licenced my MSO5074.
One little question. Is it required to update my scope to the latest version 1.3.3.0 or I can stay at 1.3.2.2?

Thanks

[BTO]

Hi all,

first of all thank you for the great effort and tutorials on the MSO Series.

I just wanted to info about a fix I did for me in the python script, sorry if this was already covered and I didn't read the correct page.

I had to exchange the Regex from:
#SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES\$(.+?)\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)\$(.+?)\$(.+?)$')
to this:
SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES\$(.+?)\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)\n\$(.+?)\$(.+?)$')

as there was a second new line in my response instead of a $, i have 4 times 3 digit ip adress.
so maybe these new lines can happen on different systems depending on string size?

So here is a general new Regex with matching $ or Newline and not interfering with the group numbers
SERIAL_PAT = re.compile(rb'RIGOL TECHNOLOGIES(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(?:\n|\$)(.+?)(?:\n|\$)(.+?)(?:\n|\$)(?:\n|\$)(.+?)(?:\n|\$)(.+?)$')

best regards and thanks again!

Thanks for that, i'll have a look at it over the next few days

[BTO]

Hi, BTO!
Thanks a lot for your great work!
I've successfully licenced my MSO5074.
One little question. Is it required to update my scope to the latest version 1.3.3.0 or I can stay at 1.3.2.2?

Thanks

Assuming you used the latest licensing Method script and not the Patch method.
NO. it's not strictly necessary to upgrade to the latest firmware version, Although it is recommended.
You can stay on 1.3.2.2 if you like.
Hell you can even stay on 1.3.1.1 if you like. it's up to you.  But i do recommend keeping up with the latest version
Also understand..... Regarding VNC Viewer ,  it isn't supported on versions below 1.3.2.2  i'm pretty sure on 2.2 is it , and i know it definitely is on 1.3.3.3.0
so keep that in mind as well

[andser]

And if I stay at 1.3.2.2 (which was installed at the factory), use licensing method, should i recalibrate the scope after all?

[BTO]

And if I stay at 1.3.2.2 (which was installed at the factory), use licensing method, should i recalibrate the scope after all?

1. You can stay on whichever version you like if you used the Licensing Method to activate your options on your scope.

2. Regardless of which version you choose to stay on IT IS HIGHLY RECOMMENDED......AFTER EACH VERSION CHANGE that you run the following

SELF CALIBRATION
SELF TEST (this consists of 3 tests)

However of all of them the Calibration is the most important, Now it's not like your scope will blow up if you don't run a self cal
and it's not like your readings will be incorrect necessarily

but .. there are reasons why we follow these procedures, and you as a beginner should make it good practice to follow them until you understand
when and where you don't need to.

so YES, YOU SHOULD RUN A SELF CALIBRATION after the upgrade

[65roadster]

Thanks for the diligent and ongoing work on this!

I have carefully followed the PDF instructions but am hung up on Step 15, a screen shot is attached. ```No connection could be made because the target machine actively refuses it.```

I verified that my scope has a proper IP address via DHCP (192.168.1.10). The subnet is correct (255.255.255.0). The default gateway is correct (192.168.1.1). The subnet and gateway match the results of 'ipconfig' on my windows PC.

The scope pings (ping -t 192.168.1.10) with 1ms response.

MSO5074
Scope firmware 1.3.3.0.
Python version 3.13.1
Windows PC IP address is 192.168.1.17, subnet 255.255.255.0, default gateway 192.168.1.1.
The scope and Windows PC are both connected via wired ethernet through a TP-Link access point.

Any help is appreciated!

Edit: webcontrol and Ultrasigma also do not work. Webcontrol just reports problem loading page and Ultra Sigma can't find the device by IP Address or by searching. This does not appear to be an issue related to the upgrade/hack process, but something I can't figure out on the scope itself. "Online Upgrade" and "option install" menu items on the scope are also greyed out.

Edit: I tried resetting to factory defaults by pressing "single" several times at power-up. This didn't resolve connections via Ultra Sigma, web control, or the Python script.

[65roadster]

Problem is solved. The IP address my scope showed on the screen was actually assigned to another device on my network. My scope is configured for DHCP, auto IP, not static IP, and showed being connected to the network. I'll go debug that.

In the meantime, the hacked upgrade worked like a charm. Thanks to all who have contributed!

[BTO]

Problem is solved. The IP address my scope showed on the screen was actually assigned to another device on my network. My scope is configured for DHCP, auto IP, not static IP, and showed being connected to the network. I'll go debug that.

In the meantime, the hacked upgrade worked like a charm. Thanks to all who have contributed!

sorry for the late reply
I realize you already solved it.  but i was gonna say

- Try Pinging the scope from your command shell first (that should always be common practice before you even post.
Example : My scope works with VNC to my Electronics computer without issue and has been doing so for a long time.
                today i went to do a tutorial video for someone and all of a sudden , i go to open VNC Viewer and it's taken way too long to load then times out.
                Ultimately.. The plastic Mod 5 Connector on the end of the cable had come out of the port JUST A SMIDGE.

               Now the first thing i did was.... Ping the bloody scope. and i could not.  Once you can't ping something you go back to Basic Troubleshooting... OSI MODEL Level troubleshooting.

              so..... LAYER 1 - Physical Layer , is anything broken etc etc  (My problem was a layer 1 Problem)
                        LAYER 2 - MAC Addresses , Figure out what you're network devices are doing and if they are functioning correcvtly
                        LAYER 3 - IP ADDRESSES (Your problem was a Layer 3 Problem)

Usually you'll most commonly troubleshoot these 3 layers.  sometimes (Especially in TP Link) the router can trip you up

CHECK    EASY MESH Settings (Best to Disable Easy Mesh)
Also disable  QOS (Quality of Service)

Then you have Firewalls

In your case, You had an I.P. Address Conflict,   now we need to ask WHY
Since your SCOPE was on DHCP  and AUTO IP   then your scope is not the issue

Now ask...
Is your Router setup for DHCP or STATIC IP ?
is the other device that shared the scopes I.P. Address STATIC of DHCP

For the most part , your network should be DHCP with the possible excption of your printer
a Printer I.P. Address is commonly 40 or 80   so   192.168.1.40  or 192.168.1.80  is the I.T. Accepted convention and if you have multiple printers you identify them as 40, 41 , 42 etc or  80,81,82 etc

in any case, You got it done... WELL DONE.. GOOD WORK

Keep those troubleshooting points in mind though.

[Gerhan]

I would like to extend my sincere thanks to BVO for their clear and structured process in hacking the MSO5100. The video tutorial was detailed and thorough, allowing me to understand all aspects of the MSO5000 series. A month ago, I successfully updated my MSO5000, and today, I purchased a DP932U and hacked it to a DP932A. I am currently focused on acquiring a RIGOL spectrometer. I highly recommend the MSO5000 for its powerful logic analyzer – an excellent product that continues to impress.

[nephilim]

Many thanks from my side, too! Got my 5074 today and with the pdf and scripts it was a breeze to unlock all the goodies. FYI, no problem here with a 4x3 digit IP.

[BTO]

I would like to extend my sincere thanks to BVO for their clear and structured process in hacking the MSO5100. The video tutorial was detailed and thorough, allowing me to understand all aspects of the MSO5000 series. A month ago, I successfully updated my MSO5000, and today, I purchased a DP932U and hacked it to a DP932A. I am currently focused on acquiring a RIGOL spectrometer. I highly recommend the MSO5000 for its powerful logic analyzer – an excellent product that continues to impress.

Thanks Mate, Appreciate it
it's not all my doing actually
The title of this thread  Dr Mefisto is largely to be thanked, as well as TV84 , ASP and many others.
I'm just the one that helps people run the script and troubleshoot 
it's me that you see and hear the most of , The other guys are hidden away in middle earth at the centre of the earth working on projects to Hack the Planet

They are Night dwellers, The Nightbreed that only come out when they need to feed or gather information or pull down an unsuspecting victim
that they need to feed on  LMFAO

But... YOU'RE WELCOME
and Glad you got your scope unlocked

[BTO]

Many thanks from my side, too! Got my 5074 today and with the pdf and scripts it was a breeze to unlock all the goodies. FYI, no problem here with a 4x3 digit IP.

You're very welcome mate
Did you also check out the deep dive video series (since you're a newbie)

[nephilim]

Did you also check out the deep dive video series (since you're a newbie)

Yes - I started watching them already. Looking forward to exploring the scope! Many thanks for recording and sharing these!

[BTO]

Did you also check out the deep dive video series (since you're a newbie)

Yes - I started watching them already. Looking forward to exploring the scope! Many thanks for recording and sharing these!

You're Welcome
I'm glad you took a look at it
The one specific reason why i made those videos is so that beginners can get beyond the basics of

- Adjust time Base
- Adjust Amplitude Base
- Measure a Battery voltage
- Hook scope up to a blinking LED

This gets boring very quickly and doesn't help anyone learn much.
But now if you get into it a bit further , at least.. knowing how to use Cursors to measure.
that can then take you much further
and then you have a whole slew of tricks you learn
then Math Functions and triggers

Once you learn this  YOUR SCOPE BECOMES FUN and you learn so so so much
that was the main purpose of the video series.   to get beginners out of the beginner phase.

so i'm glad you saw it

[Gerhan]

BVO,

I trust your recommendations and have high confidence in them. I'm relatively new to spectrometers and was wondering – do you offer sessions on Rigol spectrometers? I’d love to find a tutorial for the RSA3000, along with some quality hacks. 😄 Would you agree that’s not too much to ask? :