Configuration

Configure Monitoring > Miscellaneous > Operating Range Failure

Removing a device If a device shall be removed from an already running and commis‐
sioned network, proceed as follows:
Removing a device 1. Execute the system update order

If you are removing the device before you hit

the system update order, you must know that
it will come to a missing member alarm with
the consequence that the system goes into a
droop function (if configured). If that has hap‐
pened, you can solve the issue by a system
update order. But do not forget to make a
system check via the diagnostic screens.

2. You have now 30 seconds time to remove the device, without

getting any consequences on the system

4.5.6.16 Operating Range Failure

General notes The operating range failure monitoring issues an Operating Range
Failure Alarm "Oper.range failed XX" (where XX is the number of
Check 01 to 12) if one of the following conditions is fulfilled.
Example: Check 4 failed causes “Oper.range failed 4” .

Only the first incoming operation range failure will

tripp an alarm. Because in most cases this will be
the root cause for eventually incoming further oper‐
ating range alarms. Any other operating range
alarm can only be tripped if there is no active or
latched operating range alarm.

If there are more than one failures only the first

incoming failure will be indicated and is available at
protocol 5014.
If there is no alarm this number is 0.

n Check 1: The easYgen tries to close the GCB, but the gener‐
ator is not within its operating range (parame‐
ters 5800 Ä p. 322, 5801 Ä p. 322, 5802 Ä p. 322, or
5803 Ä p. 322).
n Check 2: The easYgen tries to synchronize the GCB, but the
busbar is not within the generator operating range (parame‐
ters 5800 Ä p. 322, 5801 Ä p. 322, 5802 Ä p. 322, or
5803 Ä p. 322).
n Check 3: The easYgen tries close the GCB in breaker transi‐
tion mode "Open transition" with GCB and MCB open status. In
this condition the busbar is expected as dead, but the busbar
voltage is NOT below the dead busbar detection limit (param‐
eter 5820 Ä p. 439).
n Check 4: The easYgen wants to close the GCB onto a dead
busbar, but the device cannot close the breaker because there
is at least one neighbor device recognized with a closed GCB.
n Check 5: The easYgen tries to synchronize the GCB, the MCB
is closed, but mains and/or bussbar are not within its operating
range (parameters 5810 Ä p. 368, 5811 Ä p. 368,
5812 Ä p. 368, or 5813 Ä p. 368).

37580C easYgen-3400XT-P1/3500XT-P1/3500XT-P1-LT | Genset Control 433

Configuration
Configure Monitoring > Miscellaneous > Operating Range Failure

n Check 6: The easYgen wants close the GGB, but the gener‐
ator minimum power is not reached.
n Check 7: The easYgen wants close the GGB in the Open
Transition Mode, but the generator minimum power is not
reached.
n Check 8: The easYgen wants synchronize the GGB , but the
generator minimum power is not reached.
n Check 9: (GGB control mode) The MCB or the GGB is closed
with min. one neighbor GCB is closed to the busbar. There is a
conflict, the external voltage monitoring of the Load Busbar sig‐
nals a "Dead load busbar", which cannot be the case.
n Check 10: The easYgen wants synchronize the GGB, the MCB
is closed, but the mains is not in operating range
n Check 11: The easYgen checks the plausibility of generator
and busbar, if GCB is closed and the engine runs without run-
up synchronization, but he operating range of generator OR
busbar is not matched.
n Check 12: The easYgen checks the phase rotation of gener‐
ator, busbar, and mains and a synchronisation shall be exe‐
cuted, but the phase rotation of all systems does not match.
(Synchronisation is blocked.)

Regarding Check 9 and 10: The GGB application

mode GCB/GGB/L-MCB is tapping the Load
busbar via the internal mains measurement. There‐
fore the check 10 is made via the load busbar con‐
dition. So the "load busbar" -OK flag is created out
of the mains operation ranges.

No alarm will be issued in idle mode. This monitoring function is

disabled below firing speed.

NOTICE!
If load-dependent start/stop (refer to Ä Chapter
4.4.5.5 “Load Dependent Start/Stop (LDSS)”
on page 304) is enabled, this monitoring function
must be configured with a shutdown alarm class C,
D, E, or F) or disable load-dependent start/stop if
triggered to ensure that the next engine will be
started.

If this protective function is triggered, the display

indicates "Operat. range failed" /("Operating Range
failed") and the logical command variable "06.31"
will be enabled.

ID Parameter CL Setting range Description

[Default]

2660 Monitoring 2 [On] Monitoring of the operating range is carried out according to the following
parameters.

Off Monitoring is disabled.

2663 Delay 2 1 to 999 s If one of the above mentioned conditions for an operating range failure is ful‐
filled, an alarm will be issued. If the respective condition is not fulfilled any‐
[30 s] more before the delay time expires, the delay time will be reset.

434 easYgen-3400XT-P1/3500XT-P1/3500XT-P1-LT | Genset Control 37580C