The setting example in the image above presents a two-shot auto-recloser. One can see that the REQ1
is started by I> START signal. The starting delay is 500 ms, followed by a 200 ms dead time; after a
200 ms "Arcing" time and a 10 s reclaim time Shot 1 is executed. If Shot 1 fails, there is a 120 s dead
time, a 200 ms "Arcing" time and a 10 s reclaim time before Shot 2 is executed. If Shot 2 fails, the auto-
recloser initiates the Final Trip. In REQ2, the settings are otherwise the same, except I> TRIP and I0dir>
TRIP are used to activate the request, Shot 1 does not have a starting delay, the dead time delay for
Shot 2 is different and the action time for both shots is zero. REQ3 has just one shot with a 60 second
dead time and a 30 ms shot reclaim. If REQ4 or REQ5 are activated, no shots are executed as none
are set.
Inhibit and Locked states of the auto-recloser function
The auto-recloser function can have several reasons to go into
"Lock-out" and "Inhibit" states where
reclosing cannot be allowed for some reason. When the function enters the "Not ready" state, it gives
an indication of the reason why it cannot be in the "Ready" state in order to quickly rectify whatever is
causing the problem of the functions operation. The reason is indicated in the auto-recloser function's
Registers menu.
The Inhibit reasons for the auto-recloser are the following:
• AR is blocked (from Blocking input)
• AR is not enabled (signal connected to "AR ON/OFF" is not active)
• AR is calculating the lock-out delay
• The object "Open" or "Close" command is blocked
• The object status is not known ("intermediate" or "bad" status)
• General reclaim time is running
• AR is locked
When the auto-recloser function is in the "Inhibit" state, it returns to the "Ready" state when the reason
for the inhibition is removed.
The Lock-out reasons for the auto-recloser are the following:
• The "AR Locked" signal is initiated (from "AR Locking" input)
• The Final Trip signal is given
• The "object not ready" failed within a given time (from Object)
• The "object no sync" failed within a given time (from Object)
• The object's "Open" timeout (from Object)
• The object's "Close" timeout (from Object)
• AR request initiated during General reclaim time
• AR request was not released during Dead Time
• Critical request initated in any state of the auto-reclosing cycle
When the auto-recloser function is in the "Locked" state, it can be recovered only through by reset
input, or by manually resetting the breaker. This depends on what the "Require manual resetting"
parameter's setting is.
Displaying auto-reclosing timers in MIMIC view
The user can enable timers to be displayed in the MIMIC view. Enable the AR timer value at
Tools
→
Events and logs
→
Set alarm events (see the image below). The timer displays the reclaim time and
the dead time delay.
A
AQ
Q-F215
-F215
Instruction manual
Version: 2.04
324
