Thank you for the quick reply! I have looked again at the instructions and am sure I have followed to the letter. I expected the code generator to parse the "key.data" file and that it would be in English.
I ran from a user account on W10 that may not have user privileges. So I retried from the start using the administrator account but still returns in Chinese. I continued with the go batch file anyway but it complains about the key.data file. I also added the path of the go.bin folder and android folder to the system environment in W10. Still no luck
The key.data file contains binary data. Never mind what it looks like when (mis-)interpreted as a text file.
Where (in which folder) did you place the key.data file, and how many bytes does it comprise?
Thank you for your reply. internet here has been minimal today, the phone company working on the cabinet.
Binary data makes sense of course, Chinese characters distracted me normally see graphics characters. I am logged on as administrator. The location is C:program files/go/bin. I also tried C:/go/bin, to take it out of the protected windows folders incase it cant write the output file. The key file is 388 bytes long.
I am getting a different message now. I also changed the scope type in rgtool.go to DHO1074. I also tried adding a dot to make "rgtool.go."
CMD screen dump
C:\GO\bin>
C:\GO\bin>go run /rigol/data/Key.data
malformed import path "/rigol/data/Key.data": empty path element
Directory of C:\GO\bin
23/04/2024 13:53 <DIR> .
23/04/2024 13:53 <DIR> ..
29/03/2024 15:27 12,957,184 go.exe
29/03/2024 15:27 2,775,040 gofmt.exe
10/04/2024 21:41 388 Key.data
23/04/2024 13:51 4,311 rgtool.go..txt
4 File(s) 15,736,923 bytes
2 Dir(s) 339,143,364,608 bytes free
C:\GO\bin>
Thanks for sharing the commands you tried and the output. Looks like you are trying to execute the key.data file as a Go program -- that can't work. Instead, you need to execute rgtool.go, that's the program.
First, rename "rgtool.go..txt" to "rgtool.go". (Your text editor probably added the unwanted .txt extension when you edited the file.) Then enter the command "go run rgtool.go". Fingers crossed!
Edit: Just to make sure -- don't enter the quotation marks, of course. There is also no "." (period) at the end of the "rgtool.go" filename.
Thank you very much.
I did notice that windows does not display the file extension in the folder, but viewing the file properties the .txt extension can be seen. I could not remove the extension as windows had associated the file with notepad. however I tried to remove it, windows kept putting it back. Nor could I find a way to remove the file association with notepad.
Finally while staring at the CMD window I remembered the dos rename command so entered "rename rgtool.go.txt rgtool.go"
and I successfully managed to generate the two keys. I am very grateful for your help, thank you.
I have installed the keys and now enjoy the extra memory and bandwidth.
There are these two versions only, you can use both (12V): NF-A6x25 PWM ( 4wire, required wires: yellow/black )
NF-A6x25 FLX ( 3wire, required wires: red/black )
The scope has 2pin fan-connectors, no speed-signal.
I removed the noctua-plug + the stiff cable sleeve and crimped the matching plug (JST XH 2.54, 2pin) to the Noctua wires.
You can also solder the cable + connector from the stock fan, or searching for 3..4pin -> 2pin fan adapter cable...
My experiments with vendor.bin :
I assembled a generator on LTC6905 SOT-23-5 at ~60 MHZ (Rise time 0,5ns)
I put vendor.bin in DHO1072 scope for DHO4804, here's what happened:
The DHO4000 interleaves its 2 ADCs to achieve 4GS/s.
The DHO1000 has only one ADC. So every second sample is missing and the frequency appears to double. It is surprising that it works at all.
It would be more promising to experiment with the DHO2000 vendorl.bin.
The DHO4000 interleaves its 2 ADCs to achieve 4GS/s.
The DHO1000 has only one ADC. So every second sample is missing and the frequency appears to double. It is surprising that it works at all.
It would be more promising to experiment with the DHO2000 vendorl.bin.
I tried to put "DHO2000 vendorl.bin." (2404 and something like that) and the oscilloscope loaded and worked, but I did not find any profit. In the case of 4804, the 400 MHz band of the input path is unlocked and this is cool, although there are problems with the readings, but the time just needs to be multiplied by 2, and the frequency divided by two. It's a pity there is no working patch to unlock the bandwidth to 400MHz for the DHO1000...
I tried to put "DHO2000 vendorl.bin." (2404 and something like that) and the oscilloscope loaded and worked, but I did not find any profit. In the case of 4804, the 400 MHz band of the input path is unlocked and this is cool, although there are problems with the readings, but the time just needs to be multiplied by 2, and the frequency divided by two. It's a pity there is no working patch to unlock the bandwidth to 400MHz for the DHO1000...
What happens when you enable CH3? This may limit CH1 to 2GS and one ADC. (If this works at all with your 2 channel hardware.)
... In the case of 4804, the 400 MHz band of the input path is unlocked and this is cool, although there are problems with the readings, but the time just needs to be multiplied by 2, and the frequency divided by two. ...
Why 400 and not 800?
Did you measured?
You are probably right, the 800 MHz band
If we can trust the TinySA Ultra, ~43mVp-p is definitely more than 50mVp-p at the 0.7 level
(-22dBm = 50mVp-p)
I tried to put "DHO2000 vendorl.bin." (2404 and something like that) and the oscilloscope loaded and worked, but I did not find any profit. In the case of 4804, the 400 MHz band of the input path is unlocked and this is cool, although there are problems with the readings, but the time just needs to be multiplied by 2, and the frequency divided by two. It's a pity there is no working patch to unlock the bandwidth to 400MHz for the DHO1000...
What happens when you enable CH3? This may limit CH1 to 2GS and one ADC. (If this works at all with your 2 channel hardware.)
When activating any channel except CH1, the oscilloscope definitely does not work correctly. And judging by the shape of the signal, 2 Gs are reduced to 1Gs
And if I activate only CH3, the oscilloscope shows 2Gs (Really 1Gs) but the signal is not displayed. In order to receive a signal on the second channel, it is necessary to activate both CH2 and CH3, the oscilloscope shows 1Gs (actually works as 500Ms)
Folks,
I purchased a new DSO (DHO1074). I see the thread to be too lengthy to exactly find the steps to upgrade the bandwidth and memory depth.
Can someone please provide the most reliable procedure to be followed to unlock my scope?
Thanks!!