Search

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

99 result(s) for DataSetMessages

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.22 NetworkMessage

NetworkMessage DataSetMessages and header to facilitate delivery, routing, security, and filtering Note 1 to entry: The Publisher hands off the NetworkMessage to the Message Oriented Middleware (transport layer) to deliver ... DataSetMessages to the Subscribers . Note 2 to entry: The term message is used with various connotations in the messaging world. The Publisher might like to think of the message
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.42 Subscriber

Subscriber entity receiving DataSetMessages from a Message Oriented Middleware Note 1 to entry: A Subscriber can be a native OPC UA Application or an application that has just knowledge about ... Message Oriented Middleware and the rules for decoding the NetworkMessages and DataSetMessages . A Subscription in the OPC UA ClientServer model has a different meaning than the Subscriber in the PubSub
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.4 DataSetReader

DataSetReader entity receiving DataSetMessages from a Message Oriented Middleware Note 1 to entry: A DataSetReader is the component that extracts a DataSetMessage from a NetworkMessage received from the Message Oriented
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.5 DataSetWriter

DataSetWriter entity creating DataSetMessages from DataSets and publishing them through a Message Oriented Middleware Note 1 to entry: A DataSetWriter encodes a DataSet to a DataSetMessage and includes the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.1 General

Each NetworkMessage includes header information (e.g. identification and security data) and one or more DataSetMessages (the payload). The DataSetMessages may be signed and encrypted in accordance with the configured message ... DataSet . A component of a Publisher called DataSetWriter generates a continuous sequence of DataSetMessages . Syntax and semantics of DataSets are described by DataSetMetaData . The selection of information for a DataSet
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.1 General

DataSet . For publishing, a DataSet will be encoded into a DataSetMessage . One or more DataSetMessages are combined to form the payload of a NetworkMessage . Figure 3 illustrates
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.2 DataSetClass

DataSetClass . The DataSetClassId shall be in the corresponding field of the DataSetMetaData . When all DataSetMessages of a NetworkMessage are created from DataSets that are instances of the same DataSetClass
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.3 DataSetMetaData

fields in the DataSetMetaData shall match the order of values in the published DataSetMessages . The DataSetMetaDataType is defined in 6.2.3.2.3 . Example description (simplified, in pseudo-language): Name: "Temperature-Sensor ... DataSetMetaData is sent as a NetworkMessage from the Publisher to the Subscriber before DataSetMessages with changed content are sent. The used Message Oriented Middleware should ensure reliable delivery
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.1 General

mean the message handed off and received from a specific Message Oriented Middleware . DataSetMessages are embedded in NetworkMessages . Figure 4 shows the relationship of these message types. Figure ... NetworkMessage . The concrete structure depends on the message mapping and is described in 7.2 . DataSetMessages are just one of the possible MessageTypes transported within a NetworkMessage. The different MessageTypes
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.3 DataSetMessage

configured DataSetMessageContentMask , a DataSetMessage may exist in different forms and with varying detail. DataSetMessages do not contain any information about the data acquisition or information source in the Publisher . Additional ... DataSetMetaData. Status Status information about the data in this DataSetMessage. Keep alive When no DataSetMessages are sent for a configured time period, a keep alive DataSetMessage is sent to signal
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.4 NetworkMessage

messages of different MessageTypes defined in 7.2 . A NetworkMessage can contain an array of DataSetMessages and includes information shared between DataSetMessages . This information consists of: PublisherId Identifies the Publisher . Security ... fields out of the DataSet also sent in the header. Payload One or more DataSetMessages. The payload, consisting of the DataSetMessages will be encrypted in accordance with the configured message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.8 Topics

Mappings to different implementation technologies may add additional constraints. A Topic for NetworkMessages containing DataSetMessages is typically used as QueueName for the broker-based communication configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.1.2 Message sending

collection. In the next step, a DataSetWriter takes the DataSet and creates a DataSetMessage . DataSetMessages from DataSetWriters in one WriterGroup can be inserted into a single NetworkMessage . The creation
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.2.1 General

unencrypted data in the NetworkMessage header to support identifying and filtering of relevant Publishers, DataSetMessages , DataSetClasses or other relevant message content (see 5.3 ). If a NetworkMessage is signed or signed ... proper security keys (see 5.3.5 ) to verify the signature and decrypt the relevant DataSetMessages . Once a DataSetMessage has been selected as relevant, it will be forwarded to the corresponding DataSetReader
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.2.2 Broker-less model with OPC UA UDP

Publisher OPC UA Address Space . For each DataSet a DataSetMessage is created. The DataSetMessages are sent in a NetworkMessage to the IP multicast address. OPC UA Applications like HMI applications ... they are interested in. An OPC UA Application that maps data fields from UADP DataSetMessages to internal Variables can be configured through the DataSetReader Object and dispatcher in the Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.1 Overview

known on the Subscriber side to configure DataSetReaders and to filter and process DataSetMessages . Figure 20 - PubSub component overview Figure 20 shows the following components: PublishedDataSet contains the DataSetMetaData describing ... PublishedDataSet and the corresponding data acquisition parameters. DataSetWriter parameters are necessary for creating DataSetMessages . Each DataSetWriter is bound to a single PublishedDataSet . A PublishedDataSet can have multiple DataSetWriters . WriterGroup parameters
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.1 Overview

DataSet . See 5.2 for the introduction to DataSets , 5.3 for the introduction to DataSetMessages and 5.4.1.2 for an introduction to the different source options and the parameters for sending ... DataSetMessages . The content of a DataSetMessage is defined by the DataSetMetaData. This information is required for interoperability between Publisher and Subscriber . See 6.2.3.2 . The information source is only necessary
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.1 General

shall match the order of DataSet fields when they are included in the published DataSetMessages . The DataSetMetaDataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

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-in types
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

type values are defined in OPC 10000-6 . All data types are transferred in DataSetMessages as one of the built-in data types. In most cases the identifier ... updated. The Property in the FieldMetaData shall correctly describe the Field Value in the DataSetMessages . For example if the Property is EngineeringUnits , the unit of the Field Value shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.6 ConfigurationVersionDataType

Subscriber shall use DataSetMetaData for decoding with a majorVersion that matches the majorVersion in DataSetMessages sent by the Publisher . Removing fields from the DataSet content, reordering fields, adding fields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.7.1 PublishedData

configuration tools. It is used as a handle to reference the Value in DataSetMessages received by Subscribers . The index may change after configuration changes. Changes are indicated by the ConfigurationVersion
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.8.2 SelectedFields

null or the field value can be a StatusCode . The encoding of Event based DataSetMessages shall be able to handle these cases. ExtensionFields defined for the instance of the PublishedEventsType ... role for Subscribers. It is used as handle to reference the Event field in DataSetMessages received by Subscribers . The index may change after configuration changes. Changes are indicated
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.9.1 CyclicDataSet

CyclicDataSet The CyclicDataSet with DataType Boolean defines the type of DataSetMessages created by the PublishedDataSet . If CyclicDataSet is false, event DataSetMessages are sent acyclicly and a related DataSetWriter shall ... KeyFrameCount of 0. If CyclicDataSet is true, key frame or delta frame DataSetMessages are sent and a related DataSetWriter shall use a KeyFrameCount that is greater than or equal
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.1 DataSetWriterId

unique ID of the DataSetWriter for a PublishedDataSet . It is used to select DataSetMessages for a PublishedDataSet on the Subscriber side. It shall be unique across all DataSetWriters
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.3 KeyFrameCount

frame message with values for all published Variables is sent. The delta frame DataSetMessages contains just the changed values. If no changes exist, the delta frame DataSetMessage shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.5.1 DataSetWriterDataType

name of the corresponding PublishedDataSet . If the DataSetWriter is used to create heartbeat DataSetMessages , the dataSetName shall be null or empty. DataSetWriterProperties KeyValuePair[] Defined in 6.2.4.4 . TransportSettings DataSetWriterTransportDataType Transport mapping
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.2 PublishingInterval

DataType Duration defines the interval in milliseconds for publishing NetworkMessages and the embedded DataSetMessages created by the related DataSetWriters . Negative values are invalid. If the PublishingInterval is 0, the KeyFrameCount ... cyclic PublishedDataSets like Event based DataSets , this may result in zero to many DataSetMessages produced for one PublishedDataSet in a PublishingInterval . All Events that occur between two PublishingIntervals shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.3 DataSetWriterId

value is 0 (null), the parameter shall be ignored and all received DataSetMessages pass the DataSetWriterId filter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.4 DataSetMetaData

DataSetMetaData The parameter DataSetMetaData provides the information necessary to decode DataSetMessages from the Publisher . If the DataSetMetaData changes in the Publisher and the MajorVersion was changed, the DataSetReader needs ... DataSetMetaData contains an empty fields array, the DataSetReader is configured to receive heartbeat DataSetMessages . For heartbeat DataSetMessages the majorVersion and minorVersion in the configurationVersion shall always
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.5 DataSetFieldContentMask

parameter DataSetFieldContentMask with DataType DataSetFieldContentMask indicates the fields of a DataValue included in the DataSetMessages . The parameter shall be ignored for heartbeat messages. The DataSetFieldContentMask DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.6 MessageReceiveTimeout

MessageReceiveTimeout The parameter MessageReceiveTimeout is the maximum acceptable time between two DataSetMessages . The time starts when the state of the DataSetReader changes to Operational . If there is no new DataSetMessage ... DataSetReader State shall be changed to Error until the next DataSetMessage is received. The DataSetMessages that reset the period include keep-alive and heartbeat messages. A DataSetMessage is considered
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.13.1 DataSetReaderDataType

concrete subtypes are defined in 6.2.10 . If the DataSetReader is configured to receive heartbeat DataSetMessages , the field shall be null. The StandaloneSubscribedDataSetDataType subtype shall not be used in this structure
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.1 SubscribedDataSetDataType

defines the metadata for the subscribed DataSet and the information for the processing of DataSetMessages . See 5.4.2.2 for an introduction to the processing options for received DataSetMessages . The SubscribedDataSetDataType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.3.1 General

Subscriber AddressSpace with a mirror Variable for each DataSet field in the received DataSetMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.5 StandaloneSubscribedDataSetDataType

String array. DataSetMetaData DataSetMetaDataType Defined in 6.2.9.4 . A Publisher must be configured to send DataSetMessages that comply with the DataSetMetaData in the standalone subscribed DataSet . SubscribedDataSet SubscribedDataSet‌DataType The SubscribedDataSet specific
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.3 DataSetOrdering

DataSetOrdering The DataSetOrdering defines the ordering of the DataSetMessages in the NetworkMessages . Possible values for DataSetOrdering are described in Table 95 . The default value is Undefined . The DataSetOrderingType ... enumeration that specifies the possible options for the ordering of DataSetMessages inside and across NetworkMessages . The possible enumeration values are described in Table 95 . Table 95 - DataSetOrderingType values Name Value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.4 NetworkMessageContentMask

DataSetClassId is included in the NetworkMessage s. The NetworkMessage can only contain DataSetMessages with the same DataSetClassId . If DataSetMessages have different DataSetClassIds they must be sent in individual NetworkMessages . PromotedFields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.4 NetworkMessageNumber

flag in the NetworkMessageContentMask is false. If the NetworkMessage layout is fixed and all DataSetMessages of a WriterGroup fit into one single NetworkMessage , the value of NetworkMessageNumber shall ... DataSetMessages of a WriterGroup are distributed or chunked over more than one NetworkMessage , the first NetworkMessage in a PublishingInterval shall be generated with the value 1, the following NetworkMessages shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.6 DataSetMessage‌ContentMask

DataSetMessageContentMask with the DataType UadpDataSetMessageContentMask indicates the optional header fields included in the DataSetMessages . The UadpDataSetMessageContentMask DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.1.1 NetworkMessageContentMask

DataSetClassId is included in the NetworkMessage s. The NetworkMessage can only contain DataSetMessages with the same DataSetClassId . If DataSetMessages have different DataSetClassIds they must be sent in individual NetworkMessages . ReplyTo
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.4.2 DataSetMessage‌ContentMask

DataSetMessageContentMask with the DataType JsonDataSetMessageContentMask indicates the optional header fields included in the DataSetMessages . The JsonDataSetMessageContentMask DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.6.4 Topic

contains the unique name of the data stream from the Publisher that contains the DataSetMessages of interest for the DataSetReader . The Topic is defined by the Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.5.1 QueueName

only valid if the NetworkMessages from the WriterGroup for this DataSetWriter contain only DataSetMessages from this DataSetWriter . If this String is not null or empty, it overrides the QueueName
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.5.5 MetaDataQueueName

message mappings like UADP, the Subscriber needs access to the DataSetMetaData to process received DataSetMessages . The Publisher can provide the DataSetMetaData through a dedicated queue. The parameter MetaDataQueueName with
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.1 General

messages on the Subscriber side. Other optional fields like PublisherId , DataSetWriterId or sizes of DataSetMessages are typically necessary for the processing of messages in generic Subscribers . If such fields ... payload. In this case the DataSetWriterId , the offset and size of the DataSetMessages is known from the DataSetReader configuration. The identification is done in this case by the group header
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.3 Error handling

defined in Clause 6 provide the settings for mapping information from the Publisher into DataSetMessages , settings to send them in NetworkMessages to the Subscribers and settings to process the DataSetMessages ... between Publisher and Subscriber is in sync. In several combinations of settings for the DataSetMessages and NetworkMessages , a Subscriber is able to process received messages without further knowledge
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

PromotedFields enabled If Promoted fields are enabled, the number of DataSetMessages in the Network Message shall be one. Bit range 2-4: UADP NetworkMessage type 000 NetworkMessage with DataSetMessage payload ... response. DataSetClassId Guid The DataSetClassId associated with the DataSets in the NetworkMessage. All DataSetMessages in the NetworkMessage shall have the same DataSetClassId. The DataSetClassId shall be omitted
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.4 UADP Chunk NetworkMessage

DataSetWriter responsible for sending Messages for the DataSet . A Subscriber can skip DataSetMessages from DataSetWriters it does not expect DataSetMessages from. Table 159 - Chunked NetworkMessage payload fields Name Type Description
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.2 DataSet payload header

false. Table 160 - UADP DataSet payload header Name Type Description Count Byte Number of DataSetMessages contained in the NetworkMessage . The NetworkMessage shall contain at least one DataSetMessage if the NetworkMessage ... DataSetWriter responsible for sending Messages for the DataSet . A Subscriber can skip DataSetMessages from DataSetWriters it does not expect DataSetMessages from
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.3 DataSet payload

DataSet payload Name Type Description Sizes UInt16 [Count] List of byte sizes of the DataSetMessages . The size of the list is defined by the Count in the DataSet payload header ... payload size exceeds 65535, the DataSetMessages shall be allocated to separate NetworkMessages . If a single DataSetMessage exceeds the payload size it shall be split into Chunk NetworkMessages . This field shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.5 Data Key Frame DataSetMessage

following structure shall not be encoded into the DataSetMessage . Generic Subscribers can detect heartbeat DataSetMessages if the DataSetMessage size equals the header size. If the DataSetMessage size is not part
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.7 Event DataSetMessage

DataSetMessage . DataSetFields BaseDataType [FieldCount] The field values of the DataSet. The fields of Event DataSetMessages shall be encoded as Variant. The Field Encoding DataSetFlags1 of the DataSetMessage header
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.10 Action response message

DataSetFields BaseDataType [FieldCount] The field values of the ActionResponse DataSet. The fields of ActionResponse DataSetMessages shall be encoded as Variant or RawData. Padding Byte [*] Optional padding added if the encoded
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

NetworkMessage containing DataSetMessages Each JSON NetworkMessage can contain one or more JSON DataSetMessages . The JSON NetworkMessage is a JSON object with the fields defined in Table 184 . Table 184 - JSON ... present. MessageType String This value shall be "ua-data" for NetworkMessages containing DataSetMessages . This value is always present. PublisherId String A unique identifier for the Publisher . It identifies
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

changed fields. DataSetWriter s may periodically provide keep-alive messages which are DataSetMessages without any Payload field. Table 185 - JSON DataSetMessage definition Name Type Description DataSetWriterId UInt16 An identifier
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

includes default values. The main use case for the VerboseEncoding is the payload of DataSetMessages . The VerboseEncoding and the following rules for DataSet field encoding ensure that Subscribers without ... special cases are defined in 7.2.5.4.3 . VerboseEncoding is the recommended default encoding for DataSetMessages. This specification defines a DataSet field encoding for the VerboseEncoding which simplifies the encoding of Variants
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.1 General

messages. The main purpose is the exchange of additional information not contained in the DataSetMessages like Properties for the DataSet fields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.2 DataSetMetaData

DataSetMetaData DataSetMetaData describe the content of DataSetMessages published by a DataSetWriter . More specifically, it specifies the names and data types of the values that shall appear in the Payload
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.2 ActionRequest

Variant encoding shall be used. The encoding rules defined in 7.2.5.4 for DataSetMessages also apply to the ActionRequest message. The DataValue encoding shall not be used in ActionRequest message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.3 ActionResponse

used. The value shall be present. The encoding rules defined in 7.2.5.4 for DataSetMessages also apply to the ActionResponse message. The DataValue encoding shall not be used in ActionResponse message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.2 MessageType mapping

applications acting as Publisher have RolePermissions . Such RolePermissions have no affect after DataSetMessages are sent to the MQTT broker. It is therefore recommended to synchronize Roles used to configure read
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.8 Message header

Table 204 . Table 208 defines an option to change the RETAIN flag setting for DataSetMessages . A Publisher shall send all RETAIN discovery messages at start up of the Publisher ... MQTT data types Description RETAIN Boolean RETAIN bit in the header RETAIN configuration for DataSetMessages. Message Expiry Interval UInt32 Four Byte Integer Not available as message property for MQTT
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

represents the information to publish and the DataSetWriter represents the transport settings for creating DataSetMessages for delivery through a Message Oriented Middleware . On the Subscriber side, a DataSetReader represents ... transport settings for receiving DataSetMessages from a Message Oriented Middleware and the SubscribedDataSet represents the information to dispatch the received DataSets in the Subscriber . The configuration can be done through
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.1 Overview

DataSet . See 5.2 for the introduction to DataSets , 5.3 for the introduction to DataSetMessages and 5.4.1.2 for an introduction to the different source options and the parameters for sending ... DataSetMessages . Figure 46 depicts the ObjectTypes of the published DataSet model and their components. Figure 46 - Published DataSet overview Instances of the DataSetFolderType are used to organize PublishedDataSetType Objects
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.1 PublishedDataSetType

PublishedDataSets . It defines the metadata and the configuration version of the DataSets sent as DataSetMessages through DataSetWriters . The PublishedDataSetType is the base type for configurable DataSets . Derived types like PublishedDataItemsType ... visible in the AddressSpace . The Object has a list of DataSetWriters . A DataSetWriter sends DataSetMessages created from DataSets through a Message Oriented Middleware . The link between the PublishedDataSet Object
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.3.1 PublishedDataItemsType

handle to reference the entry in configuration actions like RemoveVariables or the Value in DataSetMessages received by Subscribers . The index may change after configuration changes. Changes are indicated
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.3.2 AddVariables Method

assigned to the selected Variables for the fields in the DataSetMetaData and in the DataSetMessages for tagged message encoding. The size and the order of the array shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.4.1 PublishedEventsType

role for Subscribers. It is used as handle to reference the Event field in DataSetMessages received by Subscribers . The index may change after configuration changes. Changes are indicated
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.4.2 ModifyFieldSelection Method

FieldNameAliases The names assigned to the selected fields in the DataSetMetaData and in the DataSetMessages for tagged message encoding. The size and the order of the array shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.2 AddPublishedDataItems Method

assigned to the selected Variables for the fields in the DataSetMetaData and in the DataSetMessages for tagged message encoding. The size and the order of the array shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.3 AddPublishedEvents Method

FieldNameAliases The names assigned to the selected fields in the DataSetMetaData and in the DataSetMessages for tagged message encoding. The size and the order of the array shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.7.2 DataSetWriterType

DataSetWriter . The DataSetWriterType is formally defined Table 288 . A DataSetWriter that creates DataSetMessages based on a PublishedDataSet shall reference the related PublishedDataSet with an inverse DataSetToWriter Reference . A DataSetWriter that ... creates heartbeat DataSetMessages shall not have a reference to a PublishedDataSet . Table 288 - DataSetWriterType definition Attribute Value BrowseName DataSetWriterType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.7.3 DataSetWriterTransportType

ObjectType is the abstract base type for Objects defining protocol-specific transport settings of DataSetMessages . The DataSetWriterTransportType is formally defined Table 289 . Table 289 - DataSetWriterTransportType definition Attribute Value BrowseName DataSetWriterTransportType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.8.2 DataSetReaderType

DataSetReaderType This ObjectType defines receiving behaviour of DataSetMessages and the decoding to DataSets . The DataSetReaderType is formally defined in Table 291 . The SubscribedDataSetType defined in 9.1.9.1 describes the processing ... available subtypes are defined in 9.1.9 . If the DataSetReader is configured to receive heartbeat DataSetMessages , the Object shall be of the base type SubscribedDataSetType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.1 SubscribedDataSetType

defines the metadata for the subscribed DataSet and the information for the processing of DataSetMessages . See 5.4.2.2 for an introduction to the processing options for received DataSetMessages . The SubscribedDataSetType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.2.1 TargetVariablesType

defines the metadata for the subscribed DataSet and the information for the processing of DataSetMessages . The TargetVariablesType is formally defined in Table 297 . Table 297 - TargetVariablesType definition Attribute Value BrowseName
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.3 SubscribedDataSetMirrorType

SubscribedDataSetMirrorType This ObjectType defines the information for the processing of DataSetMessages as mirror Variables. For each field of the DataSet a mirror Variable is created in the Subscriber AddressSpace
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.5 StandaloneSubscribedDataSetType

configured and connected to the standalone DataSet if a Publisher provides the DataSetMessages defined by the DataSetMetaData in the standalone DataSet . The StandaloneSubscribedDataSetType is formally defined in Table 306 . Table ... Subscriber . The DataSetMetaData is defined in 6.2.9.4 . A Publisher must be configured to send DataSetMessages that comply with the DataSetMetaData in the standalone subscribed DataSet . The IsConnected Property with DataType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.11.11 PubSubDiagnosticsDataSetWriterType

Level Class Description Inherited counters from PubSubDiagnosticsType FailedDataSetMessages Mandatory Basic Error Number of failed DataSetMessages The Object LiveValues contains all live values of the diagnostics Object . If not further specified
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.1 General

General The header content and message layouts for both NetworkMessages and DataSetMessages in different message mappings were designed to be flexible and to support different use cases by enabling ... disabling individual fields within the headers. The header layouts only apply to NetworkMessages with DataSetMessages . While this flexibility makes it possible to support many different use cases with PubSub
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.1 Motivation

calculated based on the configuration. Certain encodings may result in varying size of DataSetMessages , which requires extra fields in the messages to allow the Subscriber to parse these messages. These ... extra fields can be omitted when the size of the DataSetMessages is constant. The header layout described in this section is optimized for this use case
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.2 Overview

messages is static. This implies the following: Each NetworkMessage contains the same number of DataSetMessages The sequence of the DataSetMessages within a NetworkMessage is the same in every PublishingInterval ... NetworkMessage , and the GroupVersion allows the Subscriber to verify the expected layout of the DataSetMessages and their DataSet fields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

A.2.1.7 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetMessageSequenceNumber Status Additional restrictions: Fields within the payload ... RawData Field Encoding Only data key frame DataSetMessages are supported The DataSetMessage header layout is shown in Figure A.4 . Figure A.4 - UADP DataSetMessage header layout Table A.5 shows the configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.8 Example fixed message layout without security

constant and can be pre-calculated. The Payload Header ( Count and Sizes for the DataSetMessages and DataSetWriterIds ) is deactivated and the Subscriber has to retrieve this information through the DataSetMetaData ... DataSet fields are from constant size, so the total length of theses DataSetMessages can be calculated from the DataSetMetaData . For DataSetMessage[0] in this example the Subscriber does not have
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.1 Motivation

A.2.2.1 Motivation In PubSub use cases with dynamically changing message layouts or Event based DataSetMessages, the number and ordering of DataSetMessages within different NetworkMessages can change arbitrarily. The header layouts ... section are intended for use cases with dynamic DataSets and ad-hoc identification of DataSetMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.2 Overview

described in this section, the NetworkMessage header only identifies the Publisher and the contained DataSetMessages . In contrast to the fixed layout, more header fields are enabled in the DataSetMessage header
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

A.2.2.7 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 DataSetMessageSequenceNumber Timestamp Status MinorVersion Additional remarks: Fields ... encoding All types of DataSetMessages (Data Key Frame, Data Delta Frame, Event, etc.) are supported The DataSetMessage header layout is shown in Figure A.10 Figure A.10 - UADP DataSetMessage header layout
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.8 Example dynamic message layout with different DataSetMessage types

DataSetMessage header is fixed. The number, the type, the length, and the order of DataSetMessages can vary from one NetworkMessage to the next. Figure A.11 - Example for dynamic message layout
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.4.2 Overview

Overview A minimal message has the following settings: Each NetworkMessage contains an array of DataSetMessages The NetworkMessage header is included, the header fields can be configured The DataSetMessage header
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

D.3.4 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 Additional remarks: Field is encoded as a Variant ... following types of DataSetMessages (Data Key Frame, Data Delta Frame, Keep Alive, etc.) are supported The DataSetMessage header layout is shown in Figure D.4 . Figure D.4 - UADP DataSetMessage header layout
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.4.2 Operation

that utilise the PubSub communication model and hence builds on the usage of either DataSetMessages or heartbeat messages
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.3 Multiple Connections using unicast network messages

unicast NetworkMessages . This use case is called aggregated because a single NetworkMessage aggregates multiple DataSetMessages (one per logical connection). Aggregation reduces the required network bandwidth
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.2 PubSubCommunicationFlowConfigurationType definition

optional HeaderLayoutUri specifies the UADP header formats for both NetworkMessages and DataSetMessages . If HeaderLayoutUri is omitted, a fixed layout for periodic data shall be used ( http://opcfoundation.org/UA/PubSub-Layouts/UADP-Periodic-Fixed
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.3 SubscriberConfigurationType definition

here and in the parent Object . The MessageReceiveTimeout specifies the maximum acceptable time between DataSetMessages . Received by the Subscriber . For the definition of MessageReceiveTimeout , see OPC 10000-14 . The optional
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

tools and/or ConnectionManager can make various selections. This can include optimisations which group multiple DataSetMessages into a single Network Message (see Figure E.16 ). Figure E.16 - UADP network message overview Many ... frame DataSetMessage The DataSetMessage can also be an Event . Events are much like fixed DataSetMessages , except that they are always a structure that is encoded as a Variant (see Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.3 ConnectionConfigurationSet and ReaderGroup

ReaderGroup As defined in OPC 10000-14 , DataSetReaders in a ReaderGroup can extract their DataSetMessages from different NetworkMessages . However, it is recommended that the PubSubConfiguration generated for an AutomationComponent contains
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.7 PubSubCommunicationFlowConfigurationConfDataType

HeaderLayoutUri 0:String Optional HeaderLayoutUri specifies the UADP header formats for both NetworkMessages and DataSetMessages . If HeaderLayoutUri is omitted, a fixed layout for periodic data shall be used. True HeaderLayoutUriSelection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.8 SubscriberConfigurationConfDataType

information flow. True MessageReceiveTimeout 0:Duration MessageReceiveTimeout specifies the maximum acceptable time between DataSetMessages received by the Subscriber . False MessageReceiveTimeoutSelection 0:Duration[] Selection list options for MessageReceiveTimeout. True MessageReceiveTimeoutModify