Search

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

23 result(s) for DataVariable

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

3.1.7 DataVariable

DataVariable Variables that represent values of Objects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.5.3 DataVariables

contains a stream of bytes. The stream of bytes may be defined as a DataVariable that is an array of bytes. Properties may be used to expose the creation time ... owner of the file Object . For example, if a DataVariable is defined by a data structure that contains two fields, "startTime" and "endTime" then it might
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.1 General

Reference . In this example, a setpoint parameter "SP" is represented as a DataVariable in the AddressSpace . This DataVariable is part of an Object not shown in the figure ... that can be used by other Objects , a specialised VariableType is used. Each setpoint DataVariable that uses this common definition will have a HasTypeDefinition Reference that identifies the common
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

ModellingRules ). HasProperty 0..* HasProperty References are used to identify the Properties of a DataVariable . Properties are not allowed to be the SourceNode of HasProperty References. HasComponent 0..* HasComponent References ... NodeVersion O String The NodeVersion Property is used to indicate the version of a DataVariable . It does not apply to Properties . The NodeVersion Property is updated each time a Reference
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.7.1 Method NodeClass

output argument. Input1 as a numeric input argument with a HasArgumentDescription Reference to a DataVariable Variable which provides the default value 42. Input2 as a numeric input argument with
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.7 HasComponent ReferenceType

TargetNode is a Variable , the SourceNode shall be an Object , an ObjectType , a DataVariable or a VariableType . By using the HasComponent Reference , the Variable is defined as DataVariable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.22.1 Overview

Variable which represents a field of the Structure DataType. The BrowseName of a DataVariable which is exposed shall be the same as the field name of the Structure DataType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.51 StructureField

Variable that contains the Structure Value . In this case the BrowseName of the DataVariable shall be the same as the StructureField name and the NamespaceIndex of the BrowseName shall
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.4.2 Properties or DataVariables

different syntax can help. The following points identify when it shall be a DataVariable . If it is a complex Variable or it should contain additional information in the form
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

setting by adding the MaxStringLength Property defined in OPC 10000-3 to an individual DataVariable . If a Server does not impose a maximum number of bytes or is not able ... setting by adding the MaxByteStringLength Property defined in OPC 10000-3 to an individual DataVariable. If a Server does not impose a maximum number of bytes or is not able
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.1 General

standard Property NodeVersion , defined in OPC 10000-3 , into the BaseDataVariableType , stating that each DataVariable of the Server will provide a NodeVersion
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.4 BaseDataVariableType

BaseVariableType . It is used as the type definition whenever there is a DataVariable having no more concrete type definition available. This VariableType is the base VariableType for VariableTypes of DataVariables
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.29 BitFieldType

Each bit field defined by the BitFieldDefinitions shall also be exposed as a child DataVariable . The BrowseName of the DataVariable shall be the same as the BitFieldDefinition name field ... fields may be defined by using the Optional Modeling Rule for the child DataVariable which represents the bit field. An application accessing a BitFieldType with an optional bit field should
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.45 BitFieldDefinition

DataType of the field is defined by the DataType of the BitFieldType's child DataVariable for the field. When the DataType of the field is an Integer the most significate
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.5 Complex Variables using complex DataTypes

example, the ServerStatus Variable of the Server Object is modelled as a complex DataVariable having the ServerStatusDataType providing all information about the Server status. But it also exposes the CurrentTime ... simple DataVariable , because a client may want to read only the current time of the Server , and is not interested in the build information
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.6 Complex Variables having an array

PublishRequestCount . Therefore, each entry of the array is also exposed individually as a complex DataVariable , having each entry exposed as simple data. Note that it is never necessary to expose
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.8 Usage of the BaseDataVariableType

subtyped, because they should reflect the data structure of the DataType of the complex DataVariable
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.4 Address Space model

Figure 4 - Representation of DataItems in the AddressSpace Each DataItem is represented by a DataVariable with a specific set of Attribute s. The TypeDefinition reference indicates the type
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.1.2 Annotations Property

Annotations Property The DataVariable or Object that has Annotation data will add the Annotations Property as shown in Table 2 . Table 2 - Annotations Property Name Use Data Type Description Annotations
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

4.4 Exposing Supported Functions and Capabilities

highest level may support Aggregate functionality for Interpolative, Total, Average, and others, DataVariable X only supports Interpolative, Total and Average, while DataVariable Y supports Average, a vendor defined Aggregate
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.9 Parameter

entry: In the information model it is synonymous to an OPC UA DataVariable
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.3.1 HasStatisticComponent

subtypes. The TargetNode of this ReferenceType shall be an Object or DataVariable . If an Object is referenced, the Object shall not implement the IStatisticsType Interface , in order to avoid ambiguity