Search
4 result(s) for PortableNodeId
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.1 Overviewlogical connection. The configuration might contain Nodes in any of the following formats: PortableNodeId , PortableRelativePath or AliasName , each of which has components that might have changed since they were generated
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.1 Generalrequire information from the ConnectionConfigurationSets and their components. That information may be represented as PortableNodeId , PortableRelativePath or AliasName . These all need to be resolved to NodeIds (illustrated in Figure
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.2 PortableNodeId providedPortableNodeId provided If the ConnectionConfigurationSets contain PortableNodeIds , then the ConnectionManager should perform the following steps ( Figure 68 provides an overview of the configuration and actions): Resolve the location ... matching all NamespaceUri from the NamespaceArray to the URI's store in the PortableNodeId and storing the Index of the URI in the table as the cached NodeId . The cache
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.3.7.5 PortableNodeId data typeA.3.7.5 PortableNodeId data type PortableNodeId - The identifier field of PortableNodeId has the same definition as NodeId. The NamespaceUri information of the PortableNodeId is already present in the identifier and, therefore