Recent history: Difference between revisions

488 bytes removed ,  12:45, 29 September 2022
m
Line 43: Line 43:
#* Cumulus uses current time, read from the computer, in its decision as to where to store each new recent history value set, so it can overwrite existing table rows, or array elements, if date-time matches one that already exists, such as in the hour after when clocks go back.
#* Cumulus uses current time, read from the computer, in its decision as to where to store each new recent history value set, so it can overwrite existing table rows, or array elements, if date-time matches one that already exists, such as in the hour after when clocks go back.


=Availability by Release=
The functionality was introduced from version 1.9.3 (beta build 1033 release 10 April 2012), in terms of working while the Cumulus software is running.
The functionality did not work before build 1098,in terms of initialising from archive records read from a station logger when Cumulus is restarted.
It is only from release 3.12.0, that values from a previous session of MX, are available to MX on restarting less that 7 days after previous session closed.


=How are recent history values stored?=
=How are recent history values stored?=