“Text List” |
Name of the text list where the alarm message text is saved (see below: “Message”). CODESYS generates the list automatically when you create an alarm group. You can also select an existing text list here. |
“Archiving” |
Selection of the alarm storage object for the alarm group. Alarm storage is automatically activated when an alarm storage object is specified. |
“Deactivation” |
Boolean variable that deactivates all alarms in this group. These alarms are not triggered, even if the alarm condition is fulfilled. Alarms that are already active are not affected. |
Enter the properties of the individual alarms in the corresponding columns of the table. Depending on the selected observation type, input fields for additional required parameters are available below the table. |
||
“ID” |
Unique ID which corresponds to an ID in the associated text list You can change the ID in the ID field of the table. The ID must always be unique within the alarm group. Note: A change of the ID in the alarm table also directly causes a change in the text list, and the other way around. |
|
“Observation Type” |
List box of observation types. Depending on the type, different editing fields are available below the table that define the condition for the alarm. The fields define an expression that triggers the alarm. See the following table. |
|
“Details” |
Configuration settings for the selected alarm type made in the fields below the table. You can also specify the condition directly into the field. If you input an expression that does not match the currently selected observation type, the type is automatically adapted. |
|
“Deactivation” |
Optional Variable for deactivating the alarm. |
|
“Class” |
Assigned alarm class. |
|
“Message” |
Required Entry of a message text (message) with placeholder and line break. When an alarm is triggered, this message is displayed in the Alarm Table visualization element. The text entered here is automatically entered in the text list of the alarm group. Line breaks can be inserted by pressing [Ctrl]+[Enter]. Hint: You can expand the text with the information recorded in the latch variables. The following placeholders are supported. They are replaced by the actual value at runtime. |
|
|
Date of the change to the present status. |
|
|
Time of the last status change. |
|
|
Priority of the alarm (defined in the alarm class). |
|
|
Value that caused the alarm condition to become true. |
|
|
Alarm ID as displayed in the first column of the alarm table. |
|
|
Name of the alarm class (defined in the alarm). |
|
|
Complete information about the alarm is output. |
|
|
Actual value of the monitored variable. |
|
|
Value of the first latch variable at the time when the alarm was triggered. Note: You can also use more than two latch variables. To do this, insert additional columns from the context menu. |
|
|
Value of the second latch variable at the time when the alarm was triggered. |
|
|
|
|
|
Alarm status: 0 = "normal" 1 = "active" 2 = "waiting for ACK" 3 = "active, acknowledged" |
|
* For Example: " By default, only one column is available for message text. You can add more columns from the context menu which will be available in the “Data type” property for column configuration of the “Alarm Table” and “Alarm Banner” visualization elements. |
||
“Min. Pend. Time”: |
Defines the minimum duration for fulfilling the alarm condition so that the alarm is triggered. This can be used to suppress alarm conditions which occur for only a short time. Example: t#2ms Format according to IEC 6-1131 |
|
“Latch var 1”, “Latch var 2” |
Variable with scalar type (8 bytes), STRING or WSTRING Latch variables are used to record additional values when an alarm is active. This makes it possible to provide additional information about the alarm. For example, when monitoring a motor speed, the temperature and the current are also recorded. By default, columns are available for two latch variables. You can add more columns from the context menu which will be available in the Data type property for column configuration of the Alarm Table and Alarm Banner visualization elements. Hint: You can configure the alarm visualization so that displayed alarms are filtered by the contents of the latch variables. |
|
“Higher prio. alarm” |
When the alarm is triggered, it can be acknowledged by triggering another alarm. Example: A temperature monitor should issue a warning at > 60 °C and an error at > 90 °C. If the temperature rises, then the warning is displayed starting at 60 °C. As of 90° C, the alarm is triggered for the error. This alarm automatically acknowledges the 60° warning. |
MESSAGES ARE NOT SAVED AS A COPY IN THE HISTORY
MESSAGES ARE NOT SAVED AS A COPY IN THE HISTORY
Effect: If you make a small change to a message (for example, correcting a typing error), then this change has an effect on the history because the corrected message is now displayed there. However, if you completely reconfigure the alarm (change status or condition and update the message), then all previous alarms which were recorded due to the outdated configuration will get the new message in the history. Check on a case-by-case basis whether it is not better to add a new alarm instead of upgrading the outdated alarm.
“Digital”: |
“Expression”: Expression to be observed. On the right side, the expression for the comparison.
In the middle, you select the desired comparison operator (“=” or |
“Upper limit”: |
“Expression”: As described for “Digital”, but with the compare options “>” or |
“Lower limit”: |
“Expression”: As described for “Digital”, but with the compare options “<” or |
“Inside range”: |
“Expression”: Expression to be observed. “Range”: The alarm is triggered when the monitored expression is within the range defined here. The left field defines an expression for the lower limit of this range. The right field defines an expression for the upper limit. The expression to be monitored is displayed in the field in-between. You have to set the comparison operators accordingly. You can define a “Hysteresis in %” optionally. |
“Outside range”: |
“Expression”: Expression to be observed. “Range”: The alarm is triggered when the monitored expression is outside the range defined here. The left field defines an expression for the lower limit of this range. The right field defines an expression for the upper limit. The expression to be monitored is displayed in the field in-between. You have to set the comparison operators accordingly. You can define a “Hysteresis in %” optionally. |
“Change”: |
“Expression”: Expression to be observed. The alarm is triggered when its value changes. |
“Event”: |
In this case, the application triggers the alarm (event alarm) by using functions
from the library |
For this observation type, you can monitor the specified expression as absolute or relative. Absolute means that the limit value is defined by a fixed value or a variable that returns a fixed value. Relative means that the limit value depends on an expression; for example: upper limit: “Variable x >= 0.9 * y”. “Hysteresis in %”: When you specify a hysteresis, the alarm condition is fulfilled until a certain deviation from the specified limit value is reached. The size of the deviation is specified as a percentage [%] of the limit value. Example: Upper limit: |
The context menu includes the following commands for adding and removing additional columns for messages and latch variables:
-
“Add message column”
-
“Remove message column”
-
“Add latch var column”
-
“Remove latch var column”
Multiple selected rows in the table can be edited at the same time by means of the context menu.