0005036: How do configuration changes or disable affect fixed layout messages - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0005036	10000-014: PubSub	Spec	public	2019-09-12 10:52	2021-03-30 16:12

Reporter	Matthias Damm	Assigned To	Matthias Damm
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed

Summary	0005036: How do configuration changes or disable affect fixed layout messages
Description	What happens if a DataSetWriter is deactivated? This would change all offsets of the following data sets. The configuration of DataSetOrdering only says "AscendingWriterId" but it does not define who decides on the offset in the case of (temporary) removal of a DataSetWriter. Expected behavior based on current definition: Deactivate removes the DataSet and therefore the offset changes since it is not longer contained in the group. At least for automatic configuration of offsets. Question: Should we allow a temporary deactivation and keep the layout the same but set the valid flag to false. This would help for "temporary" deactivation. If yes, how is this configured
Tags	No tags attached.

Commit Version
Fix Due Date

Thomas Enzinger 2020-12-10 14:37 reporter ~0013443	Activation/Deactivation should not affect the layout of fixed layout messages. Exactly for this the valid flag can be used to signal to the subscriber that at certain DataSetMessage is not valid. Why doe we need to configure something?

Matthias Damm 2020-12-10 15:14 developer ~0013448	Clarifications for fixed layout (group header + offsets configured): Disabled state should be handled the same way for initial disabled or for disabling later. The behaviour depends on the offset configuration. The change of the enabled state does NOT force a re-calculation of the offset. If the offset is not configured, the DataSet is not in the NetworkMessage. If a offset is configured but the DataSetWriter is disabled, the valid flag is set to false and the rest of the message window is set to 0. In the case of removal, it is up to the module that sets the configuration if the message is removed from the layout.

Matthias Damm 2021-03-03 16:45 developer ~0013936	6.3.1.3.5 DataSetOffset Added: If a DataSetWriter is disabled, the DataSetOffsets for the DataSetWriters in the WriterGroup can stay unchanged, especially if the disable is temporary. If the DataSetWriter is disabled and the DataSetOffset is configured, the valid flag of the DataSetFlags1 in the DataSetMessage header shall be false. Table 103 – DataSetMessage header structure DataSetFlags1 Bit 0 Added: All bytes of the content of the DataSetMessage shall be 0 if the status of the DataSetWriter is not Operational but the DataSetMessage is included due to a fixed layout. If the flag is set to false during operation, the content of the DataSetMessage is undefined. Added in OPC 10000-14 - UA Specification Part 14 - PubSub 1.05.0 Draft31.docx

Jim Luth 2021-03-30 16:12 administrator ~0014135	Agreed to text edited in telecon.

Date Modified	Username	Field	Change
2019-09-12 10:52	Matthias Damm	New Issue
2019-09-12 10:52	Matthias Damm	Status	new => assigned
2019-09-12 10:52	Matthias Damm	Assigned To	=> Matthias Damm
2020-12-10 14:37	Thomas Enzinger	Note Added: 0013443
2020-12-10 15:14	Matthias Damm	Note Added: 0013448
2021-03-03 16:45	Matthias Damm	Status	assigned => resolved
2021-03-03 16:45	Matthias Damm	Resolution	open => fixed
2021-03-03 16:45	Matthias Damm	Note Added: 0013936
2021-03-30 16:12	Jim Luth	Status	resolved => closed
2021-03-30 16:12	Jim Luth	Fixed in Version	=> 1.05
2021-03-30 16:12	Jim Luth	Note Added: 0014135