Alarm and event system Page 1 of 70

Alarm and event system

This chapter covers

conceptual description of the functionality of the Event system

procedures for using the system

reference information about dialog boxes, commands and other details.

Description

The event system handles the notification of system and process alarms as well as messages.

To fully understand all of the event system description, you should have a good understanding of the
module and the distributed control system concepts.

An event is a notification to the operator of some condition in the system or the controlled process that
may need attention. Which events are to be notified to the operator, depends on which list is displayed
and which filter is selected.

Events are categorized in the following types:

The Event Server in AIM maintains lists of the newest alarms while the state of all alarms in the system
is kept by the SBC. In the different event views both dynamic and static presentations can be generated.
Furthermore, the user can control the selection of what is displayed in the event views by means of
'filters'. System defined filters are associated with each list, but you can specify filters that suit specific

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 2 of 70

needs. There is one list for each client connected to the event server.

The event system provides several notification and presentation alternatives:

Alarm line

Event List image

Event popup

Event decoration

Audible alarm - a summary alarm indication

Alarm indication by means of color coding and flashing effect in the graphic presentation of
modules in flow and process images.

Event pages

There are four Event page types:

Dynamic alarm page

Static alarm page

Dynamic event page

Historic event page

The dynamic and static pages are view-ports along the imaginary list of alarms in the system.
The historic page is a view-port in the event log.

Dynamic alarm page

The dynamic alarm page is a view-port that moves automatically along the list of alarms in step with the
most recent alarm in the system. The dynamic alarm page has a limited length: As the list is filled up,
the oldest alarms are pushed out while the most recent ones are added to the top of the list.

Look up the dynamic alarm page to get a survey of the current alarm situation.

Static alarm page

The static alarm page is a view-port that can be moved by the user along the entire list of alarms. The
static alarm page is updated as major changes occur to alarms in the page. However, new alarms are not
added.

Look up the static alarm page when you want a more exhaustive but less flickering picture for the alarms
in question. As the dynamic page is filled up, the time span covered by the static page is older than the
one in the dynamic page.

Dynamic event page

The dynamic event page is only a display of events and changes of events.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 3 of 70

Historic event page

The historic event page is a view-port along the event database. I.e. it is a pure log of all events that
occur. Within the limits of the event database, you can define the time span to be covered by the historic
event page. While an alarm can appear only once in the dynamic and static page, it appears as many
times in the historic event page as there are changes - minor and major - in its state.

Use the Historic event page whenever you need to analyze the evolution of events.

Dynamic and static alarm pages

Dynamic and static alarm pages behave in a similar way: both pages are updated upon alarm changes
but static pages are snapshots of the situation at the time the page was opened. That means that the
dynamic alarm page always displays the most recent alarms. The static page, however, will is updated
with new alarms only each time it is opened. I.e. when focus is moved from the Dynamic Alarm Page to
the Static Alarm Page. Alarms that are acknowledged and return to the normal or void state are
removed.

All pages, except the Historical Event page, have a fixed length: I.e. as alarms are added to the top of the
page, older ones are pushed down or out of the page. The length of the Historical Event page depends on
how many events that pass the filter and the time span.

Note that the static and dynamic page normally have the same filters.
Upon creation of an Event List image, popup or decoration, the default filter is applied to all pages.
However, you can change to any other available filters. When the static/dynamic page is selected from
the dynamic/static page, the latest selected page inherits the filter from the latter. However, if the
previous page was the historic page, the latest selected filter for the page in question is used.

When both an Event

List image and an
event pop-up are
displayed, selections
made in one view are
reflected in the other
one too. This feature
makes it easier to track
items even when
selecting different
pages or differently
filtered pages and
apply to all event view
context.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 4 of 70

Related topics

Dynamic event page

The dynamic event page is only a display of events and changes of events. The events are displayed as
they occur and according to the selected filter. The dynamic event page can not be operated.

Historic event page

While the dynamic and static alarm pages are fed by the Event Server, the historic event page fetches
information from the event database. The historic event page acts like a log, the dynamic and static
pages act like 'indicators and controls'. That makes it obvious why alarms can not be acknowledged from
the historic event page.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 5 of 70

The historic event page lets the user query the event database. The database query is defined by the
applied filter and the user defined time span.

All functions related to historic event page operation are available from the context menu and the event
toolbar.

The universal event filter is the system default for the historic event page. That means that all events are
passed through. Historic event presentation requires that an ODBC data source name is defined and that
appropriate event storage parameters are set.

The vertical scroll bar of the historic event page lets you navigate within
the defined time span: When you operate the scroll bar a message box
displays the time stamp of the event that will appear in the top row of the
event page.

ODBC data source name (for the event database)

Historic event presentation requires that the data source name 'OSKEventDb', using the Microsoft
Access Driver (*.mdb) is defined on the OS. The User Data Source must point to the database file
defined in the OS specific EventStore parameter 'DBLocation'. The default path for the event database is
C:\lev\db\event.mdb.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 6 of 70

Event presentation

There are several presentation alternatives for displaying alarms and messages on the OS.

The Event presentation alternatives are:

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 7 of 70

Last Alarm line: A fixed area in the primary image window that is always visible, displaying the
last unacknowledged alarm. It is only displayed in the primary image window, and is always
visible, independent of the selected image type.

Event List: A listing of alarms within the image pane of any OS image window. The Event List is
selected from the icon in the toolbar. The Event List may include several 'pages': dynamic and
static alarm pages, dynamic event page and historic event page. Each page provides a specific
view of the events.

Event Popup: A free floating and resizable window, similar to the Event List. The popup window
is selected from the icon in the toolbar. The Event List may include several 'pages': dynamic
and static alarm pages, dynamic event page and historic event page. The operation of the event
popup window is identical with the operation of the Event List images.

Event Decoration: Any event view can be displayed in an Event Decoration. An Event
Decoration can be glued into any image that supports decorations. The Event Decoration may
include several 'pages': Dynamic and static alarm pages, dynamic event page and the historic
event page.

The display format is similar to a worksheet and identical for all presentation alternatives. The actual
layout (column order, width, etc.) is a matter of OS configuration.

In addition to the tabular presentations, alarm indication is included in flow and process images.

Related topics

Event List images

Named Event List images

Users with appropriate configuration privileges may define as many named Event List images as
applicable. These images may be configured into the different Image window navigators of the OS.

Displaying an Event List image

An Event List image is selected either:

by clicking the Event List icon on the toolbar, or

by selecting the Event List from the Navigator.

Event Lists are also available on the historical list.

An Event List image occupies the entire main work area of the AIM OS window.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 8 of 70

Event List tabs

Tabs at the bottom of the image pane allows you to select among different 'pages': Dynamic alarm
page, Static alarm page, Historic event page and the Dynamic Event Page. Clicking a tab, displays
the corresponding page.

Toolbar

The functions connected to the controls in the Event List image specific toolbar are:

Acknowledge. The button is available when there are unacknowledged alarms from controlled sources

The buttons are not available when the dynamic page is displayed.
In the static page, the buttons let you page up and down through all available alarms. When paging thro
gathered from the relevant stations.
In historic event page, the buttons let you move the time span forwards (up) or backwards (down).
Displays the Select filter dialog box.
Refreshes the current page. In dynamic pages, the function deletes the current records and collects new
In historic pages, a new query is sent to the event database.
The button is available with historic pages only. It displays the Date and Time dialog box.
The button is available with historic pages only. The function is available during database reading only
selection.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 9 of 70

Status line

Dynamic and static alarm and event pages

Status for these two pages are displayed.

However, if the status is not 'OK', this field displays a data gathering error message to announce that the
contents of the page may be incorrect.

Historic event page

On the historic event page, the status line displays the database status, the number of records and the
time span currently displayed. Upon error, an error message is displayed.

Related topics

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 10 of 70

Event attributes

Systematic handling and notification and presentation of events requires all events to be specified by
means of a set of attributes. Some of the attributes are represented by descriptive text found in SysConf
section Global.Event.System.EventImage. The text representation is used in the alarm line and in the
different views. Relevant event attributes are:

Time The time (local and UTC time) at which the reported condition occurred.
Originator Identification of the PS/PS group that issued the event.
Priority Each event is associated with a 'priority' level. The four priority levels are
denoted, in increasing order, by the numbers 0 through 3.
Type Description of the event or state that caused the event (reason).
Command Optional attribute, applicable for alarms only. An identification of the command
group group related to the alarm.
Text A description of the issuing module that can be understood by the operator. e.g.
"pump", "generator" etc.
Tag, Terminal Tag and Terminal denote the source of process events. The fields are used in
case of system events too.
Description Optional attribute. The module description associated with the tag.
Alarm state Applicable for alarms only. High, HighHigh, etc. or DigAlActive
Add. value Optional attribute. A value related to the event
Members Process stations in the PS group that initiates the event.

Event types

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 11 of 70

Events are categorized according to their cause:

Event type Cause

Process Alarm Violation of a defined alarm limit for a process value.
System Alarm An undesirable condition that is not related to the process. The
'station availability' alarms are a subset of the system alarms. They
deal with conditions like communication errors in the network.
Process Message A condition related to the process but not classified as a process
alarm.
System Message A condition not related to the process but not classified as a system
alarm.
Operation Message An operator intervention.
Configuration
A change of the system configuration
Message
Diagnostic message Information about the condition of the application

The exact event type names, used in event and alarm lists, are not necessarily identical to those used in
the table above. The name associated with each event type is set in the Global/Event
System/EventImage configuration parameter group 'Type Names' in the SysConf database.

Alarm limits

Digital alarms are either active or not (VOID and NORMAL). For alarms on analog terminals, however
the active state is further refined by means of alarm limits via the Analog Alarm Limits dialog box as
illustrated below:

As long as the terminal value is at least equal to the

limit but does not reach the next limit, the
corresponding alarm state is active.

E.g. On a scale from 0 to 100, the Low limit is set to

15 and the LowLow limit is set to 5. A Low alarm is
activate as 15 ≥ terminal value > 5.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 12 of 70

An analog alarm is in 'normal' or 'void' state as long as the terminal value remains within the High
and Low alarm limits. In other words, the alarm is not active.

The alarm becomes active when the terminal has reached the High or Low alarm limits but is
within the HighHigh or LowLow alarm limits.

When the terminal value has reached the HighHigh or LowLow alarm limits but is within the
High Scale or Low Scale, a new limit is passed.

The highest alarm limit is reached when the terminal value equals or exceeds the Scale High or
Scale Low limits.

Related topics

Alarm acknowledgement

Whether an alarm needs acknowledgement depends on its priority level. The priority level that marks
the limit is set in the Global/Event System configuration parameter: 'AckLimit'. All events with a priority
level at or above the 'AckLimit' need to be acknowledged. There is one exception: At OS start-up, the
'station availability' alarms caused by missing response from some station do not require
acknowledgement.

Acknowledgeable alarms must be acknowledged explicitly by the operator. Acknowledgeable alarms

become unacknowledged upon major alarm changes.

The possible acknowledge states are 'Acknowledged' and 'Unacknowledged'.

Acknowledgment authority

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 13 of 70

The authority to acknowledge alarms is built on command control and access system configuration:

An OS can only acknowledge those process alarms that are originated by the modules controlled
by that OS. This authority is exclusive: Process alarm can not be acknowledged from an OS that
does not control the source module.

An OS can acknowledge system alarms originated by itself or by controlled Process station. A PS
is controlled by the OS when it contains a module under a command group that is controlled by
the OS in question.

An OS can acknowledge system alarms for not-controlled PS, if the Global/Event
System/Privileges configuration parameter 'Ack Extended' is set to 'TRUE'.

Acknowledging methods

Alarms can be acknowledged:

Using the Ack option in the context menu of the dynamic and static alarm list and the last alarm
line.

Using the in the Event List image or event dialog toolbar.

Using the ACK key on dedicated AIM operator panels.

Selection of alarms for acknowledgement

The authority to acknowledge alarms from the OS in question is indicated in the left most column of the
list.

The effect of these actions depends on whether unacknowledged alarms are selected:

When one or several unacknowledged alarms are selected, the acknowledge action applies to
selected alarms only.

When no selection is made, the acknowledge action depends on the settings of the SysConf
Global/Event System/EventView parameter 'AckAllVisibleIfNoneSelected':
 If 'AckAllVisibleIfNoneSelected' is true, all unacknowledged alarms in the current alarm
page are acknowledged.
 If 'AckAllVisibleIfNoneSelected' is false, none of the unacknowledged alarms are
acknowledged.

Related topics

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 14 of 70

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 15 of 70

'Alarm state' and 'acknowledge state'

Alarms report the state of a condition. Three states are distinguished:

Indicating that the alarm condition does not exist, only shown in
Void
historical lists
Active Indicating that the alarm condition is present
Normal Indicating that the alarm condition is no longer present

Furthermore, alarms in the 'active' or 'normal' state can be 'acknowledged' or 'unacknowledged'.

The combination of 'alarm state' and 'acknowledge state' determines the legal transitions from one state
to another:

Alarm suppression and shelving

Suppression

Alarm systems sometimes offer a feature called 'alarm suppression'. The intention of this feature is to
reduce operator stress by holding back alarms that in some temporary system state are more or less
unwanted. The alarm property 'suppressed' indicates that the alarm is normally not intended for operator
attention. Some systems allow the operator to explicitly suppress unwanted alarms. Alarms suppressed
by the operator are called 'manually suppressed alarms'. Alarms suppressed by the system are called
'automatically suppressed alarms'.

Shelving

Some times alarms that are not applicable to the situation at hand pass through the suppression system.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 16 of 70

The alarm shelving function provides the operator with means to put these alarms a side on a temporary
basis.

The commands for shelving alarms and viewing of shelved alarms are provided on the main menu and
on the context menu of an alarm selected in the Event List image.

When you shelve the selected alarm, a dialog controlling the expiration time for the alarm
shelving is displayed. You can accept the default expiration time, or you can specify it yourself.
When the expiration time is passed, the alarm is automatically transferred back to the normal
alarm view again.

All alarms that are currently shelved may be displayed in an alarm shelving dialog. Displaying
this dialog, you can move the shelved alarm away from the shelf and back to the normal alarm
view again.

Whenever an alarm is shelved, you can select it in the alarm shelving dialog and specify a new
expiration time.

Dependent on the filter setting, shelved alarms may also be active in the images.

Filters and attributes

Filters

The presentation of events is subjected to filtering: I.e. only those events that match all attributes
specified in the filter, are included in the presentation. AIM includes system-defined filters that can not
be altered by the user. In addition, AIM provides facilities to specify additional user defined filters.

All filters are made up of a various number of configured, standard filter attributes. The system-defined
filters are:
Filter type Filter name Comments
Alarm filters Alarm line The last alarm line filter.
Default The recommended standard filter.
Only alarms, no
messages. Universal All alarms from all stations pass through the filter. This
filter is suited for test purposes. It is also suited to be the
basis for new filters, which initially must be copied from
an existing filter.
Event filters Default The recommended standard filter.
Universal All alarms and messages from all stations pass through
Both alarms and the filter. This filter is suited for test purposes. It is also
messages. suited to be the basis for new filters, which initially must
be copied from an existing filter.
Station filter Station Explorer Selected alarm- and message types from the system units
filter OS, HS and PS pass through this filter.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 17 of 70

In addition there is a horn filter for each horn on the OS.

Attributes

Filter attributes are the building blocks for all configured filters. Each filter attribute has a number of
options (see the Specified as ... column below), which may be selected or not for each of the filters.

Filter attribute Specified as ... Matched by ...

Acknowledge state Acknowledged Acknowledged alarms.
Not acknowledged Not acknowledged alarms.
Alarm type Process alarms Process alarms.
System alarms System alarms.
Command groups A specific set of Events not associated with a command group or
command groups associated with at least one of the command groups in the
set.
All command All events.
groups
Command groups Events not associated with a command group or
under control associated with a command group that is controlled by the
present OS. The effect of this filter attribute is
automatically kept in accordance with the present
command control state.
Event priority A priority level Any combination of alarm priorities.
Event type Process alarm Process alarms.
System alarm System alarms.
Process message Process messages.
System message System messages.
Operation message Operation messages.
Configuration Configuration messages.
message
History stations A specific set of HS Events not associated with any HS and events associated
with one of the HS in the set.
All HS All events.
Operator stations All operator stations Alarms and events from all operator stations will pass.
A specific set of Only alarms and events from selected operator stations
stations will pass.
Only stations in OS Only alarms and events from stations in the OS group will
group pass.
All stations except Alarms and events from all operator stations except this
"OwnStation" station will pass. Kept for backward compatibility.
Origin A single word, Events with the attribute Origin matching the pattern. The

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 18 of 70

pattern, or empty. pattern may be specified as case sensitive or not, and as

whole or partial word. If empty, all events match.
Process stations A specific set of PS Events not associated with any Process station, and events
associated with one of the PS in the set.
Source Name A single word, Events with the attribute Tag matching the pattern. The
pattern, or empty. pattern may be specified as case sensitive or not, and as
whole or partial word. If empty, all events match.
Suppression state Not suppressed All events that are neither automatically nor manually
suppressed pass the filter.
Manually Manually suppressed alarms pass the filter.
suppressed
Automatically Automatically suppressed alarms pass the filter.
suppressed
Watchcall groups A specific set of Events not associated with a watchcall group or
watchcall groups associated with at least one of the watchcall groups in the
set.

See also

Alarm groups

Grouping of alarms is a tool for providing the operator with an essential selection of alarms by
suppressing or adding alarms.
There are four different kinds of alarm groups:

First up

Logical

Aggregated

Collective

The First-Up type of group shows the first alarm in the group that occurs, but suppresses all the
following alarms. This is useful in cases where many alarms may occur for essentially the same reason.
An alarm may not be the member of more than one First-Up group.

The Logical type of group suppresses its members when a specified expression evaluates to True.

The Aggregated type of group gives an additional alarm, the Aggregated alarm, signaling that all alarms
in the group have an active state.

The Collective type of group reduces the number of alarms by providing one specific alarm, the
Collective alarm, when any member of the group is active. All members of the group are automatically
suppressed.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 19 of 70

Audible alarm - 'Horn'

An OS may be equipped with one or several audible alarms (horns). Each audible alarm on the OS has
its own set of OS-specific configuration parameters (Sections/OS<x>/Event
System/Horns/Horn/Horn<y> and ...Horns/Silence<z>) and its own filter.

Audible alarms are used to notify new alarms and major alarm changes. The horn specific filter will
normally further narrow this selection.

The OS offers a function that silences all horns, controlled by that OS. If an alarm causes Horn on more
than one OS, all horns can normally be silenced from any of the OS in question. However, system
alarms causing Horn can only be silenced from the originating OS. E.g. when an OS becomes 'not
communicational' several other OS may detect the situation and notify it by means of 'Horn'. The Horn
must be silenced on every OS that notifies the situation.

For each horn, a delay can be specified in msec (SysConf parameter: 'Sections/OS<n>/Event
System/Horns/Horn/Horn<n>/Delay) in order to suppress the audible alarm until the delay has expired.
Only alarms that remain unacknowledged for the defined delay time are considered for sounding the
horn. However, if the number of unacknowledged alarms exceeds a system defined limit, the delay will
be overridden and the horn will sound.

Related topics

Alarms and messages main features

The system alarms and adjacent messages are displayed in Event images. They are composed as
described below:

System alarms System alarms are issued when abnormal events occur in the process control
system. The station field (statid) indicates from which station the alarm is
reported. In some of the alarms, the type of CPU (376/386/960) is included in the
alarm text/identificator.
System messages System messages are issued as additional information for logging of:

system alarms on state changes, e. g. due to operator interaction

events occurring in the control system.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 20 of 70

Operation The operation messages are issued as consequences of the operator interaction on
messages the OS (by the OS itself). The station field (statid) indicates on which OS the
interaction takes place.

Related topics

System alarms list

General system messages list

HS system messages list

Operation messages list

RBUS Alarm messages

ModbusMaster Alarm messages

ModbusSlave Alarm messages

Nmea Alarm messages

Profibus Alarm messages

ProfibusSlaveRedundancy Alarm messages

HartMaster Alarm messages

NetIo Alarm messages

NetIoSafe Alarm messages

AutroSafe Alarm messages

General system messages list

As can be seen from the table below, in most cases only the message fields (value type almess) is filled
in. For some messages, however, the available alarm text field (value type altext) contains information.

The station field (statid) indicates from which station (yy in the tables, e. g. PS yy) the message is

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 21 of 70

reported. When the tag fields indicates cputest, this means either CPU376 SELF TEST, CPU386 SELF
TEST or CPU960 SELF TEST, dependent of the type of PS in which the self-test error occurred.

Tag field Alarm text field Message field Explanation

tag tag INITIALISING FLG Gr: x Alarm from tag has triggered follow-on
alarm suppression for group x.
tag tag CANCELING FLG Gr: x ttt Alarm suppression for group x, triggered by
tag "ttt" is cancelled.
Suppresses alarm from tag in follow-on
tag tag SUPPRESSED FLG Gr: x ttt alarm group "x", where tag "ttt"
initialised/triggered the suppression.
As above, but the follow-on alarm group is
tag tag SUPPRESSED ???
not identifiable.
Logical suppression of alarm from tag in
tag tag SUPPRESSED LOG Gr: x
logical suppression group 'x'.

Tag field Message field Explanation

ocuxx AUTO M/S SWITCH PS yy Auto switch mode is set for PS yy from OCU xx.
file server AUTO: WRITE PS&IO Command received from module in PS yy to write
backup of the .ps- and .io files for the PS.
file server ERROR [opc]: file name PS yy error when reading the file "file name". Code opc:
26 - consistency error
27 - unexpected end of file.
file server ERROR opc/param(d) :file File access error (other than communicational error)
name during following operations: (opc):
20 - opening of file
21 - writing of file
22 - reading of file
23 - closing of file
24 - changing of file name
25 - comparison with read-back file resulted in
differences in "storedate" line.

param is an error number from file system:

65534 - no more memory
65532 - unspecified error
65531 - server busy
65528 - end of file
65527 - no disc
65526 - illegal server
65525 - illegal access
1 - (if opc = 25).
file server ERR READING BACKUP-> PS Fatal error occurred when reading PS yy from redundant
REBOOT active station. Reloading is started automatically.
file server ERROR UPDATING Error detected during updating of PS yy from redundant

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 22 of 70

REDUNDANT PS active station.

Cpu test FIFO DATA ERROR Extra information on FIFO communication error,
DETECTED indicating data transmission error.
Cpu test FIFO IS STOPPED Extra information on FIFO communication error,
indicating that FIFO has stopped.
file server TO SMALL MEMORY Too little free memory in computer when reading .ps file
for PS yy.
station EVENT QUEUES AUTO- IF HCU dies, event queues are automatically opened.
OPENED
file server COMM. ERROR[opc]: filename Backup/read/write communicational error during
operation (opc).

(See under ERROR).

ocuxx COMMAND: WRITE IO Command received from OCU xx to write backup of .io
file for PS yy.
ocuxx COMMAND: WRITE PS&IO Command received from OCU xx to write backup of .ps-
and .io files for PS yy.
file server READ BACKUP OK ! Reading of .ps- and .io files for PS yy is completed and
OK.
file server READ BACKUP STARTED Reading of .ps- and .io files for PS yy is started, either
automatically at start-up, or manually via OCU (Unix).
file server MISSING FILE: file name File "file name", which is connected to PS yy, is non-
existent.
ocuxx MANUAL M/S SWITCH PS yy Manual switch mode set for PS yy from OCU yy.
Cpu test ZEROPT(0xaaaaa) Extra information on zero pointer:
=0xbbbbbbbb(ccc) aaaaa: Overwritten zero area
bbbbbbbb: Contents of first (d)word.
ccc: Number of overwritten (d)words.
file server PS yy READY Reading of .ps- and .io files for PS yy is ready and OK.
- PS yy STARTED IN mm MODE PS yy is started (auto start) in indicated mode: mm =
IO/SIM.
Cpu test RAM-ERROR(ttttt) Extra information on RAM error:
ADR:0xaaaaaaaa aaaaaaaa: Indicates where error is localised.

tttt: Test-type:
CACHE Error from CACHE test
R/W Error from RAM
read/write/modify
ADR Error from RAM address line test.
file server RED ST: NOT COMPLETED Message from redundant active station, with update
information to PS yy not received.
file server CHK SUM ERROR TOTAL = x After .ps file for PS yy is read, a total of x checksum
errors are found.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 23 of 70

file server 1. CHK SUM ERR: ttt First checksum error that is found after .ps file for PS yy
is read, is for tag ttt.

Tag Message field Explanation

field
file RED ST: <type>/<modno>/<id2>/<id3>/<id4>/<size> Error in reception of updating
server data from active station to PS
yy.

See below.

Each RED ST error parameter that represents received and not accepted elements is described here. The
reason why elements are rejected may be:

1. On the master, the configuration has been edited. The new configuration has not been saved to the
server that the slave loads from (or has not been saved at all). Configuration in this context means
new redundant modules, or alarm configured on a terminal that previously didn't have any.
2. On the servers there are inconsistent files, or the files don't match those files the active station
read. This means that adding (but not reducing) of modules/alarms is possible by transferring the
file and load the computers sequentially during off-line configuring.
3. The message contents has become corrupt.

<modno> - the numbers of the modules to which the data shall be sent (the number of the module on the
station that currently is updated).
<size> - size of data area that is to be updated.
<term type> - 1 - input terminal, 2 - output terminal, 4 - process terminal.
<type> - types that are not listed in the table below are regarded as erroneous.

<type> (object <id2> <id 3> <id 4>

type)
1 - modulstruct Module number on active station 0 0
2 - parameters algorithm number 0 0
4 - terminal value terminal no <term type> value no.
8 - alarm struct terminal no <term type> 0
16 - alarm limits terminal no <term type> 0
32 - terminal color terminal no <term type> 0
4096 - termination 0 0 0

Tag field Message field Explanation

file server WRITE IO OK ! Feedback from file server (OCU) reporting that backup
writing of .io file for PS yy is completed and OK.
file server WRITE PS&IO OK ! Feedback from file server (OCU) reporting that backup

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 24 of 70

writing of .ps- and .io files for PS yy is completed and

OK.
file server SLAVE: MASTER BACKUP Error detected while slave (PS yy) reads master's .ps
ERROR file.
CPU376 STACK: ss Additional information regarding used stack:
SELF TASKSTR:0xaaaaaaaa aaaaaaaa: Displays address to task struct for relevant
TEST task.
ss: Indicates free stack for the task.
CPU386/960 STAcK:ss Additional information on used stack:
SELF TASK:nnnnnnnnnnnnnnnn nnnnnnnnnnnnnnnn: Displays task name.
TEST ss: Indicates free stack for the task.
OCU name START (mm) PS yy started after having received command from
OCU "ocunavn" in indicated mode:
mm=SIM/IO.
OCU name STOP PS yy stopped on command from OCU "ocunavn".

HS system messages list

The following types of messages are with regard to historical storage and is reported via indicated (xx)
OCU (station field).

Message field Explanation

DATABASE
ERROR: Error messages from time series database. Error message number (xx), see below.
xx
-2 invalid set
-3 invalid record
-4 invalid database
-5 invalid field name
-6 invalid db address
-7 no current record
-8 set has no current owner
-9 set has no current member
-10 key value required
-11 invalid lock type
-12 record is owner of non-empty set(s)
-13 record is member of set(s)
-14 member already owned

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 25 of 70

-15 field is a compound key

-16 record not connected to set
-17 field is not a valid key
-18 record not legal owner of set
-19 record not legal member of set
error in d setpages
-20
(database open or bad param)
-21 incompatible dictionary file
-22 illegal attempt to delete system record
-23 attempt to lock previously locked rec or set
-24 attempt to access unlocked record or set
-25 transaction id not be supplied
-26 transaction already active
-28 transaction cannot begin due to locked files
-29 attempt to free a lock inside a transaction
-30 too many pages changed within transaction
-31 attempted update outside of transaction
-32 functions requires exclusive db access
-33 Attempted to write lock a static file
-34 No user id exists
-35 database file/path name too long
-36 invalid file number was passed to denfile
-37 field is not an optional key
-38 field not defined in current record type
-39 record/field has/in a compound key
-40 invalid record or set number
-41 record or set not timestamped
-42 invalid user id - not alphanumeric
-43 NetBIOS is not installed on machine
-44 bad # of elements in DBDPATH
-45 bad # of elements in DBFPATH
-46 No current record type
-47 Invalid country table sort string
-48 database not closed

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 26 of 70

-900 no more space on file

-901 system error
-902 page fault -- changed during usage
-903 no working file set in dio
-904 unable to allocate sufficient memory
-905 unable to locate a file
-906 unable to access db lock file
-907 db lock file open/access error
-908 inconsistent database locks
-909 file record limit reached
-910 key file inconsistency detected
-911 Max concurrent user limit reached
-912 Bad seek on database file
-913 Invalid file specified
-914 Bad read on database/overflow file
-915 Network synchronization error
-917 Network communications error
-919 Bad write on database/overflow file
-920 Unable to open lockmgr session
-921 DBUSERID is already used by another user
-922 The lock manager is busy

Message field Explanation

DATABASE INITIALIZED (OCU xx) Erases and prepares time series databases.
DATABASE CLOSED (OCU xx) Closes time series database from OCU xx.
DATABASE CLOSED If the time series database was open when the error occurred,
AUTOMATICALLY this message is a consequence of database error in the time
series database (see above).
DATABASE RECOVERY IN May occur during start-up of time series database after
PROGRESS interrupt/stop of HCU.
DATABASE OPENED (OCU xx) Opens time series database from OCU xx.
READ DB-BACKUP STARTED (OCU Reads the time series database from backup. Started from
xx) OCU xx.
STORE DB-BACKUP STARTED Performs backup of the time series database. Started from
(OCU xx) OCU xx.

Operation messages list

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 27 of 70

Operation messages are listed in the table at the bottom. The table below defines the message types.

Message types

Message Explanation
type
1 MOP = Change initiated from module operation menu.
2 This type of message may be displayed during operation by using the module operation
menu, provided that operation of the relevant function module by definition shall generate
an operation message.
3 This type of message is displayed during operation by using the module's operation menu,
under the System menu.
4 This type of message is linked to the command system, and regards transfer of the control of
command groups between stations. "x" is the OCU number, while "Group" is the name of
the OCU group. If the tag field displays OCU-group, this indicates that all command groups
currently under command of this OCU-group can be taken by the requesting OCU-groups.
5 This type of message is generated during use of the password system.
6 This type of message is linked to the redundancy functions of the system. "x" and "y"
represent PS numbers in a master slave pair. "zz" is either MASTER or SLAVE.
7 This type of message is displayed during operation by using the module's operation menu for
the menu ALARM GRP, which regards the module's connections with available alarm group
types. "x" is a group number.

Operation messages

The operation messages are listed in the table below.

Tag field Message field Explanation Message

type
ACCESS (See below) The user has accessed a function with access check 5
OK to which the user has access. (Each function is
described below.)
NO (See below) The user has attempted to access a function to which 5
ACCESS the user does not have access.
NO <User defined> In addition to the functions described below, user 5
ACCESS defined checkpoints with adjacent text for operation
messages etc. (accinit.c) can be installed.
Tag field ACK PROC ALARM Acknowledge process alarms. 5
Tag field ACK SYS ALARM Acknowledge system alarms. 5
Tag field ALARM OPER Use "ALARM" button during module operation. 5
Tag field ALGROUP OPER Use "ALARM GRP" button during module 5

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 28 of 70

operation.
Tag field CHANGE DBASE Change database parameters, time series etc. 5
Tag field COPY FILE Use file-copying function. 5
Tag field DELETE FILE Use file deletion function. 5
Tag field ENTER CONFIG Enter configuration mode. 5
Tag field IO-CONF READ Read IO system and configuration data. 5
Tag field IO-CONF WRITE Change IO system and configuration data. 5
Tag field NET OPERATE Modify net status. 5
Tag field OPERATE Use OPERER[OPERATE] button. 5
Tag field PRINT QUEUE Open/close printer queues. 5
Tag field PS START/STOP Start and stop PSs. 5
Tag field PWD MAINT Maintenance of password system, e. g. change 5
password.
Tag field READ PG2 Read parameter/table images page 2. 5
Tag field READ PG3 Read parameter/table images page 3. 5
Tag field SET TIME Set clock. 5
Tag field SYSTEM OPER Use "SYSTEM" button during module operation. 5
Tag field TAKE COMMAND Use the take-function in the command control 5
system.
Tag field WRITE PG1 Change data parameter/table images page 1. 5
Tag field WRITE PG2 Change data parameter/table images page 2. 5
Tag field WRITE PG3 Change data parameter/table images page 3. 5
tag ACTIVE Sets the module in active mode (out of maintenance 3
mode).
tag ACTIVE INP Sets all input terminals in active mode (out of 3
maintenance mode).
tag ACTIVE OUTP Sets all output terminals in active mode (out of 3
maintenance mode).
tag ALARM OFF Disables the module alarm system. 3
tag ALARM ON Enables the module alarm system. 3
tag ALARM CHANGE x Change in level for digital alarm (MOP) 1
-> x (0-No alarm,
1-Low level,
2-High level)
Command REQUESTED BY OCU in other OCU group requests your OCU group 4
group/OCU <OCUx>(<Group>) to take command of command group(s) currently in
group OK? command of your OS group.
tag BLOCK INP Sets all input terminals in passive mode (in 3

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 29 of 70

maintenance mode).
tag BLOCK OUTP Sets all output terminals in passive mode (in 3
maintenance mode).
- DB-BACKUP Error during read/write from/to backup for time 1
FAILED series database.
- READ DB_BACKUP Time series database read from backup, OK. 1
READY
tag HHI: xxxx.x -> xxxx.x Changed limit for HIGH HIGH alarm (MOP). 1
tag HIGH: xxxx.x -> Changed limit for HIGH alarm (MOP). 1
xxxx.x
- STORE Time series database written to backup, OK. 1
DB_BACKUP
READY
tag LLO: xxxx.x -> xxxx.x Changed limit for low low alarm (MOP) 1
User name LOGIN FAILURE : User has attempted to log in by using wrong 5
<user name> password
User name LOGIN OK : <user User has logged in with correct password. 5
name>
tag LOW: xxxx.x -> Changed limit for low alarm (MOP). 1
xxxx.x
tag MDL FLGx Module connected to follow-on alarm group x. 7
tag MDL LOGx Module connected to logical suppression group x. 7
tag MDL PANx Module connected to alarm panel group x. 7
Command Command Group not The command group is currently not under TBS
group/OCU under command command of any OS Group.
group
Command None communicating No other OS of this OS Group is currently available. TBS
group/OCU OSes in OS Group
group
Command REQUEST FAILED, A request for taking the command of command 4
group/OCU <OCUx> REFUSED group(s), which currently is under command of
group other OCU group, is refused by a member of the
other OCU group.
Command REQUEST FAILED, A request has failed because no OCU of the 4
group/OCU NO ANSWER requested OCU group has answered within the time-
group out period (approx. 60 seconds).
Command REQUEST FAILED, A request has failed due to concurrent request for 4
group/OCU BUSY the same command group(s) from other OCU group.
group
Command REQUEST Requested OS group accepts a request for transfer of 4
group/OCU SUCCEED,FROM. command of command group(s).
group <OCUx>(<Group>)

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 30 of 70

Command REQUEST Command group(s), which were not in command by 4

group/OCU SUCCEED, NO any OCU group, is transferred to the command of
group OWNER your OCU group upon request.
tag PASSIVE Sets module in maintenance mode. 3
PS-x/PXU- RED CONTROL TO Operator has selected MASTER or SLAVE 6
y zz active/online.
PS-x/PXU- REDUNDANCY TO Operator has selected automatic switching mode. 6
y AUTO
PS-x/PXU- REDUNDANCY TO Operator has selected manual switching mode. 6
y MANUAL
tag SHI: xxxx.x -> xxxx.x Changed limit for HIGH scale alarm (MOP). 1
tag SLO: xxxx.x -> xxxx.x Changed limit for LOW scale alarm (MOP). 1
Command TAKEN BY <OCUx> Command group(s), which were under command of 4
group/OCU (<Group>) your OCU group, is now under command of other
group OCU group.
Command TAKEN FROM Command group(s), which were under command of 4
group/OCU <OCUx>(<Group>) other OCU group, is now under command of your
group OCU group.
Command TAKEN, NO Command group(s), which no OCU groups were in 4
group/OCU OWNER command of, is now under command of your OCU
group group.
tag text x -> x Change of floating point parameter. "text" is either 2
the menu text, e. g. "UP", or another text defined for
the module.
tag text xxxxxxx.xx- Change of floating point parameter. "text" is either 2
>xxxxxxx.xx the menu text, e. g. "VALUE", or another text
defined for the module.
User name LOGGED OUT User has logged out. 5
tag ENTERS MANUAL Manual change option is selected. Manual changes 3
are to be entered to terminals that are blocked/set in
maintenance mode.

Pop-up messages

Message Explanation
An operator (OS Group) has attempted to operate a module
No Command Control on <command
contained in a command group, over which the operator (OS
group>
Group) currently has no command control.

RBUS system alarm list

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 31 of 70

Error in communication with RIO module on RBUS A

Error in communication with RIO module on RBUS B

FOST: Channel restored failed

FOST: Illegal channel config.

FOST: Passive side error

FOST: PDU residual voltage

FOST: PDU restore failed

FOST: PDU stuck

FOST: Shutdown test failed

Given RIO module type not found

No communication with RIO module on RBUS A

No communication with RIO module on RBUS B

No communication with RIO module

RBUS Message length is incorrect

RBUS: Cables are crossed

RBUS: Conflict between configured and connected RIO module type/ID

RBUS: Initial configuration and scan sequence failed

RBUS: IO Scan Mail box failure. Scan not running

RBUS: Memory allocation failure. Scan not running!

RBUS: Message channel type map is incorrect

RBUS: No connection with HUB A

RBUS: No connection with HUB B

RBUS: No connection with RIO modules

RBUS: RIO configuration check disabled

RBUS: RIO module in a 1oo2-pair is manually set in Maintenance or Passive mode

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 32 of 70

RBUS: RIO module set in Maintenance mode. (Configuration error)

RBUS: RIO module set in Maintenance mode. (FW version error)

RBUS: RIO module set in Maintenance mode. (Internal CFG error)

RBUS: RIO module set in Maintenance mode. (Internal SW error)

RBUS: Unknown error index (See code in separate coloumn or message)

RBUS: Unrecognized error: %d

RIO: AO not calibrated

RIO: Configuration CRC error

RIO: Critical temperature (restart required)

RIO: Current feedback outside tolerance

RIO: Error in readback of AO test value (reset required)

RIO: External voltage error. PSU1

RIO: FW A version is less than minimum

RIO: FW P version is less than minimum

RIO: Ground monitoring error, (Iso1) lower voltage limit exceeded

RIO: Ground monitoring error, (Iso1) upper voltage limit exceeded

RIO: Ground monitoring error, (Iso2) lower voltage limit exceeded

RIO: Ground monitoring error, (Iso2) upper voltage limit exceeded

RIO: Ground monitoring error, lower current limit exceeded

RIO: Ground monitoring error, lower voltage limit exceeded

RIO: Ground monitoring error, upper current limit exceeded

RIO: Ground monitoring error, upper voltage limit exceeded

RIO: High temperature

RIO: HighSide driver blocked ON

RIO: Illegal Loop monitoring type

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 33 of 70

RIO: Illegal signal or range type

RIO: IO channels locked in failsafe state

RIO: Loop mon.error 4

RIO: Loop mon.error 5

RIO: Loop stuck

RIO: Module configuration error

RIO: Not in normal IO mode. Automatically set to normal

RIO: On-board voltage error. GND1 (reset required)

RIO: On-board voltage error. GND2 (reset required)

RIO: On-board voltage error. GND3 (reset required)

RIO: On-board voltage error. PWR2 (reset required)

RIO: On-board voltage error. PWR3 (reset required)

RIO: On-board voltage error. PWR4 (reset required)

RIO: On-board voltage error. REF1 (reset required)

RIO: On-board voltage error. REF2 (reset required)

RIO: On-board voltage error. Vital CPU voltage PWR1 (reset required)

RIO: On-board voltage error. Vital CPU voltage PWR1 (restart required)

RIO: Open loop/Cable break

RIO: Overload protection activated (reset required)

RIO: PDU turned OFF (reset required)

RIO: Power A failure (restart required)

RIO: Power A failure

RIO: Power B failure (restart required)

RIO: Power B failure

RIO: Probable short-circuit

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 34 of 70

RIO: RBUS cables are crossed

RIO: Relay or relay driver fault

RIO: Reversed polarity

RIO: Selftest error (restart required)

RIO: Short-circuit

RIO: Too low feedb. while PDU=1

RIO: Too slow signal transition

RIO: Voltage feedback outside tolerance

ModbusMaster system alarm list

Checksum error

Communication error

Communication port opening error

Communication timeout

Communication with slave disabled

Error creating communication task

Exception, acknowledge

Exception, illegal data address

Exception, illegal data value

Exception, illegal function

Exception, memory parity error

Exception, negative acknowledge

Exception, slave device busy

Exception, slave device failure

High priority queue is full

No response from backup channel

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 35 of 70

No response from primary channel

Prev WriteOnChange not executed

Previous trig not executed

Wrong response from slave

ModbusSlave system alarm list

Communication error from master

Communication port opening error

Communication timeout from master

Error on communication task

Nmea system alarm list

ascreate already done

Communication port reservation error

Data overflow! Buffer size too small

Driver mail box error. (Full or illegal parameter)

Driver task creation error

Error base

Framing error

Framing/overrun error

Illegal buffer size

Illegal channel specified

Illegal config. func. in IOCTL

Illegal protocol

Interrupt disabled

IO error

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 36 of 70

Max. retransmissions reached

Message receive error or no IOCTL request

Message receive error or no read/write func.

No ack received

No ascreate done

No contact with hardware

No defined protocol in asprotocol

No more memory for system buffers

Not enough receive buffers

Overrun error

Parity error

Parity/framing error

Parity/framing/overrun error

Parity/overrun error

Receive/forward communication port reservation error

Send delay disabled due to enabled RxFwComP

Send delay set to 0 mS due to IO blocks in fast scan

Telegram checksum error

Telegram timeout

Write not allowed due to claim

Profibus system alarm list

DPV1 IO block communication failure

Error

Line break

Lower limit exceeded

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 37 of 70

Major communication failure

Master communication failure

Module communication failure

Overload

Overtemperature

Overvoltage

Short circuit

Slave communication failure

Undervoltage

Upper limit exceeded

ProfibusSlaveRedundancy system alarm list

Error

Line break

Lower limit exceeded

Major communication failure

Master communication failure

Module communication failure

Overload

Overtemperature

Overvoltage

Short circuit

Slave communication failure

Undervoltage

Upper limit exceeded

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 38 of 70

HartMaster system alarm list

Server initialization error

NetIo system alarm list

Signal value difference PS-A

Signal value difference PS-B

Signal value difference PS-C

NetIoSafe system alarm list

Error creating communication task

NetIoSafe communication error

Unknown producer PS

AutroSafe system alarm list

Autrosafe fault, check panel or event log

COMMUNICATION FAULT

Incompatible software

INTERNAL SOFTWARE FAILURE

Version check disabled

Using the Event system

This section contains procedures for how to use the Event system.

For operating and monitoring:

Viewing and acknowledging alarms

Selecting items in alarm pages

Shelving alarms

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 39 of 70

Viewing filter attributes

Defining time span

Updating filters

Selecting filter type and filter

Creating and deleting filters

Editing filter attributes

For configuration and editing:

Creating and deleting Event List images

Viewing and acknowledging alarms

Requirements

No configuration mode is required.

The Event system indicates the alarm states as shown in the table below:

Acknowledged alarm
Unacknowledged alarm
Suppressed alarm
When the alarm is marked like this it is not permitted to
acknowlede.
There are two reasons for this, either:

1. The OS is not in command of the alarm

origin command group,
or
2. The logged in user does not have the
appropriate user rights to acknowlede the
alarm.

Not acknowledged alarm from 'Delegateable' command

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 40 of 70

group at default location. The alarm can be

acknowledged.
Not acknowledged alarm from 'Delegateable' command
group at non-default location. The alarm can not be
acknowledged.

Viewing alarms

Alarms can be viewed in different ways:

The last unacknowledged alarm can be viewed on the last alarm line of any image displayed in
the primary image window.

To get a complete overview of all alarms - acknowledged and unacknowledged, display the
appropriate Event View. (The Event View with the appropriate alarm filter settings.) Use the
available pages as applicable.

Note! System alarms on PSs can also be viewed by entering the PSs from the Station Explorer or
System Status images.

Acknowledging alarms

Last alarm line

To acknowledge the last alarm on the primary image window, proceed as follows:

1. Select the last alarm line. On the toolbar, click . The alarm is removed from the last alarm line.
On the appropriate Event View, the unacknowledged alarm mark (see above) on this particular
alarm has disappeared.
2. If your application contains more unacknowledged alarms, the next, appropriate unacknowledged
alarm is displayed on the last alarm line.

Event List image

To acknowledge alarms on the appropriate Event View, proceed as follows:

1. Select the alarm(s) you want to acknowledge. On the toolbar, click . The unacknowledged
alarm mark (see above) disappears.
2. If no alarm is selected prior to clicking , and the 'Ack All Visible If None Selected'-property is
set, all visible unacknowledged alarms are acknowledged.
3. Note! System alarms on PSs can also be acknowledged by entering the PSs from the Station
Explorer or System Status images.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 41 of 70

Related topics

Selecting items in alarm pages

Selections made in one alarm page are reflected in all alarm pages. I.e. if your selection includes the
latest alarm, this item will be selected in both the actual page where you make the selection and the last
alarm line. This is a useful feature, especially when applying different filters to a page in the Event List
image and event dialog. Note that this feature does not include the historic event page.

To cancel any selection, click in any field that is not in the left column of the page.

There are several methods for selecting items in alarm pages.

Single row selection: click in the left field in the row. All previous selections are removed.

Continuous multiple row selection: Click in the left field of the first row to be included in the
selection. Keep SHIFT key down while clicking in the left field of the last row to be included in
the selection.

Random multiple row selection: Click in the left field of the first row. Keep CTRL key down
while clicking in the left field of the rows to be included in the selection.

Using CTRL+Click in the left field of a selected row, deselects that row.

Selecting all rows: use the Select all command

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 42 of 70

Related topics

Defining time span

To define the time span for events displayed on the Historic Event Page, proceed as follows:

Requirements

No configuration mode required.

Procedure

1. Display the Historic Event Page, for which you want to change the time span.
2. On the toolbar, click . The Date and Time dialog box is displayed.
3. To define the most recent end of the time span, use the fields contained in the Most recent time
group box: Either click the Now button, or use the calendar, drop-down list boxes and text boxes.
4. To define the relative backward time span, type in the appropriate values in the text boxes
contained in the And backward time span group box. Close the box.
5. The Historic Event Page is instantly updated with the new time span, which is displayed on the
status line.

Related topics

Shelving alarms

The procedure below describes how to shelve alarms, eventually view and edit them, and how to move
them back to normal alarm view again.

Requirements

Alarm shelving applies to acknowledged alarms.

Shelving an alarm

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 43 of 70

1. The command group, containing the applicable alarm, must be under command control of your
OS group.
2. Display the Event List image. Select the alarm(s) you want to shelve. Right-click to display the
context menu for the selected, acknowledged alarm(s). Click Shelve Alarm.... The Set
Expiration Time dialog box is displayed.
3. Select the expiration time and -date for the selected alarms. Check the Show list of shelved
alarms box and click the OK button. The Alarm Shelving dialog box is displayed. All shelved
alarms are displayed in the list view with their expiration times and other information.
 No sign of the alarm can be observed in Flow images or Event List images while the alarm
is shelved.
4. To restore a shelved alarm(s): On the Tools menu click Alarm Shelving.... The Alarm Shelving
dialog box is displayed. Select the applicable alarm(s) and click the Remove button. The alarm(s)
is(are) restored and thus removed from the list of shelved alarms.

In Flow images, the alarm spot is again displayed.

In Event List images, the alarm is again listed.

Note! When using certain filter settings, alarms that are shelved may be listed in Event lists.

Viewing and editing a shelved alarm

1. The command group, containing the applicable alarm, must be under command control of your
OS group.
2. On the Tools menu click Alarm Shelving.... The Alarm Shelving dialog box is displayed. All
shelved alarms are listed.
3. To restore a shelved alarm, see step 3 in the procedure above.
4. To edit the expiration time for the selected shelved alarm(s), click the Edit... button. The Select
Expiration Time dialog is displayed. Select a new expiration time as applicable.
5. To print the list of shelved alarms, click the Print... button.

Related topics

Selecting filter type and filter

Requirements

No configuration mode is required.

Note! When an Event List image is displayed, you can select among other filter types and thus among

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 44 of 70

other filters. This applies for all event view context (poput, decoration, etc). Your new selections
however apply only as long as the Event List image is displayed, or the historical list is used.

1. On the toolbar, click . Uncheck the Use default filter type box.
2. To view the navigation tree comprising all filter types, filters and attributes, click the Filters...
button. The Filters dialog box is displayed. You can view all filter attributes by double clicking
them. Close the dialog box.
3. Return to the Select Filter dialog box. To select filter type for the current Event View: From the
Filter type drop-down list, select filter type as applicable. From the Filter Name dropdown list,
select filtername. Click the OK button.
4. In the active filter field on the Event toolbar, the lead text to the left of the drop-down list box now
displays the filter type you selected in the previous step and the visible item in the dropdown list
will be the selected filtername. This does not apply for the Last Alarm Line or decoration context.

The filter change applies to the page where the change was made except for Dynamic and Static alarm
pages where the filter change will apply for both pages.

Related topics

Updating filters

Requirements

No configuration mode is required.

Updating filter

To update a filter with the attribute values of another, similar filter of the same type, proceed as follows:

1. On the toolbar, click . The Select Filter dialog box is displayed. Uncheck the Use default
filter type box.
2. Click the Filters... button. The Filters dialog box is displayed.
3. Select the filter, which attributes are to be copied across. Click the Source button. The name of
the filter is now printed in bold font.
4. Select the filter, which is to receive the filter attributes. Click the Update button. Red check marks
appear on the appropriate filter folder icons.
5. Click the Apply button. The Confirm apply dialog box is displayed. Confirm the update. Close
the Filters dialog box. Close the Select Filter filter dialog box by clicking the OK button.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 45 of 70

Related topics

Creating and deleting filters

Requirements

No configuration mode required.

Creating a new filter filter

To create a new a filter within the same filter type folder and with the attribute values of another, similar
filter, proceed as follows:

1. On the toolbar, click . The Select Filter dialog box is displayed. Uncheck the Use default
filter type box.
2. Click the Filters... button. The Filters dialog box is displayed.
3. Select the filter, which you want to copy. Right-click and select Copy from the sub-menu. The
filter is copied to a folder with yellow mark. Type in the name of the new filter. Eventually, edit
each attribute applicable.
4. Click the Apply button. The Confirm apply dialog box is displayed. Confirm the creation of the
new filter. Close the Filters dialog box. Close the Select Filter filter dialog box by clicking the
OK button.

Deleting filter

To delete a user generated filter, proceed as follows:

1. On the toolbar, click . The Select Filter dialog box is displayed. Uncheck the Use default
filter type box.
2. Click the Filters... button. The Filters dialog box is displayed.
3. Select the filter, which you want to delete. Right-click and select Delete from the submenu.
4. Click the Apply button. The Confirm apply dialog box is displayed. Confirm the deletion of the
filter. Close the Filters dialog box. Close the Select Filter filter dialog box by clicking the OK
button.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 46 of 70

Related topics

Viewing filter attributes

Requirements

No configuration mode is required.

To view the configured attributes for the filters, proceed as follows:

1. Display an Event List image. On the Event toolbar, click . The Select Filter dialog box is
displayed. Click the Filters... button. The Filters dialog box is displayed.
2. In the tree view, expand the applicable filter type. Select the filter you want to view. All attributes
of this filter is displayed when you expand the filter name.
3. Select an attribute, right-click and select View from the submenu. A dialog box containing all
options of the attribute is displayed. Thus, you can view which alarms that are filtered for this
attribute and filter.
4. If applicable, select other attributes and view them as described in step 3 above.

NOTE: Filters that are locked cannot be re-configured. (Locked filters have a padlock graphic
symbol.) Filters with attributes that may be reconfigured have associated dialogs with boxes, panes
and options that are available.

Editing filter attributes

Requirements

No configuration mode required.

Editing filter attribute

1. On the toolbar, click . The Select Filter dialog box is displayed. Uncheck the Use default
filter type box.
2. Click the Filters... button. The Filters dialog box is displayed.
3. Select the filter, which you want to edit. Right-click and select Add/Remove attributes from the

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 47 of 70

sub-menu. The Alarm Line filter attributes dialog box is displayed. Add or remove attributes as
required and press OK.
4. Click the Apply button. Close the Filters dialog box. Close the Select Filter filter dialog box by
clicking the OK button.

Related topics

Creating and editing alarm groups

Requirements

On the System menu, ensure that PS Configuration Mode is selected.

An alarm group must contain at least one alarm. Terminal alarms are allowed as members for all four
group types.

Alarm groups are organized in folders. It is advisable to structure the folders in a way which reflects the
structure of the process.

To avoid inconsistency it is important that all involved PSs are running when alarm groups are
configured.
It is vital to save the configuration for all the PSs when configuration is completed.
For information about how to save PS configuration; Save PS configuration (backup).

Definition of which PSs that are involved when creating and editing alarm groups:

A PS with terminal alarm added to or removed from any type of alarm group.

A PS with module terminal or IO-tag used in State Variable definition.

Any change in an Aggregated Group involves all PSs with members in this group.

To create a new alarm group, proceed as follows:

1. On the Tools menu, select Alarm Groups.... The Alarm Groups dialogue box is displayed.
2. In the Alarm Groups dialogue box select Edit from the Operation mode drop-down list.
3. Right-click within the graphic view pane and select New - Group Folder.
Enter the name of the group folder, which is free text, e.g the name of the process area.
4. Right-click on the folder and select New - Alarm Group - respective type of alarm group.
For description of the different types see Alarm groups dialogue box. Enter the name of the alarm
group.
5. Right-click on the Alarm group folder and select New- Alarm.
Enter the name of the alarm in the following syntax:
Digital terminal alarms: MOD.<tag name>/<terminal name>

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 48 of 70

Analog terminal alarms: MOD.<tag name>/<terminal name>/<state>, where state is specified

by the abbriviations LS, LL, L, H, HH or HS.
6. In the Alarm Groups dialogue box select Dynamic from the Operation mode drop-down list.
7. Save PS configuration for all involved PSs.

To edit an alarm group, proceed as follows:

1. On the Tools menu, select Alarm Groups.... The Alarm Groups dialog box is displayed.
2. In the Alarm Groups dialog box select Edit from the Operation mode drop-down list.
3. Right-click on a folder or an alarm and select the required edit function - cut, delete, copy, paste
or rename.
4. In the Alarm Groups dialog box select Dynamic from the Operation mode drop-down list.
5. Run a PS back-up to save your configuration.

Removing alarms from a group:

When the last alarm in a group is deleted, the group itself is deleted. This is because a group
cannot exist without members.
Similarly, a folder cannot exist without containing groups. The most efficient way of deleting a
substructure, is to delete its top level folder or group.

Creating and deleting Event List images

Requirements

On the System menu, ensure that OS Configuration Mode is selected.

Creating

To create a new Event List image, proceed as follows:

1. On the File menu, select New Image.... The New Image dialog box is displayed. Using the Type
drop-down list, select Event List. In the Name text box, type in the name of the new image and
click the OK button.
2. If the Event List image does not exist the Event List image properties dialog will be displayed.
Make your selections and close the dialog box. The new Event List image with the selected name
and properties is created and displayed.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 49 of 70

Deleting

To delete an Event List image, proceed as follows:

1. Display the Event List image you want to delete.

2. On the File menu, select Delete Image.... A dialog box containing the message 'This will
permanently destroy current image, continue?' is displayed. Confirm by clicking the OK button.
3. The Event List image is now deleted.

Reference information

The reference information section contains information regarding the commands and dialog boxes
related to the component. Titles are sorted alphabetically.

The dialog boxes may be displayed in different ways depending on the operation you are performing and
the sequence of commands executed. In the description of the dialog boxes only one of the possibilities
is given.

Dialog boxes Commands

Alarm Groups Acknowledge
Alarm Groups Properties Alarm Groups...
Alarm Line Filter Attributes Event Printer...
Alarm Shelving Filter...
Date and Time Print Events...
Define State Variables Select all
Event Printer Configuration
Event Printer
Filters
Free Text Search
Function Parameters
Lines
Overview of group folder
Properties for Events, Generic tab
Properties for Events, Popup tab
Purge unprinted events
Save alarms and events dialog box
Save Grid as Template

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 50 of 70

Select Expiration Time

Select Filter
State Variables

Acknowledge command
The Acknowledge command allows the user to confirm that he has observed the alarm indication
announced through the AIM system.

Method:

The Acknowledge command is available in the context menu of the Last alarm line whenever an alarm
is unacknowledged.
In addition, the icon is available in the event toolbar in the Event List image and the event dialog.

The effect of the Acknowledge command depends on the current image and current selection. Refer to
the Alarm acknowledgement description.

Alarm Groups... command

The Alarm Groups... command allows you to create and edit alarm groups, which contain selected
modules. The intention is to specify whether the alarm suppression shall be controlled by a terminal, or
by operating the module.

The command is available during normal operation.

Method:

On the Tools menu select Alarm Groups.... The Alarm Groups dialog box is displayed.

Event Printer... command

The Event Printer... command allows you to configure the event printer by displaying the Event
Printer Configuration dialog box.

The command is available in OS Configuration Mode.

Method:

On the Main menu select System - OS Configuration - Event Printer.... The Event Printer
Configuration dialog box is displayed.

Filter... command
The Filter... command is an option in the context menu of any alarm and event page in Event List image
and event dialog.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 51 of 70

The command is available during normal operation.

Method:

The option is equivalent to the button in the event toolbar.

Clicking Filter... displays the Select filter dialog box.

Print Events... command

The Print Events... command allows you to print all events that are contained in the buffer of the event
page printer by displaying the Event Printer dialog box.

The command is available during normal operation.

NOTE: This command is only available when the event printer of your configuration is a page
printer, for example a laser printer.

Method:

On the Main menu, select File - Print Events.... The Event Printer dialog box is displayed.

Select all command

The function let you select all currently displayed rows in the page. Rows that are not in the display
window, are not selected.

Method:

Select all is available from the context menu of event and alarm pages.

Date and Time dialog box

This dialog box allows you to define the time span for the events displayed on the Historic Event Page.

It is available during normal operation.

It may be displayed by the command <Event List image> - <Historic Event Page> - (Time span
icon).

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 52 of 70

Most recent time

The time span is defined relative to a specified date and time. The 'most recent time' is the reference.
This group contains controls for setting the most recent time.

Now sets the most recent time to the current time.

If you want another reference, use the calendar, and the Hour, Min and Sec controls.

And time span backwards

As the reference is the most recent time, the time span is defined in days, hours, minutes and seconds
backwards in time. Use the Days, Hours, Min and Sec text boxes.

Free text search dialog box

The Free text search dialog box allows you to search for a particular event message.

It is available when the OS Configuration mode is selected.

It may be displayed by the commanding <Event List image> - <Historic Event page> - <context
menu> - Free text search.

Show me an example

Lines dialog box

The Lines dialog box allows you to specify the number of lines in the current Event List image.

The dialog box is available in OS Configuration Mode.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 53 of 70

The dialog box may be displayed by the command: <Event List image> - <context-menu> - Lines…

Show me an example

Number of lines

Enter the number of rows to be displayed in the current page.

Properties for Event List dialog box - Generic tab

The Properties for Events dialog box allows you to configure the Event List image.

The dialog box is available in OS Configuration Mode.

The dialog box may be displayed by the command:in Event image File - Image properties.

Show me an example

Use Grid Template

The box is checked when you want to use a template for defining an alarm or event page.

Alarm Pages - Event Pages

There is a check box for each page type. When checked, the page is available in the event view,
independent of the context but not in the Last Alarm Line.

Show page names and navigation controls

When checked the page names and navigation controls are included in the event view.
When unchecked the page names and navigation controls are omitted in the event view.
The check box should be checked, whenever more than one page is made available.

Start Page

The list contains only those page types that are checked in the Alarm Pages and Event Pages groups.
The selected page is displayed as the active page when the framework that contains the event view is
displayed.

Number of lines

Enter the number of rows to be displayed in the current page.

Flush unacknowledged alarms

This box must be checked in order to make an unacknowledged alarm more distinguished by flushing
the alarm line.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 54 of 70

Enable dnamic values

When this box is checked two new columnswill appear on the dynmic and static alarm pages - 'Value'
and 'Unit'.

SysConf section

Since you can configure the columns in the Event List image, you can choose if the changes should be
saved on the OS you are working on or globally for the whole system.

Properties for Events dialog box - Generic tab dialog box

The Properties for Events dialog box - Generic tab dialog box allows you to define the size of the
popup window.

The dialog box is available during normal operation.

It may be displayed by the command Tools - Station Explorer - select PS - right-click - System Events
for node - Popup tab.

Show me an example

Save alarms and events dialog box

All alarms and/or events in the event view or a selection of alarms and/or events can be printed to file on
csv format.

In Event view - right click - context menu - Save to File...

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 55 of 70

The user must have the OSKEvent_ExportToFile permission before this entry is enabled.

The exported file can only be saved on the users document and settings area on the disc or to a
removable drive.

The available drives are displayed in the drop list at the top of the dialog.

The csv format can be imported into a text editor or spreadsheet for further analysis.

The alarm and events are exported on the same format as they are presented, with column order and -
names.

At the top of the file there will be information about the station from where the alarms and events were
exported, date and time, name of event view, name of event page and name of filter and filter type.

Save Grid as Template dialog box

The Save Grid as Template dialog box allows you to create a new template from an existing Event List
image grid.

It is available when the OS Configuration mode is selected.

It may be displayed by the command in <Event List image> - <context menu> - Save Grid as
Template.

Show me an example

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 56 of 70

Set Filter Parameters dialog box

The Set Filter Parameters dialog box allows you to define parameters for a filter.

It is available when the OS Configuration mode is selected.

It may be displayed by the command Add - Hotspot - Configure hotspot - Function: click in the white
field (auto prompt) - double click EventImage from dropdown window - write . (a point) - double click
SetFilter from dropdown menu - write . (a point).

Show me an example

Alarm Line filter attributes dialog box

The Alarm Line filter attributes dialog box allows you to view and edit filter attributes.

It is available during normal operation. Filter manipulation requires the AlarmChangeFilter

permission.

Display it by the command: Toolbar - Filter-icon - Select Filter - Filters… Right click on a filter type
- Add/Remove Attributes.

Not selected

The attributes that are still available, but not added to the filter.

>> > < <<

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 57 of 70

Use the arrows to select the attributes that are to be added to or removed from the filter.

Selected

The attributes that are added to the filter.

Filters dialog box

The Filters dialog box allows you to view and edit filter attributes.

It is available during normal operation. Filter manipulation requires the AlarmChangeFilter

permission.

It may be displayed by the command Toolbar - Filter-icon - Select Filter - Filters….

Show me an example

Filter explorer pane

The filter explorer pane represents the active filter fully expanded while other filters and filter types are
collapsed. You can browse all defined filters and the explorer reflects all actions taken in the dialog.
Double-clicking a filter attribute in the explorer, displays a dialog that contains all possible attribute
values and reflects the current settings.

The icon indicates that the filter is locked. Locked filters are system standard filters that can not be
modified.

Confirm irrecoverable operations

When checked, a confirmation dialog box pops up as you initiate an operation that not can be un-done.

Apply and Restore

Apply and Restore become available when you have made changes that are marked or . Restore
cancels the changes. Apply effectuates them. Both actions display a confirmation dialog.

Close

Close closes the dialog and discards all changes.

Select Filter dialog box

The Select Filter dialog box allows you to select a new filter.

It is available during normal operation. Filter selection presumes the AlarmChangeFilter permission.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 58 of 70

It may be displayed by the command Toolbar - Filter-icon.

Show me an example

Filters...

Clicking the Filters... button displays the Filters dialog box.

Filter name:

As the dialog is displayed, the list box identifies the filter currently applied in the actual page. Any other
filter - system and user-defined - within the same Filter type, can be selected from the list box. As you
enter a selection from the list, the new filter is activated for the actual page.

Filter type:

Initially, the filter type identifies the filter type that is currently applied in the actual page. Un-checking
the Use default filter type, changes it into a list box, containing the filter type alternatives. The system
defined filter types are: alarm filters, Event filters, and Horn filters. Upon selection of another filter type,
the Filter name alternatives are adjusted.

Use default filter type

When checked, the default filter type is automatically selected and filters of other types are not available
from the dialog box. The Filter name list box is than identical with the one displayed in the OS toolbar.

When unchecked, you can select any filter type and make the filters they contain available for selection.
Note that this is the only way to activate a filter that is not of the default filter type.

Alarm Shelving dialog box

This dialog box allows you to view all the acknowledged alarms that currently are shelved.

It is available during normal operation.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 59 of 70

It may be displayed by the command: Select the acknowledged alarm, which you wish to shelve and
right-click to display its context menu. Click Shelve Alarm... - Select Expiration Time - check Show
list of shelved alarms box - OK.

Show me an example

Refresh

This command allows you to refresh the list of shelved alarms.

Print...

This command allows you to print all the current shelved alarms. The information contents is the same
as the list in the dialog box above.

Remove

This command restores the selected alarm from the alarm shelf to the Event List image.

Edit...

This command allows you to edit he expiration date and -time for the selected shelved alarm.

Select Expiration Time dialog box

This dialog box allows you to select the expiration time for an acknowledged alarm, which you want to
shelve.

It is available during normal operation.

It may be displayed by the command: Select the acknowledged alarm, which you wish to shelve and
right-click to display its context menu. Click Shelve Alarm....

Show me an example

Expiration time

Two boxes for selection of the expiration time for the selected shelved alarm are supported:

Left box: Select the expiry date from the drop-down list (month, day, year).

Right box: Select the hour, minute and second.

NOTE: The time format depends on Windows settings.

Show list of shelved alarms

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 60 of 70

When this box is checked, the Alarm Shelving dialog is opened and refreshed with the current shelved
alarms.

Event Printer Configuration dialog box

The Event Printer Configuration dialog box allows you to define the properties of the printer where
all events are printed

It is available when the OS Configuration Mode is selected.

It may be displayed by the command System - OS Configuration - Event Printer...

Enable event printer:

The check box must be checked to enable the event printer.

Apply button:
Apply changes made in the configuration.

Filter

Type/name:
The text box indicates which filter is applied before printing. I.e. only events that pass the filter are
printed. Click the Edit... button if you want to select or specify another filter.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 61 of 70

Edit...
The Edit... button invokes the Select filter dialog.

Printer properties

The Printer properties group contains the controls that define the output device and format:

Name:
The text box indicates the actual printing device, which is either a printer or a file.
To select a printer, select one of the printers listed in the list box.
To select a file, click the ... control and specify the path and filename in the standard file system explorer
dialog. As you specify a file, the Properties button is disabled.

Type:
The Type input box reflects the type of output device and should correspond with the device specified in
the Name box. I.e. If the event printer is a line printer, the Type input box should be set to 'Line Printer'.

Font:
The Font list box let you select among a set of predefined fonts.

Support norwegian characters (Line Printer Type)

The check box must be checked to enable printing of the Norwegian characters Ø, Æ and Å.

Print column headers (Page Printer Type)

Each page will on the top contain column headers.

Print individual alarms from redundant nodes

Alarm messages -representing the same alarm situation- for every node in the redundancy group, will be
printed.

Enable periodic page printing (Page Printer Type)

Set up at which time a page with alarms and/or events shall be printed and at which period.
A page is normally not printed before it is full.
Enable periodic printing to print alarms and/or events periodically to force not fully filled pages to be
printed.

Unprinted events

At one side of the event print mechanism, incoming events that pass the filter, are stored in a buffer. At
the other end, the buffer is drained as events are send to the printer. Buffering is required as printer
performance does not match the rate of event occurrences.

The group contains the following controls:

Buffer length:
The text box indicates the buffer capacity. You can resize the buffer by entering a new value in the text
box.

Current number of events:

The text box indicates the number of events stored in the buffer at the moment the dialog was invoked or

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 62 of 70

refreshed.

Refresh
Clicking the Refresh button updates the number of events in the buffer.

Purge...
You can purge the buffer - that is - cancel the printing of events in the buffer. Clicking the Purge...
button displays the Purge unprinted events dialog.

Keep oldest event when buffer full

Overwrite oldest event when buffer full
As the buffer runs full, some events will not be printed. There are two ways to handle buffer overflow
and each of them is represented by an option box:

You can keep the events in the buffer and inhibit new events from being stored.

You can overwrite events that are stored in the buffer, thus skipping the oldest unprinted events
but keeping the most recent ones.

Event Printer dialog box

This dialog box allows you to perform a printout of all the unprinted events in the buffer of the event
page printer.

NOTE: This dialog box is only available when the event printer of your configuration is a page
printer, for example a laser printer.

It is available during normal operation.

It may be displayed by the command File - Print Events....

Unprinted events:

This text box shows the number of un-printed events in the event printer buffer.

Refresh

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 63 of 70

This button is used to update the information shown in the dialog box. Clicking this button causes the
name and type of the dedicated event printer as defined in the Event Printer Configuration dialog box to
be shown in the Printer name and Printer type fields. It also causes the current number of un-printed
events in the event printer buffer to be read and displayed in the Unprinted events text box.

Flush

Clicking this button sends the un-printed events in the event printer buffer out to the event printer.

Purge...

Click this button to open the Purge unprinted events dialog box

This button will only be enabled if the user has the OskEvent_CanPurge permission.

Printer name:

This field shows the name of the event printer.

Printer type:

This field shows the type of the event printer.

Purge unprinted events dialog box

This dialog box allows you to clear the events which are not yet printed.

It is available when the OS Configuration Mode is selected.

It may be displayed by the command System - OS Configuration - Event Printer... - Event Printer
Configuration - Purge....

Show me an example

The Purge unprinted events dialog box lets you specify which events to purge. The alternatives are:

All

Select this option when you want to purge the entire queue of events in the buffer.

Older than

Select this option and fill in the number of days. Only those events that are older than the specified limit
are purged.

Alarm Groups dialog box

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 64 of 70

The Alarm Groups gives an overview of all the alarm goups in the system and allows you to define
and/or edit alarm groups.
There are four different types of Alarm groups

It is available during normal operation. PS Configuration Mode together with Operation Mode Edit is
required for editing.

The dialog box is opened by the command Tools - Alarm Groups

Graphic view pane

Alarms are always shown with a colour that indicates its priority.
Logical groups and First-Up groups are shown with a colour that indicates whether they are
suppressed or not.
Aggregated groups and Collective groups are shown with a colour indicating the level of the
aggregated or Collective alarm.

Refresh

The Alarm Groups dialog box present static data. Refresh button must be used for updating with new
data from the PSs.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 65 of 70

Refresh button can also be used as an "Undo" function for leaving Edit mode without deploying
changes.

Print

Prints a bitmap version of this dialog box.

State variables

Opens the State Variables dialog box.

Operation mode

Used for selection between the two modes; Dynamic and Edit.
Dynamic mode is the default operation mode. After editing Alarm Groups the Dynamic mode must be
selected to deploy the changes.
Edit mode is required for making changes in the Alarm Groups.

Related Topics

Overview of group folder - tabular format

Alarm Groups Properties dialog box

The Alarm Group Properties allows you to define the alarm settings for the Aggregated alarm and for
the Group alarm.
For a Logic alarm group the logical expressions is defined. The First Up group do not have any group
properties.

It is available during normal operation. For editing PS Configuration Mode and Edit operation mode is
required.

Open the dialog box by selecting Properties in the context menu for an alarm group; right-clicking of an
alarm group folder in the Alarm Group dialog box.

Resulting alarm

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 66 of 70

Applicable for Aggregated and Group alarm groups.

The group alarm is defined by Tag name, Priority, Command group and Alarm text, as any other process
alarm.

Logic expression

Applicable for Logic alarm groups.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 67 of 70

The logical expression is made by inserting predefine State Variables.

Show expanded expression; for displaying the expression from which the State Variables are made
from.

Show expanded expression must be deselected to make the Insert Variable... button available.

Insert Variable

Select wanted variable from the set of predefined State Variables.

Define State Variables dialog box

Define State Variables allows you to define new state variables.

PS configuration mode is required for editing State Variables.

The dialog box is opened from: Alarm Groups dialog box - State Variables - Define

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 68 of 70

Id

An automatically generated ID number for the new variable.

Name

The name you choose for the new variable.

Expression

The logical expression for the variable.

Variables can be eigther from digital module terminal, syntax: MOD.Tag/Term or a digital IO-tag,
syntax: IO.<IOTag>

The State Variable can be made from a single variable or from logical expressions of variables.
MOD.<Tag>/<Term> OR (MOD.<Tag>/<Term> AND MOD.<Tag>/<Term>).

PS configuration mode is required and PS configuration must be saved after changes.

Saving PS configuration (backup)

Overview of group folder dialog box

The Overview of group folder lists all groups with the alarm members for a folder.

It is available during normal operation. PS Configuration Mode and Edit operation mode is required
for editing.

Open the dialog box by selecting Properties in the context menu for a folder; right-click on a folder in
the Alarm Group dialog box.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 69 of 70

Print

Prints a bitmap version of this dialog box.

State Variables dialog box

The State Variables dialog box list all existing state variables which can be used by Logic alarm
groups.
The dialog is available from Alarm Groups dialogue box.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13

Alarm and event system Page 70 of 70

Define is used for creating new variables, Delete for removing existing variables.
PS configuration mode is required and PS configuration must be stored after changes.

Define

The Define State Variables dialog box enables you to define new variables.

Delete

Deletes variables.
It is not allowed to delete a variable used by Logic Alarm Group; Message Pop-Up will be given.

file://C:\Documents and Settings\dpos\Local Settings\Temp\~hh376C.htm 04.Nov.13