Search

9 result(s) for ExpandedNodeIds

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.3.2 Parameters
  urisVersion is not 0. serverUris [] String A list of URIs referenced by ExpandedNodeIds in the request. ServerIndex 0 shall not be in this list. The first entry in this list ... urisVersion is not 0. serverUris [] String A list of URIs referenced by ExpandedNodeIds in the response. ServerIndex 0 shall not be in this list. The first entry in this list
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding
  QualifiedName, NodeId and ExpandedNodeId String Encoding QualifiedNames , NodeIds and ExpandedNodeIds optimize representation of NamespaceUris by using a NamespaceIndex to reference the location of the URI in a NamespaceTable . The NamespaceTable ... index> = "svr=" *DIGIT <server-uri> = "svu=" ENCODEDURI ExpandedNodeIds that are not specific to a Server shall use the <node-id> form
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.11 ExpandedNodeId
  defined in 5.1.12 . The NodeId portion of the ExpandedNodeId uses the rules from 5.4.2.10 . ExpandedNodeIds with a ServerIndex of 0 are encoded using the <node-id> form ... other ExpandedNodeIds use the <server-uri> form unless the first abnormal state occurs as described below. The first abnormal state occurs when the encoder cannot map a ServerIndex
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  list of URIs for namespaces used in the UANodeSet . The NamespaceIndexes used in NodeId, ExpandedNodeIds and QualifiedNames identify an element in this list. The first index is always ... list of URIs for Servers referenced in the UANodeSet . The ServerIndex in ExpandedNodeIds identifies an element in this list. The first index is always 1 (0 is always the current
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.14 Variant
  used to serialize Variant in this file syntax. Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames which must be modified so the NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables ... contain an EncodingId and a Structure with fields which with any DataType including NodeIds , ExpandedNodeIds or QualifiedNames . The NamespaceIndexes and ServerIndexes in these fields shall also reference the tables
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.5 Client use of an AliasName Server
  call via a configuration setting. The FindAlias Method call returns a list of all ExpandedNodeIds that the AliasName has a Reference to. It is important to note that there could
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  B.1 Aggregating Server with a collection of Aggregates
  same AliasName TI101 could exist in both Servers . The aggregating Server simply reports two ExpandedNodeIds to any Client that requested TI101. Figure B.1 - Aggregating AliasNames Server example In the above
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.6 Loading / Saving ConnectionConfigurationSets
  This clause provides the following instructions related to NodeIds : " Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames that must be modified, so the NamespaceIndexes and ServerIndexes reference the NamespaceUri
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.4 Additional Attribute values
  Double quotes are not included. If the DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value is an Enumeration