Back

Topic

[KB629]Why is a Dream Report statistical counter wrong?

Tags: Dream Report

12 years ago
By LM
Options
Print
Applies to:

PcVue all versions.
Dream Report all versions.


Symptom:

Sometimes, when using Dream Report, the statistical counter value is completely wrong. You get a large number instead of a short value.


Details:

This is due to the counter Quality, recorded in the PcVue archives, being other than 192 (good). Dream Report deduces from this that the counter has been reset. You will find below some examples of when this may occur and possible workarounds.

  • A null point is archived each time PcVue is closed. By default when you close the application, the database records either a null or 0 value and a quality of 64. With recent versions of PcVue, it is possible to disable this invalid point record on exit. Just select this option for each trend configuration.
    Invalid_point_on_exit
  • A zero point with a quality of 0 is archived if the variable is configured with the Simulated property set.
    Counter_simulated
  • The new minimum value is archived, with a quality of 24, if you change the minimum value.
    Counter_minimum_value
  • A null point (or minimum value), with a quality of 24 or 0, is archived if you change any other property of the counter.
    Counter_recorded

Dream Report workaround

When you define a statistical counter, select the advanced SQL condition and define it not to take into account qualities other than 192.

Dream_Report_counter

Advanced_SQL_condition

 


Created on: 17 Feb 2013 Last update: 13 May 2024