Products > Test Equipment
New Rigol HDO1000 12-bit DSO - BUGs
joeyjoejoe:
I think a bug - Every time I power up, the attenuation on my probes is set to 1X and I have to set it again. I have not seen any options to save this setting between power cycles. DHO1074
thm_w:
--- Quote from: joeyjoejoe on December 14, 2023, 02:47:00 pm ---I think a bug - Every time I power up, the attenuation on my probes is set to 1X and I have to set it again. I have not seen any options to save this setting between power cycles. DHO1074
--- End quote ---
Tap the date in the bottom right corner -> Setup -> Load last = Last
gburdzin:
--- Quote from: thm_w on December 14, 2023, 11:46:25 pm ---
--- Quote from: joeyjoejoe on December 14, 2023, 02:47:00 pm ---I think a bug - Every time I power up, the attenuation on my probes is set to 1X and I have to set it again. I have not seen any options to save this setting between power cycles. DHO1074
--- End quote ---
Tap the date in the bottom right corner -> Setup -> Load last = Last
--- End quote ---
A couple of things that I noticed were not saved by selecting the "Last" setting.
1. Screen Brightness - I set it to 50% and it always goes back to 100% on bootup
2. External 10MHz Reference - I have to turn it on each time the scope is booted
Fungus:
--- Quote from: gburdzin on December 15, 2023, 12:01:11 pm ---1. Screen Brightness - I set it to 50% and it always goes back to 100% on bootup
--- End quote ---
The DHO800 is the same. Try setting the trace intensity to 100% then reboot twice...
the Chris:
There seems to be a bug in the statistics feature for the DEViation figure when choosing larger than 1k counts, at least for the rise time measurements.
I just wanted to verify a bandwidth upgrade on my DHO1074 with FW 00.02.12 when I saw that the deviation figure for the risetime measurement statistics with 10k counts maximum was very solid while the number of measurements was counting up, but the dev figure started to rise continuously without a cause once the 10k were reached. I could replicate the error several times, at least with 10k, but I assume any number higher than default is affected or the effect is more pronounced the higher the maximum count is set (kind of a hardcoded 1k count in the calculation once the limit is reached).
So better to either stick to 1k or go with 100k to be on the safe side and take the reading as long as it is below 100k.
EDIT: set it to 100k, door bell rang, came back about 10min later with counter at ~15k and DEV was at 0.000. So there is some other bug as well :-\
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version