Project

General

Profile

Feature #622

Parameters not available in standardized LN

Added by Carlos Rodriguez del Castillo almost 2 years ago. Updated 11 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Standard extension required
Start date:
11/24/2020
Due date:
05/24/2021
% Done:

0%

Estimated time:
ID:
18
Source:
RTE
TF Unique ID:
18 # RTE
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

Need use cases before going into details

Standard(s):

IEC 61850-7-4

Needs More Information:
No

Description

Some parameters needed for RTE functions are not available in normalized LN. Some generic parameters (with threshold, delay, boolean) should be available, for example in LN GAPC.
Example : for Passive Load Feeder Protection, it is needed to have an "on/off" parameter for the blocking of PAP function in case of upstream fault detected by distance protection.


Files

20210326-RTE Use cases 622.docx 20210326-RTE Use cases 622.docx 20.2 KB Use case explanation Carlos Rodriguez del Castillo, 05/25/2021 10:14 AM
20210326-RTE Use cases 622_v2.docx 20210326-RTE Use cases 622_v2.docx 24 KB more details on use cases Maud Merley, 12/04/2022 11:56 PM

Related issues

Copied to IEC 61850 User Feedback Task Force - Feature #6216: Parameters not available in standardized LN - SetPhNumNew11/24/202005/24/2021

Actions
#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Feedback
  • Short Proposal set to Need use cases before going into details

During meeting 2020-11-24:
We need a list of the needed settings requierements and then we could decide to include in the GAPC LN.
Likely to be part of edition 3.
RTE will send us the list and use case of parameters and definition.
There is a concern about the "threshold" and how many of them we will need

#2

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Start date changed from 10/07/2020 to 11/24/2020
#3

Updated by Carlos Rodriguez del Castillo almost 2 years ago

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

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from Feedback to Triage
#5

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Due date set to 05/24/2021
  • To discuss in WG10 set to No

2021-03-02: RTE will provide use cases.

#6

Updated by Carlos Rodriguez del Castillo over 1 year ago

2021-05-25:
- GPAC LN use cases: RTE to give more information
- SetPhNum/SetPhsOrig: Information should be taken from the source, using the connection between the source and the target P-Logical Nodes.
- NamAccRtg: Should be taken from the SCL file. This setting is part of the TCTR/TVTR.
- PhyConnITF: Clarification from RTE is needed, If the goal is to indicate the type of interface, Communication section could be used to model this interface.
- VRtg – ARtg – HzRtg: Similar to the other ones, this information should be part of the source to guarantee consistency of information, rather than having the same setting in all of the P-logical node instances. The question is how to be able to get this information and how to be sure that the information is in the CID file of the IED that needs the information. Possibilities: ExtRef with Poll method.

#8

Updated by Vladan Cvejic 7 months ago

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

Updated by Vladan Cvejic 3 months ago

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

Updated by Carlos Rodriguez del Castillo 3 months ago

  • Needs More Information set to Yes
#11

Updated by Maud Merley about 2 months ago

More information added in the RTE use case document with answers to WG10 UF comments.

#12

Updated by Carlos Rodriguez del Castillo about 1 month ago

We need more time to understand the info provided by RTE.
- We need a clearer use case for SetPhNum proposal, to understand the dynamic change of the setting
- OpDlTmms in GAPC LN has been discussed in the past, should be handled in Ed3. --> Create an issue in WG10FutureWork related to this
- DITmms, StrVal, OnOff, SetNb --> Needs separate discussions

Actions for next meeting:
- CRC: Split the issue in separate issues to addressed them separately.

#13

Updated by Carlos Rodriguez del Castillo 12 days ago

  • Copied to Feature #6216: Parameters not available in standardized LN - SetPhNum added
#14

Updated by Carlos Rodriguez del Castillo 11 days ago

  • Status changed from Triage to Closed
  • Discuss in Upcoming Meeting changed from Yes to No
  • Needs More Information changed from Yes to No

This issue has been splitted in independent issues (#6216 to #6225) for each of the new DO proposal, so we close it.

Also available in: Atom PDF