Engineering Bulletin

Building Control Unit Sizing

for Version 17 Tracer Summit Systems

Use this bulletin to determine the number of building control units (BCUs) required to meet the specifications of a Tracer Summit application. The information in this bulletin pertains to Tracer Summit Version 17 software. Future enhancements to the Tracer Summit system may change the capabilities described in this bulletin.

This bulletin complements the Tracer Summit service literature. For more information on installation and programming, refer to the Tracer Summit user guides.

BAS-PRB005-EN

© 2006 American Standard Inc All rights reserved. BAS-PRB005-EN

™ ® The following are trademarks or registered trademarks of American Standard: CenTraVac, Horizon, IntelliPak, Rover, Thermostat Control Module (TCM), Tracer, Tracer Summit, Trane, TraneNet, UCP2, VariTrac, VariTrane, and Voyager.

™ ® The following are trademarks or registered trademarks of their respective companies or organizations: BACnet of ASHRAE; LonTalk and LonMark of Echelon Corporation; and Windows and Microsoft of Microsoft Corporation in the United States and other countries.

Overview

The Tracer Summit BCU is designed to be a multi-tasking, flexible, and data-rich system controller. It has an object-oriented database that allows easy access to vast amounts of information from unit control modules (UCMs) and other objects.

Like any computer, the BCU has limits for processing and memory capacity. Each of the connected Trane UCMs, as well as the user-selected application programs, consume some of the available capacity. All of the intended uses of a BCU need to be considered to determine if the BCU has sufficient capacity to meet those needs.

Many of the measurements listed in this bulletin are estimates because it is impossible to anticipate exactly how you will be applying a Tracer Summit system. In most cases, the estimates are adequate to determine BCU capacity, but some caution is advised for large or unusual applications. Contact GCS Product Support in St. Paul for assistance with unusual applications.

The following pages provide information and guidelines to help assess the needs of a particular project so that the proper quantity of BCUs is selected and applied efficiently and effectively.

BAS-PRB005-EN

Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

BCU models . . . . . . . . . . . . . . . . . . . . . . . . 4

Tracer Summit architecture . . . . . . . . . . . 5

Objects and properties . . . . . . . . . . . . . . . . 7

Input/output objects . . . . . . . . . . . . . . . . . . . . . . . . . . 7UCM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Application objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Seven-step procedure for BCU sizing . . . . . . . . . . . . . . . . . . . . . . . 8

NVM (non-volatile memory) . . . . . . . . . . . . . . . . . . . 8VM (volatile memory) . . . . . . . . . . . . . . . . . . . . . . . . . 8CPU (central processing unit) . . . . . . . . . . . . . . . . . . 8Step 1: Determine the number of UCMs . . . . . . . . . 8Step 2: Consider the building layout . . . . . . . . . . . . 13Step 3: Determine special input/output

object needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Step 4: Account for system communications . . . . 14Step 5: Determine application program

requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Step 6: Account for future enhancements . . . . . . . 17Step 7: Use a BCU sizing tool

to determine capacity . . . . . . . . . . . . . . . . . . . . . . . 17

Spreadsheet for BCU sizing . . . . . . . . . . . 18

Using the sizing spreadsheet . . . . . . . . . . . . . . . . . . 18Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Project parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 21Determine the number of UCMs . . . . . . . . . . . . . . . 21Consider the building layout . . . . . . . . . . . . . . . . . . 21Determine special input object needs . . . . . . . . . . . 22Account for system communications . . . . . . . . . . . 22Determine application program requirements . . . 22Account for future enhancements . . . . . . . . . . . . . . 22

3

BCU models

Any of four different BCU models may be running on your site.

BMTX BCU

The BMTX BCU was released with the Tracer Summit Version 16 software. The BMTX BCU has several advantages over the BMTW BCU, including increased performance and reliability.

The BMTX BCU offers a single model with the following integrated features: Ethernet, EIA-232 BACnet, four UCM communication links (one Comm3 isolated, two Comm4, one LonTalk), and high-capacity memory. Options include modem and operator display.

This bulletin focuses on BMTX BCUs; however, BMTX BCUs can

coexist on a site with the older BMTW and BMTS BCUs.

BMTW BCU

The BMTW BCU was released with the Tracer Summit Version 11 software in February 2000. The BMTW BCU has more capacity than the enhanced BMTS BCU. The BMTW BCU comes in two models: standard capacity and high capacity. The standard capacity BMTW BCU is upgradeable to a high capacity BMTW BCU.

The BMTW BCU supports BACnet/IP, an optional I/O module, an optional BCU operator display, and an additional UCM communication card slot with support for LonTalk devices.

Enhanced BMTS BCU

Beginning with the Tracer Summit Version 4.0 software release in June 1995 through January 2000, all BCU shipments were the enhanced model, which had increased performance and capacity.

Upgraded BMTS BCU

BMTS BCUs shipped prior to June 1995 can be upgraded to Version 6.0 software. Upgraded BMTS BCUs have Version 6 features and some increase in capacity. However, they do not have the same capacity as enhanced BMTS BCUs.

How to identify your BCU

Table 1 summarizes the differences among the various BCU models.

Table 1: Differences among BCU models

BMTX BCUBMTW BCU with operator display

BMTW BCUEnhanced BMTS

BCUUpgraded BMTS

BCU

Ship date North American version: 7/20/04 or laterEC version: 9/29/04 or later

North American version: 7/1/2000 or laterEC version: 6/4/2001 or later

2/1/00 to present 6/1/95 to 2/1/00 Prior to 6/1/95

Model number

BMTX 001 AAA BMTW 000 Digit 21 = 1

BMTW 000 BMTS 000 AAB Digit 10 = B

BMTS 000 AAADigit 10 = A

Serial number

North American version: E04G00000EC version: E04J000000

North American version: E00G05000EC version: E01F00000

N/A N/A N/A

Main circuit board part number

50100922 50100856 50100856 50100837 50100736

Main circuit board color

Green Green Green Blue Green

Number of UCM comm links

1 Isolated Comm3 2 Comm41 LonTalk

Up to 4 Up to 4 Up to 3 Up to 3

4 BAS-PRB005-EN

Tracer Summit architecture

The Tracer Summit building automation system (BAS) provides building control through a single, integrated system. Climate, lighting, scheduling, energy consumption, and other controllable features of a building can all be programmed and managed by a Tracer Summit BAS.

The system consists of BCUs, UCMs, PC workstations, and Tracer Summit software. The Tracer Summit system uses high-speed, distributed processing on a local area network (LAN) to operate the components as one system.

The Tracer Summit hardware architecture allows UCMs to be connected to BCUs. Multiple BCUs can be connected as needed to control various types and sizes of applications. The operator interface is provided by one or more PC workstations and/or by the optional BCU operator display.

BCUs and PC workstations are connected by Ethernet LAN or by a shared (Internet protocol) network (Figure 1 on page 6). In addition, a remote PC workstation can be connected to the system through an optional 56k modem installed in one or more of the BCUs in the system.

A Tracer Summit BCU is a control panel that communicates with multiple UCMs using up to four communication links. The BCU scans all UCMs to update information and coordinate control of the building. Each BCU contains its own unique set of application and monitoring programs to maintain comfort and control of the building, even if communication

with other BCUs and PC workstations fails.

The PC workstation is the primary operator interface for the Tracer Summit system. Multiple PC workstations can be directly connected on the LAN, as can one PC workstation connected remotely to a BCU through a modem.

Each PC workstation provides a graphical interface to system information. From the PC workstation, the operator has the ability to create and edit system data, view current and trend information, acknowledge alarms, and perform operator overrides.

The BCU operator display is an optional operator interface for the Tracer Summit system. It has a liquid crystal display (LCD) touch screen and can serve as a stand-alone operator interface between the user and the building automation system (BAS) equipment. It enables the occasional daily user to perform most Tracer Summit daily activities at the BCU, such as checking system status information, changing time-of-day schedules, handling alarms and events, and performing operator overrides.

BAS-PRB005-EN 5

Figure 1: Tracer Summit architecture

Able to connectto existing IP LAN

PC Workstation

Additional PCWorkstations or BCUs

BCU withoperator display

Remote PC Workstation

Additional BCUsor PC Workstations

LonTalk link (1)

Comm4 link (up to 2)

Isolated Comm3link (1)

Buildingcontrol

Unit control

Operatorinterface

Tracer ZN controllers

Tracer AH controllers

Tracer Loop Controller

Commercial Self-Contained

VariTrac II CCP

RTA/RTW*

PCM

TCM

LCP via LCP supervisor

Scroll chiller*

Tracer MP controllers

Generic LonTalk devices

LCI–C (Chillers)

Tracer V V controllers

Precedent*

*This UCM can communicate on other links besides the one shown.See Table 1 in the engineering bulletin(BAS-PRB006-EN) for more details.

Tracer Summit Software Versions

Horizon absorption chiller

TUC

UPCM

UCP2

VAV II, III, IV

Ethernet connection

Ethernet connection

Ethernet connection

Only 4 UCMcommunication

links can be usedon each BCU.

IntelliPak*

Voyager*

6 BAS-PRB005-EN

Objects and properties

The Tracer Summit system is based on the concept of objects. Objects are created by the operator and used to define elements of the system. The Tracer Summit system uses an object-oriented database to perform tasks and applications. All inputs, outputs, UCMs, applications, and graphics are recognized as objects by this database.

Each object has characteristic information (or properties) that may be viewed, referenced, and applied throughout the Tracer Summit system. Properties exist in the database so that the system programmer can access and apply them to the various applications without having to map over points (a process required in other systems).

For example, if the leaving chilled water temperature from a centrifugal chiller is needed as a dynamic value on a graphic display, the system programmer uses that property as a reference from the database versus creating an analog input that indexes the property.

Note: A complete list of the objects and their associated properties (along with descriptions) are available in the electronic reference library that ships with the Tracer Summit software.

Input/output objects

Input/output objects can be analog inputs, binary inputs, analog outputs, or binary outputs. Inputs reference their present value from other objects in the system—typically, UCMs. Outputs are used to control setpoint values or relay

outputs to other objects in the system.

For example, using the Analog Input editor, an analog input object can be created to reference a temperature sensor. The following are some typical properties and their values for this analog input object:

Property Value

Name Gym temperature

Present Value 75

Units Degrees F

High Alarm Limit 80

Low Alarm Limit 60

UCM objects

UCM objects can be created for the Trane unit controllers listed in Table 3 on page 9. The properties associated with UCM objects typically allow the operator to view and edit all characteristics of a piece of equipment. The following are a few of over 100 typical properties and their values for a Chiller (LonTalk) object:

Property Value

Name Chiller #1

Present Value Occupied

Chilled Water Temp: Leaving 45

Chiller Type CVH

Application objects

Applications on the Tracer Summit system, such as area control, time of day scheduling, calculation objects, custom programming language (CPL) routines, and site security are also recognized as objects by the database. Application objects typically have specific properties that relate to their operation.

BAS-PRB005-EN 7

Seven-step procedure for BCU sizing

Several factors need to be taken into account when determining the capacity of a BCU. The usage factors used in the BCU sizing spreadsheet were calculated from actual Tracer Summit installations. The sizing spreadsheet is intended to give estimates of the capacity of a BCU.

The sizing spreadsheet uses three types of measurement of BCU processor capacity: NVM, VM, and CPU usages. All three measurements must be considered to properly determine BCU loading.

NVM (non-volatile memory)

NVM is the BCU memory in which the setup parameters for objects are stored. The parameters stored in NVM are maintained indefinitely and are also referred to as the BCU database. In Tracer Summit, the NVM component of the BCU is represented by the device property “Percent BCU NVM Available.”

VM (volatile memory)

VM is the BCU memory in which current and historical data is stored, such as UCM data from the last scan and trends. In the event of a power outage, VM data is backed up for 7 days by a super capacitor in the BCU. In Tracer Summit, the VM component of the BCU is represented by the device property “Percent BCU VM Available.”

CPU (central processing

unit)

CPU refers to the BCU processor, which performs various

communication and control tasks. All of the work done by a BCU is done by the CPU.

In Tracer Summit, the CPU component of the BCU is represented by the device property “Percent Processor Idle Time.” The value of this property is valid for the first 5 minutes after a BCU reset (BMTX BCU requires reset only; BMTW BCU requires either clearing RAM or controlling from a graphic using setpoint control to 0.0).

Follow this seven-step procedure when determining the number of BCUs required for a specific application. Go to the page cited at each step for a detailed explanation of that step:

1 Determine the number of UCMs (page 8).

2 Consider the building layout (page 13).

3 Determine special input/output object needs (page 14).

4 Account for system communications (page 14).

5 Determine application program requirements (page 15).

6 Account for future enhancements (page 17).

7 Complete sizing spreadsheet to determine capacity (page 17).

Step 1: Determine the

number of UCMs

A BMTX BCU can have one isolated Comm3, two Comm4, and one LonTalk UCM communication link. A maximum quantity of each type of UCM can be connected to each communication link (Figure 1 on page 6). Additionally, a

maximum quantity of each type of UCM can be connected to each BCU. Refer to the Table 3 on page 9 for information on link sizing.

Each connected UCM device has BCU usage factors that need to be considered. Refer to the BCU sizing for BMTW and BMTX spreadsheets, which are available on TraneNet. Each UCM communication link also has base usage factors in addition to the individual UCM usage factors.

Isolated Comm3, Comm4, and LonTalk links can have a mixture of different types of UCMs, so the following rules must be used when determining the individual link capacities.

Comm3 link sizing

Multiple UCM devices can be combined on a single, isolated Comm3 link provided that the total link scan time does not exceed the specified limit. Each UCM type has a scan time, which is the time required for the BCU to scan each device. The link-loading limit is based on a maximum total scan time of 60 seconds for all devices on the link. If the link is loaded in less than the specified limit, the total scan time is reduced accordingly, down to a minimum of 10 seconds.

8 BAS-PRB005-EN

Table 4 on page 11 summarizes the UCM quantities per link and per BCU and the scan times per device for Comm3 links.

Use the formula in Table 2 to determine if a given quantity and mix of UCMs will fit on a link, add the scan times for each device and verify that the total is less than the limit of 60 seconds.

Table 2: Formula for sizing Comm3 links

Quantity TCMs × 1 second

Quantity PCMs × 1.5 seconds

Quantity RTA-RTWs × 2 seconds

Quantity scroll chillers × 1 second

Quantity CSCs × 1.5 seconds

Quantity LCPs × 1 second

≤ 60 seconds total scan time

Table 3: UCM communication link sizing for BMTX BCU

Comm link type

UCM device ObjectMaximum UCMs

per link per BCU

Comm3 Commercial Self-Contained (CSC) Commercial Self-Contained (CSC) 20 20

Lighting Control Panel (LCP) Lighting Control Panel (LCP) 8 8

Programmable Control Module (PCM) Programmable Control Module (PCM) 30 30

RTA-RTW Series R chiller (RTA/RTW) 10 10

Scroll chiller Scroll chiller (CGA/CGW) 10 10

Thermostat control module (TCM) Thermostat control module (TCM) 60 60

Trane Europe chiller (TEC) Trane Europe chiller 10 10

VariTrac II CCP VariTrac II Central Control Panel (CCP) 6 6

Voyager rooftop Voyager rooftop (Comm3) 32 32

Comm4 Horizon absorption chiller Horizon absorption chiller 10 10

IntelliPak IntelliPak rooftop 20 20

Terminal Unit Controller (TUC) Terminal Unit Controller 64 128

UCP2 Absorption chiller (UCP2)Centrifugal chiller (UCP2)Helical rotary chiller (UCP2)

10 10

UPCM Universal PCM 10 10

VAV II/III/IV VariTrane UCM II/III/IV 63 126

Voyager rooftop Voyager rooftop 32 32

Wireless receiver Wireless receiver 8 8

BAS-PRB005-EN 9

LonTalk Generic LonTalk Device (GLD) Generic LonTalk Device (GLD) 40 40

IntelliPak Commercial Self-Contained (CSC) (LCI-I)

Discharge Air Controller (DAC) 20 20

IntelliPak Commercial Self-Contained (CSC) (LCI-I)

Space Comfort Controller (SCC) 120 120

IntelliPak fresh-air unit (FAU) (LCI-I) Discharge Air Controller (DAC) 20 20

IntelliPak rooftop (LCI-I) Discharge Air Controller (DAC) 20 20

IntelliPak rooftop (LCI-I) Space Comfort Controller (SCC) 120 120

Odyssey (ReliaTel controls) (LCI-R) Space Comfort Controller (SCC) 120 120

Precedent rooftop (ReliaTel controls) (LCI-R) Space Comfort Controller (SCC) 120 120

Tracer AH540/541 Space Comfort Controller (SCC) 120 120

Tracer AH540/541 Discharge Air Controller (DAC) 20 20

Tracer CH530/531 (LCI-C) Chiller (LonTalk) 10 10

Tracer Loop Controller Tracer Loop Controller (TLC) 1 1

Tracer MP501 Space Comfort Controller (SCC) 120 120

Tracer MP501 Generic LonTalk Device (GLD) 40 40

Tracer MP503 Generic LonTalk Device (GLD) 40 40

Tracer MP580/581 MP580/581 20 20

Tracer VV550/551 Space Comfort Controller (SCC) 120 120

Tracer ZN510/511 Space Comfort Controller (SCC) 120 120

Tracer ZN520/521 Space Comfort Controller (SCC) 120 120

Tracer ZN517 Space Comfort Controller (SCC) 120 120

Tracer ZN523 Space Comfort Controller (SCC) 120 120

Tracer ZN524 Space Comfort Controller (SCC) 120 120

Voyager Commercial (ReliaTel controls) (LCI-R) Discharge Air Controller (DAC) 20 20

Voyager Commercial (ReliaTel controls) (LCI-R) Space Comfort Controller (SCC) 120 120

Voyager rooftop (LCI-V) Space Comfort Controller (SCC) 120 120

Table 3: UCM communication link sizing for BMTX BCU (continued)

Comm link type

UCM device ObjectMaximum UCMs

per link per BCU

10 BAS-PRB005-EN

For the example in Table 5, a Comm3 link with 15 TCMs, 5 PCMs, 2 RTAA-RTWA chillers, 3 scroll chillers, 2 CSCs, and 3 LCPs has a total scan time of approximately 35.5 seconds.

Note: The minimum scan time is 10 seconds, so unloading links below 10 seconds total scan time does not improve performance.

Comm4 link sizing

Up to 64 UCM devices can be combined on a single Comm4 link provided that the total link scan time does not exceed the specified limit. Each UCM type has a scan time, which is the time required for the BCU to scan each device. The link loading limit is based on a maximum total scan time of 63 seconds for all devices on the link. If the link is loaded in less than the specified limit, the total scan time is reduced accordingly, down to a minimum of 10 seconds.

Table 9 summarizes the UCM quantities, scan times, and BCU usage factors for Comm4 links.

Use Table 6 to determine if a given quantity and mix of UCMs will fit on a link, add the scan times for each device, and verify that the total is less than the limit of 63 seconds. In addition, each type of UCM must be within its individual limits, and the total number of devices on the link must be 64 or less.

For the example in Table 7, a Comm4 link with 2 UPCMs, 10 TUCs, 20 VAVs, and 6 Voyagers has a total scan time of 31 seconds.

To maximize BCU capacity, use the minimum number of links fully loaded. To maximize performance (scan time), use more links that are lightly loaded.

Note: The minimum scan time is 10 seconds, so unloading links below 10 seconds total scan time does not improve performance.

Table 4: Comm3 link parameters for BMTX BCU

UCM deviceMax per BCU

Scan time per device

CSC 20 1.5 sec

LCP** 8 1 sec

PCM 30 1.5 sec

RTAA-RTWA (Tracer CH530)

10 2 sec

Scroll chiller* 10 1 sec

TCM 60 1 sec

Trane Europe chiller

10 2 sec

VariTrac II CCP 6 10 sec

Voyager 32 1 sec

Comm3 link 1 N/A

Maximum total scan time per link = 60 seconds

*Note: Includes IntelliPak chiller**Note: LCPs can be connected to a

link only through a supervisor panel. The parameters above include a supervisor panel.

Table 5: Calculating Comm3 scan time (example)

15 TCMs × 1 sec = 15 sec

5 PCMs × 1.5 sec = 7.5 sec

2 RTA-RTW × 2 sec = 4 sec

3 scroll chillers

× 1 sec = 3 sec

2 CSCs × 1.5 sec = 3 sec

3 LCPs × 1 sec = 3 sec

Total scan time = 35.5 sec

Table 6: Formula for sizing Comm4 links

Quantity TUCs × 0.5 seconds

Quantity VAV II/III/IVs × 1 second

Quantity UPCMs × 3 seconds

Quantity UCP2 × 3 seconds

Quantity IntelliPaks × 1 second

Quantity Voyager rooftops × 0.5 second

≤ 63 seconds total scan time

≤ 64 total devices (including wireless receiver)

Table 7: Calculating Comm4 scan time (example)

2 UPCMs × 3 sec = 6 sec

10 TUCs × 0.5 sec = 5 sec

20 VAVs × 1 sec = 20 sec

6 Voyagers × 0.5 sec = 3 sec

Total scan time = 31 sec

BAS-PRB005-EN 11

LonTalk link sizing

Table 8 on page 12 summarizes the UCM quantities and BCU usage factors for LonTalk links. LonTalk links do not have scan times because each device automatically reports a change of state to the BCU.

Note: LonTalk links are limited to 120 devices.

Tracer Summit supports the following LonMark HVAC Functional Profiles: Space Comfort Controller (SCC), Discharge Air Controller (DAC), and Chiller. A Tracer Summit system can support four categories of controllers on its LonTalk communication link:

• Trane controllers that follow the supported profiles

• Non-Trane controllers that follow the supported profiles

• Trane controllers that do not con-form to the supported profiles

• Non-Trane controllers that do not conform to the supported profiles

Trane controllers that follow the

supported profiles

These controllers are configured to follow a standard LonMark® profile. Using a profile is the quickest way to install and commission a controller in Tracer Summit. LonMark® profiles supported by the Tracer Summit system include SCC, DAC, and Chiller. See Table 3 on page 9 for more information about which profiles can be used for the various LonTalk controllers.

Non-Trane controllers that follow

the supported profiles

Tracer Summit also supports controllers from other suppliers that follow the LonTalk SCC, DAC, and Chiller profiles. In addition, controllers that follow legacy terminal profiles can be supported as SCCs. Examples of these profiles include VAV, fan coil, heat pump,

and rooftop units. Refer to the Tracer Summit Connections to LonTalk® Devices engineering bulletin (BAS-PRB003-EN) for more details on support of LonTalk devices.

Trane controllers that do not

conform to the supported profiles

Certain Trane controllers do not comply to a standard profile. An example of this is the Tracer Loop Controller. In this case, we have created an object in the Tracer Summit system to support this device and set it up the same way as an object that follows a standard profile.

Similar to the Tracer Loop Controller, the Tracer MP580/581 has its own object type in Tracer Summit. It can have one of three profile configurations: No Profile, DAC, or SCC. In all three cases, it must be created in the Tracer Summit database as a Tracer MP580/581 object in order to access

Table 8: LonTalk link parameters for BMTX BCU

UCM deviceMax per

BCU

DAC 20

GLD 40

SCC 120

Tracer CH530/531 (LCI-C) 10

Tracer Loop Controller 1

Tracer MP580/581 controller

20

LonTalk link 1

Note: A LonTalk link repeater must be used when more than 60 devices are connected to a link.

Table 9: Comm4 link parameters for BMTX BCU

UCM device Max per link Max per BCUScan time per

device

Horizon absorption chiller 10 10 3 sec

IntelliPak 20 20 1 sec

TUC 64 128 0.5 sec

UCP2 10 10 3 sec

UPCM 10 10 3 sec

VAV II/III/IV 63 126 1 sec

Voyager rooftop 32 32 0.5 sec

Wireless receiver 8 8 N/A

Comm4 link N/A 2 N/A

Maximum total scan time per link = 63 seconds

Maximum number of devices per link = 64

12 BAS-PRB005-EN

all point data available to Tracer Summit.

Non-Trane controllers that do not

conform to the supported profiles

LonTalk controllers that do not conform to SCC, DAC, or Chiller profiles can be supported as a Generic LonTalk Device (GLD). Most LonTalk controllers that use FTT-10A or FT-X1 transceivers and support standard network variable types (SNVTs) can be set up as a GLD. The GLD object in the Tracer Summit system acts as a placeholder to identify the LonTalk device and store its location and type.

Each piece of data that you want to view, change, or control from this device is then set up using input and output objects (analog inputs, analog outputs, binary inputs, and binary outputs). These input and output objects are the same I/O objects that are used for other applications.

Setting up a GLD is typically used to integrate non-Trane controllers that do not follow Tracer Summit-supported profiles. Refer to the Tracer Summit Connections to LonTalk® Devices engineering bulletin (BAS-PRB003-EN) for more details.

Step 2: Consider the

building layout

In addition to the UCM quantity limitations, you should consider other factors of building layout when placing UCMs on BCUs. These factors typically fall into two categories: HVAC systems and BACnet communications.

HVAC systems

For best system performance, HVAC subsystems should be contained within a single BCU whenever possible. This limits the dependence on Ethernet LAN communications and allows the BCU and its associated HVAC subsystems to operate as a stand-alone system. This operation is especially useful during system startup and commissioning or during servicing.

For example, if a building has a central chilled water plant, the UCMs associated with the chiller plant should be connected on a single BCU. Another common example is a VAV system; the air-handling unit (AHU) and its associated VAV boxes should be connected to the same BCU.

Also, consider using the Rover service tool for VAV and TUC applications. Rover can access any VAV II/III/IV or TUC device connected on the same Comm4 link. It is recommended, for example, to connect all the VAV boxes for a single AHU on the same Comm4 link to facilitate air-balancing operations utilizing Rover. Tracer Summit software or the Rover service tool can be used for commissioning a LonTalk link.

BACnet communications

BCUs on a local area network (LAN) communicate to PC workstations through Ethernet communications (dedicated or shared network).

Ethernet communications

Ethernet cabling should be installed by certified personnel.

The BAS technician should simply be able to use patch cables to plug BAS devices into the Ethernet LAN. The Ethernet LAN can be either of the following:

• Dedicated• Shared

Dedicated network

Ethernet communication can be used for a dedicated network. Dedicated networks will remain fairly common. This is due to the fact that building LAN wiring is one of the last phases of a construction site and commissioning of an HVAC system needs to take place prior to this phase of construction. A dedicated Ethernet network can then be connected to a shared Ethernet network and become one component of that network.

BACnet/IP communications

(shared network)

BACnet/IP is supported in the BMTX BCU. This means that BCUs can be connected to a shared Ethernet building LAN. Performing the BACnet/IP functions requires more processor time. Another item to consider is whether the site you plan on connecting by BACnet/IP has any BMTS BCUs on site. If it does, you will need a router between the existing dedicated network of BMTS BCUs and the shared network.

Important: The spreadsheet does not adequately account for the load placed on a BCU by LAN network traffic when using BACnet/IP. High LAN traffic and/or broadcast storms may cause BCU perfor-mance to diminish, potentially to

BAS-PRB005-EN 13

an unacceptable degree. In these cases, the use of a router is recom-mended to isolate the BCU from the LAN.

Step 3: Determine special

input/output object needs

All Trane UCMs have internal diagnostics that you can set up to be announced on Tracer Summit PC workstations. In addition, the Tracer Summit object-oriented database allows other objects to access or reference properties (values) from all objects, such as UCMs and applications. Therefore, analog and binary inputs typically need to be created only when custom alarming sequences or a BACnet interface to another system is required.

You can create analog and binary input objects to monitor various properties within the Tracer Summit system. Set up these inputs to react to alarm conditions by notifying specific PC workstations, displaying expanded messages or graphics, and executing a control routine. These inputs consume a significant amount of memory and processor usage and must be accounted for in the BCU sizing spreadsheet.

Analog and binary outputs are typically created to allow the operator to override setpoints or enable/disable operation of several pieces of equipment simultaneously. Binary outputs may also be created for event-driven control of binary values/outputs on some UCMs, especially TCMs, PCMs, and UPCMs.

In general, all of the UCM editors have setpoints and enable/disable entries that an operator can change. Analog and binary outputs are required so that operators can override normal operation (application program control) and still maintain priority control.

Creating analog and binary outputs simplifies system operation for the operator. Output objects are also required for setpoint and start/stop control through a BACnet interface. The number of analog and binary outputs must be entered into the BCU sizing spreadsheet.

Step 4: Account for system

communications

The fourth step is to consider the system communications that may require space on the BCU.

PC workstation graphics

When graphic displays are used on PC workstations, the BCUs in the system must constantly provide updated data to be displayed on the graphics in use. The building operator can have multiple graphics concurrently displayed on multiple PC workstations. This can have a significant effect on BCU processor capacity.

A typical amount of PC workstation graphics is calculated as overhead on the BCU sizing spreadsheet. The typical allowance is based on two PC workstations in the system with average use of primarily standard graphics.

If extensive graphics with a large amount of data from a single BCU are anticipated, or if a large

number of PC workstations will be displaying data concurrently, the affected BCUs should be less heavily loaded when laying out the system.

Note: Although Tracer Summit allows multiple graphic displays to be open at the same time on a single workstation, this practice is not recommended. As described above, multiple graphics can have a significant impact on BCU processor capacity, plus an operator is typically only viewing a single graphic at one time.

Operator display customer

screens

A BCU can be equipped with the optional BCU operator display, allowing building operators to access data within the Tracer Summit site, such as viewing or editing time-of-day schedules and overriding setpoints on equipment.

The site programmer can choose which object types can be accessed from the operator display. From this list of available objects (for example, analog and binary outputs, and UCMs), the site programmer can create a member list.

The site programmer can create custom screens to be viewed at the operator display. Custom screens are similar to workstation graphics in that they not only can contain status text, override buttons, target buttons, and setpoint controls but also can contain graphics (monochrome bitmaps). These graphics can use the entire screen of the operator display 320 × 240 pixel resolution.

14 BAS-PRB005-EN

Custom screens with bitmaps consume significantly more BCU memory than custom screens without bitmaps. The BCU operator display custom screens (with or without bitmaps) must be accounted for in the BCU sizing spreadsheet.

Note: Although the custom screens with bitmaps are allowed to use the entire 320 × 240 pixel screen of the operator display, it is more typical to use half the screen or less for bitmaps to better accommodate for other information accompanying the bitmap, such as static and status text, and target buttons. If there are bitmaps larger than one-fourth of the screen size, that particular screen needs to account for two custom screens with bitmaps in the sizing spreadsheet.

The BCU operator display is a stretchy object in that its size varies by the length of its member list, the number of custom screens and the number of bitmaps used in custom screens. To account for the size of the operator display object, estimate the total number of custom screens, custom screens with bitmaps, and members.

Note: The BCU operator display members field automatically shows the calculation of all eligible objects already entered in the spreadsheet. The number can be made smaller to free memory.

Modem communications

A BCU can have an optional modem installed for communication to a remote PC workstation. A single modem in one BCU can provide communication to all of the BCUs

in the system (connected through the Ethernet LAN). This communication traffic adds load to the BCU with the modem installed. This modem capacity must be accounted for in the BCU sizing spreadsheet.

Note: Unlike its predecessors, the BMTX BCU can have simultaneous communication through a modem and an EIA-232 port.

EIA-232 BACnet communications

A BCU has an EIA-232 port installed for a BACnet interface to another BAS system. This EIA-232 BACnet port can be used to access BACnet objects on any BCU or BACnet device in the system. As a general rule, each BCU can support a maximum of 350 BACnet points through its EIA-232 port. This number may vary depending on the BCU load.

The BACnet communication traffic adds load to the BCU with the EIA-232 card installed and must be accounted for on the BCU sizing spreadsheet. If additional BACnet objects are required from a system, additional BCUs must be added.

Step 5: Determine

application program

requirements

Consider the number of application programs required to meet the job specifications when determining the capacity of a BCU. There are no set limits to the number of application programs that a BCU can execute. The number of tasks that a given application can perform is variable as well. These application program objects are variable in size and are sometimes

referred to as stretchy or expandable objects. The BCU sizing spreadsheet uses typical estimates for these objects.

Time-of-day schedules

Time-of-day (TOD) schedule objects provide the building equipment with a schedule to follow. For a sophisticated building that has multiple tenants with different hours of operation, multiple schedules may be set up based on the different scheduling characteristics. Estimate the number of TOD schedules based on how many unique scheduling requirements the building must support.

TOD schedules are stretchy objects because their sizes vary by the length of their member lists. To account for the size of the TOD schedule object, estimate the total number of TOD schedule members, as well as the typical number of holidays and exception schedules (if used), for the facility.

Note: Members of the TOD schedule can reside in one or more BCUs.

Using exceptions schedules is a method for creating a schedule change for a single day without affecting the normal schedule. Exception schedules add to the memory usage (NVM) of the BCU. After creation, exception schedules remain in memory until they are manually removed. If exception schedules are routinely used, the outdated entries should be removed routinely from each schedule to spare BCU resources.

BAS-PRB005-EN 15

Area

Use area objects for optimal start/stop capabilities and to combine HVAC equipment in a common group. Each area can range from a single office, to a group of offices, to a large, open warehouse.

Equipment is typically grouped to coordinate tasks, such as TOD scheduling for a specific area in a building. VAV boxes are typically grouped using area objects. The amount of grouping represents the number of area objects. The number of these areas needs to be estimated.

Areas are stretchy objects because their sizes vary by the length of their member lists. To account for the size of the area object, estimate the total number of area members.

Note: Members of the area can reside in one or more BCUs.

VAV air systems (VAS)

Use VAS objects for variable-air-volume applications. The main purpose of the VAS object is to provide comfort to a space by executing two procedures. The first procedure is to monitor all the assigned VAV boxes in the object for proper comfort level. The second procedure is to use feedback gathered from the VAV boxes to control the VAV air-handling unit.

Tracer Summit has two types of VAS objects:

• VAS Comm3/Comm4 object—Used with isolated Comm3 UCM objects (such as Voyager [Comm3] and PCM) and Comm4 UCM objects (such as VAV II/III/IV and IntelliPak)

• VAS LonTalk object—Used with LonTalk UCM objects: Tracer MP580/581, DACs such as the Tracer AH540/541, and SCCs designed for VAV control such as the Tracer VV550/551

Estimate the number of VAS Comm3/Comm4 objects and VAS LonTalk objects by totaling the number of VAV air-handling units in the building—one object per air-handling unit.

Note: Members of the VAS Comm3/Comm4 and VAS LonTalk objects can reside in one or more BCUs.

The VAS Comm3/Comm4 and VAS LonTalk objects are stretchy objects because their sizes vary by the length of their member lists. To account for the size of both VAS objects, estimate the total number of VAS Comm3/Comm4 and VAS LonTalk members.

Chiller plant control

Use chiller plant control objects for buildings that require control of multiple chillers. Each object represents a control sequence for a group of chillers. Typically, a single chiller plant control object provides control for an entire chiller plant. Even though it is possible to program multiple chiller plant control objects in a single BCU, it is not typical.

Calculation objects

Use calculation objects in recording historical data of individual properties. This summary calculation can be any of the following: minimum, maximum, average, peak, run hours and starts, BTU usage, degree days, and meter totalization.

For example, by using the calculation object, an owner can determine what the maximum zone temperature was yesterday, today, the last billing period, and the current billing period.

Each property an operator wishes to monitor requires the setup of a calculation object. Therefore, in estimating the usage of calculation objects for the BCU sizing spreadsheet, determine how many properties need to be monitored.

Trend objects

Trend objects are another example of stretchy or expandable application program objects; however, unlike some stretchy objects, each trend has a maximum capacity it is allowed to use. Trend objects are used for storing values in a BCU for use in historical reports.

The number of members and size of trends can vary dramatically from trend to trend. Each trend can have up to 64 members (properties) to trend. The interval at which a trend samples data from a member is flexible. A member can be sampled as often as once every minute or as infrequently as once per month or user-defined billing period.

16 BAS-PRB005-EN

The more members and samples required for a trend, the more BCU memory that trend consumes. A trend can store 1 member with up to 244 samples or up to 64 members with 8 samples. Both of these examples are considered large trends in spreadsheet because they use 100% of the available capacity of one trend.

A trend that has 1 member and 122 samples or 32 members and 8 samples is a small trend because it uses about 50% of the available capacity of one trend. Use these examples to properly estimate the BCU usage for trends.

Heat pump loop control

Use heat pump loop control (HPLC) objects for buildings that require control of a water-source heat pump loop. Each object represents a control sequence for a group of water-source heat pumps. Typically, an HPLC object provides control for an entire water-source heat pump loop. Although it is possible to program multiple HPLC objects in a single BCU, it is not typical.

HPLC objects are stretchy because their sizes vary by the length of their member lists. To account for the size of the HPLC object, estimate the total number of HPLC SCC members.

Note: Members of the HPLC can reside in one or more BCUs.

Custom programming language

(CPL)

CPL routines are one of the best examples of stretchy application program objects. The system programmer can create any

quantity of CPL routines of any size/complexity. This makes the size of CPL routines nearly impossible to estimate accurately.

The BCU sizing spreadsheet estimates small and large CPL routines. These estimates were determined from typical routines used on actual job sites and are realistic for most applications.

Compile a CPL routine in Tracer Summit to determine the amount of non-volatile memory (NVM) that a CPL routine consumes. The software indicates the number of bytes of the compiled routine.

For the CPL (small) selection, the size is about 900 bytes, approximately the size of the CPL Library routine “AIR_CALC.CPL.” For the CPL (large) selection, the size is about 3,600 bytes, approximately the size of the CPL Library routine “VAV_TMP3.CPL,” modified to include 30 VAVs and 30 wireless VAVs.

If the compiled size is unknown, estimate the size by completing a CPL text file of similar length as the routine that will be used in the site. Remove all double-slashed comment lines from the example because these comment lines are not downloaded to the BCU. (Triple-slashed comment lines are downloaded to the BCU.)

Then take the file size in bytes and multiply by 60%. Compare this number to 900 for CPL (small) and 3,600 for CPL (large). If, for example, the file size is around 1,800 bytes, use two CPL (small) objects in the sizing spreadsheet.

Because the size and run frequency of CPL routines vary and affect the

degree to which a CPL routine affects NVM, enter the CPL object estimations last when sizing a BCU. Verify that there is enough room in the BCU for varying memory usage without the usage factors becoming unacceptably low.

Step 6: Account for future

enhancements

Not all uses of a BCU can be anticipated prior to installation. Because of these unknown requirements, some BCU capacity must be reserved for future use.

The BCU sizing spreadsheet allocates 10% capacity (1 in the future expansion field) for future use. If extensive future expansion is anticipated, additional capacity should be reserved or additional BCUs can be added to the system in the future.

Step 7: Use a BCU sizing

tool to determine capacity

Use the BMTX BCU Sizing spreadsheet tool in Excel (Figure 3 on page 20) to verify that application requirements for each BMTX BCU do not exceed capacity of a BCU.

Note: BMTW and BMTS BCUs have the same considerations as BMTX BCUs, and the same seven-step sizing procedure should be used to check BCU capacity. Sizing spreadsheets for each BCU type are available on the TraneNet information system.

Down load the most recent sizing spreadsheet before starting a new project. The sizing tool is updated with new version of Tracer Summit.

BAS-PRB005-EN 17

Spreadsheet for BCU sizing

The BMTX V17 Sizing Tool is a spreadsheet for sizing BMTX BCUs by automatically calculating usage factors and scan times based on quantities entered. The spreadsheet automatically selects the minimum quantity of UCM communication links required and notifies you when any sizing limits are exceeded.

Note: The sizing spreadsheet is available on TraneNet from the Tracer Summit product page. Before starting each project, make sure you have the latest revision of the sizing spreadsheet.

Using the sizing spreadsheet

Microsoft Excel is required to use the BCU sizing spreadsheet. To enhance system performance, copy the BCU sizing spreadsheet onto your PC hard drive.

Opening the sizing spreadsheet

1 Open BMTX V17 Sizing Tool.xls in Microsoft Excel.

2 If a message appears stating that your security level will not allow the running of macros:

a Click OK.

b From the Tools menu, point to Macro and click Security.

c Click the Medium option.

d Click OK.

e Close and re-open the spreadsheet.

3 If a message appears asking if you want to enable macros, click the Enable Macros button.

4 If messages appear asking if you want to open the spreadsheet as read-only, click Yes.

Calculating BCU usage

1 In the BCU Name field, type a name for the BCU.

2 Click the Link 1 tab or the tab for the link you want to configure. The link sizing spreadsheet appears (Figure 2).

3 Type the number of UCMs on the link for each UCM type. The spreadsheet calculates the scan time, if applicable, and status.

4 Repeat steps 2 and 3 for each link you want to size.

5 Click the Go to BCU Sizing Worksheet button. The BCU sizing spreadsheet appears.

6 Click the Import UCM/Link Data button.

7 Type the quantity of any additional UCM devices and other objects for this BCU (Figure 3 on page 20).

Note: At any time, you can enter UCM device and other object quantities directly into the sizing spreadsheet without using the link sizing spreadsheets.

Figure 2: Tracer Summit BMTX BCU communication link sizing spreadsheet

18 BAS-PRB005-EN

System results

The spreadsheet completes the following functions:

• Totals the NVM, VM, and CPU columns and writes the totals in the BCU Resources Used fields

• Finds the largest number among the totals in the NVM, VM, and CPU columns and copies it into the MAX field

• Displays the limiting factor (NVM, VM, or CPU) to the right of the MAX field

• Indicates the remaining capacity in the BCU near the top in the Space Available field

• Displays the Total Scan Time for each link type in the Notes/Errors column

• Displays an error message in the Notes/Errors column if any limit is exceeded (This column must be free of error messages for the BCU to be sized properly.)

• Displays either OK or an error message in the Total BCU Status field (This cell must show OK for the BCU to be sized properly.)

Printing, saving, and closing the

spreadsheet

1 When all required quantities have been entered and all error messages are cleared, print the current sheet by clicking the Print button on the Excel toolbar.

2 From the File menu, click Save As if you want to save your last calculations under a different file name.

3 Click the Clear Input Data button to size another BCU.

4 From the File menu, choose Exit to close the program. Do not save the changes so that you can start with a clean spreadsheet the next time BMTX V17 Sizing Tool.xls is opened.

Error messages

Error messages may display in two locations: the Notes/Errors column in the BCU sizing spreadsheet and in the Device Status column in the link sizing spreadsheet. These errors appear if sizing limits are exceeded. You must not have any error messages displayed when printing the final selection.

BAS-PRB005-EN 19

Figure 3: Example Tracer Summit BMTX BCU sizing spreadsheet

20 BAS-PRB005-EN

Example

The following example illustrates the steps to determine the number of BCUs required for a Tracer Summit project. This example shows only the process of determining the number of BCUs in the given example and is not intended as a detailed applications example.

Project parameters

This project involves a 70,000 square foot, single-level school with a Tracer Summit Integrated Comfort system (ICS) containing one PC Workstation and a modem for remote communications. The HVAC systems to be used are unit ventilators in the classrooms, constant-volume AHUs for the gymnasiums, a multi-zone, constant-volume AHU for the kitchen and cafeteria area, a variable-volume AHU for the administration and library area, lighting zones, DDC and VAV terminal units, a chiller, a cooling tower, a packaged boiler, zoned hot water, and miscellaneous ventilation controls.

Determine the number of

UCMs

The UCMs in Table 10 are assumed based on the job site description.

Note: There are three different SCC types: Tracer VV550, Tracer ZN520, and Tracer AH540; and one DAC type: Tracer AH540.

Using the sizing spreadsheet, it appears that a single BCU is sufficient to handle the project. The

necessary communication links are shown in Table 11.

Consider the building layout

Shared Ethernet (BACnet/IP

communications)

This example has one PC Workstation and one BCU. The entire system is contained on a single level. Communication between the BCU and PC can be made by tapping into the existing TCP/IP LAN and configuring the BMTW BCU for BACnet/IP. This topic is described in detail in the Tracer Summit BACnet/IP Network Installation engineering bulletin (BAS-PRB004-EN).

HVAC equipment locations

Because there is only one BCU, no special considerations for HVAC subsystems need to be made. In addition, all LonTalk devices are accessible by using the Rover service tool with a single connection.

Table 10: Number of UCMs

Equipment UCMs

2 Constant-volume AHUs

2 Tracer AH540s

1 Multi-zone, constant-volume AHU

1 Tracer MP581

1 VAV AHU 1 Tracer AH540

Lighting control 1 UPCM

15 VAVs in 3 areas—5 in library, 2 in general office, 8 in administration)

15 Tracer VV550s

35 Unit ventilators 35 Tracer ZN520s

1 Series R CenTraVac chiller

1 UCP2

1 Cooling tower 1 Tracer MP581

1 Boiler/hot water controller

1 Tracer MP581

Miscellaneous ventilation controllers

2 PCMs

Table 11: Comm links in BCU

Link 1 (Comm3)

Link 2 (Comm4)

Link 4(LonTalk)

2 PCM 1 UCP2, 1UPCM

3 AH540s, 15 VV550, 35 ZN520s, 2 MP581s

Scan time = 3 sec

Scan time = 6 sec

Scan time N/A

BAS-PRB005-EN 21

Determine special input

object needs

As mentioned previously in this engineering bulletin, analog and binary inputs are typically created only when special alarming (beyond that provided automatically by the UCMs) is required. In assessing the alarming needs for the example site, the lists in the following tables might be created.

Account for system

communications

The BCU has a modem for remote communication that must be accounted for in the usage table.

Determine application

program requirements

Applications require BCU resources and must be taken into consideration when deciding how many BCUs to use. In assessing the applications requirements for our example site, the following lists might be created.

VAV air system (VAS LonTalk)

1 for VAV Tracer AH540

Calculation objects

BCU operator display

1 BCU event log for Tracer Summit Web Server, BCU operator display, and remote access events

Area control

See Table 17 on page 23.

Trend objects

See Table 18 on page 23.

Time-of-day scheduling

See Table 19 on page 24.

CPL routines

See Table 20 on page 24.

Account for future

enhancements

A BCU usage factor of 10% has been reserved for future applications.

Use a BCU sizing tool to

determine capacity

Using the information determined from steps 1–6 of the “Seven-step procedure for BCU sizing” on page 8, complete the BMTX BCU sizing spreadsheet to determine the number of BCUs required. Figure 3 on page 20 shows a spreadsheet printout for this example.

Table 12: Analog inputs for BCU #1

Object Qty

Zone temperatures from multi-zone unit

3

Zone temperatures from classroom units

7

Zone temperatures from CV AHUs

2

Boiler water temperature 1

Cooling tower sump temperature

1

VAV AHU discharge temperature 1

VAV AHU duct static pressure 1

Zone temperatures from VAV terminals

3

Total 19

Table 13: Binary inputs for BCU #1

Object Qty

Alarms from multi-zone unit (fan fail, dirty filter, low limit)

3

CHW/CDW pump failure 2

Boiler alarm 1

Total 6

Table 14: Analog outputs for BCU #1

Object Qty

CHW supply setpoint 1

Hot water supply setpoint 1

VAV AHU supply temperature setpoint

1

VAV AHU duct static pressure setpoint

1

Make-up air temperature setpoint

2

Total 6

Table 15: Binary outputs for BCU #1

Object Qty

Lighting control outputs 12

Cooling tower enable output 1

Exhaust fan outputs 4

Total 17

Table 16: Calculation objects

Object Qty

kWh consumption (On peak, Off peak, Total)

3

kW peak (On peak, Off peak) 1

Total 5

22 BAS-PRB005-EN

Table 17: Area control

Area Members per areaNo. of

members per area

No. of areas

No. of members

Classroom Heat/cool: Tracer ZN520 5

Lighting: Binary outputs 1

Total 6 7 42

Multi-zone constant-volume

Heat/cool: Tracer MP581 1

Lighting: Binary output 2

Total 3 1 3

VAV Heat/cool: Tracer VV550 5 3 15

Gymnasium #1 (CV AHUs)

Heat/cool: Tracer AH540 1

Lighting: Binary output 1

Total 2 1 2

Gymnasium #2(CV AHUs)

Heat/cool: Tracer AH540 1

Lighting: Binary output 1

Total 2 1 2

Total areas 13

Total area members 64

Table 18: Trend objects needed

TrendNo. of

membersNo. of

samplesCapacity

Object size(large/small)

Energy trend for monthly values

5 24 27% Small

Energy trend for monthly values

5 12 13% Small

Chiller trend 10 24 49% Small

Zone temperature trend 40 12 90% Large

Total trends 3 Small1 Large

BAS-PRB005-EN 23

Table 19: Time-of-day scheduling

ScheduleArea members per

schedule

No. of members

per schedule

No. of schedules

No. of members

Classroom Lighting 7

Normal/optimal start 7

Total 14 2 28

Multi-zone constant-volume

Lighting 1

Normal/optimal start 1

Total 2 1 2

Miscellaneous/wiring

Binary output normal start

1 1 1

VAV Normal/optimal start 1 1 1

Gymnasiums Lighting 2

Normal/optimal start 2

Total 4 1 4

Total schedules 6

Total schedule members 36

Note: For this example, estimate 12 holidays and 10 exception schedules in addition to the sizing quantities in the table.

Table 20: CPL routines needed

FunctionalityFile size(bytes)

Object size(large/small)

Fire shutdown 800 Small

VAV min./max. temperature 3,200 Large

VAV max. position 3,800 Large

Duct static pressure reset 3,000 Large

Chiller/boiler changeover 300 Small

Miscellaneous 500 Small

Total CPL routines 3 Large3 Small

24 BAS-PRB005-EN

BAS-PRB005-EN 25

Trane has a policy of continuous product and product data improvement and reserves the right to change design and specifications without notice.

Literature Order Number BAS-PRB005-EN

File Number PL-ES-BAS-000-PRB005-0506

Supersedes BAS-PRB005-EN August 2004

Stocking Location Electronic onlyTraneA business of American Standard Companieswww.trane.com

For more information, contact your local Trane office or e-mail us at comfort@trane.com