OPC-UA Client Server Supported hardware

The OPC-UA Client Server driver is supported on the following product platforms.

  • Asset Gateway for B+B SmartWorx Spectre V3
  • Asset Gateway for MultiTech Conduit AEP
  • Asset Gateway for MultiTech MultiConect rCell
  • Enterprise or Asset Gateway for Windows 32-bit and 64-bit
  • Enterprise or Asset Gateway for Linux 32-bit and 64-bit
  • Enterprise or Asset Gateway for ARM 64-bit
  • Asset Gateway for Teltonika

Supported devices and communication interfaces

The OPC-UA Client Server driver has been tested interacting with the following OPC-UA servers.

Device Type Protocol
OPC-UA Servers OPC-UA interface protocol
  • Beckhoff - TS6100 TwinCAT OPC-UA Server
  • Kepware - Kepware KepServerEX 6.4 
  • Siemens SIMATIC OPC UA S7-1500 Server
  • Prosys OPC UA Simulation Server
  • WAGO with OPC-UA server
  • Keyence with OPC-UA Server

All of the items above were validated and are fully compliant with OPC UA Server specification.

Server Considerations

  • The OPC-UA Client Server 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 Server 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 Server 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 Server driver include:

  1. Do not install unnecessary packages or extensions on the node.
  2. Ensure Per Variable Security is set to False in the device definitions.
  3. Increase the Timeout parameter value to 60 seconds in your OPC-UA Client device definitions.
  4. Increase the Enumeration Timeout parameter if tags are not enumerated from the OPC-UA server.
  5. 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.
  6. 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.
  7. Deadband - Deadband configuration is not supported in OPC-UA subscriptions in deviceWISE.