Integration Manual Trane Communicating Thermostats (BACnet) Building Automation System SAFETY WARNING Only qualified personnel should install and service the equipment. The installation, starting up, and servicing of heating, ventilating, and air-conditioning equipment can be hazardous and requires specific knowledge and training. Improperly installed, adjusted or altered equipment by an unqualified person could result in death or serious injury.
Copyright © 2011 Trane All rights reserved This document and the information in it are the property of Trane and may not be used or reproduced in whole or in part, without the written permission of Trane. Trane reserves the right to revise this publication at any time and to make changes to its content without obligation to notify any person of such revision or change. Trademarks Trane and its logo are trademarks of Trane in the United States and other countries.
Table of Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Planning Your Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objects and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Tracer SC Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Data Normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Example: Occupancy Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Template: TStat_FanCoil_Trane . . . . . . . . . . . . . . . .
Overview This document is written to guide you through integration of the Trane Communicating Thermostats into an MS/TP network using the BACnet protocol and managed by a Tracer SC. Product Description The Trane Communicating Thermostats are available for heat pump, rooftop, and fan coil applications.
Overview Related Documents See the following documents for Communicating Thermostat installation and configuration information. • Trane Communicating Thermostats for Heat Pump Control User Guide (BAS-SVU10x-EN) • Trane Communicating Thermostats for Rooftop Control User Guide (BAS-SVU11x-EN) • Trane Communicating Thermostats for Fan Coil Control User Guide (BAS-SVU12x-EN) See the following documents for Tracer SC network integration information.
Summary of BACnet Objects 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 many uses.
Summary of BACnet Objects (X13511541010 and -2010) Rooftop and Heat Pump Models • Default Device ID is set to: 7600MAC where MAC is the current MAC address of the device. • The device ID and the Device Name change if you change the device’s MAC address. For example, when a heat pump communicating thermostat with a MAC address of 63 is connected to a network, its default Device Name will be TStat_HeatPump_Trane_63 and its default Device ID will be 760063. Fan Coil Objects Table 2.
Summary of BACnet Objects Table 2.
Summary of BACnet Objects Rooftop and Heat Pump Objects Table 3.
Summary of BACnet Objects Table 3.
Summary of BACnet Objects Table 3.
Summary of BACnet Objects c : Object_Name property is writable only for Room Temperature (AV7). d : Present_Value and Out_of_Service properties are writable for every MV objects except Heating Valve Status (MV26), Cooling Valve Status (MV27), Fan Status (MV28), and Effective Occupancy (MV33) Footnotes for rooftop units and heat pumps e: The following AV’s are defined as read only.
BACnet Object Properties This section lists ranges, enumerations, and values for the set of Communicating Thermostat objects. Fan Coil Object Properties Table 6. List of property value range restrictions Object Name Object Type and Instance Minimum Range Maximum Range Value Value Room Temperature AV 7 -39.9°F (-40°C) 121.9°F (50°C) N/A Outdoor Temperature AV 9 -39°F (-40°C) 121.9°F (50°C) N/A Default Value Room Humidity AV 10 5% 90% N/A Supply Temperature AI 12 -39.9°F (-40°C) 121.
BACnet Object Properties Table 7.
BACnet Object Properties Table 9. MV15 (Sequence of Operation) values for Note 2 Function Default Value is BV50 Enabled Default Value is BV50 Disabled 1 Cooling Only Cool Cool 2 Cooling with Reheat Auto Heat 3 Heating Only Heat Heat MV15 Index 4 Heating with Reheat Heat Heat 5 Cooling/Heating 4 Pipes Auto Heat 6 Cooling/Heating 4 Pipes with Reheat Auto Heat Table Notes: (continued) 3 Enumeration sets for MV17 depends on Fan Mode Sequence (MV58) value upon device discovery.
BACnet Object Properties 9 meration will now reflect required configuration. Available object name, state text and default value depends on Control Type (BV75) value and Pipe Number (MV52) upon device discovery. (See Table 12.) Table 12.
BACnet Object Properties Table 13.
BACnet Object Properties Table 13. Additional MV Values (continued) Object Name On-Off Control CPH Object ID MV 77 BACnet Index Text 1 3 CPH 2 4 CPH 3 5 CPH 4 6 CPH 5 7 CPH 6 8 CPH Default Value 4 CPH Rooftop and Heat Pump Object Properties Table 14.
BACnet Object Properties Table 14. List of property value range restrictions for AI and AV objects (continued) Object Name Humidifier Output Object Type and Instance AV 101 Under Range Value 0% Over Range Value 100% Default Value N/A Table 15.
BACnet Object Properties Table 16.
BACnet Object Properties Table 16. List of property enumeration sets for MV objects (continued) Object Name DI1 Configuration DI2 Configuration Proportional Band 22 Object Type and instance MV65 MV66 MV 67 Event Display MV71 Heating Stages MV73 Cooling Stages MV74 Heat Pump Stages MV75 BACnet Index Text 1 None 2 RemNSB 3 RemOVR 4 Filter 5 Service 6 Fan lock 1 None 2 RemNSB 3 RemOVR 4 Filter 5 Service 6 Fan lock 1 2 2F 0.6 C 2 3 3F 1.2 C 3 4 4F 1.
Objects You Can Use in Site Graphics Fan Coils You can use the following objects in site graphics: Room Temperature (AV7) Heating Valve Status (MV26) Occupied and Unoccupied Heat Setpoints (AV39 and AV43) Cooling Valve Status (MV28) Occupied and Unoccupied Cool Setpoints (AV40 and AV34) PI Heating Demand (AV21) Outdoor Temperature (AV9) PI Cooling Demand (AV22) Supply Temperature (AI12) (If available) Window Alarm (BI35) Occupancy Command (MV18) Filter Alarm (BI36) System Mode (MV16) Service Alarm
Objects You Can Use in Site Graphics Rooftop and Heat Pump Units You can use the following objects in site graphics: Room Temperature (AV7) W1 Heat (BI28) Occupied and Unoccupied Heat Setpoints (AV 42 and AV44) W2 Heat (BI29) or Reversing Valve (BI30) Occupied and Unoccupied Cool Setpoints (AV 43 and AV45) Economizer Output (AV22) (if available) Outdoor Temperature (AV9) Aux (BI24) Supply Temperature (AI16) (If available) DI 1 Status (BI31) Occupancy Command (MV12) DI 2 Status (BI 32) Effective
Wiring Requirements for Communicating Thermostats BACnet networks use a daisy chain configuration. A daisy chain means that there is only one main cable and every network device is connected directly along its path. Figure 2 illustrates two improper network configurations and the proper daisy chain configuration. Figure 2.
Wiring Requirements for Communicating Thermostats BACnet Wiring Procedure Follow these steps to connect communication wiring as shown in Figure 3, p. 26. 1. Attach the communication link wiring to the Tracer SC at Link 1 or Link 2. Note: It is not necessary to place the Tracer SC at the end of the of the communication link. 2. Attach the wiring from the first unit controller to the first set of communication terminals on the next unit controller.
Figure 4. Terminating BACnet links using BACnet terminators Product Specifications Specifications for Communicating Thermostats are as follows. Table 17.
Wiring Requirements for Communicating Thermostats Communicating Thermostat Status LEDs Table 18 shows the different possibilities with the Status LED behaviour for a BACnet module. Table 18.
Additional Information and Considerations This chapter explains some special tips and considerations that apply to the Trane Communicating Thermostats. These tips and considerations are grouped in the following categories: • MS/TP network integration • Objects and parameters • Tracer SC network configuration MS/TP Network Integration Before doing any BACnet integration, make sure to have Trane PICS (Protocol Implementation Conformance Statement).
Additional Information and Considerations Rooftop and Heat Pump Units Programs writing to the devices should have a structure similar to the following: If Once Schedule = On then MV11 = Occupied End If If Once Schedule = Off Then MV11 = Unoccupied End If OR Do Every 5min If Schedule = On Then MV11= Occupied Else MV11 = Unoccupied End If End Do Retries and Timeouts (Supervisory Controllers Other Than Tracer SC) Another thing to look for in a BACnet integration is the Device object of the Supervisory Cont
Additional Information and Considerations • If the device should go offline, the communicated value from the front-end Tracer SC will be released: – Room Temperature – Outdoor Temperature – Occupancy • Device Name and Device ID properties are writable in BACnet device object. Both properties can be renamed from any BACnet network management tool as long as the tool itself give access to write to these properties.
Additional Information and Considerations Tracer SC Network Configuration You should be aware of these important facts about Communicating Thermostat capabilities in the Tracer SC network. No automatic installation The Trane Communicating Thermostats do not automatically install on the Tracer SC. Custom templates are available and you can select one of these templates (“Template: TStat_RTU_Trane,” p. 40, “Template: TStat_FanCoil_Trane,” p. 36, or “Template: TStat_HeatPump_Trane,” p.
Additional Information and Considerations Figure 6. Area members page (actions > edit configuration) Heat only/cool only If the thermostat is configured as cool only, it will not accept its Heat Cool Mode Request to be controlled to any heating mode. The converse applies if the thermostat is configured for heat only, it will not accept its Heat Cool Mode Request to be controlled to any cooling mode. If the point is controlled to an invalid state, it will quickly revert to the previous state.
Additional Information and Considerations These properties are also shown but not populated on point status pages (Figure 8, p. 34 ). Figure 8. Status section of the Point Status page No active setpoint or heat/cool mode data The Spaces Summary and Equipment Summary pages do not show data for active setpoint or heat/ cool mode as these devices do not have Space Temperature Setpoint Active and Heat Cool Mode Status points ( ). Figure 9.
Additional Information and Considerations Outdoor air temperature On the TStat_FanCoil, the point Outdoor Air Temperature is only controlled from a BAS. It is not used in the control sequence of the device. If this value is to be shown on the LCD display on the thermostat, it’s recommended to use global referencing to send the Facility Outdoor Air Temperature to this point.
Data Normalization Special data normalization has been applied to various points in the factory loaded equipment templates. This data normalization serves to make a consistent interface to equipment across Tracer SC. This chapter lists special data normalizations for each equipment template. Example: Occupancy Request The following example of the Occupancy Request point in the TStat_FanCoil_Trane template indicates how to interpret the special data normalization.
Data Normalization Tracer SC point name: Occupancy Request BACnet point name, type, and instance: Occupancy Command (MV 18) Table 24. Tracer SC writing to the fan coil (Occupancy Request) Tracer SC state and text Fan coil state and text 1 - Occupied 2 - Occupied 2 - Unoccupied 3 - Unoccupied 3 - Occupied Bypass 2 - Occupied 4 - Occupied Standby 2 - Occupied 5 - Auto 1 - Local Occupancy Table 25.
Data Normalization Tracer SC Point name: Supply Fan Staged Speed Status BACnet point name, type, and instance: Fan Status (MV 28) Table 28. Tracer SC writing to the fan coil (Supply Fan Staged Speed Status) Tracer SC state and text 1 - Auto Fan coil state and text 4 - High 2 - Off 1 - Off 3 - Low 2 - Low 4 - Medium 3 - Medium 5 - High 4 - High Table 29.
Data Normalization Template: TStat_HeatPump_Trane This section lists special data normalizations for points in this template. • Tracer SC Point name: Occupancy Status • BACnet point name, type, and instance: Effective Occupancy (MV 34) Table 32.
Data Normalization Table 36.
Data Normalization Tracer SC Point name: Occupancy Request BACnet point name, type, and instance: Occupancy Command (MV 12) Table 40. Tracer SC writing to the rooftop unit (Occupancy Request) Tracer SC state and text Rooftop unit state and text 1 - Occupied 2 - Occupied 2 - Unoccupied 3 - Unoccupied 3 - Occupied Bypass 2 - Occupied 4 - Occupied Standby 2 - Occupied 5 - Auto 1 - Local Occupancy Table 41.
Trane Communicating Thermostat Points List The following tables provide side by side lists of Tracer SC points and Communicating Thermostat device point names and related information. TStat_Fan_Coil_Trane Table 44.
Trane Communicating Thermostat Points List Table 44.
Trane Communicating Thermostat Points List Table 45.
Trane Communicating Thermostat Points List Table 46.
Notes
Notes
Trane optimizes the performance of homes and buildings around the world. A business of Ingersoll Rand, the leader in creating and sustaining safe, comfortable and energy efficient environments, Trane offers a broad portfolio of advanced controls and HVAC systems, comprehensive building services, and parts. For more information, visit www.Trane.com. Trane has a policy of continuous product and product data improvement and reserves the right to change design and specifications without notice.
