Search

14 result(s) for TargetNodes

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  only specify how the NodeClasses can be used as SourceNodes of References , not as TargetNodes . If a NodeClass table allows a ReferenceType for its NodeClass to be used as SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  same AddressSpace or in the AddressSpace of another OPC UA Server . TargetNodes located in other Servers are identified in OPC UA Services using a combination of the remote Server name
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.2 Parameters
  delete. deleteTargetReferences Boolean A Boolean parameter with the following values: TRUE delete References in TargetNodes that Reference the Node to delete. FALSE delete only the References for which the Node ... source. The Server cannot guarantee that it is able to delete all References from TargetNodes if this parameter is TRUE. Response responseHeader Response Header Common response parameters
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  subtypes are returned. nodeClassMask UInt32 Specifies the NodeClasses of the TargetNodes . Only TargetNodes with the selected NodeClasses are returned. The NodeClasses are assigned the following bits: Bit NodeClass 0 Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.1 ServerType
  server indexes or server names . They are used in OPC UA Services to identify TargetNodes of References that reside in remote Servers . Clients may read the entire table or they
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.3.4 AddAliasesToCategory Method
  arguments are defined in Table 9 . Signature AddAliasesToCategory( [in] String[] AliasNames, [in] ExpandedNodeId[] TargetNodes, [in] String[] TargetServers, [in] NodeId TargetReferenceType, [out] StatusCode[] ErrorCodes ); Table 9 - AddAliasesToCategory Method Arguments Argument Description ... AliasName . It is Server specific as to what namespace the AliasName is added to. TargetNodes An array of NodeIds that represents the target Nodes of the AliasNames to be added
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.3.5 DeleteAliasesFromCategory Method
  instances that are from the aggregated Server . Signature DeleteAliasesFromCategory ( [in] String[] AliasNames, [in] ExpandedNodeId [] TargetNodes, [out] StatusCode[] ErrorCodes ); Table 13 - DeleteAliasesFromCategory Method Arguments Argument Description AliasNames An array ... string part of the AliasName , that is to be deleted. TargetNodes An array of the NodeId of the node that is the target of the AliasName , which would further restrict
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  9.2.1 MadeUpOf
  This ReferenceType is used to describe a shared aggregation. The SourceNode contains the TargetNodes . The SourceNode of this ReferenceType shall be an Object of ISA95ObjectType or its subtype . The TargetNode
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  9.4.1 MadeUpOfEquipment
  This ReferenceType is used to describe composition of equipment. The SourceNode contains the TargetNodes . The SourceNode of this ReferenceType shall be an Object of EquipmentType or its subtype . The TargetNode
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  9.5.1 MadeUpOfPhysicalAsset
  This ReferenceType is used to describe composition of equipment. The SourceNode contains the TargetNodes . The SourceNode of this ReferenceType shall be an Object of PhysicalAsset Type or its subtype
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  9.6.1 MadeUpOfMaterialSublot
  This ReferenceType is used to describe composition of equipment. The SourceNode contains the TargetNodes . The SourceNode of this ReferenceType shall be an Object of PhysicalAsset Type or its subtype
• OPC-30020 – MDIS OPC UA Companion Specification
  4.1 MDIS definitions
  Reference . The name of a ReferenceType identifies how source Nodes are related to TargetNodes and generally reflects an operation between the two, such as "A contains
• OPC-30020 – MDIS OPC UA Companion Specification
  9.1 HasInterlock ReferenceType
  used. Multiple SourceNodes can reference the same TargetNode and a SourceNode can reference multiple TargetNodes . Like all other ReferenceTypes , this ReferenceType does not specify anything about the ownership
• OPC-30020 – MDIS OPC UA Companion Specification
  9.3 HasSignature ReferenceType
  TargetNode can be referenced by a single SourceNode and a SourceNode can reference multiple TargetNodes . Like all other ReferenceTypes , this ReferenceType does not specify anything about the ownership