Search

13 result(s) for TypeDefinition Nodes

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.17 TypeDefinitionNode
  type of another Node Note 1 to entry: ObjectType and VariableType Nodes are TypeDefinitionNodes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  HasTypeDefinition Reference will be well-known to Clients and Servers . Organizations may define TypeDefinitionNodes that are well-known in the industry. Well-known NodeIds of TypeDefinitionNodes provide for commonality across ... from the Server . Therefore, Servers may use well-known NodeIds without representing the corresponding TypeDefinitionNodes in their AddressSpace . However, the TypeDefinition­Nodes shall be provided for generic Clients . These TypeDefinitionNodes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.2 Complex TypeDefinitionNodes and their InstanceDeclarations
  Complex TypeDefinitionNodes and their InstanceDeclarations TypeDefinitionNodes can be complex. A complex TypeDefinitionNode also defines References to other Nodes as part of the type definition. The ModellingRules defined in 6.4.4 specify ... creating an instance of the type definition. A TypeDefinitionNode references instances instead of other TypeDefinitionNodes to allow unique names for several instances of the same type, to define default values
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.4 Instantiation of complex TypeDefinitionNodes
  Instantiation of complex TypeDefinitionNodes The instantiation of complex TypeDefinitionNodes depends on the ModellingRules defined in 6.4.4 . However, the intention is that instances of a type definition will reflect the structure ... might not be sufficient since the uniqueness of the BrowseName is only required for TypeDefinitionNodes and InstanceDeclarations , not for other instances. Thus, "AI_BLK_1" may have another
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  Interfaces using the same BrowsePath for Nodes that are not similar Nodes or have TypeDefinitionNodes that are not compatible (compatible means they have either the same TypeDefinitionNode or one TypeDefinitionNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.1 InstanceDeclaration
  hierarchical Reference from a TypeDefinitionNode or another InstanceDeclaration . There shall be no two TypeDefinitionNodes referencing the same InstanceDeclaration with a hierarchical Reference, either directly or from another InstanceDeclaration of that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.9 NodeIds of InstanceDeclarations
  their BrowsePath . Different Servers might use different NodeIds for the InstanceDeclarations of common TypeDefinitionNodes , unless the definition of the TypeDefinitionNode already defines a NodeId for the InstanceDeclaration . All TypeDefinitionNodes defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  override a Node unless it needs to change it. The semantics of certain TypeDefinitionNodes and ReferenceTypes may impose additional restrictions with regard to overriding Nodes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  Node exists in a different Server . A Client can use the information of TypeDefinitionNodes to access Node s which are in the hierarchy of the instance. It shall pass
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.1 Overview
  populate data for a report. A Query defines what instances of one or more TypeDefinitionNodes in the AddressSpace should supply a set of Attributes . Results returned by a Server ... selected Attribute values in each QueryDataSet come from the definition of the selected TypeDefinitionNodes or related TypeDefinitionNodes and appear in results in the same order as the Attributes that were
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  originating TypeDefinitionNode . Additionally, the Client can request the Server return instances of subtypes of TypeDefinitionNodes . If a selected Attribute does not exist in a TypeDefinitionNode but does exist
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  Nodes are identical for all Attributes in all Servers , including the Value Attribute . For TypeDefinitionNodes , also the InstanceDeclarations shall be identical. That means that for static Nodes the semantic
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.4 Conditions in InstanceDeclarations
  ObjectType . The use of the HasEventSource Reference in the context of InstanceDeclarations and TypeDefinition Nodes has no effect for Event generation. Figure 28 - Use of HasCondition in an InstanceDeclaration