L-Proxy User Manual
62
LOYTEC
Version 3.1
LOYTEC electronics GmbH
3.
Select data points and create connections.
The CEA-709 NVs on the L-Proxy can be created in three different ways:
•
Static NV
: For each selected NV on the network there is a static NV created on the L-
Proxy. This NV can be bound to the NV on the network. Note that adding static NVs
to the L-Proxy results in a change to the default XIF file. The L-Proxy is assigned a
new “model number” to reflect this change (see Section 6.5.2). Static NVs are the way
to use NVs in non-LNS systems, where NVs shall be bound instead of using polling.
•
Dynamic NV
: For each selected NV on the network there is a dynamic NV created on
the L-Proxy. Compared to static NVs, dynamic NVs do not change the XIF interface
of the L-Proxy. The dynamic NVs are created by the network management tool.
Currently, only LNS-based tools can manage dynamic NVs. As for static NVs, with
dynamic NVs it is possible to use bindings instead of polling.
•
External NV
: The selected NVs on the network are treated as external NVs to the L-
Proxy. The L-Proxy doesn’t create any NVs on the device, but instead uses polling to
read from those NVs and explicit updates to write to the NVs. Therefore, no bindings
are necessary for external NVs. For input data points using external NVs however, a
pollcycle must be configured. If not configured explicitly, a default pollcycle of 10 sec.
is chosen. The default pollcycle can be changed in the project settings menu.
Based on the NV the data point is derived from, the following kinds of data points are
created:
•
Simple NVs that hold only one scalar value, e.g., SNVT_amp: Those kinds on NVs are
represented as analog data points. The data points holds the current value, NV scaling
factors are applied.
•
Simple NVs based on an enumeration, e.g., SNVT_date_day: Enumeration types result
in multistate data points. They represent the state of the NV.
•
Structured NVs that consists of a number of fields, e.g., SNVT_switch: All structured
NVs are represented as user point. That is, the data point is structured similar to the
NV it is based on. Beneath the user data point, the individual structure fields are
presented as “sub-data points”.
For more information on the different types of network variables and their implications
please refer to the application note in Section 13.2. For CPs the allocation type “File” is
used.
6.5.2 Static Interface Changes
The L-Proxy can be configured to use static NVs. Unlike dynamic NVs, static NVs cannot
be created in the network management tool. They are part of the static interface and are
usually compiled into the device. When static NVs are used, the L-Proxy changes its static
interface and boots with a new one.
Each time the static interface of the L-Proxy changes (i.e., static NVs are added, deleted, or
modified), the model number is changed. The model number is the last byte of the program
ID. Thus, a change in the static interface results in a change of the program ID and a new
device template needs to be created in the network management tool. A new device
template usually means that the device has to be deleted and added again in the database.
All bindings and dynamic NVs have to be created again for the new device.
When the Configurator software is connected via LNS, it supports the process of changing
the device template for the new static interface. It automatically upgrades the device
template of the L-Proxy device in the LNS database and restores the previous bindings and
dynamic NVs. If the L-Proxy is not configured with an LNS-based tool, this support is not
available. The new static interface is only available in a new XIF file or by uploading the
Summary of Contents for L-Proxy
Page 1: ...L Proxy CEA 709 Gateway User Manual LOYTEC electronics GmbH ...
Page 10: ......
