View Issue Details

IDProjectCategoryView StatusLast Update
000562110000-014: PubSubSpecpublic2020-06-17 15:14
ReporterWolfgang Mahnke Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0005621: Representation of Standardized DataSets in NodeSet-File
Description

Remark: I am not sure if this belongs into this part or some other (e.g. Part 5).

Topic comes from the Harmonization group, where CS like PA-DIM want to define standardized DataSets in future versions.
The desire is to put that information also in the NodeSet-File, and make it accessable for OPC UA clients (what standardized DataSets are known by the server).

Proposal (to be disucssed): Have a folder object referencing Objects with informtion of the standarized DataSets. That could be manged somewhere under the server capabilities.
To manage the information of the standardized DataSet, it looks to me like the PublishedDataSetType ObjectType would be a good candidate for that.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2020-05-12 16:07

developer   ~0012048

The PublishedDataSet is a concrete instance of a DataSet with the configuration of the data source.

A standardized DataSet is just a OPC UA Structure instance (value) that has no relation to any node in the address space as long it is not used in a PublishedDataSet.
But a standard cannot define a PublishedDataSet since a Publisher can have several instances of PublishedDataSets that publish all the same class of DataSet.

This is even worse than representing a standard Property in a NodeSet that has not parent type.

A standard DataSet has not even a Node, it is just a value.
The Nodeset would need a Variable as container for the value. The DataSetMetaData has a Name (can be used for BrowseName and DisplayName) and a DataSetClassId (GUID that can be used as NodeId).
To create a “Parent” for the Variable, we can introduce a Folder “DataSetClasses” below the PublishSubscribe Object in Part 14.

In this case the companion specs just need to define a Variable for each DataSetClass where the DataSetMetaData is the value of this variable and this variable has an inverse reference to the DataSetClasses Folder in the OPC UA namespace.

Matthias Damm

2020-06-09 20:49

developer   ~0012221

Added DataSetClasses to PublishSubscribeType definition.

The DataSetClasses Folder references a list of Variables where the Value of a Variable represents a DataSetClass. For each Variable, the Name field of the BrowseName equals the Name in the DataSetMetaData and the Identifier of the NodeId equals the DataSetClassId of the DataSetMetaData.

Added in OPC 10000-14 - UA Specification Part 14 - PubSub Draft 1.05.26.docx

Jim Luth

2020-06-17 15:14

administrator   ~0012400

Agreed to changes in virtual F2F.

Issue History

Date Modified Username Field Change
2020-05-06 12:30 Wolfgang Mahnke New Issue
2020-05-12 16:07 Matthias Damm Note Added: 0012048
2020-05-12 16:10 Jim Luth Assigned To => Matthias Damm
2020-05-12 16:10 Jim Luth Status new => assigned
2020-06-09 20:49 Matthias Damm Status assigned => resolved
2020-06-09 20:49 Matthias Damm Resolution open => fixed
2020-06-09 20:49 Matthias Damm Note Added: 0012221
2020-06-17 15:14 Jim Luth Status resolved => closed
2020-06-17 15:14 Jim Luth Fixed in Version => 1.05
2020-06-17 15:14 Jim Luth Note Added: 0012400