133   LN RREC - Unsuccesfull

Created: 21 Mar 2005

Status: In Force (green)

Part: Part 7-4 (2003)





Category: Issue for edition 2 of this part


In LN RREC is has been proposed AutoRecSt with new value 4 Unsuccesfull.

A new and different concept is “Definite Trip” that must also be signalized whether RREC is blocked, as any new trip lead to a definite trip.

Juan Torres


To add Definite Trip as different value from Unsuccesfull.

(In case of local data the value = -1 has been chosen by Iberinco).

Discussion Created Status
15 Jul 05 In Force (green)
There is a general problem if we have too many data as optional but being related with the basics of a functions. E.g. if we have TrBeh and RecCyc only optional then the protection which needs this data does'nt now where to get it from. At least the system engineering tool doing consistency checks will state an uninteroperability which is true. Or with other words: Not all autoreclosers are compatible with all protection despite both are IEC 61850 compliant. Nevertheless, to get agreement, I have left this data optional.
The settings of the Max Cycl and both the TrMod1 and RecTmms1 have to stay mandatory since otherwise we have no autoreclosure at all.
The comment from Thierry to skip the Close Pulse Time PlsTmms since it belongs to the circuit breaker is true by theory but we have als such a setting in the PTRC.
Therefore I do not skip this data but I will open a new tissue to clarify the relationsship between PlsTmms in RREC, TrPlsTmms in PTRC and the pulseConfig attribute in DPC. Attached you will find the final proposal for voting.
12 May 05 Ballot Period


Privacy | Contact | Disclaimer

Tissue DB v.