21
11UNT-PRC002-GB
Sound power levels
Discharge
Measurement conditions:
Measurements taken in a room adjacent to the room containing the FWD, at the outlet of the rectangular duct (1.5 m
long) fixed to its discharge opening.
Fan Power level in dB(A), per Hz frequency band Overall power
Unit speed 125 250 500 1000 2000 4000 8000 dB(A)
1 55 50 42 37 37 31 30 46
FWD 08 2 57 54 47 40 30 38 40 50
3 58 57 50 42 32 40 43 53
1 57 51 45 42 34 33 28 48
FWD 10 2 58 54 48 45 38 39 35 51
3 60 58 50 48 40 42 39 54
1 57 51 45 42 34 33 28 48
FWD 12 2 58 54 48 45 38 39 35 51
3 60 58 50 48 40 42 39 54
1 56 62 50 48 39 38 36 56
FWD 14 2 61 66 55 53 47 46 45 60
3 63 69 58 56 50 50 49 63
1 57 63 51 49 40 39 37 57
FWD 20 2 61 66 55 53 47 46 45 60
3 63 69 58 56 50 50 49 63
Intake
Measurement conditions:
Measurements taken at the horizontal air intake.
Fan Power level in dB(A), per Hz frequency band Overall power
Unit speed 125 250 500 1000 2000 4000 8000 dB(A)
1 56 55 55 53 46 45 42 57
FWD 08 2 63 62 60 60 53 53 53 64
3 66 65 63 62 56 55 57 67
1 62 58 55 58 51 48 44 61
FWD 10 2 66 63 60 62 56 55 52 66
3 70 67 63 65 59 59 57 69
1 62 58 55 58 51 48 44 61
FWD 12 2 66 63 60 62 56 55 52 66
3 70 67 63 65 59 59 57 69
1 66 65 65 65 57 50 46 68
FWD 14 2 73 72 69 71 64 59 57 74
3 78 76 73 75 69 64 63 78
1 68 72 64 64 56 52 50 69
FWD 20 2 76 76 68 71 65 61 61 75
3 78 79 71 74 69 66 66 78
CG-SVU010C-GB
LonTalk™ Interface (LCI-C)
UC800 provides an optional LonTalk™ Smart Com Protocol (LCI-C) between the chiller and a Building Automation
System (BAS). An LCI-C LLID shall be used to provide “gateway” functionality between a LonTalk compatible device
and the Chiller. The inputs/outputs include both mandatory and optional network variables as established by the
LonMark Functional Chiller Profile 8040. See integration guide for detailed information.
BACnet Interface (BCNT)
The Building Automation and Control Network (BACnet and ANSI/ASHRAE Standard 135-2004) protocol is a standard
that allows building automation systems or components from different manufacturers to share information and
control functions. BACnet provides building owners the capability to connect various types of building control
systems or subsystems together for a variety of reasons. In addition, multiple vendors can use this protocol
to share information for monitoring and supervisory control between systems and devices in a multi-vendor
interconnected system. The BACnet interface identifies standard objects (data points) called BACnet objects. Each
object has a defined list of properties that provide information about that object. BACnet also defines a number of
standard application services that are used to access data and manipulate these objects and provides a client/server
communication between devices. See integration guide for detailed information.
BACnet Testing Laboratory (BTL) Certification
All Tracer™ UC800 controllers are designed to support BACnet Smart Com Protocol. In addition, some particular
revisions of the UC800 firmware have been tested and have achieved BTL certification by an official BACnet testing
laboratory.
For more details, refer to the BTL website at www.bacnetassociation.org.
ModBus RTU Interface
Modicon Communication Bus (Modbus) is an application layer-messaging protocol that, like BACnet, provides
client/server communication between devices over a variety of networks. During communications on a Modbus RTU
network, the protocol determines how each controller will know its device address, recognize a message addressed
to its device, determine what action to take, and extract any data or other information contained in the message.
Controllers communicate using a master/slave technique, whereby, only one device (master) can initiate transactions
(queries). Other devices (slaves) respond by supplying the requested data to the master or by taking the action
requested in the query.
The master can address individual slaves or it can initiate a broadcast message to all slaves. In turn, the slaves
respond to queries that are addressed to them individually or broadcasted. The Modbus RTU Interface establishes
the format for the master’s query by placing into it the device address, a function code defining the requested action,
any data to be sent, and an error-checking field. See integration guide for detailed information.
Smart Communication Protocol
To Next Page
Loading...