Control Source - Siemens Connect: Local control will not be allowed while Siemens connect is
in session with the Fusesavers.
Control Source – Remote: Local control may not be allowed while the remote operator has control
to the Fusesavers. This functionality depends on the configuration setting of the RCU.
RCU Power up: On power up the RCU will search for and check the configurations of Fusesavers
in the vicinity. During this time the RCU Switchgear OK LED will be flashing and both local and
remote control to Fusesavers is not available.
Fusesaver External Lever Down: When the external lever of any Fusesaver on the line is down
then controls to all Fusesavers, remote or local, are disallowed. Depending on the RCU
configuration trip controls may still be allowed even though the control source is LED is not lit.
RCU Synchronising New Time: All RCU controls, remote or local, will be locked out for a short
period (less than 30 seconds) when new time is being synchronised from the RCU to the
Fusesavers, this avoids unreliable controls.
9.7.3 Fusesaver Control – No Control In Progress
When an operator presses a Fusesaver 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 Fusesaver controls
from the Control Panel will be rejected.
Control Already Active: The control has been reject 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 Fusesaver line on start-up then
all controls to Fusesavers will be rejected. RCU Switchgear Problem LED will be red in this case.
RCU Power up: On power up the RCU searches for Fusesavers, check their configuration for
correct match and synchronises time to them. The RCU Switchgear 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 Fusesaver or is currently verifying
the configuration of a Fusesaver that had lost communications then all Fusesaver controls will
be rejected. This is because all Fusesaver Control Panel controls are ganged controls that
require communications to be good to all phases. Communications lost can be indicated by the
Fusesaver Health Indicators whereas the RCU verifying the Fusesaver configuration after having
lost communications will result in the Fusesaver status data for that phase being No Data.
Button Press Rejected: If the Operator Presses the control button for more than 5 seconds or
presses more than one button at the same time the button press will be ignored.
9.7.4 Fusesaver Control – Does Not Complete
When an operator presses a Fusesaver 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.
9.7.5 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. This 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.
9.7.6 Panel On Indicator LED and Control Source are the only LED that are lit