there's a section in the code called "Change the data" which is completely commented out.
I didn't realized that i should decoment first
is clear that without consistent modifications at main app, it cannot be used too much.
Try cursors. One knob should do horizontal setting and the other vertical
Thank you, but believe me I have checked all contexts as I said. Both knobs have vertical and horizontal functions in different contexts. I have checked all functions many times.Switched from automatic to manual and back, etc.
The best method to check is to use integrated routine from Self Check->Key test. In attached pic you can see that this knob(1) don't take any value, while the others have values each other.
Fun part: Yesterday I have filled a request for assistance at Rigol, but soon after that the knob started to work. I didn't received yet an answer from Rigol.
Could you post the screen with HW/FW versions ?
My scope works like a charm encoders wise, they do no skip a bit even if i rotate them very fast, so in your case it could be a bad soldering or damaged device.
Ok, now i'm messing with the fan speed as suggested by markone. My scope is running in a cool basement so what would be a practical pwm value for the fan in this case?
They are running at full speed.
They are running at full speed.
Thanks. It's a bit disappointing that Rigol have not improved this so far. How annoying do yo ufind the fan noise?
Did anyone come across details about changing the PWM settings via some Android hack? (Is it even confirmed that the fans are PWM-driven? How do we know if they are always on at full speed?)
How annoying do yo ufind the fan noise?
Did anyone come across details about changing the PWM settings via some Android hack? (Is it even confirmed that the fans are PWM-driven? How do we know if they are always on at full speed?)
How annoying do yo ufind the fan noise?
That's a very subjective question, of course. Personally, I don't find it to be a problem with mine (although to be fair, I've only run it ~ 1 hour so far, more to come this weekend if there is time).
The DHO800 fan is noisy, for sure, but for some reason I don't find it too annoying. Not sure why.
They are running at full speed.
Thanks. It's a bit disappointing that Rigol have not improved this so far. How annoying do yo ufind the fan noise?
Did anyone come across details about changing the PWM settings via some Android hack? (Is it even confirmed that the fans are PWM-driven? How do we know if they are always on at full speed?)
In this thread I remember Markone has find a setting for lowering the speed. You can try the following command: echo 100> /sys/devices/platform/pwm_fan/hwmon/hwmon5/pwm1 where echo can have values from 50...255. It will lower the fan but not at 0 speed. at 50 it is barelly audible but some of the chips temp increase to 72 degree C (from 64) (it has a hw monitor in board test section).
The readme.txt file in the FPGA folder has this content: [...]
I ran it through a translator:Code: [Select]FPGA bit file description
[...]
HDO2000/1000-FPGA-A100T
bit1 SPU_H12S2_SelfTest.bit Complete chip and board level self-test; including DDR calibration parameter readback.
bit2 SPU_H12S2.bit Regular oscilloscope program, no Bode map function
bit3 SPU_H12S2_bode.bit Bode function version, no high resolution
[...]
I have tried updating the code to use the BW100T20 option and then also modified the device id to be HDO1104 instead of HDO1072, but none of the generated licenses are accepted when using these permutations. The licenses created using the BW100T20 option don't seem to do anything at all (scope doesn't even give an error message), while the ones for BW7T20 at least give a message about "invalid license".
So I just received my DHO1104 and am attempting to use the rgtool1000 code to upgrade it. Of course the code is setup to generate licenses for the BW7T20 and RLU options, but since my model is already enabled for 100MHz, the BW upgrade license is reported as invalid (RLU works fine though).
I have tried updating the code to use the BW100T20 option and then also modified the device id to be HDO1104 instead of HDO1072, but none of the generated licenses are accepted when using these permutations. The licenses created using the BW100T20 option don't seem to do anything at all (scope doesn't even give an error message), while the ones for BW7T20 at least give a message about "invalid license".
Any thoughts on how to debug this further? I'm not sure who found the list of options, but is it possible to double check what the correct option for going from 100->200MHz BW would be?
Thanks very much...
Thanks. The changes that you made to the code is exactly what I had tried already unsuccessfully.
Today I tried again after leaving the scope off for the evening yesterday, and it worked now. So I suspect there is some kind of silent lockout feature to prevent generation attempts on the license (which makes total sense).
Thanks. The changes that you made to the code is exactly what I had tried already unsuccessfully.
Today I tried again after leaving the scope off for the evening yesterday, and it worked now. So I suspect there is some kind of silent lockout feature to prevent generation attempts on the license (which makes total sense).
I don't think so. The rigol1000 file didn't work for me either.