UM AER 01 N 1GB
Table Of Contents
- CONTENTS
- 1. INTRODUCTION
- 2. INPUTS/OUTPUTS DESCRIPTION
- 3. ROOM AIR TEMPERATURE CONTROL
- 3.1. SUMMER/WINTER SWITCHING
- 3.2. UNIT ON/OFF
- 3.3. COMPRESSOR CONTROL
- 3.4. DEFROST MODE
- 3.5. MAIN FAN
- 3.6. TEMPERATURE-BASED FREECOOLING AND FREEHEATING CONTROL
- 3.7. THREE DAMPERS ECONOMIZER OPTION
- 3.8. Supply air temperature minimum limit
- 3.9. FRECO OPTION
- 3.10. THERMODYNAMIC RECOVERY OPTION - TRECO
- 3.11. AUXILIARY HEATING
- 3.12. Set point compensation
- 4. ROOM AIR QUALITY CONTROL
- 5. SMOKE DETECTOR
- 6. SCHEDULING
- 7. USER INTERFACE
- 8. ALARM MANAGEMENT
- 9. SERVICING (CAREL)
- 10. MENU DESCRIPTION (CAREL)
English
27SysAer
7.5. MULTI ROOFTOPS INSTALLATION
7.5.1. PRINCIPLE
7.5.1.1. SHAREDE DISPLAY
When an installation is composed of many units (in different zones/groups or not), it is possible to connect all
the Rooftops together and display each unit parameters using only one interface for the whole installation.
7.5.1.2. MASTER/SLAVE
Keeping the unique display, it is also possible to congure the network in Master/Slave. In that case, the rst
unit (with address 1) is considered as the Master and all the other units (with address from 2 to 31) are the
Slaves. The aim is to have all the units running in the same way. The master sends ON/OFF, Summer/Winter,
active setpoint, Hour/Date, unoccupied mode and Economizer minimum opening to the connected slaves.
All the other parameters have to be congured on each unit. One of the advantages is to t only one clock
board in the master unit and send the hour and the date via the network to the slaves (also available in the
Shared Display conguration).
Via the Service menu on the master unit, several parameters must be congured for the PLAN,. There is
nothing to congure on the slaves concerning the PLAN:
² PLAN network enabling (for Shared Display also): If No, the alarms in relation with the PLAN are not
generated any more. But the PLAN for the Shared Display is still available (with the slaves units that
are connected). In the Master/Slave conguration, the master stops sending the data to the slaves
and the units congured as PLAN slaves run in stand-alone. To have a unit running as stand-alone
or master, its PLAN address must be 1. If the PLAN is enabled, PLAN alarms can be generated and in
the Master/Slave conguration, the slaves always run with the data sent by the master unit.
IMPORTANT: If a unit congured as PLAN slave is disconnected before conguring it as stand-alone
or if the PLAN network fails, the slave unit(s) will continue to run as slave with the last data sent by
the master unit.
² Number of units connected (for Shared Display also): From 2 to 31. It is strongly recommended to set
the units address by increasing order and not let a missing address. If 20 units are to be connected,
the addresses must be set from 1 (for the master) to 20.
² PLAN conguration: Display only (Shared Display) or Master/Slave
² PLAN units activation: To run as slave, the units must be activated. If a unit has to be shut down or
disconnected from the PLAN, it must be deactivated. Otherwise, an alarm will appear on the master
and the slave to signal a PLAN failure. Moreover, the slave unit will continue to run with the last sent
data.
² PLAN units conguration: If the network is congured in Master/Slave, the connected units with the
addresses from 2 to 31 can be separately congured as Display only (stand-alone with the shared
display) or as slave.
NB: If a unit is not detected any more by the master, a PLAN failure alarm is displayed on the master. To
know which unit(s) is disconnected, have a look at M6 and M7 (main screens) where the units that are
connected are displayed.
The principle is to connect all the units in parallel via one PLAN bus, using the J11 plug of the controller,
while the graphic interface is connected to one of the units (preferably the one with the address 1) using
the J10 plug.