View Issue Details

IDProjectCategoryView StatusLast Update
0009166Part 84: UAFX ProfilesSpecpublic2024-11-13 14:44
ReporterThomas Assigned ToBob Lattimer  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version1.00.03Fixed in Version1.00.03 
Summary0009166: Do we need a Conformance Unit requiring a minimum number of UAFX Connections
Description

During the test cases review in the test development workshop in Austin was a discussion if a Conformance Unit has to be defined requiring a minimum number of connections. Currently is a CU defined which limits the maximum number of connections.

TagsNo tags attached.

Relationships

related to 0009361 closedPaul Hunkar Part 81: UAFX Connecting Devices and Information Model Do we need a Conformance Unit requiring a minimum number of UAFX Connections 

Activities

Bob Lattimer

2024-01-17 15:57

manager   ~0020649

The CU would indicate that a Controller can support at least this number of Connections no matter what. The existing CU MaxConnections only says the AC will refuse any additional Connections beyond the MaxConnections value. However, there is no guarantee that the MaxConnections can be supported depending on other constraints such as Connection speed or size.

Bob Lattimer

2024-01-17 15:58

manager   ~0020650

Updates are needed to Part 81 to describe this capability Variable. CUs will be added to Part 84 once that work is complete.

Bob Lattimer

2024-09-04 01:50

manager   ~0021650

Last edited: 2024-09-04 02:00

Added UAFX AutomationComponent MinConnections CU and added the new CU to the UAFX AutomationComponent Facet as Optional = False.

The Profiles database will be updated once the proposed resolution is approved.

Bob Lattimer

2024-09-04 13:54

manager   ~0021653

Reviewed and approved during the AWG meeting. The addition of the mandatory CU to the UAFX AutomationComponent Facet so a new 2024 Facet will be created as well.

Greg Majcher

2024-11-13 14:44

manager   ~0022050

Reviewed and approved in call.
It is ready to close when the database is updated.

Issue History

Date Modified Username Field Change
2023-09-22 10:02 Thomas New Issue
2024-01-17 15:57 Bob Lattimer Note Added: 0020649
2024-01-17 15:58 Bob Lattimer Assigned To => Bob Lattimer
2024-01-17 15:58 Bob Lattimer Status new => acknowledged
2024-01-17 15:58 Bob Lattimer Note Added: 0020650
2024-01-17 15:59 Bob Lattimer Issue cloned: 0009361
2024-01-17 15:59 Bob Lattimer Relationship added related to 0009361
2024-07-23 13:21 Paul Hunkar Status acknowledged => assigned
2024-08-21 13:37 Greg Majcher Target Version => 1.00.03
2024-09-04 01:50 Bob Lattimer Status assigned => resolved
2024-09-04 01:50 Bob Lattimer Resolution open => fixed
2024-09-04 01:50 Bob Lattimer Fixed in Version => 1.00.03
2024-09-04 01:50 Bob Lattimer Note Added: 0021650
2024-09-04 02:00 Bob Lattimer Note Edited: 0021650
2024-09-04 13:54 Bob Lattimer Note Added: 0021653
2024-11-13 14:44 Greg Majcher Note Added: 0022050