View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000865110000-014: PubSubSpecpublic2023-01-25 10:442023-06-20 14:44
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.03 RC1 
Summary0008651: Conflicting requirements for heartbeat message header
Description

6.2.4.2 DataSetFieldContentMask
This DataType defines flags to include DataSet field related information like status and timestamp in addition to the value in the DataSetMessage. The parameter is ignored for heartbeat messages.

Table A.5 – UADP DataSetMessage header layout
Bit range 1-2: Field Encoding
01 RawData Field Encoding

Based on the first statement, bits 1-2 must be 00.
The second statement requires 01. Is this true for heartbeat messages as well?

This came up at the last OPC UA FX plugfest

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008729 closedMatthias Damm How can UADP heartbeat messages be recognized? 

Activities

Matthias Damm

2023-06-20 13:10

developer   ~0019558

6.2.4 DataSetWriter parameters
6.2.4.2 DataSetFieldContentMask
Replced
The parameter is ignored for heartbeat messages.
with
The parameter is not relevant for heartbeat messages but should be configured according to the header layout requirements.

6.2.9 DataSetReader parameters
6.2.9.5 DataSetFieldContentMask
Added
The parameter is ignored for heartbeat messages.

Jim Luth

2023-06-20 14:44

administrator   ~0019561

Agreed to changes edited in Virtual F2F.

Issue History

Date Modified Username Field Change
2023-01-25 10:44 Matthias Damm New Issue
2023-03-14 15:14 Jim Luth Assigned To => Matthias Damm
2023-03-14 15:14 Jim Luth Status new => assigned
2023-03-14 16:16 Zbynek Zahradnik Relationship added related to 0008729
2023-06-20 13:10 Matthias Damm Status assigned => resolved
2023-06-20 13:10 Matthias Damm Resolution open => fixed
2023-06-20 13:10 Matthias Damm Fixed in Version => 1.05.03 RC1
2023-06-20 13:10 Matthias Damm Note Added: 0019558
2023-06-20 14:44 Jim Luth Status resolved => closed
2023-06-20 14:44 Jim Luth Note Added: 0019561