2
Concepts
, functions and gateway design
UGW X-series
Concepts, functions and gateway design
11 of 66
2.5.2
Data point files
The data points to be used and the properties these data points should have are determined in the
data point file of each protocol. The file name is derived from a protocol-specific part of the name, a
serial number, which is numbered in the event of multiple connections for the same protocol, and
the extension *.txt.
Example: eib1.txt
and
eib2.txt
.
The name of the protocol-specific part is mentioned in the description of the designated protocol. The
address of the data point serves as the section’s name. An abbreviation of the address is used. Since the
routing address and the data point type have already been determined by the file, they are not indicated
again. This means that the full address
60.X eib 2/3/5
is written in the data point list as
X 2/3/5
.
The use of the following keywords is standard:
Table 2: Keywords in the data point files
name
Optionally, you can specify plain text for the data point here. The text is usually only used
for commentary purposes within the gateway. In some protocols, e.g. BACnet, the text is
used in the protocol.
format
Optionally, protocol-related properties of the data point are described here which cannot be
derived solely from the address. For example, it is common to transfer analogue values of
many protocols using a scaling factor. This scaling factor must be specified in the
configuration so the gateway can interpret this value correctly (protocol-dependent).
writecache
Optional; possible values are YES or NO (default). This parameter only has meaning for
those parameters whose value is described by the gateway. If YES, the gateway remembers
a value during a failed entry and repeats its entry attempt when, for example, the
connection to the device has been restored. If this option is missing or its value is NO, the
value is discarded after a failed entry.
Usage scenario: Transfer of a binary fault visual via EIB. If the EIB bus is not connected to
the gateway at the time of occurrence of the failure, the gateway cannot report the failure.
When the connection is restored, the fault condition should generally be transmitted
afterwards, at the least.
Scenario in which this behaviour is not desired: switching of room lighting. If at the time of
the switching the EIB does not work, switching is not to take effect after the event (e.g. after
several days).
query
Specifies how the data point should be picked up via the corresponding protocol. With only
a few exceptions, which are described separately, the value permanent (
pe
) is used here
(default).
Other
options
For some protocols, there are other options that need to be projected at this point. The
description can be found in the documentation on these protocols.
2.5.3
Configuration files
The file name is derived from a protocol-specific name, a serial number, which is numbered in the
event of multiple connections for the same protocol, and the extension *.cfg.
Example
:
eib1.cfg
and
eib2.cfg
The name of the protocol-specific part is mentioned in the description of the designated protocol.
General communication parameters for each connection are established in the configuration file.
Typically, information such as baud rate, individual addresses or poll rates should be indicated. The
content consists of a section with a protocol-specific description and configuration entries.
