Okay, let's go over the moment of correctly installing Python and its modules; if at least one of the modules is not installed,
the script will not be executed at all, but we see that it is launched.
Here is the sequence I followed (according to your instructions):
1) installed firmware version 1.3.2.2
2) python rigol_kg2.py –i xx.xx.xx.xx
3) python rigol_kg2.py –r xx.xx.xx.xx (we get an error, but the key file is being created)
4) python rigol_kg2.py xx.xx.xx.xx
5) flash again firmware version 1.3.2.2
6) python rigol_kg2.py –i xx.xx.xx.xx
7) python rigol_kg2.py xx.xx.xx.xx
Is everything right?
Not exactly, and as i suspected, YOU'RE SKIPPING STEPS,
You've basically taken what i instructed and SUMMARIZED IT. don't do that.
i we are going to help you, you have to follow the steps EXPLICITLY !! You already have a problem , skipping introduces more problems.
RE This
let's go over the moment of correctly installing Python and its modules; if at least one of the modules is not installed,
the script will not be executed at all, but we see that it is launched.
and.. No mention of what options you selected upon install python, You just SKIPPED to the part of installing the modules
Also, you didn't answer my question about zoom (i will therefore no longer ask, it will be upon you to ask if you want it now)
Now you stated 7 steps, Mate in the PDF there are like 22 steps i think
but let's jump to step 3 in your list
3) python rigol_kg2.py –r xx.xx.xx.xx (we get an error, but the key file is being created)
OK, so if you got an error while creating the priv.pem why did you proceed ?
but also, we didnt' get a screenshot to show any of this
Now re this
4) python rigol_kg2.py xx.xx.xx.xx
You said that you ran -r
then you ran the script
HOWEVER IN YOUR SCREENSHOT IT IS CLEARLY SEEN THAT YOU RAN
-r then
-r
then the error happened
so like i said.... Start it all over again, Follow those instructions that i gave you.
Give us the screenshots, Each and everyone in a separate comment. I know it's a pain, but it will help immensely and will get your scope
licensed correctly, ARE YOU ABLE TO DO THAT ?
I want to help you, but at times you're being vague and not precise.
so far i've activated 7 people, its unlikely that your scope is different to their one
and another 3 or 4 people have just done it on their own without a problem, we only had 1 complaint , and that was valid
and that was that i forgot to include the step with the modules in the pdf, i've corrected this
so..
we know the script works
we know the PDF works
we know our scopes are the same
the only 2 things that are variables are..
You... and Your computer
Are you able to try the process on another computer by any chance ?
Also... You know how you suggested there is a problem with the script and we should get DrMefist0 involved.
here is my opinion of what is happening with him
1. i reckon he's busy
2. i reckon he's see the post and isn't bothering because he knows there isn't a problem with the script.
Guys like DrMefist0 don't just jump in for any reason, but i reckon if there was a valid problem with the script, he would jump in and rectify it.
i reckon he's just waiting for all of us to troubleshoot through it, Exercise some common sense and work through the problem without him
getting invovled as there is no need to.
Again, Many others are doing it without problem. this problem is isolated to you and we need to weed out what's going on.
Now, he wrote the script, Fair enough, I know enough python to see what's in the script, but clearly he is more fluent at python that i am.
Not to say that i don't understand it though. but it's a pretty straight forward script to understand what's going on
ON ANOTHER QUICK NOTE and i don't know if this may benefit you, You can go ahead and try it as well.
as per the PDF, we are
Downgrading from 1.3.3.0 to 1.3.2.2
then we are applying the -r then running the script
then we run 1.3.2.2 again
then we run the script again
and that activates it.
A USER BROUGHT UP... Why don't we just activate it from 1.3.3.0
Now.. there are downsides to this
THE MAIN BEING... when you do the full activation you end up on 1.3.2.2 and then you UPGRADE to 1.3.3.0 and you can see confirmation
that options survived activation.
I have not actually tried to run the script from 1.3.3.0 , MAYBE YOU WANT TO GIVE IT A GO, it can't hurt, Worse case, it doesn't license it.
you've lost nothing
I'm going to try and give it a go in the near future, just to see what happens
so... I REALLY REALLY BELIEVE if you put in the effort to give us all those step by step screenshots
1. we can get to the root of the problem
2. it was ABSOLUTELY help others if they have the same problem
what are your thoughts