Project

General

Profile

Issues #5917

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

Added by yifan wang 4 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Urgent
Due date:
10/18/2022 (43 days late)
Discuss in Upcoming Meeting:
No
Clause Reference:
Ed2.0 Server TP2.0.6 CB9b: GOOSE subscribe
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
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

#1

Updated by yifan wang 4 months ago

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

Updated by IEC 61850 TPWG 4 months ago

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

Updated by yifan wang 4 months ago

  • Description updated (diff)
  • Priority changed from Normal to Urgent
#4

Updated by Richard Schimmel 3 months ago

see proposal attached file

#5

Updated by IEC 61850 TPWG 3 months ago

  • Due date changed from 09/06/2022 to 09/20/2022
#6

Updated by Thierry Dufaure 3 months 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.

#7

Updated by Richard Schimmel about 2 months ago

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

#8

Updated by IEC 61850 TPWG about 2 months ago

"GOOSE ping-pong" change to "ping-pong", otherwise accepted.

#9

Updated by IEC 61850 TPWG about 2 months ago

  • Due date changed from 09/20/2022 to 10/18/2022
#11

Updated by Thierry Dufaure about 1 month ago

I agree with the proposed changed of draft from Oct, 5th.

#12

Updated by IEC 61850 TPWG about 1 month ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF