Project

General

Profile

Issues #7091

sSrv17 - New value should be different from the previous one and not from the SCL value. Test case will not work twice with SPG setpoints.

Added by Erik San Telmo 5 days ago. Updated about 17 hours ago.

Status:
In Progress
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
01/21/2025 (Due in 13 days)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
sSrv17
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

The first step is wrong, as these values are non-volating the new value shall be different from the existing one in the DUT. Imagine the case with a SPG setpoing that is set to "false" in the CID file. You will execute the test case to modify the SPG.setVal to "true" and the first time the test case works but once you reboot the DUT the SPG.setVal will start in value "true" and if you repeat the test case and you have to write a "value different from the SCL" you are not changing the current value of the SPG setpoint.

Please, change the first step in Test Description from

1. For each functional constraint client requests at least one SetDataValues of a writable attribute with FC=SP, DC, EX with a new
value which is different from the initial value in SCL

to

1. For each functional constraint, client requests at least one SetDataValues of a writable attribute (Valkind=Set) with FC=SP, DC with a new
value which is different from the existing value in the DUT.

#1

Updated by Erik San Telmo 5 days ago

There are (at least) two typos in my previous description.... I cannot modify the original wording,sorry, please change
volating ---> volatile
setpoing ---> setpoint

#2

Updated by IEC 61850 TPWG about 17 hours ago

  • Due date set to 01/21/2025
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel

Also available in: Atom PDF