Advertisement
Siemens Connect control
If a local operator is using the Siemens
Connect PC application to operate the line
Fusesavers (this is called being in-session),
then the RCU will not send controls to the
Fusesavers and will not retrieve events from
the Fusesavers. This is because Siemens
Connect is considered to be a local operator
and takes charge of communications to the
Fusesavers. Any controls received from the
SCADA system or from a Fusesaver control
panel fitted to the RCU will be rejected.
Once the Siemens Connect session is
complete, all new events in the Fusesaver
will be passed to the RCU for relay through
the SCADA system.
While Siemens Connect is in-session with
the Fusesavers, a digital point indicating
that the Fusesavers are not in-session with
the RCU is available for transmission to the
SCADA system.
Fusesaver protection mode control
One of the core functions of the RCU is to
allow remote control of the Fusesaver
protection functionality. The Fusesaver has
five possible protection modes as defined in
the Fusesaver operating instructions
(IC1000-F320-A170-XX-XXXX) as follows:
1. Normal mode: The Fusesaver utilizes the
protection curve defined by the policy
file and fuse settings at time of
configuration. The Fusesaver will
automatically close after the dead time.
2. Protection off mode: The Fusesaver will
not trip when a fault occurs, protection
functionality is disabled.
3. Normal single mode: The Fusesaver
utilizes the protection curve defined by
the policy file and fuse settings at time
of configuration. The Fusesaver will not
automatically close after the dead time,
i.e., it will trip and stay in the open
state.
4. Fast single: The Fusesaver protection is
set to instantaneous. The Fusesaver will
not automatically close after the dead
time, i.e., it will trip and stay in the open
state.
5. Fast mode: Fusesaver protection is set to
instantaneous. The Fusesaver will
automatically close after the dead time.
The Fusesaver can be put into any of these
modes from the following inputs:
1. The external lever of the Fusesaver.
When the lever is pulled down, the
protection mode is forced to the mode
defined in Fusesaver policy file. This
always overrides the current mode
setting in force. Important - when the
external lever is returned to the UP
position the protection mode will return
to whichever mode was active prior to
the lever being pulled down.
2. Commands from the RCU sent over the
short-range radios that have originated
from a SCADA operator.
3. Commands from the RCU sent over the
short-range radios that have originated
from an operator control panel in the
RCU (if one is fitted).
4. Commands from the RCU sent over the
short-range radios that have originated
from the RCU itself when certain
configurable conditions are met.
The interlocking of these sources of control
is defined in Table 3 on page 22, the result
of the interlocking can be summarized as
follows:
When a Fusesaver external lever is
down, the protection mode is set to the
mode predetermined in the Fusesaver
policy file (for example, a Fast-Single
mode to be used for live line working).
When any Fusesaver external level is
down, the RCU locks out all Fusesavers
on the line from operations (including
mode change) via RCU control panel or
SCADA. Normally, all the Fusesavers on
the line will have their levers pulled
down at the same time so their mode is
the same.
When the Fusesaver external lever is up
on all the Fusesavers, then the SCADA
operator can control the protection
mode or a local operator can control the
protection mode depending on the
position of the remote control on
switch. However, if desired, the RCU can
be configured so that the RCU operator
control panel is always active to change
mode control irrespective of the remote
control switch.
21
Advertisement
