Search

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

200 result(s) for DataTypes

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

4.1 Overview

Clause 6 defines details on the type model for ObjectTypes and VariableTypes . Standard ReferenceTypes , DataTypes and EventTypes are defined in Clauses 7 to 8.61 . The informative Annex A describes general
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.9.1 Overview

only accessible from the same machine. OPC 10000-5 defines the Objects , Methods and DataTypes used to represent and manage these mapping rules in the Address Space
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

shall be a valid NodeId of a DataType and shall not be null. Standard DataTypes are defined in Clause 8 . ValueRank M Int32 This Attribute indicates whether the Value Attribute ... ScalarOrOneDimension (-3): The value can be a scalar or a one dimensional array. All DataTypes are considered to be scalar, even if they have array-like semantics like ByteString
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.5 VariableType NodeClass

shall be a valid NodeId of a DataType and shall not be null. Standard DataTypes are defined in Clause 7.23 8 . ValueRank M Int32 This Attribute indicates whether the Value ... value can be a scalar or a one dimensional array. NOTE All DataTypes are considered to be scalar, even if they have array-like semantics like ByteString and String. ArrayDimensions
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.1 DataType Model

DataType NodeClass as shown in Figure 17 . Figure 17 - Variables, VariableTypes and their DataTypes In many cases, the NodeId of the DataType Node - the DataTypeId - will be well-known ... Clients and Servers . Clause 8 defines DataTypes and OPC 10000-6 defines their DataTypeIds . In addition, other organizations may define DataTypes that are well-known in the industry. Well-known
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.2 Encoding Rules for different kinds of DataTypes

Encoding Rules for different kinds of DataTypes Different kinds of DataTypes are handled differently regarding their encoding and according to whether this encoding is represented in the AddressSpace . Built ... DataTypes are a fixed set of DataTypes (see OPC 10000-6 for a complete list of Built-in DataTypes ). They have no encodings visible in the AddressSpace since the encoding
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.3 DataType NodeClass

DataType NodeClass The DataType NodeClass describes the syntax of a Variable Value . DataTypes are defined using the DataType NodeClass , as specified in Table 16 . Table 16 - DataType NodeClass Name ... DataTypeDefinition Attribute is used to provide the meta data and encoding information for DataTypes . The abstract DataTypeDefinition DataType is defined in 8.47 . Structure and Union DataTypes The Attribute shall
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.4 DataTypeEncoding and Encoding Information

HasEncoding References . These References shall be bi-directional. Figure 19 provides an example how DataTypes are modelled in the AddressSpace . Figure 19 - Example of DataType Modelling The information
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.2 DataTypeRefinement Objects

stays as an Int32 . Figure 20 - Example of a DataTypeRefinement As fields of Structured DataTypes may use Structured DataTypes , it may be desirable to refine fields of those fields
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.6.1 Overview

with UsesSubtypeRestriction . This is allowed since the DataType of Z:SampleVar is Number . The DataTypes always have to match exactly. The NoSubDataTypes is set to true, which is required, since
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.1 Overview

subtyping ReferenceTypes are described in 5.3.3.3 . There is no common definition for subtyping DataTypes , as described in 5.8.3 . The remainder of 6.3 specify subtyping rules for single inheritance on ObjectTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.26 HasFieldDescriptionSetMandatory

fields declared as optional, i.e., fields having IsOptional set to 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.1 General

General The remainder of 8 defines DataTypes . Their representation in the AddressSpace and the DataType hierarchy is specified in OPC 10000-5 . Other parts of this series of standards ... specify additional DataTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.14 Enumeration

Enumeration This abstract DataType is the base DataType for all enumeration DataTypes like NodeClass defined in 8.29 . All DataTypes inheriting from this DataType have special handling for the encoding ... defined in OPC 10000-6 . All enumeration DataTypes shall inherit from this DataType . Some special rules apply when subtyping enumerations. Any enumeration DataType not directly inheriting from the Enumeration DataType
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 ... shall have one or more fields defined directly or from a super type. All DataTypes inheriting from this DataType have special handling for the encoding as defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.40 OptionSet

OptionSet This abstract DataType is the base DataType for all DataTypes representing a bit mask which is larger than 64 bits or where the validity of the bits within ... identified. All OptionSet DataTypes representing bit masks shall inherit from this DataType . Its elements are described in Table 32 . Table 32 - OptionSet Definition Name Type Description OptionSet structure Value ByteString
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.41 Union

Union This abstract DataType is the base DataType for all union DataTypes . The DataType is a subtype of Structure DataType . All DataTypes inheriting from this DataType have special handling ... encoding as defined in OPC 10000-6 . All union DataTypes shall inherit directly from this DataType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.47 DataTypeDefinition

DataTypeDefinition This abstract DataType is the base type for all DataTypes used to provide the meta data for custom DataTypes like Structures and Enumerations
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.51 StructureField

defines a number of DataEncodings which specify how to serialize Structure DataTypes . Some of these DataEncodings are text based and make use of Name field. For this reason, the Name
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.52 EnumField

defines a number of DataEncodings which specify how to serialize Enumeration DataTypes . Some of these DataEncodings are text based and make use of Name field. For this reason, the Name
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.58 AccessLevelExType

ensure atomicity. The NoSubDataTypes Field represents the ability of a Variable to accept derived DataTypes . In general Variables are expected to allow the defined DataType or any subtype of that
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 ... DataTypes always reflecting parts of the simple structure. Objects are used to group the Variables according to the structure of the data. Create a Structured DataType and a simple Variable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.1 Background

marked with the stereotype <<TypeExtension>>. Those stereotyped UML objects represent DataTypes or ReferenceTypes . The domain model can contain user-defined ReferenceTypes and DataTypes , also marked
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.3 Extended notation

following rules define some special handling of structures. In general, values of all DataTypes should be represented by an appropriate string representation. Whenever a NamespaceIndex or LocaleId is used
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.1 AdditionalParametersType

they add prefix that ensures uniqueness. The same restriction applies to values which contain DataTypes with NamespaceIndexes . The components of this structure are defined in Table 108 . Table 108 - AdditionalParametersType
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.3 FilterOperator

nested RelatedTo operator. Operands that resolve to an ordered value are restricted to the DataTypes Byte , Int16 , Int32 , Int64 , SByte , UInt16 , UInt32 , UInt64 , Float , Double and DateTime . When testing
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.40.2.1 Overview

secret. If the TypeId does not resolve to one of the defined EncryptedSecret format DataTypes and a USERNAME UserIdentityToken has been provided then the Server may attempt to handle
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.40.2.3 EncryptedSecret Format

DataType describes how the Signature is calculated for different SecurityPolicies . The currently available EncryptedSecret DataTypes are defined in Table 184 . Table 184 - EncryptedSecret DataTypes Type Name When to Use RsaEncryptedSecret
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description Int32 Int32 -1 omitted or null A scalar Int32. Int32 ... level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.21 VectorType

DataType , defined in 12.23 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for each dimension of the vector ( Property VectorUnit
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.23 CartesianCoordinatesType

DataType , defined in 12.25 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for the coordinates ( Property LengthUnit ). The VariableType is formally
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.25 OrientationType

DataType , defined in 12.27 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for the orientation angles ( Property AngleUnit ). The VariableType
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.28 3DFrameType

space. It reflects the semantic of its DataType , defined in 12.30 . It refines the DataTypes and VariableTypes of the CartesianCoordinates and Orientation to the corresponding 3D types. The VariableType
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.2.9 DataTypes

DataTypes This standard Object is the browse entry point for DataTypes that the Server wishes to expose in the AddressSpace . DataType Nodes should be made available using Organizes References pointing ... either directly from the "DataTypes" Object to the DataType Nodes or using additional Folder Objects for grouping purposes. The intent is that all DataTypes of the Server exposed
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.3.1 General

sessions. Such a Variable also exposes all its information as Variables with simple DataTypes containing the same information as in the complex DataType . Not shown in Figure
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.1 General

General Standard DataTypes are described in the following subclauses
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.2 DataTypes defined in OPC 10000-3

DataTypes defined in OPC 10000-3 OPC 10000-3 defines a set of DataTypes . Their representations in the AddressSpace are defined in the following subclauses
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.3 DataTypes defined in OPC 10000-4

DataTypes defined in OPC 10000-4 OPC 10000-4 defines a set of DataTypes . Their representations in the AddressSpace are defined in the following subclauses
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.29 Frame

orientation of the frame using as DataType a subtype of Orientation . The concrete DataTypes need to be defined by the subtype. Both fields shall have the same number of dimensions
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.30 3DFrame

3DFrame DataType . It is a subtype of the Frame DataType and refines the DataTypes of its elements, as described in Table 281 . Table 281 - 3DFrame Structure Name Type Description 3DFrame
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.31 DataTypeSchemaHeader

this array maps to NamespaceIndex 1. structureDataTypes StructureDescription[] Description of Structure and Union DataTypes used in the data that follows the DataTypeSchemaHeader . This includes nested Structures . DataType NodeIds for Structure ... DataTypes used in the data refer to entries in this array. The StructureDescription DataType is defined in 12.33 . enumDataTypes EnumDescription[] Description of Enumeration or OptionSet DataTypes used in the data
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.32 DataTypeDescription

type for all DataType descriptions containing the DataType NodeId and the definition for custom DataTypes like Structures and Enumerations . The DataTypeDescription is formally defined in Table 285 . Table 285 - DataTypeDescription
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.34 EnumDescription

EnumDescription This Structure DataType provides the concrete DataTypeDescription for Enumeration or OptionSet DataTypes . It is a subtype of the DataTypeDescription DataType . The EnumDescription is formally defined in Table 289 . Table ... Int32 , the DataType is an Enumeration . If the builtInType is one of the UInteger DataTypes or ExtensionObject , the DataType is an OptionSet . Its representation in the AddressSpace is defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.35 SimpleTypeDescription

SimpleTypeDescription This Structure DataType provides the information for DataTypes derived from built-in DataTypes . It is a subtype of the DataTypeDescription DataType . The SimpleTypeDescription is formally defined in Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.36 UABinaryFileDataType

fileHeader KeyValuePair[] The file-specific header. body BaseDataType The body of the file. The DataTypes used in the body are described through the structureDataTypes , enumDataTypes and simpleDataTypes fields ... DataTypeSchemaHeader Structure which is the base type for the UABinaryFileDataType . DataTypes defined by OPC UA can be omitted. Its representation in the UABinaryFileDataType is defined in Table 294 . Table
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.45 BitFieldDefinition

MyBitFieldArrayType VariableType .The example illustrates how the StartBitPosition and EndingBitPosition are used with Array DataTypes . The first element of the array identified as bit positions 0 to 15 represent
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.1 Overview

following subclauses describe the design decisions made while modelling the Server Object . General DataTypes , VariableTypes and ObjectTypes such as the EventTypes described in this standard are not taken into account
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.10 Extensibility mechanism

Server vendors. There are preferred ways to provide the additional information. Do not subtype DataTypes to provide additional information about the Server . Clients might not be able to read those ... defined DataTypes and are not able to get the information, including the basic information. If information is added by several sources, the DataType hierarchy may be difficult to maintain. Note
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding

database table, so it is necessary to provide a self-contained representation of these DataTypes . This clause defines a normative String representation using the ABNF like notation (see IETF
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.1.19 Subtypes of Built-in Types

Subtypes of Built-in Types The subtypes of the built-in DataTypes described in 5.3.1 are encoded as the base built-in DataType
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

access to the associated metadata. These fields are not omitted when serialization uses abstract DataTypes such as Structure (i.e. ExtensionObject ) or BaseDataType (i.e. Variant ). OPC 10000-14 specifies the behaviour ... Publisher is misconfigured with metadata that uses abstract DataTypes
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

D.1 XML Schema

Schema Clause D.1 defines the XML Schema for all DataTypes and Messages defined in the OPC UA namespace The XML Schema released with this version of this document
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.1 Overview

reference that would make them visible in an AddressSpace. The tables defining the DataTypes in the specification have field names starting with a lowercase letter. The first letter shall ... when the field names are formally defined in a UANodeSet . Every UANodeSet that defines DataTypes has associated schema files that define how to serialize the DataTypes using the UA Binary
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.2 UANodeSet

String The URI for the XML schema namespace used to serialize values of the DataTypes defined by the Model. The field is required if DataTypes are defined in the UANodeSet
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.11 UADataType

forms. This is only used to define subtypes of the Structure , Enumeration or UInteger DataTypes . UInteger DataTypes only have this field if they represent an OptionSet . Purpose DataTypePurpose An enumeration ... DataType . It can be used by modelling tools and code generators to exclude DataTypes that are not necessary. Possible values are: Normal - The DataType is used in the AddressSpace . ServicesOnly
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.12 DataTypeDefinition

DataTypeDefinition type are defined in Table F.12 . This field is not be present for DataTypes that have no fields. Code generators may choose to create a class with no fields
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.13 DataTypeField

Node with its own DataTypeDefinition . This field is not specified for Enumeration or OptionSet DataTypes . ValueRank Int32 The value rank for the field. It shall be Scalar ... fixed rank Array (>=1). This field is not specified for Enumeration or OptionSet DataTypes . ArrayDimensions String The maximum length of an array. This field is a comma separated list
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.15 Example

rules for what is included. A useful guideline would include standard ReferenceTypes and DataTypes if they are referenced in the document. An Alias may be used for any NodeId value
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

G.2 JSON Schema Mapping

JSON Schema Mapping Clause G.2 defines the JSON Schema for all DataTypes defined in the OPC UA namespace. The JSON Schema for the CompactEncoding for all DataTypes released with this ... found here: https://reference.opcfoundation.org/files/opc.ua.services.jsonschema.compact.json?u=http://opcfoundation.org/UA/ The JSON Schema for the CompactEncoding for all DataTypes, excluding DataTypes used for only for Services, released with this version of this document
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.1 DataItemType

based on restrictions in the target environment. ValuePrecision can be used for the following DataTypes : For Float, Double, and Decimal values it specifies the number of digits after the decimal
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.3.3 MultiStateDiscreteType

elements in the array. NOTE The EnumStrings property is also used for Enumeration DataTypes (for the specification of this DataType , see OPC 10000-3 ). The StatusCode SemanticsChanged bit shall
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.3.4 MultiStateValueDiscreteType

lookup a name or help whenever they receive the numeric representation. Only DataTypes that can be represented with EnumValues are allowed for Variables of MultiStateValueDiscreteType . These are Integers
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.1 Overview

Overview Following is a description of the DataTypes defined in this specification. DataTypes like String , Boolean , Double or LocalizedText are defined in OPC 10000-3 . Their representation is specified
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.3 NumberRange

range. If a limit is not known In case of Floating-Point DataTypes: a NaN shall be used In case of Integer DataTypes : minimum or maximum value of the DataType
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.9 ProgramDiagnostic2Type VariableType

ProgramDiagnostic2Type VariableType This VariableType aggregates 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
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

UABinaryFileDataType . This information includes a namespace array and DataType descriptions. OPC UA namespace defined DataTypes are not included in the PubSubConfiguration . The DataTypeSchemaHeader of the DataSetMetaData shall be populated with ... necessary information. This includes all namespaces and DataTypes that are potentially contained in the associated DataSetMessages . DataTypes defined in the OPC UA namespace ( NamespaceIndex 0) that are not built
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

field is represented as RawData set by the DataSetFieldContentMask defined in 6.2.4.2 . (2) Enumeration DataTypes are encoded as Int32 . The Enumeration strings are defined through a DataType referenced through ... dataType field. (3) Structure and Union DataTypes are encoded as ExtensionObject . The encoding rules are defined through a DataType referenced through the dataType field. (4) DataTypes derived from built
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.9.2 PublishedDataSetCustomSourceDataType

further information is exposed for the source. OPC UA Applications shall use DataTypes derived from PublishedDataSetSourceDataType if they want to provide custom information about the source e.g. product specific configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.7.1 PublisherId

filter setting on the Subscriber side is contained in the DataSetReader parameters. Valid DataTypes are UInteger and String . A zero UInteger and a Null or empty String are invalid PublisherIds
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.1 PublisherId

parameter shall be ignored and all received NetworkMessages pass the PublisherId filter. Valid DataTypes are UInteger and String
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.4 DataSetMetaData

indices in NodeIds and BrowseNames contained in the messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes have the same structure but different DataType NodeIds , the Subscriber ... This includes ArrayDimensions and MaxStringLength information in the FieldMetaData and the StructureFields of Structure DataTypes . The verification should be executed at the start-up of the DataSetReader and when
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.12.1 PubSubConfigurationDataType

body. Examples are NodeIds contained in PublishedDataSets . The OPC UA namespace is skipped. The DataTypes used for configuration are defined in the OPC UA namespace. structureDataTypes StructureDescription[] Null or empty ... DataTypes used for configuration are defined by OPC UA. The DataTypes used in DataSetMetaData are described in the DataTypeSchemaHeader of the associated DataSetMetaData . This field is only used if KeyValuePairs
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.3 ConfiguredSize

reason would be to maintain predictable network behaviour even when using a volatile field DataTypes like String or ByteString
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

UADPFlags is false. The Id of the Publisher that sent the data. Valid DataTypes are UInteger and String . The DataType is indicated by bits 0-2 of the ExtendedFlags1 ... does not expect NetworkMessages from. PublisherIds are only equal if they have the same DataTypes and equal values. For ActionRequest and ActionResponse messages, the PublisherId of the Responder is used
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.11 RawData field encoding

padding only applies to RawData field encoding. All restrictions for the encoding of Structure DataTypes also apply to the RawData Field Encoding . A DataSet field is encoded in the DataType ... valueRank has a value of n > 0. This includes Structure fields with such DataTypes or ValueRank . DataSet fields and Structure fields shall not have an abstract DataType and shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

ensure that OPC UA aware Subscribers can fully reverse the payload to OPC UA DataTypes if they have access to the DataSetMetaData of the Publisher . The rules for the special ... Structure where the fields are described by the FieldMetaData . This includes fields with Enumeration DataTypes which are encoded using verbose Enumeration with the definition in the FieldMetaData . The additional simplification
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.3 VerboseEncoding and abstract type handling

information in the payload is required to fully reverse the payload to the original DataTypes for DataSet fields in the following cases where the DataSetMetaData is insufficient to unambiguously decode ... UaTypeId and UaType which means OPC UA DataSetReaders are not able to determine the DataTypes of the original values. If DataSetMetaData contains abstract types and RawData =TRUE is configured
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.3 SubscribedDataSetMirrorType

FieldMetaData . The properties in the FieldMetaData are created as Properties of the Variable . The DataTypes are created in the Subscriber from the DataSetMetaData if they do not exist. The NamespaceUri ... created DataTypes shall match the namespace contained in the DataSetMetaData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

4.3 Features

SafetyProvider . Length of user data: 1 octet to 1 500 octets, structures of basic DataTypes
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

SafetyProvider requires its own copy of the Methods which contain the concrete DataTypes for OutSafetyData and OutNonSafetyData . Figure 4 - Instances of Server Objects for this document
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.2 Safety ObjectType definitions

testing, the following restrictions apply to instances of SafetyProviderType and SafetyConsumerType (or instances of DataTypes derived from SafetyProviderType or SafetyConsumerType ): The references shown in Figure 4 originating at SafetyProviderType ... DataType of both Properties and MethodArguments shall be used as specified, and no derived DataTypes shall be used (exception: OutSafetyData and OutNonSafetyData ). In IEC 62541, the order of Method arguments
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.4 ResponseSPDUDataType

RQ6.7] To define the concrete DataType for the ResponseSPDU (which specifies the concrete DataTypes for SafetyData and NonSafetyData , respectively), proceed as follows: (1) Derive a concrete DataType from the abstract
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.4 SafetyProvider version

Method when using Client/Server communication or RequestSPDUV2DataType and ResponseSPDUV2DataType for the SPDU DataTypes when using PubSub communication), allowing a SafetyProvider to implement multiple versions of this document at the same
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.5 DataTypes and length of SafetyData

DataTypes and length of SafetyData This document supports sending of the Built-in and Simple DataTypes specified in OPC UA (see OPC 10000-3 and OPC 10000-6) within SafetyData ... supported DataTypes are vendor-specific. [RQ6.9] Only scalar DataTypes shall be used. Arrays are currently not supported by this document. The supported maximum length of the SafetyData is vendor-specific
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.5 Signature over the SafetyData Structure (SafetyStructureSignature)

Signature over the SafetyData Structure (SafetyStructureSignature) SafetyStructureSignature is used to check the number, DataTypes , and order of application data transmitted in SafetyData . If the SafetyConsumer is expecting anything different than ... using a different version number. OPC 10000-3, 5.8.2 defines different categories of DataTypes . Regarding the DataTypeEncodingID which is to be used within the SafetyStructureSignature , the following holds: For Built
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

RQ6.4 Provide SPDUs for diagnostics in Method ReadSafetyDiagnostics 6.2.2.1 SafetyACSet Object RQ6.5 Restrictions on DataTypes 6.2.2.2 Safety ObjectType definitions RQ6.6 Non-abstract DataTypes for out data 6.2.2.2 Safety ObjectType definitions ... RQ6.7 Definition of concrete DataTypes for ResponseSPDU 6.2.3.4 ResponseSPDUDataType RQ6.8 Usage of NonSafetyDataPlaceHolder 6.2.3.4 ResponseSPDUDataType RQ6.9 Restriction to scalar types 6.2.5 DataTypes and length of SafetyData RQ6.10 List supported DataTypes
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

5 AliasNames Information Model overview

overview The AliasNames functionality (illustrated in Figure 1 ) defines a number of ObjectTypes , Methods , DataTypes and References . Figure 2 illustrates an example of the Object model defined for AliasNames . Figure
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

7.1 Overview

Overview The following DataTypes are defined for the AliasNames model
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

4.1 Type and Naming Conventions

IEEE to allow an effortless mapping against existing network technologies. Therefore, selected DataTypes shall fit to the types used by the related managed objects of IEEE and IETF. BrowseNames
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.2 SerializationEntity

Variable containing the SerializationValue and allows the configuration of the SerializationScope and the Serialization DataTypes
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.6 SerializationFieldDataType

Structures ) and contain the SerializationFieldDataType s of child Nodes . The SerializationFieldDataType s are Structure DataTypes created by the Server
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.4 SerializationScope and SerializationEntity

DataType of the Variable itself. Dependent on SerializationProperties, Variables can be represented by Structure DataTypes also (see 6.4.2 ). If the Variable has children in the SerializationScope , the SerializationFieldDataType
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.1 Overview

shown in Figure 6 , the SerializationFieldDataTypes of the Variables in the SerializationScope equal the DataTypes of the original Values . Figure 6 - Example: Instance-specific serialization for the Object "MyObject
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.2 Limitations

characters used for the BrowseNames must be permissible in field names of Structure DataTypes . To achieve this, it is recommended to limit the characters used in BrowseNames to letters (lower
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.3 RIO Channel Process Values

generated QualifierValueStructureDataType structures are not shown in the table visualizing the nested structure DataTypes , whereas the JSON snippet shows these structures in-depth. Figure A.3 - RIO Channel Process Values
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

1 Scope

collect diagnostic information in a system. The LogObject model and related Events , Methods and Datatypes are defined in this specification
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.1 Namespace metadata

Table 256 define the namespace metadata for this document. Table 254 defines DataTypes that are shared between the AutomationComponent and the ConnectionManager . Table 255 defines the namespace associated with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

wire. This includes which Nodes are used for the Values , their DataTypes (on the wire and native), the size (if an array or string) and the possible pre-processing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.1 Overview

F.1.1 Overview This section describes DataTypes that can be used to serialise the Objects that compose a ConnectionConfigurationSet (see 6.8 and 6.10 ) into a single structure ( ConnectionConfigurationSetDataType) . The ConnectionConfigurationSetDataType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.2 Namespaces

Figure F.2 - Scopes within a ConnectionConfigurationSet To reduce the overall size of the DataTypes defined in this Clause (i.e. ConnectionConfigurationSetConfDataType ), NodeId , AliasName and RelativePath are used instead of their portable ... related ServerAddressConfDataType . A ConnectionManager can map NodeId and RelativePath contained in the DataTypes to their portable versions using the NamespaceUri from the Namespace array when it loads the ConnectionConfigurationSet from
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.3 SelectionListType

Variable. A generic definition would create additional overhead since the values can have different DataTypes . To simplify the handling of SelectionListType , each Variable that is of SelectionListType is mapped
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.4 Extensibility

F.1.2.4 Extensibility Structured DataTypes can only be extended by subtyping. This is a problem if Structures are embedded into other Structures , e.g., the ConnectionConfigurationSet -related Structure has an array
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.2 ConnectionConfigurationSet file content

content, http://opcfoundation.org/UA/FX/Data/ may also be required. structureDataTypes 0:StructureDescription[] Null or empty DataTypes used for configuration are defined by OPC UA FX. enumDataTypes 0:EnumDescription[] Null or empty ... DataTypes used for configuration are defined by OPC UA FX. simpleDataTypes 0:SimpleTypeDescription[] Null or empty DataTypes used for configuration are defined by OPC UA FX. schemaLocation 0:String Null
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.2 Built-in Types

A.3.2 Built-in Types Table A.2 shows the mapping of the simple built-in DataTypes in OPC UA that correspond to simple XML schema types used in AML. Each ... built-in UA DataTypes is defined as an AML AttributeType in the AttributeType Library for the base OPC UA Namespace . Table A.2 - Mapping simple built-in Datatypes UA DataType
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.3 Structures

derived from other Structures and composed of any other OPC UA DataTypes . Similarly, AML AttributeTypes can be derived from other AML AttributeTypes and composed of any other AttributeTypes. This allows ... DataTypes (including Structures ) to appear as AML AttributeTypes with the same derivation and composition structure as seen
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.4 Arrays

Arrays Arrays are most naturally represented as lists in XML, so in AML, array DataTypes are represented as XML lists. The AML AttributeType Library of an OPC UA Namespace defines ... number of lists for arrays of UA DataTypes , of which a subset is shown in Figure A.3 . The same pattern shall be used to construct arrays of any derived DataTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7 DataTypes with special mappings

A.3.7 DataTypes with special mappings The following complex DataTypes have special mappings that are non-intuitive
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.6 VariableType mapping

configured values. BaseDataType is the root abstract DataType from which all other OPC UA DataTypes derive. The semantic implied by this is that the Value of an instance ... alter the DataType of Value to be more restrictive. This could be other abstract DataTypes like the Number AttributeType or a concrete AttributeType from an OPC UA-based AML AttributeTypeLibrary
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

B.1.4 UA AttributeType Library

opcfoundation.org/UA/" defines the AttributeTypes that correspond to their equivalent OPC UA DataTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

C.1.3 DI AttributeType Library

opcfoundation.org/UA/DI/" defines the AttributeTypes that correspond to their equivalent OPC DI DataTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

D.1.3 OPC UA FX AttributeType Libraries

opcfoundation.org/UA/FX/CM" define the AttributeTypes that correspond to their equivalent OPC UA FX DataTypes . OPC UA FX SystemUnitClass Libraries The SystemUnitClass Libraries "SUC_ http://opcfoundation.org/UA/FX/AC"
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.6 UAFX ConnectionManager

File , the CloseAndUpdate Method , including the ElementAdd , ElementRemove and ElementReplace Operations , and all related DataTypes for the File content. Server UAFX ConnectionManager Exposes CCSs Exposes a ConnectionConfigurationSet for each
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.1.7 Parameters

Clients shall always pass null. Future versions of this specification can define concrete DataTypes . If the restore of parameters succeeds but the software cannot run properly this should
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.4 Structures

without optional fields where none of the fields allows subtype (except fields with abstract DataTypes ). Its definition is in Table 12 . Table 12 - Structures without optional fields where none ... with optional fields where none of the fields allows subtypes (except fields with abstract DataTypes ). Its definition is in Table 13 . Structures with fields that are optional have
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value, a subtype
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

5.1.6.1 General

represented as complex Variables ( Variable with nested sub-variable) and/or as complex DataTypes , where a DataType has a structure or other special meaning associated with it. Each of the nested
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.1 General

defined for Variables . Most of the CDTs, defined in CCTS , are defined as CDT DataTypes in this standard but some CDTs are mapped to OPC UA Built-in DataTypes directly ... client to obtain the value for the CDT DataType supplemental Properties . However, for some DataTypes or VariableTypes the supplemental Properties may have different values on instances than the default value
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.2.1 General

Content Component. These data types are mapped to OPC UA CC (Content Component) DataTypes which are OPC UA Built-in DataTypes or DataTypes defined in the following clauses. Table ... defines mapping between the primitive data types for the Content Component and the CC DataTypes . Table 10 - Built-in data types CCTS Primitive data type OPC UA CC DataType Description
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.3.1 General

General All data types defined as CDT are mapped to CDT DataTypes or CC DataTypes . Table 20 defines mapping of data types between CCTS and OPC UA. Table
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.3.2 CDTAmountDecimal

CDTAmountDecimal is a DataType that conforms to Amount type. Table 21 defines the DataTypes . Table 21 - DataTypes for Amount Content Component data type for Amount OPC UA CC DataType
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.3.8 CDTMeasure

CDTMeasure The CDTMeasure is a generic term for DataTypes that conform to the Measure type. The actual DataTypes are defined separately according to each primitive data type of content component ... Table 28 defines the DataTypes . Table 28 - DataTypes according to CDTMeasure Content Component data type OPC UA CC DataType OPC UA CDT DataType Decimal Decimal CDTMeasureDecimal Double Double CDTMeasureDouble Float
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

6.3.11 CDTRate

CDTRate The CDTRate is a generic term for DataTypes that conform to the Rate type. The actual DataTypes are defined separately according to each primitive data type of content component ... Table 32 defines the DataTypes . Table 32 - DataTypes according to CDTRate Content Component data type OPC UA CC DataType OPC UA CDT DataType Decimal Decimal CDTRateDecimal Double Double CDTRateDouble Float
OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control

5 Modelling Approach of ISA-95

Responses. Data types from the ISA-95 model are mapped to OPC UA DataTypes (i.e. strings if localized are mapped to LocalizedText
OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control

6.1 General

representation of the ISA-95 data model in OPC Methods , ObjectTypes , VariableTypes , DataTypes and ReferenceTypes . This model generates standard types. All ISA-95 types will be defined in their ... DataType naming: All ObjectTypes include "ObjectType" as part of the name All DataTypes that are structures include "DataType" as part of the name, this
OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition

3.4.2.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value, a subtype
OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-10101 – OPC UA for WoT Binding

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value, a subtype
OPC-10101 – OPC UA for WoT Binding

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.1.3.3 Object Diagnostics

Identifier which was accessed by the command. The DataType can be one of the DataTypes defined in the ScanData Union defined in 9.4.2 . Due to the use case for limited
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.1.3.9 Variable LastScanData

Variable represents the last scanned AutoID Identifier . The DataType can be one of the DataTypes defined in the ScanData Union defined in 9.4.2 . Due to the use case for limited ... Data Access functionality. Such OPC UA Clients are typically limited to built-in DataTypes like String or ByteString too. The use of this Variable implies the following restrictions. Only
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.1.3.10 Variable LastScanTimestamp

Data Access functionality. Such OPC UA Clients are typically limited to built-in DataTypes like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.2 Object Diagnostics

from the Rfid Transponder by the command. The DataType can be one of the DataTypes defined in the ScanData Union defined in 9.4.2 . Due to the use case for limited
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.11 Variable LastScanAntenna

Data Access functionality. Such OPC UA Clients are typically limited to built-in DataTypes like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.12 Variable LastScanRSSI

Data Access functionality. Such OPC UA Clients are typically limited to built-in DataTypes like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier
OPC-30020 – MDIS OPC UA Companion Specification

4.3.4.1 Concepts

type as if it was of the parent type. With regard to DataTypes , if a Variable is defined to have a numeric value, a subtype could restrict the value
OPC-30020 – MDIS OPC UA Companion Specification

4.3.4.3 Companion Specifications

specification for an industry specific vertical market describes an InformationModel by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market. Table 3 contains
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model

10.3.1 General

General BACnet bit strings data types are mapped to OPC UA Structure DataTypes derived from the OptionSet DataType defined in OPC 10000-5 . The OptionSet structure contains the field value ... ByteString. The validBits field indicates which bits in the field value are valid. All DataTypes defined in this clause are derived from the OptionSet DataType and expose the list
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model

10.4.1 General

General BACnet ENUMERATED definitions are mapped to OPC UA Enumeration DataTypes . All DataTypes in this clause derived from the Enumeration DataType defined
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model

10.5.1 General

General BACnet SEQUENCE definitions are mapped to OPC UA Structure DataTypes . BACnet CHOICE definitions are mapped to OPC UA Union DataTypes . These types are defined
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model

10.6.1 General

General BACnet CHOICE definitions are mapped to OPC UA Structure DataTypes derived from the Union DataType defined
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

4.3.4.3 Companion Specifications

industry specific vertical market describes an information model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market. Table 1 contains an example
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

5 Modelling Approach of PackML

reflect the state of the system Methods to issue commands to the Server DataTypes
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.1 General

information model is a representation of the PackML data model in OPC ObjectTypes , VariableTypes , DataTypes and ReferenceTypes . This model generates standard types. All PackML types will be defined in their ... State", All Transitions will end in "Transition" All DataTypes that are structures include "DataType" as part of the name, this is to be able
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

Annex C : DataType (Non-Normative)

data types The mapping of IEC 61131-3 generic data types to OPC UA DataTypes is formally defined in OPC 30000 (PLCOpen companion specification). Table 72 . is copied from that
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

C.1 Mapping of enumerated data types

data type or on a variable instance. In OPC UA the enumerated DataTypes are defined as subtypes of Enumeration . The data has an EnumStrings Property that contains the possible string
OPC-30060 – OPC UA for Tobacco Machine Communication

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30060 – OPC UA for Tobacco Machine Communication

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30060 – OPC UA for Tobacco Machine Communication

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

3.4.1.1 Node definitions

HasModellingRule Reference to point to the corresponding ModellingRule Object . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar Int32 ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

3.4.3.6 Structures

without optional fields where none of the fields allows subtype (except fields with abstract DataTypes ). Its definition is in Table 12 . Table 12 - Structures without optional fields where none ... with optional fields where none of the fields allows subtypes (except fields with abstract DataTypes ). Its definition is in Table 13 . Structures with fields that are optional have
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>

3.3.5.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30140 – OPC UA for PROFINET

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in [OPC 10000-3] . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30140 – OPC UA for PROFINET

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30140 – OPC UA for PROFINET

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30141 – OPC UA for PROFIenergy

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in [OPC 10000-3] . Attributes not marked as optional are mandatory and shall be provided by the Server
OPC-30141 – OPC UA for PROFIenergy

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30141 – OPC UA for PROFIenergy

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30142 – OPC UA for PROFINET Remote IO

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30142 – OPC UA for PROFINET Remote IO

4.3.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30142 – OPC UA for PROFINET Remote IO

4.3.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30142 – OPC UA for PROFINET Remote IO

9.2 Process Value VariableTypes

Process Value VariableTypes Table 62 lists the Process Value VariableTypes and their DataTypes defined for RIOforPA and RIOforFA. There are different VariableTypes together with their DataTypes defined for each profile ... digital and analog Process Values . Table 62 - RIO Process Value VariableTypes and DataTypes Profile Digital Channel Types Process Value VariableType DataType RIOforPA RioPaDigitalProcessValueVariableType RioPaDigitalProcessValueDataType RIOforFA RioFaDigitalProcessValueVariableType RioFaDigitalProcessValueDataType Analog Channel Types
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.5.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.5.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.4.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.4.4 Structures

without optional fields where none of the fields allows subtype (except fields with abstract DataTypes ). Its definition is in Table 12 . Table 12 - Structures without optional fields where none ... with optional fields where none of the fields allows subtypes (except fields with abstract DataTypes ). Its definition is in Table 13 . Structures with fields that are optional have
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value, a subtype
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

3.5.1.1 Node definitions

null or is omitted. Examples are given in Table 1 . Table 1 - Examples of DataTypes Notation DataType ValueRank ArrayDimensions Description 0:Int32 0:Int32 -1 omitted or null A scalar ... VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies. For additional details
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

3.5.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.2.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

7.1 DriveAxisType

Signals , the DataType shall be 0:UInt32 . For Signals with sign, the corresponding signed DataTypes 0:Int16 and 0:Int32 shall be provided. Monitoring folder in Actual and Command Values
OPC-30200 – OPC UA for Commercial Kitchen Equipment

3.4.3.1 General

General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided
OPC-30200 – OPC UA for Commercial Kitchen Equipment

4.3.1 Concepts

treat the new type as if it was of the parent type. Regarding DataTypes , subtypes can only restrict. If a Variable is defined to have a numeric value
OPC-30200 – OPC UA for Commercial Kitchen Equipment

4.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects