View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010161 | Part 81: UAFX Connecting Devices and Information Model [sg.BaseFacet] | Spec | public | 2025-02-21 22:45 | 2025-11-11 14:23 |
| Reporter | Suad Morgan | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | NextMaintenance | Fixed in Version | 1.00.04 | ||
| Summary | 0010161: Clarification on the CommuniationFlowQosDataType | ||||
| Description | Provide explanation in the document of why there are two places in the PubSubCommunicationFlowConfigurationType to define the Subscriber’s Qos. One in CommuniationFlowQosDataType and the second in the SubscriberConfiguration. So far, Prototyping has only needed to use the first one. It was suggested that the second one would be used for multicast communications. But clarification is needed. | ||||
| Tags | No tags attached. | ||||
| related to | 0010382 | assigned | Jan Murzyn | Clarify usage of QosDataType similar as Part 14 did. |
|
|
The first is defined in the PubSubCommunicationFlowConfigurationType QOS variable with the following definition - "The optional Qos specifies the Quality of Service to be used for the information flow. For the definition of CommunicationFlowQosDataType, see 10.12. Qos ReceiveQos may be overridden by a <SubscriberConfiguration>" The second location is in the SubscriberConfigurationType (type for <SubscriberConfiguration>) With the following definition - "The optional ReceiveQos specifies the Quality of Service to be used for the Subscriber of the information flow. It shall only be present if Qos is present in the parent Object. If present, ReceiveQos will override Qos ReceiveQos of the parent Object. For the definition of ReceiveQos, see OPC 10000-14." |
|
|
Added text explain that this setting is typically used when a publisher is multicast and an individual subscriber requires a different Qos setting |
|
|
reviewed change in call - agreed and closed issue |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-21 22:45 | Suad Morgan | New Issue | |
| 2025-02-28 13:41 | Paul Hunkar | Assigned To | => Paul Hunkar |
| 2025-02-28 13:41 | Paul Hunkar | Status | new => assigned |
| 2025-02-28 13:41 | Paul Hunkar | Target Version | => 1.00.03 |
| 2025-06-14 06:10 | Paul Hunkar | Note Added: 0023010 | |
| 2025-06-14 06:11 | Paul Hunkar | Note Edited: 0023010 | |
| 2025-07-18 13:02 | Paul Hunkar | Target Version | 1.00.03 => NextMaintenance |
| 2025-08-08 12:36 | Paul Hunkar | Relationship added | related to 0010382 |
| 2025-09-09 06:28 | Paul Hunkar | Status | assigned => resolved |
| 2025-09-09 06:28 | Paul Hunkar | Resolution | open => fixed |
| 2025-09-09 06:28 | Paul Hunkar | Note Added: 0023273 | |
| 2025-09-09 06:52 | Paul Hunkar | Fixed in Version | => 1.00.04 |
| 2025-11-11 14:23 | Paul Hunkar | Status | resolved => closed |
| 2025-11-11 14:23 | Paul Hunkar | Note Added: 0023521 |
