Search

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

47 result(s) for DataSets

OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.2 DataSetClass

content of a DataSet Note 1 to entry: A DataSetClass is used to type DataSets for use in several Publishers and for filtering in Subscribers
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

3.1.10 SubscribedDataSet

SubscribedDataSet configuration for dispatching of received DataSets Note 1 to entry: A SubscribedDataSet can be a mapping of DataSet fields to Variables in the Subscriber AddressSpace
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.1 General

each other. Their primary relation is the shared understanding of specific types of data ( DataSets ), the publish characteristics of messages that include these data, and the Message Oriented Middleware ... 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 in the Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.1 General

combined to form the payload of a NetworkMessage . Figure 3 illustrates the use of DataSets for publishing. Figure 3 - DataSet in the process of publishing A PublishedDataSet is similar ... Most of these settings depend on the selected Message Oriented Middleware . The configuration of DataSets and the way the data is obtained for publishing can be configured using the PubSub
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.2 DataSetClass

DataSetClass DataSets can be individual for a Publisher or they can be derived from a DataSetClass . Such a DataSetClass acts as template declaring the content of a DataSet . The DataSetClass ... corresponding field of the DataSetMetaData . When all DataSetMessages of a NetworkMessage are created from DataSets that are instances of the same DataSetClass, the DataSetClassId of this class can be provided
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.3 DataSetMessage

still alive. DataSetMessages are either sent cyclicly or acyclicly in a publishing interval. Acyclic DataSets are sent as event DataSetMessages . Cyclic DataSets can create at most one DataSetMessages per interval ... Acyclic DataSets can create multiple event DataSetMessages per interval. For cyclic DataSets , some encodings differentiate between key frame DataSetMessages and delta frame DataSetMessages. A key frame DataSetMessage includes values
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.2.2 Broker-less model with OPC UA UDP

connection can have one or more groups with DataSetWriters . A group can publish DataSets at the defined publishing interval. In each publishing interval, a DataSet is collected for a PublishedDataSet
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.1 Overview

each other. The WriterGroup , DataSetWriter and PublishedDataSet components define the data acquisition for the DataSets , the message generation and the sending on the Publisher side. These parameters need ... shows the following components: PublishedDataSet contains the DataSetMetaData describing the content of the DataSets produced by the PublishedDataSet and the corresponding data acquisition parameters. DataSetWriter parameters are necessary for creating
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.1 Overview

configuration of the information source for a 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 ... configuration of the Publisher . The standard configuration options are published data items for cyclic DataSets as defined in 6.2.3.7 and published events for acyclic DataSets as defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.3 DataSetMetaDataType

case, this field shall match the DataSetClassId of the concrete DataSet configuration. If the DataSets are not created from a class, this field is null. ConfigurationVersion Configuration‌VersionDataType The configuration version
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.3 DataSetClassId

defined by a standards organization or by a plant operator as a DataSetClass . DataSets that conform to such a DataSetClass are identified with a DataSetClassId . The DataSetClassId is the globally
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.5 PublishedDataSetDataType

DataSetSource PublishedDataSetSourceDataType Defined in 6.2.3.6 . If the parameter is null, the source creates cyclic DataSets . This is equal to a PublishedDataSetCustomSourceDataType with cyclicDataSet set to true. True Its representation
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.8.3 Filter

Filter defines the filter applied to the Events . It allows the reduction of the DataSets generated from Events through a filter. The ContentFilter DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.3 KeyFrameCount

true provide cyclic updates. For non-cyclic PublishedDataSets that provide acyclic event based DataSets , the value shall be 0. PublishedEvents or custom sources with CyclicDataSet set to false provide acyclic
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.2 PublishingInterval

DataSetMessage is sent. In the case non-cyclic PublishedDataSets like Event based DataSets , this may result in zero to many DataSetMessages produced for one PublishedDataSet in a PublishingInterval . All Events
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.7 KeyFrameCount

PublishingInterval expires before a key frame message, with all field values, is received. For DataSets that provide cyclic updates, the value shall be greater than or equal ... cyclic DataSets, like PublishedEvents, that provide event based DataSets , the value shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.3 DataSetOrdering

only one DataSetMessage is sent per NetworkMessage . If DataSetOrdering is Undefined any ordering between DataSets and their distribution into NetworkMessages is allowed. Ordering and distribution even may change between each ... DataSetOrdering is set to AscendingWriterId, the Publisher shall fill up each NetworkMessage with DataSets with an ascending order of the related DataSetWriterIds as long as the accumulated DataSet sizes will
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.6 PublishingOffset

affect sending of multiple NetworkMessages . Figure 31 - PublishingOffset options for multiple NetworkMessages If all DataSets of a group are transferred with a single NetworkMessage , the scalar value or the first ... sending the NetworkMessage relative to the start of the PublishingInterval cycle. If the DataSets of a group are sent in a series of NetworkMessages , the values in the array define
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.1 General

DataSetWriters in a WriterGroup can result in a fixed NetworkMessage layout where all DataSets have a static position between NetworkMessages . In this case the parameters NetworkMessageNumber and DataSetOffset provide information
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

Responder is used for request and response. DataSetClassId Guid The DataSetClassId associated with the DataSets in the NetworkMessage. All DataSetMessages in the NetworkMessage shall have the same DataSetClassId. The DataSetClassId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

depends on the setting in the JsonNetworkMessageContentMask . DataSetClassId String The DataSetClassId associated with the DataSets in the NetworkMessage . The DataSetClassId is a Guid and shall be converted to a String
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

Message Oriented Middleware and the SubscribedDataSet represents the information to dispatch the received DataSets in the Subscriber . The configuration can be done through Methods or product-specific configuration tools ... specific settings can be configured. If a Publisher allows dynamic creation of Objects like DataSets and DataSetWriters , this can be done through product-specific configuration tools or through the standardized
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.2 Configuration behaviours

defined in 6.2.2 . Add, modify and remove operations for all PubSub configuration elements including DataSets and security key exchange configuration can be executed in one atomic write operation through
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.1 Overview

configuration of the information source for a 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
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.1 PublishedDataSetType

base type for 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 ... published. For PublishedDataItemsType this is a list of monitored Variables used to create cyclic DataSets . For PublishedEventsType this is an Event selection used to create acyclic DataSets . The list
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.3.1 PublishedDataItemsType

select a list of OPC UA Variables as the source for the creation of DataSets sent through one or more DataSetWriters . The PublishedDataItemsType is formally defined Table 253 . Table
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.3 AddPublishedEvents Method

Filter The filter applied to the Events . It allows the reduction of the DataSets generated from Events through a filter like filtering for a certain EventType . The ContentFilter DataType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.5 AddPublishedEventsTemplate Method

Filter The filter applied to the Events . It allows the reduction of the DataSets generated from Events through a filter like filtering for a certain EventType . The ContentFilter DataType
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
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.1 Motivation

header layouts described in this section are intended for use cases with dynamic DataSets and ad-hoc identification of DataSetMessages
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.2 Header layout for NetworkMessages

PubSubConnection. The datatype shall be UInt64. DataSetClassId Guid The DataSetClassId associated with the DataSets in the NetworkMessage. All DataSetMessages in the NetworkMessage shall have the same DataSetClassId. - It shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.5 DataSetMetaData

lifetime of a Connection, another engineering tool can update a FunctionalEntity, including its preconfigured DataSets . In addition, the Descriptor can describe a different version of the FunctionalEntity to be connected
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.12.2 ConnectionEndpointParameterType definition

specifies the name of a preconfigured PublishedDataSet (see 6.2.7 for more information on preconfigured DataSets ) to be used for connecting the OutputVariables . The ConnectionManager can obtain any required information related ... specifies the name of a preconfigured StandaloneSubscribedDataSet (see 6.2.8 for more information on preconfigured DataSets ) to be used for connecting the InputVariables . The ConnectionManager can obtain any required information related
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.1 Overview

ControlGroups and the resulting Connections . It will also describe the use of pre-configured DataSets and dynamically created DataSets . In later clauses, these examples are linked to the Asset examples
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.1 Overview

FunctionalEntity Type The following examples illustrate how InputData and OutputData can be joined with DataSets . Consider, for example, an analogue input module with four channels plugged into
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.4 Using customised DataSets

D.3.6.4 Using customised DataSets A third variant assumes that the module supports data exchange with customised DataSets only. In this case, a possible Information Model looks like the one illustrated ... Figure D.25 . However, the absence of PreconfiguredPublishedDataSets indicates that only customised DataSets are supported. Figure D.25 - Sample for analogue input module - customised DataSets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.5 Using groups

Again, as stated in the variants before, the module can choose to support preconfigured DataSets (e.g., one for all Int16 channels and one for all Float channels) and/or allow customised ... DataSets , depending on the setting of PreconfiguredDataSetOnly. A Connection can, for example, select Channel1 and Channel6. Figure D.27 illustrates this sample. Figure D.27 - ConnectionEndpoint using grouped data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.5 Using ControlGroups to expose functionality.

other controller. This requires bidirectional communication. In this example, Controller B comes with preconfigured DataSets , one for the Publisher and one for the Subscriber . Figure D.31 - ControlGroup cascade Controller example ... ConnectionManager in Controller A, which would see the ControlGroup and would utilise the preconfigured Datasets that are described in the ControlGroup
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

E.4.7 PubSub DataSets This subclause provides an overview of PubSub communication options and the use of DataSets . For a complete description of PubSub communication, PubSub communication options, DataSets and DataSetMetaData ... array provides the order in which they will be in the DataSet . These DataSets could be preconfigured or could be created at run time. Figure E.21 illustrates what is defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

datatype of PubSubConfiguration2DataType . The PubSubConfiguration2DataType is a complex structure that can include DataSets (published or subscribed) that would include fields that are of NodeId DataType . NodeIds contain a NamespaceIndex ... complex data structure. When an engineering tool generates a ConnectionConfigurationSet , if it includes DataSets, then it will need to ensure that any NodeId it generates for its ConnectionManager's Server
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.2 Descriptor with product information

information of the AutomationComponent product contains the Asset and functional structure, (pre-configured) DataSets , capabilities, and the property name defined in OPC 10000-81 . In the Information Model , there
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.3 Descriptor with configuration information

AutomationComponent : Controller configurations typically contain the FunctionalEntities together with input and output Variables , DataSets , and the publisher and subscriber capabilities. For IO and field devices, the configuration typically contains ... values for the parameters for the built-in FunctionalEntities , the built-in DataSets , and the publisher and subscriber capabilities. For modular devices, the configuration may also include the definitions
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.4 Creation of the FunctionalEntity structure

Table F.1 shows the values of the Variables used in the example: NOTE The DataSets referenced in the table are defined in F.1.5 . Table F.1 - SubscriberCapabilities Variables and values
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.5 Creation of the Data Sets

F.1.5 Creation of the Data Sets Since the example is using pre-configured DataSets , the DataSets for the communication of the "FillLevel" and "ValveOpenClose" signals ... defined in the next step. This is shown in Figure F.11 : Figure F.11 - DataSets for the FillControl FunctionalEntity Two DataSets are defined: A publication dataset, "ValveOpenCloseDataSet
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.6 Usage of the Descriptor in subsequent engineering

phase, as shown in Figure F.13 , a System Integrator defines the ITagNameplate information, custom DataSets (if allowed), the connections between machines in the production, the communications intervals and Quality ... Descriptor in subsequent engineering As the final step, the connection information, including custom DataSets , the communication intervals and QoS, is deployed to the ConnectionManager(s), which is responsible for establishing
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.6 UAFX ConnectionManager

SetCommunicationConfigurationCmd command of the EstablishConnections Method. This includes support of preconfigured and dynamic DataSets . Client UAFX Client ConnectionManager EnableCommunication Is capable of issuing the EnableCommunicationCmd command of the EstablishConnections Method