Project

General

Profile

Support #524

The use of the Simulation bit in the R-GOOSE Payload is not clearly defined. It refers only to 8-1 which currently only specifie

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

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
5
Source:
IOP_2017/7
TF Unique ID:
5 # IOP_2017/7
WG10 Proposal:

covers by the next revision

Estimated Completion:
Wait until 61850-8-1 Ed.2.1 IS is published
Discuss in Upcoming Meeting:
To discuss in WG10:
Short Proposal:

Clarify the text so that it is clear that there is a Simulation Bit in the payload whose value is the same as the Simulation bit in the GOOSE PDU for which the payload production wraps. The text should be similar to clause C.2.5 which states:

“S: simulated. The S bit mirrors the service parameter Simulation of the SendGOOSE service. Its (redundant) presence in the ethernet header has been specified to allow performant filtering on layer 2 level. “.

8-1 Ed2.1 CDV issue

Resolved in FDIS, no action needed.

Standard(s):

1-Aug

Needs More Information:
Assigned TF:

Description

The use of the Simulation bit in the R-GOOSE Payload is not clearly defined. It refers only to 8-1 which currently only specifies the meaning of the simulation bit in the GOOSE PDU. The standard does not describe that the payload Simulation bit should reflect whether or not the Simulation bit is set on ANY GOOSE PDUs in that payload.

J.3.2.6.3 states:
Simulation shall be a BOOLEAN value (e.g. one octet) and shall be as defined in
IEC 61850-8-1.

This clause is self-referencing and does not properly define what the definition is.

#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Closed

Confirm to IEC 61850-6 editor that this issue has been accounted for.

Also available in: Atom PDF