Siemens MindConnect Nano System Manual page 50

Configuring protocols
4.3 Overview of OPC UA protocol for MindConnect Nano
Parameter Description
You can enable the transfer and takeover of events and alarms in the OPC UA
protocol to Industrial IoT. Insights Hub Monitor shows all events and alarms in the
Enable OPC "Events" extension of the agent asset.
UA Events Limits:
- For Nanobox the proposed limit is 25 events/alarms per second
- For IoT2040 the proposed limit is 10 events/alarms per second
OPC UA Data Access Specification
OPC UA Data Access Specification does not specify a certain representation for OPC UA
Addresses (NodeId). A NodeId is represented by a combination of:
NamespaceIndex
IdentifierType
Identifier
OPC UA Client Driver addresses have the following syntax: ns=;=.
OPC browsing is not supported.
For more information refer to the table below:
Field
NamespaceIndex
IdentifierType
Identifier
Examples NodeId
Below you can see examples of an OPC UA Addresses (NodeId) representation:
String:
String IdentifierType
MindConnect Nano
System Manual 7/2023
Description
The index of the OPC UA Server namespace in which the address resides. If the
index is 0, the entire ns=;= clause is omitted.
The type of address. OPC UA supports the following four address types:
i: A numeric address represented with 32-bit unsigned integer
s: A string address containing characters that can be encoded using UTF-8
g: A GUID address in the format of XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
b: An opaque address (such as a byte string)
The address that is formatted as a string. This address may be numeric, string,
GUID, or opaque.
Example
50