L-VIS User Manual
181
LOYTEC
Version 6.2
LOYTEC electronics GmbH
The following properties are available as property relations:
feedbackValue:
This property relation is used for feedback alarm conditions.
The data point value is compared against the feedback value. An alarm is
generated, if these values differ (by a certain amount). It exists only, if an alarm
condition has been created.
enableAlarm:
This property relation is used to enable or disable alarm
generation on the data point. It exists only, if an alarm condition has been
created.
inAlarm:
This property relation is TRUE, if the data point is in an alarm. It
exists only, if an alarm condition has been created.
ackPend:
This property relation is TRUE, if the data point’s alarm needs
acknowledgement. It exists only, if an alarm condition has been created.
highLimit:
This property relation defines the high limit for analog alarms. It
exists only, if an alarm condition has been created.
lowLimit:
This property relation defines the low limit for analog alarms. It exists
only, if an alarm condition has been created.
deadband:
This property relation defines the dead band for analog alarms. It
exists only, if an alarm condition has been created.
nativeAlarm:
This property relation links to a technology data point, which is
required for alarms reported to another technology. It exists only, if an alarm
condition has been created and alarms are reported to the given technology (e.g.
BACnet). This property relation cannot be modified by the user.
reportTo:
This property relation exists only in generic alarm servers. It may be
linked to a technology alarm server to report alarms to that network technology.
totalActive, totalUnacked, totalAcked:
These property relations exist only in
alarm servers. They contain counters for active unacknowledged, inactive
unacknowledged, active acknowledged alarm records of the alarm server,
respectively.
ackAll:
This property relation exists only in alarm servers. When writing TRUE,
all alarms on that alarm server are acknowledged.
historicFilter:
This property relation exists for data points that have at least one
historic filter assigned (see Section 10.3.5).
enable:
For Schedulers can be enabled or disabled by the use of this property
relation. If the enable data point has been defined in the scheduler’s
configuration, this property relation is linked to that data point.
enableFb:
This property relation shows the enable state of the scheduler. If the
enable feedback data point has been defined in the scheduler’s configuration, this
property relation is linked to that data point.
presetName:
This property relation of type string shows the preset name of the
currently scheduled value. If the preset name data point has been defined in the
scheduler’s configuration, this property relation is linked to that data point.
timeToNext:
This analog property relation contains the number of minutes till
the next scheduled state changes. It can be used to implement an optimum start
algorithm.
nextState:
This property relation contains the next scheduled state. It can be used
to implement an optimum start algorithm.
nextPresetName:
This property relation contains the preset name of the next
scheduled state, if such name exists. Otherwise it stays at invalid value.