View Issue Details

IDProjectCategoryView StatusLast Update
0008212Part 81: UAFX Connecting Devices and Information ModelSpecpublic2022-09-13 21:37
ReporterBrian Batke Assigned ToGeorg Biehler  
PriorityhighSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.00.00 RC3 
Target Version1.00.00 ReleaseFixed in Version1.00.00 Release 
Summary0008212: Missing mechanism to indicate which connection types (uni, uni+HB, bi-dir) are supported
Description

Part 81 (as well as the OED) has no way for an implementation to indicate which connection types it supports: unidirectional (autonomous), unidirectional with heartbeat, bidirectional. And engineering tool would need this info also when setting up the connection manager

TagsNo tags attached.

Relationships

related to 0008213 closedGreg Majcher Part 84: UAFX Profiles Missing CUs for different connection types 
related to 0008322 closedGeorg Biehler Part 84: UAFX Profiles Missing mechanism to indicate which connection types (uni, uni+HB, bi-dir) are supported 
related to 0008323 closedPaul Hunkar UAFX Nodeset Missing mechanism to indicate which connection types (uni, uni+HB, bi-dir) are supported 

Activities

Georg Biehler

2022-08-22 10:08

developer   ~0017347

Added five capabilities to clause 6.2.6
Added check for the capabilities to clause 6.2.4.3.5, and error cause to Table 12

Paul Hunkar

2022-08-23 13:24

manager   ~0017353

needs more discussion

Paul Hunkar

2022-09-09 13:17

manager   ~0017584

Last edited: 2022-09-13 21:29

Decision in team meeting on 2022-08-30: FE will support the connection types autonomous publisher and unidirectional as publisher only, if the new capability FeedbackSignalRequired is set to FALSE or not present. Further more, the FE will include an optional folder that include only capabilities (named Capabilities). this folder in the future can contain other capabilities. IF it s omitted no capabilities are being provided or required. (Note: edited in 2022-09-13 meeting to reflect correct actual names - no changes in general decision)

Paul Hunkar

2022-09-13 14:58

manager   ~0017645

reviewed in call, agreed to changes and closed issue

Issue History

Date Modified Username Field Change
2022-08-19 13:34 Brian Batke New Issue
2022-08-19 13:51 Greg Majcher Relationship added related to 0008213
2022-08-19 14:02 Paul Hunkar Assigned To => Georg Biehler
2022-08-19 14:02 Paul Hunkar Status new => assigned
2022-08-22 10:08 Georg Biehler Status assigned => resolved
2022-08-22 10:08 Georg Biehler Resolution open => fixed
2022-08-22 10:08 Georg Biehler Fixed in Version => 1.00.00 Release
2022-08-22 10:08 Georg Biehler Note Added: 0017347
2022-08-23 13:24 Paul Hunkar Status resolved => feedback
2022-08-23 13:24 Paul Hunkar Resolution fixed => reopened
2022-08-23 13:24 Paul Hunkar Note Added: 0017353
2022-08-23 13:25 Paul Hunkar Status feedback => assigned
2022-08-30 15:34 Georg Biehler Status assigned => resolved
2022-09-09 13:17 Paul Hunkar Note Added: 0017584
2022-09-13 14:56 Paul Hunkar Issue cloned: 0008322
2022-09-13 14:57 Paul Hunkar Issue cloned: 0008323
2022-09-13 14:58 Paul Hunkar Status resolved => closed
2022-09-13 14:58 Paul Hunkar Note Added: 0017645
2022-09-13 20:19 Greg Majcher Relationship added related to 0008322
2022-09-13 21:23 Paul Hunkar Resolution reopened => fixed
2022-09-13 21:23 Paul Hunkar Product Version => 1.00.00 RC3
2022-09-13 21:23 Paul Hunkar Target Version => 1.00.00 Release
2022-09-13 21:29 Paul Hunkar Note Edited: 0017584
2022-09-13 21:37 Paul Hunkar Relationship added related to 0008323