Search

Scope: Core (OPC-10000-*) All specs

17 result(s) for RelativePath

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.30 RelativePath

RelativePath The components of this parameter are defined in Table 169 . Table 169 - RelativePath Name Type Description RelativePath structure Defines a sequence of References and BrowseNames to follow. elements [] RelativePath ... next element. The targets of the final element are the target of the RelativePath . referenceTypeId NodeId The type of reference to follow from the current node. The current path cannot
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.1 Description

paths to NodeIds . Each browse path is constructed of a starting Node and a RelativePath . The specified starting Node identifies the Node from which the RelativePath is based. The RelativePath
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.2 Parameters

following indented items. startingNode NodeId NodeId of the starting Node for the browse path. relativePath RelativePath The path to 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 Bad _ BrowseNameInvalid if the targetName is missing. The RelativePath structure is defined
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.4 AttributeOperand

alias this operand and use it in other locations in the filter structure. browsePath RelativePath Browse path relative to the Node identified by the nodeId parameter ... definition of RelativePath . attributeId IntegerId Id of the Attribute . This shall be a valid AttributeId . The IntegerId is defined in 7.19 . The IntegerIds for the Attributes are defined
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.5 SimpleAttributeOperand

however, the AttributeOperand can be replaced by a SimpleAttributeOperand whenever all ReferenceTypes in the RelativePath are subtypes of HierarchicalReferences and the targets are Object or Variable Nodes and an Alias ... This parameter specifies a relative path using a list of BrowseNames instead of the RelativePath structure used in the AttributeOperand . The list of BrowseNames is equivalent to a RelativePath that
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

A.2 BNF of RelativePath

RelativePath A RelativePath is a structure that describes a sequence of References and Nodes to follow. This annex describes a text format for a RelativePath that can be used ... documentation or in files used to store configuration information. The components of a RelativePath text format are specified in Table A.1 . Table A.1 - RelativePath Symbol Meaning / The forward slash character
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.3 QueryFirst

Query can request data from instances of related Node types by specifying a RelativePath from an originating TypeDefinitionNode. In the filter, a separate set of paths can be constructed ... instance or any of the intermediate instances. When querying for related instances in the RelativePath , the Client can optionally ask for References . A Reference is requested via a RelativePath that
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.9 Example 6

QueryDataSets shown in Table B.27 . Table B.27 - Example 6 QueryDataSets NodeId TypeDefinition NodeId RelativePath Value 12:42 (HFamily1) PersonType ".NodeId" 12:42 (HFamily1) <12:HasChild ... HasChild>12:PersonType<12:HasAnimal> HasPet ReferenceDescription NOTE The RelativePath and browse name (in parentheses) is not in the QueryDataSet and is only shown here for clarity
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.10 Example 7

QueryDataSets shown in Table B.31 . Table B.31 - Example 7 QueryDataSets NodeId TypeDefinition NodeId RelativePath Value 12:42 (HFamily1) PersonType ".NodeId" 12:42 (HFamily1) <12:HasChild> HasChild ... AnimalType.NodeId 12:91 (Pig1) <12:HasAnimal> HasFarmAnimal ReferenceDescription NOTE The RelativePath and browse name (in parentheses) is not in the QueryDataSet and is only shown here for clarity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.36 PortableNodeIdentifier

where the Node is located, using a portable NodeId , an Alias , or a portable RelativePath . The PortableNodeIdentifier DataType is formally defined in Table 196 . Table 196 - PortableNodeIdentifier union Name Type
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.39 PortableRelativePath

where the target of the relative path is located. It is semantically equivalent to RelativePath . The PortableRelativePath DataType is formally defined in Table 202 . Table 202 - PortableRelativePath structure Name Type
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.2 Namespaces

overall size of the DataTypes defined in this Clause (i.e. ConnectionConfigurationSetConfDataType ), NodeId , AliasName and RelativePath are used instead of their portable version. The scope of those identifiers is defined ... into the Namespace array of the related ServerAddressConfDataType . A ConnectionManager can map NodeId and RelativePath contained in the DataTypes to their portable versions using the NamespaceUri from the Namespace array
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.5 ConnectionEndpointConfigurationConfDataType

FunctionalEntityNode specifies the identifier of the FunctionalEntity to configure for the Connection . If a RelativePath is specified, the path shall be relative to FxRoot . False FunctionalEntityNodeSelection 4:NodeIdentifier[] Selection list ... array is null or empty, the optional InputVariableIds node is not available. If a RelativePath is specified, the path shall be relative to the FunctionalEntityNode specified in the ConnectionEndpointConfigurations . True
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

AutomationComponentNode specifies the AutomationComponent that is to be used for establishing Connections . If a RelativePath is specified, the path shall be relative to FxRoot . False AutomationComponentNodeSelection 4:NodeIdentifier[] Selection list
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.12 AssetVerificationConfDataType

AssetToVerify 4:NodeIdentifier Specifies the expected Asset to be verified. If a RelativePath is specified, the path shall be relative to AutomationComponentNode . False VerificationMode 2:AssetVerificationModeEnum The mode ... ExpectedVerificationVariables 4:NodeIdentifierValuePair[] The variables to be verified for compatibility and/or identity. If a RelativePath is specified, the path shall be relative to the expected Asset . False ExpectedAdditionalVerificationVariables 4:NodeIdentifierValuePair
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.15 NodeIdentifier

store an identifier, where the identifier can be NodeId , Alias String , or a RelativePath . It is semantically equivalent to the PortableNodeIdentifier as defined in 10.36 , except it uses the optimisation ... related Server . Alias 0:String The AliasName of the Node. IdentifierBrowsePath 0:RelativePath The IdentifierBrowsePath to the Node . The starting Node of the IdentifierBrowsePath shall be specified where this type
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7.3 NodeId DataType

identified by the RootNodeId or the NodeId resolved from the alias. BrowsePath - An optional RelativePath to follow from either the RootNodeId or the NodeId resolved from the Alias ... definition of the RelativePath structure in OPC 10000-4 . If a BrowsePath is present and not empty in a NodeId , then the RootNodeId should be a well-known NodeId like