Issues #5917: 'Expected result' for some test cases of CB9b: GOOSE subscribe - Server - UCAIug Issue Tracking System

Issues #5917

'Expected result' for some test cases of CB9b: GOOSE subscribe

Added by yifan wang over 1 year ago. Updated about 2 months ago.

Status:

Closed

Priority:

Urgent

Assignee:

Richard Schimmel

Due date:

10/18/2022

Discuss in Upcoming Meeting:

Clause Reference:

Ed2.0 Server TP2.0.6 CB9b: GOOSE subscribe

61850 Standard:

Triggering Tissue:

Final Decision:

Initial Test Document:

Ed2Amd1 TP1.1 and Ed2 TP2.0.6

Updated Test Document:

TP1.3

Test Case ID:

sGos1, sGos8, sGos9, sGos10, sGos11, sGos12, sGos13, sGos23.

Closed Reason:

--Not Set---

Triggering Tissue 2:

Triggering Tissue 3:

Description

According to page 156 of Ed2.0 Server TP2.0.6:
"To perform the DUT subscribe test procedures the DUT need to be configured as follows:
• a data value that is connected to a subscribed GOOSE member, e.g. GGIO.SPS01
• a data set that contains the value of this data point
• a GoCB that publishes this data set (or a RCB that sends a data change/quality change report)"

Suggest to update the description for some test cases of CB9b: GOOSE subscribe:
'Expected result': "DUT updates the value and sends a GOOSE message with changed status value" => "DUT updates the changed status value"
'Test description': "Test engineer configures the DUT with subscribed GOOSE (ping-pong mechanism)" => "Test engineer configures the DUT with the ping-pong mechanism ("the ping-pong mechanism" can either be using GOOSE or RCB)"

Files

Solution to redmine sGos with report 5917.docx	Solution to redmine sGos with report 5917.docx	39.1 KB	Richard Schimmel, 08/23/2022 09:28 AM
Solution to redmine sGos with report 5917 (4oct2022).docx	Solution to redmine sGos with report 5917 (4oct2022).docx	40.5 KB	Richard Schimmel, 10/04/2022 02:56 AM
Solution to redmine sGos with report 5917 (5oct2022).docx	Solution to redmine sGos with report 5917 (5oct2022).docx	40.5 KB	Richard Schimmel, 10/05/2022 02:10 AM

Updated by yifan wang over 1 year ago

Clause Reference set to Ed2.0 Server TP2.0.6 CB9b: GOOSE subscribe

Updated by IEC 61850 TPWG over 1 year ago

Due date changed from 08/03/2022 to 09/06/2022
Status changed from New to In Progress
Assignee set to Richard Schimmel

Updated by yifan wang over 1 year ago

Description updated (diff)
Priority changed from Normal to Urgent

Updated by Richard Schimmel over 1 year ago

File Solution to redmine sGos with report 5917.docx Solution to redmine sGos with report 5917.docx added
Initial Test Document set to Ed2Amd1 TP1.1 and Ed2 TP2.0.6

see proposal attached file

Updated by IEC 61850 TPWG over 1 year ago

Due date changed from 09/06/2022 to 09/20/2022

Updated by Thierry Dufaure over 1 year ago

I principle I agree,
The attached file nevertheless only concentrate on changing: "GOOSE message" to "GOOSE message or Report", but does not change the test description:
"with subscribed GOOSE (ping-pong meachnism)" to the proposed "with the pinong-pong mechanism involving GOOSE subscription, and either GOOSE publish or Report"....
I think the attached proposal need to be updated.

Updated by Richard Schimmel over 1 year ago

File Solution to redmine sGos with report 5917 (4oct2022).docx Solution to redmine sGos with report 5917 (4oct2022).docx added

The “goose ping-pong mechanism” is specified in detail after the table of abstract test procedures. And then referred to in each test procedure. We don’t need to copy the ping-pong mechanism details in each test procedure again. I propose we just improve the introduction text:

To perform the DUT subscribe test procedures the DUT need to be configured with a GOOSE ping-pong mechanism as follows:
• a data value that is connected to a subscribed GOOSE member, e.g. GGIO.SPS01
• a data set that contains the value of this data point
• a GoCB that publishes this data set or a RCB that sends a data change/quality change report
• the subscribed GOOSE messages have variable length encoding unless specified otherwise (sGos9