Author Topic: Rigol MSO5000: Observation / Issue with statistics module  (Read 504 times)

0 Members and 1 Guest are viewing this topic.

Offline passenger54321Topic starter

  • Newbie
  • Posts: 5
  • Country: de
Rigol MSO5000: Observation / Issue with statistics module
« on: November 05, 2024, 10:25:58 am »
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.

Is this behaviour known and understood? Any workaround available?
Thanks for taking the time to look into the topic.
-Ulrich
 

Online thm_w

  • Super Contributor
  • ***
  • Posts: 9185
  • Country: ca
  • Non-expert
Re: Rigol MSO5000: Observation / Issue with statistics module
« Reply #1 on: November 05, 2024, 09:12:28 pm »
The bug thread is here: https://www.eevblog.com/forum/testgear/review-rigol-mso5000-tests-bugs-questions/
Though I don't see anything related to what you are talking about.

Have you tried calling Measure:Clear?
Presumably the workaround would be to read Vrms every trigger, run that ten times, and average the result?
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 
The following users thanked this post: tautech, passenger54321


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf