View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000787610000-007: ProfilesSpecpublic2022-03-18 16:502023-03-23 14:30
ReporterAlexander Allmendinger Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.04 
Target Version1.05.02 
Summary0007876: Introduce CU for supported of PublisherId Types
Description

Part 14 currently defines two possibilities for PublisherId Type (UInt16 or UInt64). But we don't have CUs defining what is required for a full featured profile. UAFX for example requires the support of the UInt64 PublisherId Type for the auto generated IDs which could currently not be defined in a profile.

Proposal is to generate two CUs:

  • Supports PublisherId Type UInt16
  • Supports PublisherId Type UInt64
TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Karl Deiretsbacher

2022-06-23 07:14

developer   ~0017011

Needs discussion. Part 14 (6.2.7.1 - PublisherId) has the following statements:
Valid DataTypes are UInteger and String. A zero UInteger and a Null or empty String are invalid PublisherIds.
The unique identifier for an OPC UA Application is the ApplicationUri. It is recommended to use the ApplicationUri String as a default PublisherId for broker based transport protocols.
The default PublisherId for datagram transport protocols has a DataType of UInt64. If the default PublisherId is created by the OPC UA Application, it is recommended to set the first 6 bytes with the MAC address of one of the network interfaces and to set the two remaining bytes to the OPC UA Server port of the OPC UA Application.

The UADP NetworkMessage allows the following datatypes:
Bit range 0-2: PublisherId Type
000 The PublisherId is of DataType Byte
This is the default value if ExtendedFlags1 is omitted
001 The PublisherId is of DataType UInt16
010 The PublisherId is of DataType UInt32
011 The PublisherId is of DataType UInt64
100 The PublisherId is of DataType String

Jim Luth

2022-07-12 16:01

administrator   ~0017114

We think the fixed profile needs these proposed CUs because it offers either UINT16 or UINT64. We think subscribers that support the flexible Profile need to accept all possible datatypes for PublisherId (hence no additional CUs needed).

Karl Deiretsbacher

2022-09-15 08:22

developer   ~0017662

Created CUs and added (as draft) to the "Periodic Fixed Layout Facet" --> https://profiles.opcfoundation.org/profile/731.

Karl Deiretsbacher

2022-09-27 15:16

developer   ~0017851

Also add this to 1.04.

Karl Deiretsbacher

2023-03-22 08:00

developer   ~0018956

The issue was fixed in the profile database for v1.04 and v1.05.

In the Publisher UADP Periodic Fixed Layout Facet:

  • Added "PubSub Publisher UADP Periodic Fixed Settings2" as mandatory CU with text "Support of at least one of the optional Conformance Units for PublisherId types is required"
  • Added "PubSub Publisher UADP PublisherId UInt16" and "PubSub Publisher UADP PublisherId UInt16" which represents the different datatypes for PublisherId

In the Subscriber UADP Periodic Fixed Layout Facet:

  • Added "PubSub Subscriber UADP Periodic Fixed Settings2" as mandatory CU with text "All PublisherId types defined for periodic data with fixed layout shall be supported"

Jim Luth

2023-03-23 14:30

administrator   ~0018999

Agreed to changes in Dallas Meeting.

Issue History

Date Modified Username Field Change
2022-03-18 16:50 Alexander Allmendinger New Issue
2022-06-23 07:14 Karl Deiretsbacher Note Added: 0017011
2022-07-12 16:01 Jim Luth Note Added: 0017114
2022-07-12 16:02 Jim Luth Product Version => 1.04
2022-07-12 16:02 Jim Luth Target Version => 1.05.02
2022-07-12 16:02 Jim Luth Assigned To => Matthias Damm
2022-07-12 16:02 Jim Luth Status new => assigned
2022-09-15 08:22 Karl Deiretsbacher Note Added: 0017662
2022-09-27 15:16 Karl Deiretsbacher Note Added: 0017851
2023-03-22 08:00 Karl Deiretsbacher Status assigned => resolved
2023-03-22 08:00 Karl Deiretsbacher Resolution open => fixed
2023-03-22 08:00 Karl Deiretsbacher Note Added: 0018956
2023-03-23 14:30 Jim Luth Note Added: 0018999
2023-03-23 14:30 Jim Luth Status resolved => closed