Search

9 result(s) for ReferenceDescription

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  References do indicate the direction the Server followed in the isForward parameter of the ReferenceDescription . Symmetric References are always considered to be in forward direction therefore the isForward flag ... remote Node , the nodeClassMask is ignored. resultMask UInt32 Specifies the fields in the ReferenceDescription structure that should be returned. The fields are assigned the following bits: Bit Result 0 ReferenceType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  This relative path could end on a Reference , in which case the ReferenceDescription of the Reference would be returned as its value. The targetName field of the relativePath may contain
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.5 QueryDataSet
  array of values is returned. If the requested item is a reference then a ReferenceDescription or array of ReferenceDescription is returned for that item. If the QueryDataSet is returned ... QueryNext to continue a list of ReferenceDescription , the values array will have the same size but the other values already returned are null
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.9 Example 6
  HasAnimal> 12:AnimalType.NodeId 12:91 (Pig1) <12:HasChild> HasChild ReferenceDescription <12:HasChild>12:PersonType<12:HasAnimal> HasFarmAnimal ReferenceDescription 12:48 (HFamily2) PersonType ... HasAnimal> 12:AnimalType.NodeId 12:91 (Pig1) <12:HasChild> HasChild ReferenceDescription <12:HasChild>12:PersonType<12:HasAnimal> HasPet ReferenceDescription NOTE The RelativePath and browse
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.10 Example 7
  HFamily1) PersonType ".NodeId" 12:42 (HFamily1) <12:HasChild> HasChild ReferenceDescription <12:HasAnimal>12:AnimalType.NodeId NULL <12:HasAnimal> HasFarmAnimal ReferenceDescription 12:48 (HFamily2 ... PersonType ".NodeId" 12:48 (HFamily2) <12:HasChild> HasChild ReferenceDescription <12:HasAnimal>12:AnimalType.NodeId 12:91 (Pig1) <12:HasAnimal> HasFarmAnimal ReferenceDescription NOTE
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.1 Overview
  desirable to add more information to such a Reference . The concept of a ReferenceDescription keeps the simple Reference unchanged, and creates a Variable which is used to add more information ... provide additional information (see also 5.2 ). As Nodes can have several References , each ReferenceDescription Variable contains the unique definition of one Reference . An example is given in Figure 2 . ObjectA
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.2 Reference Refinement
  make the refined References explicit. In Figure 5 , an example is given. The ReferenceDescription Variable containing the refinement can be referenced by any Node in the refinement path using ... Example of how to use Reference Refinements When multiple levels are addressed, each ReferenceDescription Variable only contains one level, as shown in Figure 6 . The "Controls" Variable only
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.4.1 HasReferenceDescription
  subtype of HasChild . The semantic of this ReferenceType is to link to a ReferenceDescription either from a Node directly participating in the Reference that is described in the ReferenceDescription ... BrowseName Comment Subtype of HasChild defined in OPC 10000-5 Conformance Units Base Info ReferenceDescription
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  A.2 Alternative Approach: Intermediate Object
  intermediate Object first and from there to the original target. Therefore, the ReferenceDescription uses an approach, where the Reference directly connects both Nodes without the need to deal with