Issues #5917

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

Added by yifan wang 8 months ago. Updated 5 months ago.

Due date:
10/18/2022 (about 5 months late)
Discuss in Upcoming Meeting:
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:


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)"


Also available in: Atom PDF