View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000853710000-014: PubSubSpecpublic2022-12-21 15:342023-03-22 22:06
ReporterKai Schnellecke Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 RC1 
Fixed in Version1.05.03 RC1 
Summary0008537: Clarification for item SubstituteValue in PublishedVariableDataType when PublishedVariable is an array
Description

Request for clarification:

PublishedVariableDataType contains the Item "SubstituteValue" with DataType "BaseDataType".

Part 14 states (https://reference.opcfoundation.org/v105/Core/docs/Part14/6.2.3/#6.2.3.7.1):
This Value shall match the DataType of the PublishedVariable since DataSetWriters may depend on a valid Value with the right DataType that matches the ConfigurationVersion.

By "this Value" I would assume, that this specifically refers to the value of the substitute value within the publishedvariable structure.

Now, the encoding of the value for "SubstituteValue" of the PublishedVariableDataType works well, if the PublishedVariable is scalar.
But how should this be handled, if the publishedVariable is an array?

As "SubstituteValue" has ValueRank = -1 (Scalar) -> is it possible to provide a substitute value as array?

Steps To Reproduce

-Create an instance of "publishedVariableDataType"

  • provide a value for "substituteValue" that should be of a concrete array datatype (e.g. boolean array).
TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2023-03-18 23:53

developer   ~0018878

The BaseDataType can take any ValueRank.

Added clarification that also ValueRank must match the PublishedVariable

Jim Luth

2023-03-22 22:06

administrator   ~0018983

Agreed to changes in Dallas meeting.

Issue History

Date Modified Username Field Change
2022-12-21 15:34 Kai Schnellecke New Issue
2023-03-18 23:53 Matthias Damm Assigned To => Matthias Damm
2023-03-18 23:53 Matthias Damm Status new => resolved
2023-03-18 23:53 Matthias Damm Resolution open => fixed
2023-03-18 23:53 Matthias Damm Fixed in Version => 1.05.03 RC1
2023-03-18 23:53 Matthias Damm Note Added: 0018878
2023-03-22 22:06 Jim Luth Status resolved => closed
2023-03-22 22:06 Jim Luth Note Added: 0018983