Advertisement
62
Fusesaver control – no control In progress
When an operator presses a FS control, the
control-in-progress LED and the
corresponding control status LED will begin
to flash when the control has been accepted
by the RCU and sent to the Fusesavers. If the
control-in-progress LEDs do not start to
flash, the control has been rejected. A
control will be rejected for the following
reasons.
Control source – local: The control
source local LED is not lit, therefore all
FS controls from the control panel will
be rejected. See No control source –
local on page 61 to get the panel into
local control.
Control already active: The control has
been rejected because the RCU is already
in the process of sending a control to
the Fusesavers. The previous control
may have been from the remote
operator, the RCU itself (if configured to
do so) or from the control panel. If the
previous control was from the control
panel, the control-in-progress LEDs will
already be flashing.
Line not configured: If the RCU fails to
find a correctly configured FS line on
start-up, then all controls to Fusesavers
will be rejected. RCU problem LED will
be red in this case.
RCU power up: On power up, the RCU
searches for Fusesavers, checks their
configuration for correct match and
synchronizes time to them. The RCU OK
LED will be flashing during this time,
which may take up to 10 minutes to
finish and there will be no data for some
or all of the Fusesaver status LEDs.
During this time, controls to Fusesavers
will be rejected.
Communications lost: If the RCU loses
communications to a FS or is currently
verifying the configuration of a FS that
had lost communications, then all FS
controls will be rejected. This is because
all FS control panel controls are ganged
controls that require communications to
be good to all phases. Communications
lost can be indicated by the FS health
indicators, whereas the RCU verifying
the FS configuration after having lost
communications will result in the FS
status data for that phase being no data.
Button press rejected: If the operator
presses the control button for more than
5 s or presses more than one button at
the same time, the button press will be
ignored.
Fusesaver control – does not complete
When an operator presses a FS control, the
control-in-progress LED and the
corresponding control status LED will begin
to flash when the control has been accepted
by the RCU and sent to the Fusesavers. If the
control that was sent does not complete
(e.g., close control sent but some/all phases
still in open state), the most likely cause is
communications failure during the control.
Note that if the control in progress LED is
flashing, then the RCU has determined the
communications to the Fusesavers to be
working at the start of the control, so the
probability of this occurring is low.
Panel on indicator is the only LED that is
lit
When the panel is turned on and panel on
LED is the only LED that is lit, it is because
the control panel has no data for any of the
phases. The most likely cause in this case is
the RCU has just been powered up.
Panel on indicator LED and control source
are the only LEDs that are lit
When the panel is turned on and the panel
on LED and control source are the only LEDs
that are lit, it is because the control panel
has no data for any of the phases. The most
likely cause in this case is the RCU has just
been powered up, is searching for
Fusesavers and has not found a correctly
configured FS line.
Panel does not turn on
There are a number of valid reasons for a FS
control panel not turning on:
The RCU is configured with the FS
control panel disabled.
The RCU firmware is an old version and
cannot drive the FS control panel.
The FS control panel connector is not
plugged into the RCU. It is acceptable to
plug the panel into a powered up RCU
(hot connection). On re-connection, it
may take up to 30 s for the RCU to
detect the FS control panel.
The RCU power is off.
Advertisement
