User Manual

67/90
Building Technologies Integration of DESIGO™ RXC CM2Z8338en_01
Building Automation Engineering 12.06.2006
Network variables can be integrated as single parameters, provided that:
- the RXT10 tool knows the application concerned
- the allocation from input (nvi) or output (nvo) on the NIDES.RX side to the link point
element address is defined. Caution: This only applies to some of the NVs shown in
the NIDES.RX window (target). NVs not documented in Tables 4.10.1 and 4.10.2 are
excluded from single parameter integration.
The network variables of RXC applications for which an integration function is proposed
(see Sections 3.2.3 to 3.2.28) are excluded from single parameter integration.
For third-party devices (device numbers equal to or greater than 128), the integration
functions are disabled. This means that all the NVs documented in Tables 4.10.1 and
4.10.2 can be integrated as single parameters.
To integrate a single parameter, an appropriate binding must be created using the
Binding Template Editor of the RXT10 tool. In this process, only the input/output on the
NIDES.RX side is relevant for integration purposes. In conjunction with Device No. x, it
defines the associated link point.
The source for the input/ouput on the NIDES.RX side can be selected freely, provided it
is of the same SNVT type. When the project is saved, the RXT10 tool generates an
entry for each binding of this kind in the configuration file RxNiBps.col for the BPS.
If the nvi/nvo has not been allocated to a link point, an error message will appear:
Caution: Before you continue to work, please delete this binding or change to another
one. During the save operation, the above pop-up must not appear.
Otherwise the stability of the application will suffer seriously.
The NIDES.RX-CFE software automatically generates the link point associated with the
binding, on the basis of the entry in file RxNiBps.col.
When it is generated, every link point is assigned a text number TXI2 (Information Text,
Part 2) in the range Ig1001 to Ig1408 of the global VISONIK text catalog. This range
includes the names of all the network variables that can be integrated. The name of the
relevant NV is therefore shown for each integrated single parameter in the BPS and
DCS reports.
Example: If the NV Application Mode is integrated, the following display appears in a
DIR @AO on the BPS.
@AO128'26 ; -- nviApplicMode
Note that here, the NV is qualified as an input (on the device side).
The direction of data flow is unambiguously defined by the type of link point.
The text items required are normally loaded from the DCS to the BPS via the DCS
command LoTx. This presupposes that all the link points of the project have already
been generated on the DCS and that they have all been assigned the correct text
numbers. In other words, the text must not be loaded until the process image has been
created in the DCS (Command SaPa). Refer to the section on “Commissioning the
BPS” in the Engineering Guide.
Restrictions affecting
single parameter
integration
Engineering the
single parameters
Text commentary for
link points
Text download
SAPIM text label,
identifying the nvi / Gnvo
.
.
.
.
.
.
.
.