1892   Remove TapOpStop from ATCC

Created: 06 Nov 2023

Status: Accepted

Part: Part 7-4 (2020; Edition 2.1)


Page: 140

Clause: 6.4.5

Paragraph: Table 55


I do not see any reason what the TapOpStop in ATCC should be used for. If a tap changer shall be stopped while it is running this is a case of emergency. In this case either the motor protective switch of the motor is activated or the motor automatically stops and runs in the other direction. Both cases are not used via 61850.
The information that the motor protective switch was activated should be another DO but also not TapOpStop.
The reason why I created this tissue is that in 90-29 this DO was proposed to also be added to YLTC and in my opinion this should not be done.


Remove the DO TapOpStop from ATCC

Discussion Created Status
On behalf of Leader of TF 90-29:
Yes, in the TF90-29 meeting it was understood that the falling edges of TapOpR and TapOpL are to be used to represent the end (stop) of the raise resp. lower operate execution. In pulse mode (‘persistent’=”false”) a control will trigger a singular step raising or lowering of the OLTC.
In persistent mode the engineer will need to use a “stop” for initiating the termination of the persistent outputs “higher” or “lower”.
24 Nov 23 Accepted
The ATCC.TapOpStop was introduced in Ed2 to map a stop status when the service Operate(ATCC.TapChg, ctlVal = stop).
Consider deprecation instead of removal during the discussion in the TF + consider enhancing the TapOpR, and TapOpL that are both Trigger, because it seems (TF 90-29 discussion in Stockholm) that there are Trigger anymore but active as long as they stay. The falling edge for TapOpR and TapOpL was discussed as representing the end (stop) of the raise resp. lower operate execution, was it not?
24 Nov 23 Accepted
This issue should be discussed within task force 61850-7-500.
A description of the different control methods to change position of OLTC (in automatic, manual modes) could be included in future TR 7-500. LN ATCC and YLTC are involved in these control actions.
22 Nov 23 Accepted


Privacy | Contact | Disclaimer

Tissue DB v.