Daikin McQuay ED 15117 User manual

Engineering Data ED 15117
Group: Controls
Part Number: ED 15117
Date: April 2010
Supersedes: New
MagnitudeTM Chiller Unit Controller
Protocol Information
BACnet®Networks (MS/TP, IP, Ethernet)
LONWORKS®Networks
Daikin McQuay Magnitude™Magnetic Bearing Centrifugal Chiller, Single-
Compressor Model WME
© 2010 McQuay International

2 ED 15117
Table of Contents
BACnet®Networks (MS/TP, IP, Ethernet)
LONWORKS®Networks .............................. 1
Table of Contents ..................................... 2
REVISION HISTORY ........................................4
SOFTWARE REVISION .....................................4
REFERENCE DOCUMENTS...............................4
NOTICE...........................................................4
LIMITED WARRANTY .....................................4
Introduction ............................................... 5
UNIT CONTROLLER DATA POINTS..................5
PROTOCOL DEFINITIONS.................................5
Basic Protocol Information ........................ 6
SETTING UNIT CONTROLLER
COMMUNICATIONS PARAMETERS...................6
BACNET NETWORKS .....................................6
MAGNITUDE CHILLER UNIT CONTROLLER
DEVICE OBJECT..............................................8
Network Considerations.......................... 11
ACCESS TO PROPERTIES ...............................11
BACNET NETWORKS ...................................11
BACNET DEVICE MANAGEMENT.................13
Configuring the Unit Controller................ 15
LONWORKS NETWORKS...............................15
Typical Application: Minimum Integration 20
SET UP THE UNIT CONTROLLER FOR NETWORK
CONTROL .....................................................20
DISPLAY IMPORTANT DATA POINTS.............20
ALARMS.......................................................21
Protocol Point Summary - BACnet.......... 22
Protocol Point Summary - LONWORKS .... 25
NETWORK OUTPUT VARIABLES ...................25
NETWORK INPUT VARIABLES.......................26
NETWORK CONFIGURATION PARAMETERS...27
Detailed Data Point Information .............. 28
ACTIVE SETPOINT ........................................28
ACTUAL CAPACITY ......................................28
ALARM DIGITAL OUTPUT.............................29
APPLICATION VERSION ................................29
CAPACITY LIMIT ..........................................29
ACTIVE CAPACITY LIMIT OUTPUT ...............30
CAPACITY LIMIT SETPOINT -NETWORK.......30
CHILLER ENABLE.........................................31
CHILLER ENABLE OUTPUT ...........................31
CHILLER ENABLE SETPOINT.........................32
CHILLER CAPACITY LIMITED .......................32
CHILLER LOCAL/NETWORK .........................34
CHILLER LOCATION .....................................34
CHILLER MODE............................................35
CHILLER MODE OUTPUT..............................35
CHILLER MODE SETPOINT -NETWORK ........36
CHILLER MODEL..........................................36
CHILLER ON OFF..........................................36
CHILLER STATUS .........................................37
CLEAR ALARM NETWORK............................38
COMPRESSOR AVERAGE CURRENT ..............40
COMPRESSOR AVERAGE VOLTAGE ..............40
COMPRESSOR DISCHARGE REFRIGERANT
PRESSURE.....................................................40
COMPRESSOR DISCHARGE REFRIGERANT
TEMPERATURE .............................................41
COMPRESSOR DISCHARGE SATURATED
REFRIGERANT TEMPERATURE......................41
COMPRESSOR PERCENT RLA.......................42
COMPRESSOR POWER...................................42
COMPRESSOR RUN HOURS...........................42
COMPRESSOR SELECT ..................................43
COMPRESSOR STARTS ..................................43
COMPRESSOR SUCTION SATURATED
REFRIGERANT TEMPERATURE......................44
COMPRESSOR SUCTION REFRIGERANT
PRESSURE.....................................................44
COMPRESSOR SUCTION REFRIGERANT
TEMPERATURE .............................................45
CONDENSER ENTERING WATER
TEMPERATURE .............................................45
CONDENSER FLOW SWITCH STATUS ............45
CONDENSER LEAVING WATER TEMPERATURE
.....................................................................46
CONDENSER PUMP RUN HOURS ...................46
CONDENSER REFRIGERANT PRESSURE.........47
CONDENSER SATURATED REFRIGERANT
TEMPERATURE .............................................47
CONDENSER WATER FLOW RATE ................47
CONDENSER PUMP STATUS..........................48
COOL SETPOINT -NETWORK........................49
COOL SETPOINT ...........................................49
CURRENT DATE &TIME...............................49
DEFAULT VALUES........................................50
EVAPORATOR ENTERING WATER
TEMPERATURE .............................................50
EVAPORATOR FLOW SWITCH STATUS..........50

ED15117 3
EVAPORATOR LEAVING WATER
TEMPERATURE .............................................51
EVAPORATOR PUMP RUN HOURS .................52
EVAPORATOR PUMP STATUS........................52
EVAPORATOR WATER FLOW RATE ..............53
FILE DIRECTORY ADDRESS ..........................53
HEAT RECOVERY ENTERING WATER
TEMPERATURE .............................................53
HEAT RECOVERY LEAVING WATER
TEMPERATURE .............................................54
HEAT SETPOINT -NETWORK ........................54
HEAT SETPOINT............................................55
ICE SETPOINT -NETWORK............................55
ICE SETPOINT ...............................................55
MAXIMUM SEND TIME .................................56
MINIMUM SEND TIME ..................................56
OBJECT STATUS ...........................................57
OBJECT REQUEST.........................................58
OUTDOOR AIR TEMPERATURE......................59
PUMP SELECT...............................................59
RECEIVE HEARTBEAT...................................60
RUN ENABLED..............................................60
SOFTWARE IDENTIFICATION (MAJOR
VERSION) .....................................................61
SOFTWARE IDENTIFICATION (MINOR VERSION)
.....................................................................61
UNITS...........................................................61
Alarms-BACnet........................................63
ALARM CLASSES..........................................63
BACNET ALARM HANDLING .......................63
Clearing Alarms-BACnet .........................65
BACNET ALARM MESSAGES .......................65
Alarms-LONWORKS ..................................67
CURRENT ALARM.........................................67
Clearing Alarms - LONWORKS ..................68
LONWORKS ALARM MESSAGES...................68
Appendix A: Protocol Implementation
Conformance Statement (PICS)..............70
BACNET PROTOCOL IMPLEMENTATION
CONFORMANCE STATEMENT........................70
PRODUCT DESCRIPTION................................70
BACNET STANDARDIZED DEVICE PROFILE..70
BACNET INTEROPERABILITY BUILDING
BLOCKS (BIBBS)SUPPORTED......................70
STANDARD OBJECT TYPES SUPPORTED........72
DATA LINK LAYER OPTIONS........................74
SEGMENTATION CAPABILITY .......................74
DEVICE ADDRESS BINDING..........................74
NETWORKING OPTIONS................................74
CHARACTER SETS SUPPORTED.....................74
NON-BACNET EQUIPMENT/NETWORK(S)
SUPPORT ......................................................74
Index of Detailed Point Information .........75

4 ED 15117
Revision History
ED15117 April 2010 Preliminary release.
Software Revision
This edition documents all versions of the standard Magnitude Chiller Unit Controller software and all
subsequent revisions until otherwise indicated. You can determine the revision of the application
software from the display. The version is located on the Service screen. BACnet can also read the
software revision by reading the Application_Software_Version property of the Device Object.
Reference Documents
Company Number Title Source
McQuay International OM 1034 MagnitudeFrictionless Centrifugal Chiller Operation and
Maintenance Manual www.mcquay.com
McQuay International IM 963 Magnitude Frictionless Centrifugal Chiller, BACnet
Communication Module (MSTP, IP/Ethernet) Installation
Manual www.mcquay.com
McQuay International IM 965 Magnitude Frictionless Centrifugal Chiller, LONWORKS
Communication Module Installation Manual www.mcquay.com
American Society of
Heating, Refrigerating and
Air-Conditioning Engineers
ANSI/
ASHRAE 135-
2004
BACnet® A Data Communication Protocol for Building
Automation and Control Networks www.ashrae.org
LonMark Interoperability
Association
078-0120-01G LonMark® Layers 1-6 Interoperability Guidelines, Version 3.4 www.lonmark.org
LonMark Interoperability
Association 078-0120-01G LonMark Application Layer Interoperability Guidelines, Version 3.4 www.lonmark.org
LonMark Interoperability
Association 8040_10 LonMark Functional Profile: Chiller, Version 1.0 www.lonmark.org
Echelon Corporation 078-0156-01G LONWORKS FTT-10A Free Topology Transceiver Users Guide www.echelon.com
Notice
© 2010 McQuay International, Minneapolis MN. All rights reserved throughout the world
McQuay International reserves the right to change any information contained herein without prior
notice. The user is responsible for determining whether this product is appropriate for his or her
application.
The following are trademarks or registered trademarks of their respective companies: BACnet
from American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. Echelon,
LONWORKS, LONMARK, and LonTalk from Echelon Corporation, Windows from Microsoft
Corporation, and McQuay, Daikin McQuay, and Magnitude from McQuay International.
Limited Warranty
Consult your local McQuay Representative for warranty details. Refer to Form 933-430285Y. To find
your local McQuay Representative, go to www.mcquay.com.

ED15117 5
Introduction
This document contains the necessary information you need to incorporate a Daikin McQuay
Magnitude™ Chiller Unit Controller into a building automation system (BAS). It lists all BACnet®
properties, LONWORKS®variables, and corresponding Magnitude Chiller Unit Controller data points. It
also contains the BACnet Protocol Implementation Conformance Statement (PICS). BACnet and
LONWORKS terms are not defined. Refer to the respective specifications for definitions and details.
Unit Controller Data Points
The Magnitude Chiller Unit Controller contains data points or unit variables that are accessible from
three user interfaces: the unit controller OITS panel, a BACnet network (BACnet/IP, Ethernet, or
MS/TP), or a LONWORKS network. Not all points are accessible from each interface. This manual lists
all important data points and the corresponding path for each applicable interface. Refer to OM 1034
(available on www.mcquay.com) for display details. This document contains the network details
necessary to incorporate the Magnitude Chiller Unit Controller into the network.
Protocol Definitions
The Magnitude Chiller Unit Controller can be configured in either an interoperable BACnet or
LONWORKS network. The unit controller must have the corresponding communication module installed
for network integration (see Reference Document section for corresponding part numbers). There are
three communication modules: BACnet IP/Ethernet, BACnet MS/TP (Master/Slave Token Passing),
and LONWORKS.
BACnet Protocol
BACnet is a standard communication protocol for Building Automation and Control Networks
developed by the American National Standards Institute (ANSI) and American Society of Heating,
Refrigeration and Air-conditioning Engineers (ASHRAE) specified in ANSI/ASHRAE standard 135-
2004. It addresses all aspects of the various systems that are applied to building control systems.
BACnet provides the communication infrastructure needed to integrate products manufactured by
different vendors and to integrate building services that are now independent.
The Magnitude Chiller Unit Controller is tested according to the BACnet Testing Laboratory (BTL)
Test Plan. It is designed to meet the requirements of the BACnet Standard (ANSI/ASHRAE 135-2004)
as stated in the Protocol Implementation and Conformance Statement (PICS). However, it is not BTL
listed. The PICS are located at the end of this manual or the separate PICS document, ED 15119
(available on www.mcquay.com.)
LONWORKS Networks
A control network specification for information exchange built upon the use of the LonTalk®protocol
for transmitting data developed by the Echelon®Corporation.
LonTalk Protocol
A protocol developed and owned by the Echelon Corporation. It describes how information should be
transmitted between devices on a control network.
LonMark®Certification
LonMark certification is an official acknowledgement by the LonMark Interoperability Association that
a product communicates using the LonTalk protocol and transmits and receives data per a standard
LonMark functional profile. The LONWORKS communication module is LonMark 3.4 certified in
accordance with the Chiller functional profile.

6 ED 15117
Basic Protocol Information
Setting Unit Controller Communications Parameters
There are 12 communication parameters involved in setting up the unit controller for proper
communication with the three communication module options (BACnet IP/Ethernet, BACnet MS/TP,
LONWORKS). These parameters are set differently depending on which communication module is
ordered and shipped with the unit. The table below lists the three possible sets of default parameter
settings. Not all the parameters apply to all the module options. All parameters, except for Receive
Heartbeat, are configurable via the unit controller display. The boldface settings can only be
configured via the unit controller OITS (Operator Interface Touch Screen). See Magnitude
Chiller Unit Controller Operation Manual, OM 1034, for details. The items in parenthesis indicate
whether the parameter is Read-Only (R) or Read/Write (W) from the BACnet network.
Communication Parameter Settings
Parameter Name BACnet IP BACnet MS/TP BACnet Ethernet LONWORKS
IP Address 172.15.5.82N/A N/A N/A
IP Subnet Mask 255.255.255.0 N/A N/A N/A
Default Gateway
Address “None” N/A N/A N/A
UDP Port 47808 N/A N/A N/A
MSTP MAC Address N/A 1 N/A N/A
MSTP Baud Rate N/A 38400 N/A N/A
Device Instance Number
(W) 3000330003N/A N/A
Max APDU Length (R) 1024 480 1476 N/A
Device Object Name (W) Magnitude3Magnitude3Magnitude3N/A
Max Master (W) N/A 127 N/A N/A
Max Info Frames (W) N/A 5 N/A N/A
APDU Retries (W) 3 3 N/A N/A
APDU Timeout (W) 3000 3000 N/A N/A
Receive Heartbeat1N/A N/A N/A 0Sec
1. All parameters, except for Receive Heartbeat, are configurable via the OITS panel.
2. If the IP Address is set to 0.0.0.0 from the unit controller OITS panel or through the network,
DHCP addressing will be enabled and the IP address will be requested from the network DHCP
server.
3. Device value must be unique on the BACnet network.
BACnet Networks
Compatibility
The Magnitude Chiller Unit Controller is tested according to the BACnet Testing Laboratory (BTL)
Test Plan. It is designed to meet the requirements of the BACnet Standard (ANSI/ASHRAE 135-2004)
as stated in the Protocol Implementation and Conformance Statement (PICS). However, it is not BTL
listed. The PICS is located at the end of this manual or the separate PICS document, ED 15119
(available on www.mcquay.com.)
BACnet Objects
Magnitude Chiller Unit Controllers incorporate standard BACnet object types (i.e., object types defined
in the BACnet Standard) that conform to the BACnet Standard. Each object has properties that control
unit variables or data points. Some object types occur more than once in the Magnitude Chiller Unit
Controller; each occurrence or instance has different properties and controls different unit variables or
data points. Each instance is designated with a unique instance index. Some properties can be adjusted

ED15117 7
(read/write properties, e.g., setpoints) from the network and others can only be interrogated (read-only
properties, e.g., status information).
Each data point accessible from a BACnet network is described with a table that gives the Object
Identifier, Property Identifier, Full BACnet Reference or path, and the Name enumeration of the
property.
Example of BACnet Data Point
Object Identifier Property Identifier
Object Type Type Enumeration Instance Property Name Property Enumeration
Binary Output 4 5 Present Value 85
Object Name
AlarmDigitalOutput
Property Values
0 = No Alarm
1 = Alarm
Object Identifier
Object Identifiers are each designated with an Object type as defined in the BACnet specification. The
first column of the data point definition gives the object type. This object happens to be Alarm Digital
Output. The object identifier is a property of the object that you can read from the object. The name of
the property is “Object_Identifier” and the property identifier is 75.
Each object in the unit controller has a unique identifier. BACnet object identifiers are two-part
numbers of BACnet Object Identifier data type. The first part identifies the object type (the first 10 bits
of the 32-bit BACnet Object Identifier [See ANSI/ASHRAE 135-2004 BACnet A Data
Communication Protocol for Building Automation and Control Networks]). The first column of the
data point definition gives the object type. The second part identifies the instances of that particular
object type (the last 22 bits of the 32-bit BACnet Object Identifier).
The object identifier is shown in the data points listing as two numbers. The first number is shown in
the Type ID column and designates the Object type enumeration. The second number is shown in the
Instance column and designates the instance of that particular object type.
The object identifier is a property of the object that you can read from the object code. The name of the
property is “Object_Identifier” and the property identifier is 75. The ASHRAE BACnet specification
reserves the first 128 numbers for ASHRAE defined objects. Manufacturers may define additional
object types and assign a number above 127 as long as they conform to the requirements of the
ASHRAE BACnet specification.
Each object also has a name. Object Names are character strings. The object name is a property of the
object that you can read from the object. The name of the property is “Object_Name” and the property
identifier is 77.
Objects are sometimes referred to as an Object Type and Instance Number as they are in the BACnet
specification. The example object above would be: Binary Output, Instance 5.
Property Identifier
Each object has a number of properties or attributes. Each property has a unique identifier of BACnet
Property Identifier data type. Property identifiers are an enumerated set; a number identifies each
member. The Property Identifier enumeration number is shown in the Property ID column. In the
example above the property identifier is 85.

Property Name
Each property also has a unique name. Property names are character strings and shown in the Property
Name column. In the example above the property name is Present Value.
Object Name
The Object Name is the name of the object in the device. Object Names must be unique within each
BACnet device. In the example above the object name is AlarmDigitalOutput.
Enumerated Values
Some properties are standard data types and some are enumerated sets. If the property value is an
enumerated set, all enumerated values and corresponding meaning are given in the Enumeration
column of the data point listing.
Magnitude Chiller Unit Controller Device Object
Each BACnet-compatible device can only have a single BACnet Device Object.
Device Object Identifier
The Magnitude Chiller Unit Controller Device Object Identifier uniquely specifies the unit within the
network. The device object type for all devices is fixed by ASHRAE at 8. Therefore the device object
instance number must be unique. The device object instance will be read from a parameter in the
Magnitude Chiller Unit Controller during the BACnet communication module’s initialization phase.
The BACnet communication module continues to poll the device object instance parameter during run-
time. If the device object instance is changed at the controller during run-time, the update will be
automatically applied to the BACnet communication module as soon as the change is received. The
allowable range of values for the device object instance will be 0 to 4194302. (The value 4194303 is
reserved by BTL for reading a device’s object id.) If a value greater than 4194302 is read from the
controller, the following default value will be used:
Default device object instance: 3000 + address*
*Address = the last two octets of the MAC Address
For example:
BACnet MS/TP: 3023
BACnet Ethernet: 10312 (3000 + F75A)
BACnet/IP: CDB (3000 + 0123)
The device object identifier can be read from the unit controller. The name of the property is
“Object_Identifier” and the property identifier is 75. Changing the device object ID may affect the
operation of other BACnet devices on the network that have previously discovered the device. The
object instance number can be changed via the unit controller OITS panel.
!CAUTION
If another device in the network already has this object identifier (instance number), you must change the instance number of one
device object, so that all devices in the network have a unique device identifier.
Device Object Name
The Device Object Name uniquely specifies a device in the network. It must be unique in the network.
The device object name will be read from a parameter in the Magnitude Chiller Unit Controller during
the BACnet communication module’s initialization phase. The BACnet communication module
continues to poll the device object name parameter during run-time. If the device object name is
changed at the controller during runtime, the update will be automatically applied to the BACnet
8 ED 15117

ED15117 9
communication module as soon as the change is received. The allowable range of characters for the
device object name will be 1 to 31 characters. If an empty string is read from the controller, the
following default name will be used:
Default device object name: MTE Chiller UCA - address*
*Address = the MAC Address
For example:
BACnet MS/TP: MTE Chiller UCA-23
BACnet Ethernet and BACnet/IP: MTE Chiller UCA-0-176-208-13-247-90
Note: If the constructed name is longer than 31 characters, the numeric portion of the name will be
shortened to fit the name into the 31 character limit.
The Device Object name is also available to the network in the device. The property name is
“Object_Name” and property identifier is 77. Changing the device object name may affect the
operation of other BACnet devices on the network that have previously discovered the device. The
object name can be changed via the unit controller OITS panel.
Device Object Properties
The device object contains many other informative properties as shown in Table 1. Items in bold are
configurable via the BACnet network.
Table 1. Magnitude Chiller Unit Controller Device Object Properties
Property Identifier Default Value Data Type
Object Identifier 75 Device, variable BACnetObjectIdentifier
Object Name 77 Magnitude Character String
Object Type 79 8 BACnetObjectType
System Status 112 BACnetDeviceStatus
Vendor Name 121 McQuay International Character String
Vendor Identifier 120 3 Unsigned 16
Model Name 70 WME Character String
Firmware Revision 44 variable Character String
Application Software Version 12 variable Character String
Location 58 Character String
Description 28 McQuay Chiller Character String
Protocol Version 98 1 Unsigned
Protocol Revision 139 4 Unsigned
Protocol Services Supported 97 readProperty, readPropertyMultiple,
writeProperty,
writePropertyMultiple,
deviceCommunicationControl,
timeSynchronization, who-Has,
who-Is, utcTimeSyncronization,
BACnetServicesSupported

10 ED 15117
Property Identifier Default Value Data Type
reinitializeDevice
Protocol Object Types Supported196 AI, AO, AV, BI, BO, BV, Device,
MSI, MSO, MSV
BACnetObjectTypesSupported
Object List 76 Sequence of BACnetObjectIdentifer
Max APDU Length Accepted 62 1024 (IP) / 480 (MS/TP) Unsigned 16
Segmentation Supported 107 None BACnetSegmentation
APDU Timeout 11 3000 Unsigned
Number of APDU Retries 73 3 Unsigned
Max Master 64 127 (Range: 1 .. 127) Unsigned
Max Info Frames 63 5 (Range: 1.. 5) Unsigned
Device Address Binding 30 Sequence of BACnetAddressBinding
Database Revision 115 1 Unsigned
Local Time257 variable (read from the controller) Time
Local Date256 variable (read from the controller) Date
UTC Offset 119 0 (Range: –720 .. 720) Integer
Daylight Savings Status 24 0 (False) Boolean
1. While the Magnitude Chiller Unit Controller supports all shown object types, not all object types are used. See the Object List for
details.
2. The device properties will be read-only. The controller values are writable from BACnet via the BACnet TimeSynchronization
services.