View Issue Details

IDProjectCategoryView StatusLast Update
0007717Part 81: UAFX Connecting Devices and Information Model [sg.BaseFacet]Specpublic2022-05-30 22:59
ReporterDavid Puffer Assigned ToGeorg Biehler  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.00.00 RC2 
Target Version1.00.00 RC3Fixed in Version1.00.00 RC3 
Summary0007717: EstablishConnections: Description of SetCommunicationConfigurationCmd
Description

6.2.4.3.9 describes behavior of SetCommunicationConfigurationCmd.

Current text refers to:

1) Table 10 for StatusCodes indicating errors regarding the FunctionalEntity -> OK
2) Table 11 for StatusCodes indicating errors regarding the ConnectionEndpoint -> not OK (the text does not describe creating the ConnectionEndpoint).
Proposal: remove reference
3) Table 14 and 15, which contain possible StatusCodes in case of errors during processing of the command -> OK, but table 14 only contains a single entry: "Bad_InvalidArgument: At least one of the fields does not match communication model specific requirements: InputVariableIds, InputGroupId, OutputVariableIds, OutputGroupId."
This description is not specific enough.
Proposal: Clarify under which conditions the implementation has to issue this StatusCode (e.g. does this have to be returned, if an OutputVariable was requested, but is then not contained in the PublishedDataSet?)

TagsNo tags attached.

Activities

Georg Biehler

2022-02-14 11:51

developer   ~0016002

2) Reference is needed, if the ConnectionEndpoint provided does not exist, invalid NodeId... --> reference to Table 11 is kept
3) updated Text in 6.2.4.3.9 and clarified usage of the statusCodes throughout

Paul Hunkar

2022-02-18 15:06

manager   ~0016052

reviewed changes in call , agreed to text and closed issue

Issue History

Date Modified Username Field Change
2022-02-10 14:17 David Puffer New Issue
2022-02-11 13:50 Paul Hunkar Assigned To => Georg Biehler
2022-02-11 13:50 Paul Hunkar Status new => assigned
2022-02-14 11:51 Georg Biehler Status assigned => resolved
2022-02-14 11:51 Georg Biehler Resolution open => fixed
2022-02-14 11:51 Georg Biehler Fixed in Version => 1.00.00 Release
2022-02-14 11:51 Georg Biehler Note Added: 0016002
2022-02-18 15:06 Paul Hunkar Status resolved => closed
2022-02-18 15:06 Paul Hunkar Note Added: 0016052
2022-05-30 22:59 Paul Hunkar Fixed in Version 1.00.00 Release => 1.00.00 RC3
2022-05-30 22:59 Paul Hunkar Target Version 1.00.00 Release => 1.00.00 RC3