L-INX User Manual 88 LOYTEC
Version 4.0 LOYTEC electronics GmbH
m inputs data points are connected to 1 output data point.
The most common connection will be the 1:1 connection. This is the type of connection that
is auto-generated by the Configurator software. Other types must be created manually in the
Configurator.
In the 1:n connection the input value is distributed to all n output data points. In the m:1
connection, the most current input value is written to the output data point. When polling
the output data point in poll-through mode (maximum cache age is set on the output), the
value from the first input data point is polled.
Connections can connect data points of different technologies with each other (also mixed
among the target data points) but are restricted to the same class of data points. This means
only data points of class analog can exchange values within a connection.
For certain classes of data points, additional restrictions exist:
Analog: The value range is capped on the output data points. This means, if the input
value in the hub does not fit into the range of an output data point, the value is capped
to the biggest or smallest allowed value.
Binary: No special restrictions exist.
Multi-state: Only multi-state data points of an equal number of states can be placed
into a connection. The actual state Ids need not be equal. They are ordered and the n-th
state is propagated over a connection. For example, the 2nd state on the hub has the
state ID ‗2‘, while on the target the 2nd state has the state ID ‗0‘.
String: No special restrictions exist.
User: Only user data points of the same length can be placed in a connection.
5.3 AST Features
5.3.1 Alarming
The alarming architecture comprises a number of entities. Objects that monitor values of
data points and generate alarms depending on an alarm condition are called alarm sources.
The alarms are reported to an alarm server on the same device. The alarm server maintains
a list of alarm records, called the alarm summary. The alarm server is the interface to access
the local alarms. This can be done over the network or the Web UI.
An alarm record contains the information about the alarm. This includes information about
the alarm time, the source of the alarm, an alarm text, an alarm value, an alarm type, an
alarm priority, and an alarm state. An alarm record undergoes a number of state changes
during its life-cycle. When the alarm occurs, it is active. When the alarm condition subsides,
the alarm becomes inactive. Active alarms can be acknowledged by an operator. Then they
become active acknowledged. Active alarms can also become inactive, but an
acknowledgement is still required. Then they become ack-pending. When an alarm is
inactive and was acknowledged it disappears from the alarm summary.
Other devices can access the alarm information of an alarm server. These devices are alarm
clients. They register with the alarm server and get notified about changes to the alarm
summary. Alarm clients can be used to display the current alarm summary and acknowledge
alarms.
Depending on the underlying technology, some restrictions to the available alarm
information and acknowledgement behavior may exist.
To Next Page
Loading...