L-VIS User Manual
239
LOYTEC
Version 6.2
LOYTEC electronics GmbH
Enter a name for the calendar point, a name for the input NV which will be used
to connect the calendar from another device to this data point, and select the
desired functional block in which the NV should be located.
Press OK to create the calendar point (repeat for more calendar points if
required). There should be one calendar point for each device from which
schedule data is viewed, since the calendar point will carry the information about
exception days used in the schedules.
Select the data point folder named
Scheduler
and use the context menu to create a
New Remote Scheduler
point. Enter a name for the data point, a name for the
input NV which will be used to connect the point to a scheduler server and select
the functional block in which the NV should be located.
Press OK to create the scheduler point and repeat for additional points as
required. Each of the created scheduler points will later provide access to the
configuration of the scheduler unit to which the scheduler link NV was bound in
the network (see below).
On CEA-709 devices, there is one extra step to take before the new data points will be
operational: The new static input NV representing the remote calendar on the local device
(this NV is normally called
nviCalLink
) needs to be bound to the output NV called
nvoCalLink
located in the Calendar functional block of the remote device and the new static
nviSchedLink
NVs which were created for each remote scheduler point need to be bound to
the respective
nvoSchedLink
variable located in the Scheduler functional block of the
remote device. The binding between the
nvoSchedLink
variable on the remote device to the
nviSchedLink
variable on the local device defines which of the scheduler data points on the
local device connect to which scheduler unit on the remote device.
On BACnet devices, the new data points can be used right away to exchange configuration
data with the scheduler on the remote device. Just connect the new scheduler data point to a
schedule control to view and edit the configuration of the remote devices scheduler.
10.14.2 Alarm Clients
Accessing alarm server objects on remote devices is done by creating remote alarm data
points. These points may either be created from data obtained by a network scan, or can be
created manually (CEA-709 only). Here are the steps to create the required points from a
network scan:
Execute a network scan, as described earlier in this document.
From the points in the import folder, select the alarm server points you are
interested in and use the command
Use on Device
to create suitable alarm client
points in your project.
For CEA-709, select the new alarm client point and adjust the name of the local
NV (default name is nviAlarm_2). Also, you may assign this NV to one of the L-
VIS functional blocks as required.
NOTE:
Due to the static input NV which is required for a CEA-709 alarm client point, adding
alarm clients will change the static interface of the device.
To keep the project reusable in different networks, it is desirable to create the remote alarm
data point manually on CEA-709 devices and define the connection to the alarm server by
the network binding only. Instead of using data from a network scan, a remote alarm data
point can be created as follows:
