Introduction

The default alarm stack is organized in FIFO (First In First Out) mode and has 32 levels.

This implies that the first verified alarm will always remain displayed in the initial position. In the event that more than 32 alarms occur, only the first 32 will remain in the stack.

The alarm is removed:

•By pressing the red ADV button located on the front panel of the CPU or on the bottom of the HI-DRIVE

•By using the adv_rq keyword

•Using the instruction alarm_reset

•From the Dispan/Vispan terminals

NOTE: You can change the working mode of the alarm stack by using LIFO (Last In First Out) mode by means of the predefined variable as_lifo.

User interaction with the alarms stack

The user has several possibilities to interact with the alarm stack:

•[from RDE shell] Via the ALS shell command or the D AL device command, it is possible to view the contents of the stack

•[from RDE shell] Via the ADV device command, an alarm reset command can be sent

•[from RDE shell and/or application] Various information can be obtained by querying the predefined variables al_stack_mask, al_pres, and ax_in_alarm

•[from application] Via the predefined variables aln, als and as_get_d, the levels of the alarm stack (1÷32) can be accessed

•[from application] Through the adv_rq variable it is possible to give a reset command

•[from application] Through the function alarm_set it is possible to generate an alarm

•[from application] Through the function alarm_set_us it is possible to generate an alarm with user string variable USV

•[from application] Via the alarm_reset function it is possible to reset an alarm present in the stack

•[from application] Via the function alarm_reset_par it is possible to reset an alarm present in the stack by also specifying the parameter

•[from application] Via the function alarm_reset_par_us it is possible to reset an alarm present in the stack by also specifying the user string parameter USV

•[from application] Through the function is_alarm_present it is possible to check the presence of an alarm in the stack

•[from application] Via the is_alarm_par_present function, it is possible to check for the presence of an alarm in the stack by also specifying the parameter

•[from application] Through the function is_alarm_par_present_us it is possible to check the presence of an alarm with USV user string parameters in the stack by also specifying the parameter