Project

General

Profile

Feature #521

The GSEControl has a datSet element indicating that the gocb is configured (but with no communication entry)

Added by Herbert Falk over 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Implementation - improve conformance testing
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
2
Source:
IOP_2017/3
TF Unique ID:
2 # IOP_2017/3
WG10 Proposal:

Add a general statement into part 6 to not allow referencing a SCL element which does not exist in the file unless the reference is none.-> OK: Solved in IEC 61850-8-1 Ed2.1. A requirement is included to define GSE section for each fully defined GOOSE.

Estimated Completion:
2019-06
Discuss in Upcoming Meeting:
No
To discuss in WG10:
Short Proposal:

UCA SCT conformance testing must address.Make a generic rule at the beginning of -6 about inter section references. In this particular case,<GSE can not exist without the matching/referenced <GSEControl

Standard(s):

IEC 61850-8-1

Needs More Information:
Assigned TF:

Description

In Version 2 of the IntegratedApplication.scd”, we found the IED “CYG_PR7367_A1_P1” AccessPoint “G1” which contains a GSEControl named “gocb” but there is no associated GSE address in the Communication section. This seems to be an invalid GOOSE configuration because it cannot be published without an address.

The GSEControl had a datSet!=null. Indicating that the gocb was configured (but with no communication entry). The standard does not declare if this is valid or not.

There may be more errors like this, but this was just the first one we found.

Also available in: Atom PDF