Project

General

Profile

Issues #6724

GOOSE Subscriber sGos12 test expects DUT to _send_ a GOOSE message

Added by Ursula Kramarczyk about 2 months ago. Updated 11 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
04/30/2024 (Due in 3 days)
Discuss in Upcoming Meeting:
Yes
Clause Reference:
18.2.3.6
61850 Standard:
7-2
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
sGos12
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

The expected result of mandatory sGos12 demands that DUT sends (so, it publishes) a GOOSE message. What if DUT does not have Publisher services, or its GoCB do not refer dataset with the subscribed state change?

#1

Updated by IEC 61850 TPWG 25 days ago

  • Project changed from Server to Client
  • Due date set to 04/16/2024
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel

Add a client tp to test GOOSE subscriber without server model.

Changed to client test.

Richard to submit proposal. PIXIT should indicate how the data received is exposed.

#2

Updated by IEC 61850 TPWG 11 days ago

  • Due date changed from 04/16/2024 to 04/30/2024

Also available in: Atom PDF