Search

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

14 result(s) for Structured

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

5.8.2 Encoding Rules for different kinds of DataTypes

DataType Attribute and thus interpret the value as defined by Duration (see 8.13 ). Structured DataTypes are DataTypes that represent structured data and are not defined as Built-in DataTypes . Structured ... DataTypes inherit directly or indirectly from the DataType Structure defined in 8.32 . Structured DataTypes may have several encodings and the encodings are exposed in the AddressSpace . How the encoding
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.3 DataType NodeClass

identify the encodings of the DataType represented as Objects of type DataTypeEncodingType . Only concrete Structured DataTypes may use HasEncoding References . Abstract, Built-in, Enumeration, and Simple DataTypes are not allowed ... SourceNode of a HasEncoding Reference . Each concrete Structured DataType shall point to at least one DataTypeEncoding Object with the BrowseName "Default Binary" or "Default XML" having
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.1 Overview

Overview A DataTypeRefinement refines the usage of a concrete Structured DataType . It can restrict the usage of fields of the Structured DataType and add meta data to fields ... Structured DataType , like providing the EngineeringUnits or EURange . In order to restrict the usage for each field of a Structured DataType , the following can be defined: What DataType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.2 DataTypeRefinement Objects

HasDataTypeRefinement Reference (see 7.30 ) or subtype from exactly one DataType Node representing a Structured DataType that is being refined. For each field having a refinement, a Variable of BaseDataVariableType ... that a field where subtypes are allowed, no longer allows subtypes. Depending on the Structured DataType, some limitations on the DataTypeRefinement occur. If the DataType of a field being refined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.3 Usage of DataTypeRefinements

subtype. Those References always starts from an instance of a Variable , where the Structured DataType is used. They point to an Object of DataTypeRefinementType or a subtype, which contains ... only allowed to be used on the concrete occurrence of the usage of the Structured DataType , that is on a Variable . DataTypeRefinements shall not be used from any DataType Node
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.6.2 SubtypeRestriction on fields of Structured DataTypes

SubtypeRestriction on fields of Structured DataTypes Using a SubtypeRestriction , it is possible to restrict the usage of subtypes on fields of a Structured DataType , by combining it with DataTypeRefinements
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.25 HasFieldDescription

semantic of this ReferenceType is to link from a DataTypeRefinement Object refining a Structured DataType to a Variable representing a field of that Structured DataType , containing additional metadata, that ... BrowseName of the Variable shall have the same name as the field of the Structured DataType that it refines, and the same NamespaceIndex as the DataType , where the field
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.26 HasFieldDescriptionSetMandatory

field shall be provided, although it is defined as optional field in the Structured DataType . This ReferenceType shall only be applied to fields declared as optional, i.e., fields having IsOptional ... true of Structured DataTypes with StructureType StructureWithOptionalFields
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.27 IsDisabledOptionalField

fields declared as optional, i.e., either fields having IsOptional set to true on Structured DataTypes where the StructureType is StructureWithOptionalFields; or fields of Structured DataTypes where the StructureType is Union
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.6 Argument

Argument This Structured DataType defines a Method input or output argument specification. It is for example used in the input and output argument Properties for Methods . Its elements are described
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.28 TimeZoneDataType

TimeZoneDataType This Structured DataType defines the local time that may or may not take daylight saving time into account. Its elements are described in Table 29 . Table 29 - TimeZoneDataType Definition
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.32 Structure

Structure This abstract DataType is the base DataType for all Structured DataTypes like Argument defined in 8.6 . While abstract Structures may be defined with no fields a non-abstract Structure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.39 EnumValueType

EnumValueType This Structured DataType is used to represent a human-readable representation of an Enumeration. Its elements are described in Table 31 . When this type is used in an array
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.4.3 Many Variables and / or Structured DataTypes

A.4.3 Many Variables and / or Structured DataTypes When structured data structures should be made available to the Client there are basically three different approaches: Create several simple Variables using simple ... used to group the Variables according to the structure of the data. Create a Structured DataType and a simple Variable using this DataType . Create a Structured DataType and a complex