7. Events Menu
Introduction
An event is a special message that is generated on the card asynchronously. This means that it is not the
response to a request to the card, but a spontaneous message.
What is the Goal of an Event?
The goal of events is to inform the environment about a changing condition on the card. A message may
be broadcast to mark the change in status. The message is volatile and cannot be retrieved from the
system after it has been broadcast. There are several means by which the message can be filtered.
The events reported by the card are as follows:
Menu Item
Description
Announcements
Announcements is not an event. This item is only used for switching the
announcement of status changes on/off. 0=off, other =on
What Information is Available in an Event?
The message consists of the following items:
•
A message string to show what has happened in text, for example: “INP_LOSS”, “REF_LOSS”, “INP_
RETURN”.
•
A tag that also shows what happens, but with a predefined number: e.g. 1 (= loss of input), 2 (= loss
of reference), 129(= 1+128 = return of input). For a list of these predefined tags, please see the table
below.
•
A priority that marks the importance of an event. This value is defined by the user and can have any
value between 1 and 255, or 0 when disabled.
•
A slot number of the source of this event.
Message String
The message string is defined in the card and is therefore fixed. It may be used in controlling software
like Synapse Set-up to show the event.
Tags
The tag is also defined in the card. The tag has a fixed meaning. When controlling or monitoring software
has to make decisions based on events, it is easier to use the tag instead of interpreting a string. The
first implementation is the tag-controlled switch in the GPI16.
40
| December 2021 | Issue 1.00.B
