NOTICE
In case of a reset (origin), the alarm storage file is deleted.
In “Alarm Storage”, you define the settings for the database file where the occurring alarms are stored. You can insert the object only once below an alarm configuration.
There is exactly one memory file located in a database. This file is saved optionally in a file directory on the controller. You cannot change the name it is derived from the application name according to the following convention: <application name>.alarmstorage.sqlite. The alarm classes and alarm groups define whether or not the memory file should be used.
|
“Subdirectory:” |
Name of a subdirectory on the PLC where the memory file is saved (optional) |
|
“No limit” |
No limit for the file size for the alarm storage |
|
“Maximum number of records” |
Number of recorded entries When this number is reached, the oldest entry is deleted as soon as a new one is queued (ring buffer). |
|
“Maximum storage size” |
Maximum size of the memory file with specification of the unit. This size is implicitly converted into an approximate maximum number of entries which can be saved in the file (ring buffer). |
|
“Ring buffer” |
For display purposes only (not editable)
|
: Memory in a ring buffer
: Memory in an unlimited buffer
The records which are automatically saved in the database can be displayed in the “Alarm Table” visualization element.
-
Command: CSV Export of Alarm Storage
-
Dialog: Alarm Storage Export Configuration – Basic Settings
-
Dialog: Alarm Storage Export Configuration – Advanced Settings