Honeywell TB7200 Series Use and care manual

INTEGRATION MANUAL
Put Bar Code Here
63-4524—02
BACnet Integration Manual for
TB7200 & TB7300 Series
Thermostats
TB7200 Series
Thermostat TB7300 Series
Thermostat with
Occupancy Sensor
Contents
Product Overview .............................................................1
Compatibility .....................................................................2
Tips and Things You Need To Know .................................2
Wiring Guidelines .............................................................3
Network Configuration ......................................................5
Network Adapter ...............................................................8
Integration ........................................................................9
Troubleshooting ................................................................14
Appendix ..........................................................................15
BACnet Objects Supported ..............................................16
PRODUCT OVERVIEW
The TB7200 Series PI thermostats are designed for zoning
applications, and the TB7300 Series PI thermostats are
designed for fan coil control. Both Series are communicating
thermostats with models available in BACnet®MS/TP and
ZigBee®wireless mesh protocols and can be easily
integrated into a WEBs-AX building automation system based
on the NiagaraAX®platform.
TB7200 and TB7300 Series thermostats are compatible with
the Honeywell Occupancy Sensor Cover. Thermostats
equipped with an occupancy sensor cover provide advanced
active occupancy logic, which will automatically switch
occupancy levels from Occupied to Stand-By and Unoccupied
as required by local activity being present or not. This
advanced occupancy functionality provides advantageous
energy savings during occupied hours without sacrificing
occupant comfort. All thermostats can be ordered with or
without a factory installed PIR cover.
More information
The additional following documentation is available on
http://customer.honeywell.com.
• TB7200 Series Installation Instructions (form number 62-
2019).
• TB7300 Series Installation Instructions (form number 62-
2018).
• PIR Application Guide for TB7200 and TB7300 Series
Thermostats (form number 63-4526).

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 2
COMPATIBILITY
Honeywell TB7200 and TB7300 Series thermostat compatiblity information is provided in Table 1.
Table 1. TB7200 Series and TB7300 Series Thermostat Compatibility Information
* 128 total devices supported. One node used by controller and one for a repeater. A repeater is required if more than 64 devices
are on a bus.
TIPS AND THINGS YOU NEED TO KNOW
• Each thermostat is delivered from the factory with the default MAC address set at 254. At this value, BACnet communication is
NOT active and the device will not participate in the token pass either. The local LED status for the communication adapter at
this point is one short flash only. To enable BACnet communication, set the local MAC address configuration property of the
thermostat to any valid value from 0 to 127.
• After the initial configuration of your device and if your BAS allows you to remove objects, we suggest that you remove all the
configuration objects to prevent unnecessary polling of non used objects and to help speed up the network.
• All configuration objects are available and accessible locally from the device itself using the local configuration routine. Please
refer to the PIR Application Guide for TB7200 and TB7300 Series Thermostats (form number 63-4526).
• In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic
baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is
changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-
powering the devices will force immediate auto-bauding.
• Enumeration sets for System Mode MV16 depends on Sequence of Operation (MV15) value upon device discovery. If
required enumerations are not present, set MV15 to desired value and rediscover MV16 object. Available enumeration will
now reflect required configuration.
• Enumeration sets for MV16 depends on Fan Mode Sequence (MV58) value upon device discovery. If required enumerations
are not present, set MV58 to desired value and rediscover MV16 object. Available enumeration will now reflect required
configuration.
• Enumeration sets for MV26 and MV27 depend on Control Type (BV75) value and Pipe Number (MV52) value upon device
discovery. If required enumeration is not present, set BV75 and MV52 to desired value and rediscover MV26 and BV27 object.
Available enumeration will now reflect required configuration.
• If the device should go off-line, the following binded thermostat parameters will be released:
• Room Temperature
• Outdoor Temperature
• Occupancy
• The BACnet Data Link layer has two key parameters: the device object name and the device object ID. The device object
name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-
network). The device object ID must be unique from any other BACnet device object ID on the entire BACnet network (i.e. not
just the MS/TP sub-network).
WEBs-AX Controller Thermostats Per Controller* WEBStation-AX
WEB-2xx 126 3.0 or later
WEB-6xx 126 3.0 or later
WEB-7xx 126 3.5

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
363-4524—02
• To assign a Room Temperature (AV7) value manually, users must first enable the Override mode in the Room Temp Override
(BV8) object.
• To assign a Room Humidity (AV10) value manually, users must first enable the Override mode in the Room Humidity Override
(BV11) object.
• Device Name and Device ID properties are writable in Honeywell device object. Both properties can be renamed from any
BACnet network management tool as long as the tool itself give access to write to these properties.
WIRING GUIDELINES
Overview
Honeywell uses EIA-485 as the physical layer between their devices and supervisory controllers
For clarity we will use the term “Device” to represent any product with an active EIA-485 network connection, including Honeywell
and non-Honeywell thermostats.
Table 2. Summary of Specifications for a Honeywell EIA-485 Network
Parameter Details
Media Twisted pair 22AWG-24 AWG, shielded recommended
Characteristic Impedance 100-130 ohms
Distributed capacitance Less than 100 pF per meter (30 pF per foot)
Maximum length per segment 1200 meters (4000 feet)
Polarity Polarity sensitive
Multi-drop Daisy-chain (no T connections)
Terminations 1. TB7200, TB7300 and/or TB7600 Series thermostat devices
are installed at both ends of the MS/TP network:
120 Ohms resistor should be installed at each end.
2. A TB7200, TB7300 or TB7600 Series thermostat is installed at
one end of the MS/TP network and another device is installed
at the other end:
Install an End-Of-Line resistor value that matches the other
device’s instructions regarding the End-Of-Line resistors
3. Other devices are installed at both ends of the MS/TP
network:
Follow the other device’s instructions regarding the End-Of-Line
resistors.
Maximum number of nodes per segment 64 (Honeywell devices only)
Maximum number of nodes per network 128
Baud rate 9600, 19200, 38400, 76800 (Auto detect)

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 4
Cable Type
Honeywell recommends the use of balanced 22-24 AWG twisted pair with a characteristic impedance of 100-130 ohms,
capacitance of 30 pF/ft or lower. A braided shield is also recommended.
Impedance
A value based on the inherent conductance, resistance, capacitance and inductance that represent the impedance of an infinitely
long cable. The nominal impedance of the cable should be between 100Ωand 120Ω. However using120Ωwill result in a lighter
load on the network.
Capacitance (pF/ft)
The amount of equivalent capacitive load of the cable, typically listed in a per foot basis. One of the factors limiting total cable
length is the capacitive load. Systems with long lengths benefit from using low capacitance cable (i.e. 17pF/ft or lower).

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
563-4524—02
NETWORK CONFIGURATION
EIA-485 networks use a daisy chain configuration. A daisy chain means that there is only one main cable and every network
device is connected directly along its path.
Figure 1 illustrates two improper network configurations and the proper daisy chain configuration.
Other methods of wiring an EIA-485 network may give unreliable and unpredictable results. There are no troubleshooting
methods for these types of networks. Therefore, a great deal of site experimentation may have to be done, making this a difficult
task with no guarantee of success. Honeywell will only support daisy chain configurations.
Fig. 1. Three different network configurations: star, bus, and daisy chain.
Only the daisy chain configuration is correct for an EIA-485 network.
Maximum Number of Devices
A maximum of 64 nodes is allowed on a single daisy chain segment. A node is defined as any device (controller, thermostat,
repeater, etc.) connected to the RS485 network. Terminators do not count as a node.
NOTE: Biasing is not required with this series of devices.
To determine the number of nodes on a network, add the following:
• One node for each device, including the controller
• One node for each repeater on the chain
For the example in Figure 2, we have one node for the controller, plus 4 for the thermostats for a total of 5 nodes.
Fig. 2. Five nodes network example.
If you have more than 64 devices, then repeaters are required to extend the network.
M32571
DAISY CHAIN
CONFIGURATION
BUS CONFIGURATION
STAR CONFIGURATION
EOL
NODE 2 NODE 3 NODE 4 NODE 5
SC
EOL
NODE 1
END OF LINE RESISTOR DOES
NOT COUNT AS A NODE
M32572
LEGEND
EOL: END OF LINE RESISTOR
SC: SUPERVISORY CONTROLLER

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 6
Maximum Cable Length
The maximum length of a chain is related to its transmission speed. The longer the chain, the slower the speed. Using proper
cable, the maximum length of an EIA-485 daisy chain is 4000-ft (1200 m). This will only work reliably for data rates up to 100,000
bps. The maximum data rate is 76,800 bps for TB7200 and TB7300 Series thermostats.
If you require a maximum network length of more than 4000 feet, then repeaters are required to extend the network.
EIA-485 Repeaters
If you have more than 64 devices, or require a maximum network length of more than 4000 feet, then repeaters are required to
extend the network. The best configuration is to daisy chain the repeaters to the controller. From each of these repeaters, a
separate daisy chain will branch off. Figure 3 demonstrates a valid use of repeaters in an EIA-485 network.
Fig. 3. Correct usage – repeaters are daisy chained to the supervisory
controller and separate daisy chains branch from each repeater.
Do not install repeaters in series, as this may result in network reliability problems. Figure 4 demonstrates an incorrect use of a
repeater in an EIA-485 network.
Fig. 4. Incorrect usage – the second repeater in series may result in an unreliable system.
EOL
SC
EOL
M32573
LEGEND
EOL: END OF LINE RESISTOR
R: RS485 REPEATER
SC: SUPERVISORY CONTROLLER
EOL
R
EOLEOL
R
EOLEOL
R
EOL
EOL
SC
M32574
LEGEND
EOL: END OF LINE RESISTOR
R: RS485 REPEATER
SC: SUPERVISORY CONTROLLER
EOL
R
EOL
EOL
R
EOL
DO NOT ADD
SECOND
REPEATER
IN SERIES

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
763-4524—02
End Of Line (EOL) Resistors
MS/TP network must be properly terminated. For daisy chain configurations, you must install an EOL resistor at each end of the
daisy chain. Depending on your MS/TP network configuration, the resistance value of the EOL resistor may change:
• TB7200, TB7300, or TB7600 Series devices are installed at both ends of the MS/TP network:
• 120 Ohms resistor should be installed at each end.
• A TB7200, TB7300, or TB7600 device is installed at one end of the MS/TP network and another device is installed at the other
end:
• Install an End-Of-Line resistor value that matches the other device’s instructions regarding its EOL resistor value;
• Other devices are installed at both ends of the MS/TP network:
• Follow the other device’s instructions regarding its EOL resistor value.

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 8
NETWORK ADAPTER
The polarity of the connection to the cable is important. From one module to the other it is important that the same colored wire be
connected to “plus” or “+” and the other colored wire be connected to the “minus” or ”-“. Figure 5 shows the proper MS/TP
connections and the location of the Status LED. This Status LED may help to troubleshoot network problems.
Fig. 5. Correct MS/TP connections and location of a Status LED on a BACnet module
IMPORTANT NOTE: The Ref terminal should NEVER be used to wire shields. The 2 shields from each feed of the network
connection to a thermostat should be wired together in the back of the thermostat and properly protected to prevent any
accidental connection to the ground.
The joined shield connection should then be grounded at a SINGLE point on the whole segment. More than one ground
connection to a shielded wire may induce ground loop noises and affect communication.
Network Adapter Status LED
Table 3 shows the different possibilities with the Status LED behavior for a BACnet module.
Table 3. Status LED condition and possible solutions.
Condition of the Status LED Possible Cause Solution
•1 short blink BACnet communication NOT active at
default MAC address = 254
Change MAC address to another
value from 0 to 127
•2 short blink (no wires
connected to the module) The right module has been installed on
the right thermostat model N/A
•2 short blink (wires connected
to the module) Module is not at the same baud rate as
the network Power off and on the thermostat
•2 short blinks and a longer blink
(wires connected to the
module)
The module has detected the presence
of a network N/A
•Right after power is applied: 2
long blinks and then no blinking Polarity has been reversed at the
module Reverse polarity at the module

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
963-4524—02
INTEGRATION
Global Commands
The following figure shows which objects from the thermostat can be monitored and commanded from the BAS front-end.
Fig. 6. Global commands from a BAS front-end to a typical TB7300 Series thermostat.
GLOBAL COMMAND CONTROL LEVEL DEVICE LEVEL
BAS FRONT-END
MSTP NETWORK
GLOBAL COMMANDS ALL DEVICES
(ALL THERMOSTATS)
OUTDOOR TEMPERATURE
OUTDOOR TEMPERATURE AND OUTDOOR HUMIDITY (ENTHALPY)
OUTDOOR TEMPERATURE AND HVAC PLANT CURRENT MODE
GLOBAL COMMANDS SPECIFIC DEVICES
(SPECIFIC AREA THERMOSTATS)
SCHEDULE
SCHEDULE AND OUTDOOR TEMPERATURE
OCCUPANCY (MV18)
FAN MODE (MV17)
OCCUPIED HEATING SETPOINT (AV39)
UNOCCUPIED HEATING SETPOINT (AV43)
OCCUPIED COOLING SETPOINT (AV40)
UNOCCUPIED COOLING SETPOINT (AV44)
KEYPAD LOCKOUT (MV19)
ROOM TEMPERATURE (AV7)
AUX OUTPUT (BV14)
MCR32655
TB7300 SERIES TSTAT
OUTDOOR TEMPERATURE (AV9)
DEHUMIDIFICATION LOCKOUT (BV13)
SEQUENCE OF OPERATION (MV15)
SYSTEM MODE (AV16)
RESTRICT USER ACCESS TO THERMOSTAT
ROOM TEMPERATURE FOR TESTING AND OVERRIDE
REMOTE CONTROL OF THE AUXILIARY OUTPUT

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 10
TB7200 Integration – Graphical User Interface (GUI) objects
The following objects should be typically used in a GUI:
• Room Temperature (AV7);
• Occupied and Unoccupied Heat Setpoints (AV 39 and AV43);
• Occupied and Unoccupied Cool Setpoints (AV 40 and AV34);
• Outdoor Temperature (AV 9);
• Supply Temperature (AI12) (If available);
• Occupancy Command (MV18);
• System Mode (MV16);
• Heating Valve Status (MV26);
• Cooling Valve Status (MV28);
• PI Heating Demand (AV21)
• PI Cooling Demand (AV22)
• Window Alarm (BI 35);
• Filter Alarm (BI 36);
• Service Alarm (BI 37)
Fig. 7. Example of graphical user interface objects.

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
11 63-4524—02
TB7300 Integration – Graphical User Interface (GUI) Objects
The following objects should be typically used in a GUI:
• Room Temperature (AV7);
• Occupied and Unoccupied Heat Setpoints (AV 39 and AV43);
• Occupied and Unoccupied Cool Setpoints (AV 40 and AV34);
• Room Humidity (AV10) (If available);
• Room Humidity Setpoint (AV 71) (If available);
• Outdoor Temperature (AV 9);
• Supply Temperature (AI12) (If available);
• Occupancy Command (MV18);
• System Mode (MV16);
• Fan Mode (MV17);
• Fan Status (MV28);
• Heating Valve Status (MV26);
• Cooling Valve Status (MV28);
• PI Heating Demand (AV21);
• PI Cooling Demand (AV22);
• Window Alarm (BI 35);
• Filter Alarm (BI 36);
• Service Alarm (BI 37)
Fig. 8. Example of graphical user interface objects.

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 12
Configuration Objects
The following objects and group objects should be typically used for configuration purposes:
• General Options 1 Group GRP 45 and its complete list of objects;
• General Options 2 Group GRP 55 and its complete list of objects;
• Humidity Models Configuration Options Group GRP 69 and its complete list of objects;
• Output Configuration Options Group GRP 74 and its complete list of objects.
If your BAS allows you to remove objects, Honeywell recommends removing all configuration objects once your setup is
complete. This will prevent unnecessary network polling and traffic.
Default Device Name and default Device ID
Default Device Name is set to: Model number – MAC:
• Where MAC is the current MAC address of the device.
• Where Model number is Honeywell part number.
The device name will be upgraded as soon as there is a change to the device MAC address.
The Device Name and Device ID properties are writable in Honeywell device object. Both properties can be renamed from any
BACnet network management tool as long as the tool itself can write to these properties.
TB7200 Models
Default Device ID is set to: 72000 + MAC
• Where MAC is the current MAC address of the device.
The device ID will also be upgraded as soon as there is a change to the device’s MAC.
For example, when a TB7200F5014B thermostat with a MAC address of 41 is connected to a network, its default Device Name
will be TB7200F5x14B-41 and its default Device ID will be 72041.
TB7300 Models
Default Device ID is set to: 73000 + MAC
• Where MAC is the current MAC address of the device.
The device ID will also be upgraded as soon as there is a change to the device’s MAC.
For example, when a TB7300C5014B thermostat with a MAC address of 63 is connected to a network, its default Device Name
will be TB7300C5x14B-63 and its default Device ID will be 73063.
Integrating Honeywell Devices on an MS/TP Network
Before doing any BACnet integration, make sure to have Honeywell PICS (Protocol Implementation Conformance Statement).
This PICS document lists all the BACnet Services and Object types supported by a device and can be found at
http://customer.honeywell.com.
Honeywell devices do not support the COV service. COV reporting allows an object to send out notices when its Present-Value
property is incremented by a pre-defined value. Since this is not supported at Honeywell’s end, special attention should be given
to the polling time settings at the Supervisory Controller and Workstation level when using a graphic interface or an application
program to read or write to a Honeywell object.

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
13 63-4524—02
Graphical interfaces
For example, some graphic interface might poll every data linked to the graphic page on a COV basis. If the 3rd party device does
not support COV, the graphic interface then relies on a pre-configured polling interval, which is usually in hundredths of
milliseconds. Any device containing a monitored object could be subject to network traffic congestion if such a polling interval is
used. Honeywell strongly recommends a polling interval of 5 seconds minimum for any graphic interface. This becomes even
more critical in area graphics where a single representation might poll many devices. If proper poll rate is not respected, devices
may be reported offline by certain front end by saturating the traffic handling capacity of BACnet MS/TP without COV
subscription.
Free programmed object or loops
As for the application program, you might want to read and write any MS/TP data on an “If Once” basis or a “Do Every” loop basis
instead of reading or writing to a 3rd party device’s object directly in the program. Otherwise, any read or write request will occur
at the Supervisory Controller’s program scan rate, which might as well be in hundredths of milliseconds. This can easily bog
down a network as single commands can be sent to all ASC devices down the MS/TP trunks every hundredth of milliseconds
Programs writing to the devices should have a structure similar to the following:
Retries and Timeouts
Another thing to look for in a BACnet integration is the Device object of the Supervisory Controller (and the Operator’s
Workstation). This object contains the 2 following required properties: Retry Timeout and Number of APDU Retries.
1. The Retry Timeout property specifies the time between re-transmissions if the acknowledgement has not been received.
When you are experiencing problems with controllers dropping off-line, increasing this value may help.
2. The Number of APDU Retries property specifies the number of times unsuccessful transmissions will be repeated. If the
receiving controller has not received the transmission successfully after this many attempts, no further attempts will be
made.
For example, if one of the thermostats does not reply to a Supervisory Controller (SC) request, and the SC’s Retry Timeout is set
to 2000 msec and the Number of APDU Retries is set to 1 (still at the SC level), then the SC will send one other request, 2 sec
later. If the MS/TP device does not reply, it will be considered Off-line by the workstation.
So having a Retry Timeout value of 10000 msec and a Number of APDU Retries property set to 3 at the SC level may prevent
device from dropping Off-line. These properties should also be changed at the Workstation level since the workstation will likely
issue requests to any MS/TP devices when the graphics are used.
If Once Schedule = On then
MV13 = Occupied
End If
If Once Schedule = Off Then
MV13 = Unoccupied
End If
OR
Do Every 5min
If Schedule = On Then
MV13= Occupied
Else
MV13 = Unoccupied
End If
End Do

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 14
TROUBLESHOOTING
Error / Trouble
Condition Possible Cause Solution
Thermostat does not
come online
Two or more controllers have the same
MAC address.
Modify each duplicate address to a unique
number.
The MS/TP network has too many devices. Do not exceed the maximum number of
devices and maximum length allowed by the
EIA-485 specifications.
Too many devices were installed without
any repeaters.
Repeaters need to be installed as specified
in this document.
The MS/TP cable runs are broken Locate the break and correct wiring
MS/TP connections at the module are
reversed
Respect polarity of the wires on a MS/TP
network.
The thermostat does not have power Apply power to the thermostat

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
15 63-4524—02
APPENDIX
TB7200 & TB7300 Series Protocol Implementation Conformance Statement
(PICS)
Vendor Name: Honeywell
Product Name: TB7200 and TB7300 Series Thermostats
TB7200 Product Description
The TB7200 series BACnet communicating thermostat has been specifically designed for zoning applications to be monitored on
a BACnet MS-TP®network.
TB7200 Product Model Number: TB7200C5x14B and TB7200F5x14B
TB7300 Product Description
The TB7300 series BACnet communicating thermostat has been specifically designed for zoning and fan coil applications to be
monitored on a BACnet MS-TP®network.
TB7300 Product Model Number: TB7300A5x14B, TB7305A5x14B, TB7300C5x14B, TB7305C5x14B, TB7350C5x14B,
TB7355C5x14B, TB7300F5x14B, TB7305F5x14B, TB7350F5x14B and TB7355F5x14B
Supported BACnet Services
The BACnet communicating thermostat meets all requirements for designation as an Application Specific Controller (B-ASC).
The BACnet thermostat series supports the following BACnet Interoperability Building Blocks (BIBBs).
NOTE: The thermostat does not support segmented requests or responses.
Application Service Designation
Data Sharing – Read Property - B DS-RP-B
Data Sharing – Read Property Multiple - B DS-RPM-B
Data Sharing – Write Property - B DS-WP-B
Device Management - Device Communication Control - B DM-DCC-B
Device Management – Dynamic Device Binding - B DM-DDB-B
Device Management – Dynamic Object Binding - B DM-DOB-B

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 16
BACNET OBJECTS SUPPORTED
Device Objects
Table 4. Device Objects.
Object Name Type and
Instance Object Property Thermostat Parameter
TB7200X5x14B
TB73xxX5X14B
Device Object_Identifier
Property 75 (R,W)
Unique ID number of a device on a network.
Object_Name
Property 77 (R,W)
Unique name of a Device on a network.
Model Name
Property 70 (R)
Thermostat Model number.
Firmware Revision
Property 44 (R)
Current BACnet firmware revision used by the
thermostat.
Protocol Version
Property 98 (R)
Current BACnet firmware protocol version.
Default is Version 1.
Protocol Revision
Property 139 (R)
Current BACnet firmware protocol revision.
Default is Version 2.
Max ADPU Length
Property 62 (R)
Maximum ADPU Length accepted
Default is 244
ADPU Timeout
Property 10 (R)
ADPU timeout value
Default is 60,000 ms
Application-Software-
Version Property 12 (R)
Thermostat base application software version.
Default is based on current released version
Max_Master (R,W) Maximum master devices allowed to be part of the
network. 0 to 127, default is 127.
MS/TP_Address
Property 1001 (R,W)
BACnet MS-TP MAC Address. Proprietary attribute.
Default is as assigned by configuration.
MS/TP_Baud_Rate
Property 1002 (R,W)
BACnet MS-TP Baud-Rate. Proprietary attribute.
Range is: 1 = 9.6 KBps, 2 = 19.2 KBps, 3 = 38.4 KBps, 4
= 76.8 KBps and 5 = Auto Baud Rate. Index 5 is Write
only. Reading attribute will state current Baud rate used.
Writing index 1 to 4 will fix the Baud rate to the desired
value.

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
17 63-4524—02
Objects Table Table 5. Objects.
Object Name Type and
Instance Object Property
TB7200C5x14B
TB7200F5x14B
TB7300A5x14B TB7305A5x14B TB7300C5x14B TB7305C5x14B TB7350C5x14B TB7355C5x14B
TB7300F5x14B TB7305F5x14B TB7350F5x14B TB7355F5x14B
Room Temperature AV 7 Present_Value (R,W) √√√√√√√√√√√√
Room Temp Override BV 8 Present_Value (R,W) √√√√√√√√√√√√
Outdoor Temperature AV 9 Present_Value (R,W) √√√√√√√√√√√√
Room Humidity AV 10 Present_Value (R,W) √√ √√
Room Humid Override BV 11 Present_Value (R,W) √√ √√
Supply Temperature AI 12 Present_Value (R) √√√√√√√√√√√√
Dehumidification
Lockout BV 13 Present_Value (R,W) √√ √√
AUX Command BV 14 Present_Value (R,W) √√√√√√√√√√√√
Sequence of Operation MV 15 Present_Value (R,W) √√√√√√√√√√√√
System Mode MV 16 Present_Value (R,W) √√√√√√√√√√√√
Fan Mode MV 17 Present_Value (R,W) √√√√√√√√√√
Occupancy Command MV 18 Present_Value (R,W) √√√√√√√√√√√√
Keypad Lockout MV 19 Present_Value (R,W) √√√√√√√√√√√√
Control Output GRP 20 Present_Value (R) √√√√√√√√√√√√
PI Heating Demand AV 21 Present_Value (R) √√√√√√√√√√√√
PI Cooling Demand AV 22 Present_Value (R) √√√√√√√√√√√√
Dehumidification Status BI 23 Present_Value (R) √√ √√
Controller Status GRP 24 Present_Value (R) √√√√√√√√√√√√
AUX Status BI 25 Present_Value (R) √√√√√√√√√√√√
Heating Valve Status MV 26 Present_Value (R) √√√√√√√√
Cooling Valve Status MV 27 Present_Value (R) √√√√√√√√
Fan Status MV 28 Present_Value (R) √√√√√√√√√√
BI 1 Status BI 29 Present_Value (R) √√√√√√√√√√√√
BI 2 Status BI 30 Present_Value (R) √√√√√√√√√√√√
UI 3 Status BI 31 Present_Value (R) √√√√√√√√√√√√
Local Motion BI 32 Present_Value (R) √√√√√√√√√√√√
Effective Occupancy MV 33 Present_Value (R) √√√√√√√√√√√√
Controller Alarms GRP 34 Present_Value (R) √√√√√√√√√√√√
Window Alarm BI 35 Present_Value (R) √√√√√√√√√√√√

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 18
Filter Alarm BI 36 Present_Value (R) √√√√√√√√√√√√
Service Alarm BI 37 Present_Value (R) √√√√√√√√√√√√
Temperature Setpoints GRP 38 Present_Value (R) √√√√√√√√√√√√
Occupied Heat Setpoint AV 39 Present_Value (R,W) √√√√√√√√√√√√
Occupied Cool Setpoint AV 40 Present_Value (R,W) √√√√√√√√√√√√
Stand-by Heat Setpoint AV 41 Present_Value (R,W) √√√√√√√√√√√√
Stand-by Cool Setpoint AV 42 Present_Value (R,W) √√√√√√√√√√√√
Unoccupied Heat
Setpoint AV 43 Present_Value (R,W) √√√√√√√√√√√√
Unoccupied Cool
Setpoint AV 44 Present_Value (R,W) √√√√√√√√√√√√
General Options 1 GRP 45 Present_Value (R) √√√√√√√√√√√√
BI 1 Configuration MV 46 Present_Value (R,W) √√√√√√√√√√√√
BI 2 Configuration MV 47 Present_Value (R,W) √√√√√√√√√√√√
UI 3 configuration MV 48 Present_Value (R,W) √√√√√√√√√√√√
Menu Scroll BV 49 Present_Value (R,W) √√√√√√√√√√√√
Auto Mode Enable BV 50 Present_Value (R,W) √√√√√√√√√√
Temperature Scale BV 51 Present_Value (R,W) √√√√√√√√√√√√
Pipe Number MV 52 Present_Value (R,W) √√√√√√√√√√
Out#1 Config MV 53 Present_Value (R,W) √√
AUX Configuration MV 54 Present_Value (R,W) √√√√√√√√√√√√
General Options 2 GRP 55 Present_Value (R) √√√√√√√√√√√√
Password Value AV 56 Present_Value (R,W) √√√√√√√√√√√√
Fan Mode Sequence MV 58 Present_Value (R,W) √√√√√√√√√√
Heating Setpoint Limit AV 58 Present_Value (R,W) √√√√√√√√√√√√
Cooling Setpoint Limit AV 59 Present_Value (R,W) √√√√√√√√√√√√
Setpoint Type BV 60 Present_Value (R,W) √√√√√√√√√√√√
Setpoint Function BV 61 Present_Value (R,W) √√√√√√√√√√
Temporary Occupancy
Time MV 62 Present_Value (R,W) √√√√√√√√√√√√
Deadband AV 63 Present_Value (R,W) √√√√√√√√√√√√
Reheat Time Base BV 64 Present_Value (R,W) √√√√√√√√√√√√
Table 5. Objects. (Continued)
Object Name Type and
Instance Object Property
TB7200C5x14B
TB7200F5x14B
TB7300A5x14B TB7305A5x14B TB7300C5x14B TB7305C5x14B TB7350C5x14B TB7355C5x14B
TB7300F5x14B TB7305F5x14B TB7350F5x14B TB7355F5x14B

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
19 63-4524—02
Proportional Band MV 65 Present_Value (R,W) √√√√√√√√√√√√
Auto Fan BV 66 Present_Value (R,W) √√√√√√√√√√
Stand-by Time AV 67 Present_Value (R,W) √√√√√√√√√√√√
Unoccupied Time AV 68 Present_Value (R,W) √√√√√√√√√√√√
Humidity Models
Configuration Options GRP 69 Present_Value (R) √ √ √ √
RH Display BV 70 Present_Value (R,W) √√ √√
RH Setpoint AV 71 Present_Value (R,W) √√ √√
Dehumidification
Hysterisys AV 72 Present_Value (R,W) √√ √√
Dehumidification MAX
Cooling AV 73 Present_Value (R,W) √√ √√
Output Configuration
Options GRP 74 Present_Value (R) √√√√√√√√√√√√
Control type BV 75 Present_Value (R,W) √√√√√
Floating Motor timing MV 76 Present_Value (R,W) √√√√√
On Off Control CPH MV 77 Present_Value (R,W) √√√√√√√
Direct Reverse Acting BV 78 Present_Value (R,W) √√√√√
Table 5. Objects. (Continued)
Object Name Type and
Instance Object Property
TB7200C5x14B
TB7200F5x14B
TB7300A5x14B TB7305A5x14B TB7300C5x14B TB7305C5x14B TB7350C5x14B TB7355C5x14B
TB7300F5x14B TB7305F5x14B TB7350F5x14B TB7355F5x14B

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS
63-4524—02 20
Standard Object Types Supported
Table 6. Standard object types supported.
aPresent_Value and Out_of_Service properties are writable for every AV objects except :
• PI Heating Demand (AV21)
• PI Cooling Demand (AV22)
bPresent_Value property for Room Temperature (AV7) and Room Humidity (AV10) is writable only if Room Temp
Override (BV8) is enabled and Room Humidity Override (BV11) is enabled respectively.
cObject_Name property is writable for the following object only :
• Room Temperature (AV7)
dPresent_Value and Out_of_Service properties are writable for every MV objects except :
• Heating Valve Status (MV26)
• Cooling Valve Status (MV27)
• Fan Status (MV28)
• Effective Occupancy (MV33)
List of Proprietary Properties
Table 7. Proprietary Properties.
Object Type Supported
Objects Dynamically Creatable Dynamically Deletable
Optional
Properties
Supported Writable Properties
Analog Input ; 
Reliability Out_of_Service
Analog Value ; 
Reliability
Present_Valuea,b
Out_of_Servicea
Object_Namec
Binary Input ; 
Reliability
Active_Text
Inactive_Text
Out_of_Service
Binary Value ; 
Reliability
Active_Text
Inactive_Text
Present_Value
Out_of_Service
Device ; 
Max_Master
Max_Info_frames
Object_Identifier
Object_name
Max_Master
Group ;  N/A N/A
Multi-state Value ; 
Reliability
States_Text
Present_Valued
Out_of_Serviced
Property name ID BACnet Data type Description
Major_Version 1000 CharacterString The version number of the BACnet communications
module. This is the hardware version number
MS/TP_Address 1001 Unsigned Display the MAC layer address of the module
MS/TP_Baud_Rate 1002 Unsigned Display the communication baud rate of the module
Sensor_Offset 1005 REAL
Display the temperature or humidity calibration value.
The range is –5.0 deg F to 5.0 deg F for a temperature
and –15% to 15% for humidity.