Issues #6518
Functional constraint object non-volatility ambiguous - TISSUE 1822
Description
Test procedure needs to add steps to consider writable CF, SP, DC.
Write CF/SP/DC, restart device, validate online changes are kept.
Files
Updated by Richard Schimmel over 1 year ago
- Initial Test Document set to Ed2.1 TP1.2
- Test Case ID set to sSrv16 (new)
I propose to add a new (conditional) test case (sSrv16) in the server group.
Test description
1. Client requests SetDataValues of a writable attribute with FC=SP, DC, EX with a new value which is different from the initial value in SCL
2. Client requests GetDataValues
3. Cause DUT restart by simulating a temporarily power outage and client requests associate
4. Client requests GetDataValues
Expected result
1. DUT sends response+
2. DUT sends response+ with the new value
3. DUT send Associate response+
4. DUT sends response+ with the new value
Updated by Richard Schimmel over 1 year ago
solution attached
Updated by IEC 61850 TPWG over 1 year ago
- Due date changed from 11/28/2023 to 12/12/2023
Add: test one of each FC, selected by the test engineer.
Updated by Richard Schimmel over 1 year ago
- File Solution to redmine 6518 sSrv16 dd20231219.docx added
Added "For each functional constraint client requests at least one" in the attachment.