The OpcNetwork is the top-level container component for “everything OPC” in a station.
Only one OpcNetwork component is valid in a station—regardless of how many OPC servers the station will make client connections to.
The OpcNetwork should reside in the station’s DriverContainer (“Drivers”). The simplest way to add an OpcNetwork is from the
“Driver Manager” view, using the command. Or, you can simply copy the OpcNetwork from the opc palette into Drivers.
The JACE-NXS or JACE-NX platform must have the Opc module installed. Otherwise, an error occurs explaining that the Opc module
is missing. If this occurs, install the opc module in that platform and repeat the operation.
The OpcNetwork component has the typical collection of slots and properties as most other network components. For details, See “Common network components” in the Drivers Guide. One exception is the location of poll components (Poll Scheduler), which is not at the network-level, but under each OpcDaClient (device-level) component.
In addition, the following OpcNetwork property has special importance:
-
Thread Pool
Controls the number of threads used to execute all actions of all OPC objects in the network. This includes most communications with remote devices, which can be multi-threaded. In this case, if there are performance issues, you can increase the number of threads.
The following sections provide additional OpcNetwork details: