Issues #6724
GOOSE Subscriber sGos12 test expects DUT to _send_ a GOOSE message
Due date:
08/06/2024 (about 4 months late)
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?
Files
Updated by IEC 61850 TPWG 8 months 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.
Updated by Richard Schimmel 6 months ago
- File Solution to redmine 6724 GOOSEsub.docx Solution to redmine 6724 GOOSEsub.docx added
- Initial Test Document set to Client amd1 TP1.0
Added solution - need to be reviewed at TPWG
Updated by IEC 61850 TPWG 6 months ago
- Due date changed from 05/28/2024 to 06/11/2024
Change "display" to "expose as described in PIXIT"
Updated by Richard Schimmel 4 months ago
- File Solution to redmine 6724 GOOSEsub - July26.docx Solution to redmine 6724 GOOSEsub - July26.docx added
Updated the solution;
How about sGos6b, putting the device in simulation mode “LPHD.Sim=T”. Should we keep this?
Updated by IEC 61850 TPWG 4 months ago
- File Solution to redmine 6724 GOOSEsub - Aug6.docx Solution to redmine 6724 GOOSEsub - Aug6.docx added
- Status changed from In Progress to Resolved