ComAp InteliMains NT IM-NT, Справочное руководство

Страница: 87 / 437

InteliMains
NT
, SW version 3.2.0
InteliMains-NT-MCB-MGCB-3.2.0-Reference Guide.pdf,
©ComAp – April 2015
87
7.6.3.2 Load demand swap (LDS)
– different sized engines
If there are gen-sets of different size at the site, it may be required always to run such gen-sets that
best fit to the actual load demand. The
Load demand swap function is intended for this purpose and
can control up to 3 gen-sets (priorities). Up to three running engines (priorities) can be swapped based
on lo
ad demand (e.g. one “small” engine may run on “small” load and swaps to another one, “big”
engine that runs when load increases). This function is available only in combination with absolute
power management .
Activation: Pwr management: #PriorAutoSwap = LD DEMAND SWAP
Important setpoints: #PwrBandContr1 , #PwrBandContr2 , #PwrBandContr3, #PwrBandContr4 ,
#PwrBandChngDlUp, #PwrBandChngDlDn, Load reserve setpoints (depending on selected load
reserve set), Priority ctrl, Control group.
The gen-sets must have addresses 1, 2 and 3. There are four power bands; each of them has
adjusted specific combination of gen-sets that run within it. Power bands are adjusted by setpoints
#PwrBandContr1, #PwrBandContr2, #PwrBandContr3 and #PwrBandContr4 . The load levels of
the power bands are defined by sum of nominal powers of gen-sets that are adjusted to run in each
particular power band, and the load reserve for start. The combinations of gen-sets must be created in
the way the total nominal power of the Power band #1 < #2 < #3 < #4. If the load demand is above the
power band #4 then all gen-sets are ordered to run. In fact there is power band #5, which has fixedly
selected all the gen-sets to run.
The currently active power band is given by the actual load demand. If the load demand changes and
gets out from the current power band, the next/previous power band is activated with delay
Pwr management: #PwrBnChngDlUp or Pwr management: #PwrBnChngDlDn depending on
the direction of the change. The gen-sets which are included in the current power band get engine
priority 1, the others get priority 32. The setpoint
Pwr management: Priority is not influenced by this
function.
Virtual values “engine priority” are used.
N
OTE
:
If the power band change delays (i.e. Pwr management: #PwrBnChngDlUp and
Pwr management: #PwrBnChngDlDn ) are adjusted to higher values than
Pwr management: #NextStrt del and Pwr management: #OverldNextDel setpoints then it may occur,
that also the gen-sets not belonging to the current power band will start. This is normal and it prevents
the system from overloading. Priority setpoints are not actually changed. Virtual values “engine
priority” are used.