Project

General

Profile

Improvement #441

Limitations of one to one mapping between LNode and LN

Added by Herbert Falk about 3 years ago. Updated 5 months ago.

Status:
Closed
Priority:
High
Category:
Standard clarification required
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
4
Source:
Vattenfall
TF Unique ID:
4 # Vattenfall
WG10 Proposal:

to be adressed to the 61850-6-100 (need a realistic date)6-100 states that n:1 relationship between LNodes and LNs is allowed and supported. No need to change the SCL scheme for this.

Estimated Completion:
End of 2023
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

Discussed with TF SCL function modelling.

Standard(s):

IEC 61850-90-30

Needs More Information:
No
Assigned TF:
61850-6-100 (Function modeling)

Description

The Standard requires a one to one mapping between LNode and LN. This creates serious limitations. Examples:
1. Let us assume vendor makes use of GGIO and represent a 32 bit BI/O Interface Card in the IED with the LN BIO32GGIO1. Now in my Substation section I define two Functions with Fun1/BIOGGIO1, Fun2/BIOGGIO2. Fun1 and Fun2 are two very different functions, but I have only one BIO card in my IED. Now I would like to map the LNode Fun1/BIOGGIO1 to LN BIO32GGIO1 and Fun2/BIOGGIO2 also to LN BIO32GGIO1. Naturally they use distinct Data Attributes.

2. It is easy to find a similar example for MMXU. Power Measurement and Current/ Voltage Measurement can be used in different Functions in the Single Line, but are using the same LN MMXU.


Files

Captura.PNG View Captura.PNG 28.4 KB Mapping LNode DOs to LN DOs when mapping is not direct from doName Carlos Rodriguez del Castillo, 03/15/2022 11:08 AM

Related issues

Related to IEC 61850 User Feedback Task Force - Bug #442: Maping LNode (substation section) to LN (IED section)Closed

Actions
#1

Updated by Herbert Falk about 3 years ago

  • Priority changed from Normal to High
#2

Updated by Carlos Rodriguez del Castillo about 3 years ago

  • Tracker changed from Bug to Improvement
  • Subject changed from The Standard requires a one to one mapping between LNode and LN. This creates serious limitations. Examples: 1. Let us assume ve to Limitations of one to one mapping between LNode and LN
  • Status changed from New to In Progress
  • Standard(s) set to IEC 61850-6-100
  • WG10 Proposal changed from to be adressed to the 61850-6-100 (need a realistic date) 6-100 states that n:1 relationship between LNodes and LNs is allowed and supported. No need to change the SCL scheme for this. to to be adressed to the 61850-6-100 (need a realistic date)6-100 states that n:1 relationship between LNodes and LNs is allowed and supported. No need to change the SCL scheme for this.
  • Discuss in Upcoming Meeting set to Yes
#3

Updated by Carlos Rodriguez del Castillo about 3 years ago

Checking onde

#4

Updated by Carlos Rodriguez del Castillo about 2 years ago

  • Status changed from In Progress to Resolved
  • Estimated Completion changed from Ed 3 to Ed 1
  • Discuss in Upcoming Meeting changed from Yes to No
  • To discuss in WG10 set to No

6-100 does not cover the issue completely. Relation LNode - LN is 1:1, but what it is possible is to map remaining DOs not covered by mapped LN to DOs of other LN.

#6

Updated by Carlos Rodriguez del Castillo 12 months ago

  • Estimated Completion changed from Ed 1 to End of 2023
  • Standard(s) changed from IEC 61850-6-100 to IEC 61850-90-30
  • Needs More Information set to No
#7

Updated by Vladan Cvejic 5 months ago

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

Updated by Vladan Cvejic 5 months ago

  • Status changed from Resolved to Closed
  • Discuss in Upcoming Meeting changed from Yes to No
  • Assigned TF 61850-6-100 (Function modeling) added

Solution is incorporated in the 90-30. Mapping is done on DO level (not LN level) which increase flexibility.

#9

Updated by Vladan Cvejic 5 months ago

  • Related to Bug #442: Maping LNode (substation section) to LN (IED section) added

Also available in: Atom PDF