Project

General

Profile

Support #613

Clarification of representation of tap changer (LN ATTC, YLTC).

Added by Carlos Rodriguez del Castillo almost 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Standard clarification required
Start date:
10/23/2020
Due date:
% Done:

0%

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

1. TapOpR and TapOpL are for control by GOOSE 2. TapChg/TapPos.valWTr has the transient indication. TapChg/TapPos.valWTr will be updated with transient indication even if the command has been executed with control by GOOSE or by any other means. RTE will provide more information from the use case with the people originating the issue.

Standard(s):

IEC 61850-7-4

Needs More Information:
Assigned TF:

Description

1.The semantic of TapOpL et TapOpR (ATCC) is not clear between status and control objects. In IEC61850-7-3, it is mentionned "The command is received ('opRcvd') by the IED as a control service or as a GOOSE message with a data object semantic resulting in a change of the controllable object (e.g. CSWI.OpOpn/OpCls, CPOW.OpOpn/OpCls, PTRC.Tr, RREC.OpCls, RBRF.OpEx, ATCC.TapOpR/TapOpL, SIMG.InsTr, ...)." or ATCC.TapOpR/TapOpL are status DO (SPS).

2. There is no DO in YLTC to indicate that the position is being changed.

1. Risk of misunderstanding.
2. Helpful for maintenance and exploitation of the system.

Also available in: Atom PDF