Using CitectSCADA > Configuring Your System > Alarm Configuration

Alarm Configuration

The Alarm Configuration page will only be displayed if this machine is configured as an Alarm Server in the Project Editor.

CitectSCADA has several options available for alarm processing. These are set in the Alarm section of the Citect.ini file. Refer to the Parameters help for information on these parameters.



Alarm scan time

Determines the rate at which alarms are scanned and processed. A value of 500 (the default value) indicates that CitectSCADA tries to process the alarms every 500 ms. However, if CitectSCADA cannot read the alarm data from the I/O Device within 500 ms, the alarms are processed at a slower rate. For example, if it takes 800 ms to read the alarm data from the I/O Device, CitectSCADA processes the alarms every 800 ms.

If you select a larger value for the alarm scan time, the alarms server uses less CPU (because it does not need to process the alarm records as often). The amount of data read from the I/O Device is also reduced, so that other processes (Trends, Reports, and the current page) get their I/O Device data more quickly. You can enter any value from 0 to 60000 (milliseconds).

Alarm save period

The period for saving alarm and event data (to disk). You can save alarm and event data periodically so that the data is restored after a planned or unplanned system shutdown. The smaller the period, the greater is the load on the system.

Summary length

The maximum number of alarm summary entries that can be held in memory. You can view these alarm summary entries on the alarm summary page. Each event requires approximately 300 bytes of memory, including the length of the comment. 10,000 events require 3 to 4 MB of memory. If you use many events, have enough memory to keep them in RAM.

Summary timeout

The length of time that alarm summary entries remain in the alarm summary queue.

Primary alarms server save path

The path to the primary save files. CitectSCADA uses two save files for each alarms server, ALMSAV.DAT and ALMINDEXSAVE.DAT. The save primary path is the directory where the primary alarms server creates its save files. When restoring the files, the most recent (of the primary and secondary) save files will be used.

Standby alarms server save path

The path to the secondary save files.

To minimize the chance of conflicts between alarm files used by multiple Alarm Servers from different clusters running on the same machine, the alarm files have a dynamic naming convention based on the following format:


See Also