Project

General

Profile

Issues #5119

LGOS/LSVS subscribe with functional naming

Added by Richard Schimmel over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
8-1
Triggering Tissue:
Final Decision:
As attached
Initial Test Document:
TP2.1
Updated Test Document:
Server Ed2.1 TP1.2
Test Case ID:
sGos4, sSbs12
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

At the 2021 SCL IOP an issue has been detected that an SCT did not provide the correct reference in the LGOS/LSVS SetSrcRef in case the publisher (logical) device uses a functional ldName. The ORG setSrcRef shall use the functional naming reference value (see clause in part 8-1). It was suggested to add/update LGOS/LSVS testcase (and also a testcase for SCT tool test)

Files

Solution to redmine 5119 LGOS-LSVS.docx Solution to redmine 5119 LGOS-LSVS.docx 19.7 KB Richard Schimmel, 12/01/2021 09:57 AM
#1

Updated by Richard Schimmel over 3 years ago

TPWG agree to add to supervise (LGOS) a GOOSE with functional naming. Similar for LSVS.
We also discussed that an ICT expects to receive an SCD from from a conformant SCT tool. An ICT is not expected to resolve all errors that a non-conformant SCT can create.

#2

Updated by Richard Schimmel over 3 years ago

Created/attached proposal

#3

Updated by Richard Schimmel over 3 years ago

  • Status changed from In Progress to Resolved
  • Final Decision set to As attached
  • Initial Test Document set to TP2.1

TPWG agrees with the attached proposal

#4

Updated by Bruce Muschlitz almost 3 years ago

  • Status changed from Resolved to Closed
  • Updated Test Document set to Server Ed2.1 TP1.2
  • Closed Reason Test Procedure Update added
  • Closed Reason deleted (--Not Set---)

Also available in: Atom PDF