The OPC-UA Client driver is supported on the following product platforms.
- Asset Gateway for B+B SmartWorx Spectre V3 1
- Asset Gateway for CalAmp CDM5030 (Discontinued)
- Asset Gateway for CalAmp LMU5000 RevG (Discontinued)
- Asset Gateway for MultiTech OCG-D H5 (Discontinued)
- Asset Gateway for MultiTech Conduit AEP
- Asset Gateway for MultiTech MultiConect rCell
- Asset Gateway for Windows 32-bit and 64-bit
- Asset Gateway for Linux 32-bit and 64-bit
- Enterprise Gateway for Linux 32-bit and 64-bit
- Enterprise Gateway for Windows 32-bit and 64-bit
The OPC-UA Client driver is the extension that contains the protocol specific logic to communicate with servers that support the OPC-UA specification. Communication support is provided for OPC-UA servers that are installed on the same network and are accessible from the Enterprise Gateway machine.
Supported devices and communication interfaces
The OPC-UA Client driver has been tested interacting with the following OPC-UA servers.
| Device Type | Protocol |
|---|---|
| OPC-UA Servers | OPC-UA interface protocol |
- Unified Automation - UA SDK C++ Server Professional 1.5.0
- Unified Automation - UA SDK ANSI C Server Professional 1.5.1
- Beckhoff - TS6100 TwinCAT OPC-UA Server
- Kepware - Kepware KepServerEX 6.4
- Siemens SIMATIC OPC UA S7-1500 Server
- Prosys OPC UA Simulation Server
Server Considerations
- The OPC-UA Client driver supports reading and writing to subsets of variable arrays. Not all OPC-UA servers, however, support reading and writing to array subsets. If an OPC- UA server does not provide this support, the entire array must be read or written to.
- The OPC-UA Client driver uses OPC-UA subscriptions for monitoring items used in triggers, variable groups, and in variable watch windows. Each trigger and each variable in the watch window requires its own subscription. OPC-UA servers may need to be configured to increase the number of allowed subscriptions.
Limitations
The OPC-UA Client driver requires significant system resources to connect to OPC-UA servers and subscribe to the tags supported by the OPC-UA server.
In resource constrained nodes, primarily memory constrained environments, configuration topics to review when using the OPC-UA Client driver include:
- Do not install unnecessary packages or extensions on the node.
- Ensure Per Variable Security is set to False in the device definitions.
- Increase the Timeout parameter value to 60 seconds in your OPC-UA Client device definitions.
- Increase the Enumeration Timeout parameter if tags are not enumerated from the OPC-UA server.
- Subscribing to a large numbers of tags will have a performance impact. Consider the minimum requirements for the application, and scale down the number of tags that are subscribed to.
- There is a limitation of 25 concurrent Started OPC-UA Client devices on each deviceWISE node.
- For the Mitsubishi MESInterface IT product, review the Memory Optimization parameters:
- Throughput = Low Capacity
- Enterprise Access = Optimized for SQL Server
For information on memory optimization, see Memory Optimization.
- Security using X.509 Certificates is not supported on VxWorks platforms or Asset Gateway for B+B SmartWorx Spectre V3.
- MaxAge - By default, the MaxAge is set to zero for all reads to receive the new value from the Server data source . Reading cache value from Server is not supported in deviceWISE.
-
Deadband - Deadband configuration is not supported in OPC-UA subscriptions in deviceWISE.