Project

General

Profile

Improvement #5372

Simultaneous change of InRef.setSrcRef and InRef.setSrcCB for dynamic commutation

Added by Maud Merley over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Standard extension required
Start date:
05/31/2022
Due date:
% Done:

0%

Estimated time:
ID:
Source:
RTE
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):

IEC 61850-7-1

Needs More Information:
No
Assigned TF:

Description

A simple static communication description in SCD based on “Input/ExtRef” combined with later binding is not always sufficient for all applications. Indeed, one of the most important use cases is redundancy management. For example, it may be necessary for a protection function to switch the subscription between SV streams published by two redundant MU or between GOOSE streams published by two redundant SCU.
The associated configuration used by Rte is based on the DO “InRef”. This DO allows to point to different IEC 61850 addresses and also to manage the test streams. The dynamic change to another SV or GOOSE stream is based on updating the Data Attributes (DA) “setSrcCB” and “setSrcRef”.

1. It seems required to have the capability of changing simultaneously the DA setSrcRef / setSrcCB of an InRef DO.
If not, there is a risk that the application use the wrong input signal while setSrcRef has changed and setSrcCB has not, for instance.

2. It seems required to have the capability of changing simultaneously the DA setSrcRef / setSrcCB of multiple InRef DO of a same LD.
If not, there is a risk that the application use for instance an input signal on SAMU A, and other inputs signal from SAMU B, which is discrepant from a system perspective.


Files

Multiplexer.PNG View Multiplexer.PNG 15.9 KB Vladan Cvejic, 06/07/2022 09:23 AM

Proposal descriptions

Referring to TISSUE: https://iec61850.tissue-db.com/tissue/1727 (Similar problem that has to be resolved in future)
Suggestion is to subscribe to all streams and to have multiplexer behind to swap between the streams.
How the multiplexer will be resolved?
Proposal is that there should be DataObject (or other) that will be associated to Multiplexer mechanism.

ExtRefs are coming from different IEDs. ExtRef/InRef are in 1:1 relation.
Proposal of this group is to start with multiplexer solution in 7-1 (Ed 3) and to extend to other Parts.


Related issues

Copied to IEC TC57 WG10 Future Work - WG10 Future Work #5934: Simultaneous change of InRef.setSrcRef and InRef.setSrcCB for dynamic commutationNew05/31/2022

Actions
#1

Updated by Vladan Cvejic over 2 years ago

  • File Multipexer.PNG added
  • Proposal descriptions updated (diff)
#2

Updated by Vladan Cvejic over 2 years ago

  • File deleted (Multipexer.PNG)
#3

Updated by Vladan Cvejic over 2 years ago

  • Category set to Standard extension required
  • Status changed from New to Resolved
  • Proposal descriptions updated (diff)
  • Standard(s) set to IEC 61850-7-1
#4

Updated by Vladan Cvejic over 2 years ago

#5

Updated by Vladan Cvejic over 2 years ago

  • Copied to WG10 Future Work #5934: Simultaneous change of InRef.setSrcRef and InRef.setSrcCB for dynamic commutation added
#6

Updated by Carlos Rodriguez del Castillo over 1 year ago

  • Needs More Information set to No
#7

Updated by Carlos Rodriguez del Castillo over 1 year ago

  • Discuss in Upcoming Meeting changed from No to Yes
#8

Updated by Carlos Rodriguez del Castillo over 1 year ago

  • Discuss in Upcoming Meeting changed from Yes to No

Also available in: Atom PDF