Search

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

23 result(s) for HasTypeDefinition

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.1 General

General OPC UA Servers shall provide type definitions for Objects and Variables . The HasTypeDefinition Reference shall be used to link an instance with its type definition represented by a TypeDefinitionNode ... their TypeDefinitionNode (see 6.4 for details). In some cases, the NodeId used by the HasTypeDefinition Reference will be well-known to Clients and Servers . Organizations may define TypeDefinitionNodes that
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

instance of "AI_BLK_TYPE", called AI_BLK_1", has a HasTypeDefinition Reference to "AI_BLK_TYPE". It also contains a Variable ... InstanceDeclarations shall always reside in the same Server . However, instances may point with their HasTypeDefinition Reference to a TypeDefinitionNode in a different Server
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasTypeDefinition 1 The HasTypeDefinition Reference points to the type definition of the Object. Each Object shall ... have exactly one type definition and therefore be the SourceNode of exactly one HasTypeDefinition Reference pointing to an ObjectType . See 4.6 for a description of type definitions. HasEventSource
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.4 Client-side creation of Objects of an ObjectType

ObjectType Objects are always based on an ObjectType , i.e. they have a HasTypeDefinition Reference pointing to its ObjectType . Clients can create Objects using the AddNodes Service defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

DataVariables to identify their composed DataVariables . Properties are not allowed to use this Reference . HasTypeDefinition 1 The HasTypeDefinition Reference points to the type definition of the Variable. Each Variable shall ... have exactly one type definition and therefore be the SourceNode of exactly one HasTypeDefinition Reference pointing to a VariableType . See 4.6 for a description of type definitions. <other References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.3 Properties

their complex structure. However, they may be the SourceNode of any NonHierarchical References . The HasTypeDefinition Reference points to the VariableType of the Property . Since Properties are uniquely identified by their
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.6 Client-side creation of Variables of an VariableType

VariableType Variables are always based on a VariableType , i.e. they have a HasTypeDefinition Reference pointing to its VariableType . Clients can create Variables using the AddNodes Service defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

changed as defined in 6.4.4.2 . Each overriding InstanceDeclaration needs its own HasModellingRule and HasTypeDefinition References , even if they have not been changed. A subtype should not override a Node unless
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.3 Constraints on an Instance

InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode as the InstanceDeclaration or a subtype
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.13 HasTypeDefinition ReferenceType

HasTypeDefinition ReferenceType The HasTypeDefinition ReferenceType is a concrete ReferenceType and can be used directly. It is a subtype of NonHierarchicalReferences. The semantic of this ReferenceType is to bind an Object ... VariableType . Each Variable and each Object shall be the SourceNode of exactly one HasTypeDefinition Reference
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.3.6 Variable and VariableType

same as or a subtype of the DataType of its VariableType (referred with HasTypeDefinition ). If a HasProperty points to a Variable from a Base "A" then the following
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.2 Simple notation

shown on the left. The double hashed lines have to be near the TargetNode . HasTypeDefinition The notation provides a shortcut for HasTypeDefinition References shown on the left. The double closed
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.3 Extended notation

text used in the graphical representation of a Node . Instead of using the HasTypeDefinition reference to point from an Object or Variable to its ObjectType or VariableType the name ... Node2" the shortcut in both notation variants. A figure can contain HasTypeDefinition References for some Nodes and the shortcut for other Nodes . It is not allowed that a Node
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

specifies a symbolic name for a NodeId , i.e., the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.3 UANode

automatically add reverse references unless reverse references are not appropriate given the ReferenceType semantics. HasTypeDefinition and HasModellingRule are two examples where it is not appropriate to add reverse references. When
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.7 UAInstance

implies that child Nodes , even Mandatory ones, are not added to the Node. The HasTypeDefinition reference shall be specified
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

specifies a symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.3.1 General

data If Online/Offline is supported, the main (leading) instance represents the offline information. Its HasTypeDefinition Reference points to the concrete configured or identified ObjectType . All Parameters of this instance represent
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.1.1 Node definitions

specifies a symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

specifies a symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying ... References are also selected. Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.1 Conventions for Node descriptions

specifies a symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.1.1 Node definitions

specifies a symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

specifies a symbolic name for a NodeId , i.e., the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying ... References are also selected. Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target