-
Oh well then.. it's 100% compatible with your scope as i also have a MSO5074.What Model do you have anyway ?
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 runningCode: [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.
-
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 -
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. 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 atCode: [Select]python rigo_kg2.py [Your I.P. Address here]there is no switch here.
if you keep running the script asCode: [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. -
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.QuoteI 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.QuoteThe 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 MSO5074QuoteThat 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 -
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!
-
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
-
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 likeCode: [Select]ModuleNotFoundErrorand it will have something on the end... Like thisCode: [Select]ModuleNotFoundError: No Module named 'requests'This means that you do not have the "REQUESTS" Module installed, to install the module you do this...Quotepip 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.Quotepip intstall tqdm
Quotepip intstall tabulate
Quotepip intstall xxtea
Quotepip intstall ecdsa
When you have all options installed and you runQuotepython 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 -
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 isCode: [Select]pip intstall argparseCode: [Select]pip intstall base64Code: [Select]pip intstall binasciiCode: [Select]pip intstall os.pathCode: [Select]pip intstall reCode: [Select]pip intstall socketCode: [Select]pip intstall structCode: [Select]pip intstall timeCode: [Select]pip intstall zlibCode: [Select]pip intstall requestsCode: [Select]pip intstall tqdmCode: [Select]pip intstall hashlibCode: [Select]pip intstall tabulateCode: [Select]pip intstall xxteaCode: [Select]pip intstall struct import packCode: [Select]pip intstall ecdsa
YOU CAN RUN THIS COMMAND TO SEE THE INSTALLED MODULESCode: [Select]pip list
-
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 ?
-
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,
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 @BTOQuotefor me all have worked very well. Job well done with PDF @BTO
Thankyou and Excellent work WELL DONEQuoteThe 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 -
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 ? -
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.
-
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 calledCode: [Select]rigol_kg2_3_000in 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 thisCode: [Select]python rigol_kg2_3_000 -i 10.1.1.666replace 10.1.1.666 for your I.P. Address
STEP 5 - Run the -r commandCode: [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 switchCode: [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 thisCode: [Select]python rigol_kg2_3_000 -i 10.1.1.666
STEP 11 - Run the script without the switchCode: [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.
-
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 -
Hi,
Hi Michal, Hope your scope is going well.
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
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 -
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! -
Thanks BTO,
THAT'S AWESOME.. Well Done
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!
You're Welcome
it is interesting however that , You have an MSO5074 and yet you used theCode: [Select]python rigol_kg2_3_000.pyscript
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 -
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. -
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.QuoteFirst, thank you for all of the instructions and hard work!
You're WelcomeQuoteI 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 PROBLEMQuoteI 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 optionsQuoteMy 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 itQuoteIs 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
ExampleCode: [Select]python rigol_kg2_3_000.py -i 192.168.0.158TO UNINSTALL YOU RUNCode: [Select]python rigol_kg2_3_000.py -u 192.168.0.158QuoteI 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 followCode: [Select]python rigol_kg2_3_000.py -i 192.168.0.158Code: [Select]python rigol_kg2_3_000.py -r 192.168.0.158Code: [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
thenCode: [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 ?
-
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
-
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! -
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)
THERE YOU GO, that's Awesome
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!
Now don't forget to follow those last few steps in my last post in the EDIT section
the are important, but.. WELL DONE -
Dear BTO
Hi mate
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
firstlyQuoteI am new to this forum (and a newbie).
That's ok, no problemQuoteI 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 thisQuoteYour summary of the diverse posts re the methods made it all so clear. Great work.
THANKS i appreciate that.
QuoteWould 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.QuoteI 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 instructionsQuoteI understand it may have the same board.
No, the MSO5000 and the DS1100B have different boards, i'ts not even the same process.QuoteIt 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... YESQuoteI 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.QuoteDespite 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 upgradedQuoteBTW 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 200MHzQuoteI 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