Location:
<WorkspaceDirectory>\DataFiles\nxaClusterItem.40.dat
Using the cluster item definition file, the different datapoints that shall be integrated into the NETx BMS Core Server are specified.
The structure of the cluster item definition file is as follows:
' Cluster Item Definition File
'
' ServerName;ItemID;Description;ReadInterval;Autorefresh;Persistent;Historical;Backup
OPCX;OPCItem1;\Path\To\Item;Foreign OPC Item 1;1000;F;F;F;F
NETxOPC;KNXItem1;\NETxKNX\BROADCAST\04/0/001;0;T;F;F;F
NETxSubBMS1;Item1;NETx\XIO\Modbus\Controller1\Input Registers\5000;0;T
NETxSubBMS2;Item2;NETx\XIO\BACnet\Device0\BINARY0\BINARY0;0;T
Each line – except comment lines that start with ' – defines a single datapoint that shall be integrated into the NETx BMS Core Server.
| 1 | ServerName | This is the name of the server that provides the datapoint. It has to match the name that is used in the cluster server definition file (cf. Section 4.4.1.1). | |
| 2 | ItemID | Here the ItemID that is used within the foreign server to identify the datapoint has to be specified. | |
| 3 | Description | This parameter specifies the description of the datapoint. | |
| 4 | ReadInterval | Using this parameter, the polling inter- val that is used to cyclically read the datapoint within the remote server can be specified. If it is set to "0", cyclically reading the value is disabled. | |
| 5 | Autorefresh | If this parameter is set to "T", the NETx BMS Core Server subscribes to the datapoint within the remote server. Using subscription, data changes are automatically pushed from the remote server to the NETx BMS Core Server. If the remote server is a NETx BMS Core Server (ServerType is set to "VNET"), then subscription is always used. | |
| 6 | Persistent | This parameter specifies whether the value of the datapoint is persistent (restored from the database after server start up ) or not. | |
| 7 | Historical | This parameter specifies whether historical values of the datapoint are stored within the database or not. | |
| 8 | Synchronize | If this parameter is set to "T", the value is synchronized between the main and backup server (if present). This will work only if synchronize is enabled in the NMESH configuration of the NETx BMS Core Server. |