Search

4 result(s) for targetName

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.2 Parameters
  follow from the startingNode . The last element in the relativePath shall always have a targetName specified. This further restricts the definition of the RelativePath type. The Server shall return ... BrowseNameInvalid if the targetName is missing. The RelativePath structure is defined in 7.30 . Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). results [] BrowsePathResult List of results
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.30 RelativePath
  ReferenceType should be followed. Subtypes are included if this value is TRUE. targetName QualifiedName The BrowseName of the target node. The final element may have an empty targetName . In this ... references identified by the referenceTypeId are the targets of the RelativePath . The targetName shall be specified for all other elements. The current path cannot be followed any further
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  returned as part of the QueryDataSets . Query Services allow a special handling of the targetName field in the RelativePath. In several Query use cases a type NodeId is necessary ... NodeId in the QualifiedName. This is done by setting the namespaceIndex of the targetName to zero and the name part of the targetName to the XML representation of the NodeId
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.40 PortableRelativePathElement
  ReferenceType should be followed. Subtypes are included if this value is TRUE. TargetName 0:PortableQualifiedName The BrowseName of the target node. The final element may have an empty TargetName ... references identified by the ReferenceTypeId are the targets of the PortableRelativePathElement . The TargetName shall be specified for all other elements. The current path cannot be followed any further