EasyManua.ls Logo

AERMEC Multichiller-Evo - Installer - Thresholds & Timings: Chiller On;Off Management

AERMEC Multichiller-Evo
44 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
27
INSTALLER - Thresholds and mings - Chiller On/O management
A
B
C

Index Meaning
1
Indicates which logic will be used to control the ignition commands compared to the power de-
mand by the system; these logics can be:
All chillers on = when the Multichiller-Evo gives the On command, all system chillers will be set to
On (observing the “Next On delay timing specied on the next page), while the chillers will be set
to O (observing the “Next O delay with multichiller O” specied on the next page) once O has
been set by the Multichiller-Evo;
Fixed thresholds = this logic involves the ignition of the rst chiller together with the Multichiller-
Evo; the thermostats of the remaining chillers will be subsequently controlled and when the average
power demand will be higher than the “partialisation On %” (specied on the next page) for longer
than the “Next On delay (again, available on the next page), then an additional chiller will be set to
On (choosing the one that worked less hours) and so forth... similar logic will be used (in the opposi-
te direction) to calculate the chiller switch-o;
Optimiser 1 = during the Multichiller-Evo commissioning, the loading is met using the xed
threshold logic; then this logic manages the chiller ignitions based on an algorithm that veries the
systems power demand and its stability over time. If the power demand is stable, the best combi-
nation will be calculated between the available chillers (which can be activated with partialisations
dierent from each other) to provide for the demand itself (in this way the hours worked by each
chiller will not be taken into account);
Optimiser 2 = during the Multichiller-Evo commissioning, the loading is met using the xed
threshold logic; then this logic follows the same algorithm as above, however, in this case, the calcu-
lated combination will operate the selected chillers with the same partialisation steps;
2
Indicates whether to use one of the chillers as monitor for the system’s power demand; in this case,
the chiller will always remain on and the Multichiller-Evo uses its thermostat to establish the power
demand; if you select “NO, the Multichiller-Evo will use one of the probes connected to the pCOe
expansion board (according to the one selected for the “System re-start”) to establish the threshold
below which to start the rst chiller
3
Indicates which threshold, connected to the pCOe expansion board, will be used to read the tempe-
rature below which to consent to start the rst chiller (system side)
4
Indicates which threshold, connected to the pCOe expansion board, will be used to read the tempe-
rature below which to consent to start the rst chiller (recovery side)
ACTIONS
AVAILABLE:
1
A B C
2
3
4


D
E
F
G
D
        

E


F



G



REMEMBER THAT:
OPTIMISATION 1 and OPTIMISATION 2 mulchiller management is not availa-
ble with mulpurpose machines

Table of Contents

Related product manuals