L-DALI User Manual
124
LOYTEC
Version 5.2
LOYTEC electronics GmbH
The setting is stored in the project and will be applied again with the next generation. The
project settings also provide defaults for auto-generation. How exactly data points are
created depends on the target technology. Refer to the technology sections for more
information how data points are used in connections.
For more advanced connection tasks that involve specific adaptors
auto-generate templates
must be used. An auto-generate template contains the source data point, the desired target
data point and the local connection with all appropriate adaptors. There are two types of
auto-generate templates:
Simple auto-generate template
. This template contains exactly one source data point
(scalar or structured). It may contain one or more target data points, which will be
generated. This template can be applied on any selection of single source data points. If
the type of the source data point matches the one in the template, this auto-generate
template can be selected to generate the target data points. This template type can be
used to generate special target objects for certain scalar source data points using
adaptors. It can also be used to connect structure elements of the source to structure
elements of a target using a math block adaptor.
Complex auto-generate template
. This template contains more than one source data
points. This type must be used, if two or more sources shall generate the targets in a
specific way. Since no single source data points can be matched in this case, the source
data points which belong together must be grouped under a folder. Math block adaptors
can be used with complex auto-generate templates.
Auto-generate templates can use configurable placeholders for data point name, data point
description, server object name, server object description. These placeholders are evaluated
when the template is applied and new data point instances are created. The available
placeholders are listed in Table 15.
Placeholder
Meaning
%{name}
In simple auto-generate templates this expands to the source data point name.
%{descr}
In simple auto-generate templates this expands to the source data point description.
%{native_name}
In simple auto-generate templates this expands to the native name (e.g. register name,
NV programmatic name, server object name) of the source data point. If no such native
name exists, the data point name is used instead.
%{native_descr}
In simple auto-generate templates this expands to the native object description (e.g.
server object description) of the source data point. If no such native description exists,
the data point description is used instead.
%{path}
This placeholder expands to the source data point/folder path. The path extends up until
the respective data point folder root folder. Example: The source data point is located in
‘CEA-709 Port.Datapoints.Floor1.Room202’. The path expands to ‘Floor1.Room202’.
Table 15: Placeholders in auto-generate templates.
6.3.4
Global Connections
Global connections provide the same notions as local connections but extend beyond the
scope of one device. A global connection establishes a data cloud with a system-wide name.
Data points added to a global connection can send data into that connection or receive data
from the connection. The data is transferred over an IP-based network. All data is
automatically matched by the global connection name. This makes global connections
especially useful to provide certain global data in a system, without knowing who will be
reading that data. Examples are weather station data, wind alarms or global on/off.
Global connections cannot use adaptors for conversions as in local connections. If
conversions are needed, an intermediate register data point must be used to receive/send
data from/to the global connection. The adaptor needs to be installed with a local
connection between the register and the data point, which requires the conversion.