Search

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

32 result(s) for DataVariables

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

4.5.1 General

Variables are used to represent values . Two types of Variables are defined, Properties and DataVariables . They differ in the kind of data that they represent and whether they can contain
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.5.2 Properties

Properties Properties are Server -defined characteristics of Objects , DataVariables and other Nodes . Properties differ from Attributes in that they characterise what the Node represents, such as a device
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.5.3 DataVariables

DataVariables DataVariables represent the content of an Object . For example, a file Object may be defined that contains a stream of bytes. The stream of bytes may be defined ... parameters of the function block, such as its setpoints, may be represented as DataVariables . The function block Object might also have Properties that describe its execution time and its type
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

Events . The EventNotifierType is defined in 8.59 . References HasComponent 0..* HasComponent References identify the DataVariables , the Methods and Objects contained in the Object . HasProperty 0..* HasProperty References identify the Properties ... history of the Events . The Object NodeClass uses the HasComponent Reference to define the DataVariables , Objects and Methods of an Object . It uses the HasProperty Reference to define the Properties
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.2 ObjectType NodeClass

Objects of this type can exist. References HasComponent 0..* HasComponent References identify the DataVariables , the Methods , and Objects contained in the ObjectType . If and how the referenced Nodes are instantiated ... abstract or not. The ObjectType NodeClass uses the HasComponent References to define the DataVariables , Objects , and Methods for it. The HasProperty Reference is used to identify the Properties . The Property
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.1 General

General Two types of Variables are defined, Properties and DataVariables . Although they differ in the way they are used as described in 4.5 and have different constraints described ... constraints of Properties based on this NodeClass are defined in 5.6.3 , the constraints of DataVariables
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

defined by VariableTypes , as specified in 5.6.5 . Variables are always defined as Properties or DataVariables of other Nodes in the AddressSpace . They are never defined by themselves. A Variable ... SourceNode of HasProperty References. HasComponent 0..* HasComponent References are used by complex DataVariables to identify their composed DataVariables . Properties are not allowed to use this Reference . HasTypeDefinition 1 The HasTypeDefinition
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.3 Properties

shall be the TargetNode of at least one HasProperty Reference . To distinguish them from DataVariables , they shall not be the TargetNode of any HasComponent Reference . Thus, a HasProperty Reference pointing
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

DataVariable DataVariables represent the content of an Object . DataVariables are defined using the Variable NodeClass , specified in Table 13 . DataVariables identify their Properties using HasProperty References . Complex DataVariables use HasComponent ... References to expose their component DataVariables . The Property NodeVersion indicates the version of the DataVariable . The Property LocalTime indicates the difference between the SourceTimestamp of the value and the standard
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.5 VariableType NodeClass

HasComponent 0..* HasComponent References are used for complex VariableTypes to identify their containing DataVariables . Complex VariableTypes can only be used for DataVariables . The referenced Nodes may be instantiated ... VariableType NodeClass uses HasProperty References to define the Properties and HasComponent References to define DataVariables . Whether they are instantiated depends on the ModellingRules defined in 6.4.4 . The Property NodeVersion indicates
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.4 Example of usage of DataTypeRefinements

SuperObjectType, both using DataTypeRefinements . Z:Object1 has the Property Z:Prop1 and the DataVariables Z:Var1 and Z:Var2, as defined on the X:SuperObjectType. Although all three Variables
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.7 HasComponent ReferenceType

SourceNode . This ReferenceType is used to relate Objects or ObjectTypes with their containing Objects , DataVariables , and Methods . This ReferenceType is also used to relate complex Variable s or VariableTypes with ... their DataVariables . Like all other ReferenceTypes , this ReferenceType does not specify anything about the ownership of the parts, although it represents a part-of relationship semantic. That
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.51 StructureField

allows subtyping. Subtyping is allowed when set to TRUE. StructureFields can be exposed as DataVariables that are children of the Variable that contains the Structure Value . In this case
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.4.1 General

A.4.1 General VariableTypes are only used for DataVariables and should be used when there are several Variables having the same semantic (e.g. set point). It is not necessary to define
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.4.2 Properties or DataVariables

A.4.2 Properties or DataVariables Besides the semantic differences of Properties and DataVariables described in Clause 4 there are also syntactical differences. A Property is identified by its BrowseName , that ... used several times, they should always have the same BrowseName . The same semantic of DataVariables is captured in the VariableType . If it is not clear which concept to use based
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

client. Servers may use the Property MaxArrayLength defined in OPC 10000-3 on individual DataVariables to specify the size on individual values. The individual Property may have a larger
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.4 BaseDataVariableType

more concrete type definition available. This VariableType is the base VariableType for VariableTypes of DataVariables , and all other VariableTypes of DataVariables shall either directly or indirectly inherit from it. There
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.6 ServerStatusType

ServerStatusType This complex VariableType is used for information about the Server status. Its DataVariables reflect its DataType having the same semantic defined in 12.10 . The VariableType is formally defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.7 BuildInfoType

BuildInfoType This complex VariableType is used for information about the Server status. Its DataVariables reflect its DataType having the same semantic defined in 12.3.15.1 . The VariableType is formally defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.8 ServerDiagnosticsSummaryType

ServerDiagnosticsSummaryType This complex VariableType is used for diagnostic information. Its DataVariables reflect its DataType having the same semantic defined in 12.9 . The VariableType is formally defined in Table 78 . Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.10 SamplingIntervalDiagnosticsType

SamplingIntervalDiagnosticsType This complex VariableType is used for diagnostic information. Its DataVariables reflect its DataType , having the same semantic defined in 12.8 . The VariableType is formally defined in Table 80 . Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.12 SubscriptionDiagnosticsType

SubscriptionDiagnosticsType This complex VariableType is used for diagnostic information. Its DataVariables reflect its DataType , having the same semantic defined in 12.15 . The VariableType is formally defined in Table 82 . Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.14 SessionDiagnosticsVariableType

SessionDiagnosticsVariableType This complex VariableType is used for diagnostic information. Its DataVariables reflect its DataType , having the same semantic defined in 12.11 . The VariableType is formally defined in Table 84 . Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.16 SessionSecurityDiagnosticsType

SessionSecurityDiagnosticsType This complex VariableType is used for diagnostic information. Its DataVariables reflect its DataType , having the same semantic defined in 12.12 . The VariableType is formally defined in Table 86 . Since
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.4 Properties versus DataVariables

Properties versus DataVariables Since the general description in OPC 10000-3 about the semantic difference between Properties and DataVariables are not applicable for the information provided about the Server ... Object and the MinSupportedSampleRate of the ServerCapabilities Object . If complex data structures are used, DataVariables are used. Examples of DataVariables are the ServerStatus of the Server Object and the ServerDiagnosticsSummary
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.5 Complex Variables using complex DataTypes

Complex Variables using complex DataTypes DataVariables providing complex data structures expose their information as complex DataTypes , as well as components in the AddressSpace . This allows access to simple values
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.7 Redundant information

fulfil the needs of different clients, it may be helpful. Using complex DataVariables automatically leads to providing redundant information, because the information is directly provided in the complex DataType
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.8 Usage of the BaseDataVariableType

Usage of the BaseDataVariableType All DataVariables used to expose complex data structures of complex DataVariables have the BaseDataVariableType as type definition if they are not complex by themselves. The reason ... this approach is that the complex DataVariables already define the semantic of the containing DataVariables and this semantic is not used in another context. It is not expected that they
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.9 ProgramDiagnostic2Type VariableType

simple Variables using simple DataTypes that reflect the elements of the ProgramDiagnosticDataType structure. Its DataVariables have the same semantic as defined in in 5.2.8 . Note The original ProgramDiagnosticType VariableType
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.1.2 Annotations Property

allowed for Properties to have Properties , the Annotations Property is only available for DataVariables or Objects . The Annotations Property shall be present on every HistoricalDataNode that supports modifications, deletions
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.2 HistoricalDataNodes Address Space Model

Folder Object". Figure 3 illustrates the basic AddressSpace Model of DataVariables that includes History. Figure 3 - Historical Variable with Historical Data Configuration and Annotations Each HistoricalDataNode with history shall
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.1.1 Overview

provides general information about those statistical data. The concrete statistical data are managed in DataVariables referenced from the Object or ObjectType implementing the Interface with a HasStatisticComponent Reference , either directly