After power is restored or after the HS/FS is restarted, the data saved under Retentively saved data is available again. The non-volatile memory is contained in the HS/FS under the term retentive memory.
1.Retentively saved data
The following data is permanently saved in the retentive memory:
- Programming of the HS (Menu, Visualisation, Query, Sequences, Logic, etc.)
- EIB communication objects (with retentive marking)
- Internal communication objects (with retentive marking)
- Universal timers with settings
- Public holiday calendar with settings
- Scenes
- Occupancy simulation
- Holiday calendar with settings
- Archives
- Message archives
- Login protocol
- EIB Monitor
- Logic: Elapsed operating time meter
- Logic: Meters and more ...
- Logic: Retentive memory
- Logic: all modules marked as retentive
- Image archive in HS
- External switching lists
In addition, all data which can be edited by the user in the QuadClient are retentively saved:
- Self-entered user password
- Administrator password
- Timers
- Favourites configuration
- Plug-in/quadrant configuration
- Changes to the URLs in the URL input screens of Menu, MyTouch and the Navigation button
2.Saving periods
Every 15 minutes the HS/FS automatically transfers all of the data listed above to retentive memory, as long as something has changed. This 15-minute span is also called a saving cycle.
All data about this topic can be found on the debug page under the point "Retentive memory".
There are also status objects which provide information on the topic:
All data about this topic can be found on the debug page under the point "Retentive memory".
There are also status objects which provide information on the topic:
Important
All data changes are not transferred to the retentive data until after the next saving cycle, and they are not permanently saved until then!
Note
If restarting the HS/FS is triggered via the "Transfer -> Restart only" Expert function or the command "Restart device", there is always additional saving to the retentive memory directly BEFORE shutting down the HS/FS. This is notthe case if restarting is triggered by a power failure or switching the HS/FS on or off.
Note
Should a reboot (e.g. due to a power failure) be carried out before the last saving of the data, then the data which was created in this period is lost!!!
Note
All retentive data is immediately saved again permanently before programming (during the transfer).
3.Memory spaces
There are 2 memory spaces (0 and 1) for 2 copies of the retentively saved data. These are then written in the saving cycle. If the HS/FS is restarted, the memory space with the latest data is always read out.
The Debug page lists which of the two memory spaces was the last to be written and which memory space was read last.
The Debug page lists which of the two memory spaces was the last to be written and which memory space was read last.
4.Cut-off
Data compression methods are used in the HS/FS. Compression varies depending on characteristics of the data. Therefore, an exact size of the required memory capacity cannot be determined when creating the project.
Therefore, due to the filling of archives, particularly camera archives, there may not be enough memory capacity available for automatic saving. In this case, the HS/FS tries to make space.
The method for making space to save retentive data is to remove images from the camera archives.
Per saving cycle, the HS/FS makes up to five consecutive attempts to obtain enough free space by freeing up 10% of the space currently occupied by camera images in the camera archives: Camera images are deleted until the space occupied by camera images has been reduced to a maximum of 90% of its size. In doing so, the status CO Cleanings (number) is increased each time.
If this method does not successfully make enough free space, an error is shown on the debug page and the HS/FS attempts the entire process again during the next saving cycle. This continues until there is enough space for saving.
Therefore, due to the filling of archives, particularly camera archives, there may not be enough memory capacity available for automatic saving. In this case, the HS/FS tries to make space.
The method for making space to save retentive data is to remove images from the camera archives.
Per saving cycle, the HS/FS makes up to five consecutive attempts to obtain enough free space by freeing up 10% of the space currently occupied by camera images in the camera archives: Camera images are deleted until the space occupied by camera images has been reduced to a maximum of 90% of its size. In doing so, the status CO Cleanings (number) is increased each time.
If this method does not successfully make enough free space, an error is shown on the debug page and the HS/FS attempts the entire process again during the next saving cycle. This continues until there is enough space for saving.
Note
During cut-off, the oldest images are always deleted first.
Important
Retentive data cannot be saved successfully if the same number of camera images are saved in the camera archives (or large amounts of data in other archives) in the time period until retentive data is saved again as the HS/FS deleted during the last cut-off!
Note
There is an option of keeping an eye on this issue by monitoring the CO Cleanings (number) by setting up an alert (e-mail, text message, phone, push notification) for this purpose.
5.Other topics
The retentive memory can be deleted in the program item Transfer.
The retentive memory can be backed up in the program item Main mask/HS/FS/Back up retentive data.
The retentive memory can be restored in the program item Main mask/HS/FS/Upload retentive data.
The retentive memory can be saved externally and read in via FTP.
The retentive memory can be backed up in the program item Main mask/HS/FS/Back up retentive data.
The retentive memory can be restored in the program item Main mask/HS/FS/Upload retentive data.
The retentive memory can be saved externally and read in via FTP.