L-INX User Manual
97
LOYTEC
Version 4.0
LOYTEC electronics GmbH
Feedback_Value property available, alarm conditions cannot be defined for binary output
(BO) and multi-state output (MSO) objects.
Alarm servers in the BACnet technology are mapped to BACnet Notification Class (NC)
objects. Each alarm server is mapped to one NC. The notification class number can be
configured in the object instance number property of the alarm server object.
Remote alarms in the BACnet technology refer to a remote NC object. When the device
starts up, the remote alarm object reads out the current alarm state of the remote NC and
reporting objects. To get notified about alarm transitions during run-time, the device
registers in the Recipient_List of the remote NC object.
5.5.3 BACnet Schedulers and Calendars
BACnet schedulers and the BACnet calendar adhere to the standard schedule and calendar
object in BACnet. For each scheduler a BACnet Schedule object is created. The calendar
deserves a closer look. For each calendar pattern a BACnet Calendar object is created. The
visible calendar on the Web UI is therefore a collection of BACnet calendar objects. Each
calendar pattern therefore is associated with a BACnet object instance number. The
calendar pattern ―Holidays‖ is for example visible as CAL,1 on the BACnet port.
The BACnet schedule object allows only objects of one selected data type to be scheduled.
Therefore, schedulers on BACnet can only schedule one class of data points (e.g., only one
group of analog data points). As a consequence, the value preset in BACnet always has only
one element. The name of the value preset is not stored in BACnet. It is not accessible over
the BACnet network, either. Therefore, a default name is created, such as ‗Value(22)‘ for an
analog value. An example of two scheduled BACnet objects is shown in Figure 79.
Figure 79: Example value presets in BACnet schedulers.
Priorities of exception days in a BACnet scheduler range from 1 (the highest) to 16 (the
lowest). Weekdays in BACnet have no priority.
Changing the number of calendar patterns in a BACnet calendar can only be done through
the configuration software and not during run-time. The individual calendar pattern entries
in the calendar patterns can be changed at run-time. Therefore, it is advisable to reserve a
suitable number of calendar patterns in a BACnet calendar and leave them empty if not
needed immediately.
5.5.4 BACnet Trend Logs
Trending in the BACnet technology is based on the BACnet TrendLog object. A number of
restrictions apply to trend log objects in BACnet. Trend log objects must be created by the
Configurator software. These objects are accessible over the BACnet network for other
BACnet devices and operator workstations (OWS). All configuration properties can be
modified by the Configurator software as well as an OWS. The number of trend log objects
cannot be changed at run-time. Therefore, if it is intended that an OWS configures the trend
logs, a suitable number of empty trend log objects (i.e., without attached data points) must
be created in the Configurator software.
In BACnet trend logs, only one data point can be trended per trend log object. The trended
data point can be either a local BACnet server object or a remote BACnet object accessed
through a client mapping. Data points of other technologies and the min/max/avg algorithms
cannot be trended in this firmware version.
