Alarm saving

For each alarm group a file can be defined, in which the alarm events are stored, if (!) a 'Save' action has been assigned to the class in the alarm class configuration dialog.
Select the alarm group in the configuration tree and open the dialog tab 'Alarm saving':

Configuration dialog 'Alarm saving'

The following definitions are possible:

Filepath: Directories path of the file which is defined in Filename; via button "..." you get the standard dialog for selecting a directory.

Filename: Name of the file which should save the alarm events (e.g. "alarmlog"). Automatically a file will be created which gets the name defined here plus an attached digit and which has the extension ".alm". The digit indicates the version of the log-file. The first file gets a "0"; each further file, which will be created according to the defined File change event, will be numbered with 1, 2 etc. (Examples: "alarmlog0.alm", "alarmlog1.alm).

File change event: Define here the event which will cause the creation of a new file for alarm-saving. Possible entries: Never, after one Hour, after one Day, after one Week, after one Month, at a rising edge of the variable defined in field Triggervariable, when the number of records in the file as defined in Number of records gets exceeded.

Triggervariable resp. Number of records: see above, File change event.

Delete old files after .. Hours: Number of days since the day of creation, after which all alarm log-files except from the actual one should be deleted.

The log-file (History) contains the following entries:

(See the column types and exemplary entries for two alarms)

EXAMPLE: