Bender FTC470XET, Руководство по эксплуатации

Страница: 57 / 84

57 TGH1375en/02.2010
8. Application of the internal OPC server
8.1 Function
The FTC470XET contains a network-capable OPC server continuously providing the alarm
and operating messages of the BMS bus being monitored. For retrieving this OPC data, an
appropriate client is to be used. The data is provided by the OPC server as items. Parallel
access of several clients is possible.
If devices are added to or removed from the BMS bus, the update of the OPC server data
(Items) can be carried out in the following way:
- an update of the BMS explorer of the internal Web server is to carried out or
- the FTC470XET has to be restarted.
Only then, the OPC server is able to provide the actual data.
Data available in OPC format can then also be processed using a suitable visualisation soft-
ware of automation technology. BENDER uses the visualisation software Wizcon Application
Studio, Axeda Systems Inc. and the application Studio from Advantech.
8.1.1 OPC specification
The FTC470XET server supports the OPC specification Data Access 2.0.
An OPC client must meet the requirements of the respective specification in order to be ca-
pable of retrieving data from the BMS bus.
8.1.2 OPC data structure
The hierarchy of the OPC data structure is as follows:
The first elements of the items are the BMS address and the respective BMS channel. The
following screen shot illustrates the link of this data to the Items.
A summary of the correlation between the BMS device, the BMS channel No., the BMS data
type and BMS data value provide the tables in "chapter 8.4 Channels, data types and data
values of BMS devices".
Node = IP address of the FTC-OPC server e.g. 172.17.60.11
Group = can be named as required e.g. device name, BMS address, etc.
Items = Value Item
= Type Item
= Alarm Item
= Active Item
BMS data value
BMS data type
BMS alarm (0 or 1),
(2 = device error)
BMS operating state (0 or 1)