Honeywell TB7200 Series Integration Manual

BACnet Integration Manual for

TB7200 & TB7300 Series

Thermostats

INTEGRATION MANUAL

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).

TB7200 Series

Thermostat

TB7300 Series

Thermostat with

Occupancy Sensor

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 automation system based on the NiagaraAX

®

MS/TP protocol and can be easily integrated into a WEBs-AX building

®

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.

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

63-4524-03

BACNET INTEGRATION MANUAL FOR TB7200 & TB7300 SERIES THERMOSTATS

COMPATIBILITY

Honeywell TB7200 and TB7300 Series thermostat compatiblity information is provided in Table 1.

Table 1. TB7200 Series and TB7300 Series Thermostat Compatibility Information

WEBs-AX Controller

WEB-2xx

WEB-6xx

WEB-7xx

Thermostats Per Controller*

126

126

126

3.0 or later

3.0 or later

3.5

WEBStation-AX

* 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. Repowering 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 subnetwork). 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).

• To assign a Room Temperature (AV7) value manually, users must first enable the Override mode in the Room Temp Override

(BV8) 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.

63-4524—03 2


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

Media

Characteristic Impedance

Distributed capacitance

Maximum length per segment

Polarity

Multi-drop

Terminations

Details

Twisted pair 22AWG-24 AWG, shielded recommended

100-130 ohms

Less than 100 pF per meter (30 pF per foot)

1200 meters (4000 feet)

Polarity sensitive

Daisy-chain (no T connections)

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.

Maximum number of nodes per segment

Maximum number of nodes per network

Baud rate

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.

64 (Honeywell devices only)

128

9600, 19200, 38400, 76800 (Auto detect)

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).

3 63-4524—03


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.

STAR CONFIGURATION BUS CONFIGURATION

DAISY CHAIN

CONFIGURATION

M32571

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.

EOL

END OF LINE RESISTOR DOES

NOT COUNT AS A NODE

EOL

SC

NODE 2 NODE 3 NODE 4 NODE 5

NODE 1

LEGEND

EOL: END OF LINE RESISTOR

SC: SUPERVISORY CONTROLLER

M32572

Fig. 2. Five nodes network example.

If you have more than 64 devices, then repeaters are required to extend the network.

63-4524—03 4


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.

EOL EOL EOL

R

SC

EOL

R

EOL

EOL

EOL

R

EOL

LEGEND


R: RS485 REPEATER


M32573

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.

SC

EOL

R

EOL

EOL

DO NOT ADD

SECOND

REPEATER

IN SERIES

EOL

R

EOL

LEGEND


R: RS485 REPEATER


M32574

Fig. 4. Incorrect usage – the second repeater in series may result in an unreliable system.

5 63-4524—03


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.

63-4524—03 6


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

• 2 short blink (no wires connected to the module)

• 2 short blink (wires connected to the module)

BACnet communication NOT active at default MAC address = 254

The right module has been installed on the right thermostat model

Module is not at the same baud rate as the network

• 2 short blinks and a longer blink

(wires connected to the module)

• Right after power is applied: 2 long blinks and then no blinking

The module has detected the presence of a network

Polarity has been reversed at the module

Change MAC address to another value from 0 to 127

N/A

Power off and on the thermostat

N/A

Reverse polarity at the module

7 63-4524—03


INTEGRATION

Global Commands

The following figure shows which objects from the thermostat can be monitored and commanded from the BAS front-end.

GLOBAL COMMANDS ALL DEVICES

(ALL THERMOSTATS)

OUTDOOR TEMPERATURE

OUTDOOR TEMPERATURE AND HVAC PLANT CURRENT MODE

GLOBAL COMMANDS SPECIFIC DEVICES

(SPECIFIC AREA THERMOSTATS)

SCHEDULE

SCHEDULE AND OUTDOOR TEMPERATURE

OUTDOOR TEMPERATURE (AV9)

SEQUENCE OF OPERATION (MV15)

SYSTEM MODE (AV16)

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)

RESTRICT USER ACCESS TO THERMOSTAT

ROOM TEMPERATURE FOR TESTING AND OVERRIDE

REMOTE CONTROL OF THE AUXILIARY OUTPUT

MSTP NETWORK

BAS FRONT-END

GLOBAL COMMAND CONTROL LEVEL

TB7300 SERIES TSTAT

DEVICE LEVEL

Fig. 6. Global commands from a BAS front-end to a typical TB7300 Series thermostat.

M32655A

63-4524—03 8


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.

9 63-4524—03


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);

• 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)

63-4524—03

Fig. 8. Example of graphical user interface objects.

10


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;

• 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


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


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.

11 63-4524—03


Graphical interfaces

For example, some graphic interface might poll every data linked to the graphic page on a COV basis. If the 3 rd

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 3 rd

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:

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

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.

63-4524—03 12

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.

The MS/TP cable runs are broken

Repeaters need to be installed as specified in this document.

Locate the break and correct wiring

MS/TP connections at the module are reversed

The thermostat does not have power

Respect polarity of the wires on a MS/TP network.

Apply power to the thermostat

13 63-4524—03


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, TB7300F5x14B, and

TB7305F5x14B

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).

Application Service

Data Sharing – Read Property - B

Data Sharing – Read Property Multiple - B

Data Sharing – Write Property - B

Device Management - Device Communication Control - B

Device Management – Dynamic Device Binding - B

Device Management – Dynamic Object Binding - B

Designation

DS-RP-B

DS-RPM-B

DS-WP-B

DM-DCC-B

DM-DDB-B

DM-DOB-B

NOTE: The thermostat does not support segmented requests or responses.

63-4524—03 14


BACNET OBJECTS SUPPORTED

Device Objects

Object Name

TB7200X5x14B

TB73xxX5X14B

Table 4. Device Objects.

Type and

Instance

Device

Object Property

Object_Identifier

Property 75 (R,W)

Object_Name

Property 77 (R,W)

Model Name

Property 70 (R)

Firmware Revision

Property 44 (R)

Protocol Version

Property 98 (R)

Protocol Revision

Property 139 (R)

Max ADPU Length

Property 62 (R)

ADPU Timeout

Property 10 (R)

Application-Software-

Version Property 12 (R)

Thermostat Parameter

Unique ID number of a device on a network.

Unique name of a Device on a network.

Thermostat Model number.

Current BACnet firmware revision used by the thermostat.

Current BACnet firmware protocol version.

Default is Version 1.

Current BACnet firmware protocol revision.

Default is Version 2.

Maximum ADPU Length accepted

Default is 244

ADPU timeout value

Default is 60,000 ms

Thermostat base application software version.

Default is based on current released version

Max_Master (R,W)

MS/TP_Address

Property 1001 (R,W)

MS/TP_Baud_Rate

Property 1002 (R,W)

Maximum master devices allowed to be part of the network. 0 to 127, default is 127.

BACnet MS-TP MAC Address. Proprietary attribute.

Default is as assigned by configuration.

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.

15 63-4524—03


Objects Table

Table 5. Objects.

Object Name

Type and

Instance

Object Property

Room Temperature

Room Temp Override

Outdoor Temperature

Supply Temperature

AUX Command

Sequence of Operation

System Mode

Fan Mode

Occupancy Command

Keypad Lockout

Control Output

PI Heating Demand

PI Cooling Demand

Controller Status

AUX Status

Heating Valve Status

Cooling Valve Status

Fan Status

BI 1 Status

BI 2 Status

UI 3 Status

Local Motion

Effective Occupancy

Controller Alarms

Window Alarm

Filter Alarm

Service Alarm

GRP 20

AV 21

AV 22

GRP 24

BI 25

MV 26

MV 27

MV 28

BI 29

BI 30

BI 31

BI 32

MV 33

GRP 34

BI 35

BI 36

BI 37

AV 7

BV 8

AV 9

AI 12

BV 14

MV 15

MV 16

MV 17

MV 18

MV 19

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

Present_Value (R)

Present_Value (R)

Present_Value (R)

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

Present_Value (R)

Present_Value (R)

Present_Value (R)

Present_Value (R)

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

63-4524—03 16


Table 5. Objects. (Continued)

Object Name

Type and

Instance

Object Property

Temperature Setpoints

Occupied Heat Setpoint

Occupied Cool Setpoint

Stand-by Heat Setpoint

GRP 38

AV 39

AV 40

AV 41

Stand-by Cool Setpoint AV 42

Unoccupied Heat Setpoint AV 43

Unoccupied Cool Setpoint AV 44

General Options 1

BI 1 Configuration

BI 2 Configuration

UI 3 configuration

Menu Scroll

Auto Mode Enable

Temperature Scale

Pipe Number

Out#1 Config

AUX Configuration

General Options 2

Password Value

Fan Mode Sequence

Heating Setpoint Limit

Cooling Setpoint Limit

Setpoint Type

Setpoint Function

Temporary Occupancy

Time

Deadband

Reheat Time Base

Proportional Band

Auto Fan

Stand-by Time

Unoccupied Time

MV 62

AV 63

BV 64

MV 65

BV 66

AV 67

AV 68

GRP 55

AV 56

MV 58

AV 58

AV 59

BV 60

BV 61

GRP 45

MV 46

MV 47

MV 48

BV 49

BV 50

BV 51

MV 52

MV 53

MV 54

Present_Value (R)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

Present_Value (R)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √

√ √ √ √ √ √ √ √

Present_Value (R)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √

√ √ √ √ √ √ √ √

√ √ √ √ √ √ √ √

17 63-4524—03


Table 5. Objects. (Continued)

Object Name

Type and

Instance

Object Property

Output Configuration

Options

Control type

Floating Motor timing

On Off Control CPH

Direct Reverse Acting

GRP 74

BV 75

MV 76

MV 77

BV 78

Present_Value (R)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

Present_Value (R,W)

√ √ √ √ √ √ √ √

√

√

√

√ √

√

√

√

√

√

√

√

√ √

63-4524—03 18


Standard Object Types Supported

Table 6. Standard object types supported.

Object Type

Supported

Objects

Dynamically

Creatable

Dynamically

Deletable

Optional

Properties

Supported

Reliability

Writable Properties

Analog Input

Analog Value











 Reliability

Out_of_Service

Present_Value a,b

Out_of_Service a

Object_Name c

Binary Input

Binary Value













Reliability

Active_Text

Inactive_Text

Reliability

Active_Text

Inactive_Text

Max_Master

Max_Info_frames

Out_of_Service

Present_Value

Out_of_Service b c

Device

  

Group

Multi-state Value













N/A

Reliability

States_Text a

Present_Value and Out_of_Service properties are writable for every AV objects except :

• PI Heating Demand (AV21)

• PI Cooling Demand (AV22)

Object_Identifier

Object_name

Max_Master

N/A

Present_Value d

Out_of_Service d

Present_Value property for Room Temperature (AV7) is writable only if Room Temp Override (BV8) is enabled.

Object_Name property is writable for the following object only :

• Room Temperature (AV7) d

Present_Value and Out_of_Service properties are writable for every MV objects except :

• Heating Valve Status (MV26)

• Cooling Valve Status (MV27)

• Fan Status (MV28)

• Effective Occupancy (MV33)

List of Proprietary Properties

Property name

Major_Version

MS/TP_Address

MS/TP_Baud_Rate

Sensor_Offset

ID

1000

Table 7. Proprietary Properties.

BACnet Data type

CharacterString

Description

The version number of the BACnet communications module. This is the hardware version number

1001 Unsigned Display the MAC layer address of the module

1002 Unsigned

1005 REAL

Display the communication baud rate of the module

Display the temperature calibration value.

The temperature range is –5.0 ºF to 5.0 ºF.

19 63-4524—03


Property Value Range Restrictions

Object name

Room Temperature

Outdoor Temperature

Supply Temperature

PI Heating demand

PI Cooling demand

Occupied Heat Setpoint

Occupied Cool Setpoint

Stand-by Heat Setpoint

Stand-by Cool Setpoint

Unoccupied Heat Setpoint

Unoccupied Cool Setpoint

Password Value

Heating Setpoint Limit

Cooling Setpoint Limit

Deadband

Stand-by Time

Unoccupied Time

Table 8. Property value range restrictions.

Object Type and instance

Minimum range value

Maximum range value

AV 7

AV 9

AI 12

-39.9°F (-40°C)

-39°F (-40°C)

-39.9°F (-40°C)

121.9°F (50°C)

121.9°F (50°C)

121.9°F (50°C)

AV 21

AV 22

AV 39

AV 40

AV 41

AV 42

AV 43

AV 44

AV 56

0%

0%

40°F (4.5°C)

54°F (12°C)

40°F (4.5°C)

54°F (12°C)

40°F (4.5°C)

54°F (12°C)

0

100%

100%

90°F (32°C)

100°F (37.5°C)

90°F (32°C)

100°F (37.5°C)

90°F (32°C)

100°F (37.5°C)

1000

AV 58

AV 59

AV 63

AV 67

AV 68

40°F (4.5°C)

54°F (12°C)

2°F (1°C)

0.5 Hours

0.0 Hours

90°F (32°C)

100°F (37.5°C)

5°F (2.5°C)

24.0 Hours

24.0 Hours

Default value

N/A

N/A

N/A

0%

0%

72°F (22°C)

74°F (24°C)

72°F (22°C)

74°F (24°C)

62°F (16.5°C)

80°F (26.5°C)

0

90°F (32°C)

54°F (12°C)

2°F (1°C)

0.5 Hours

0.0 Hours

63-4524—03 20


Property Enumeration Sets for BV & BI Objects

Table 9. Property enumeration sets for BV and BI objects.

Room Temp Override

AUX Command

Aux Status

BI 1 Status

BI 2 Status

UI 3 Status(*)

Local Motion

Window Alarm

Filter Alarm

Service Alarm

Menu Scroll

Auto Mode Enable

Temperature Scale

Setpoint Type

Setpoint Function

Reheat Time Base

Auto Fan

Object Name

Control Type

Direct/ Reverse Acting

Object Type and Instance

BV 8

BV 14

BI 25

BI 29

BI 30

BI 31

BI 32

BI 35

BI 36

BI 37

BV 49

BV 50

BV 51

BV 60

BV 61

BV 64

BV 66

BV 75

BV 78

Inactive_Text

Normal

Off

Off

Deactivated

Deactivated

Deactivated

No Motion

Off

Off

Off

No Scroll

Disabled

°C

Permanent

Dual Setpoints

15 minutes

Auto Speed

On/Off

Direct Acting

Active_Text

Override

On

On

Activated

Activated

Activated

Motion

On

On

On

Scroll Active

Enabled

°F

Temporary

Attached

Setpoints

10 seconds

Auto Speed / Auto

Demand

Floating

Reverse Acting

Default value

Normal

Off

Off

Deactivated

Deactivated

Deactivated

No Motion

Off

Off

Off

Scroll Active

Enabled

°F

Permanent

Dual Setpoints

15 minutes

Auto Speed

On/Off

Direst Acting

(**) This object will be linked to the value of the “UI 3 Configuration” object. When the “UI 3 Configuration” object value is 0, 3 or 4, the value will be set to “Deactivated.”

21 63-4524—03


Enumeration Sets for MV Objects

Table 10. Property enumeration sets for MV objects.

Object Name

Sequence of

Operation

System Mode

Note 1

Fan Mode

Note 3

Occupancy

Command

Keypad Lockout

Object ID

MV 15

MV 16

MV 17

MV 18

MV 19

2

3

6

1

4

3

4

1

2

5

BACnet Index

1, 2, 3 or 4

3

4

1

2

5

6

1

2

3

Text

Cooling Only

Heating Only

Cooling & Reheat

Heating & Reheat

Cool/Heat4P

Cool/Heat4P&Reht

Off

Auto

Cool

Heat

Note 4

Local Occupancy

Occupied

Unoccupied

Level 0

Level 1

Level 2

Level 3

Level 4

Level 5

Default value

Heating Only

Note 2

Note 5

Depends on network command

Level 0

NOTES:

1.

2.

Enumeration sets for MV16 depends on Sequence of Operation (MV15) value upon device discovery. If required enumeration is not present, set MV15 to desired value and rediscover MV16 object. Available enumeration will now reflect required configuration.

Default value of MV16 depends on MV15 value upon device discovery

.

MV15 Index

3

4

1

2

5

6

3.

4.

5.

Function

Cooling Only

Cooling with Reheat

Heating Only

Heating with Reheat

Cooling/Heating 4 Pipes

Cooling/Heating 4 Pipes with Reheat

Default Value is BV50

Enabled

Cool

Auto

Heat

Heat

Auto

Auto

Default Value is BV50

Disabled

Cool

Heat

Heat

Heat

Heat

Heat

Enumeration sets for MV17 depends on Fan Mode Sequence (MV58) value upon device discovery. If required enumeration is not present, set MV58 to desired value and rediscover MV17 object. Available enumeration will now reflect required configuration.

Available state text and default value depends on Fan Mode Sequence (MV58) value upon device discovery.

Same as Note 4.

63-4524—03 22


2

3

MV17 Index

1

4

5

Function MV58 State Text Index

1 Low - 2 Med - 3 High

1 Low - 2 High

1 Low - 2 Med - 3 High - 4 Auto

1 Low - 2 High - 3 Auto

1 Auto -2 On

Default Value

High

High

High

High

Auto

Object Name

Heating Valve Status

Note 6

Cooling Valve Status

Note 8

Table 10. Property enumeration sets for MV objects. (Continued)

Object ID BACnet Index Text Default value

MV 26

MV 27

Note 7 Note 7 Note 7

Note 9

Fan Status

Effective Occupancy

MV 28

MV 33

Note 9

4

1

2

3

4

1

2

3

Note 9

Off

Low

Med

High

Occupied

Unoccupied

Temporary Occupied

Stand-by

Off

Depends on local occupancy

6.

7.

Enumeration sets for MV26 depends 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 object.


Available object name, state text and default value depends on Control Type (BV75) value and Pipe Number (MV52) upon device discovery.

BV75 Value

On/Off

Floating

MV52 Index

1 (2 pipe)

2 (4 pipe)

1 (2 pipe)

2 (4 pipe)

MV26 Object

Name

Unused Output

Heating Valve

Status

Unused Output

Heating Valve

Status


N/A

1 Closed – 2 Open

N/A

1 Stopped - 2 Opening - 3 Closing

Default Value

N/A

Closed

N/A

Stopped

8.

9.

Enumeration sets for MV27 depends 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 MV27 object.


Available object name, state text and default value depends on Control Type (BV75) value and Pipe Number (MV52) upon device discovery.

23 63-4524—03


BV75 Value

On/Off

Floating

MV52 Index

1 (2 pipe)

2 (4 pipe)

1 (2 pipe)

2 (4 pipe)

MV27 Object

Name

Heat/Cool Valve

Status

Cooling Valve

Status

Heat/Cool Valve

Status

Cooling Valve

Status


1 Closed – 2 Open

1 Closed – 2 Open



Default Value

Closed

Closed

Stopped

Stopped

Object Name

BI1 Configuration

BI2 Configuration

UI3 Configuration

Pipe Number

Out#1 Cfg

AUX Configuration


Object ID

MV 46

MV 47

MV 48

MV 52

MV 53

MV 54

4

5

2

3

5

1

3

4

1

2

1

2

5

1

2

3

4

1

2

3

4

1

2

5

6

BACnet Index Text

None

Rem NSB

Motion NO

Motion NC

Window

None

Door Dry

Override

Filter

Service

None

COC/NH

COC/NC

COS

SS

2

4

2 Pipe

4 Pipe

Not used

NO with Occ

NC with Occ

NO with Occ & Fan

NC with Occ & Fan

Network controlled

Default value

None

None

None

4 Pipes

4

Not Used

63-4524—03 24


Object Name

Fan Mode Sequence

Temporary Occupancy

Time

Proportional Band


Object ID

MV 58

MV 62

MV 65

BACnet Index

3

4

1

2

22

23

24

25

7

8

5

6

14

15

16

17

10

11

12

13

18

19

20

21

4

5

2

3

5

1

3

4

8

9

6

7

1

2

Text

9 hours

10 hours

11 hours

12 hours

13 hours

14 hours

15 hours

16 hours

17 hours

18 hours

19 hours

20 hours

7

8

9

10

5

6

3

4

21 hours

22 hours

23 hours

24 hours

3 F

4 F

5 F

6 F

7 F

8 F

9 F

10 F

Low-Med-High

Low-High

Low-Med-High-Auto

Low-High-Auto

On-Auto

0 hour

1 hour

2 hours

3 hours

4 hours

5 hours

6 hours

7 hours

8 hours

1.2 C

1.7 C

2.2 C

2.8 C

3.3 C

3.9 C

5.0 C

5.6 C

Default value

On-Auto

2 hours

3

25 63-4524—03


Object Name

Floating Motor Timing

On-Off Control CPH


Object ID

MV 76

MV 77

BACnet Index

1

2

7

8

9

10

5

6

3

4

11

12

13

14

3

4

1

2

5

6

15

16

17

18

0.5 minute

1 minute

1.5 minutes

2 minutes

2.5 minutes

3 minutes

3.5 minutes

4 minutes

4.5 minutes

5 minutes

5.5 minutes

6 minutes

6.5 minutes

7 minutes

7.5 minutes

8 minutes

8.5 minutes

9 minutes

3 CPH

4 CPH

5 CPH

6 CPH

7 CPH

8 CPH

Text Default value

1.5 minutes

4 CPH

63-4524—03 26


27 63-4524—03


By using this Honeywell literature, you agree that Honeywell will have no liability for any damages arising out of your use or modification to, the literature. You will defend and indemnify Honeywell, its affiliates and subsidiaries, from and against any liability, cost, or damages, including attorneys’ fees, arising out of, or resulting from, any modification to the literature by you.

Automation and Control Solutions

Honeywell International Inc.

1985 Douglas Drive North

Golden Valley, MN 55422 customer.honeywell.com

® U.S. Registered Trademark

© 2014 Honeywell International Inc.

63-4524—03 M.S. Rev. 12-14

Printed in United States

Honeywell TB7200 Series Integration Manual

BACnet Integration Manual for

TB7200 & TB7300 Series

Thermostats

PRODUCT OVERVIEW

COMPATIBILITY

TIPS AND THINGS YOU NEED TO KNOW

WIRING GUIDELINES

NETWORK CONFIGURATION

NETWORK ADAPTER

INTEGRATION

TROUBLESHOOTING

APPENDIX

BACNET OBJECTS SUPPORTED

Key Features

Related manuals

Frequently Answers and Questions

How many thermostats can be connected to a single WEB-2xx controller?

What is the maximum number of nodes allowed on a single daisy chain segment?

Is biasing required with this series of devices?

Table of contents

Honeywell TB7200 Series Integration Manual

BACnet Integration Manual for

TB7200 & TB7300 Series

Thermostats

PRODUCT OVERVIEW

COMPATIBILITY

TIPS AND THINGS YOU NEED TO KNOW

WIRING GUIDELINES

NETWORK CONFIGURATION

NETWORK ADAPTER

INTEGRATION

TROUBLESHOOTING

APPENDIX

BACNET OBJECTS SUPPORTED

Key Features

Related manuals

Honeywell

TB7600

Vykon

VT7600 Series

Honeywell

TB7600

Viconics

VT7200C5531B

Vykon

VT7600 Series

Honeywell

TB7600 Series

Honeywell

TB7300 Series

Tait

TB7300

Honeywell

63-4526-01

Frequently Answers and Questions

How many thermostats can be connected to a single WEB-2xx controller?

What is the maximum number of nodes allowed on a single daisy chain segment?

Is biasing required with this series of devices?

Table of contents