Looks like the issue is with the statistics. The Δt keeps resetting to zero, resetting the 'high', low' & 'average' to zero, thus causing the values to switch from 3 or 2 digits to one. Then the right justified formatting makes adjustments to the position of the bar graph.

This is a small and not always reproducible "error" in the Aquasuite.
I have observed this phenomenon several times when I want to generate a new maximum value in the Playground, i.e. when I take the output of the virtual sensor as an input again and forward the maximum value between the current value and the formerly max. value to the output.



When I create this (respectively a new) virtual sensor, the output (in the above case: 60,75°C) sometimes fluctuated between the maximum value (60,75°C) and the current value (45,50°C). After a restart, however, everything is as it should be and this phenomenon never occurs again (for this new virtual sensor)

The statistics evaluation stored in the Aquasuite will have a similar structure to my virtual Sensor (maximum value) described above and your "jumping" from Zero to the max./min. and average should not be there anymore after a restart of the PC or Aquasuite and AS Service.


In my opinion, this has something to do with the update rate (one second?) of the inputs and intermediate storage of the values as well as the time needed for processing the logic for the values.
The evaluation of the data sometimes hiccups a little, but this calms down after a restart (at least for me).

if you set the time to 0, you don't need statistics, that's no problem.

Zitat von »sebastian«

if you set the time to 0, you don't need statistics, that's no problem.

Oh... that make sense (I did not see the "0s")
However, my described problem still occurs sporadically (with the virtual sensors)

Zitat von »sebastian«

if you set the time to 0, you don't need statistics, that's no problem.

Actually, that is a problem. If the time range is set to zero, 'high', 'low' & 'average' should all reflect the current value, not reset to zero... unless the current value is zero.

Zitat von »InfoSeeker«

If the time range is set to zero

disable the statistics data, this is useless with a zero timespan

Zitat von »sebastian«

disable the statistics data, this is useless with a zero timespan

Agreed, the function is useless with a zero time span, but shouldn't it return the correct value even if used in a 'useless' manner?

EDIT: The simplest solution is to not have zero be an option on the selection slider (stats.jpg)