I also assumed that not many people have removed the upgraded licenses yet.
Each license creates a ".lic" file in /rigol/bin.
You can add them, remove them, do whatever you like. They're just a text file with the license key in it to match the file name.
I also assumed that not many people have removed the upgraded licenses yet.
Each license creates a ".lic" file in /rigol/bin.
You can add them, remove them, do whatever you like. They're just a text file with the license key in it to match the file name.
That was obvious once I opened the batch file and saw the adb shell rm command. I suppose I should have shared that for people following along though.
Follow up to my original post:
I modified rgtool.go for my DHO914S to try to extract the BW15T25 license key from the Key.data file to upgrade to 250 MHz bandwidth. When I run it I get back a string that shows this:
Key: brainpoolP256r1;0429C03147397DB14EF8300804016CDF9281DBBE2E3488ADC3BAD82E042
B00A6E8509E688BA16719D929D2314CE1978E17EC393A58E27D70B49133A80B3B6E831E
Generating options for DHO9XXXXXX
:SYST:OPT:INSTall%!(EXTRA string=DHO900-BW15T25@8bd798ba1bd51cdbee7792d403cf4f8e
60a7d9802aaa6f5315498d25ffe5bae906e69767702c7527bce533b1ebe963bd)
What does all of this output signify? Why does the output of the rgtool program show "EXTRA string=" and have the presumed license string enclosed in parentheses? Is BW15T25 the valid keyword to extract the license key?
I used the SCPI interface to try to install this license but obviously it doesn't work.
Thanks!
What does all of this output signify? Why does the output of the rgtool program show "EXTRA string=" and have the presumed license string enclosed in parentheses?
I had the same output, so no worries about that.
I used the SCPI interface to try to install this license
In this way:
:SYST:OPT:INST DHO900-BW15T25@8bd798ba1bd51cdbee7792d403cf4f8e
60a7d9802aaa6f5315498d25ffe5bae906e69767702c7527bce533b1ebe963bd
?
What options will be shown on your DHO914S ?
Just a theoretical question, if I upgraded my DHO914s from BW 125MHz to 250MHz is it possible to undo the upgrade later, and how would that be done? Reversing the change would reduce input noise and aliasing effects.
Thanks for the info. As I understand it, you got the same output format as I did with the :SYST:OPT:INSTall%!(EXTRA string= at the beginning and the ) at the end, and you just edited out the all%!(EXTRA string= and the )?
I tried that and still no joy. My installed options are the same as before, with three serial bus analysis options (embedded, auto, and computer), as well as the Bode plot analysis. The "About" screen shows DHO914S (Max BW 125M).
What am I doing wrong?
Hi,
Yepp only copy this :
DHO900-BW15T25@8bd798ba1bd51cdbee7792d403cf4f8e
60a7d9802aaa6f5315498d25ffe5bae906e69767702c7527bce533b1ebe963bd
And type it in the scpi command prompt like I´ve posted before with :SYST:OPT:INST
My installed options are the same as before
Your options screen shows nothing else ?
Just a theoretical question, if I upgraded my DHO914s from BW 125MHz to 250MHz is it possible to undo the upgrade later, and how would that be done?
I guess (not know!) by removing the license key.
Reversing the change would reduce input noise and aliasing effects.
I consider noise to be negligible.
Just a theoretical question, if I upgraded my DHO914s from BW 125MHz to 250MHz is it possible to undo the upgrade later, and how would that be done? Reversing the change would reduce input noise and aliasing effects.
Yes. It's easy.
Either delete the license file using ADB or try ":SYST:OPT:UNINST ALL"
(I'm typing that last command from memory from DS1054Z days so it
might be wrong.
Point is: It CAN be done... I've done it several times with ADB method while I was messing around. Basic ADB use is well worth learning for hacking these 'scopes... )
adb connect 192.168.1.xxx:55555 (five fives)
adb shell ls -l /rigol/data (all the files related to model/licenses are in "/rigol/data")
adb pull /rigol/data/file.dat
adb push file.dat /rigol/data
adb shell rm /rigol/data/file.dat
In your case it would be much easier to push a DHO924's vendor.bin to your scope than to mess around generating licenses. There's one attached to the fifth post of this thread.
Remember: Pull your own vendor.bin file first and keep it safe so you can push it back and return to your original DHO914.
Thank you very much Martin72 and Fungus, good to know.
Reversing the change would reduce input noise and aliasing effects.
I consider noise to be negligible.
I didn't notice any change in noise level when I was switching between 804/924.
Aliasing will change in DHO924 mode when more than two channels are enabled (312.5MHz sample rate isn't high enough for 250MHz+ analog bandwidth).
Solution: Be aware of it. Go to 625MHz sample rate by turning off a channel or two when you're looking at something important or when you suspect aliasing is happening.
Remember: Aliasing can occur at
any frequency. I can alias a 1kHz sine wave as something else by setting up my 200MHz DHO800 badly enough.
I modified rgtool.go for my DHO914S to try to extract the BW15T25 license key from the Key.data file to upgrade to 250 MHz bandwidth. When I run it I get back a string that shows this:
.........
I used the SCPI interface to try to install this license but obviously it doesn't work.
Thanks!
Use my
Rigol Unlock Tools. It's a trasparent script. Original instruction has some mistakes.
Just a theoretical question, if I upgraded my DHO914s from BW 125MHz to 250MHz is it possible to undo the upgrade later, and how would that be done? Reversing the change would reduce input noise and aliasing effects.
Yes, you can delete lic files, see the
Rigol Unlock Tools
Thanks for the info! I ran your unlock tool after modifying it for my HDO914S, but I still cannot get the bandwidth to upgrade. I'm running 1.01 firmware, if that makes any difference. Here's the output from run_DHO_tools.bat:
C:\Users\Stan\Desktop\ADB>run_dho_tools_900.bat
List of devices attached
connected to 192.168.1.211:55555
Here you can find all *.lic files of options already installed:
total 680
-rwxrwxrwx 1 system system 148 2013-01-18 08:55 Key.data
-rwxrwxrwx 1 system system 1876 2013-01-18 08:51 cal_adc.hex
-rwxrwxrwx 1 system system 348 2023-11-06 20:08 cal_afe_bandwidth.hex
-rwxrwxrwx 1 system system 348 2013-01-18 08:52 cal_afe_zero.hex
-rwxrwxrwx 1 system system 96372 2013-01-18 08:58 cal_afg.hex
-rwxrwxrwx 1 system system 76 2013-01-18 09:09 cal_ddr.hex
-rwxrwxrwx 1 system system 36 2013-01-18 09:12 cal_la.hex
-rwxrwxrwx 1 system system 156 2013-01-18 08:58 cal_lsb.hex
-rwxrwxrwx 1 system system 205084 2013-01-18 09:07 cal_vertical.hex
drwxrwxrwx 2 root root 4096 2023-06-02 14:16 default
drwxrwxrwx 2 root root 4096 2013-01-18 16:50 probe
-rwxrwxrwx 1 shell shell 220 2023-10-28 22:12 vendor.bin
Making backup, see the "/backup/" folder (you can install it from a flash drive,
as you do it with the official update)
/rigol/data/Key.data: 1 file pulled, 0...kipped. 0.0 MB/s (148 bytes in 0.040s)
go run rgtoolMod.go
keyFile: Key.data
deviceId: DHO9
SCPI format: ':SYSTem:OPTion:INSTall'
options: [BODE BW15T25]
Key: brainpoolP256r1;0429C03147397DB14EF8300804016CDF9281DBBE2E3488ADC3BAD82E042
B00A6E8509E688BA16719D929D2314CE1978E17EC393A58E27D70B49133A80B3B6E831E
Generating unlock SCPI commands for the DHO900 series scope:
:SYSTem:OPTion:INSTall DHO900-BODE@20634951498c770751a30efddf5229e51a68bdf4ce38c
6f64229625b2961e9e706e69767702c7527bce533b1ebe963bd
:SYSTem:OPTion:INSTall DHO900-BW15T25@8bd798ba1bd51cdbee7792d403cf4f8e60a7d9802a
aa6f5315498d25ffe5bae906e69767702c7527bce533b1ebe963bd
Generated option commands saved to the file: 'SCPI_commands_generated.txt'
Please, send generated :SYSTem:OPTion:INSTall commands to the scope via the SCPI
interface, and press any key to check for the new *.lic files.
Options are installed without scope reboot.
Press any key to continue . . .
Here you can find all *.lic files of options already installed:
total 680
-rwxrwxrwx 1 system system 148 2013-01-18 08:55 Key.data
-rwxrwxrwx 1 system system 1876 2013-01-18 08:51 cal_adc.hex
-rwxrwxrwx 1 system system 348 2023-11-06 20:08 cal_afe_bandwidth.hex
-rwxrwxrwx 1 system system 348 2013-01-18 08:52 cal_afe_zero.hex
-rwxrwxrwx 1 system system 96372 2013-01-18 08:58 cal_afg.hex
-rwxrwxrwx 1 system system 76 2013-01-18 09:09 cal_ddr.hex
-rwxrwxrwx 1 system system 36 2013-01-18 09:12 cal_la.hex
-rwxrwxrwx 1 system system 156 2013-01-18 08:58 cal_lsb.hex
-rwxrwxrwx 1 system system 205084 2013-01-18 09:07 cal_vertical.hex
drwxrwxrwx 2 root root 4096 2023-06-02 14:16 default
drwxrwxrwx 2 root root 4096 2013-01-18 16:50 probe
-rwxrwxrwx 1 shell shell 220 2023-10-28 22:12 vendor.bin
Press any key to continue . . .
You mentioned that you corrected some mistakes in the original instructions. I assume that the one I d/l'd is the corrected version, right?
Regards,
Stan
There doesn't seem much point in generating keys on a 900-series.
It's far easier to just change the DHO914 vendor.bin to a DHO924 vendor.bin, eg. use the one in post #5 of this thread.
nb. You need keys for a DHO800 because it's the only way to get the memory upgrade.
The problem with changing the vendor.bin file is that unless it's from a 924S, you lose the AWG and the Bode plot functionality (I've already tried that).
A minor issue is that the serial number is changed as well. Not really a huge deal, but I'd like to make the upgrade as "clean" as possible, and the license keygen seems to be the better way to do that.
Regards,
Stan
The problem with changing the vendor.bin file is that unless it's from a 924S, you lose the AWG and the Bode plot functionality (I've already tried that).
can someone identify these parts? they are missing in dho800... b,c,d,e. especially d,e please...
Here you can find all *.lic files of options already installed:
.....
Regards,
Stan
As you can see, there is no *.lic files in the file listing at the end. Did you send command:
"
:SYSTem:OPTion:INSTall DHO900-BW15T25@8bd798ba1bd51cdbee7792d403cf4f8e60a7d9802aaa6f5315498d25ffe5bae906e69767702c7527bce533b1ebe963bd
"
through the SCPI page to the scope.
I've seen BW15T25 command working on DHO914 model earlier in this thread, as far as I remember. (see
https://www.eevblog.com/forum/testgear/hacking-the-rigol-dho800900-scope/msg5147868/?topicseen#msg5147868)
can someone identify these parts? they are missing in dho800... b,c,d,e. especially d,e please...
From the locations on the PCB I'd guess they're something to do with power for the AWG daughterboard.
I'm not sure what went wrong with my previous upgrade attempts, because I sent the identical string, but I tried it again after power cycling the DHO914S and it worked!
Unlike the other Rigol scopes I have, the BW upgrade doesn't show up as an option in the options list, but does show "Max BW:250M" in the "About" section.
Thanks to all who had the patience to help me with this!
I'm not sure what went wrong with my previous upgrade attempts, because I sent the identical string, but I tried it again after power cycling the DHO914S and it worked!
The problem was in the extra symbol you'd copied from the terminal window. There should be no extra spaces or carriage return symbols, but your original message has "enter" symbols at the 80 symbols mark.
That's why the script is writing commands to the file.
Copy the commands from the file "SCPI_commands_generated.txt".
The a,b,c is related to the logic analyzer most probably (a- power, b-c setting the threshold level?), the d,e with the AWG.
I'm not sure what went wrong with my previous upgrade attempts, because I sent the identical string, but I tried it again after power cycling the DHO914S and it worked!
Unlike the other Rigol scopes I have, the BW upgrade doesn't show up as an option in the options list, but does show "Max BW:250M" in the "About" section.
Thanks to all who had the patience to help me with this!
Hi, I order a 914s from China and it is on the way. Can you post steps to upgrade to 924s in detail?
Here again a comparison between the original 70Mhz version and now, the "unleashed" version, which has 200Mhz bandwidth (although you can only hack on 100Mhz and only 100Mhz are displayed, maybe the reason why after the last firmware update the bandwidth option is no longer displayed).
As noted earlier: The "70MHz" version of the DHO800 has 125MHz measured bandwidth.
I think Rigol's marketing department is under-labelling the DHO800 to fool people into buying the DHO900.
(Which makes perfect sense - they probably make 3x profit in return for a $1 edge connector!)
is 250MHz BW now enabled in DHO800? how about AFG and LA capability? any news?