Electronic Control; Client And Server Controllers - Trane Manhattan Gen II Installation, Operation And Maintenance Manual

Module Electrical and Control Panel
Each module has its own electrical and control panel that
distributes electricity to individual components. It also has
Figure 7. Module electrical and control panel

Electronic Control

Manhattan™ Gen II Air-Cooled Modular Chiller models
use Carel c.pCO series microprocessor controllers to
monitor and report critical operating parameters. See
Figure 9, p. 24.
A client controller is used to control and coordinate the
functioning of all the modules that make up the chiller unit.
For units consisting of more than a single chiller, each
module has its own controller.
There are five BMS communication options:
Note: BMS is not included as standard, but available as
an option.
1. BACnet® MS/TP - Connection through built-in BMS2
port
2. BACnet IP - BACnet router is used.
3. Modbus™ RTU - Connection through built-in BMS2
port.
4. Modbus IP - Modbus router is used
5. LonWorks® - LonWorks router is used
ARTC-SVX002A-EN
fuses and breakers, compressor switches, and the
microprocessor controller. See below figure.

Client and Server Controllers

The distributed microprocessor control system enables all
server modules to operate independently in the event that
the client microprocessor controller fails. All chiller
safeties including temperature set point, refrigerant
pressures, and freeze protection are preserved. The
distributed microprocessor control programming only
lacks the ability to rotate the lead compressors which
typically occurs every 168 compressor operating hours.
In a normal configuration, a server controller controls the
single module to which it is dedicated.
The server controller monitors key performance
parameters for its module and sends real-time
information to the client controller. The client controller
monitors the performance of the chiller, activating and
deactivating modules as needed to maintain the leaving
water temperature for the chiller.
(See Figure 8, p. 24 for a simplified example of a typical
microprocessor controller network.)
Operating Procedures
23