RSS

Alarms and Change-Of-State

Once the variable that represents the alert condition and its associated message exist, an alert may be defined by two methods.

Screen editing method

Locate the alert variable. Click in the "A" column. Then select :

• 0 for FALSE = alert condition
• 1 for TRUE = alert condition
• E for EITHER (change of state)
• N for NO alert condition

The "E" directs any change of state of this variable to the change of state logger.

The "N" simply eliminates a previously defined alert condition for that variable.

ALERT command method

An alert condition may be defined or removed with the ALERT command. The format of the command is :

ALERT name state[cr]

name is the name of the variable to be associated with the alert condition
state is

• 0 for FALSE = alert condition
• 1 for TRUE = alert condition
• E for EITHER. This tags the variable for change of state recording.
• N for NO alert condition (to cancel a previously existing alert condition)

Alarm acknowledge

The command ACK name RTES32 locates and maintains these registers:

• ALARM$ - The quantity of alarms currently active
• ACK$ - The quantity of alarms currently active and acknowledged

RTES32 locates the following registers on startup and uses them:

• LOG$ defines an array of file names in the "Message" column where the alarm events are logged
• DLOGS$ is a swith to turn on and off the alarm events logging
• COS$ defines an array of file names in the "Message" column where the change of states are logged
• DCOS$ is a switch to turn on and off the change of states logging
• STATUS$ is an array of 16 registers that define in the "Message" column the status descriptors.