Search

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

34 result(s) for TypeDefinitionNode

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

3.1.17 TypeDefinitionNode

TypeDefinitionNode Node that is used to define the 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

3.1.10 InstanceDeclaration

InstanceDeclaration Node that is used by a complex TypeDefinitionNode to expose its complex structure Note 1 to entry: This is an instance used by a type definition
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.1 General

shall be used to link an instance with its type definition represented by a TypeDefinitionNode . Type definitions are required; however, OPC 10000-5 defines a BaseObjectType , a PropertyType ... specialised type information is available. Objects and Variables inherit the Attributes specified by their TypeDefinitionNode (see 6.4 for details). In some cases, the NodeId used by the HasTypeDefinition Reference will
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 ... those Nodes are handled when 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
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

that instances of a type definition will reflect the structure defined by the TypeDefinitionNode . Figure 7 shows an instance of the TypeDefinitionNode "AI_BLK_TYPE", where the ModellingRule ... having the same BrowseName as the Variable "SP" used by the TypeDefinitionNode and thereby reflects the structure defined by the TypeDefinitionNode . Figure 7 - Object and its Components defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

have TypeDefinitionNodes that are not compatible (compatible means they have either the same TypeDefinitionNode or one TypeDefinitionNode is the subtype of the other TypeDefinitionNode ). Subtypes should not have a HasInterface ... applied on the Object when the Interface cannot be applied on the TypeDefinitionNode of the Object . The same rules on the Object apply as if the Interface would have been
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.4 BrowseName

defining standard type definitions shall use their namespace(s) for the NodeId of the TypeDefinitionNode as well as for the BrowseName of the TypeDefinitionNode. BrowseNames of TypeDefinitionNodes, ReferenceTypes, and DataTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.4 Client-side creation of Objects of an ObjectType

using the AddNodes Service defined in OPC 10000-4 . The Service requires specifying the TypeDefinitionNode of the Object . An Object created by the AddNodes Service contains all components defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.6 Client-side creation of Variables of an VariableType

using the AddNodes Service defined in OPC 10000-4 . The Service requires specifying the TypeDefinitionNode of the Variable . A Variable created by the AddNodes Service contains all components defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.1 InstanceDeclaration

with a HasModellingRule Reference and is the TargetNode of a hierarchical Reference from a TypeDefinitionNode or another InstanceDeclaration . There shall be no two TypeDefinitionNodes referencing the same InstanceDeclaration with ... hierarchical Reference, either directly or from another InstanceDeclaration of that TypeDefinitionNode , i.e. an InstanceDeclaration belongs to exactly one TypeDefinitionNode . The type of an InstanceDeclaration may be abstract, however the instance
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.2 Instances without ModellingRules

instantiation of a type nor for subtyping. If a Node referenced by a TypeDefinitionNode does not reference a ModellingRule it indicates that this Node only belongs to the TypeDefinitionNode
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.3 InstanceDeclarationHierarchy

InstanceDeclarationHierarchy The InstanceDeclarationHierarchy of a TypeDefinitionNode contains the TypeDefinitionNode and all InstanceDeclarations that are directly or indirectly referenced from the TypeDefinitionNode using forward hierarchical References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.4 Similar Node of InstanceDeclaration

NodeClass as the InstanceDeclaration and in cases of Variables and Objects the same TypeDefinitionNode or a subtype of it. In the case of a Method a similar Node
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.6 BrowseName within a TypeDefinitionNode

BrowseName within a TypeDefinitionNode A BrowsePath within a TypeDefinitionNode which include targets of forward hierarchical References shall have a BrowseName that is unique within the TypeDefinitionNode, this same restriction applies
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.9 NodeIds of InstanceDeclarations

different NodeIds for the InstanceDeclarations of common TypeDefinitionNodes , unless the definition of the TypeDefinitionNode already defines a NodeId for the InstanceDeclaration . All TypeDefinitionNodes defined in OPC 10000-5 already define
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.2 Fully-inherited InstanceDeclarationHierarchy

Fully-inherited InstanceDeclarationHierarchy An instance of a TypeDefinitionNode is described by the fully-inherited InstanceDeclarationHierarchy of the TypeDefinitionNode . The fully-inherited InstanceDeclarationHierarchy can be created by starting with the InstanceDeclarationHierarchy ... TypeDefinitionNode and merging the fully-inherited InstanceDeclarationHierarchy of its parent type. The process of merging InstanceDeclarationHierarchies is straightforward and can be illustrated with the example shown in Figure 25 which
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

same BrowsePath . An overridden InstanceDeclaration shall have the same NodeClass and BrowseName . The TypeDefinitionNode of the overridden InstanceDeclaration shall be the same or a subtype of the TypeDefinitionNode specified ... Node ). It is only possible to override InstanceDeclarations that are directly referenced from the TypeDefinitionNode . If an indirect referenced InstanceDeclaration , such as "J" in Figure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.1 Overview

Overview Any Instance of a TypeDefinitionNode will be the root of a hierarchy which mirrors the InstanceDeclarationHierarchy for the TypeDefinitionNode. Each Node in the hierarchy of the Instance will have ... same as the BrowsePath for one of the InstanceDeclarations in the hierarchy of the TypeDefinitionNode. The InstanceDeclaration with the same BrowsePath is called the InstanceDeclaration for the Node
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.2 Creating an Instance

inherit the initial values for the Attributes that they have in common with the TypeDefinitionNode from which they are instantiated, with the exceptions of the NodeClass and NodeId . When ... Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . Standard
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.3 Constraints on an Instance

deleted as long as the ModellingRules defined on the InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

There are two different use cases when creating an instance 'A' based on a TypeDefinitionNode 'A_Type'. Either 'A' is used as normal instance or it is used ... InstanceDeclaration of another TypeDefinitionNode . In the first case, it is not required that newly created or referenced instances based on InstanceDeclarations have a ModellingRule , however, it is allowed that they
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.1 Mandatory

Node is created or an existing Node is referenced. For example, the TypeDefinitionNode of a functional block "AI_BLK_TYPE" will have a setpoint
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

9.32.6 GeneralModelChangeEventType

Node , etc.). If the affected Node is a Variable or Object , then the TypeDefinitionNode is also present. To allow Event compression, a GeneralModelChangeEvent contains an array of changes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

9.33.1 General

owning the Property that was changed. If this is a Variable or Object , the TypeDefinitionNode is also present. The SemanticChange bit of the AccessLevel Attribute of a Property indicates whether
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

AddressSpace hierarchy (see OPC 10000-3 ). When a Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy of Node s beneath the new Object or Variable
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.2 Parameters

Attribute value is null, the Server shall use the default values from the TypeDefinitionNode . If a TypeDefinitionNode was not provided the Server shall choose a suitable default value. The Server ... Client does not specify a value. typeDefinition Expanded NodeId NodeId of the TypeDefinitionNode for the Node to add. This parameter shall be null for all NodeClasses other than Object
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.5 SimpleAttributeOperand

SimpleAttributeOperand structure Attribute of a Node in the AddressSpace . typeDefinitionId NodeId NodeId of a TypeDefinitionNode . This parameter restricts the operand to instances of the TypeDefinitionNode or one of its subtypes
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.3 QueryFirst

simple to highly sophisticated. The Query can simply request data from instances of a TypeDefinitionNode or TypeDefinitionNode subject to restrictions specified by the filter. On the other hand, the Query ... 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 for limiting the instances
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.5 QueryDataSet

Node returned in a Query response. nodeId ExpandedNodeId The NodeId for this Node description. typeDefinitionNode ExpandedNodeId The NodeId for the type definition for this Node description. values [] BaseDataType Values ... requested items. There is an entry for each requested item for the given TypeDefinitionNode that matches the selected instance, this includes any related nodes that were specified using a relative
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.3 ServerDiagnosticsType

There is one entry for each sampling rate currently used by the Server . Its TypeDefinitionNode is the VariableType SamplingIntervalDiagnosticsArrayType , providing a Variable for each entry in the array, as defined ... There is one entry for each Notification channel actually established in the Server . Its TypeDefinitionNode is the VariableType SubscriptionDiagnosticsArrayType, providing a Variable for each entry in the array as defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.5 SessionDiagnosticsObjectType

array of Subscription diagnostic information per opened subscription, as defined in 12.15 . Its TypeDefinitionNode is the VariableType SubscriptionDiagnosticsArrayType providing a Variable for each entry in the array, as defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.6 ServerStatusType

these Objects and Variables are defined by their BrowseName defined in the corresponding TypeDefinitionNode . The NodeId is defined by the composed symbolic name described in 4.1 . Conformance Units Base Info
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.16 ModelChangeStructureDataType

affected Node was an Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node . Otherwise it is set to null. verb Byte Describes the changes happening
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.17 SemanticChangeStructureDataType

affected Node was an Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node . Otherwise it is set to null. Its representation in the AddressSpace