Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The NETx BMS Server provides a clustering module, which integrates datapoints from alien OPC DA Servers or other NETx BMS Servers through the OPC DA protocol.The datapoints to be synchronized with this server instance are selected with the discovery tool, the Cluster Explorer.

Shut down the NETx BMS Server and select the menu item Cluster / Start Explorer ... within the NETx BMS Studio.

This will start the Cluster Explorer. To add a new server, click the Add icon . The Server Definition window will show up. 


Important

An OPC Server can be running either locally on the same PC or on a remote PC. Integration of a local OPC server can be done without further preparation. To access a remote OPC Server make sure to go through the DCOM configuration as explained in detail in this document.

 
In the Server Definition window provide the server name and choose type OPC DataAccess. Click the Refresh OPC List button to refresh the drop-down list holding available program IDs.

ParameterDescription
NameName of the cluster server definition.
TypeServer type. Can be OPC DataAccess or VNET.
HostnameThe hostname or IP. Leave this field empty for a local connection.
Program IDOPC Server ID. Refresh OPC List will update the list.
Description

(optional) Verbal description of the connection.


Click Ok and the connection will appear in the Cluster Explorer window. Now datapoints from the OPC Server can be imported into the NETx BMS Server: Click the Explore Items of Cluster Server  icon of the selected server.

The Cluster Item Manager window will appear with the list of all OPC Server's items. Individually select with the mouse or use the Select all button to choose the desire item(s) and press Ok.

Afterwards, in Cluster Explorer click Ok and confirm to save the changes.

Then start the NETx BMS Server. In the item tree the Cluster branch contains the configured server connections and their respective data points. These data points are two-ways synchronized with their source server.

  • No labels