Products > Test Equipment
REVIEW - Rigol MSO5000. Tests, bugs, questions
core:
I tried it myself, with the internal generator but also with an external generator.
I tried different waveforms, amplitude and DC offset.
The results are the same, below 20 degrees the errors are getting bigger and bigger.
Below about 7 degrees it doesn't decrease regardless of the settings.
Doesn't inspire much confidence.
passenger54321:
Hi,
When trying to script for the statistics mode of my MSO5074, I ran into the following observation.
User issue or bug?
The goal is reading the noise level (Vrms) statistics for the different vertical ranges.
For completeness, I am using the following SCPI command which is not listed in the programming manual.
Not sure though if it is hidden for a reason
Setting the moving average window (in display: Measure -> Statistics -> Counter)
:MEASure:STATISTIC:COUNT
range probably [10..100000]
This one exists once for all up to 10 ITEMs
So, I am setting :MEASure:STATISTIC:COUNT to 10.
The issue I am observing is that the reset does not completely reset for larger time base settings e.g. 1 sec / div.
So after a
:MEASURE:STATISTIC:RESET
I am waiting until
:Measure:Statistic:Item? Cnt, VRMS
reaches the value of above COUNT, so I know the window is full.
(and yes, the Cnt comes back as a scientific E-notation float, but should be int. And this is not my main issue)
While waiting, I can see on the display that the first [1..5] values in the statistics box are still from the previous
measurement (from before the reset). The # is somewhat random; mostly 1
So, when next calling
:Measure:Statistic:Item? AVerages, VRMS
the average is wrong.
After every measurement cycle, I am completely erasing the measurement ITEMs like this:
:Measure:Statistic:Display OFF
:Measure:Clear ALL
:Channel' + str(active_channel) +':Display OFF
Is this behaviour known and understood? Any workaround available?
Thanks for taking the time to look into the topic.
And thanks to thm_w. As suggested, I am moving the entry to this topic
-Ulrich
P.S. with regards to
Presumably the workaround would be to read Vrms every trigger, run that ten times, and average the result?
-> Yes, this was my first approach. But, runtime.... I stopped it after three days, and still not complete. So, saw the statistics are much faster.
Next try would be to make statistic from RMS and RMS from the waveform reading. Howerver this is another issue, let me investigate it before I post nonsense.
Bill3745:
Has anyone verified the amplitude flatness of their built-in AWGs? The spec states +/- 0.5 db from a 1 KHz reference, but mine drops closer to 1 db when cranked all the way up to 25 MHz. Both 50 Ohm (properly terminated) and HighZ were tested with similar results, although it seems to do slightly better on HighZ. I ruled out cable, terminator and scope by running a similar test with a known good external AWG.
Scope is a 5074 purchased in late '21 running on current 1.03.03 unpatched firmware.
sorenkir:
Hi,
I have checked generator 1 on my MSO5074.
The graph is below.
G1 @ 1Vpp, 50 ohm cable and termination, measured with a HP3403C.
Michel.
Bill3745:
--- Quote from: sorenkir on December 11, 2024, 04:22:17 pm ---Hi,
I have checked generator 1 on my MSO5074.
The graph is below.
G1 @ 1Vpp, 50 ohm cable and termination, measured with a HP3403C.
Michel.
--- End quote ---
Thanks so much. Roll off looks fairly similar to what I am seeing and not to the spec of +/-0.5 db. Not a big deal as I wasn't expecting a ton of accuracy from the built in AWGs, but annoying that it doesn't meet their published spec. Really just wanted to see if my unit was an anomaly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version