Introduction
Alarms can be generated by the operating system (RTE or system alarms) or by the user application (user alarms).
System alarms are standard (see list) and described within the system alarms file, while user alarms must be configured through the appropriate user alarms file.
Each alarm consists of: identification number, descriptive text, bit of one of the AM variables (is set to 1 if alarm is present) and any parameters that are displayed in the descriptive text.
If RPE is present some subsets of the RTE alarms are handled by it.
NOTE: Alarm Ascii strings have a maximum length of 63 bytes.
Related arguments
Categories of alarms
Based on their severity, alarms are divided into four categories:
Category |
System Alarms |
User alarms |
Description |
|---|---|---|---|
Major alarms
|
1÷999 AM(0)...AM(36)
|
1000÷1999 AM(37)...AM(40) |
They cause power drop in accordance with the Power Set. NOTE: Axis ones are those followed by # axis number am (1-:-32) bits 0 to 15. |
Minor alarms
|
2000÷2999 AM(41)...AM(44)
|
3000÷3999 AM(45)...AM(48) |
Causes set one bit in the predefined variable hold. NOTE: Axis ones are those followed by # axis number am(1-:-32) bits 16 to 31. |
Warnings |
9000÷9999 AM(49)...AM(52) |
4000÷8999 AM(53)...AM(63) |
Do not cause power drop |
|
|
|
10000-:-11999 |
They do not cause power drop. They are entered only in the alarms history |
Types of alarms
All alarms handled by RTE fall into one of these types:
Type |
Description |
|---|---|
memory |
Memory alarms |
autodia |
Alarms self-diagnosis |
axis |
Axis alarms |
language |
R3 alarms |
powerSet |
Alarms of power set |
extDev |
Alarms of external device |
Some alarms, having peculiarities compared with standard alarms, are handled differently. Such alarms are:
Axis alarms
Alarms that refer to an axis managed by the control.
Since they are not global alarms, but refer to a specific axis, both the identifying number and the axis that generated it are specified for such alarms.
The variables am (1-:-32) are reserved exclusively for axis alarms, in fact (1-:-32) indicates the axis number that generated the alarm.
Emergency
Emergency are error alarms sent to the control by the drives connected to it.
All emergency are considered axis alarms.
RTE can handle such alarms in a compact manner (generating generic alarms 19 and 81), or in an extended manner (generating alarms between 30 and 39, specific according to the drive used).
For configuration of Emergency alarms, see the chapter Alarms: settings in RTE configuration.
Messages
Alarms that are not entered in the alarm stack, but are entered only in the alarm history.
They do not cause a power drop.
They do not have a bit of one of the AM variables associated with.
They are generated through the AH_LOG instruction.
There are no messages generated by the operating system. It is up to the user to create the messages using the user alarm file.
Alarms with relevant parameters
Some alarms managed by RTE are considered "Parameters prominent alarms". These kinds of alarms are handled differently than others in terms of their entry into the alarm stack.
In order to enter the stack, the incoming alarm must have a different identification number from those already present, unless it has been declared to be of type ALARM_PAR_PROMINENT. In such a case, RTE also analyzes the parameters of the alarm and, in case one of them is different from the same alarm with previous relevant parameters, inserts it into the stack.
From the project configurator -> general -> alarms it is possible to enable/disable the checking of alarms with relevant parameters.
To know if a system alarm is of type PAR_PROMINENT see the documentation of the specific alarm.
NOTE: To declare a user alarm of type PAR_PROMINENT use bit 0x02000000 (AH_FILTER) in the user alarms file.
