Installation, Operation, and

Maintenance

Tracer™ UC600 Programmable Controller

Ordering Number: BMUC600AAA100011
Part Number: X13651548

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. When working on the equipment, observe all precautions in the literature and on the tags,
stickers, and labels that are attached to the equipment.

July 2012 BAS-SVX45C-EN

Copyright
© 2012Trane All rights reserved

This document and the information in it are the property ofTrane and may not be used
or reproduced in whole or in part, without the written permission ofTrane.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 ofTrane in the United States and other countries. All
trademarks referenced in this document are the trademarks of their respective owners.

Warnings, Cautions, and Notices

Warnings, cautions, and notices are provided in appropriate places throughout this
document:

Indicates a potentially hazardous situation which, if not avoided, could result in

WARNING death or serious injury.
Indicates a potentially hazardous situation which, if not avoided, could result in
CAUTIONs minor or moderate injury. It could also be used to alert against unsafe practices.
NOTICE: Indicates a situation that could result in equipment or property-damage only
accidents.

Revision Summary
BAS-SVX45C-EN:
• Creating and viewing Schedules
• Viewing custom graphics

© 2012Trane All rights reserved BAS-SVX45C-EN

Table of Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Expansion Module Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Hardware Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Agency Listings and Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Additional Ordering Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Dimensions and Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Location of LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mounting and Removing the UC600 Controller . . . . . . . . . . . . . . . . . . . . . . . 12
DIN Unit Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Setting Addresses using Rotary Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Setting the MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Setting the BACnet Device ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Rotary Dial Address Settings for Non-Trane Systems . . . . . . . . . . . . . . . 15

UC600 Pre-power Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Resistive Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Voltage Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Current Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Binary Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

UC600 Power Budget Check in an Un-powered State . . . . . . . . . . . . . . . . . . . . . 20

Calculating AC Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Calculating DC Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Wiring and Powering the UC600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
AC Power Warnings and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Requirements and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Wiring and Circuit Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Transformer Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Avoid Equipment Damage! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Terminal Connectors and Tug Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Wiring AC Power to the UC600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Controller Startup and Power Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
BACnet MS/TP Link Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Wiring Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Input/Output Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Providing Low-voltage Power for Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . 28

BAS-SVX45C-EN 3
 Input and Output Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Wiring Universal Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Wiring Binary Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Wiring 0–10 VDC Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Wiring 0–20 mA Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Wiring Variable Resistance Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . 32
Wiring Trane Zone Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Wiring Analog Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Wiring Binary Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Connecting Pressure Transducer Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Operation of the UC600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
LED Descriptions and Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Communication Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Output Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring the UC600 with the Tracer TU Service Tool . . . . . . . . . . . . . . . . . . . 40

Starting a Session of TU and Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Connecting Using Tracer SC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Tracer TU Installation and Connection Error Conditions . . . . . . . . . . . . . 43
Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuring the UC600 and Creating or Editing Points . . . . . . . . . . . . . . . . . 45
Configuring the UC600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Using Pre-packaged Solutions (PPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Creating or Editing Points for the UC600 . . . . . . . . . . . . . . . . . . . . . . . . . 46
Placing Points in Out-of-Service Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating Points to Monitor Device Communication and TGP2 Programs .
48
Creating Points for Timed Override (TOV) and */** Functions . . . . . . . . 49
Monitoring and Viewing the Status of the UC600 . . . . . . . . . . . . . . . . . . . . . . 52
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Setting Up and Maintaining Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Creating a Weekly Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Changing the Schedule Default Value and Adding Events . . . . . . . . . . . 56
Adding Exceptions to a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Modifying Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Deleting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Deleting Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Deleting a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Custom Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4 BAS-SVX45C-EN
 Graphics Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

UC600 Commissioning/Troubleshooting in Powered State . . . . . . . . . . . . . . . . 65

Resistive Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Voltage Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Current Inputs - Methods 1 or 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
24 Vac Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Binary Inputs, 24 Vac Detect- Methods 1 or 2 . . . . . . . . . . . . . . . . . . . . . . . . . 70
Binary Inputs- Based on Analog Output Connection . . . . . . . . . . . . . . . . . . . 70
Open-collector Based Binary Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Voltage Analog Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Current Analog Output- Methods 1 or 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Ground Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Appendix: Protocol Implementation Conformance Statement (PICS) . . . . . . . 75
Declaration of CE Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

BAS-SVX45C-EN 5
Overview
TheTracer UC600 controller (order no. BMUC600AAA100011) is a multi-purpose, programmable,
wireless-compatible device. It is designed to control the following types of equipment:
• Air-handling units (AHUs)
• Rooftop units
• Chillers
• Central heating and cooling plants
• Cooling towers
• Generic input/output (I/O) control

Specifications
The UC600 conforms to the specifications shown inTable 1.

Table 1. Specifications
Storage

Temperature: -67°F to 203°F (-55°C to 95°C)

Relative humidity: Between 5% to 95% (non-condensing)

Operating

Temperature: -40°F to 158°F (-40°C to 70°C)

Humidity: Between 5% to 95% (non-condensing)

Input: 20.4–27.6 VAC (24 VAC, ±15% nominal) 50 or 60 Hz, 26 VA

Power: (26 VA plus a maximum of 12 VA for each binary output)
Output: 24 VDC, ±10%, device max load 600 mA

Time Clock: On-board real time clock with 7 day backup

Mounting weight of controller: Mounting surface must support 1.3 lb. (0.6 kg)

Environmental rating (enclosure): NEMA 1

Installation: UL 840: Category 3

Pollution: UL 840: Degree 2

Expansion Module Requirements

If additional input or output points are needed, the XM30, XM32, and XM70 expansion modules
can be used.The UC600 controller will support up to 120 combined I/O terminations. See the
“Tracer Expansion Module IOM,” (BAS-SVX046-EN), for application and installation information.

6 BAS-SVX45C-EN
 Overview

Hardware Terminations
The UC600 supports the following hardware terminations:
• Temperature sensors (resistive and thermistor)
• Linear inputs 0–20 mA, such as humidity sensors
• Linear inputs 0–10 VDC, such as indoor air-quality sensors
• Linear outputs 0-20 mA, such as variable frequency drives
• Linear outputs 0–10 VDC, such as accuators for dampers and valves
• Pulse outputs, such as electric heat or humidifier control
• Binary outputs, such as fan start/stop.
• One 3-wire pressure transducer input

Table 2. UC600 device connections

Input/Output type Quantity Types Range Notes
10k– Type II, 10k –Type III,
Universal input Thermistor 2252– Type II, 20k – Type IV,
100 k

Resistive (Setpoint) 100 – 1M

RTD Balco™ (Ni-Fe), 1k; 385 (Pt), 1k

8
Current 0–20 mA (linear)

Voltage 0–20 VDC (linear)

Binary Dry contact

Pulse Width Accumulator Minimum 20 ms, opened or closed

Universal Input/Analog
Configure using any combination of analog or binary inputs/analog outputs
Output

10k– Type II, 10k –Type III,

Thermistor 2252– Type II, 20k – Type IV,
100 k The UC600 provides 600 mA of DC power for 0–
20 mA inputs and/or outputs, and to power
Resistive (setpoint) 100–1M expansion modules. See the power budget
RTD Balco™ (Ni-Fe), 1k; 385 (Pt), 1k
table “UC600 Power Budget Check in an Un-
powered State,” p. 20.
Current –20 mA (linear)
Inputs
Voltage 0–20 VDC (linear)

6 Binary Dry contact

Pulse Width Accumulator Minimum 20 ms, opened or closed

Current 0–20 mA @16 V

Voltage 0–10 VDC @20 mA

Outputs
12.5ms to 1 second (12.5ms
Pulse resolution), 1 second to 60 seconds
(0.5 second resolution)

Binary output 4 Relay (form A) wet 24 VAC, 0.5A maximum Ranges are given per contact.

Pressure input supplied with 5 VDC. Designed for

Pressure input 1 3-wire 0–5 inwc.
Kavlico™ pressure transducers.

Point total 19

BAS-SVX45C-EN 7
Overview

Agency Listings and Compliance

This section lists compliance with Conformity European (CE) and Underwriters Laboratories (UL)
standards for the UC600 controller:
• UL916 PAZX, Open Energy Management Equipment
• UL94-5V, Flammability
• CE Marked
• FCC Part 15, Subpart B, Class B Limit

Additional Ordering Options

Additional ordering options are available for the UC600:
• TracerTD7 Operator Display (order number: X13651571010)
• TD7 Sealed Ethernet cable (for wet environments) (order number: X19070632020)
• TD7 Display Portable Carry Case (order number: X18210613010)
• TD7 Mounting Bracket (flat surface, fixed position) (order number: X05010511010)
• Tracer XM30 expansion module (order number: X13651537010)
• Tracer XM32 expansion module (order number: X13651563010)
• Tracer XM70 expansion module (order number: X13651568010)
• Tracer BACnetTerm (2 pack) (order number X1365152401)
• Tracer Large enclosure 120 VAC with display capable door (order number: X13651552010)
• Tracer Large enclosure 230 VAC with display capable door (order number: X13651554010)
• Tracer Medium enclosure 120 VAC (order number: X13651559010)
• Tracer Medium enclosure 230 VAC (order number: X13651560010)
• Tracer Small 10" DIN Rail enclosure (order number: X19091354010)
• Power Supply 24VAC to 1.4A 24 VDC for XM modules exceeding UC600 power budget
(order number: X1365153801)
• IMC Harness (order number: S3090059462)

Required Tools
A 1/8 in. (3 mm) flat-bladed screwdriver is required to perform functions such as setting rotary
addressing switches, tightening or loosening screw terminals, and removing or repositioning the
controller on DIN rail.

8 BAS-SVX45C-EN
 Overview

Dimensions and Clearances

Figure 1. Controller dimensions

8.50 in. (215.9 mm) width (12 DIN units)*

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

* DIN Standard 43 880

Built-in Equipment for Electrical Installations,
Overall Dimensions and Related Mounting
2.17 in. Dimensions.
(55 mm) 1.73 in One DIN unit = 18 mm (0.71 in.)
(44 mm)

4.00 in.
(101.6 mm)

BAS-SVX45C-EN 9
Overview

Figure 2. DIN rail clearances

4.00 in. (101.6 mm)

Controller Height

2.0 in. (50.8 mm) 7.08 in. (180 mm)

Wiring Space Between Controllers (see note) Centerline to Centerline

Note: Allow a minimum of 2.0 in. (50.8 mm)

wiring space between controllers,
sides of controllers, and bottom of
cabinet.

Represents Terminal Connector

10 BAS-SVX45C-EN
 Overview

Location of LEDs
Light emitting diodes (LEDs) indicate the operation and communication status of the controller.
To interpret the UC600 LEDs and safely operate the UC600, see “LED Descriptions and Activities,”
p. 37.
For detailed information about wiring communication links, refer toTracer SC Unit Controller
Wiring Guide (BAS-SVN03) listed in the section, “Other Resources,” p. 74.
.
Figure 3. UC600 LEDs
Power LED

UC600

Communication status
LINK MBUS IMC
BO1 BO2 BO3 BO4
Binary output status TX

LEDs (Link, MBUS, IMC) RX

LINK
SERVICE
ACT
SERVICE TOOL

901
ADDRESS
901 901
Ethernet LEDs
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

Service button and LED

BAS-SVX45C-EN 11
Installation
This section describes how to install the UC600 onto a DIN rail and set rotary switches.

Mounting and Removing the UC600 Controller

TheTracer UC600 controller should be properly mounted on a DIN rail. Enclosure cabinets that
include DIN rails are available fromTrane. See “Additional Ordering Options,” p. 8.
To mount or remove the controller from the DIN rail, follow the illustrated instructions in Figure 4
and Figure 5, p. 13. If using a DIN rail from another manufacturer, follow the recommended
installation procedures that accompany it.
Important: When mounting the controller in a control cabinet, provide adequate spacing
between modules to allow for ventilation and heat dissipation.

Notice:
Avoid Equipment Damage
Do not use excessive force to install the controller on the DIN rail. Excessive force could result in
damage to the enclosure.

Figure 4. Mounting the UC600

To mount the UC600:

1. Hook device over top of DIN rail.

2. Gently push on lower half of device in
the direction of arrow until the release
clip clicks into place.

DIN Unit Width

The following table provides DIN unit width measurements forTrane devices.

Table 1. DIN unit width measurements

DIN Unit Width
Device Device Width (mm/in)
(1 unit = 18 mm)

Tracer SC system controller 143.6 mm/5.6 in 8

Tracer UC400 controller 143.6 mm/5.6 in 8

Tracer UC600 controller 215.9 mm/8.5 in 12

Tracer UC800 controller 71.6 mm/2.8 in 4

Tracer XM30 expansion module 53.6 mm/2.1 in 3

Tracer XM32 expansion module 71.6 mm/2.8 in 4

Tracer XM70 expansion module 215.9 mm/8.5 in 12

PM014 power supply module 107.6 mm/4.2 in 6

Tracer BACnet terminator 35.6 mm/1.4 in 2

12 BAS-SVX45C-EN
 Installation

Figure 5. Removing the UC600

To remove or reposition the controller:

1. Disconnect all connectors before removing or repositioning.

2. Insert screwdriver into slotted release clip and gently pry upward with the screwdriver to
disengage the clip.
3. While holding tension on the clip, lift device upward to remove or to reposition.
4. If repositioned, push on the device until the release clip clicks back into place to secure the
device to DIN rail.

BAS-SVX45C-EN 13
Installation

Setting Addresses using Rotary Switches

There are three rotary switches on the front of the UC600 for the purpose of defining a three-digit
address when the UC600 is installed on a BACnet communications network.The three-digit
address setting is used as both the BACnet MAC address and the BACnet device ID.

Setting the MAC Address

The MAC address is the rotary dial address. ForTrane systems, this address must be between 1 and
127. Although “0,0,0,” is a valid BACnet address,Trane reserves this address for theTracer SC
controller. For non-Trane systems, see “Rotary Dial Address Settings for Non-Trane Systems,”
p. 15. All device addresses on the BACnet MS/TP link must be unique.
• Before powering up the UC600, set the rotary address as shown in Figure 6.
• If the UC600 was previously powered up, do the following if you wish to make changes:
– Make the preferred changes to the rotary address as illustrated in Figure 6.
– Power down the UC600; when re-powered the new MAC address should be active.
Note: Valid MAC addresses used with theTracer UC600 are 001 to 120 for BACnet.

Figure 6. Setting rotary switches

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO 3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
90 1 90 1 90 1
ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

4 56 4 56 4 56

x100 x10 x1
AO1 AO2 AO3 AO4 AO5 AO6
UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

This example illustrates the

rotary switches after addresses
have been set.
Important: Each UC600 device on the BACnet link must have a unique rotary switch setting, otherwise,
communication problems will occur.

Use a 1/8 in. (3 mm) flathead

screwdriver to set rotary 901

23
78

switches. Dial rotates either 456

direction.

14 BAS-SVX45C-EN
 Installation

Setting the BACnet Device ID

The BACnet device ID uniquely identifies each BACnet device. It can range from 0 to 4194303.
Device IDs cannot be shared among devices on the same network. Each UC600 operates as a device
and requires its own device ID, which defaults to the rotary switch address settings. Refer to
Figure 7, p. 16.
There are three ways that the BACnet device ID can be set on the UC600:
• After powering up UC600 for the first time, the UC600 device ID will match the rotary address.
• When installing a UC600 on aTracer SC, the SC will soft set the BACnet device ID based on the
SC rotary address, the link number on which it is installed, and the UC600 rotary address. For
example, theTracer SC will create a BACnet device ID of 101030 under the following conditions:
– The rotary dials on the UC600 are set to 30 (0,3,0), which is also the MAC address.
– TheTracer SC address is “0,1,0”.
– The UC600 is installed on link 1.
• Soft set the BACnet device ID by using theTracerTU service tool.
The BACnet device ID is set to the UC600 MAC address on the rotary switches. If a BACnet device
ID outside of the allowed range is required, you can soft set the device ID by using theTracerTU
service tool.
Important: The UC600 BACnet device ID defaults to the value of the rotary switches if the BACnet
device ID has not been soft set. If a device ID has been soft set, the rotary switches
are no longer representative of the BACnet device ID.
Note: When integrating the UC600 with third party vendors refer to “Appendix: Protocol
Implementation Conformance Statement (PICS),” p. 69.

Rotary Dial Address Settings for Non-Trane Systems

The Max Master value defines the maximum allowable MAC address (rotary setting) on an MSTP
link.The MAC address is present in each device on the MSTP link. When the last communicating
device on the MSTP link polls for the Max Master MAC address with no response, the token rotation
will be restricted on the MSTP link.
For non-Trane systems, the Max Master value must be greater than the unique address settings
from the rotary dials. Although 999 is possible from the dials, the maximum allowed number by
BACnet is 127.
The Max Master is not adjustable inTrane SC systems. For example, if the MAC address is 101 and
the front-end system has a Max Master value of 100, the device will not be discovered.
Many systems have a minimum BACnet device ID value. Ensure that the device ID is greater than
this value.

BAS-SVX45C-EN 15
Installation

Figure 7. Rotary switch and Tracer SC addressing

ADDRESS
UC600 addressing 90 1 90 1 90 1
before installation on Tracer SC = 001 MAC: 0

2 3

2 3

2 3
7 8

7 8

7 8
Tracer SC 4 56 4 56 4 56 Device ID: 001 0 000

x100 x10 x1

ADDRESS
90 1 90 1 90 1
MAC: 1

2 3

2 3

2 3
UC600 = 001 7 8

7 8

7 8
4 56 4 56 4 56 Device ID: 000 0 001

x100 x10 x1

ADDRESS
90 1 90 1 90 1
UC600 = 002 MAC: 2
2 3

2 3

2 3
7 8

7 8

7 8
4 56 4 56 4 56 Device ID: 000 0 002

x100 x10 x1

ADDRESS
90 1 90 1 90 1
UC600 = 003 MAC: 3
2 3

2 3

2 3
7 8

7 8

7 8

4 56 4 56 4 56 Device ID: 000 0 003

x100 x10 x1

UC600 addressing after

installation on Tracer SC

MS/TP Link 1 MS/TP Link 2

Device ID Device ID
SC Link UC 90 1
ADDRESS
90 1 90 1
SC 001 90 1
ADDRESS
90 1 90 1 SC Link UC
2 3

2 3

2 3
7 8

7 8

7 8

2 3

2 3

2 3

001 1 001
7 8

7 8

7 8

4 5 6 4 5 6 4 56 Device ID = 4 5 6 4 5 6 4 56 001 2 001

Mac: 1 Mac: 1
x100 x10 x1
10000 x100 x10 x1
ADDRESS ADDRESS
90 1 90 1 90 1 90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

001 1 002
2 3

2 3

2 3
7 8

7 8

7 8

4 5 6 4 5 6 4 5 6 001 2 002
Mac: 2 4 5 6 4 5 6 4 56
Mac: 2
x100 x10 x1 x100 x10 x1
ADDRESS
ADDRESS
90 1 90 1 90 1
90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

001 1 003 001 2 003

2 3

2 3

2 3
7 8

7 8

7 8

4 5 6 4 5 6 4 56
Mac: 3 4 5 6 4 5 6 4 56
Mac: 3
x100 x10 x1
x100 x10 x1

Note: Always start rotary addressing at 1 for each link with no gaps in addresses.

16 BAS-SVX45C-EN
UC600 Pre-power Checks
To avoid equipment damage, a pre-power check for inputs and outputs is recommended before
applying power to the UC600.
Before applying power, check for the following:
• All thermistors; check for 10K by using a digital multimeter (DMM).
• Thumbwheels; range between 189  and 890 
• Binary outputs; check for any dead shorts.
• Analog outputs; verify that AC voltage is not present and that the load does not have 24 VAC
or 120 VAC.
This section provides illustrations and methods of how to check the UC600 points before
connection has been made and power applied.The step numbers in each illustration correspond
to the information in each table. (Refer to Table 2, p. 7 for a list of device connections.)
Note: The illustrations in the section, “UC600 Commissioning/Troubleshooting in Powered State,”
p. 65 show the location of the UC600.

Resistive Inputs

Checkout Procedure Measurement Expected Value

VAC 0.0 V
Step 1 Measure AC voltage across the resistive termination.
AC voltage will affect further measurement.
VDC 0.0 V
Step 2 Measure DC voltage across the resistive termination.
DC voltage will affect further measurement.
Compare the measured resistance with the
Step 3 Measure the resistance across the resistive termination. expected value based on the manufacturer’s
specification and current conditions.

BAS-SVX45C-EN 17
UC600 Pre-power Checks

Voltage Inputs

The sensor sources voltage and is powered.

Checkout Procedure Measurement Expected Value
VAC 0.0 V
Step 1 Measure AC voltage across the voltage input.
AC voltage will affect further measurement.
Compare the measured voltage with the
Step 2 Measure DC voltage across the voltage termination. expected value based on the manufacturer’s
specification and current conditions.

Current Inputs

The sensor sources 4-20 mA and is powered.

Checkout Procedure Measurement Expected Value
VAC 0.0 V
Step 1 Measure AC voltage across the current input.
AC voltage will affect further measurement.
VDC 0.0 V.
Step 2 Measure DC voltage across the current input.
DC voltage will affect further measurement.
Compare the measured current with the
Step 3 Measure the DC current across the current input. expected value based on the manufacturer’s
specification and current conditions.

18 BAS-SVX45C-EN
 UC600 Pre-power Checks

Binary Inputs

Checkout Procedure Measurement Expected Value

VAC 0.0 V
Step 1 Measure AC voltage across the resistive termination.
AC voltage will affect further measurement.
VDC 0.0 V
Step 2 Measure DC voltage across the resistive termination.
DC voltage will affect further measurements.
contact open = infinity (∞)
Step 3 Measure the resistance across the resistive termination.
contact closed = shorted (0 )

BAS-SVX45C-EN 19
UC600 Power Budget Check in an Un-powered State
This section provides information about power budget consumption for the UC600 in an
un-powered state.

Calculating AC Power Consumption

The UC600, along with the 24 VAC transformer, can draw up to 26 VA AC power. Observe the
following rules when calculating AC power:
• Each UC600 can power a maximum of two additional modules (XM30, XM32, WCI); reserve 8
VA for this application.
• Additional expansion modules require an additional power supply module (PM014).
• Each UC600 can power a maximum of 10 points, configured as 4-20 mA in/out (loop-powered).
Each of the components in the following table requires a specific amount of power (VA) from the
24 VAC transformer.The following table breaks down the power requirement for each, assuming
that:
• Universal inputs (UI) and universal input/outs (UI/O) draw at most, 20 mA.
• Binary outputs (BO) are not loaded; pilot relays are used.
• Expansion modules will draw full power.

Table 3. UC600 power draw (transformer sizing)

Quantity and Type of VA Draw Per Maximum Total VA Draw

Component Input/Output Input/Output (24 VAC)
UC600 (alone) 5.5 VA
8 Universal Inputs 0.8 VA 6.4 VA
UC600 Board 6 Universal/Analog Outputs 0.8 VA 4.8 VA
4 Binary Outputs 0.3 VA 1.2 VA
1 Pressure Input (Kavlico) 0.1 VA 0.1 VA
Subtotal for UC600 18.0 VA
Tracer TD7 display 21.0 VA
Expansion Modules (Maximum of 2) 8.0 VA
Additional 24 VAC needs, such as actuators and additional VA requirements.
Total for UC600 + expansion modules + end devices 47.0 VA + additional 24 VAC

20 BAS-SVX45C-EN
 UC600 Power Budget Check in an Un-powered State

Calculating DC Power Consumption

The UC600 is capable of providing 600 mA of power. Observe the following rules when budgeting
for DC power:
• The UC600 can power a maximum of two small modules (WCIs, expansion modules) and a
maximum of 10 points configured as 4-20 mA In/Out (loop powered), simultaneously.
• Include any additional devices where the UC600 is providing 24 VDC that are not part of the
current loop.
Use the following table to help determine your DC power supply needs.
Note: If additional 0-20 mA inputs are needed, expansion modules can be powered from a PM014
power supply module instead of the UC600. See the “Tracer Expansion Modules IOM,”
BAS-SVX46-EN, for more details.

Table 4. DC power budget worksheet

Component No. of terminations mA power draw Total mA
Base electronics 1 x 146 146
Universal inputs/outputs x 20
XM30 expansion module x 115
XM32 expansion module x 100
WCI (can be powered by 24 VAC) x 90
Additional DC powered devices 1 x (varies)
Total DC power draw must be less than 600 mA

BAS-SVX45C-EN 21
Wiring and Powering the UC600
This section describes how to wire and safely power the UC600.
Important: If problems occur after powering refer to the troubleshooting section, “UC600
Commissioning/Troubleshooting in Powered State,” p. 65.
Tip: Before powering the UC600, read sections, “UC600 Pre-power Checks,” p. 17 and “UC600
Power Budget Check in an Un-powered State,” p. 20.

AC Power Warnings and Cautions

WARNING
Hazardous Voltage!
Disconnect all electric power, including remote disconnects, before servicing. Follow proper
lockout and/or tagout procedures to ensure the power cannot be inadvertently energized.
Failure to disconnect power before servicing could result in serious injury or death.

 CAUTION
Personal Injury and Equipment Damage!
After installation, verify that the 24 VAC transformer is grounded through the controller. Failure
to do so could result in personal injury and/or damage to equipment. Measure the voltage
between chassis ground and any ground terminal on the controller. Expected result: VAC 4.0 V.
Refer to the section, “Wiring AC Power to the UC600,” p. 24.

Notice:
Equipment Damage!
Complete input/output wiring before applying power to the UC600 controller. Failure to
complete this task may cause damage to the controller or power transformer due to inadvertent
connections to power circuits. The designed units accept only copper conductors. Other types
may cause equipment damage. Do not share 24 VAC between controllers. Sharing 24 VAC power
may cause controller damage (refer to the section, “Transformer Requirements,” p. 23).

Requirements and Recommendations

Wiring and Circuit Requirements
All wiring must comply with the National Electrical Code (NEC)™ and local electrical codes.
To ensure proper operation of the UC600, observe the following guidelines:
• The controller should receive AC power from a dedicated power circuit; failure to comply may
cause the controller to malfunction.
• A dedicated power circuit disconnect switch must be near the controller, easily accessible by
the operator, and marked as the disconnecting device for the controller.
• Do not run AC power wires in the same wire bundle with input/output wires; failure to comply
may cause the controller to malfunction due to electrical noise.
• 18 AWG copper wire is recommended for the circuit between the transformer and the
controller.

22 BAS-SVX45C-EN
 Wiring and Powering the UC600

Transformer Requirements
• AC transformer requirements: UL listed, Class 2 power transformer, 24 VAC ±15%, device max
load 26 VA.The transformer must be sized to provide adequate power to the UC600 controller
(26 VA) and any external device outputs.
• DC power can be used for 4-20 mA devices and up to two expansion modules (XM30, XM32)
and one WCI.
• Include in the total power budget any devices that are powered from the 24 VAC terminal.
• CE-compliant installations:The transformer must be CE marked and SELV compliant per IEC
standards.

Avoid Equipment Damage!

Sharing 24 VAC power between controllers could cause equipment damage.

A separate transformer is recommended for each controller.The line input to the transformer must
be equipped with a circuit breaker sized to manage the maximum transformer line current.
If a single transformer is shared by multiple UC600 controllers:
• The transformer must have sufficient capacity.
• Polarity must be maintained for every UC600 controller powered by the transformer
Important: If polarity is inadvertently reversed between controllers that are powered by the
same transformer, a difference of 24 VAC will occur between the grounds of each
controller.The following symptoms could result:
–Partial or full loss of communication on the entire BACnet MS/TP link.
–Improper function of UC600 controller outputs.
–Damage to the transformer or a blown transformer fuse.

Terminal Connectors and Tug Test

When wiring to the UC600 using terminal connectors, strip the wires to expose 1/4 in. (7 mm) of
bare wire. Insert each wire into a terminal connector and tighten the terminal screw. A tug test is
recommended after tightening terminal screws to ensure all wires are secure.

Torque Reference: tighten screw terminals to 0.5 to 0.6 N-m

(71 to 85 ozf-in or 4.4 to 5.3 lbf-in)

N-m (Newton-meter)
ozf-in (ounce force-inch)
lbf-in (pound force-inch)

BAS-SVX45C-EN 23
Wiring and Powering the UC600

Wiring AC Power to the UC600

1. Connect both secondary wires from the 24 Vac transformer to the XFMR terminals on the
device.
2. Ensure the device is properly grounded.
Important: This device must be grounded for proper operation! The factory-supplied
ground wire must be connected from any chassis ground connection on the device
to an appropriate earth ground ( ).The chassis ground connection used may be the
24 Vac transformer input at the device, or any other chassis ground connection on
the device.
Note: The device is not grounded through the DIN rail connection.

Figure 8. Wiring AC power to the transformer

24 VAC
transformer

Note: A pigtail connection should be used

between the chassis ground on the device
and an earth ground, if the device is not
grounded through one leg of the
transformer wiring.

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
9 0 1 9 0 1 9 0 1
23

23

23
78

78

78

4 5 6 4 5 6 4 5 6
x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

24 BAS-SVX45C-EN
 Wiring and Powering the UC600

Controller Startup and Power Check

1. Verify that the 24 VAC connector and the chassis ground are properly wired.
2. Remove the 24 VAC connector from the UC600.
3. Remove the lockout/tagout from the line voltage power to the electrical cabinet.
4. Using a digital multimeter (DMM), verify that 24 VAC is present at the 24 VAC connector.
If voltage reading is within plus or minus 10%, connect the 24VAC connector to the transformer
XMRF input on the UC600.
The following table describes the UC600 service and power LED indicators.

Table 5. LED startup sequence

Power LED Indicates...

Solid Green Normal operation.

Blinking Red Alarm or fault is present.

Solid Red Low voltage or malfunction.

Sequence on Powerup: Illuminates red, then green.

Service LED Indicates...

Solid Green LED has been pressed and remains on until powered down.

Blinking Green Controller not accessing application software.

Not illuminated Normal operation.

Sequence on Power-up: Does not illuminate during power-up.

BAS-SVX45C-EN 25
Wiring and Powering the UC600

BACnet MS/TP Link Wiring

BACnet MS/TP link wiring must be field-supplied and installed in compliance with the National
Electrical Code and local codes. In addition, the wire must be of the following type:
low-capacitance, 18-gauge, stranded, tinned-copper, shielded, twisted-pair.
Important: BACnet links are polarity sensitive; consistent wiring polarity must be maintained
between devices.
Note: For more details on this topic, refer to theTracer SC Unit Controller Wiring Guide listed
under “Other Resources,” p. 74.
The illustration below shows an example of BACnet link wiring with a combination of UC600 and
UC400 controllers.
Note: A maximum of 20 UC600 controllers are allowed perTracer SC (10 per MSTP link).

Figure 9. BACnet link wiring

Tracer SC UC600 UC600 UC400

+ IM +
IMC + IM
VDC VDC VDC
LINK IMC LINK IMC BI LINK IMC

+
AI AI AI AI AI

P1 P1 P P
+

LINK MBUS IMC LINK MBUS IMC LINK IM

TX TX TX
RX RX
RX
LINK LINK
SERVICE SERVICE
ACT ACT SERVI

SERVICE TOOL SERVICE TOOL SERVICE TOOL

BACnet BACnet
terminator terminator

Zone sensor

26 BAS-SVX45C-EN
Wiring Inputs and Outputs
Wiring and configuration for UC600 inputs and outputs is described in this section. Refer to Table 2,
p. 7 for a complete list of device connections and descriptions of each type.
Important: If there are problems after powering, refer to the troubleshooting section, “UC600
Commissioning/Troubleshooting in Powered State,” p. 65.

Input/Output Requirements
All input/output wiring for the UC600 must meet the following requirements:
• All wiring must be in accordance with the National Electrical Code and local codes.
• Do NOT run input/output wires in the same wire bundle with AC-power wires.
• Use only 18–22 AWG (1.02 mm to 0.65 mm diameter), stranded, tinned-copper, shielded,
twisted-pair wire.
• Binary output wiring must not exceed 1,000 ft. (300 m).
• Binary input and 0–20 mA input wiring must not exceed 1,000 ft. (300 m).
• Analog and 24VDC output wiring distances are dependent on the specifications of the receiving
unit. Use shielding for analog and 24 VDC outputs.
• Thermistor input and 0–10 VDC input or output wiring must not exceed 300 ft. (100 m).

Avoid Equipment Damage!

Remove power to the UC600 controller before making input or output connections. Failure to do
so may cause damage to the controller, power transformer, or input/output devices due to
inadvertent connections to power circuits.

Table 6. Maximum wire lengths

Maximum Wire Lengths
Type Inputs Outputs
Binary 1,000 ft (300 m) 1,000 ft (300 m)
0–20 mA 1,000 ft (300 m) 1,000 ft (300 m)
0–10 VDC 300 ft (100 m) 300 ft (100 m)
Thermistor/Resistive 300 ft (100 m) Not Applicable

BAS-SVX45C-EN 27
Wiring Inputs and Outputs

Providing Low-voltage Power for Inputs/Outputs

The UC600 is capable of providing low-voltage power to the inputs/outputs. For limitations, refer
to the section, “Calculating AC Power Consumption,” p. 20.
Note: More than one input or output can receive power from a given terminal. However, the only
limitation is the total amount of supplied power.

Input and Output Wiring

Figure 10 shows an example of an input and output wiring configuration.

Figure 10. UC600 wiring example

0-10 VDC 0-20 mA

Input Sensor
Temperature
Sensor

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

0-10 VDC 0-20 mA 0-10 VDC/

output output Powered
0-20 mA
Sensor Output

(0.5 A maximum)

28 BAS-SVX45C-EN
 Wiring Inputs and Outputs

Wiring Universal Inputs

The UC600 has a total of 14 universal input and output terminals: eight universal inputs located
on the upper tier and six universal input/output terminals on the bottom tier. Refer to Table 2, p. 7
for device connections and ranges.

Wiring Binary Inputs

Binary inputs are two-state inputs, such as fan on/off or alarm resets.
1. Connect the common wire to a common terminal as shown below.
Note: Because the common terminals are in parallel, wiring can be made to any common
terminal.
2. Connect the shield wire to a common terminal at the termination board and tape it back at the
input device.
3. Connect the signal wire to an available input terminal.
4. Use theTracerTU service tool to configure the binary input that references the corresponding
hardware termination.

Figure 11. Wiring binary inputs

Binary inputs wired to universal input

Signal Tape back shield
terminations (top tier of the UC600).

Binary
Switch

Common Shield
IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

UC600

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

Binary
Switch
AO1 AO2 AO3 AO4 AO5 AO6
UI9 UI10 UI11 UI12 UI13 UI14

Signal

Binary inputs wired to analog

outputs/ universal input
Common terminations
Tape back shield (bottom tier of the UC600).

BAS-SVX45C-EN 29
Wiring Inputs and Outputs

Wiring 0–10 VDC Analog Inputs

Connect 0–10 VDC analog inputs to sensors such as indoor air quality sensors and pressure
sensors. Wiring can be done on the top tier or the bottom tier by using a combination of universal
and analog input terminations.
To wire a 0–10 VDC analog input:
1. Connect the shield wire (as common connection) to a common terminal as shown in Figure 12.
2. Connect the signal wire to an available input terminal.
3. Connect the supply wire to a 24 VDC or 24 VAC terminal as required.
4. Use theTracerTU service tool to configure the analog input that references the corresponding
hardware termination.
Figure 12. Typical wiring, 0–10 VDC
24 VDC

0-10 VDC out

Top tier wiring: Connect to any
Common universal input (UI1 through UI8).

24 24 24 +24 +24 +24

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

IMC IMC
1

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

Bottom tier wiring: Connect to any

24 VDC
AO/UI input. Connect 24 VDC wire to
0-10 VDC out
available 24 VDC on top tier.

Common

30 BAS-SVX45C-EN
 Wiring Inputs and Outputs

Wiring 0–20 mA Analog Inputs

Connect any 0–20 mA analog input to sensors such as humidity sensors and pressure sensors.
1. Connect the shield to a common terminal at the terminal board and tape it back at the input
device.
Note: Do Not use the shield as the common connection. For 3-wire applications, use a 3-
conductor cable with shield and for 2-wire applications, use a 2-conductor cable with
separate shield.
2. Connect the signal wire to an available input terminal.
3. Connect the supply wire to a 24 VDC or 24 VAC terminal as required.
4. Use theTracerTU service tool to configure the analog input that references the corresponding
hardware termination.
Figure 13. Typical wiring, 0–20 mA
24 VDC
3-wire
0-20 mA out
Top tier wiring: connect to any
UI input
Common

Tape shield back

24 VDC
2-wire

0-20 mA out

IMC 24 24 24 +24 +24

VAC VAC VAC VDC VDC
XFMR OUT MBUS OUT OUT
OUT

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

Bottom tier wiring: connect to any

AO/UI input. Connect 24 VDC wire IMC

to available 24 VDC on top tier

+24 +24 +24
UI6 UI7 UI8 VDC VDC VDC
OUT LINK IMC

24 VDC

ADDRESS

0-20 mA out
90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

4 56 4 56 4 56

3-wire
x100 x10 x1

Common
AO1 AO2 AO3 AO4 AO5 AO6
UI9 UI10 UI11 UI12 UI13 UI14

24 VDC
2-wire

0-20 mA out

Tape shield back

BAS-SVX45C-EN 31
Wiring Inputs and Outputs

Wiring Variable Resistance Analog Inputs

Variable resistance analog inputs include 10K thermistors, resistance temperature detectors (RTD,
and setpoint thumbwheels on zone sensors.To wire a variable resistance analog input:
1. Connect the shield to a common terminal at the terminal board and tape it back at the input
device.
2. Connect the signal wire to an available input terminal.
3. Use theTracerTU service tool to configure the analog input that references the corresponding
hardware termination.
Figure 14. Typical wiring, variable resistance

Temperature Sensor Signal

Common

Tape back shield

Signal
Variable
resistance

Common

AO/UI connections located on

Tape back shield the bottom tier can also be used.
Wire the same way as shown on
the top tier.
IMC 24 24 24 +24 +24 +24 IMC
VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
B O1 B O2 BO3 B O4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

4 56 4 56 4 56

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

32 BAS-SVX45C-EN
 Wiring Inputs and Outputs

Wiring Trane Zone Sensors

The table in Figure 15 shows the terminations on aTrane zone sensor and a typical UC600
application.
1. Connect the shield to a common terminal at the terminal board device.
Note: Do Not use the shield as the common connection. For 3-wire applications, use a
3-conductor cable with shield and for 2-wire applications, use a 2-conductor cable with
separate shield.
2. Connect the zone sensor wires to any available input (UI, UIO) terminals; refer to table 7 as an
example.
3. Use theTracerTU service tool to configure the analog input that references the corresponding
hardware termination.

Figure 15. Typical wiring, Trane zone sensors

Table 7. Example zone sensor terminations

Zone Sensor Zone Sensor UC600
Termination Output Termination Type Range
1 Zone Temp UI1 Thermistor 10k
2 Ground n/a n/a

Space Zone Temp

1 3 UI2 Resistive 20020k
Setpoint
2 4 Fan Mode UI3 Resistive 20020k
Setpoint
3 Note: Example hardware terminations. Any universal input or universal
input/analog output may be used for terminating zone temp, zone temp
Fan mode
4 setpoint, or fan mode.

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
B O1 BO2 BO3 BO 4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

4 56 4 56 4 56

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

BAS-SVX45C-EN 33
Wiring Inputs and Outputs

Wiring Analog Outputs

The UC600 has six analog output terminations.These outputs can be used for 0–10 VDC outputs
or 0–20 mA outputs and used to control actuators or secondary controllers.To wire an analog
output:
1. Connect the shield to a common terminal at the terminal board and tape it back at the input
device.
Note: Do Not use the shield as the common connection. For 2-wire applications, use a 2-
conductor cable with separate shield.
2. Connect the signal wire to an available output terminal.
3. Connect the supply wire to a 24 VDC or 24 VAC terminal as required.
4. Use theTracerTU service tool to configure the analog output that references the corresponding
hardware termination.
Figure 16. Typical wiring, analog outputs

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
0-20 mA ACT
SERVICE

SERVICE TOOL

ADDRESS

24 VDC
90 1 90 1 90 1
2 3

2 3

2 3
7 8

7 8

7 8

4 56 4 56 4 56

x100 x10 x1

Signal
AO1 AO2 AO3 AO4 AO5 AO6
UI9 UI10 UI11 UI12 UI13 UI14

Common BO1
RELAYS 0.5 A MAX

BO2 BO3 BO4

Tape back shield

0-10 volt Signal

Common

34 BAS-SVX45C-EN
 Wiring Inputs and Outputs

Wiring Binary Outputs

The UC600 has four binary outputs that are used as powered outputs.

Notice:
Controlling coil-based loads: Inrush current (the initial surge of a current into a load before it attains
normal operating condition) can be three times greater, or more, than the operating current.
Important: Use pilot relays for dry contact outputs for load currents greater than 0.5 amperes
and use powered outputs for load currents less than 0.5 amperes.
1. Connect the shield to a common terminal at the terminal board and tape it back at the powered
output device.
2. Connect the signal wire to an available output terminal.
3. Use theTracerTU service tool to configure the binary output for binary operation.
Figure 17. Typical wiring, relays (binary outputs)

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO 3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
9
01 0
9 1 9
01
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

Powered
Signal Pilot relay
output
(24 VAC coil)

Signal

Common

Common
Tape back shield

BAS-SVX45C-EN 35
Connecting Pressure Transducer Inputs
The UC600 is equipped with one 3-pin, 5 VDC pressure transducer input connection (P1) designed
for Kavlico pressure transducers.Transducers measure duct static pressure in UC600 equipment
(VAV AHUs) that is detected from the connected sensor (mounted near the UC600).
Important: To ensure accurate data transmission, use Kavlico pressure transducers. Contact
Trane for more details on pressure transducers.

To connect to the pressure transducer input, press the pressure transducer cable onto the pressure
input (P1). Refer to the illustration below.
IMC 24 24 24 +24 +24 +24 IMC
VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
Pressure Input P1 LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

36 BAS-SVX45C-EN
Operation of the UC600
LED Descriptions and Activities
The following table provides a description of LED activity, indicators, and troubleshooting tips.
Refer to Figure 3, p. 11, for locations of the LEDs.

Table 8. LED identification and interpretation

LED type LED activity Indicates... Troubleshooting/Notes

Solid green Normal operation
Sequence on powerup: Illuminates
Power Solid red Low voltage or malfunction
red, then flashes green, then solid green.
Blinking red Alarm or fault is present (*see note)
TX LED: Regardless of connectivity, the
Normal operation; blinks at a fixed rate when
TX (transmit) blinks green TX will blink as it searches for devices to
transferring data to other devices on the link
communicate with.
Normal operation; blinks at a fixed rate when
RX (receive) blinks yellow
receiving data from other devices on the link
Communication RX on solid (yellow) Reverse polarity is present
(Link, MBUS, IMC)
• Cycle the power to reestablish
communication.
The controller is not detecting • Verfiy that the controller is capable of
LED not illuminated
communication communicating with other devices on
the link.
• Check polarity and baud rate.
LED has been pressed and remains on until
Solid green powered down (does not affect normal
Service operation)
LED not illuminated Normal operation

Binary outputs Solid yellow Relay coil energized

(BO1 through BO4 LED not illuminated Relay coil de-energized or No command
LINK on solid (green) Valid Ethernet connection
Ethernet
ACT flickers (yellow) Data transmission and reception

Note: Points that are in an alarm state when the notification type is configured as “alarm” will
cause the power LED to flash red. If the notification type of a point is configured as “event,”
the power LED will not flash when the point is in an alarm state. Modbus is not supported
at this time.

BAS-SVX45C-EN 37
Operation of the UC600

Troubleshooting
The section provides troubleshooting solutions for problems that sometimes occur with the
UC600.

Communication Problems
Problem:The UC600 is not communicating withTracer SC, but can communicate withTracerTU
using a direct USB connection.
Possible cause:The “Soft Set Device ID” check box was unchecked after the UC600 was installed
onto theTracer SC.
Possible solution: Reinstall the UC600 device onto theTracer SC.
1. Verify that the UC600 device ID is set to the rotary address, which is found in
TracerTU/controller/controller settings/protocol.
2. Log on toTracer SC and navigate to the Devices page; select the UC600 device from the list, then
select replace from the actions button.
Alternative cause:The baud rate changed in the controller settings.
Solution: InTracerTU, open the Controller Settings page. Set the baud rate to to match the baud
rate on theTracer SC MS/TP link.
Alternate Cause:The rotary switch is not set properly or another device on the same MS/TP link
is set to the same rotary address.
Solution: Verify that the rotary address is correct. If not, change the address and cycle power. If the
device was previously installed in theTracer SC, the device may need to be "replaced" from the
Tracer SC Devices page.
Alternate Solution: If the device is set to the proper rotary address, then another device(s) could
be using the same rotary address on the MS/TP link.
1. Power down the UC600 and discover the link withTracer SC to see if a duplicate device is
present.
2. Change address of duplicate device, then reapply power the UC600.
If previously installed, the device may need to be replaced in theTracer SC.

Output Points
Problem: Output points are not being controlled by the UC600.
Possible cause:The output point was not configured properly inTracerTU.
Solution: Verify the hardware configuration inTracerTU and change as needed.
Problem:The value of an analog point reads correctly inTracerTU but does not read correctly in
theTracer SC.
Solution:Verify that the dimensionality was set properly on the point configuration page ofTU. Log
on toTracer SC and navigate to the Devices page; select the UC600 device from the list, then select
replace from the actions button.
Alternate solution: Verify that the equipment template is pointing to the proper output point in the
UC600.
Problem:The output point is out of service.
Solution: Place point in service from eitherTracerTU orTracer SC.

38 BAS-SVX45C-EN
 Operation of the UC600

Connection Problems
Problem:The UC600 is not responding, communicating, or is unable to connect withTracer SC or
theTracerTU service tool. (For more information about theTracerTU service tool, see “Configuring
the UC600 with theTracerTU ServiceTool,” p. 40.)
Possible cause: Defective application code in the controller.
Possible solution: Reload the application firmware.
1. Power down the controller (make sure to disconnect the USB cable).
2. Continuously hold down the service button pin while applying power. Press the service button
until the power LED illuminates green. Connect withTracerTU and reload the application
firmware.
Note: During the above process, the service LED will be green and the communication status LEDs
will be inactive.

BAS-SVX45C-EN 39
Configuring the UC600 with the Tracer TU Service
Tool
TheTracerTU service tool is comprised of tools that allow users to edit objects, configure
equipment, customizeTGP2 programs, and create and edit custom graphics.These functions are
performed using the Device NavigationTree and theTU Utility tab. For more detailed information
about any of these functions and theTU service tool, refer to “Other Resources,” p. 74.
Important: The UC600 is not intended to be disassembled for maintenance.
This section describes:
• Starting a session ofTU and establishing a direct USB connection.
• Establishing a connection using Ethernet or LAN.
• Checking andTransferring Application Code.
• Configuring the UC600.
• Creating and editing points for the UC600.
• Monitoring and viewing the status of the UC600.
• Backing up files and replacing corrupt files (Backup and Replace).

Starting a Session of TU and Connection

If you need to install theTU service tool, refer to theTracerTU ServiceTool Getting Started Guide
(TTU-SVN01).This document will provide information about features, capabilities, and
requirements ofTU.
To start aTU session:
1. Connect the USB cable directly from the laptop to the UC600.
Important: Observe existing USB standards for cable length. (For more information go to
informational Web sites, such as http://www.USB.org.)
When connecting to the controller for the first time, the Found New HardwareWizard appears.

Figure 18. Found New Hardware Wizard screen

2. If the UC600 appears, select Install the software automatically (Recommended) and then click
Next.
If the UC600 does not appear, repeat theTracerTU installation.

40 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

3. Click Continue Anyway if a warning message dialog box appears stating that the software has
not passed Windows Logo testing.
4. Click Finish on the final dialog box to complete the installation.
Note: If encountering an error condition or message during this installation procedure or
during the subsequent connection steps, refer to the section, “TracerTU Installation and
Connection Error Conditions,” p. 43 below for corrective actions.
5. Click either the Tracer TU desktop icon or the Tracer TU program item in theTracerTU group
on the Start menu.
TheTracerTU splash screen appears briefly followed by the Connect dialog box.

Figure 19. Connect dialog box

6. Select the Direct Connection (Via USB cable) radio button, if not already selected.

Connecting Using Tracer SC

The following instructions describe a direct connection using an Ethernet cable (Tracer SC only) or
an indirect connection using an IP address over a local area network (LAN) on which theTracer SC
resides.The UC600 must be installed in theTracer SC and communication must be up. If necessary,
refer to the “Tracer SC System Controller Installation and Setup Guide”,
BAS-SVX31.
Using an Ethernet cable or a LAN connection requires creating a facility using the Add/Edit Facility
dialog box that is accessed from the Connect dialog box.To create a facility, you must know the
IP address assigned to theTracer SC.The UC600 must also be installed onto theTracer SC in order
for theTracer SC to pass through by way of an IP address.
To connect to a controller using an Ethernet cable or LAN connection:
1. Click either the Tracer TU desktop icon or the Tracer TU program item in theTracerTU group
on the Start menu.TheTracerTU splash screen appears briefly followed by the Connect dialog
box.
2. Click Setup New and the Add/Edit Facility Information dialog box appears.

BAS-SVX45C-EN 41
Configuring the UC600 with the Tracer TU Service Tool

3. Click Add and the Add Facility dialog box appears.

Figure 20. Add/Edit Facility dialog box

4. Enter the name and IP address of theTracer SC to access and then click Save. Each created
facility is saved and can then be selected from the Connect To drop-down list.
5. Select the Connect To option and then select the new entry on the Connect To drop-down list.

Figure 21. Connect dialog box

42 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

6. Click Connect.TheTracer SC Unit Summary screen appears.

7. From the left navigation menu, click on the UC600 to which you want to connect.
Note: The UC600 must be installed in theTracer SC in order to access the device through the SC.

Figure 22. Unit summary screen

Tracer TU Installation and Connection Error Conditions

During installation or initial connection to a UC600, the user may encounter an error message or error condition.The
messages with corrective actions are listed in the following table.

Error Message/Condition Corrective Action

Respond as follows:
Install correct USB drivers using Tracer TU Setup.exe.
Does not recognize USB hardware
If the user receives this message and have the correct USB drivers installed, wait for the
UC600 to completely boot before attaching the USB cable.
The phrase Connected Local USB should appear in the lower left hand corner of the Tracer
TU screen. If it does not, the connection has been lost. Restart Tracer TU by clicking the
Tracer TU does not respond, or the screen is blank
Connection icon in the upper left of the Tracer TU window.

Open the Found New Hardware Wizard and verify that UC600 is displayed after “This
wizard helps you to install software for”.
Respond as follows:
Found New Hardware (Popup message)
If this text is displayed, then select, Install the software automatically
(Recommended). If this text does not appear, run the Tracer TU installation file, Tracer TU
Setup.exe.
Open the File Transfer Utility in the Tracer TU service tool to transfer the UC600 application
No application code present
firmware. (Refer to “Upgrading Firmware,” p. 44.)

BAS-SVX45C-EN 43
Configuring the UC600 with the Tracer TU Service Tool

Upgrading Firmware
Firmware upgrades require the use ofTracerTU (version 8.0 or higher).
To upgrade UC600 firmware:
1. ConnectTracerTU to the UC600 using a USB connection (direct connect).
It is not recommended that the firmware be updated using single-link access or connecting
through theTracer SC.
2. Click the file transfer utility icon ( ) located on the upper left portion ofTracerTU, then click
next.
3. Select the UC600 from the Selected devices box. Click next.
The Choose the Files Affected dialog box appears.
4. Click Browse, which opens the Selected files dialog box.
5. Browse to theTracerTU/Firmware/UC600 directory which is often found in My Documents.
6. Select the firmware file that has the .mod file extension. Version 2.0 firmware and higher uses
the .mod extension.
Important: Selecting a lower version of firmware will clear all configuration in the controller.

Figure 23. Browsing for UC600 firmware

7. Click open to open the file (the firmware file).

8. Click Start Transfer.Two separate series of files will begin downloading one at a time.
9. When a confirmation dialog box appears upon completion of the file transfer, click Finish.
Do not closeTracerTU or navigate away from the FileTransfer page until the FileTransfer
Confirmation dialog box appears.

44 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Configuring the UC600 and Creating or Editing Points

Configuring the UC600
Use the TU Controller Settings Utility to configure the UC600.This utility configures date and time,
units of measure, and protocol.
1. Select the Controller Settings Utility tab from the vertical tab set located on the right side of the
TU window.
Note: The content of this screen is based on the type of controller that is connected and the
system protocol used to communicate with the controller.
2. Click Date and Time to set the preferred date and time formats and then click Send to Device.
Optional: If daylight saving time is observed in the region where the UC600 resides, select the
Use Daylight SavingTime check box. Select dates and time from the drop-down lists that follow.
3. Click Units and set the preferred units of measure and then click Send to Device. (Check Modify
Default Units to change default units.)
4. Click Protocol to display a list of protocol that the UC600 uses to communicate with other
controllers. For BACnet protocol, specify the Baud Rate, click Send to Device (Figure 24).
5. If the device ID must be set manually (typically for 3rd party integrations), click Protocol again
to display its contents and click Soft Set Device ID.
6. Click Send to Device.
If a soft set Device ID is not present or to change an existing soft set Device ID, select the Soft
Set Device ID check box, enter a new ID, click Save, and then cycle the power to the controller
for changes to take effect.
To return to the rotary dial Device ID setting, click Remove Soft Set ID, click Save, and then cycle
the power to the controller for changes to take effect.

Figure 24. Configuring the date and time

BAS-SVX45C-EN 45
Configuring the UC600 with the Tracer TU Service Tool

Using Pre-packaged Solutions (PPS)

Pre-packaged solutions (PPS) is the preferred method to add pre-configured control applications
that contain:
• Point configuration
• TGP2 code
• Template forTracer SC installation
• Pre-defined custom reports
• Standard graphic for air handler unit (AHU)
PPS files for the UC600 are available for download on the My Ingersoll Rand corporate IntranetWeb
site.
To add points using PPS:
1. Navigate to the Pre-packaged Solutions page from the My Ingersoll Rand Intranet Web site:
https://home.ingerrand.com/our%20businesses/ClimateSolutions/Sales/prepackaged/Pages/
Home.aspx, or enter pre-packaged solutions in the search field.
2. Locate the UC600 PPS file, then select to save the file to your hard drive.
3. Open a session ofTracerTU.
4. Click on the File Transfer Utility
icon located in the upper left-hand side of theTU window and then click Next.
5. Click Browse and locate the PPS file that was previously saved. Highlight the file and click Open.
6. Click Start Transfer. A progress meter displays while the file downloads.
7. Navigate to the Controller Settings Utility screen and rename the controller.
8. From the Controller Settings screen, select Protocols. Verify that the Softset Device ID check
box is not checked.
9. For input and output points, verify and set the appropriate hardware references for each.
10. Commission the AHU controls as normal.
11. Discover and install PPS intoTracer SC.
The PPS AHUs should auto-install and not require a user-created template.
Note: If adding additional points into the PPS programs it is necessary to first auto-install the
device in theTracer SC in order to load the template. Upon installation, the current template
can be used as a basis for the custom template that contains the new points.This can be
done by editing the template on the Device List page on theTracer SC UI.

Creating or Editing Points for the UC600

Note: Points are not pre-configured in the UC600 controller. Refer to Table 9, p. 47 for the
maximum number of each point type that can be created in a UC600.
Use theTU Controller Settings Utility to create and edit points.
To create a point:
1. Select the Controller Settings Utility tab from the vertical tab set located on the right side of the
TU window.
2. Select the menu option for the type of point to create.
3. Click the Create New button for the type of point you want to create.
4. On the Point Configuration tab, enter a meaningful name in the Name field.
5. If expansion modules have been added, click on button in the Reference frame.The additional
points will be available in the drop-down list.

46 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

6. Continue to enter required or optional settings on the Point Configuration tab and on the Alarm
Configuration tab. (Refer toTracerTU online help for descriptions of all fields on these two
tabs.)
7. Click Save to File to save the new point configuration or click Send to Device to send the new
point configuration to the controller.

To edit, copy, or delete a point:

1. Select the Controller Settings Utility tab from the vertical tab set located on the right side of the
TU window.
2. Select the menu option for the type of point to edit.
3. Select an existing point from the Name field drop-down list.
4. Choose an action to perform.
5. Click OK to save the change.

Figure 25. Creating and editing points

Table 9. Maximum number of points supported in the UC600 by type

Point Type Point Maximum

Analog Input 160
Analog Output 80
Analog Value 160
Binary Input 160
Binary Output 80
Binary Value 160
Multistate Input 64
Multistate Output 64
Multistate Value 64

BAS-SVX45C-EN 47
Configuring the UC600 with the Tracer TU Service Tool

Placing Points in Out-of-Service Mode

Inputs/Outputs
The out-of-service mode disconnects the point from its reference, which has the following effect
on input and output points:
Inputs
An input point no longer obtains the value from its reference; however, you are allowed to write
a value to the point.This is primarily used for testing purposes.
Outputs
An outpoint point will not push (write) its value to its output reference.The value of the point can
be changed without affecting the referenced value.
Note: This will require the use of the priority table.

Values
Value objects will not accept a written value from applications on the controller, such asTGP2 or
schedules. A remote application, such asTracerTU orTracer SC, allows you to write to a value
object when out-of-service.
Note: This will require the use of the priority table.

Creating Points to Monitor Device Communication and TGP2 Programs

Multistate points can be created to monitor expansion module (XM) communication,Tracer SC
communication, andTGP2 programs as well as program states and results. When multistate input
points are created that reference these properties,TracerTU will automatically define the number
of states and the state text, based on the selected property.
Note: TracerTU Version 8.1 andTracer UC600 Version 3.34 and higher are required for this
functionality.
To create points for XM communication loss:
1. Open a session ofTracerTU.
2. Select the Controller Settings Utility tab from the vertical tab set located on the right side of the
TracerTU window.
3. Select the Multistate tab.
4. Click the Create New button.
5. On the Point Configuration tab, enter a meaningful name in the Name field.
6. Click on the button in the Reference field.The Reference dialog box appear.
7. From the Selection Tree, select the appropriate XM module located under the Device node
(Figure 26, p. 49).
After the XM is selected, Communication Status appears in the Available Properties frame.
8. Click Ok, which returns you to the Point Configuration tab. Click Ok to return to the Multistate
Point page.
9. Click Send to Device to send the new point configuration to the controller.

48 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Figure 26. Creating multistate points to monitor communication status

Select an XM
module from the
Device node

Creating Points for Timed Override (TOV) and */** Functions

Functionality forTOV and */** (thumb wheel) functions can be configured for the UC600, UC400,
and the XM70.This is required in order forTGP2 when creating programs forTOV and */***. After
creating points as described below, see “EnablingTOV and */** forTGP2 Programs,” p. 50.

To create points for TOV functions

1. Open a session ofTracerTU.
2. Select the Controller Settings Utility tab from the vertical tab set located on the right side of the
TracerTU window.
3. Select the Analog tab.
4. Click the Create New button.
5. On the Point Configuration tab, enter a meaningful name in the Name field.
6. Click on the button in the Reference field.The Reference dialog box appears.
7. Select a point to reference, then select analog value from the Available Properties frame. Click
OK.
8. In the Definition frame, select the Create an associated Multistate Input check box.
9. The required multistate input is automatically created (Figure 27, p. 50).
10. Click Send to Device to send the new point configuration to the controller.

BAS-SVX45C-EN 49
Configuring the UC600 with the Tracer TU Service Tool

Figure 27. TOV point configuration

Select
“analog
value” from Select this
the reference check box
dialog box.

To create points for the */** function

1. Complete steps 1 through 6 as described in “To create points forTOV functions,” p. 49.
2. In the Reference dialog box, select mode from the Available Properties frame. Click OK.
3. In the Definition frame, select the Create an associated Multistate Input check box.
The required multistate input is automatically created (Figure 28).
4. Click Send to Device to send the new point configuration to the controller.

Figure 28. */** point configuration

Select “mode” in
the reference
dialog box.

Multistates
for */**
mode

Enabling TOV and */** for TGP2 Programs

After creating points specifically forTOV and */** functions, you can now enable the points in the
TGP2 Editor.
To enableTOV and */** points:

50 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

1. Open up a session ofTGP2.

2. Select the point type from the left side bar; click and drag onto the editing space.
3. Right-click and then choose Block Properties from the menu.The Point Properties Dialog box
appears.
4. Use the check boxes to select eitherTOV or */**, depending on the point.
5. Click Save.
6. Continue to build theTGP2 program using the providedTGP2 Editor tools (Figure 29).
7. When finished, name and save your newTGP2 program.
Note: For additional information, see “TGP2 Applications Guide, BAS-APG008-EN.”

Figure 29. TGP2 program example

BAS-SVX45C-EN 51
Configuring the UC600 with the Tracer TU Service Tool

Monitoring and Viewing the Status of the UC600

Use the Status Utility tab to monitor and view the details of UC600 points list, alarms, and controller
status.
To monitor and view details:
1. Select the Status Utility tab from the vertical tab set located on the right side of theTU window.
Tabs are located across the top of theTU screen for analog, binary, and multistate points,
controller status, and alarms.
2. Choose and select a member tab to view its list of information such as data type, value, unit,
state, control, and details.
Note: If viewing alarm status, this tab screen displays up to 100 active alarms. Alarms
automatically reset when their condition returns to normal.

Figure 30. Viewing Tracer TU Status

52 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Backup
When you commission a system, it is strongly recommended that you create a backup file of the
initial configuration settings. If necessary, the backup file can be restored at a later date.
The backup procedure storesTGP2 files, all object configuration, setup files, and BACnet
identification files. In addition, the data log configuration is stored in the backup file (data
excluded).
To back up files from the controller:
1. Click the Backup Wizard icon in the upper left corner of theTU window.The Welcome to the
Backup Wizard opens.
2. Click Next.
The Choose From Available Devices dialog box appears.
3. Select the controller from which you will be backing up files.
4. Click Next.
The Backup File Name and Destination dialog box appears.
5. Click Browse to navigate to the directory where the backup file will be saved.
6. Click Start Backup.
A dialog box containing a progress meter appears. When the backup process is complete, a
message appears stating, “The backup is now complete. 0 errors were found”.
7. Click Close and then click Yes.

Restore
You can restore files on the controller with backup files in the event that the controller becomes
corrupt or must be replaced.
To restore files to the controller:
1. Click the File Transfer Wizard icon in the upper left corner of theTU window.The Welcome
to the File Transfer Wizard opens.
2. Click Next.
The Choose From Available Devices dialog box appears.
3. Select the controller that you will be restoring files for.
4. Click Next and then click Browse to navigate to the directory to locate the file to restore.
5. Select the last backup file on the Choose the Files Affected dialog box.
The Start Transfer button is now enabled.
6. Click Start Transfer to download the backup file to the controller.
Note: Backup files are controller dependent. Backup files made for a UC600 can only be
restored on a UC600.

BAS-SVX45C-EN 53
Configuring the UC600 with the Tracer TU Service Tool

Setting Up and Maintaining Schedules

Tracer UC600 supports three types of schedules: analog, binary, and multistate. Schedules can be
set up and maintained inTracerTU and theTracerTD7 Display (see “TracerTD7 Display,
Installation, Operation, and Maintenance, “BAS-SVX50C-EN).
Schedules are based on a series of “events” that occur on each day of the week. An event is a
change in a value at a specific time that can occur during any day of the week.
Each day is independent of the others and always begins with the schedule default value.The
schedule default value is applied to each day of the week and is the value that the schedule defaults
to at 12:00 a.m. for any given day. In addition to the schedule default, a maximum of ten unique
events can be defined for each day of week.
Note: Scheduling requires installation of UC600 version 3.0 or higher firmware.

Creating a Weekly Schedule

1. Open a session ofTracerTU.
2. Select Utilities > Equipment > Scheduling.
3. Expand one of the unused Schedule boxes.
4. Click the Edit icon on the right of the Schedule box to activate the Name and Description
fields (Figure 31).

Figure 31. Creating a new schedule

Name and
Description fields

54 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

5. Enter a schedule Name and Description.

TheType and Dimensionality boxes will be populated based on the selections you make in the
Members group box.
6. Expand the Members group box and select the PointType (Analog, Binary, or Multistate) from
the PointType drop-down list.
The point list is filtered to exclude all points other than the selected type. All members must be
the same type.
If you selected analog as the point type, specify a dimensionality from the drop-down list
(Figure 32). All analog members must have the same dimensionality.

Figure 32. Specifying member dimensionality

7. Use the arrow controls to select up to 10 members by transferring points from the All Points
box to the Selected Points box (Figure 33).
The first member added will filter the remaining list of available members to display only
members with the same point type and units.

Figure 33. Adding members

8. Click Send to Device to save the schedule. If working offline, click Save to File, which will save
the schedule to the configuration file.

BAS-SVX45C-EN 55
Configuring the UC600 with the Tracer TU Service Tool

Changing the Schedule Default Value and Adding Events

After creating a schedule and selecting the members, the next step is to determine the schedule
default value and add weekly events. An event is defined as a time-value pair.

About the Schedule Default Value

• The default value is the relinquish default value of the first specified member. However,
changing this value affects only the schedule. It does not affect the Relinquish Default value
specified in that member’s point configuration.
• The default value can be changed. (Changing the default value does not affect the actual
configured default value of the point.)
• The default value goes into effect each day at 12:00:00 a.m, provided that no other event takes
control at that time. It remains in effect until the first event occurs.
• If the schedule members are multistate points, the states of the first selected member are used
for all members.You can select a default value from these states from the drop-down list.

Changing the Schedule Default Value

1. Open the schedule that in which you want to make changes.
When a schedule is created, the only event in the schedule is the schedule default value.This
value occurs every day at midnight and cannot be removed. If the schedule default value is
edited, the value applies to each day in the schedule.
2. From the Default Value drop-down list select a different value.
3. Click Go.The new value is applied to the schedule.

Figure 34. Changing the schedule default value

56 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Adding Events
1. From the Actions drop-down list, select Add Event then click Go to display the Events dialog
box (Figure 35).
Events for a particular day can be viewed by selecting the day of the week at the top of the Add
Events dialog box (Figure 36).

Figure 35. Selecting Add Event from Actions list

2. Follow the steps in the dialog box to add events to one or more days at a time. (Events are
defined as time-value pairs.)
a. Select the day or days that share the event.
b. Set the start time and value.
c. Click Add Events to add the events to the schedule for the days selected.
Note: Verify that the events are current for each day by selecting the day of the week at the top
of the Add Events dialog box.

Figure 36. Add Events dialog box

Day being
viewed

Events for selected

day (10 maximum)

Select days to
which new events
will be applied

Time and value of

new event (allows
for a second event to
be added)

BAS-SVX45C-EN 57
Configuring the UC600 with the Tracer TU Service Tool

3. Repeat the above steps to add up to 10 events for each day of the week. Click OK to return to
the Schedules page.
To modify events on a particular day:
Select a day in the EventTable from the Add Event dialog box. Use the arrow buttons to change
the value.The new value is automatically saved.
To delete an event:
Select a day in the EventTable from the Add Event dialog box. Click the Delete button, which
removes the event from the schedule for that particular day.

Adding Exceptions to a Schedule

After you have created a schedule and have added events, you can add exceptions for holidays and
other special events. Each exception can also contain up to ten (10) of its own events.The UC600
can support up to 25 exceptions in a single schedule. However, it is not recommended to place more
than one exception on a single day.
Exceptions contain their own set of events. Exceptions can be:
• Configured for a single date or to recur on a user-defined recurrence pattern such as the third
Thursday of the month.
• Stacked on a single day, with the newest defined exception having the higher rank.
There are two main purposes for exceptions:
• To override an entire day.
• To extend or change a schedule's events over a normal daily schedule.
For a exceptions that last an entire day, you should define an exception event at midnight.The
exception then takes control of the normal daily events for the entire day.

58 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

To add exceptions:
1. Open the schedule to which you want to add exceptions.
2. From the Actions drop-down list Select Add Exceptions. Click Go to display the Add Exceptions
dialog box (Figure 37). (Or access from the Exception list page).

Figure 37. Adding exceptions

3. Select Does Not Recur for a one-time exception and then select the specific date in the Occurs
on Date fly-out calendar on the right. Otherwise, select Monthly or Yearly recurrence options
and specify the appropriate recurrence pattern on the right.
Note: Exceptions that occur on the same date each year, such as Christmas Day and NewYear’s
Day, are examples of exceptions that should be set as recurring.
4. Enter the StartTime and Value. A second event can be added by selecting the corresponding
check box.
5. Click Add Event(s).
The event(s) appear in the Exceptions list at the bottom of the dialog box.
6. Repeat steps 4 and 5 to add more events for an exception. Up to 10 events can be added.
7. Click OK when you have finished adding all exceptions and events.
Note: It is best practice to add an event at midnight to ensure that the exception is in control of
the events for the entire day.
Figure 38, p. 60 shows a typical schedule (resultant) with events and exceptions applied.
Exceptions that do not recur are identified by a downward pointing arrow icon. Exceptions
that do recur are identified by an circular arrow icon.

BAS-SVX45C-EN 59
Configuring the UC600 with the Tracer TU Service Tool

Click on day in the resultant to view all exceptions applied to the day from the highest priority to
the lowest, with normal events at the bottom.

Figure 38. Typical schedule (resultant) with events and exceptions

Weekly View

Click inside the row

of a particular day in
the schedule for an
expanded daily
view.

Expanded View (Thursday)

60 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Modifying Exceptions
1. Open the schedule containing the exception you want to modify.
2. Select an exception from those listed in the Exceptions group box.
3. From Actions drop-down list, select Modify Selected Exception, then click Go.

Figure 39. Modifying exceptions

Edit time or value

directly from
Exception list

4. Do one of the following to modify the exception:

• Change the start time and / or the value of an event.
• Add an event.
• Delete an event.
5. Click Add Event(s).
6. Repeat above steps as necessary.
7. Click OK when you have finished modifying the events.

Deleting Events
1. Open the schedule from which you want to delete events.
2. From the Actions drop-down list in the Events group box, select Modify Events and then click
Go.
3. Click the tab of the first day of the week to which the event belongs.
4. Click the Delete button in the row of the event you want to delete (Figure 39).

BAS-SVX45C-EN 61
Configuring the UC600 with the Tracer TU Service Tool

5. Repeat for all other affected days.

6. Click OK to return to the schedule.

Deleting Exceptions
1. Open the schedule containing the exception you want to delete.
2. Select an exception from those listed in the Exceptions group box.
3. From the Actions drop-down list, select Delete Selected Exception and then click Go.

Figure 40. Deleting an exception

Deleting a Schedule
1. Select Utilities > Equipment > Scheduling to display the Schedules screen.
2. Expand the Schedule box containing the schedule you want to delete.
3. From theActions drop-down list in the Scheduled Events group box, select Delete Schedule and
then click Go (Figure 41).

Figure 41. Deleting a schedule

The schedule is deleted.You can then create a new schedule with a new set of members.

Custom Graphics
Graphics can be viewed inTracerTU by accessing theTD7 operator display user interface.
To access, navigate to the Unit Summary screen. Click the Operator Display User Interface button
located on the bottom left portion of the page. It is not necessary to be connected to aTracerTD7
Display to view the interface.
Note: In order to view theTD7 operator display user interface, you must be connected to the
UC600 using a USB cable.

62 BAS-SVX45C-EN
 Configuring the UC600 with the Tracer TU Service Tool

Figure 42. Accessing the TD7 operator display user interface

Click to access the TD7

operator display

Custom graphics are created and loaded usingTracer Graphics Editor (TGE). See theTGE online
help for more information. Standard graphics are available in the most recent Pre-Packaged
Solutions (PPS) library at https://home.ingerrand.com/our%20businesses/ClimateSolutions/Sales/
prepackaged/Pages/Home.aspx.
Graphics allow you to:
• Perform overrides
• Assign a graphic as your home page
• Link to the Alarms page
• Link to a schedule
• Link to the All Points Report and Custom Reports
• Link to another graphic

BAS-SVX45C-EN 63
Configuring the UC600 with the Tracer TU Service Tool

Figure 43. Example graphic

Graphics Best Practices

Individual graphic files cannot exceed 2 megabytes (Mbs). Files that exceed 2 Mbs will cause slow
controller performance and increased graphic loading times.
Observe the following best practices:
• Use a program such as Microsoft Paint to save graphics using the following recommended
formats: png, jpg, or gif. File formats such as bitmap (bmp) result in much larger files sizes.
• Open the image using Microsoft Paint, and resize the image to smaller dimensions.
• If the image file was created by Centralized Graphics or another graphics specialist, request a
new image with a file size under 2 Mb.
Note: Verify that the image quality is acceptable after saving in one of the recommended
formats. JPG and GIF file formats use image compression which can reduce the quality
of the image.

64 BAS-SVX45C-EN
UC600 Commissioning/Troubleshooting in Powered State
This section provides instructions for testing the UC600 points after making connection and
applying power (indicated in each figure by the terminal connector and U600 label).The step
numbers or method numbers in each figure correspond to the information in each table. (Refer to
Table 2, p. 7 for a list of device connections.)
The following equipment is required in order to test inputs and outputs:
• Digital multimeter (DMM)
• Small flat-bladed screwdriver

BAS-SVX45C-EN 65
UC600 Commissioning/Troubleshooting in Powered State

Resistive Inputs

Checkout Procedure Measurement Expected Value

Vac 0.0 V
Step 1 Measure AC voltage across the resistive termination
AC voltage will affect further measurement
Step 2 Measure DC voltage across the resistive termination Refer to the charts below

Measured Voltage Across a Thermistor Input Measured Voltage Across a Thermistor Input
4 4
Voltage Measured Across Input–Vdc

Voltage Measured Across Input–Vdc

3.5 3.5

3 3

2.5 2.5

2 2

1.5 1.5

1 1

0.5 0.5

0 0
0 50 100 150 200 -40 -20 0 20 40 60 80 100

Thermistor Input–°F Thermistor Input–°C

Measured Voltage Across a Resistive Input

2.5
Voltage Measured Across Input–Vdc

Charts show
measurements 2

across thermistor
input (Fahrenheit
1.5
and Celsius) and
resistive input.
1

0.5

0
0 2 4 6 8 10 12 14 16 18 20

Resistive Input–kΩ (Ohms)

66 BAS-SVX45C-EN
 UC600 Commissioning/Troubleshooting in Powered State

Voltage Inputs

Checkout Procedure Measurement Expected Value

Measure AC voltage across the Vac 0.0 V
Step 1
voltage termination AC voltage will affect further measurement
Measure DC voltage across the
Step 2 Compare to input status in Tracer TU
voltage termination

BAS-SVX45C-EN 67
UC600 Commissioning/Troubleshooting in Powered State

Current Inputs - Methods 1 or 2

General Information Checkout Procedure Measurement Expected Value

Method 1 capitalizes on the Measure AC voltage across the Vac 0.0 V
Step 1
very low input resistance of a current input AC voltage will affect further measurement
DMM in current measurement
mode. However, this method Measure DC voltage across the Vdc 0.0 V
Step 2
affects the value that the current input DC voltage will affect further measurement.
UC600 will use while controlling
outputs. When the meter is set
to current mode, the current Measure DC current across the
Step 3 Compare to input status in Tracer TU
flowing into the UC600 circuit current input
will drop to zero or near zero.

General Information Checkout Procedure Measurement Expected Value

Method 2 is less disruptive to the Measure AC voltage across the Vac 0.0 V
Step 1
system. In voltage mode, the DMM voltage input AC voltage will affect further measurement
affects the circuit less. Additional
information is needed to translate Measure DC voltage across the
the voltage measured to current Step 2 voltage termination
Refer to the chart below
flowing through the circuit.

Measured Voltage Across a Linear Current Input

4.5
Voltage Measured Across Input–Vdc

3.5

2.5

1.5

0.5

0
0 2 4 6 8 10 12 14 16 18 20

Linear Current Input–mA

68 BAS-SVX45C-EN
 UC600 Commissioning/Troubleshooting in Powered State

24 Vac Measurement

IMC 24 24 24 +24 +24 +24 IMC

VAC VAC VAC VDC VDC VDC
XFMR OUT MBUS OUT OUT LINK IMC

UI1 UI2 UI3 UI4 UI5 UI6 UI7 UI8

P1

UC600
LINK MBUS IMC
BO1 BO2 BO3 BO4 TX
RX
LINK
SERVICE
ACT
SERVICE TOOL

ADDRESS
901 901 901
2 3

2 3

2 3
7 8

7 8

7 8

456 456 456

x100 x10 x1

AO1 AO2 AO3 AO4 AO5 AO6

UI9 UI10 UI11 UI12 UI13 UI14

RELAYS 0.5 A MAX

BO1 BO2 BO3 BO4

General Information Checkout Procedure Measurement Expected Value

Checking the voltage that powers Measure AC voltage with the
the UC600 is often a necessary step Step 1 UC600 connected. Perform this
20.0 Vac  Vac  30.0 Vac
when commissioning or measurement while the unit is
troubleshooting. Operational issues under load.
and LED operation may result in a
need to measure the input power.

When troubleshooting, it is faster to

take measurements while the load is Measure AC voltage with the
in place. If Step 1 indicates an out- UC600 unconnected. Perform this
of-specification voltage, disconnect Step 2 measurement while the unit is not
20.0 Vac  Vac  30.0 Vac
the UC600 and measure the AC under load.
voltage across the transformer.
These measurements can direct you
toward the problem source.

BAS-SVX45C-EN 69
UC600 Commissioning/Troubleshooting in Powered State

Binary Inputs, 24 Vac Detect- Methods 1 or 2

General Information and Checkout Procedure Measurement Expected Value

Method 1: Measure AC voltage across Vac 0.0 V (state = ON)
Voltage across binary input measured without reference to chassis the binary input Vac 24.0 V (state = OFF)
ground.
Method 2: Measure DC voltage across Vac 0.0 V (state = OFF)
Voltage across binary input measured with reference to chassis the binary input Vac 24.0 V (state = ON)
ground. Any connection with chassis ground symbol can serve as a
ground reference for this method.

Binary Inputs- Based on Analog Output Connection

General Information Checkout Procedure Measurement Expected Value

The UC600 analog output Measure AC voltage across the Vac 0.0 V
Step 1
connections can be binary input AC voltage will affect further measurement
configured as binary
inputs. This can be used Vdc 2.0 V (state = ON)
only with dry contact or Measure DC voltage across the
Step 2 Vdc 2.0 V (state = OFF)
open collector-type binary input
sensors.

70 BAS-SVX45C-EN
 UC600 Commissioning/Troubleshooting in Powered State

Open-collector Based Binary Sensors

Measurement Procedure Expected Value

Measure DC voltage across the binary input Vdc 0.2 V (BJT = ON)
UI: Vdc 3.3 V (BJT = OFF)
AO: Vdc 22.0 V (BJT = ON)

Open-collector based binary sensors use a bipolar junction transistor (BJT).This is a three-
terminal device in which emitter-to-collector current is controlled by base current as the
switching device in place of a relay.The term, open-collector, refers to the collector connection
on the transistor itself. Open-collector circuits are used for their low fatigue rate and quick
response relative to relay-based outputs.
The circuit within the pulse meter is completed when adding a pull-up resistance and reference
voltage. On the UC600, both universal input (UI) and analog output (AO) circuits add the
necessary resistance and voltage without external parts.
Note: The reference voltage must always be DC.
The voltage across the pulse meter terminals will bounce between Vsat (saturation voltage) of
the transistor in the pulse meter and theVref (reference voltage) provided by the UI or AO circuits
of the UC600. Most bipolar transistors have a Vsat of less than 0.2 Vdc.
The DMM sampling rate may be too slow to measure pulse meter output transitions.
Note: Check the specifications of the DMM. It may be necessary to use an oscilloscope to
measure the transition voltages.

BAS-SVX45C-EN 71
UC600 Commissioning/Troubleshooting in Powered State

Voltage Analog Output

Measurement Procedure Expected Value

Compare to the expected value
Measure DC voltage across the voltage based on request from controller.
termination This request may be based on an
override of the output value.

Current Analog Output- Methods 1 or 2

General Information and Checkout Procedure Measurement Expected Value

Method 1: Measure DC current Compare expected value based on request
Shorting the current output- this method leaves the circuit intact, across the current from controller. This request may be based
however, it will cause the vast majority of the current to flow through termination on an override of the output value.
the meter instead of the load (NOTE LOAD RESISTANCE).
Method 2: Measure DC current Compare expected value based on request
Measuring current directly- this method is most the typical way to across the current from controller. This request may be based
measure current and has the advantage of leaving the load in the loop. termination on an override of the output value.
However, the circuit must be broken when using this method.

72 BAS-SVX45C-EN
 UC600 Commissioning/Troubleshooting in Powered State

Ground Measurements

General Information and Checkout Procedure Measurement Expected Value

Method 1: Measure AC current across Vac 2.0 V
AC voltage between shield conductors and device chassis ground- the the current termination and
voltage difference between BACnet MS/TP device chassis ground connections confirm that only one end of
should be close to zero. If the voltage difference is greater that 4.0 Vac, there the shield conductor is tied
will be marginal communication or intermittent communication problems. If the to the earth ground
voltage difference is greater that 7.0 Vac, some devices will no longer
communicate.
Method 2: Measure AC current across Vac 4.0 V
AC voltage between earth ground and device chassis ground- the the current termination and (Must comply with National
chassis ground of the UC600 needs to be connected to earth ground by some confirm that only one end of Electrical Code™and local electric
route. the shield conductor is tied codes)
to the earth ground
Note: Do not assume that the building frame is a valid earth ground.
Method 3: Measure AC voltage across Vac 4.0 V
AC voltage between case (nominal chassis ground) and device chassis the current termination. For (Must comply with National
ground connector- in this illustration the connection appears as a short. this measurement, confirm Electrical trical Code™and local
However, it is possible that the chassis ground connection on the controller may that only one end of the electrical codes)
actually be connected to the equipment metal some distance away. Use this shield conductor is tied to
measurement method if there are communication issues or input stability the earth ground. Typically, this should be
problems. Vac .0 V

BAS-SVX45C-EN 73
Other Resources
For more detailed information, refer to the following documentation:
• Tracer SC System Controller Installation and Setup (BAS-SVX31)
• BACnet Best Practices andTroubleshooting Guide (BAS-SVX51-EN)
• Tracer Graphical Programming 2 (TGP2) Editor Online Help
• Tracer Graphical Programming (TGP2) Application Guide (BAS-APG008)
• TracerTU Online Help
• TracerTU ServiceTool Getting Started Guide (TTU-SVN01)
• Tracer UC600 Installation Instructions (X39641178-01)
• Tracer XM30 Expansion Module Installation Instructions (X39641148-01)
• Tracer XM32 Expansion Module Installation Instructions (X39641174-01)
• Tracer Expansion Module Installation, Operation, and Maintenance (BAS-SVX046-EN)

74 BAS-SVX45C-EN
Appendix: Protocol Implementation Conformance
Statement (PICS)
This section contains theTracer UC600 BACnet Protocol Implementation Conformance Statement (PICS).The UC600 can
be programmed with a variety of sequence of operations. All data used in the sequences are accessed through the BACnet
protocol.

Standardized Device Profile (Annex L)

BACnet Operator Workstation (B-OWS) 
BACnet Building Controller (B-BC) 
BACnet Advanced Application Controller (B-AAC) 
BACnet Application Specific Controller (B-ASC) 
BACnet Smart Sensor (B-SS) 
BACnet Smart Actuator (B-SA) 

Interoperability Building Blocks (Annex K)

Data Sharing Supported
Data Sharing-ReadProperty-B (DS-RP-B) 
Data Sharing-ReadPropertyMultiple-B (DS-RPM-B) 
Data Sharing-WriteProperty-B (DS-WP-B) 
Data Sharing-WritePropertyMultiple-B (DS-WPM-B) 
Alarm and Event Management Supported
Alarm and Event-Notification Internal-B (AE-N-I-B) 
Alarm and Event-ACKI-B (AE-ACK-B) 
Alarm and Event-Alarm Summary-B (AE-ASUM-B) 
Alarm and Event-Enrollment Summary-B (AE-ESUM-B) 
Alarm and Event-Information-B (AE-INFO-B) 
Scheduling Supported
Scheduling-Internal-B (SCHED-I-B) 
Trending Supported
Trending-viewing and Modifying Trends Internal-B (T-VMT-I-B) 
Trending-Automated Trend Retrieval-B (T-ATR-B) 
Device Management Description Supported
Device Management-Dynamic Device Binding-A (DM-DDB-A) 
Device Management-Dynamic Device Binding-B (DM-DDB-B) 
Device Management-Dynamic Object Binding-B (DM-DOB-B) 
Device Management-Device Communication Control-B (DM-DCC-B) 
Device Management-TimeSynchronization-B (DM-TS-B) 
Device Management-UTC Time Synchronization (DM-UTC-B) 
Device Management-Reinitialize Device-B (DM-RD-B) 
Device Management-Backup and Restore-B (DM-BR-B) 
Device Management-List Manipulation-B (DM-LM-B) 
Device Management-Object Creation and Deletion-B (DM-OCD-B) 

BAS-SVX45C-EN 75
 Appendix: Protocol Implementation Conformance Statement (PICS)

Segmentation Capability
Segmentation Supported
Segmented Requests/ Window Size: 1 
Segmented Responses/ Window Size: 1 

Object Types
Note: For objects that contain the Present_Value and Reliability properties, these properties are only writable when
the Out_Of_Service property isTrue.

Table 10. Descriptions and configurations

Ability Ability
Optional Properties to to
Object Type Writable Properties Required Properties Supported Create Delete
Analog Input • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name • Reliability user
• Out_Of_Service • Object_Type • Min_Pres_Value created
• Present_Value • Present_Value • Max_Pres_Value objects
• Reliability • Status_Flags • COV_Increment only
• Min_Pres_Value • Event_State • Time_Delay
• Max_Pres_Value • Out_Of_Service • Notification _Class
• COV_Increment • Units • High_Limit
• Time_Delay • Low_Limit
• Notification_Class • Deadband
• High_Limit • Limit_Enable
• Low_Limit • Event_Enable
• Deadband • Acked_Transitions
• Limit_Enable • Notify_Type
• Event_Enable • Event_Time_Stamps
• Notify_Type
Analog • Object_Name • Object_Identifier • Description Yes Yes,
Output • Description • Object_Name • Reliability user
• Out_Of_Service • Object_Type • Min_Pres-Value created
• Present_Value • Present_Value • Max_Pres_Value objects
• Reliability • Status_Flags • COV_Increment only
• Min_Pres_Value • Event_State • Time_Delay
• Max_Pres_Value • Out_Of_Service • Notification _Class
• Relinquish_Default • Units • High_Limit
• COV_Increment • Priority_Array • Low_Limit
• Time_Delay • Relinquish_Default • Deadband
• Notification_Class • Limit_Enable
• High_Limit • Event_Enable
• Low_Limit • Acked_Transitions
• Deadband • Notify_Type
• Limit_Enable • Event_Time_Stamps
• Event_Enable
• Notify_Type
Analog Value • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name • Reliability user
• Out_Of_Service • Object_Type • Priority_Array created
• Present_Value • Present_Value • Relinquish_Default objects
• Reliability • Status_Flags • COV_Increment only
• Relinquish_Default • Event_State • Time_Delay
• COV_Increment • Out_Of_Service • Notification_Class
• Time_Delay • Units • High_Limit
• Notification_Class • Low_Limit
• High_Limit • Deadband
• Low_Limit • Limit_Enable
• Deadband • Event_Enable
• Limit_Enable • Acked_Transitions
• Event_Enable • Notify_Type
• Notify_Type • Event_Time_Stamps

76 BAS-SVX45C-EN
 Appendix: Protocol Implementation Conformance Statement (PICS)

Table 10. Descriptions and configurations (continued)

Ability Ability
Optional Properties to to
Object Type Writable Properties Required Properties Supported Create Delete
Binary Input • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name • Inactive_Text user
• Out_Of_Service • Object_Type • Active_Text created
• Inactive_Text • Present_Value • Change_Of_State_Time objects
• Active_Text • Status_Flags • Change_Of_State_Count only
• Present_Value • Event_State • Time_Of_State_Count_Reset
• Reliability • Out_Of_Service • Elapsed_Active_Time
• Change_Of_State_Count • Polarity • Time_Of_Active_Time_Reset
• Elapsed_Active_Time • Time_Delay
• Time_Delay • Notification_Class
• Notification_Class • Alarm_Value
• Alarm_Value • Event_Enable
• Event_Enable • Acked_Transitions
• Polarity • Notify_Type
• Notify_Type • Event_Time_Stamps
• Reliability
Binary • Object_Name • Object_Identifier • Description Yes Yes,
Output • Description • Object_Name • Inactive_Text user
• Out_Of_Service • Object_Type • Active_Text created
• Inactive_Text • Present_Value • Change_Of_State_Time objects
• Active_Text • Status_Flags • Change_Of_State_Count only
• Present_Value • Event_State • Time_Of_State_Count_Reset
• Reliability • Out_Of_Service • Elapsed_Active_Time
• Change_Of_State_Count • Polarity • Time_Of_Active_Time_Reset
• Elapsed_Active_Time • Priority_Array • Minimum_On_Time
• Minimum_On_Time • Relinquish_Default • Minimum_Off_Time
• Minimum_Off_Time • Time_Delay
• Relinquish_Default • Notification_Class
• Time_Delay • Feedback_Value
• Notification_Class • Event_Enable
• Event_Enable • Acked_Transitions
• Notify_Type • Notify_Type
• Polarity • Event_Time_Stamps
• Reliability
Binary Value • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name • Inactive_Text user
• Out_Of_Service • Object_Type • Active_Text created
• Inactive_Text • Present_Value • Change_Of_State_Time objects
• Active_Text • Status_Flags • Change_Of_State_Count only
• Present_Value • Event_State • Time_Of_State_Count_Reset
• Reliability • Out_Of_Service • Elapsed_Active_Time
• Change_Of_State_Count • Time_Of_Active_Time_Reset
• Elapsed_Active_Time • Priority_Array
• Minimum_On_Time • Relinquish_Default
• Minimum_Off_Time • Minimum_On_Time
• Relinquish_Default • Minimum_Off_Time
• Time_Delay • Time_Delay
• Notification_Class • Notification_Class
• Alarm_Value • Alarm_Value
• Event_Enable • Event_Enable
• Notify_Type • Acked_Transitions
• Alarm_Value • Notify_Type
• Event_Time_Stamps
• Reliability
Calendar • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name user
• Date_List • Object_Type created
• Present_Value objects
• Date_List only

BAS-SVX45C-EN 77
 Appendix: Protocol Implementation Conformance Statement (PICS)

Table 10. Descriptions and configurations (continued)

Ability Ability
Optional Properties to to
Object Type Writable Properties Required Properties Supported Create Delete
Device • Object_Name • Object_Identifier • Location No No
• Location • Object_Name • Description
• Description • Object_Type • Max_Segments_Accepted
• APDU_Segment_Timeout • System_Status • APDU_Segment_Timeout
• APDU_Timeout • Vendor_Name • Max_Master
• Number_Of_APDU_Retries • Vendor_Identifier • Max_Info_Frames
• Max_Master • Model_Name • Local_Time
• Max_Info_Frames • Firmware_Revision • Local_Date
• Backup_Failure_Timeout • Application_Software_Version • UTC_Offset
• Protocol_Version • Daylight_Savings_Status
• Protocol_Revision • Configuration_Files
• Protocol_Services_Supported • Last_Restore_Time
• Protocol_Object_Types_Supported • Backup_Failure_Timeout
• Object_List • Profile_Name
• Max_APDU_Length_Accepted
• Segmentation_Supported
• APDU_Timeout
• Number_Of_APDU_Retries
• Device_Address_Binding
• Database_Revision
Event • Object_Name • Object_Identifier • None Yes Yes,
Enrollment • Notify_Type • Object_Name user
Object • Event_Parameters • Object_Type created
• Object_Property_Reference • Event_Type objects
• Event_Enable • Notify_Type only
• Notification_Class • Event_Parameters
• Object_Property_Reference
• Event_State
• Event_Enable
• Acked_Transitions
• Notification_Class
• Event_Time_Stamps
Event Log • Object_Name • Object_Identifier • None No No
Object • Enable • Object_Name
• Stop_When_Full • Object_Type
• Record_Count • Status_Flags
• Event_State
• Enable
• Stop_When_Full
• Buffer Size
• Log_Buffer
• Record_Count
• Totla_Record_Count
Multistate • Object_Name • Object_Identifier • State_Text Yes Yes,
Input • Description • Object_Name • Description user
• State_Text • Object_Type • Reliability created
• Out_Of_Service • Present_Value • Time_Delay objects
• Present_Value • Status_Flags • Notification_Class only
• Reliability • Event_State • Alarm_Values
• Time_Delay • Out_Of_Service • Fault_Values
• Notification_Class • Number_Of_States • Event_Enable
• Alarm_Values • Acked_Transitions
• Fault_Values • Notify_Type
• Number_Of_States • Event_Time_Stamps
• Event_Enable
• Notify_Type
Multistate • Object_Name • Object_Identifier • State_Text Yes Yes,
Output • Description • Object_Name • Description user
• State_Text • Object_Type • Reliability created
• Out_Of_Service • Present_Value • Time_Delay objects
• Present_Value • Status_Flags • Notification_Class only
• Reliability • Event_State • Feedback_Values
• Relinquish_Default • Out_Of_Service • Event_Enable
• Time_Delay • Number_Of_States • Acked_Transitions
• Notification_Class • Priority_Array • Notify_Type
• Event_Enable • Relinquish Default • Event_Time_Stamps
• Number_Of_States
• Notify_Type

78 BAS-SVX45C-EN
 Appendix: Protocol Implementation Conformance Statement (PICS)

Table 10. Descriptions and configurations (continued)

Ability Ability
Optional Properties to to
Object Type Writable Properties Required Properties Supported Create Delete
Multistate • Object_Name • Object_Identifier • State_Text Yes Yes,
Value • Description • Object_Name • Description user
• Number_Of_States • Object_Type • Priority_Array created
• State_Text • Present_Value • Reliability objects
• Out_Of_Service • Status_Flags • Relinquish_Default only
• Present_Value • Event_State • Time_Delay
• Reliability • Out_Of_Service • Notification_Class
• Relinquish_Default • Number_Of_States • Alarm_Values
• Time_Delay • Fault_Values
• Notification_Class • Event_Enable
• Alarm_Values • Acked_Transitions
• Fault_Values • Notify_Type
• Event_Enable • Event_Time_Stamps
• Notify_Type
Notification • Object_Name • Object_Identifier • None Yes Yes,
Class • Priority • Object_Name user
• Ack_Required • Object_Type created
• Recipient_List • Notification_Class objects
• Priority only
• Ack_Required
• Recipient_List
Schedule • Object_Name • Object_Identifier • Description Yes Yes,
• Description • Object_Name user
• Present_Value • Object_Type created
• Effective_Period • Present_Value objects
• Weekly_Schedule • Effective_Period only
• Exception_Schedule • Weekly_Schedule
• Schedule_Default • Exception_Schedule
• List_Of_Object_Property • Schedule_Default
_References • List_Of_Object_Property
• Priority_For_Writing _References
• Out-Of_Service • Priority_For-Writing
• Status_Flags
• Reliability
• Out-Of-Service
Trend • Object_Name • Object_Identifier • Start_Time Yes Yes,
• Enable • Object_Name • Stop_Time user
• Start_Time • Object_Type • Log_Device_Object_Property created
• Stop_Time • Enable • Log_Interval objects
• Log_DeviceObjectProperty • Stop_When_Full • Notification_Threshold only
• Log_Interval • Buffer_Size • Records_Since_Notification
• Stop_When_Full • Log_Buffer • Last_Notify_Record
• Buffer_Size • Record_Count • Notification_Class
• Record_Count • Total_Record_Count • Event_Enable
• Notification_Threshold • Event_State • Acked_Transitions
• Notification_Class • Logging_Type • Event_Time_Stamps
• Event_Enable • Status_Flags • Notify_Type
• Notify_Type • Event_Time_Stamps

BACnet Protocol
Data Link Layer Options
Data Link Layer Options
BACnet IP, (Annex J) 
BACnet IP, (Annex J), Foreign Device 
ISO 8802-3, Ethernet (Clause 7)(10Base2, 10Base5, 10BaseT, Fiber) 
ANSI/ATA 878.1, 2.5 Mb ARCNET (Clause 8) 
ANSI/ATA 878.1, RS-485 ARCNET (Clause 8), Baud Rate(s) 
MS/TP Master (Clause 9), Baud Rate(s): 9600, 19200, 38400, and 76800 
MS/TP Slave (Clause 9), Baud Rate(s) 
Point-to-Point, EIA 232 (Clause 10), Baud Rate(s): 9600, 19200, 38400 
Point-to-Point, Modem (Clause 10), Baud Rate(s): 9600, 19200, 38400 

BAS-SVX45C-EN 79
Appendix: Protocol Implementation Conformance Statement (PICS)

LonTalk, (Clause 11), Medium 

Other 

Device Address Binding

Is static device binding supported?  Yes  No

Networking Options
Router 
Annex H, BACnet Tunneling 
BACnet/IP Broadcast Management Device (BBMD) 
Does the BBMD Support Registrations by Foreign Devices? 

Character Sets
Indicating support for multiple characters sets does not imply that all character sets are supported simultaneously.
Maximum supported string length is 64 bytes (any character set).

ANSI X3.4 (UTF-8) 

IBM/Microsoft DBCS 
JIS C 6226 
ISO 10646 (UCS-4) 
ISO 10646 (UCS2) 
ISO 8859-1 

80 BAS-SVX45C-EN
 Declaration of CE Conformity
Manufacturer name: Trane

Manufacturer address: 3600 Pammel Creek Road

LaCrosse, WI 54601
USA

The manufacturer hereby declares that the product:

Product name: Tracer™ UC600 Unit Controller

Model numbers: X13651548

Conforms to the following standards or other normative documents:

Electrical equipment for measurement, control,

EN61326-1:2006 and laboratory use—EMC requirements, part 1:
Electromagnetic Emission: General Requirements

EN55022:2006 (CISPR
(by Council Directive 2004/108/EEC) 22:2005+A1:2005) Radiated Class B Limit (30 MHz—1000 MHz, 1 GHz—2 GHz)
Emissions

EN55022:2006 (CISPR
22:2005+A1:2005) Radiated 150 kHz—30 MHz
Emissions

Electromagnetic Immunity for Industrial: EN61326-1:2006

EN61000-4-2: 1995+A1:
(by Council Directive 89/336/EEC) 1998+A2:2001 Electrostatic 8 kV air, 4 kV contact
Discharge (ESD)

10 V/m, 80 MHz—1000 MHz

EN61000-4-3: 2002 Radiated Fields 3 V/m, 1.4 GHz—2.0 GHz
1 V/m, 2.0 GHz—2.7 GHz

I/O port, 1 kV
EN61000-4-4: 2004 Fast Transients
AC inputs and output ports, 2 kV

EN61000-4-5: 1995+A1: 2001

AC input ports (L/L), differential mode, 1 kV
Surge Transients

EN61000-4-6: 1996+A1: 2001

3 V, 0.15 MHz—80 MHz
Conducted Disturbance

EN61000-4-8: 1993+A1: 2001

30 A/m, 50 Hz
Power Frequency Magnetic Field

EN61000-4-11: Second Edition: 0% Vnom, 1 cycle; 70% Vnom, 25 cycle; 40%

2004 Voltage Dips and Interruptions Vnom, 10 cycle; 0% Vnom, 250 cycle

Where and When Issued: Electromagnetic Emission 10/01/2010

Electromagnetic Immunity 10/13/2010

Mark of Compliance: European Contact

Societe Trane (Epinal, France)
1, rue des Ameriques, B.P. 6
F-88191 Golbey Cedex, France
Phone: (33) 329.31.73.00
Fax: (33) 329.81.24.98

This document validates CE conformity of the Tracer UC600 Unit Controller

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.

© 2012Trane All rights reserved

BAS-SVX45C-EN 31 Jul 2012 We are committed to using environmentally
Supersedes BAS-SVX45B-EN (20 Dec 2011) conscious print practices that reduce waste.