Search

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

41 result(s) for InstanceDeclaration

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

3.1.12 ModellingRule

ModellingRule metadata of an InstanceDeclaration that defines how the InstanceDeclaration will be used for instantiation and also defines subtyping rules for an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.2 Complex TypeDefinitionNodes and their InstanceDeclarations

However, this term is used to simplify this specification, if an instance is an InstanceDeclaration or not is only visible in the AddressSpace by following its References . Some instances
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

There are several constraints related to programming against the TypeDefinitionNode . A TypeDefinitionNode or an InstanceDeclaration shall never reference two Nodes having the same BrowseName using forward hierarchical References . Instances based ... InstanceDeclarations shall always keep the same BrowseName as the InstanceDeclaration they are derived from. A special Service defined in OPC 10000-4 called TranslateBrowsePathsToNodeIds may be used to identify
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

Interface with a HasInterface Reference or a subtype, the following rules apply: Each mandatory InstanceDeclaration of the fully-inherited InstanceDeclarationHierarchy of the Interface shall have for each BrowsePath a similar ... ObjectType . The rules for instantiating InstanceDeclarations defined in 6.2.6 shall be applied. Each optional InstanceDeclaration of the fully-inherited InstanceDeclarationHierarchy of the Interface should have for each BrowsePath a similar
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

Standard ReferenceTypes are described in Clause 7 . If the Object is used as an InstanceDeclaration (see 4.6 ) then all Nodes referenced with forward hierarchical References direction shall have unique BrowseNames ... context of this Object . If the Object is created based on an InstanceDeclaration then it shall have the same BrowseName as its InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

Object . ModellingRules are defined in 6.4.4 . If the Variable is created based on an InstanceDeclaration (see 4.6 ) it shall have the same BrowseName as its InstanceDeclaration . The other References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

VariableType used as type definition of the DataVariable . If the DataVariable is used as InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

specify argument metadata. If the SourceNode of this Reference is defined on an InstanceDeclaration the TargetNode shall use the Mandatory ModellingRule . <other References> 0..* Methods may contain other ... detect the context of the Method operation. If the Method is used as InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.3 Usage of DataTypeRefinements

DataTypeRefinements shall not be used from any DataType Node , from any VariableType , or any InstanceDeclaration , only from concrete Variables . This does include Variables describing a DataTypeRefinement , as shown in Figure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.1 InstanceDeclaration

InstanceDeclaration An InstanceDeclaration is an Object , Variable or Method that references a ModellingRule 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 a hierarchical Reference, either directly or from another InstanceDeclaration of that TypeDefinitionNode , i.e. an InstanceDeclaration belongs to exactly
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.4 Similar Node of InstanceDeclaration

Similar Node of InstanceDeclaration A similar Node of an InstanceDeclaration is a Node that has the same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects ... subtype of it. In the case of a Method a similar Node of an InstanceDeclaration is a Node that also has the same arguments of the InstanceDeclaration , however
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.6 BrowseName within a TypeDefinitionNode

TypeDefinitionNode, this same restriction applies to the targets of forward hierarchical References from any InstanceDeclaration . This means that any InstanceDeclaration within the InstanceDeclarationHierarchy can be uniquely identified by a sequence
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.7 Attribute Handling of InstanceDeclarations

Attribute Handling of InstanceDeclarations Some restrictions exist regarding the Attributes of InstanceDeclarations when the InstanceDeclaration is overridden or instantiated. The BrowseName and the NodeClass shall never change and always ... same as the original InstanceDeclaration . In addition, the rules defined in 6.2.8 apply for InstanceDeclarations of the NodeClass Variable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.8 Attribute Handling of Variable and VariableTypes

restrictions exist regarding the Attributes of a VariableType or a Variable used as an InstanceDeclaration with regard to the data type of the Value Attribute . When a Variable used ... InstanceDeclaration or a VariableType is overridden or instantiated the following rules apply: The DataType Attribute can only be changed to a new DataType if the new DataType is a subtype
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.9 NodeIds of InstanceDeclarations

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

6.3.3.2 Fully-inherited InstanceDeclarationHierarchy

InstanceDeclarationHierarchy and all Nodes referenced with a NonHierarchical Reference from such an InstanceDeclaration are added to the table. Hierarchical References to Nodes without a ModellingRule are not considered. Table
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

Overriding InstanceDeclarations A subtype overrides an InstanceDeclaration by specifying an InstanceDeclaration with the 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 in the supertype. When overriding an InstanceDeclaration it is necessary to provide hierarchical References that link
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.1 Overview

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 . If a Node ... InstanceDeclaration then it shall have the same BrowseName and NodeClass as the InstanceDeclaration and, in cases of Variables and Objects , the same TypeDefinitionNode or a subtype of it. Instances
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.2 Creating an Instance

Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . Standard ModellingRules are defined in 6.4.4.4 . The Node s within the newly created hierarchy ... copies of the InstanceDeclaration s, the InstanceDeclaration itself or another Node in the AddressSpace that has the same TypeDefinitionNode and BrowseName . If new copies are created, then the Attribute values
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.3 Constraints on an Instance

Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode as the InstanceDeclaration or a subtype of it. If two InstanceDeclarations of the fully-inherited InstanceDeclarationHierarchy have been connected
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.1 General

instance hierarchy or not. Other ModellingRules may define behaviour for NonHierarchical References between InstanceDeclaration as well. ModellingRules are represented in the AddressSpace as Objects of the ObjectType ModellingRuleType . There
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

Type'. Either 'A' is used as normal instance or it is used as an InstanceDeclaration of another TypeDefinitionNode . In the first case, it is not required that newly created ... allowed that they have any ModellingRule independent of the ModellingRule of their InstanceDeclaration . In Figure 29 an example is given. The instances A1, A2, and A3 are all valid instances
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.1 Mandatory

Mandatory An InstanceDeclaration marked with the ModellingRule Mandatory means that for each existing BrowsePath on the instance a similar Node shall exist, but it is not defined whether ... have a newly-created setpoint "SP1" as a similar Node to the InstanceDeclaration SP1. Figure 31 illustrates the example. Figure 31 - Use of the Standard ModellingRule Mandatory
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.2 Optional

Optional An InstanceDeclaration marked with the ModellingRule Optional means that for each existing BrowsePath on the instance a similar Node may exist, but it is not defined whether ... same Node or two different Nodes with the same BrowseName (similar Node to InstanceDeclaration F). Not considered in the example is if the instances have ModellingRules
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.3 ExposesItsArray

value array. Therefore it references two instances of the same type as the InstanceDeclaration ArrayExpose. The BrowseNames of those instances are not defined by the ModellingRule . In general ... ArrayExpose and therefore each instance based on ArrayExpose references the instance based on the InstanceDeclaration EUUnit
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

TypeDefinition . It just provides useful information when exposing a TypeDefinition . When the InstanceDeclaration is complex, i.e. it references other InstanceDeclarations with hierarchical References , these InstanceDeclarations are not further considered ... InstanceDeclarations having the OptionalPlaceholder ModellingRule should be enclosed within angle brackets. When overriding the InstanceDeclaration, the ModellingRule shall remain OptionalPlaceholder . For Methods, the ModellingRule OptionalPlaceholder is used to define
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.5 MandatoryPlaceholder

TypeDefinition expects of instances of the TypeDefinition to add instances defined by the InstanceDeclaration . However, MandatoryPlaceholder requires that at least one of those instances shall exist. For example, when ... requires that each instance provides at least one instance with the TypeDefinition of the InstanceDeclaration or a subtype, and is referenced with the same ReferenceType or a subtype
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.17 HasEventSource

within the EventNotifier Attribute . The SourceNode may also be an ObjectType when referencing an InstanceDeclaration where an instance of the ObjectType containing the InstanceDeclaration generates events. Note the ObjectType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.24 UsesDataTypeRefinement

Variable having a Structured DataType . The Variable shall not be used as InstanceDeclaration . Note that Method Arguments can be further described using Variables referenced with a HasArgumentDescription . If the Method
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.28 UsesSubtypeRestriction

this type shall be a Variable . The Variable shall not be used as InstanceDeclaration . Note, that Method Arguments can be further described using Variables referenced with a HasArgumentDescription . This Variable
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . All Nodes with a ModellingRule of Mandatory shall be created or an existing Node shall ... referenced that conforms to the InstanceDeclaration . The creation of Nodes with other ModellingRules is Server specific
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.1 Description

example, an ObjectType "Boiler" may have a "HeatSensor" Variable as InstanceDeclaration . A graphical element programmed against the "Boiler" may need to display the Value
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.22.3 EventFilter

NodeId of an EventType supported by the Server and a path to an InstanceDeclaration . An InstanceDeclaration is a Node which can be found by following forward hierarchical references from ... SimpleAttributeOperand.typeDefinitionId then the Server shall evaluate the SimpleAttributeOperand.browsePath without considering the SimpleAttributeOperand.typeDefinitionId . Each InstanceDeclaration in the path shall be Object or Variable Node . The final Node in the path
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.1 NodeIds

InstanceDeclarations would be identified as "ServerType.ServerCapabilities". Since this Object is complex, another InstanceDeclaration of the ServerType is "ServerType.ServerCapabilities.MinSupportedSampleRate". The Server Object defined in 8.3.2 is based ... symbolic name "Server". Therefore, the instance based on the InstanceDeclaration described above has the symbolic name "Server.ServerCapabilities.MinSupportedSampleRate". The NamespaceIndex for all NodeIds defined in this standard
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

A.3 Numeric Node Ids

ServerType ObjectType Node which has the NamespaceArray Property . The SymbolName for the NamespaceArray InstanceDeclaration within the ServerType declaration is: ServerType_NamespaceArray . OPC 10000-5 also defines a standard instance
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.4 Conditions in InstanceDeclarations

shows the use of the HasCondition Reference and the HasEventSource Reference in an InstanceDeclaration . They are used to indicate what References and Conditions are available on the instance ... Nodes has no effect for Event generation. Figure 28 - Use of HasCondition in an InstanceDeclaration
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.19 Special Restrictions on subtyping StateMachines

well. If InstanceDeclarations are referenced (e.g., Methods used to trigger Transitions ) either the InstanceDeclaration of the supertype is referenced or the InstanceDeclaration is overridden, and in the latter case ... overridden InstanceDeclaration of the subtype shall be referenced. If a StateMachine type is not abstract, subtypes of it shall not change the behaviour of it. That means, that in this
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.2 StateMachineType with a SubStateMachine using inheritance

Variable representing the current State . Since it is used as an InstanceDeclaration , no value is assigned to this Variable . An Object of "MyStateMachineType", called "MyStateMachine
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.1 SerializationStartNode

entry: The SerializationStartNode can also be an ObjectType or VariableType to use the InstanceDeclaration mechanism when creating instances of these types
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.2 SerializedData Variable

addition, the AddressSpace may have changed (reconfigured) during shutdown. If the SerializationEntity is an InstanceDeclaration , accessing the SerializedData Variable is not possible. Reading attempts are answered with the StatusCode