View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010246 | Part 81: UAFX Connecting Devices and Information Model | Spec | public | 2025-03-21 11:43 | 2025-03-21 13:33 |
| Reporter | Jan Murzyn | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Product Version | 1.00.03 | ||||
| Summary | 0010246: Extend description of BadNothingToDo in Table 19 – CommunicationConfigurationResults Result StatusCodes | ||||
| Description | In the Base Facet WG call on 17th Jan 2025 it was agreed that if the SetCommunicationConfigurationCmd is skipped due to a failure of any of the previous commands, the implementations shall set BadNothingToDo as a result code corresponding to the command. This would be consistent with specification of all other commands. The above agreed update must have slipped, because it's not included in the released text. The following text must be added in Table 19 in the description of BadNothingToDo code: "SetCommunicationConfigurationCmd was skipped because a preceding command had already resulted in an error." | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-21 11:43 | Jan Murzyn | New Issue | |
| 2025-03-21 13:33 | Paul Hunkar | Assigned To | => Paul Hunkar |
| 2025-03-21 13:33 | Paul Hunkar | Status | new => assigned |
