The built-in arbitrary waveform generator doesn't seem to contain any built-in (or pre-recorded) "standard" arbitrary waveforms. Moreover, I cannot find any method to convert a stored waveform file from the oscilloscope section (.CSV or .bin) into a waveform that would be compatible with the built-in AWG (.ARB). So apparently there's no simple way to play back a waveform that had been previously recorded with the scope. That's even possible by directly connecting one of Rigol's "Legacy" Scopes to any of their AWGs via a direct USB link!
I more and more get the impression that those folks who buy this product in two year's time will be quite happy campers...
Rigol DHO800 Aliasing effectIt's not a bug, but could be fixed. Press "Default", use 12.5 MHz (or 25, 20, 10, 5 MHz), 1k memory depth, increase the timebase until aliasing appears. Firmware version 1.00.
https://youtu.be/D_kHEUk-zKo
Please stop double posting. Thank you!
I ran several test with the threshold voltage and found that it is the threshold voltage scale issue. If I set the probe to X1 scale then everything works fine but with the X10 probe scale does not work because the actual threshold voltage 10 times less than I set. But if I increase the threshold voltage 10 times (10V instead of 1V) then decoding starts again.
Yep. I received my 'scope today and serial decoding only works when the probes are set to 1x.
Edit: This is NOT fixed in the 1.01 firmware.
Two bugs I found in the web interface:
1) When you open the web control it gives you a 1280x800 display as if it's for the DHO1000/DHO4000. The means image is stretched and blurred.
2) The window is the wrong size for the image - it's off by a pixel and that makes the scroll bars appear. Really annoying.
Also a peeve: When you take a snapshot could it be in lossless PNG format instead of JPG to preserve detail?
Can this be a "suggestions for Rigol" thread as well?
Rigol DHO800 waveform update freezing bugThis bug occurs at a horizontal scale of 200 ms per division and above, when you set the trigger position to the time before the capture starts.
Setting the trigger some time before the capture is used widely to debug large signal sequences. By moving the trigger position, you can study the whole signal in small portions.
Firmware version 1.00
https://youtu.be/FyM5jibkgfE
Can this be a "suggestions for Rigol" thread as well?
I'm sure that many operators would have a problem with the two-color button display due to vision issues: the check mark is more obvious.
As an app dev in the past, I think a toggle switch more preferable at nowadays UIs, and the checkbox is already a relic.
But anyway I totally agree those OFF/ON looks so-so.
BTW, this style of slider looks like "slide left to enable" (the upper one) and "slide right to disable" (the lower one). This could be confusing.
I'd put "ON" to the left but that's just me.
As well as many others. But oh why didn’t I thank Serg65536's post?
What about this? A fine example of "when you only have a hammer"?
Nothing complicated, just need to refine the labels
Ans in that SelfCal section, the toggles also could be used without any problems.
I'd put "ON" to the left but that's just me.
As well as many others. But oh why didn’t I thank Serg65536's post?
Answered in the other thread...
Don't know if anyone observed this yet: F/W 00.01.01.00.02 -- Channel 3 not working in horizontal roll mode!
Edit: Strange, now that I cold started the scope (and I mean really cold, after ~20hrs of pause), CH3 roll mode works again. I'll let the scope warm up and re-check, since it was pretty "steaming" hot when I observed the problem. This smell from the thing is abominating...
There's an option in Setup to make the horizontal timebase knob do a "zoom". This option isn't remembered when you power-off the 'scope.
PS: I think "Zoom" should be the default for this knob. It's what people expect and "fine" is much less useful.
People are probably going to use pinch-zoom for "fine" adjustments anyway.
1) After taping "save" at the "storage" window with *.wfm format (it's available if "memory" is selected), the file is not saved, and the scope won't run again.
2) The "overlay" option should be named "overwrite", as the industry standard suggests.
The operator "AX+B" should be named "kA+c", because in other operators A and B are input channels, but here A and B are constants, and X is the channel.
DHO924S arrived yesterday.
I can't get SPI decode to work at all on digital channels. Upgraded firmware to to 00.01.01, same thing (but at least the location of the analogue probe X10 setting is far more obvious).
The decoder seems to be fixed to the analogue channels whether you try changing them to the digital channels or not.
(Attachment Link)
The operator "AX+B" should be named "kA+c", because in other operators A and B are input channels, but here A and B are constants, and X is the channel.
Ax+B is industry standard name for that function. With uppercase A and B and lower case x
Ax+B is industry standard name for that function. With uppercase A and B and lower case x
Please, check other operators on the DHO800 (A+B, A-B, A||B, etc.): all other operators show A and B as actual captured waveforms, but in the operator "AX+B" letters A and B represent the numeric constants.
So, to prevent confusion, either the mentioned operator should be renamed, or all the other.
PS: I would prefer mathematical conventions: "x y" - for the waveforms, and "a b c" - for the constants.
That's normal behavior for all oscilloscopes. It's due to the input amp overload. You need to remove input circuitry overload, to see the undistorted signal.
) I've found on youtube
