OPC Type Cloud Type
Integer INT
UInt16 INT
Int64 LONG
UInt32 LONG
UInt64 STRING
String STRING
If the connection to OPCUA Server is disconnected during browsing, then the whole
operation of browsing is failed. It is expected from the customer to trigger the browsing
result again in those situations.
If a node with supported node type is not fulfilling the required fields on server side which
is browsed than this node will be excluded, and it will not affect the whole browsing flow.
The excluded node and its child nodes will not be displayed in browsing results.
The default type for “Acquisition type” for browse result will be READ.
Performance of OPCUA Browsing
The browsing of an OPCUA server can be a time-consuming task depending on the number of
existing nodes on the server. Below table describes the time consumption for idle devices which
only perform browsing operations to OPC servers.
Number of Nodes Type of Device Time Consumed
5K MindConnect Nano ~6 min
75K MindConnect Nano ~16 min
150K MindConnect Nano ~36 min
The reading cycles of datasources can be affected during the OPCUA browsing
operation, as it requires a huge performance activity on the MindConnect Element.
4.4 Overview of Modbus TCP protocol for MindConnect Nano
To Next Page
Loading...
Need help?
General