Project

General

Profile

Improvement #441

Limitations of one to one mapping between LNode and LN

Added by Herbert Falk over 1 year ago. Updated 7 months ago.

Status:
Resolved
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:
Ed 1
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

Discussed with TF SCL function modelling.

Standard(s):

IEC 61850-6-100


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

Also available in: Atom PDF