Skip to main content

Object: Alarm Configuration

Symbol: _vis_icon_alarmconfiguration.png

The alarms are managed in the Alarm Configuration object.

When you insert the object, the following default objects are also inserted automatically:

  • Alarm class: Error

  • Alarm class: Info

  • Alarm class: Warning

  • Alarm storage: AlarmStorage

You can use these objects, but it is not required. You can delete them and replace them by objects that you add yourself.

Alarm instances

_vis_icon_alarmgrouptemplate.png

List with alarm instances

Variable

Function block instance or structure variable for which an alarm definition exists

Example: PLC_PRG.fb1Test

Alarm Group Template

Alarm group template (usually from a library)

Example: AGT_FB_1

Alarm Group

Alarm group in which the alarm instance is implicitly included.

Create

_visu_icon_checked_box.png: The alarms of this instance are created.

Button: Create or update alarm instances

If new IEC code has been created in the project and new instances have been added, then the alarm configuration requires an update. Click the button to create or update the alarm instances. Then IEC programming and alarm configuration match again.

If, for example, another library has been inserted or function block instances are created from this library without changing the alarm configuration, then the list of alarm instances needs to be updated.

Check alarm instances during compilation

_visu_icon_checked_box.png: Enabled by default

Automatically checks the list of alarm instances for completeness and correctness during compilation and issues a message. The alarm configuration then has to be updated by means of the Create or update alarm instances button.

It is checked whether or not all instances of function blocks and all variables of structures with AlarmGroupTemplate are covered.

No online change

After switching the option, it is no longer possible to log in without a change.

Settings

_cds_icon_application.png

Alarm Storage Task

Enable

_visu_icon_checked_box.png: The alarm evaluation is distributed to two tasks. The faster task (AlarmManagerTask object) is responsible for evaluating the alarm conditions. The slower task (alarm storage task) is responsible for saving the alarm information in the alarm database. When you select the option, the alarm storage task is created automatically. This task is not visible in the task configuration.

_visu_icon_unchecked.png: The alarm evaluation and the alarm storage are processed in one task (AlarmManagerTaskobject). This is the default setting for existing projects which were created before V4.6.0.0.

Task Interval

Task cycle time of the alarm storage task in ms (1..1000000)

Example: 2000

Note

Set a higher task cycle time and a lower priority for the alarm storage task than for the alarm manager task. The alarm storage task requires a slow frequency to execute file access to the alarm database.

Priority (0..31)

Priority of the alarm storage task

Example: 31

For more information, see: Distributing the Alarm Management to Two Tasks

Alarm history updates during runtime start

Change state of not normal alarms to normal

_visu_icon_checked_box.png: When the application is started, all alarms in the alarm history which are not in the "Normal" state are automatically assigned the "Normal" state.

_visu_icon_unchecked.png: The alarm state is retained when the application is started.

Assign missing inactive time stamps to runtime start

_visu_icon_checked_box.png: When the application is started, missing inactive time stamps are assigned the time of the application start.

_visu_icon_unchecked.png: The time stamp is retained when the application is started.

:
See also: