Installation and Operations Guide

BACtalk Control Modules

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

Installation and Operations Guide | BACtalk Control Modules

Important safety information and installation

precautions
Read all instructions
Failure to follow all instructions may result in equipment damage or a hazardous condition. Read all instructions
carefully before installing equipment.
Local codes and practices
Always install equipment in accordance with the National Electric Code and in a manner acceptable to the local
authority having jurisdiction.
Electrostatic sensitivity
This product and its components may be susceptible to electrostatic discharge (ESD). Use appropriate ESD
grounding techniques while handling the product. When possible, always handle the product by its non-electrical
components.
High voltage safety test
Experienced electricians, at first contact, always assume that hazardous voltages may exist in any wiring
system. A safety check using a known, reliable voltage measurement or detection device should be made
immediately before starting work and when work resumes.
Lightning and high-voltage danger
Most electrical injuries involving low-voltage wiring result from sudden, unexpected high voltages on normally
low-voltage wiring. Low-voltage wiring can carry hazardous high voltages under unsafe conditions. Never install
or connect wiring or equipment during electrical storms. Improperly protected wiring can carry a fatal lightning
surge for many miles. All outdoor wiring must be equipped with properly grounded and listed signal circuit
protectors, which must be installed in compliance with local, applicable codes. Never install wiring or equipment

!
while standing in water.
Wiring and equipment separations
All wiring and controllers must be installed to minimize the possibility of accidental contact with other, potentially
hazardous and disruptive power and lighting wiring. Never place 24VAC or communications wiring near other
bare power wires, lightning rods, antennas, transformers, or steam or hot water pipes. Never place wire in any
conduit, box, channel, duct or other enclosure containing power or lighting circuits of any type. Always provide
adequate separation of communications wiring and other electrical wiring according to code. Keep wiring and
controllers at least six feet from large inductive loads (power distribution panels, lighting ballasts, motors, etc.).
Failure to follow these guidelines can introduce electrical interference and cause the system to operate
erratically.
Warning
This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to part
15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the interference at his own expense.
© 2007 Honeywell International Inc. All Rights Reserved.
6670 185th AVE NE
Redmond, WA 98052 USA
Phone: (425)869-8400 FAX: (425)869-8445
Web Site: www.alerton.com E-mail: [email protected]
All information in this document is provided as is without warranty of any kind. Honeywell reserves the right to
change any information herein without prior notice. No guarantees are given as to the accuracy of information.
Trademarks and trade names may be used in this document to refer to either the entities claiming the marks and
names or their products. Alerton, BACtalk, and their logos are registered trademarks and VisualLogic is a
trademark of Honeywell. Honeywell disclaims any proprietary interest in trademarks and trade names other than
its own.
Questions, corrections, comments?
To improve our information products and better serve our readers, your feedback is vital. If you have any
questions, corrections, or comments about this publication or any other Alerton information products, please
send e-mail to [email protected].

2 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Contents

Contents

About this guide 5

How to use this guide 5
Other resources 6
Key illustrations 7
About BACtalk control modules 10
Compatibility information for Alerton devices 11
Data persistence 12
Realtime Operating Code (ROC) files 12
Hardware installation and operation 14
Mounting 14
Power requirements 15
Communications connections 15
Using switches on BACtalk control modules 21
Initial firmware and operator workstation setup 22
Configuration requirements and guidelines 22
Connecting to the BCM with HyperTerminal 22
Navigating and entering data 25
Configuring settings that apply to most modules 26
Saving changes 31
Saving configuration files 31
Sending configuration files 31
Final setup and checkout at the operator workstation 33
Scanning for the BCM and setting up a device record 33
BCM-PWS module 34
BCM-ETH module 35
Software and programming support 35
Technical data 37
Configuration settings unique to this module 37
Using diagnostic LEDs for this module 44
BCM-MS/TP module 45
Software and programming support 45
Technical data 46
Configuration settings unique to this module 46
Using diagnostic LEDs for this module 48
NAT Firewall Limitation 48
BCM-TUX module 49
Software and programming support 49
Technical Data 50
Configuration settings unique to this module 50
How the BCM-TUX exposes TUXs and TUX data to BACnet 53
How to convert APEX DDC for use in the BCM-TUX 54
Using diagnostic LEDs for this module 56
NAT Firewall Limitation 56
BCM-MDBS module 57
Software and programming support 57
Technical Data 58
Configuration settings unique to this module 58
Mapping Modbus data to AVs and BVs 61
Defining multiple register requests 65
Setting up data mappings 68
Using diagnostic LEDs for this module 69
NAT Firewall Limitation 70

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 3

Installation and Operations Guide | BACtalk Control Modules

BCM-HOTEL module 71
Protocol One 71
Protocol Two 72
Custom 73
Hotel computer acknowledgement and response 73
Software and programming support 73
Technical data 74
Configuration settings unique to this module 74
Using diagnostic LEDs for this module 76
NAT Firewall Limitation 76
BCM-FPCS module 77
Software and programming support 77
Technical Data 78
Integrating P1 protocol network devices with BACtalk 79
Configuration settings unique to this module 79
Mapping P1 network data to BACnet AVs and BVs 84
Setting change-of-value options for P1 devices 88
Using diagnostic LEDs for this module 89
Using diagnostic AVs for this module 90
BCM-MDM module 91
Configuration settings unique to this module 91
Using diagnostic LEDs for this module 93
Appendix A: HyperTerminal settings 94
Appendix B: BACnet object and property reference 95
Appendix C: Virtual device object and property reference 103
Appendix D: Diagnostic AVs 113
Appendix E: The alerton-gateway-setup property 121
Appendix F: TUX data point to BACnet object mappings 123
Appendix G: Modbus function codes 167
Appendix H: Error indicators 168

4 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | About this guide

About this guide

In addition to technical data and general information about BACtalk control
modules (BCM), this guide provides instructions and guidelines for:

• Mounting
• Connecting power and communications cabling
• Performing initial configuration and setup
• Verifying configuration and setup

Appendixes provide information about configuration connection settings and

object and property references to aid in diagnostic and integration activities.

This guide applies to the following modules:

• BCM-PWS module
• BCM-ETH module
• BCM-MS/TP module
• BCM-TUX module
• BCM-MDBS module
• BCM-HOTEL module
• BCM-FPCS module
• BCM-MDM module

BCMs not listed here have separate installation and operation guides.

How to use this guide

This document was created to assist engineers and technicians when installing
and programming BACtalk control modules.

• Check Table 1 for other documentation you might need.

• Even if you’re an expert with the Alerton and BACtalk systems, review
“About BACtalk control modules” on page 10. This section gives you
important information about how to apply BACtalk control modules.
• “Key illustrations” on page 7 is a good starting point for installation
technicians and engineers. Browse this section to become familiar with
the hardware and unique installation requirements.
• Programmers and system developers can use the Appendixes at the end
of this manual for quick reference information.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 5

Installation and Operations Guide | BACtalk Control Modules

Other resources
Ta bl e 1 Sources for more information

Document ID Contains
BACtalk Control Modules data sheet A summary of applications, capabilities, and
technical data.

Envision for BACtalk Installation and Information needed to use Device Manager to
Startup Guide (LTBT-TM-ADMIN) view device information about the BACtalk control
modules or to download a ROC file.

Envision for BACtalk Operator’s Information for setting up automated control

Manual (LTBT-OP-EBT20) and features for your BACtalk system.
online Help

Programmer’s Guide and Reference Detailed information about programming DDC and
for BACtalk Systems referencing system data points in a BACnet
(LTBT-TM-PRGRMR) environment.

BACtalk System Design Guide Use to design a BACnet internetwork or for

(LTBT-TM-SYSDSGN) specific integration tips for your application.

6 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Key illustrations

Key illustrations

Figure 1 A series (array) of BACtalk control modules

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 7

Installation and Operations Guide | BACtalk Control Modules

Office computer
running BAS workstation
Office computer Printer software

Enterprise Network (Ethernet)

BCM-PWS

BCM-MDM
BCM-ETH

BAS server

BACnet MS/TP

VLC VLC

Figure 2 Simple architecture using BACtalk control modules

8 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Key illustrations

Communication connections appear at

the top of the module. Be sure to leave 4-5
inches minimum above each module
during mounting and installation.

Use the DB-9 port behind the front cover

of a BCM module to connect the module
to a computer with a null modem cable.
Use this connection for local
configuration.

The BCM-MDM uses the module directly

to its left as its host control module. You
configure PTP settings and modem
options using HyperTerminal at the host
control module. Note that BCM-WEB does
not support a BCM-MDM.

Power is provided by the BCM-PWS.

Each BCM obtains power through its
ribbon-cable connection to the other
BCMs.

Use the Reset button and DIP switches to erase all user objects or the Use the locking cam on the front of the
ROC file in the module. See “Using switches on BACtalk control modules” BCM module to secure the module to the
on page 21 for more information. DIN rail.

Figure 3 BACtalk control modules with power cabling detail

5"
1.50" (122mm)
(38mm)

35mm DIN rail

not included

6.5"
(165mm)

Figure 4 BACtalk control module dimensions

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 9

Installation and Operations Guide | BACtalk Control Modules

About BACtalk control modules

You can combine BACtalk control modules in various combinations for
maximum flexibility to meet the various needs of each job site. Connect from
one to seven BACtalk control modules (not including a power module) in a
series with a provided ribbon cable. BACtalk control modules can support
Ethernet, MS/TP, TUX trunk, modem, and gateway connections to various non-
BACnet devices.

Each module (except the BCM-PWS and BCM-MDM) has a unique device
instance and hosts its own connections, DDC programming, and automation
features.
Ta bl e 2 BCM models and descriptions

Model Description
BCM-PWS The base module for a BCM array, providing power for up to seven
BCMs. It conditions power and provides battery backup using a
ribbon-cable connection.

BCM-MSTP BACnet-compliant global controller that supports up to 65 field

controllers on a single BACnet MS/TP LAN. The BCM-MSTP hosts
its own automation features.

BCM-ETH A BACnet-compliant router and global controller that supports both a

BACnet Ethernet and a BACnet MS/TP network connection. Includes
an onboard Ethernet network interface card (NIC) that supports
10base-T (10 Mbps) or 100Base-TX (100 Mbps) Ethernet connection
to the BACnet internetwork. Required for Ethernet access for rest of
modules. Supports BACnet/IP and can function as a BBMD. The
BCM-ETH hosts its own automation features.

BCM-TUX A BACnet-compliant global controller and IBEX gateway for BACnet

systems. Reads TUX data from up to 64 Alerton TUXs on an IBEX
TUX trunk and makes data available to the BACnet network as
BACnet objects and properties. The BCM-TUX hosts its own DDC
and automation features.

BCM-MDBS A fully-programmable BACnet-compliant gateway to a Modbus EIA-

232, EIA-422, or EIA-485 network. The BCM-MDBS supports one
slave Modbus device using an EIA-232 connection or up to 247
Modbus slave devices using an EIA-485 or EIA-422 connection.
Converts data from connected Modbus devices to BACnet AV and
BV objects. Each BCM-MDBS has a capacity for 1000 AV and 1000
BV objects and each object can be assigned to one Modbus data
point. The BCM-MDBS hosts its own BACtalk DDC and automation
features.

10 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | About BACtalk control modules

Ta bl e 2 BCM models and descriptions

Model Description
BCM-HOTEL Connects to a hotel reservation and check-in system over EIA-232,
EIA-422 or EIA-485. When combined with a BCM-ETH, it makes
rented or not-rented information for up to 10,000 rooms available to a
BACnet system over BACnet Ethernet and IP WANs. The BCM-
HOTEL hosts its own BACtalk DDC and trendlogs.
BCM-FPCS ®
A gateway global controller used between a Siemens P1 trunk and
Alerton’s Envision for BACtalk BACnet system. The P1-trunk field
devices supported (MPU, DPU, and TEC) will appear as BACnet
devices at the Envision for BACtalk front end. Real-time point data
from the Siemens controllers is automatically detected and mapped
as equivalent AV and BV BACnet objects in BACtalk when the BCM-
FPCS is brought online. The Ethernet network is a 10base-T (10
Mbps) or 100Base-TX (100 Mbps) Ethernet. The Siemens P1 trunk is
a 4800-baud RS-485 multi-drop connection. The P1 network must be
shielded and terminated.

BCM-MDM Provides dial-out and dial-in capacity for BACtalk systems,

supporting remote operator workstation connections or alarm dial-
out. The preconfigured V.90/56K serial-interface modem includes an
RJ-11 jack to direct connect to an analog phone line and the public
switched telephone network (PSTN). Operates on most telephone
systems outside of North America by setting a country code and
adding a telephone line adapter.

BCM-WEB Allows users to access a BACtalk system using a standard Web

browser. BCM-WEB has a separate installation and operation guide
(LTBT-TM-BCMWEBIOG).

Compatibility information for Alerton devices

The BCMs operate in a BACtalk system using BACtalk operator workstation
software. BCMs support Alerton’s field level devices from both the BACtalk and
IBEX systems.

• Alerton BACtalk operator workstation software Envision for

BACtalk version 1.1 or later is required to download a ROC file,
program, or connect to the BCM over a modem.
N o t e You can use BCMs in a system with BACtalk for Windows
v3.11 or Envision for BACtalk, but the new features in Envision for
BACtalk are not available in BACtalk for Windows and the operator
workstation software may not be able to correctly read device
information. Thus, the information may not appear correctly in dialog
boxes and displays. Upgrade to the latest version of Envision for
BACtalk to take advantage of the latest BACtalk features.
• Alerton VisualLogic controllers (VLCs) All versions. However,
versions 1.02 and earlier require special MS/TP configuration. See
Table 21 on page 47 for more information.
• TUXs The following TUX models are supported. See Table 25 on
page 51 for more information.
TX-450 (REV 2) TX-16160 TX-651 PULSE

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 11

Installation and Operations Guide | BACtalk Control Modules

TX-VAV TX-SA TX-SA-651

TX-HOST-R3 TX-APLC TX-APLC2

TX-R3P TX-653P TX-MQ-WSHP

PCL TUX (All)

Legacy TUX models (1200 baud only)

TX-450-ST TUX-HOST TUX-PULSE

TUX-780-ST TUX-784-ST TUX-884

TUX-651P

• BCM-WEB Requires Envision for BACtalk 2.5 or later.

Data persistence
All programmed objects (such as schedules, trendlogs, and alarms), DDC, data
values, and the ROC file execute in RAM and are periodically backed up in flash
memory. All data is retained through power loss.

Configuration parameters set up in HyperTerminal are also stored in flash

memory. Likewise, all configuration data is retained through power loss.

Configuration parameters can be saved as a Z-modem data file and then sent to
the BCM. This facilitates off-site setup and easy replication of settings to other
controllers in similar installations.

Realtime Operating Code (ROC) files

Each BCM ships with the system boot code and real-time operating code (ROC) file pre-loaded
at the factory. Diagnostic LEDs indicate the operational status of these files.

Unique to application,
DDC Automation
user interactive

Operator upgradable ROC (Application *.BIN)

Factory loaded System Boot Code (Loader)

Figure 5 Relationship of BCM system boot code, ROC, and application files

The ROC file is the foundation of controller operations and is required for the BCM to host DDC
and automation features. Although, an initial ROC file is loaded at the factory, periodic updates
may be required (for example, when a new version of operator workstation software becomes
available).
Download ROC files from the <bactalk root>\system directory using BACtalk operator

12 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | About BACtalk control modules

workstation software. See BACtalk operator workstation software online Help for more
information about downloading ROC files or checking ROC file versions.

• BCM-ETH ROC file: <bactalk root>\system\app18.bin

• BCM-TUX ROC file: <bactalk root>\system\app19.bin
• BCM-MS/TP ROC file: <bactalk root>\system\app20.bin
• BCM-MDBS ROC file: <bactalk root>\system\app22.bin
• BCM-HOTEL ROC file: <bactalk root>\system\app23.bin
• BCM-FPCS ROC file: <bactalk root>\system\app25.bin
• BCM-WEB ROC file: <bactalk root>\system\alerwb\bwroc\bcmweb_roc.dist

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 13

Installation and Operations Guide | BACtalk Control Modules

Hardware installation and operation

This section describes installation of BACtalk control modules, covering
requirements for mounting, connecting to the power supply, and setting up
communication connections.

WARN ING Do not “hot swap” modules. Failure to disconnect power before
adding or replacing modules can cause hardware damage and loss of data.

Mounting
Each BCM is designed to mount to a 35mm DIN rail, with the connection
terminals facing up. Use the screw behind the front cover of the module to open
the tabs on the rear of the BCM, position the unit against the DIN rail, push the
tabs in to secure the BCM to the DIN rail, and then tighten the screw to hold the
BCM in place.

Situate the BCM-PWS on the DIN rail such that subsequent modules mount to
the right of the BCM-PWS. Situate the BCM-MDM to the right of all other
modules. If BCM-WEB and BCM-MDM modules are mounted on the same rail,
another module must be placed between the BCM-WEB and the BCM-MDM.

The graphic on the left

shows the ribbon cable
terminated at the
modem.
If you do not have a
modem module,
terminate the ribbon
cable at the module
farthest on the right with
the provided terminating
resistor (shown below).
Modules are linked together
with ribbon cables. Starting
with the power module, each
module is linked to the
module on its right.
The only exception to this
rule is the modem module
(always the last module on
the right) which connects to
the module directly to its left.

Figure 6 BCMs showing ribbon cable connections

BCM modules are intended for indoor applications. Install in a UL listed

enclosure, in a dry location, away from direct sunlight, and free from excessive

14 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Hardware installation and operation

dust, vibration, and electrical interference. Operating temperature range is

32-131 deg. F (0-55 deg. C).

Power requirements
Each BCM obtains power through its ribbon-cable connection to the BCM-PWS.
See “BCM-PWS module” on page 34 for more information.

Communications connections
This topic describes hardware network connections to each BCM.
Configurations performed over a HyperTerminal connection are important for
connectivity. See page 22 for information about HyperTerminal configuration.

I MP O R TA N T EIA-422 and 4-wire EIA-485 are electrically compatible and

fully-interoperable.

Using terminal blocks

Each BCM uses removable terminal blocks to simplify field wiring of
power and cabling. You can remove the terminal blocks from the unit,
terminate the cable, and then re-seat the terminal block when you
finish.

X To terminate cable
1. Strip a maximum of 3/8” (10 mm) of the wire jacket from the
end of the cable.

2. Use a small screwdriver (1/8” max.) to turn the adjustment

screw fully counter-clockwise.
The clamps in the wire slot separate as you turn the screw.

3. When the clamps in the wire slot are fully open, insert the
stripped end of the cable (insulation end must be flush with
the terminal block). Be sure to insert all cable strands into the
wire slot.

4. Hold the cable in place and turn the adjustment screw

clockwise to tighten it until the clamps in the wire slot secure
the cable.

5. Tug gently on the cable to ensure that it’s secure.

CAUTION Set up firmware using HyperTerminal before physically connecting

networks. This helps to avoid potential network conflicts and communication
errors.

Ethernet
Ethernet is a high-speed LAN widely installed in commercial buildings.

Twisted-pair Ethernet networks use four conductors (two twisted-pair wires) to

carry the network signal. The first pair carries the transmit signal positive and
negative. The second pair carries the receive signal positive and negative.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 15

Installation and Operations Guide | BACtalk Control Modules

The BCM-ETH has an onboard Ethernet network interface that supports

10Base-T (10 Mbps) and 100Base-TX (100 Mbps) Ethernet connections to the
BACnet internetwork.

The BCM-ETH will automatically switch to 100 Mbps operation if other devices
and cabling support it.

Ethernet RJ-45 jack An RJ-45 jack for connection to Ethernet is on the

top edge of the BCM-ETH. Pin designations for
the RJ-45 jack (perspective is looking into the
jack) are shown.
PR1 PR2
XMIT RCV
Pin Assignment
_ _
+ +
1 Transmit +

2 Transmit –

1 2 3 4 5 6 7 8 3 Receive +
6 Receive –

Cable type and length Use an approved Category 5 or better Ethernet

drop cable with RJ-45 plugs to connect to an
Ethernet switch. Use professionally manufactured
cables and a switch that supports 100 Mbps for
best results. Cable length should be no more than
328 feet (100 meters).
The BCM-ETH does not implement internal
crossover. Use a straight-through or crossover
cable as appropriate for the device that the
BCM-ETH connects to.

MS/TP
MS/TP is a LAN standard designed specifically for BACnet applications. It uses
the EIA–485 signaling standard on twisted-pair cabling in a simple bus
configuration.

Terminal identification Terminals for MS/TP are on the top edge of the
BCM-ETH and BCM-MS/TP and are labeled
MS/TP + and MS/TP –.
Cable type and length BACnet specifies shielded, twisted-pair cabling
with characteristic impedance between 100 and
130 ohms. Distributed capacitance between
conductors must be less than 30 pF/foot
(100 pF/m). Distributed capacitance between
conductor and shield must be less than 60 pF/foot
(200 pF/m). Foil or braided shield is acceptable.
Cable length should be no more than 4000 feet
(1200 meters) per segment. Maintain polarity
throughout the MS/TP segment.

16 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Hardware installation and operation

Terminating resistors Matched precision resistors are required at each

end of the MS/TP segment. Wire the resistors
across + and –. Resistors should be sized to match
the characteristic impedance of the cable installed
- typically 100 to 130 ohms.
Shield grounding Terminate shield drain along the MS/TP segment
to ground.
Tie shield drain through with wire nut at each
intermediate device and insulate to avoid potential
ground contact. Tape shield drain back at other
end of segment.

TUX trunk
The BCM-TUX communicates to TUXs over a simple, twisted-pair, multi-drop
communications bus known as a TUX trunk. Maximum allowable distance
depends on the type of wire used, the baud rate of communications (set in the
HyperTerminal configuration, see “Initial firmware and operator workstation
setup” on page 22) and the number of TUXs the trunk supports. See the IBEX
Technical Manual (LT-MAN-TECH) for TUX trunk wiring and termination
guidelines.

TUX trunk connections are made on removable, header-style screw terminals on

the top of the BCM-TUX. The BCM-TUX supports TUXs operating at 4800 and
9600 baud. The BCM-TUX now supports 1200 baud when running with
Envision for BACtalk v2.0 or later.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 17

Installation and Operations Guide | BACtalk Control Modules

Modbus
The BCM-MDBS connects to modbus devices over a two-wire EIA-485
Modbus network, EIA-232 Modbus network, or an EIA-422 Modbus network.
Only one network type can be operational.

EIA-232 serial connection Modbus

Device

BCM-PWS

BCM-MDBS

BCM-MDM
BCM-ETH

- OR -

EIA-422 connection Maximum of 247

slave nodes

NOTE: Although 247 slave nodes can be

supported, this number is limited by unit
load. The BCM-MDBS supports a
maximum unit load of 32.
BCM-PWS
BCM-MDBS

BCM-ETH
BCM-MDM

- OR -

EIA-485 connection Maximum of 247

slave nodes

NOTE: Although 247 slave nodes can be

supported, this number is limited by unit
load. The BCM-MDBS supports a
maximum unit load of 32.
BCM-PWS

BCM-MDBS
BCM-ETH
BCM-MDM

Figure 7 BCM-MDBS architecture examples

18 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Hardware installation and operation

The EIA-232 connection is made through the DB-9 connector, and the EIA-422
and EIA-485 connections are made on removable, header-style screw terminals
on the top of the BCM-MDBS.
Ta bl e 3 EIA–232 male DB-9 connector pin assignments

Pin # Designation
1 CD

2 RXD

3 TXD
4 DTR

5 GND

6 DSR

7 RTS

8 CTS

9 RING

Note The wiring configuration of connections varies depending on MODBUS

system and equipment requirements.

BTP-MODBUS Other Equipment

Figure 8 Typical DB-9 to DB-9 connection for BTP-MODBUS, showing RXD-to-

TXD and GND-to-GND connections. It is preferable to leave other connections
unterminated.

Ta bl e 4 EIA-422 pin assignments

Pin Assignment
1 Transmit +

2 Transmit -

3 GND

4 Receive +

5 Receive -

Ta bl e 5 EIA-485 pin assignments

Pin Assignment
1 Data +

2 Data -

3 GND

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 19

Installation and Operations Guide | BACtalk Control Modules

Hotel
The BCM-HOTEL typically connects to a hotel information system over
EIA-232 at 9600 bps. The BCM-HOTEL supports the following:

Port = EIA-232, EIA-422, EIA-485

Bps = 300, 1200, 4800, 9600

Port
The EIA-232 connection is made through the male DB-9 connector on the top of
the BCM-HOTEL. The EIA-422 and EIA-485 connections are made on
removable, header-style screw terminals on the top of the BCM-HOTEL.
Ta bl e 6 EIA–232 male DB-9 connector pin assignments

Pin # Designation
1 CD
2 RXD

3 TXD

4 DTR

5 GND

6 DSR

7 RTS

8 CTS

9 RING

Ta bl e 7 EIA-422 pin assignments

Pin Assignment
1 Transmit +

2 Transmit -
3 GND

4 Receive +

5 Receive -

Ta bl e 8 EIA-485 pin assignments

Pin Assignment
1 Data +

2 Data -

3 GND

Modem connection
Connect to the BCM-MDM with a minimum 26 AWG phone cord.

20 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Hardware installation and operation

P1 trunk
The P1 trunk communicates only over an EIA-485 connection. See Table 8
above.

Using switches on BACtalk control modules

A dual two-position switch is used to control BACtalk control module
configuration and operation. See the following table for a description of switch
placement and associated operation.
Ta bl e 9 BCM switch settings

Switch 1 Switch 2 Description

OFF OFF Normal operation.

OFF ON If you cycle power to the module or press the

Reset button, the LEDs (SYS, ROC, DDC, and
BAT) will turn on and remain on for 3 seconds. If
you press the Reset button before the LEDs turn
off, all user objects in the module are erased.
This does not include device configuration
information.

ON OFF If you cycle power to the module or press the

Reset button, the LEDs (SYS, ROC, DDC, and
BAT) will turn on and remain on for 3 seconds. If
you press the Reset button before the LEDs turn
off, the current ROC file in the module is erased.
This does not include device configuration
information.
NOTE: The ROC file is only erased if there is a
valid loader program.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 21

Installation and Operations Guide | BACtalk Control Modules

Initial firmware and operator workstation setup

This topic provides instructions for connecting to a BCM using a null modem
cable and a terminal emulation program, such as HyperTerminal, for initial
firmware configuration.

This topic provides information about:

• Connecting to a BCM with HyperTerminal, the recommended terminal

emulation program
• Setting up network and other operational parameters using
HyperTerminal
• Using an operator workstation to add the BCM to your system and set
configuration values
N o t e This information applies to BACtalk control modules in general.
Specific setup details for a specific module are explained later in the
applicable section for each module.

Configuration requirements and guidelines

CAUTION It is highly recommended that you connect to the BCM and
configure it before connecting to networks to minimize the potential for network
conflicts.

• The BCM must be connected to power during configuration. See

“Mounting” on page 14.
• A null modem cable, a computer with a free 9-pin COM port, and a
terminal emulation program (HyperTerminal) are required to configure
the BCM.
• Connection issues are often attributed to a disabled or non-standard
computer COM port configuration. Use Windows Device Manager or
the computer BIOS setup to debug if the COM port doesn’t appear to be
functional.
• Configuration testing was performed with HyperTerminal in a Windows
environment. Use HyperTerminal for best results.
• Configuration parameters are stored in persistent memory. You can
perform configuration tasks offline, remove power, and the BCM will
retain settings.
• Configuration parameters can be backed up to a configuration file using
the Z-modem transfer file. The file extension is *.dcf.

Connecting to the BCM with HyperTerminal

For initial setup, use a null modem cable connected between the COM port on a
personal computer and the DB-9 connector behind the front cover of the BCM.

X To connect to the BCM and start a HyperTerminal session

1. Power up the BCM (See “Mounting” on page 14) and start the
computer.

2. Connect the computer COM port to the DB-9 connector behind the
front cover of the BCM with a null modem cable. Make a note of the

22 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Initial firmware and operator workstation setup

computer COM port number you use. You will need the COM port
number in HyperTerminal.

3. Start HyperTerminal, which is typically under Programs/Accessories/

Communications on the Windows Start Menu.
HyperTerminal prompts you to create a connection profile in the
Connection Description dialog box.

4. Type a name for the new connection, select a different icon if desired,
and then click OK.

5. In the Connect To dialog box, from the Connect using list, select the
COM port you used to connect to the BCM, and then click OK.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 23

Installation and Operations Guide | BACtalk Control Modules

6. In the connection properties dialog box, select port settings according to

the following (also listed in Table 44 on page 94), and then click OK.

The setup window closes and the HyperTerminal window is blank with
a blinking cursor.

7. Press Enter on the computer keyboard to initiate the session with the
BCM.
The opening screen of the BCM Configuration Utility appears.

Bootloader Revision indicates

the boot code revision.

Firmware Revision

Application indicates the ROC

version.
Position of the module in the
series indicates where the
module is installed (from left to
right, excluding the power
module).
DDC indicates the DDC used.

Device Instance indicates the

BACnet device instance assigned MS/TP settings indicate the network number, MS/TP MAC address,
to the device. and transmission speed for this device on the MS/TP network.
NOTE: The TUX Base Device Instance and VNET fields are
displayed when you connect to a BCM-TUX module. Modbus/Hotel
port type, mode, parity, and stop bits are displayed when you
connect to a BCM-MDBS/BCM-HOTEL module.

Ethernet Network Number and MAC indicates the BACnet network number
assigned to the Ethernet network. MAC indicates the Ethernet MAC address, which
may be useful if using a network sniffer for troubleshooting.

Figure 9 The opening screen of the Configuration utility

8. From the File menu in HyperTerminal, choose Save to save the

connection as a session file (*.ht). This saves the HyperTerminal

24 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Initial firmware and operator workstation setup

session setup for later use. No configuration data is saved. See

“Navigating and entering data” on page 25 for instructions about saving
configuration data.

9. Type the case-sensitive configuration password (pass), and then press

Enter to view the Main menu.

10. Type A, and then press Enter to set up the BCM.

11. Set configuration parameters and save your work according to

instructions in this guide.

Navigating and entering data

This topic provides general instructions for navigating menus, entering and
saving data, and correcting entries while working with a HyperTerminal
connection.

If you make a typing error, press the backspace key to correct it. If you enter the
wrong selection or menu item, retype the value for that field, and then press
Enter to exit the field.

X To change parameters in the Configuration Utility

1. Type the letter of the menu you want to display or the item you want to
change, and then press Enter.

2. To change a value, type the new value, and then press Enter to set it.
-or-
To go to a submenu, type the letter of the item, and then press Enter.

X To return to the main menu

• Type Z, and then press Enter.

X To return to the previous menu

• Type Y, and then press Enter.

X To refresh the current menu

• Press Enter. This is useful when you edit the date and time.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 25

Installation and Operations Guide | BACtalk Control Modules

Configuring settings that apply to most modules

Although each BACtalk control module offers unique features and functions,
there are certain configuration settings that apply regardless of module type.
These configuration settings are described in this section.

Note Specific set up details for a module are explained in the applicable
section for the module. For example, see “BCM-ETH module” on page 35 or
“BCM-TUX module” on page 49 for module-specific information.

Setting the device instance

The device instance is a unique number throughout the BACnet internetwork
that identifies the device for BACnet communications. Valid range for the device
instance is 0 to 4,194,302. Ensure that the device instance is different from any
other device on any connected network.

Note BACnet reserves device instance 4194303 for special purposes. Do not
use device instance 4194303.

Device Instance is item A on the Change Configuration screen.

Setting up the Ethernet network

Ethernet network settings are items B and C on the Change Configuration
screen. Select options according to Table 10.
Ta ble 10 Ethernet network settings

Field Value Remarks

B. BACnet Over Ethernet Y|N Determines whether BACnet packets are
Enabled transmitted on the Ethernet network. Typically
set to Y. Set to N only if IP is enabled (see
“Setting IP network options” on page 26) and
the network allows only IP packets. N is an
advanced setting that requires IP network
knowledge and may cause communication
failures if used incorrectly.

C. Network Number 1–65,534 Sets the BACnet network number for the
Ethernet LAN. Each interconnected BACnet
network must have a network number unique
throughout the internetwork. Selecting a
number in the range 1–65,534 (and not 0) is
highly recommended for flexibility and future
compliance.

Setting IP network options

Annex J BACnet/IP enables BACnet messages to run over Internet Protocol (IP)
wide area networks (WAN). Each BACtalk control module can act as a BBMD
on the BACnet internetwork.

Note The BCM-MS/TP, BCM-MDBS, BCM-HOTEL, and BCM-TUX can

only act as a BBMD if the BCM-ETH is present.

Note See the BACtalk System Design Guide (LTBT-TM-SYSDSGN) for

information on using a BCM as a BBMD with Network Access Translation
(NAT).

26 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Initial firmware and operator workstation setup

I MP O R TA N T BACnet/IP settings rely on correct Ethernet network settings

and connections. See Table 10 on page 26.

Ta bl e 11 BACnet/IP settings

Field Values Remarks Default

A. IP Enabled? Y|N Y = Enables IP support. N
N = Disables IP support. Default.
If the device is on an Ethernet LAN but does not use IP,
ensure that IP Enabled = N (or that IP Address = 0.0.0.0).
This prevents the device from sending any IP messages
over the LAN. Default is N and IP Address is set to
0.0.0.0. IP won't run until IP Address is set.

B. IP Frame Type? DIX | 802.2 The Ethernet frame type used for incoming and outbound DIX
IP transmissions. The primary difference between frame
types is the LLC header.
DIX = The device generates and routes DIX (Ethernet II)
frames. Default.
802.2 = The device generates and routes 802.2 (also
known as 802.3/802.2-not RAW Ethernet) frames.

C. Reassembly Time- 1-300 The fragment reassembly time-out, in seconds. Default is 120
out 120.
D. Maximum MTU 90-1500 The Maximum Transmission Unit (MTU) in bytes. Default 1500
is 1500 (typical for Ethernet networks).

E. Time to Live 001-255 Sets the initial Time to Live (TTL) value for IP packets 64
sent from this device. TTL enumerates the number of
hops (the number of forwarding routers) the packet is
allowed to pass between source and destination. This
prevents looping packets from crashing routers and
saturating entire links or networks. Default is 64.

F. Type of Service 0-15 Sets the 4-bit type of service (TOS) value in the IP packet 0
header. Some applications may use TOS to provide
precedence levels and determine optimum routing
methods for packets. Default is 0.

Value TOS bits Description

0 0000 Default

1 0001 Minimize monetary cost

2 0010 Maximize reliability

4 0100 Maximize throughput

8 1000 Minimize delay

15 1111 Maximize security

G. Virtual Net Number 1-65,534 The BACnet network Number is assigned to the virtual 1
network created by the IP WAN. All BBMDs participating
on the IP WAN (in other words, all BBMDs in the
broadcast distribution table) must have this Virtual Net
Number set to the same number. This Network Number
must also be unique with respect to the internetworked
BACnet LANs. It cannot match other BACnet Network
Numbers (Ethernet LANs, MS/TP LANs, ARCNET LANs,
etc.) Default is 1.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 27

Installation and Operations Guide | BACtalk Control Modules

Ta bl e 11 BACnet/IP settings (Continued)

Field Values Remarks Default

H. IP Address nnn.nnn.nnn.nnn The IP address assigned to this device in dotted-decimal 0.0.0.0
format. nnn is a number from 0-255. Follow IP addressing
conventions and rules for your network. Default is 0.0.0.0,
which prevents IP operation event when IP Enabled? = Y.

I. UDP Port 1-65,534 The UDP port of this controller, which is used to establish 47808
connectionless transmission over IP with other BACnet/
IP-enabled controllers. This UDP port must be the same
as other BACnet/IP-enabled controllers on the same
subnet, especially if the controllers exchange messages
only using BACnet/IP (BACnet/Eth = NO).
There are notable exceptions to this rule:
• When another BBMD is on the same subnet, the UDP
ports of the BBMD must be different.
• Any device on the same subnet that registers with the
BBMD as a foreign device (such as a BACnet operator
workstation) must have a different local UDP port from
the BBMD.
Only those controllers with the same UDP port on a
subnet will exchange BACnet/IP messages. For best
results, always ensure that controllers on an internetwork
use the same UDP ports.

J. Subnet Mask nnn.nnn.nnn.nnn The netmask value for transmission on this network in 255.255.255.0
dotted-decimal. Follow IP netmasking conventions and
rules. Default is 255.255.255.0, which is typical.

K. Gateway 1 Address nnn.nnn.nnn.nnn The IP address, in dotted-decimal, of the primary IP 0.0.0.0

router the device uses to connect to the IP internetwork.
nnn is a number from 0-255. Default is 0.0.0.0, indicating
no device.

L. Gateway 2 Address nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the 0.0.0.0

secondary IP router the device uses to connect to the IP
internetwork. nnn is a number from 0-255. Default is
0.0.0.0, indicating no device.
M. BDT Server IP nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the device 0.0.0.0
Address that functions as the broadcast distribution table (BDT)
server to this device. This BBMD can retrieve its routing
table from the BDT Server if its own BDT is lost for any
reason. If left to 000.000.000.000, the BDT must be
reentered manually. For this reason, the IP address of the
BDT server should appear in its own routing table.

N. BDT Server UDP 1-65,534 The UDP port of the broadcast distribution table (BDT) 47808
Port server defined under Server IP Address.
Broadcast Distribution Table (BDT) entries

The broadcast distribution table (BDT) contains three associated entries for each BACnet/IP broadcast management device
(BBMD) on the IP Virtual Net being defined. A maximum of 32 devices is supported. Each BBMD should have an entry for itself
in its BDT. The three entries must be assigned for each BBMD on the Virtual Network. For each BBMD, the first entry identifies
the IP address, the second the UDP port associated with the BBMD, and the third the netmask used on the BBMD’s subnet.
Usually, BBMDs have identical BDTs because one is set up as the BDT server (see “Server IP Address” and “Server UDP Port”
herein).

28 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Initial firmware and operator workstation setup

Ta bl e 11 BACnet/IP settings (Continued)

Field Values Remarks Default

BBMD n IP Address nnn.nnn.nnn.nnn Each entry is the IP address of a BBMD on the IP virtual
network.

BBMD n UDP Port 47808-47999 Each entry is the UDP port of the BBMD of interest. This
recommended is the same value set up as the “UDP Port” in the BBMD
of interest.

BBMD n Subnet Mask nnn.nnn.nnn.nnn Each entry is used as a mask on the network of the 255.255.255.255
BBMD of interest. Typically set to 255.255.255.255
(default), which indicates that BACnet/IP messages go
only to the BBMD of interest and to no other devices on
the subnet. CAUTION! Changing this setting (most
commonly to 255.255.255.0) is a common cause of IP
routing issues, since most IP routers will not allow
messages to be forwarded to multiple devices as a
security precaution. In nearly all applications, leave this
setting to the default of 255.255.255.255.

Get BDT from Server Y|N When set to Y, the device will read the broadcast N
distribution table (BDT) from the BDT server when you
save changes and exit the configuration utility. Pending:
Yes|No indicates the status of the setting. If Pending =
Yes, the command will execute when you save changes
and exit.

Configuring the date, time, time zone, and daylight savings

Items for the date, time, time zone, and daylight savings settings are on a
submenu accessed through item G on the Change Configuration screen.

Figure 10 Date, time, time zone, and daylight saving settings

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 29

Installation and Operations Guide | BACtalk Control Modules

Ta ble 12 Date, time, time zone, and daylight saving settings

Field Values Remarks

Set local date MM/DD/YYYY Shows the BCM’s current date in mm/dd/yyyy format. To change the date, select
this item and then type today’s date in MM/DD/YYYY format. For example, type
11/14/2008 for November 14, 2008. The BCM automatically calculates the day of
the week.

Set local time [HH:MM[:SS] Shows the BCM’s current time in 24-hour format. To change the time, select this
item and then type the current hour, minute, and second in 24-hour format.
Seconds are optional. For example, type 15:42 if the current time is 3:42 pm.

Set UTC offset -780 to 780 Type the UTC offset, in minutes, that corresponds to the difference between
UTC and local standard time where the BCM operates. Time zones to the West
of the zero-degree meridian are positive values and those to the East are
negative values.
Coordinated Universal Time (UTC) is equivalent to Greenwich Mean Time,
which refers to time kept on zero-degree meridian (Greenwich meridian). Use
the UTC offset to specify the time zone in which the BCM is operating. Typical
UTC offsets for the US are listed.
Atlantic Standard Time: +240
Eastern Standard Time: +300
Central Standard Time: +360
Mountain Standard Time: +420
Pacific Standard Time: +480
Alaska Standard Time: +540
Hawaii-Aleutian Standard Time: +600
Samoa Standard Time: +660

Set daylight saving Disabled|Date range Use this setting to specify whether you want the BCM to automatically adjust its
mode clock for daylight savings time (DST). D=Disabled and R=Date Range. If
disabled, items E-H are not available.

DST start date Fixed|Calculated Specify the day you want the BCM to start daylight savings time. When you
choose to edit this item, you are prompted to enter F for fixed or C for calculated.
F. Fixed = The BCM will prompt you to provide a date in mm/dd/yyyy format.
C. Calculated (default) = The BCM will prompt you to provide parameters to
calculate a relative date. This is automatically set to “first Sunday in April.” Use
the following sequence to enter calculated dates:
The BCM prompts you for the relative position of the day within the month.
Type 1 for the 1st, 2 for the second, and so on. Type L for last. Press Enter
when you finish.
The BCM prompts you for the day of the week. Type 1 for Monday, 2 for
Tuesday, and so on (Sunday = 7). Press Enter when you finish.
The BCM prompts you for the month. Type 1 for January, 2 for February
and so on. Press Enter when you finish.
The calculated date you selected appears as the DST start date.
For example, to enter the “first Sunday in April,” type E and press Enter (to edit
the DST start date), type C and press Enter (to specify a calculated date), type 1
and press Enter (to specify the first), type 7 and press Enter (to specify Sunday),
type 4 and press Enter (to specify April).

DST start time HH:MM[:SS] Specify the exact time that daylight savings time begins in 24-hour format.
02:00:00 by default.

DST end date Fixed|Calculated Specify the day you want the BCM to end daylight savings time. When you
choose to edit this item, you are prompted to enter F for fixed or C for calculated.
See “E. DST start date” herein for instructions.
DST end time HH:MM[:SS] Specify the exact time that daylight savings time ends in 24-hour format.
02:00:00 by default.

30 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Initial firmware and operator workstation setup

Saving changes
After you make changes in HyperTerminal, you must exit appropriately to save
your changes.

CAUTION You will lose changes if you close the HyperTerminal session or
disconnect without saving. After making any changes, be sure to exit
appropriately to save your work.

X To save changes to the BCM

1. Type Z, and then press Enter.

2. Type E, and then press Enter to exit.

The device prompts you to save your changes to a configuration file.

3. If you want to save the file as a backup or to configure other devices,

type Y, otherwise type N.
The device prompts you to load changes to the device.

4. Type Y, and then press Enter. The device restarts.

5. Close HyperTerminal.

Saving configuration files

The configuration utility enables you to save all setup and configuration settings
to a data file that you can archive on hard disk or removable media. This enables
you to quickly duplicate standard configurations in a number of controllers and
provide comprehensive backups of BCM configurations.

When you exit the configuration utility after making changes, the configuration
utility prompts you to save a configuration file to the computer. You can also
choose to save at any time using option C from the Main menu.

X To save changes to a configuration file in Zmodem format

1. After making changes in the configuration menu, type Send then press
Enter to return to the main menu.

2. Type C, and then press Enter.

The configuration utility prompts you to confirm that you want to save
configuration data to a file.

3. Type Y, and then press Enter.

The utility saves the configuration file in Zmodem (with crash
recovery) format in HyperTerminal’s default directory. The file is
named DEV<devinst>.DCF, where <devinst> is the BACnet device
instance of the device.

Sending configuration files

You can update the configuration file on the module by replacing it with the file
on the local computer.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 31

Installation and Operations Guide | BACtalk Control Modules

X To send a configuration file to a BCM

1. Connect to the BCM with HyperTerminal and log in. See “Connecting
to the BCM with HyperTerminal” on page 22.

2. From the Transfer menu in HyperTerminal menu, select Send File.

The Send File dialog box appears.

3. Click the Browse button, select the file you want to send, and then click
Open.

4. In the Protocol field, select Zmodem.

5. Click Send.
HyperTerminal provides information about the status of the send
operation in a dialog box that automatically closes when the send
operation finishes. The configuration utility provides feedback about
the status of the send operation and prompts you to load the new file.

6. Type Y and press Enter to load the new configuration file to the BCM.
The send operation is complete and the main menu appears.

32 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Final setup and checkout at the operator workstation

Final setup and checkout at the operator workstation

After the BCM is configured with HyperTerminal and connected to appropriate
networks, use Envision for BACtalk to:

• Confirm network communications, if applicable, and add a record to

Device Manager
• Download DDC
• Set up automation features

If the BCM is on a BACnet internetwork, the operator workstation can connect

using the internetwork. In stand-alone applications, you can use an Ethernet
connection (using a crossover cable or a hub) or a modem connection.

See Envision for BACtalk online help for step-by-step instructions.

Scanning for the BCM and setting up a device record

Use Device Manager to confirm that the BCM is online and to add a device
record for ongoing management. The device record stores setup information
about the BCM. An accurate device record is the key to managing DDC, ROC
files, and automation features.

CAUTION A device record must exist in Device Manager for you to view and
change BCM values using Envision for BACtalk.

Use the Device Scan feature to scan the network for the BCM. This is the easiest
way to add a record and also ensures that the BCM is communicating. Once a
device record exists, use Device Manager to send data to and read data from the
BCM. See the Envision for BACtalk Installation and Startup Guide (LTBT-TM-
ADMIN) or the Envision for BACtalk Operator’s Manual (LTBT-OP-EBT20)
for more information about working in Device Manager.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 33

Installation and Operations Guide | BACtalk Control Modules

BCM-PWS module
The BCM-PWS requires 19 - 30 VAC @ 30 VA, 47–63 Hz power for itself and
all connected modules. The BCM-PWS uses a half-wave rectifier, which enables
it to share a power supply with other half-wave devices.

If the BCM-PWS loses operating power, it reverts to a 7.2 volt NiCad battery,
which provides interim power to the BCMs so they can conduct an orderly
shutdown.

34 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-ETH module

BCM-ETH module
This section describes details specific to the BCM-ETH module. See other
sections in this manual for similar details about other available modules.

The BCM-ETH module is a BACnet router and controller that supports BACnet/
IP and is capable of operation as a BACnet Broadcast Management Device
(BBMD). Install the BCM-ETH in the middle of the BCM array for optimal
performance.

The BCM-ETH supports BACnet Ethernet and MS/TP connections, making I/O,
operational, and functional data for connected BACnet devices available to the
site-wide automation system as BACnet objects and properties.

Note Since the BCM-ETH processes every Ethernet packet it receives to

determine if it must be routed to one of the connected modules, it is critical that
you use a switch to connect the BCM-ETH to the Ethernet network. Otherwise,
the BCM-ETH could be overwhelmed if it is connected to a busy Ethernet
network.

BACnet devices connect to the BCM-ETH’s MS/TP connection over a simple

shielded, twisted-pair bus. The BCM-ETH hosts automation features (schedules,
trendlogs, and alarms) and DDC for any BACnet device on its MS/TP network.

The BCM-ETH connects to other BCM modules using a keyed ribbon cable. The
ribbon cable provides power and connectivity to the modules. For this reason,
the BCM-ETH requires at minimum a BCM-PWS to be installed.

The Alerton BCM-ETH is a high-performance router and global controller. Use

the BCM-ETH to:

• Route BACnet messages between BACnet MS/TP, Ethernet and IP

networks. The BCM-ETH supports one of each network type.
• Serve as a BACnet broadcast management device (BBMD) on a
BACnet/IP wide area network (WAN).
• Host automation features such as schedules, trendlogs, alarms, optimum
start, demand limiting, and tenant activity for connected BACnet
devices.
• Run DDC sequences for connected BACnet devices.
Note See the BCM-ETH version history for a complete list of changes and
enhancements made with each new release of the BCM-ETH ROC. View the file
from the ROC downloads page on the ASN.

Note See the BACtalk System Design Guide (LTBT-TM-SYSDSGN) for

information on using a BCM as a BBMD with Network Access Translation
(NAT).

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 35

Installation and Operations Guide | BACtalk Control Modules

automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 13 Programming features
Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle

time is typically 1 second but may be longer for large
DDC files.

Branch points 2048 branch points (0-2047).

AVs and BVs 1000 AVs and 1000 BVs. BVs support the priority-array.

Schedules Supports 65 schedules and 65 calendar objects.

Alarms Supports 256 alarms.

Trendlogs Supports 256 trendlog objects.

Zones Supports 65 BACtalk zone objects.

Tenant activity logs Supports 65 tenant activity logs.

Demand limiting Supports two demand limiter objects, each with 100
loads defined.

36 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-ETH module

Technical data
Ta ble 14 BCM-ETH hardware capabilities
Controller support on 65 VLCs max. supported on MS/TP LAN.
MS/TP LAN

Power Provided through ribbon cable connection to the

BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to

back up DDC, automation features, and software objects to
flash memory.

Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.

Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.

32-bit, high-integration Motorola CPU.

Real-time clock Onboard real-time clock supports schedule operations,

trendlogs, and timed DDC functions.

BACnet Ethernet Integrated Ethernet adapter circuitry with RJ-45 jack for
connection to 10Base-T or 100Base-TX networks.

BACnet Internet Protocol IP support for interoperability on wide area networks

(BACnet/IP) (WANs) and campus area networks (CANs). Functions as
a BACnet broadcast management device (BBMD) in
accordance with Annex J BACnet/IP.
BACnet MS/TP Removable, header-style screw terminals for 1 BACnet
MS/TP (shielded, twisted-pair bus) LAN. Supports 65
VLCs. Configurable from 9.6 to 76.8 Kbps.

Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.

(122mm) D.

Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.
BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy

Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Configuration settings unique to this module

Before you can set configuration settings, you must connect to the module using
HyperTerminal. See “Connecting to the BCM with HyperTerminal” on page 22
for instructions.

The BCM-ETH supports connection to the Ethernet network. See “Configuring

settings that apply to most modules” on page 26 for more information.

The BCM-ETH also supports MS/TP connections. MS/TP network settings are
accessed through item D on the Change Configuration screen. See Table 21 on
page 47 for information about MS/TP network settings.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 37

Installation and Operations Guide | BACtalk Control Modules

I MP O R TA N T BACnet/IP settings rely on correct Ethernet network settings

and connections. See Table 10 on page 26 .

Figure 11 BCM-ETH: IP network settings

Ta ble 15 BCM-ETH: BACnet/IP settings

Field Values Remarks Default

A. IP Enabled? Y|N Y = Enables IP support. N
N = Disables IP support. Default.
If the device is on an Ethernet LAN but does not use IP,
ensure that IP Enabled = N (or that IP Address = 0.0.0.0).
This prevents the device from sending any IP messages
over the LAN. Default is N and IP Address is set to
0.0.0.0. IP won't run until IP Address is set.

B. IP Frame Type? DIX | 802.2 The Ethernet frame type used for incoming and outbound DIX
IP transmissions. The primary difference between frame
types is the LLC header.
DIX = The device generates and routes DIX (Ethernet II)
frames. Default.
802.2 = The device generates and routes 802.2 (also
known as 802.3/802.2-not RAW Ethernet) frames.

C. Reassembly Time- 1-300 The fragment reassembly time-out, in seconds. Default is 120
out 120.

D. Maximum MTU 90-1500 The Maximum Transmission Unit (MTU) in bytes. Default 1500
is 1500 (typical for Ethernet networks).

E. Time to Live 001-255 Sets the initial Time to Live (TTL) value for IP packets 64
sent from this device. TTL enumerates the number of
hops (the number of forwarding routers) the packet is
allowed to pass between source and destination. This
prevents looping packets from crashing routers and
saturating entire links or networks. Default is 64.

38 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-ETH module

Ta ble 15 BCM-ETH: BACnet/IP settings (Continued)

Field Values Remarks Default

F. Type of Service 0-15 Sets the 4-bit type of service (TOS) value in the IP packet 0
header. Some applications may use TOS to provide
precedence levels and determine optimum routing
methods for packets. Default is 0.

Value TOS bits Description

0 0000 Default

1 0001 Minimize monetary cost

2 0010 Maximize reliability

4 0100 Maximize throughput

8 1000 Minimize delay

15 1111 Maximize security

G. IP Address nnn.nnn.nnn.nnn The IP address assigned to this device in dotted-decimal 0.0.0.0

format. nnn is a number from 0-255. Follow IP addressing
conventions and rules for your network. Default is 0.0.0.0,
which prevents IP operation event when IP Enabled? = Y.

H. Subnet Mask nnn.nnn.nnn.nnn The netmask value for transmission on this network in 255.255.255.0
dotted-decimal. Follow IP netmasking conventions and
rules. Default is 255.255.255.0, which is typical.

I. Gateway 1 Address nnn.nnn.nnn.nnn The IP address, in dotted-decimal, of the primary IP 0.0.0.0

router the device uses to connect to the IP internetwork.
nnn is a number from 0-255. Default is 0.0.0.0, indicating
no device.
J. Gateway 2 Address nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the 0.0.0.0
secondary IP router the device uses to connect to the IP
internetwork. nnn is a number from 0-255. Default is
0.0.0.0, indicating no device.

K. Configure private See table below.

BACnet/IP

L. Configure public See table below.

BACnet/IP

M. Disable Local Y|N N

Annex-J Broadcasts?

Broadcast Distribution Table (BDT) entries

The broadcast distribution table (BDT) contains three associated entries for each BACnet/IP broadcast management device
(BBMD) on the IP Virtual Net being defined. A maximum of 32 devices is supported. Each BBMD should have an entry for itself
in its BDT. The three entries must be assigned for each BBMD on the Virtual Network. For each BBMD, the first entry identifies
the IP address, the second the UDP port associated with the BBMD, and the third the netmask used on the BBMD's subnet.
Usually, BBMDs have identical BDTs because one is set up as the BDT server (see “Server IP Address” and “Server UDP Port”
herein).

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 39

Installation and Operations Guide | BACtalk Control Modules

Figure 12 BCM-ETH: Configure private BACnet/IP

40 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-ETH module

Ta ble 16 BCM-ETH: Configure private BACnet/IP settings

Field Value Remarks Default

A. Private BACnet/IP Y|N Y = Enables IP support. Y
Enabled? N = Disables IP support. Default.
If the device is on an Ethernet LAN but does not use IP, ensure
that IP Enabled = N (or that IP Address = 0.0.0.0). This
prevents the device from sending any IP messages over the
LAN. Default is N and IP Address is set to 0.0.0.0. IP won't run
until IP Address is set.

B. Virtual Net Number 1-65,534 The BACnet network Number is assigned to the virtual network 1
created by the IP WAN. All BBMDs participating on the IP WAN
(in other words, all BBMDs in the broadcast distribution table)
must have this Virtual Net Number set to the same number.
This Network Number must also be unique with respect to the
internetworked BACnet LANs. It cannot match other BACnet
Network Numbers (Ethernet LANs, MS/TP LANs, ARCNET
LANs, etc.) Default is 1.
C. Local UDP Port 1-65,534 The local UDP port is how the global controller speaks to the 47808
gateway. The UDP port of this controller, which is used to
establish connectionless transmission over IP with other
BACnet/IP-enabled controllers. This UDP port must be the
same as other BACnet/IP-enabled controllers on the same
subnet, especially if the controllers exchange messages only
using BACnet/IP (BACnet/Eth = NO).
There are notable exceptions to this rule:
• When another BBMD is on the same subnet, the UDP ports
of the BBMD must be different.
• Any device on the same subnet that registers with the BBMD
as a foreign device (such as a BACnet operator workstation)
must have a different local UDP port from the BBMD.
Only those controllers with the same UDP port on a subnet will
exchange BACnet/IP messages. For best results, always
ensure that controllers on an internetwork use the same UDP
ports.

H. BDT Server IP Address nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the device that 0.0.0.0
functions as the broadcast distribution table (BDT) server to
this device. This BBMD can retrieve its routing table from the
BDT Server if its own BDT is lost for any reason. If left to
000.000.000.000, the BDT must be reentered manually. For
this reason, the IP address of the BDT server should appear in
its own routing table.

I. BDT Server UDP Port 1-65,534 The UDP port of the broadcast distribution table (BDT) server 47808
defined under Server IP Address.

J. Get BDT from Server Y|N When set to Y, the device will read the broadcast distribution N
table (BDT) from the BDT server when you save changes and
exit the configuration utility. Pending: Yes|No indicates the
status of the setting. If Pending = Yes, the command will
execute when you save changes and exit.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 41

Installation and Operations Guide | BACtalk Control Modules

Figure 13 BCM-ETH: Configure public BACnet/IP

42 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-ETH module

Ta ble 17 BCM-ETH: Configure public BACnet/IP settings

Field Value Remarks Default

A. Public BACnet/IP Y|N Y = Enables IP support. N
Enabled? N = Disables IP support. Default.
If the device is on an Ethernet LAN but does not use IP, ensure
that IP Enabled = N (or that IP Address = 0.0.0.0). This
prevents the device from sending any IP messages over the
LAN. Default is N and IP Address is set to 0.0.0.0. IP won't run
until IP Address is set.

B. Virtual Net Number 1-65,534 The BACnet network Number is assigned to the virtual network 1
created by the IP WAN. All BBMDs participating on the IP WAN
(in other words, all BBMDs in the broadcast distribution table)
must have this Virtual Net Number set to the same number.
This Network Number must also be unique with respect to the
internetworked BACnet LANs. It cannot match other BACnet
Network Numbers (Ethernet LANs, MS/TP LANs, ARCNET
LANs, etc.) Default is 1.
C. UDP Port 1-65,534 The UDP port of this controller, which is used to establish 47809
connectionless transmission over IP with other BACnet/IP-
enabled controllers. This UDP port must be the same as other
BACnet/IP-enabled controllers on the same subnet, especially
if the controllers exchange messages only using BACnet/IP
(BACnet/Eth = NO).
• There are notable exceptions to this rule:
• When another BBMD is on the same subnet, the UDP ports
of the BBMD must be different.
• Any device on the same subnet that registers with the BBMD
as a foreign device (such as a BACnet operator workstation)
must have a different local UDP port from the BBMD.
Only those controllers with the same UDP port on a subnet will
exchange BACnet/IP messages. For best results, always
ensure that controllers on an internetwork use the same UDP
ports.

H. Public IP Address nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the device that 0.0.0.0
functions as the server to this device. This is the public-facing
(NAT) IP address.

I. Public UDP Port 1-65,534 The UDP port of the server defined under Server IP Address. 47808
This is the public-facing (NAT) UDP port number.

Note See the BACtalk System Design Guide (LTBT-TM-SYSDSGN) for more
information about Network Address Translation (NAT) and to view example
configurations.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 43

Installation and Operations Guide | BACtalk Control Modules

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM provide important information about operation
and connection to networks.
Ta ble 18 BCM-ETH LEDs

Function LED label Description

Diagnostics SYS ON = System boot code (loader) is valid and
running.
Momentary OFF = ROC is updating system boot
code.
OFF = Loader in flash memory is not valid.
Factory service is required.

ROC ON = Real-time operating code (ROC) loaded

and running.
OFF = ROC not running.

DDC FLASHING = DDC loaded and operational (LED

changes state with each DDC cycle).
OFF = DDC not loaded or not executing.
BAT ON = Unit is operating from battery power.
OFF = Unit is operating from 24 VAC power or
not powered at all.

Ethernet LINK ON = Link to Ethernet network has been

established.

TX ON or flashing = Ethernet transmitter is active.

RX ON or flashing = Ethernet receiver is active.

100 Mbps ON = 100Mbps link is established.

MS/TP RX ON or flashing = Incoming MS/TP

communications.

TX ON or flashing = Outgoing MS/TP

communications.

44 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MS/TP module

BCM-MS/TP module
This section describes details specific to the BCM-MS/TP module. See other
sections in this manual for similar details about other available modules.

The BCM-MS/TP is a BACnet controller that supports BACnet/IP and is

capable of operation as a BACnet Broadcast Management Device (BBMD)
when connected to a BCM-ETH.

The BCM-MS/TP supports a BACnet MS/TP connection, making I/O,

operational, and functional data for connected BACnet devices available to the
site-wide automation system as BACnet objects and properties.

BACnet devices connect to the MS/TP connection over a simple shielded,

twisted-pair bus. The BCM-MS/TP hosts automation features (schedules,
trendlogs, and alarms) and DDC for any BACnet device on its MS/TP network.

The BCM-MS/TP connects to other BCM modules using a keyed ribbon cable.
The ribbon cable provides power and connectivity to other modules for the
BCM-MS/TP. For this reason, the BCM-MS/TP requires at minimum a
BCM-PWS to be installed.

Use the BCM-MS/TP to:

• Route BACnet messages between BACnet MS/TP and Ethernet.

• Serve as a BACnet broadcast management device (BBMD) on a
BACnet/IP wide area network (WAN).
• Host automation features such as schedules, trendlogs, alarms, optimum
start, demand limiting, and tenant activity for connected devices.
• Run DDC sequences for connected devices.

Note See the BCM-MS/TP version history for a complete list of changes and
enhancements made with each new release of the BCM-MSTP ROC. View the
file from the ROC downloads page on the ASN.

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up
automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 19 Programming features

Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle
time is typically 1 second but may be longer for large
DDC files.
Branch points 2048 branch points (0-2047).

AVs and BVs 1000 AVs and 1000 BVs. BVs support the priority-array.

Schedules Supports 65 schedules and 65 calendar objects.

Alarms Supports 256 alarms.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 45

Installation and Operations Guide | BACtalk Control Modules

Ta ble 19 Programming features

Trendlogs Supports 256 trendlog objects.

Zones Supports 65 BACtalk zone objects.

Tenant activity logs Supports 65 tenant activity logs.

Demand limiting Supports two demand limiter objects, each with 100
loads defined.

Technical data

Ta ble 20 BCM-MS/TP hardware capabilities

Controller support on 65 VLCs max. supported on MS/TP LAN.
MS/TP LAN

Power Provided through ribbon cable connection to BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to
back up DDC, automation features, and software objects to
flash memory.
Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.

Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.

32-bit, high-integration Motorola CPU.
Real-time clock Onboard real-time clock supports schedule operations,
trendlogs, and timed DDC functions.

BACnet Ethernet Ethernet connection to 10Base-T or 100Base-TX networks

through its ribbon cable connection to a BCM-ETH.

BACnet Internet Protocol IP support for interoperability on wide area networks

(BACnet/IP) (WANs) and campus area networks (CANs). Functions as
a BACnet broadcast management device (BBMD) in
accordance with Annex J BACnet/IP.
NOTE: Can only act as a BBMD if a BCM-ETH is present.

BACnet MS/TP Removable, header-style screw terminals for 1 BACnet

MS/TP (shielded, twisted-pair bus) LAN. Supports up to 65
VLCs. Configurable from 9.6 to 76.8 Kbps.

Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.

(122mm) D.
Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.

BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy

Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Configuration settings unique to this module

Before you can set configuration settings, you must connect to the module using
HyperTerminal. See “Connecting to the BCM with HyperTerminal” on page 22
for instructions.

46 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MS/TP module

MS/TP network settings are accessed through item D on the Change

Configuration screen.

Note There are certain configuration settings required for all modules. See
“Configuring settings that apply to most modules” on page 26 for more
information.

Figure 14 The MS/TP configuration screen in the BCM Configuration Utility

Ta ble 21 MS/TP network settings

Item Value Remarks

A. MS/TP Network 1–65,534 Sets the BACnet network number for the
Number MS/TP LAN. Each interconnected BACnet
network must have a network number unique
throughout the internetwork. Selecting a
number in the range 1–65,534 (and not 0) is
highly recommended for flexibility and future
compliance.

B. MS/TP MAC 0-127 Sets the MAC address of the unit on the
MS/TP LAN. Each BACnet device on an
MS/TP LAN must have a unique MAC address.
The device has a default MS/TP MAC address
of 0.

C. MS/TP Kbps 9.6, 19.2, Sets the communication speed for the MS/TP
38.4, 76.8 LAN.

D. Enable support for Y|N Set to Y if any VLCs with firmware v1.02 or
VLCs with firmware v1.02 earlier are connected to the MS/TP LAN.
and earlier

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 47

Installation and Operations Guide | BACtalk Control Modules

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM provide important information about operation
and connection to networks.
Ta ble 22 BCM-MS/TP LEDs

Function LED label Description

Diagnostics SYS ON = System boot code (loader) is valid and
running.
Momentary OFF = ROC is updating system boot
code.
OFF = Loader in flash memory is not valid.
Factory service is required.

ROC ON = Real-time operating code (ROC) loaded

and running.
OFF = ROC not running.

DDC FLASHING = DDC loaded and operational (LED

changes state with each DDC cycle).
OFF = DDC not loaded or not executing.
BAT ON = Unit is operating from battery power.
OFF = Unit is operating from 24 VAC power.

Status RX ON or flashing = Incoming MS/TP

communications.

TX ON or flashing = Outgoing MS/TP

communications.

NAT Firewall Limitation

Under certain scenarios, BCM-MS/TP will not communicate across a NAT
firewall. In a job with two arrays that communicate using IP only, with one array
behind a NAT firewall and the other array outside the NAT firewall, the
BCM-MS/TP outside the firewall will not communicate with modules behind
the firewall.

48 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-TUX module

BCM-TUX module
This section describes details specific to the BCM-TUX module. See other
sections in this manual for similar details about other available modules.

The BCM-TUX reads TUX data from up to 64 Alerton TUXs on an IBEX TUX
trunk and makes the data available to the BACnet network as BACnet objects
and properties. The BCM-TUX enables your BACnet system to read and write
TUX point data, as well as read TUX alarms.

The BCM-TUX connects to another BCM module using a keyed ribbon cable.
The ribbon cable provides power and connectivity to other modules for the
BCM-TUX. For this reason, the BCM-TUX requires at minimum a BCM-PWS
to be installed.

The Alerton BCM-TUX is a high-performance global controller. Use the

BCM-TUX to:

• Serve as a BACnet broadcast management device (BBMD) on a

BACnet/IP wide area network (WAN).
• Host automation features such as schedules, trendlogs, alarms, optimum
start, demand limiting, and tenant activity.
• Run building-wide DDC sequences.

Note See the BCM-TUX version history for a complete list of changes and
enhancements made with each new release of the BCM-TUX ROC. View the file
from the ROC downloads page on the ASN.

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up
automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 23 Programming features
Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle

time is typically 1 second but may be longer for large
DDC files.

Branch points 2048 branch points (0-2047).

AVs and BVs 1000 AVs and 1000 BVs. BVs support the priority-array.

Schedules Supports 64 schedules and 64 calendar objects.

Alarms Supports 256 alarms.

Trendlogs Supports 256 trendlog objects.

Zones Supports 64 BACtalk zone objects.

Tenant activity logs Supports 64 tenant activity logs.

Demand limiting Supports two demand limiter objects, each with 100
loads defined.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 49

Installation and Operations Guide | BACtalk Control Modules

Technical Data

Ta ble 24 BCM-TUX hardware capabilities

Controller support on 64 TUXs max. supported on IBEX TUX trunk.
TUX trunk
IMPORTANT! Only TUXs communicating at 4800 or 9600
are supported.

Power Provided through ribbon cable connection to BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to

back up DDC, automation features, and software objects to
flash memory.

Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.

Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.

32-bit, high-integration Motorola CPU.
Real-time clock Onboard real-time clock supports schedule operations,
trendlogs, and timed DDC functions.

BACnet Ethernet Ethernet connection to 10Base-T or 100Base-TX networks

through a ribbon cable connection to a BCM-ETH.
BACnet Internet Protocol IP support for interoperability on wide area networks
(BACnet/IP) (WANs) and campus area networks (CANs). Functions as
a BACnet broadcast management device (BBMD) in
accordance with Annex J BACnet/IP.
NOTE: Can only act as a BBMD if a BCM-ETH is present.
TUX trunk Removable, header-style screw terminals for 1 TUX trunk
(shielded, twisted-pair bus). Auto-detects TUX trunk baud
rate or manually configurable.
Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.
(122mm) D.

Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.

BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy

Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Configuration settings unique to this module

Before you can set configuration settings, you must connect to the module using
HyperTerminal. See “Connecting to the BCM with HyperTerminal” on page 22
for instructions.

For BCM TUX modules, TUX network settings are accessed through item D on
the Change Configuration screen.

50 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-TUX module

Note There are certain configuration settings required for all modules. See
“Configuring settings that apply to most modules” on page 26 for more
information.

Figure 15 The TUX configuration screen in the BCM Configuration Utility

Ta ble 25 TUX network settings

Item Value Remarks Default

TUX Base 0 - 4194303 This is the device instance of the first virtual 10200
Device device on the TUX trunk (TUX trunk address 0).
Instance
IMPORTANT! This number must be unique. It
cannot match any other base or virtual device
instance on the network.

TUX Virtual 1 - 65,534 This is the network number assigned to the TUX 22222
Network trunk. All TUXs are referenced in BACnet with
Number respect to this number.
IMPORTANT! This number must be unique. It
cannot match any other network number.

TUX Kbps 1200, 4800 The BCM-TUX can only support TUXs 9600
or 9600 communicating at 4800 or 9600 Kbps Now
supports 1200 baud with Envision for BACtalk
v2.0 or later.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 51

Installation and Operations Guide | BACtalk Control Modules

Figure 16 BCM-TUX: Auto/manual TUX trunk adjustment (Menu D)

Ta ble 26 BCM-TUX: Auto/manual TUX trunk adjustment settings

Item Value Remarks Default

Automatic Trunk Y|N BCM automatically adjust to maintain Y
Tuning Enabled appropriate TUX voltage

Manual Drive 1-100 User can manually tune trunk -

Decrease Manual N|A Increment down on percent (%) -

Drive by 1%
Increase Manual N|A Increment up in percent (%) -
Drive by 1%

52 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-TUX module

Figure 17 BCM-TUX: 1200 Baud Expanded Mode configuration. NOTE: This

screen is only displayed after a newer TUX operating at 1200 baud is specified.

A 1200 baud TUX does not support expanded mode. Newer TUXes on a
1200 baud trunk can be configured according to the table below.
Ta ble 27 BCM-TUX: 1200 Baud Expanded Mode configuration settings

Item Value Remarks Default

A. TUX Address 00 Y|N Sets the expanded mode for the address 00. N
Expanded Mode
Enabled
B. TUX Address 01 Y|N Sets the expanded mode for address 01. N
Expanded Mode
Enabled

C. TUX Address 02 Y|N Sets the expanded mode for address 02. N
Expanded Mode
Enabled

D-P... Y|N Sets the expanded mode for the specified N

address.

How the BCM-TUX exposes TUXs and TUX data to BACnet

On the BACnet network, the BCM-TUX has one device instance associated with
its physical presence. The BCM-TUX hosts a virtual network for the TUX trunk
and a virtual device instance for each TUX on the TUX trunk (up to 64). These
virtual device instances are based on the TUX base device instance added
together with the address of the TUX (set with DIP switches).

TUX Virtual DI = TUX Base DI + TUX DIP

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 53

Installation and Operations Guide | BACtalk Control Modules

For example, if you set a base TUX device instance of 10200 (using
HyperTerminal), a TUX with address 2 is identified in BACnet with device
instance 10202.

TUX data points as present-values of BACnet objects

The BACnet objects that the BCM-TUX generates from TUX data points
depends on the particular TUX model. The BCM-TUX automatically assigns
BACnet objects to TUX data points based on the TUX type. See “Appendix F:
TUX data point to BACnet object mappings” on page 123 for a list of TUX data
points by TUX model and their mappings to BACnet objects.

The BCM-TUX makes TUX data available as the present-value property of the
BACnet object. The object and its properties are referenced by the Virtual TUX
Device Instance.

For example, AI-1 in a TX-VAV, which represents space temperature in degrees

(see “TX-VAV” on page 128), maps to the present-value of BACnet object AI-1
in the corresponding virtual device. If the TUX has its DIP switch address set to
4, and the BCM-TUX has a base TUX device instance of 10200, you reference
this data point in BACnet as Device 10204, AI-1, present-value (Device 10204 is
the Virtual Device Instance of the TUX in BACnet).

Note If a corresponding input or output doesn’t exist, and an object property is

referenced, the BCM-TUX returns an UNKNOWN_OBJECT for the present-
value property, UNRELIABLE_OTHER for the reliability property, and FAULT
for the status-flags property.

Using the alerton-gateway-setup property

Use this special property of AIs and AOs to customize data translation if
necessary (see “Appendix E: The alerton-gateway-setup property” on page 121)
from TUX to BACnet object and vice versa. In most cases, customizing the
alerton-gateway-setup property is not necessary. The BCM-TUX uses
appropriate defaults. Defaults are listed for each object in “Appendix F: TUX
data point to BACnet object mappings” on page 123.

How to convert APEX DDC for use in the BCM-TUX

The BCM-TUX serves as the global controller for all connected TUXs. If you
are converting an existing IBEX system to a BACtalk system, you must first
write new global controller DDC in the BCM-TUX to replace functions that

54 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-TUX module

were normally provided by the APEX in your IBEX system. Use the following
table to determine how to accomplish these functions in your BACtalk system.

Function If you did this in IBEX... Do this in BACtalk...

Schedule operation of a TUX Linked a control panel to the TUX and In the virtual device, set up the BO that
transferred the Zone Generic Day point to represents the TUX as a scheduled point in
the appropriate TUX DO (typically, DO 3) BACtalk (typically, BO 3).
using subroutine DDC.

Enable heating, cooling, and unit Used APEX DDC to send ON values to DOs Set up DDC in the BCM-TUX to write to the
operation in application specific TUXs. appropriate BO in the virtual device. See the
IBEX technical manual to identify the BO to
write to (typically BO 1, BO 2, or BO 8).

Programming with zone custom Used APEX DDC to generate values for Place available AVs and BVs (not mapped
points zone custom points that you placed on a to specific TUX points) in the virtual device
control panel template. on a device template. See “Appendix F:
TUX data point to BACnet object mappings”
on page 123 for information about TUX
point mapping.
Zone TUX points Used TUX points in control panel DDC. Use the Set Context function in Global/
Building Controller DDC.

Pulse data conversion Used Device 9 (APEX DDC) to convert Use DDC math functions in Global/Building
compound data (AI 1 through AI 6) from a Controller DDC.
TX-651 Pulse to consumption and rate.

View, create and edit TUX DDC Used TUX DDC in IBEX operator You cannot view, create or edit TUX DDC in
workstation software to view, create and edit BACtalk. Create and edit TUX DDC using
DDC. IBEX VisualLogic. If the TUX has a direct-
connect header, connect using an AC-2650
cable and use the TUX Development
System. Otherwise, connect using an IBEX
global controller and the TUX Interface
Device.

Control Panel Subroutines The TUX is linked to a control panel using Use the Set Context Function to reference a
Device 80. changing device in Subroutine DDC.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 55

Installation and Operations Guide | BACtalk Control Modules

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM provide important information about operation
and connection to networks.
Ta ble 28 BCM-TUX LEDs

Function LED label Description

Diagnostics SYS ON = System boot code (loader) is valid and
running.
Momentary OFF = ROC is updating system boot
code.
OFF = Loader in flash memory is not valid.
Factory service is required.

ROC ON = Real-time operating code (ROC) loaded

and running.
OFF = ROC not running.

DDC FLASHING = DDC loaded and operational (LED

changes state with each DDC cycle).
OFF = DDC not loaded or not executing.
BAT ON = Unit is operating from battery power.
OFF = Unit is operating from 24 VAC power.

TUX trunk COMM STATUS Flashing = Normal communication.

communications
ON = No communication (typically indicates a
status
short on the TUX network).
OFF = No communication (typically indicates a
bad BCM module or no power).

NAT Firewall Limitation

Under certain scenarios, BCM-TUX will not communicate across a NAT
firewall. In a job with two arrays that communicate using IP only, with one array
behind a NAT firewall and the other array outside the NAT firewall, the
BCM-TUX outside the firewall will not communicate with modules behind the
firewall.

56 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

BCM-MDBS module
This section describes details specific to the BCM-MDBS module. See other
sections in this manual for similar details about other available modules.

The BCM-MDBS is a BACnet-compliant gateway to a Modbus EIA-232,

EIA-422, or EIA-485 network. The BCM-MDBS is a fully programmable
network controller. It hosts its own schedules, calendars, alarms, trendlogs, and
DDC.

The BCM-MDBS connects Modbus devices—such as variable speed drives—to

a BACnet system, converting data from connected Modbus devices to BACnet
AV and BV objects. The BCM-MDBS has a capacity for 1000 AV and 1000 BV
objects—each AV and BV can be assigned to one Modbus data point. These
assignments are accomplished using the BACnet description property of the AV
or BV object to be mapped. The description property is an ASCII string.

On an EIA-485 or EIA-422 network, data from up to 247 slave nodes can be read
and written using the BACnet system. On an EIA-232 network, only one
Modbus device is supported.

CAUTION The number of slave nodes supported depends on the total unit
load. The BCM-MDBS supports a maximum unit load of 32.

You can also scale Modbus data. See “Syntax for description string” on page 62
for more information.

Note See the BCM-MDBS version history for a complete list of changes and
enhancements made with each new release of the BCM-MDBS ROC. View the
file from the ROC downloads page on the ASN.

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up
automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 29 Programming features
Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle

time is typically 1 second but may be longer for large
DDC files.

Branch points 2048 branch points (0-2047).

AVs and BVs 1000 AVs and 1000 BVs. BVs support the priority-array.

Schedules Supports 65 schedules and 65 calendar objects.

Alarms Supports 256 alarms.

Trendlogs Supports 256 trendlog objects.

Zones Supports 65 BACtalk zone objects.

Tenant activity logs Supports 65 tenant activity logs.

Demand limiting Supports two demand limiter objects, each with 100
loads defined.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 57

Installation and Operations Guide | BACtalk Control Modules

Technical Data

Ta ble 30 BCM-MDBS hardware capabilities

Modbus slave device Supports connection to one EIA-232 modbus device or up
support to 247 EIA-422 or EIA-485 Modbus slave devices.
NOTE: The number of devices supported depends on the
total unit load. The BCM-MDBS supports a maximum unit
load of 32.

Power Provided through ribbon cable connection to BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to

back up DDC, automation features, and software objects to
flash memory.

Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.
Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.
32-bit, high-integration Motorola CPU.

Real-time clock Onboard real-time clock supports schedule operations,

trendlogs, and timed DDC functions.
BACnet Ethernet Ethernet connection to 10Base-T or 100Base-TX networks
through its ribbon cable connection to a BCM-ETH.

BACnet Internet Protocol IP support for interoperability on wide area networks

(BACnet/IP) (WANs) and campus area networks (CANs). Functions as
a BACnet broadcast management device (BBMD) in
accordance with Annex J BACnet/IP.
NOTE: Can only act as a BBMD if a BCM-ETH is present.

Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.

(122mm) D.

Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.

BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy

Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Configuration settings unique to this module

Before you can set configuration settings, you must connect to the BCM-MDBS
using HyperTerminal. See “Connecting to the BCM with HyperTerminal” on
page 22 for more information.

For BCM-MDBS modules, use option D on the Change Configuration screen to

access Modbus protocol settings. Use option C on the Main Menu to view
modbus diagnostic information. See “Appendix H: Error indicators” on
page 168 for more information.

58 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

Note There are certain configuration settings required for all modules. See
“Configuring settings that apply to most modules” on page 26 for more
information.

Figure 18 BCM-MDBS Configuration screen

Ta ble 31 BCM-MDBS: Configuration settings

Item Value Remarks

A. Physical Port EIA-232, EIA-422, or Select the physical port on the
EIA-485 BCM-MDBS on which Modbus
communications will be
attempted. The setting is
indicated by an LED on the BCM-
MDBS faceplate.

B. Mode ASC or RTU Select one of two protocol

options: ASCII or RTU.

C. Parity NONE, ODD, or EVEN Select the parity of the Modbus

connection.

D. Stop Bits STD or ONE Select the number of stop bits per
character of the Modbus
connection. STD uses the
number of stop bits specified by
the Modbus specification (one
stop bit if even or odd parity is
used; two stop bits if no parity is
used).
NOTE: Some Modbus device
manufacturers do not follow the
Modbus specification and use
one stop bit with no parity; the
ONE option may be used to
match this behavior.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 59

Installation and Operations Guide | BACtalk Control Modules

Ta ble 31 BCM-MDBS: Configuration settings

Item Value Remarks

E. Baud 4.8, 9.6, 19.2, 38.4, Select the communication speed
57.6, 76.8, or 115.2 kbd for the connection.

F. Reply Timeout 10 - 5000 Specify the maximum time, in

milliseconds, that the BCM-
MDBS is to wait for a response
after issuing a request. This
allows the BCM-MDBS to
communicate with equipment that
has a long reply delay. The
default is 200 milliseconds.
NOTE: A long reply timeout can
result in slow communications if
there are assigned modbus
points that do not exist because a
full delay will occur each time a
request for data is sent to the
non-existent point.

G. Poll Delay 0 - 5000 Specify the minimum time delay,

in milliseconds, to occur between
BCM-MDBS requests. This
allows the BCM-MDBS to
communicate with equipment that
cannot handle a rapid succession
of requests. The default is 10
milliseconds.
NOTE: Extending the poll delay
slows down overall
communications so keep this
delay as short as the modbus
equipment will tolerate.

H. Reset Reply Timeout N/A Select this option to reset the

and Poll Delay to Reply Timeout and Poll Delay to
defaults their default settings.

I. Enable multiple register Y or N Select whether or not to allow the

requests BCM-MDBS to read multiple
register requests. When enabled,
the BCM-MDBS analyzes the
various modbus mapping set in
the AV and BV description
properties and combines read
requests for mappings to
sequential registers. The default
is N.
NOTE: You can override the
multiple register request setting
for individual modbus mappings
using the Mxx parameter in the
modbus mapping string. See
“Mapping Modbus data to AVs
and BVs” on page 61.

J. Multiple register limit 2-32 If the BCM-MDBS is set up to

allow multiple register requests,
define the maximum number of
modbus registers that can be
requested at the same time.
The default is 8.

60 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

Mapping Modbus data to AVs and BVs

The BCM-MDBS is a BACnet device that contains 1000 AV and 1000 BV
objects. The present-value of each AV and BV may be read from or written to
points on the Modbus network. Map each AV and BV to a single Modbus point
using the BACnet description property as described in “Assigning Modbus
addresses” on page 61. AVs and BVs that are not mapped to Modbus points may
be used for DDC or other control purposes by the BCM-MDBS.

Note BVs have priority arrays. When data from a Modbus device is written to a
BV, it is placed at priority 16. When data from a BV is written to a modbus
device, the BV’s present-value is the output data.

Assigning Modbus addresses

Modbus data points use an addressing format that combines a reference number
and a point address. For example, 0xxxx indicates reference 0 (zero), 1xxxx
indicates reference 1, and so on. The point address range is from 1 to 9999.
Therefore, 40010 is entered as reference 4 and address 10.

Note Some manufacturers bias the Modbus addresses by 1. That is, their point
addresses range 0-9999 instead of 1-9999. In these cases you need to assign their
register address +1. For example, to read their register 3, you would assign
register 4.

When you set up a data mapping, you specify the type of object in the BACtalk
system to use to map data. You also specify whether the item is intended for a
read-only input or whether it should be commanded from the BACnet system.
The reference type of the Modbus data determines how you need to map it (see
the following table) and “Syntax for description string” on page 62 for more
information.
Ta ble 32 Modbus addressing format

Reference Type BACnet Remarks

(NX reference) Object
0x BV Can be set up as Input or Output.

1x BV Modbus read-only. Must be set up as Input.

3x BV or AV Modbus read-only. Must be set up as Input.

(analog)

4x BV or AV Can be set up as Input or Output.

(analog)

6x BV or AV Can be set up as Input or Output.

(analog)

Note A BV mapped to a reference type 3 or 4 would typically use the bitmap

option.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 61

Installation and Operations Guide | BACtalk Control Modules

Syntax for description string

The description string is a BACnet property of each AV and BV object. It is used
to assign a Modbus data point to a BACnet data object.

• Items in [brackets] are optional.

• Type items in boldface exactly as they appear.
• A vertical line separates exclusive options.
• Items set off in angle brackets and italics are variables.
• Commas are required between each argument with no spaces between
items.
N o t e Use a space instead of a comma between the last argument and
the descriptor.
• Use uppercase letters only.
• Each string can contain a maximum of 250 characters.

N o t e You do not need placeholder commas for undesired options; list

only the options you want.
In most cases, this Modbus mapping information is provided by the
manufacturer of the Modbus device as part of the data point assignment.

I | O | W | T | A, <Slave Address>, <Reference>, <Register or Coil Number>

[, <Extended Memory File Number>] [, F | Fb | Fl] [, L | Lb | Ll] [, BU<nn>]
[, <Real Number1>] [, <Real Number2>] [, M<nn>] <Descriptor>

62 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

Ta ble 33 Description string arguments

Argument Explanation
I|O|A|W|T Message type. Determines if the value will be an input (read-only) or output (writable). The Modbus
reference type determines acceptable entries.
I Read-only input from Modbus to BACtalk. The Modbus value is read into BACtalk and cannot be
commanded through the AV or BV present-value property. The BCM-MDBS performs a round-robin poll of
all input points to request values from the Modbus equipment.
O Verified output from BACtalk to Modbus using message code 6 (Preset Single Register) or message
code 5 (Force Single Coil). The Modbus value is writable through the AV or BV present-value property. On
change-of-state and during round-robin poll, the Modbus data is read and compared against BACtalk data.
A write to the Modbus point occurs only if the compared values are different.
Type O should be used for output points unless problems are encountered and especially if the Modbus
device stores its data in EEPROM. This eliminates unnecessary writes to EEPROM.
Note Use types A, T, and W when the Modbus device has problems with type O operation.
A Verified multiple register output from BACtalk to Modbus. The Modbus value is writable through the AV
or BV present-value property. Behaves precisely like the O point, but A values are written on the Modbus
side using the “Preset Multiple Registers” message (Modbus message code 16).
NOTE: The A designator can only be used with AV objects.
W Unverified output from BACtalk to Modbus using message code 6 (Preset Single Register). The
Modbus value is writable through the AV or BV present-value property. The value is not read from the
Modbus side or compared to the BACtalk value. A write occurs on BACtalk change-of-state and during
round-robin poll of Modbus values. Note: The W option was added primarily for compatibility with Liebert
Modbus systems, which may flag points internally as NULL on reset. This caused an error message to
occur when the BCM-MDBS attempted to read them for comparison using the O point.
T Unverified multiple register output from BACtalk to Modbus. The Modbus value is writable through the
AV or BV present-value property. Behaves precisely like the W point, but T values are written on the
Modbus side using the “Preset Multiple Registers” message (Modbus message code 16). Developed
primarily for Triatek applications.
NOTE: The T designator can only be used with AV objects.

<Slave Address> Specifies the Modbus slave number where the data originates. Range is 1–247.

<Reference> Specifies the Modbus reference type. One digit. Acceptable values are 0, 1, 3, 4, or 6.
NOTE: The number in parenthesis below is the Modbus function code. See “Appendix G: Modbus function
codes” on page 167 for more information.
For operation I: 0=read coil status (binary) (1), 1=read input status (binary) (2), 3=read input register
(analog) (4), 4=read holding register (analog) (3), 6=read general reference (analog) (20).
For operation O: 0=read coil status (1) then write (5), 4=read holding register (3) then write (16), 6=read
general reference (20) then write (21).
For operation A: 4=read holding register (3) then write (16).
For operation W: 0=write coil status (5), 4=write holding register (6)
For operation T: 4=write holding register (16)

Register or Coil Specifies the Modbus register or coil address. Range is 1–9999.

<Extended Omit unless Reference is set to 6. When the reference type is set to 6, File Number must specify a file or
Memory File group number in the range 0–9999.
Number>
(optional)

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 63

Installation and Operations Guide | BACtalk Control Modules

Ta ble 33 Description string arguments (Continued)

Argument Explanation
F | Fb | Fl Optional floating point designation to support the reading and writing of floating point values when
(optional) interfacing to Modbus equipment that stores such values in two consecutive Modbus register addresses.
The F designator can only be used with AV objects.
When F is appended to the I message-type indicator, the Modbus register reference type must be 3 or 4
(not 6). For example, the description string “I,1,4,206,F Sample float” requests a floating point value from
slave #1, register addresses 40206 and 40207.
When F is appended to an output message type (O,A,W,T) the BCM-MDBS writes the BACnet AV floating
point value to two consecutive Modbus registers, beginning with the register specified in the gateway string.
NOTE: The original Modbus standard did not support floating point. Modbus registers normally contain 2
bytes of data. Floating points contain 4 bytes. Some manufacturers store these 4 bytes in “Little endian”
order; others use “Big endian” order. Try swapping the order If you are not getting valid floating point data.
F= Fb = Big endian
Fl = Little endian
The option must immediately follow the preceding comma (no intervening spaces).

L | Lb | Ll Optional long integer point designation to support reading or writing of 32-bit integers when interfacing with
(optional) Modbus equipment that stores such values in two consecutive Modbus register addresses. The L
designator can only be used with AV objects.
When L is appended to the I message-type indicator, the Modbus register reference must be 3 or 4. For
example, the description string “I,1,4,206,L Sample long int” requests a long integer value from slave #1,
register addresses 40206 and 40207.
When L is appended to an output message type (O,A,W,T) the BCM-MDBS converts the BACnet AV
floating point value to a long integer and writes it to two consecutive Modbus registers, beginning with the
register specified in the gateway string.
NOTE: The original Modbus standard did not support long integers. Modbus registers normally contain 2
bytes of data. Long integer points contain 4 bytes. Some manufacturers store these 4 bytes in “Little endian”
order; others use “Big endian” order. Try swapping the order If you are not getting valid point data.
L= Lb = Big endian
Ll = Little endian
The option must immediately follow the preceding comma (no intervening spaces).

BU <nn> Bit Unpack. Some Modbus devices send bit-packed data. If the BU field is present, the bit number specified
(optional) in nn (0-15) are extracted and used as the present-value of the BACnet object. Use only for message type I
(read-only).
The option must immediately follow the preceding comma (no intervening spaces).

<Real Number1> Any real number, which will be used to scale Modbus data. See “Scaling point data” on page 64.
(optional)

<Real Number2> Any real number, which will be used to scale Modbus data. See “Scaling point data” on page 64.
(optional)

M <nn> Optional argument used to override the multiple register request setting for individual modbus mappings.
(optional) This option only operates on modbus data read request messages. See “Defining multiple register
requests” on page 65 for more information.

<Descriptor> Optional (recommended) text description.

(optional)
NOTE: This text is not used when constructing Modbus messages. It is only used in data displays.

Scaling point data

Use the two Real Number arguments in the description string to scale Modbus
data. You can scale Modbus data for AV objects only. The first Real Number
argument is applied first. Data sent to and from the Modbus device is a 16-bit
integer with a range of 0 to 65535. The manufacturer of the device should
provide the required math conversion. The format of the Real Number argument

64 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

is: * | + | - 123.456E-12 where at least one of the symbols *, +, or - must

appear. The following table shows valid combinations and their meaning.

Symbol Meaning
* Means multiply by a positive number
*+ Means multiply by a positive number
*- Means multiply by a negative
number
+ Means add a positive number
- Means subtract

• E and E+ are optional and followed by a positive power to 10 exponent.

• E- is optional and is followed by a negative power to 10 exponent.
N o t e Exponent is limited to the range of +/-38.

Examples
The following syntax examples show how scaling works for different situations.

Example 1
Modbus register 4 0032 reports sensed pressure 0-4095. You want AV 15 to read
as 0-300 psi. The Modbus slave address is 44.

AV 15 = ModbusValue * 300/4095
300/4095 = 0.07326.

Solution 1
The Description for AV 15 should be I, 44, 4, 32, *0.07326.

Example 2
Modbus register 44 now reports 820-4095 as gpm ranges 0-600.
The range is 600/(4095 -820) = 0.1832.
The offset = 820.

Solution 2
The Description for AV 15 should now be I, 44, 4, 32, -820.0, *0.1832.

Defining multiple register requests

The BCM-MDBS can be configured to optimize read messages by requesting
multiple registers for each message. The modbus protocol allows you to request
more that one register by specifying a base register address and a count of the
number of registers requested. Therefore, only sequential register addresses can
be requested in the same modbus message. If the “Enable multiple register
requests” option is set to Y, the BCM-MDBS analyzes the current modbus
mappings and attempts to optimize read requests. Depending on how your data is
mapped, this option can significantly increase the speed at which data is
refreshed. That is, if there are no sequential registers in the mappings, no
optimization can take place. Additionally, if the modbus equipment you are

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 65

Installation and Operations Guide | BACtalk Control Modules

interfacing with does not support multiple register read requests, the requests
will fail and most likely generate an exception message reply. See “Appendix H:
Error indicators” on page 168 for more information.

The actual grouping of mapped registers in the various requests is handled

automatically by the BCM-MDBS once the feature is enabled (that is, no other
user interaction is required). The following example shows how the BCM-
MDBS performs this grouping.

Example
AV 6 mapping: I, 1, 4, 34
AV 7 mapping: I, 1, 4, 35
AV 8 mapping: I, 1, 4, 32
AV 9 mapping: I, 1, 4, 33
AV 10 mapping: I, 1, 4, 37
AV 11 mapping: I, 1, 4, 38
BV 5 mapping: I, 1, 4, 33, BU4

Multiple Register Limit set to 3.

Actual mappings grouped by request:

x40032 AV 8
x40033 AV 9
x40033 BV 5
x40034 AV 6

x40035 AV 7

x40037 AV 10
x40038 AV 11

Assuming that these are the only mappings found in the BCM-MDBS, three data
request messages are made under multiple mode.

• One request is for three registers starting at x40032 (here the Multiple
Register Limit has come into play). The returned data is placed in the
present-value of AV 8, AV 9, BV 5, and AV 6.
• A second request is made for the single register x40035 since there were
no mapped consecutive registers to group it with. Returned data is
placed into the present-value of AV 7.
• A third request is made for 2 registers starting at register x40037. The
returned data will be placed into the present-value of AV 10 and AV 11.
Any scaling, floating point, long integer, or bit unpacking options
assigned to the various points will be applied and is not affected by the
multiple requests.

Overriding Multiple Mode

Use this option if a multiple register request must take place on a certain register
boundary or if a register only responds to a single register request.

When (M <nn>) is appended to the end of a mapping, a register request is made

(with the register specified in the mapping string as the base register of the
request). The number of registers requested is specified by <nn> and is limited

66 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

by the Multiple Register Limit parameter. The returned data from the request is
placed in the present-value of the AV specified in the mapping string, and also
into the present value of AVs that are mapped in this range.

Example 1
AV 10 mapping: I, 1, 4, 32, M3
AV 11 mapping: I, 1, 4, 33
AV 12 mapping: I, 1, 4, 34

Regardless of the other consecutive mappings that BCM-MDBS discovers while

analyzing the mapping strings, requests for registers x40032-34 are always made
in a single request. The response data is placed in the present-value of AV 10, AV
11, and AV 12.

Example 2
AV 6 mapping: I, 1, 4, 30
AV 7 mapping: I, 1, 4, 31
AV 10 mapping: I, 1, 4, 32, M1
AV 11 mapping: I, 1, 4, 34
AV 12 mapping: I, 1, 4, 35, M1

Assuming that these are the only assigned mappings, BCM-MDBS will request
two registers (x40030 and x40031) with a single request and place the returned
data in the present-value of AV 6 and AV 7. A request for the single register
x40032 is made with returned data placed into the present-value of AV 10. A
request for the single register x40034 is made with returned data placed into the
present-value of AV 11 (the BCM-MDBS was not able to optimize to a multiple
request because of the “M1” assigned to x40035 in AV 12. A request for the
single register x40035 is made with returned data placed into the present-value
of AV 12.

Overriding Single Mode

Use Single Mode and this override when most of the data needs to be requested
as single registers, but some data is only returned by multiple register request.

When (M <nn>) is appended to the end of a mapping, it overrides the single

mode and forces a multiple-register request. The number of registers requested is
determined by <nn> and is limited by the Max Multiple Count parameter. The
returned data from the request is placed in the present-value of the AV
corresponding to the mapping string, and also into the present-value of AVs that
are contained in this range, if they are mapped. The scaling, floating point, or
long integer options assigned to AVs in range is applied to the data returned.
Each mapping string that has this override assigned will be the base of a modbus
request (see Example 2 below).

Example 1
AV 6 mapping: I, 1, 4, 34
AV 7 mapping: I, 1, 4, 35
AV 10 mapping: I, 1, 4, 32, M4

BCM-MDBS makes a single request for four registers starting at x40032. The
response data is placed in the present-value of AV 10, AV 6, and AV 7. The data
returned for register x40033 will be discarded since there is no string mapping to
this register. For clarity it would make sense to map consecutive AVs to

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 67

Installation and Operations Guide | BACtalk Control Modules

consecutive registers, but this was avoided in this example for purposes of
instruction.

Example 2
AV 6 mapping: I, 1, 4, 34, M2
AV 7 mapping: I, 1, 4, 35
AV 10 mapping: I, 1, 4, 32, M4

BCM-MDBS makes a request for four registers starting at x40032. The returned
data for register x40032 is placed in the present-value of AV 10. The data
returned for register x40033-35 is discarded since x40033 is not mapped and the
“M2” option assigned to AV 6 specifies that a multiple message is to be used
with x40034 as its base. A request for two registers starting at x40034 is made
with returned data placed in the present-value of AV 6 and AV 7.

Setting up data mappings

Use the BACnet description property to assign a Modbus data point to a BACnet
data object. Each BACnet object can be assigned to read data from or write data
to a single Modbus data point.

The description property is a standard ASCII text string. If the BCM-MDBS

detects an error in the description string, it reports the error as a text string
appended to the front of the description when the string is read. See “Appendix
H: Error indicators” on page 168 for more information about errors.

Note You can still use the description property for AVs and BVs that are not
intended to be mapped to Modbus points. The BCM-MDBS assumes that any
description property that does not contain a comma as the 2nd character is not
intended to be a Modbus mapped point and an error string is not inserted.

X To map an AV or BV to a Modbus data address

1. In Edit Mode, open the data display where you want to place Modbus
data mappings.

2. From the Place Item menu, choose Prompted Property, and then click
the display where you want to place the item.

3. Double-click the item to view the Prompted Property Setup dialog box.

4. Click the command button beside the Property box to open the Object
Specification dialog box.

5. In the Device Instance field, type the device instance of the

BCM-MDBS and select the object type (AV or BV) and instance of the
AV or BV you want to use to map Modbus data.

68 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDBS module

6. From the Property list, choose description.

7. Click OK in the Object Specification dialog box, and then click Close in
the Prompted Property dialog box.

8. Repeat steps 2 through 7 for all data points you want to map.

9. Resize the prompted item to the size you want, save the display, and
close the Display Editor.

10. Open the display for viewing.

11. Click the command button for the prompted property you created.

12. In the Edit Property dialog box, under Value, type a mapping value for
the description property according to the guidelines in “Syntax for
description string” on page 62.

13. Click OK.

The data mapping is saved to the BCM-MDBS, and the present-value
displayed in BACtalk operator workstation software for that point now
reflects the value of the Modbus point.
N o t e When finished making assignments, use Device Manager to save
point data. On subsequent downloads, this data is available from the
hard disk, eliminating the need to reassign it.

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM-MDBS provide important information about
operation and connection to Modbus slave devices.
Ta ble 34 BCM-MDBS LEDs

Function LED label Description

Port 485 ON = Port is currently being used for Modbus
protocol.

422 ON = Port is currently being used for Modbus

protocol.

232 ON = Port is currently being used for Modbus

protocol.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 69

Installation and Operations Guide | BACtalk Control Modules

Ta ble 34 BCM-MDBS LEDs (Continued)

Function LED label Description

Status DTR ON = the module is ready to transmit.
OFF = indicates the module is not ready to
transmit.

DSR ON = normal operation

OFF = Module will disregard all signals (except
RI) appearing on the interchange circuits. It does
not indicate an actual link with any remote data
equipment.

RTS ON = the module is allowed to send data.

OFF = the module must stop sending data.
This LED normally remains on, but may blink off
during reception of large blocks of data.

CTS ON = the module is ready to send.

TX ON or flashing = Outgoing Modbus data.

RX ON or flashing = Incoming Modbus data.

Diagnostics SYS ON = System boot code (loader) is valid and

running.
Momentary OFF = ROC is updating system boot
code.
OFF = Loader in flash memory is not valid.
Factory service is required.

ROC ON = Real-time operating code (ROC) loaded

and running.
OFF = ROC not running.

DDC FLASHING = DDC loaded and operational (LED

changes state with each DDC cycle).
OFF = DDC not loaded or not executing.

BAT ON = Unit is operating from battery power.

OFF = Unit is operating from 24 VAC power.

NAT Firewall Limitation

Under certain scenarios, BCM-MDBS will not communicate across a NAT
firewall. In a job with two arrays that communicate using IP only, with one array
behind a NAT firewall and the other array outside the NAT firewall, the
BCM-MDBS outside the firewall will not communicate with modules behind the
firewall.

70 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-HOTEL module

BCM-HOTEL module
This section describes details specific to the BCM-HOTEL module. See other
sections in this manual for similar details about other available modules.

The BCM-HOTEL is a BACnet-compliant gateway to a hotel reservation and

check-in system using an EIA-232, EIA-485, or EIA-422 serial communications
line.

The BCM-HOTEL handles communications between the Ethernet LAN (to

which operator workstations, global controllers, and BACnet devices are
connected), hotel information system, and Annex J BACnet/IP. It can act as a
BACnet broadcast management device (BBMD) on a BACnet internetwork. See
“Setting IP network options” on page 26 for more information about BACnet/IP
settings.

The BCM-HOTEL has 10,000 BVs (numbered 0000 to 9999), each

corresponding to a room number as reported by the hotel information system in
ASCII format according to Protocol One, Protocol Two or CUSTOM. The
BCM-HOTEL also contains 10 AVs (numbered 0 to 9).

The hotel computer sends an ASCII message to the BCM-HOTEL when the
room is first rented and again when the guest checks out. Either message can be
repeated any number of times, but repetition is not necessary.

Note See the BCM-HOTEL version history for a complete list of changes and
enhancements made with each new release of the BCM-HOTEL ROC. View the
file from the ROC downloads page on the ASN.

Protocol One
This type of data transmission includes checksum data at the end of messages.

• 8 data bits
• No parity
• 1 stop bit
The message format is Exxxxy or Vxxxxy, where E = rented and V = vacant.

Character Meaning
1 E for check in, V for check out

2 Room number, thousands digit

3 Room number, hundreds digit

4 Room number, tens digit

5 Room number, ones digit

6 Checksum

To generate the checksum, add the room number digits in decimal and send the
ones place digit of the sum as an ASCII character.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 71

Installation and Operations Guide | BACtalk Control Modules

For example:

Meaning ASCII message BCM-HOTEL result

Room 413 is rented E04138 BV 413 ACTIVE

Room 8467 is rented E84675 BV 8467 ACTIVE

Room 1 is rented E00011 BV 1 ACTIVE

Room 1621 is not rented V16210 BV 1621 INACTIVE

When PROT1 is selected, options D-H change to the following values. These
values cannot be edited.

Option Value
D. Response code ACK

E. Parity N

F. Data bits 8

G. Stop bits 1

H. Checksum byte included Y

Protocol Two
This type of data transmission omits checksum data from the end of messages.

• 7 data bits
• No parity
• 1 stop bit
The message format is Exxxx or Vxxxx, where E = rented and V = vacant (same
as Protocol One but the checksum is omitted).

Character Meaning
1 E for check in, V for check out

2 Room number, thousands digit

3 Room number, hundreds digit

4 Room number, tens digit

5 Room number, ones digit

For example:

Meaning ASCII message BCM-HOTEL result

Room 413 is rented E0413 BV 413 ACTIVE

Room 1621 is not rented V1621 BV 1621 INACTIVE

72 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-HOTEL module

When PROT2 is selected, options D-H change to the following values. These
values cannot be edited.

Option Value
D. Response code ACK

E. Parity N

F. Data bits 7

G. Stop bits 1

H. Checksum byte included N

Custom
When CUSTOM is selected, options D-H change to the following values:

Option Value
D. Response code ACK or W

E. Parity NONE, ODD or EVEN

F. Data bits 7 or 8

G. Stop bits 1 or 2

H. Checksum byte included Y or N

Hotel computer acknowledgement and response

The BCM-HOTEL returns an ASCII ACK if a received message is valid. It
returns an ASCII NAK message if it received an invalid checksum. The
BCM-HOTEL will not respond to garbled messages.

Note Normally EIA-232 is used. Disconnect the TX wire if you do not want to
receive ACK messages.

The BCM-HOTEL ignores other characters sent between messages, such as

carriage lines and line feeds. Use the characters “E” or “V” to resynchronize the
message process.

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up
automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 35 Programming features
Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle

time is typically 1 second but may be longer for large
DDC files.

Branch points 2048 branch points (0-2047).

AVs and BVs 10,000 BVs and 10 AVs. BVs support the priority-array.

Trendlogs Supports 320 trendlog objects.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 73

Installation and Operations Guide | BACtalk Control Modules

Technical data

Ta ble 36 BCM-HOTEL hardware capabilities

Hotel reservation and Supports connection to a hotel information system over
check-in support EIA-232, EIA-485, or EIA-422. Uses hotel Protocol 1 or
Protocol 2 to designate if a room is rented or vacant (max.
room numbers = 10,000).

Power Provided through ribbon cable connection to BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to

back up DDC, automation features, and software objects to
flash memory.

Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.

Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.

32-bit, high-integration Motorola CPU.

Real-time clock Onboard real-time clock supports trendlogs and timed DDC
functions.

BACnet Ethernet Ethernet connection to 10Base-T or 100Base-TX networks

through its ribbon cable connection to a BCM-ETH.
BACnet Internet Protocol IP support for interoperability on wide area networks
(BACnet/IP) (WANs) and campus area networks (CANs).

Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.

(122mm) D.

Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.

BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy

Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Configuration settings unique to this module

Before you can set configuration settings, you must connect to the BCM-
HOTEL using HyperTerminal. See “Connecting to the BCM with
HyperTerminal” on page 22 for more information.

For BCM-HOTEL modules, hotel protocol settings are accessed through item D,
Configure Hotel Protocol, on the BCM-HOTEL Configuration Utility Change
Configuration screen.

74 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-HOTEL module

Note There are certain configuration settings required for all modules. See
“Configuring settings that apply to most modules” on page 26 for more
information.

Figure 19 BCM-HOTEL Configure Hotel Protocol screen

Item Value Remarks

A. Physical Port EIA- (232, 485, 422) Select the physical port on the BCM-HOTEL
on which communications with the hotel
information will be attempted. The setting is
indicated by an LED on the BCM-HOTEL
faceplate.

B. Protocol PROT1, PROT2 or Select one of two protocol options: Protocol

CUSTOM 1 or Protocol 2. All messages are in ASCII.

C. Baud 300, 1200, 4800, or Select the communication speed for the
9600 connection. Typically, 9600 is used.
Note Set this parameter to match the baud
rate on the hotel side.

D. Response ACK
code

E. Parity N

F. Data bits 8,

G. Stop bits 1,

H. Checksum byte Y, N
included:

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 75

Installation and Operations Guide | BACtalk Control Modules

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM-HOTEL provide important information about
connection to networks and operation.
Ta ble 37 BCM-HOTEL LEDs

Function LED label Description

Port 485 ON = Port is currently being used for hotel
protocol.

422 ON = Port is currently being used for hotel

protocol.

232 ON = Port is currently being used for hotel

protocol.

Status DTR ON = Module is ready to transmit.

OFF = Module is not ready to transmit.

DSR ON = Normal operation

OFF = Not operating normally.

RTS ON = Module is allowed to send data.

OFF = Module must stop sending data.
This LED normally remains on, but may blink off
during reception of large blocks of data.

CTS ON = Module is ready to send.

TX ON or flashing = Outgoing hotel data.

RX ON or flashing = Incoming hotel data.

Diagnostics SYS ON = System boot code (loader) is valid and

running.
Momentary OFF = ROC is updating system boot
code.
OFF = Loader in flash memory is not valid.
Factory service is required.

ROC ON = Real-time operating code (ROC) loaded

and running.
OFF = ROC not running.

DDC FLASHING = DDC loaded and operational (LED

changes state with each DDC cycle).
OFF = DDC not loaded or not executing.

BAT ON = Unit is operating from battery power.

OFF = Unit is operating from 24 VAC power.

NAT Firewall Limitation

Under certain scenarios, BCM-HOTEL will not communicate across a NAT
firewall. In a job with two arrays that communicate using IP only, with one array
behind a NAT firewall and the other array outside the NAT firewall, the
BCM-HOTEL outside the firewall will not communicate with modules behind
the firewall.

76 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

BCM-FPCS module
This section describes details specific to the BCM-FPCS module. See other
sections in this manual for similar details about other available modules.

The BCM-FPCS is an Alerton gateway device that enables data sharing between
an Alerton BACtalk system and Siemens® floor level network (FLN) devices on
a P1 protocol network. The BCM-FPCS reads data from up to 98 devices on a P1
network protocol trunk and makes the data available to the BACnet network as
BACnet objects and properties. The BCM-FPCS enables your BACnet system to
read and write P1 point data, as well as read P1 network alarms.

Connect devices using a simple 18 AWG shielded, twisted-pair bus.

Note Like Gen4 VLCs, the BCM-FPCS communicates using the RS-485
signaling standard so see “MS/TP” on page 16.

The BCM-FPCS connects to adjacent BCM modules using a keyed ribbon cable.
The ribbon cable provides power and connectivity to all modules and the
BCM-FPCS. The BCM-FPCS requires at minimum a BCM-PWS with a 24 Volts
power connection and a BCM-ETH to be installed.

The Alerton BCM-FPCS is a high-performance global controller. Use the

BCM-FPCS to:

• Serve as a gateway device between Siemens® P1 protocol network

devices and Alerton’s Envision for BACtalk BACnet system.
• Serve as a BACnet broadcast management device (BBMD) on a
BACnet/IP wide area network (WAN).
• Host automation features such as schedules, trendlogs, alarms, optimum
start, zones, demand limiting, and tenant activity.
• Run DDC sequences for connected devices.

Note See the BCM-FPCS version history for a complete list of changes and
enhancements made with each new release of the BCM-FPCS ROC. View the
file from the ROC downloads page on the ASN.

Siemens® is a registered trademark of Siemens AG.

Software and programming support

For detailed information about programming DDC and referencing system data
points in a BACnet environment, see the Programmer’s Guide and Reference for
BACtalk Systems (LTBT-TM-PRGRMR). For information about setting up

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 77

Installation and Operations Guide | BACtalk Control Modules

automation features, see the operator’s manual for your BACtalk operator
workstation software.
Ta ble 38 Programming features
Programming interface Global/Building controller DDC (VisualLogic).

DDC 32 MB SDRAM for DDC program execution. DDC cycle

time is typically 1 second but may be longer for large
DDC files.

Branch points 2048 branch points (0-2047).

AVs and BVs 1000 AVs and 1000 BVs. BVs support the priority-array.

Schedules Supports 96 schedules and 96 calendar objects.

Alarms Supports 160 alarms. Supports a BCM-MDM for alarm

dialout.

Trendlogs Supports 160 trendlog objects.1

Zones Supports 32 BACtalk zone objects.

Tenant activity logs Supports 32 tenant activity logs.

Demand limiting Supports two demand limiter objects, each with 100
loads defined.

1
Virtual points in the BCM-FPCS are treated like external points, therefore they
have a lower maximum trendlog sampling rate than internal points.

Technical Data

Ta ble 39 BCM-FPCS hardware capabilities

Controller support on 98 controllers max. supported on one Protocol 1 (P1) trunk
P1 trunk (shielded, twisted-pair bus). A Siemens® controller has 3
trunks and the BCM-FPCS has one trunk. Replace a
Siemens® controller that has 3 trunks with 3 BCM-FPCS
controllers. The BCM-FPCS detects the 4800 P1 trunk
baud rate.
Power Provided through ribbon cable connection to BCM-PWS.

NiCad battery 7.2V 700mA-h provided by BCM-PWS. Provides power to

back up DDC, automation features, and software objects to
flash memory.

Super capacitor Powers the real-time clock when AC power is not present.
Standby life is 20 days.
NOTE: The super capacitor is not user serviceable and
does not require replacement.

Memory and CPU 8 MB Flash RAM. 32 MB SDRAM for program execution.

32-bit, high-integration Motorola CPU.

Real-time clock Onboard real-time clock supports schedule operations,

trendlogs, and timed DDC functions.

BACnet Ethernet Ethernet connection to 10Base-T or 100Base-TX networks

through a ribbon cable connection to a BCM-ETH.

78 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

Ta ble 39 BCM-FPCS hardware capabilities (Continued)

BACnet Internet Protocol IP support for interoperability on wide area networks
(BACnet/IP) (WANs) and campus area networks (CANs). Functions as
a BACnet broadcast management device (BBMD) in
accordance with Annex J BACnet/IP.
NOTE: Can only act as a BBMD if a BCM-ETH is present.

Dimensions 6.48 in. (165mm) H x 1.50 in. (38mm) W x 4.82 in.

(122mm) D.

Environmental 32-131 deg. F (0-55 deg. C). 0-95% RH, non condensing.

BACnet conformance Pending.

Ratings Listed Underwriters Laboratories for Open Energy
Management Equipment (PAZX) under the UL Standard
for Safety 916.
EMC Directive 89/336/EEC (European CE Mark).
FCC Part 15, Subpart J, Class A.

Integrating P1 protocol network devices with BACtalk

The BCM-FPCS gateway serves as the global controller for connected Siemens®
field level controllers. It enables Envision for BACtalk to communicate to P1
trunk field equipment. Simply disconnect a P1 trunk from its P1 controller and
connect it to the BCM-FPCS. Powering up and configuring the BCM-FPCS
initiates the auto-detection operation that enables BACtalk to see the connected
P1 devices as BACnet devices. To successfully integrate P1 controllers with a
BACtalk system:

1. Uninstall Siemens® P1 controllers (SCU, RCU, MEC, and UC).

2. Install one Alerton BCM-FPCS gateway for each P1 trunk.

3. Power up and configure each BCM-FPCS for its corresponding P1

virtual network and for its connection to the BACnet network.using a
terminal emulation program such as HyperTerminal. The BCM-FPCS’s
auto-discovery cycle will scan the network and automatically discover
each device on its connected P1 trunk and create BACnet device
addresses, standard device properties, and all points under the device,
according to the Application Number running in the P1 device.

Configuration settings unique to this module

To set device configuration settings, connect to the DB-9 connector under the
front cover of the BCM-FPCS and the serial port on your computer using a null
modem cable and a terminal emulation program such as HyperTerminal. See
“Connecting to the BCM with HyperTerminal” on page 22 for instructions.

For BCM-FPCS modules, P1 network settings are accessed through item E on

the Change Configuration screen. P1 diagnostics are accessed through item J.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 79

Installation and Operations Guide | BACtalk Control Modules

Note There are certain configuration settings required for all modules. See
“Configuring settings that apply to most modules” on page 26 for more
information.

Figure 20 The Change Configuration screen in the BCM-FPCS Configuration

Utility

Use the Change Configuration screen to change the device instance of the
BCM-FPCS. The device instance must be unique to the BACnet system.

Figure 21 Type E on the Change Configuration screen and press Enter to

display the Configure P1 Virtual Network screen.

Use the Configure P1 Virtual Network screen to change the base virtual device
instance of the BCM-FPCS. (This number gets displayed on the bottom of the
main menu when you first log on.) The base virtual device instance must be
unique to the BACnet system and it can not be the same as the BCM-FPCS
device instance. The virtual device instance is the base of the BACnet device

80 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

numbers generated during auto-discovery. For example, a Base Virtual Device

Number of 1000 means the BCM-FPCS can map device instances 1000-1098.
Valid P1 device range is 0-98. The BACnet number is generated by adding the
actual P1 device address (set by either the DIP switches or through software) to
the Base Device Number.

Figure 22 The Configure PTP network and Modem screen in the BCM-FPCS
Configuration Utility. The virtual network is shared by P1 and PTP.

Use the P1 Diagnostics Menu to check the status of the BCM-FPCS and its
connected devices.

Figure 23 The P1 Diagnostics Menu in the BCM-FPCS Configuration Utility.

Type S and press Enter to see a list of devices that have been discovered, their
Application Number, and if they are online.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 81

Installation and Operations Guide | BACtalk Control Modules

Type R and press Enter to remove a P1 device from the BCM-FPCS. If you
renumber P1 devices, split a loaded P1 trunk in two, or do anything else that
physically removes a P1 device from the bus, the BCM-FPCS will continue
looking for the device once every scan. For improved performance, use the
Remove feature to purge off-line device numbers that won’t be replaced.

Note For a device offline for maintenance, do not use the Remove feature or
you will lose any customization you’ve done to that profile.

The Remove feature will remove any defined device, whether offline or online.
If an online device is removed, all the writable device properties (object name,
location, description) and all points of the virtual device will be deleted. Since
the device is still connected, it will be re-discovered by the background scan but
the device properties and point properties will be the application defaults.

Note It’s good practice to back up and save any changes you make to device
profiles as you work so you’ll have the changes later if a backup is required.

Type I and press Enter to start scanning for P1 trunks and automatically detect
and map new P1 device data as BACnet objects and properties. Note that Auto-
discovery is automatically started when the BCM-FPCS is powered up and it
does not need to be repeated unless you are experiencing problems or have done
some work on devices connected to the P1 trunk.

When a new device is detected, the BCM-FPCS gets the Hardware Type and
Application Number from the P1 device and creates an appropriate database of
points for that application. The Auto-discovery operation may take up to 2
minutes to complete if many new devices are discovered.

Type P and press Enter to see the current percentage complete of the Auto-
discovery process.

Figure 24 Scanning status is displayed at the bottom of the P1 Diagnostics

Menu

Type D and press Enter to see the display modes for the P1 trunk. Of all the three
diagnostic modes (C, D, and V) item D displays data in the simplest terms.

82 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

Note You should not leave the BCM-FPCS in any diagnostic display mode for
long periods of time or the scan time will be adversely affected.

Display Modes are intended to aid during troubleshooting or when contacting

technical support.

Figure 25 Display mode D shows a trace of communications between the

BCM-FPCS and all the devices on the P1 trunk.

The display mode tells you that devices are communicating as they are scanned,
polled, and data points are automatically mapped. Items V and C are
increasingly more technical forms of data. V is a verbose form of D that shows
actual communication packets. C shows only commands received over BACnet
and issued to the P1 network. Type Q and then press Enter to stop the trace
display and restore the P1 Diagnostics Menu screen.

Online and offline processing

The BCM-FPCS gateway is constantly polling and scanning devices on the P1
trunk. A P1 device will react differently to the system when it is and it is not
online.

Online
If the device is online, the BCM-FPCS reads its data and shares it with the
BACtalk system. As the BCM-FPCS receives change-of-state (COS), change-
of-value (COV) packets or new point data, all points return current data.

Offline
If a device fails to respond for four consecutive commands, it goes offline: the
BCM-FPCS places it on an abbreviated poll cycle and flags all of the device’s
points as unreliable until communications are re-established. The BCM-FPCS
scans the unresponsive device once per scan cycle to see if it is communicating.

If a P1 device goes offline, the Aler-Dev-Comm-Fail object that is setup, enabled

and hosted in the BCM-FPCS currently will not detect or report the
communication failure.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 83

Installation and Operations Guide | BACtalk Control Modules

Also, a trendlog hosted in the BCM-FPCS, on a point in the virtual P1 device,

will continue to log the last present value received from the virtual device rather
than logging a fault.

Mapping P1 network data to BACnet AVs and BVs

The BCM-FPCS creates a virtual BACnet device for each P1 device found on
the network. P1 devices have up to 99 data points, depending on the application
present in the device. Access data for P1 device data point #nn by assigning a
text string to AV #nn or BV #nn of the virtual BACnet device associated with the
P1 device. The text string specifies whether the P1 device data point that is
mapped to it is an AI, AO, BI, or BO. The text string also specifies scaling
factors to use for analog points, whether or not the point is writeable, etc. The
BCM-FPCS creates the appropriate mappings automatically if it detects a P1
device with a know application.

AO and AI points in a P1device map to AV points in the BCM-FPCS. BO and BI

points in a P1 controller are BV points. Some AO and BO points are writable,
but many P1 AO and BO points can only be set by the system. These internally
written points are used for specific operations like configuration, test and
balance.

Day and Night modes

Alerton data points reflect Day mode as Active and Night Mode as Inactive.
Several P1 device data points are opposite and reflect Day mode as Inactive and
Night mode as Active (BV-21 for Night Override status and BV-29 for
Occupied/Unoccupied Control). An invert option on all day/night or
occupied/unoccupied digital points allows you to specify whether or not the
BCM-FPCS should invert P1 data when returning Day and Night mode values in
Envision for BACtalk.

Auto-discovery and application templates

The BCM-FPCS will perform an auto-discovery operation on startup. During
auto-discovery each P1 network address is polled. When a P1 device is detected
on the network, it is queried for the application number running in the P1 device.
The application number is used to create default AV and BV mappings for that
device by indexing a template file that contains default mappings for many
standard P1 applications. The gateway-strings for the mapped points are
automatically loaded, and a text description of the functionality of the mapped
point is placed in the description property of the mapped AV or BV. In many
cases the default mappings will be sufficient and configuration is complete. The
application number always auto-maps to AV-2. The application number
identifies the application running in the P1 device. These P1 device points are
then mapped as BCM-FPCS points on Alerton standard templates.

You may customize mappings for an application after auto-discovery by deleting

mappings for data points you do not want the user to access, by adding or
removing write permissions, or by adding mappings to any relevant data points
that are not included on the default template for the given application.

If the auto-discovery operation runs out of memory while creating points under a
new device, all points created for that device so far will be deleted. The device
name changes to “Failed to map device #nnnn,” where #nnnn is the application

84 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

number, and the description of the device location changes to “Failure due to
lack of memory.”

Unknown applications
The BCM-FPCS can identify many standard applications, but it is possible for a
P1 device to contain a custom application not found in the BCM-FPCS database
of known applications. The BCM-FPCS will default to an auto-mapping
operation that maps AV-2 through AV-99 to AI-2 through AI-99 on a P1 device
with an unknown application. You may alter these mappings as required using
the point list for the given application. The description properties of AV-3
through AV-99 are loaded with “UNUSED AV #nn” by this default mapping.

Customizing P1 device mappings

You may change the description of any AV or BV without affecting the operation
of the data mapping. The description property is used only to remind you of the
functionality of the given, mapped data point.

Note Only set up a gateway-string for points you want to map. Mapping
multiple points may generate excess traffic and slow down system performance.

Drop a data point from the mapping by deleting the gateway-string associated
with that point. After the gateway-string is deleted, the P1 device will no longer
be polled for that data point.

Add a data point to the mapping by writing a mapping into the AV or BV

gateway-string corresponding to the P1 data point number. Only one AV or BV
object can be mapped to a given P1 data point. If you assign a mapping using the
gateway-string of BV #nn, the gateway string for AV #nn will be automatically
deleted, and vice versa.

Change mapping properties by modifying a point’s Aler-Gateway-Setup

property. The ability to change a mapped AV to a mapped BV is included to ease
the work required in customizing the default points created for an unknown
application. If you change an AV’s gateway string to map to a P1 network BV or
BO object, the mapping will be inserted into the gateway string for the BV with
the same instance as the original AV and the original AV gateway string will be
deleted.

Saving and loading P1 device mappings

Use BACtalk’s Device Manager to save your custom AV and BV mappings by
doing a point data save for the corresponding virtual device. Normally the
BCM-FPCS stores a copy of the mappings in non-volatile memory. The
mappings can be downloaded by Device Manager in the unlikely event of a
BCM-FPCS loss of non-volatile memory. You may also use Device Manager to
propagate a custom mapping to other P1 devices using the three application
commands listed below.

Application commands
There are four application commands that will help you customize application
mappings: LOAD APP, #nnnn, REDISCOVER, CLEAR MAP, and RELOAD.
These are especially useful for applications that are unknown (not part of BCM-
FPCS known application database). The commands are made by typing the
command as input to the AV-2 gateway-string property. Note that AV-2 is always
mapped to the P1 device application number. The gateway-string for AV-2 is

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 85

Installation and Operations Guide | BACtalk Control Modules

always set automatically and you cannot alter it. The AV-2 gateway string will
revert to its previous contents after the command is issued.

Use the LOAD APP, nnnn command to load the mappings from an application
that BCM-FPCS has in its known application database. This command is useful
for using the loaded application as a customization starting point, since your
custom application may be very near to one of the standard applications. Note
that the application contained in the P1 device does not change when this
command is issued. The command simply sets the mappings of the AVs and BVs
to match the loaded application’s mappings. If you issue this command for an
application number that the BCM-FPCS does not know about, the gateway-
string will be set to “BAD PROFILE: #nnnn.”

Use the REDISCOVER command to force a reload of mappings from the

BCM-FPCS application database. This command may take up to 1.5 minutes to
complete. During that time the gateway-string property will display as
“Rediscovering – wait.” The P1 device will eventually be polled, its application
number queried, and the standard mappings loaded into the AV and BV gateway-
strings for this device.

Use the CLEAR MAP command to clear all mappings except for the
application number mapping (AV-2) from a device. This command should be
issued before you download a custom mapping from Envision for BACtalk,
since the BACtalk download does not erase existing mappings before the
download.

Use the Clear Map command in the gateway setup string of AV-2 to refine your
mapped point list so the system uses just the mapped points you want, rather than
all exposed P1 device points. The BCM-FPCS by default automatically maps all
exposed P1 device points into BACnet data, which may result in far more
mapped points than you need. Clear Map enables you to operate efficiently.

You may also use the Clear Map command as a one-step method for copying a
stored profile from one controller to one or more other controllers. If you’ve
edited the profile by deleting some points and changing some others, and you
want to make all similar controllers exactly the same, copy the PointData.mdb
file from the \Rep\job\Devxxxxx\ folder of the device you customized to the
corresponding folder for all other similar devices. Then do a Clear Map
command in each of the target devices to empty its point list before you Send the
Point Data to it.

Use the RELOAD command if you have deleted or edited a point (AV-3 through
AV-98) and now want to restore its standard configuration from its Alerton
profile. Type RELOAD in the point’s gateway string. Remember that BV’s are
automatically created from the information in an AV’s gateway string, so type
RELOAD in the AV of the same point number to restore a BV.

The Reload feature does not work on legacy devices, such as the Siemens® MPU
and DPU controllers. Entering RELOAD into the gateway string for a point
AV-3 through AV-99of a MPU or DPU at address 0 through 99 causes the point
to load the default unused point configuration: description = “UNUSED_AV_n”
and “AI, ,0,1.0” instead of the standard mapped or unmapped configuration for
that point from the MPU or DPU as expected. In this case, you may manually
edit the gateway string to the profile’s default value, or edit AV-2 to “LOAD
MAP, 1” if it’s a MPU or “LOAD MAP, 2” if it’s a DPU.

86 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

Writing to P1 data points

True analog outputs and true digital outputs have additional BV points that can
be used for auto and manual points. These BVs are created at instances 100+I/
O_Addr and allow true outputs to release to automatic control. Auto mode is a
release command that allows the P1 device to be controlled by internal PID and
control loops. Manual mode allows the controller to accept an override
command to force the output to a certain value.

AVs and BVs mapped to P1 data points are normally read-only, even if the P1
data point type specified was AO or BO. If you want to write to a data point you
have to specify the point is writeable using a flag in the gateway-string property.
Valid values for the flag are “W” (writeable) and “F” (forced).

If the “W” flag is used, the AV or BV present value is written to the P1 device
data point whenever a BACnet write property command is issued for the AV or
BV, or when the DDC internal to the BCM-FPCS makes any writes to the AV or
BV.

If the “F” flag is used, the AOs and BOs that are controlled by the P1 device can
be “forced” to values sent from BACnet. The AVs and BVs mapped to these
points have an F flag in their gateway strings and an additional BV is created at
100+I/O_Addr to allow or disallow the force feature. When the BV at 100+I/
O_Addr is active, the value sent to BACnet is forced. When the BV at 100+I/
O_Addr is inactive, control for the point at I/O_Addr is released back to the local
P1 device.

Status flags
Two BACnet status flags for AVs and BVs on the virtual devices reflect the state
of mappings and communication to the P1 devices.

The “Out-of-Service” flag is set to TRUE for AVs and BVs that are not currently
mapped to P1 device data. Set it to FALSE for AVs and BVs with valid
mappings.

The Reliability flag is set to “RELIABLE” for AVs and BVs that the BCM-
FPCS has obtained valid data for from the mapped P1 device or has sent valid
data to the mapped P1 device. All other AVs and BVs have this flag set to
“UNRELIABLE_OTHER.” When a P1 device doesn’t respond or returns an
error code, the corresponding AV or BV is flagged UNRELIABLE_OTHER
until that AV or BV once again returns valid communication.

Note For MPU and DPU controllers only, after auto-discovery the output
points will normally have status of in-fault and unreliable until you send a
controlling value to them.

Analog points
The text format for changing an analog point to another analog type is POINT
TYPE, FLAG, INTERCEPT, SLOPE.

POINT TYPE AI or AO point types on the P1 trunk. Entering BO or BI causes

the AV gateway string to be erased and a BV gateway string to be created
instead.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 87

Installation and Operations Guide | BACtalk Control Modules

FLAG Blank (input only), W, or F. A comma separator must be used between

flags, even if blank. If “W”ritable, field adjust commands will go to P1 devices.
If “F”orceable, override and release commands will go to P1 devices.

INTERCEPT The offset is the zero level for this point in the P1 device. The
value returned when zero counts are returned from the field; must be a real
number.

SLOPE The scale factor for the point data. The value of each count; must be a
real number.

Example: AO,W,0,0.25
A setpoint (analog output, writeable, starting at 0 in 1/4 degree increments.)

Binary points
The text format for changing a binary point to another binary type is POINT
TYPE, FLAG, ZERO TEXT, ONE TEXT, INVERT FLAG.

POINT TYPE BO or BI point type on the P1 trunk.

FLAG Blank (input only), W, or F. A comma separator must be used between

flags, even if blank. If “W”ritable, field adjust commands will go to P1 devices.
If “F”orceable, override and release commands will to P1 devices.

ZERO TEXT Text that appears when the point is in the zero state.

ONE TEXT Text that appears when the point is in the one state.

Example: BO,F,OFF,DOWN
A true digital output. (Binary output, may be forced--overridden or released.
OFF is displayed in the zero state and DOWN is displayed in the one state.

INVERT FLAG If this flag is included then the status of the P1 BO is inverted
when displayed or commanded in BACnet. See “Day and Night modes” page 84.

Setting change-of-value options for P1 devices

Assign change-of-value (COV) settings to P1 data points and specify the limit
that will trigger the COV when the P1 device is polled. Designate a COV for
every AI point. For example, the temperature COV is typically set to 2 degrees
Fahrenheit and other points, like duct static, may be set to 0.1” WC. All digital
points register when they change state so you don’t have to set them up.

Table 40 below lists common values that come from a P1 device by COV. The
list of what is assigned to COV typically varies with each application so use this
list as a guideline only.

Tab le 40 Common P1 device COV values

Point # Data type

4 Room temp

5 Heat/Cool status

13 Thermostat setpoint knob

88 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-FPCS module

Tab le 4 0 Common P1 device COV values

Point # Data type

15 Auxiliary temperature

19/24 Wall switch push button

21/29 Day/Night modes

35 Air volume flow

48 Damper command

49 Damper position

75 Flow

78 Calculated control temperature

79 Cooling loop calculated output

80 Heating loop calculated output

91 Total volume

93 Calculated flow setpoint

99 Error status

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM provide important information about operation
and connection to networks. Transmit, receive and the RTS light in the Status
area on the front panel indicate when the P1devices are sending and receiving
transmissions.
Ta ble 41 BCM-FPCS LEDs

Function LED label Description

Diagnostics SYS ON (Bootup) = System boot code (loader) is
valid and running.
ON = Normal device poll and scanning cycle.
OFF = Auto-discovery is in progress.

ROC ON = Real-time operating code (ROC) is loaded

but not yet running.
FLASHING = BCM-FPCS is operating normally.
OFF = ROC is not running.
DDC FLASHING = DDC loaded and operational (LED
changes state with each DDC cycle).
OFF = DDC not loaded or not executing.

BAT ON = Unit is operating on battery power.

OFF = Unit is operating from 24 VAC power or
disconnected from power.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 89

Installation and Operations Guide | BACtalk Control Modules

Ta ble 41 BCM-FPCS LEDs

Function LED label Description

COMM STATUS RX FLASHING = Data is being received from field.

TX FLASHING = Data is transmitting to field.

Port 485 ON = BCM-FPCS is using the RS-485 protocol.

This LED should always be ON.

422 ON = BCM-FPCS is using the RS-422 protocol.

This LED should always be OFF.

232 ON = BCM-FPCS is using RS-232 protocol. This

LED should always be OFF.

Using diagnostic AVs for this module

Each virtual device contains 4 AV points (100-103) dedicated to
communications for diagnostics and troubleshooting.

• AV-100: packets since midnight (in thousands of packets)

• AV-101: percent RX (receive) errors since midnight
• AV-102: percent TX (transmit) errors since midnight
• AV-103: background scan time for all points on the device (in seconds)

90 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDM module

BCM-MDM module
This section describes details specific to the BCM-MDM module. See other
sections in this manual for similar details about other available modules.

The BCM-MDM provides dial-out and dial-in capability for a BACnet system.

Configuration settings unique to this module

The BCM-MDM itself does not have any configuration settings. However, you
must connect to the host control module using HyperTerminal to configure your
PTP network settings and modem options if a BCM-MDM is present. See
“Connecting to the BCM with HyperTerminal” on page 22 for instructions.

The host control module is the module directly to the left and connected to the
modem module. PTP network and modem options are on a submenu accessed
through item E on the Change Configuration screen.

Note The words “Modem Not Installed” appear for Item C on the Configure
PTP network and modem screen for all modules other than the host control
module.

Figure 26 PTP network and modem screen in the BCM Configuration Utility

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 91

Installation and Operations Guide | BACtalk Control Modules

Ta ble 42 PTP settings

Field Values Remarks

A. PTP Virtual Network 1-65534 Sets the BACnet network number for
Number this device’s half of the PTP
connection. Each interconnected
BACnet network must have a network
number unique throughout the
internetwork. Selecting a number in
the range 1–65,534 (and not 0) is
highly recommended for flexibility and
future compliance.
This virtual network number must be
unique for all connected BCMs and
BACnet devices. No other network
can have this number on any network
that will interconnect, including the
other half of the PTP connection.

B. PTP password 1-8 alphanumeric A case-sensitive PTP password

characters restricting remote access to the BCM.
Set the password and make a note of
it. When you set up an outbound
connection in the Connection
Manager of Envision for BACtalk, you
need to provide this password. If no
password is entered here, access is
unrestricted.

C. Modem Dial-in Enabled Y|N Appears only if a BCM-MDM is

connected to the current module with
a ribbon cable. Set to Y to enable
inbound connections. Set to N to
disable inbound connections, for
example, if you want this modem to
function for alarm dial out only.

D. Modem Speaker On YES|NO Sets the BCM-MDM’s speaker on or

off.

E. Modem Country of Two letter country Indicates the country where the
Operation code or full country modem is located.
name. For
example, US or
United States.

92 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | BCM-MDM module

Using diagnostic LEDs for this module

Diagnostic LEDs on the BCM provide important information about operation
and connection to networks.
Ta ble 43 BCM-MDM LEDs

Function LED label Description

Status RI ON = there is a ring signal on the phone line. The
modem waits for RI to go inactive before going
off-hook.

CD ON = a carrier is detected on the phone line.

DTR ON = the module is ready to transmit.

OFF = indicates the modem is not ready to
transmit. This LED will be OFF when the Modem
Dial-in Enabled option on the Configure PTP
network and modem screen is set to N. See
Table 42 on page 92 for more information.

DSR ON = normal operation

OFF = indicates that the module is to disregard
all signals (except RI) appearing on the
interchange circuits. It does not indicate an
actual link with any remote data equipment.

RTS ON = the modem is allowed to send data to the

host control module and when off the modem
must stop sending data. This LED normally
remains on, but may blink off during reception of
large blocks of data.

CTS ON = the modem is ready to send.

TX ON = data is being transmitted by the modem.

RX ON = data is being received by the modem.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 93

Installation and Operations Guide | BACtalk Control Modules

Appendix A: HyperTerminal settings

The following settings apply to HyperTerminal and most other terminal
emulation programs. Exceptions to these guidelines are listed in the sections for
specific modules.
Ta ble 44 HyperTerminal settings for connecting to the BCM

Property Setting
Bits per second BCM-WEB:115,200
All Other BCMs: 57,600

Data bits 8

Parity None

Stop bits 1

Flow control None

For HyperTerminal, default advanced settings should be appropriate. However,

if advanced settings are changed, use the following defaults as a reference.

Note To view advanced settings, choose Properties from the HyperTerminal

File menu.

94 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix B: BACnet object and property reference

Appendix B: BACnet object and property reference

Use Table 45 for a general overview of the BACnet objects available in the BCM modules. Use
the tables that follow for details about the properties of each object listed. For properties, a check
in the W column indicates a property is writable. Items in bold always appear as shown.
Ta ble 45 BCM module objects

Object (instance range) Remarks

AV (0–999) General use AVs. Note: BCM-HOTEL has only 10 AVs.

AV (1000-10279) Diagnostic AVs - refer to Appendix D.

BV (0-999) General use BVs. These BVs support the priority-array property.
Note: The BCM-HOTEL has 10,000 BVs reserved for hotel room numbers.

Calendar Describes a list of calendar dates, special event dates, holiday dates, and date
ranges.

Device Provides general information about a device.

Event Enrollment Defines an event and connects the occurrence of the event to the transmission of
an event notification. Used in BACtalk primarily for alarms.

File (0) Provides information about the ROC file.

File (1024) Provides information about the current DDC file.

File (2048) Provides information about DDC trap file.

Notification Class Stores a list of available recipients for the distribution of event notifications (alarms,
trendlog gathering, and so on.).

Program (0) Stores information about the ROC/controller program.

Program (1024) Stores program status information about the current DDC program.

Schedule Controls designated properties by periodic schedule that may recur during a range
of dates.
Trendlogs Helps troubleshoot problem areas and identify critical operating trends in the
BACnet system.

Zones * Defines a space in a building that is controlled by a BACtalk system. Zones

provide a convenient mechanism to monitor, manage and arbitrate multiple
Envision features, such as, schedules, optimum start, and tenant activity. Optimum
start and tenant activity require a zone to be setup. A zone may represent one floor
of a building, multiple floors, a particular room or area on a floor, a hallway, foyer,
or stairwell.

Demand Limiting* Monitors and controls energy demand and then automatically adjust equipment
operation to limit the demand and reduce costs.

* Alerton proprietary object

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 95

Installation and Operations Guide | BACtalk Control Modules

Properties of AV objects
Ta ble 46 Properties of AV objects
Property W Type Example Remarks

cov-increment 9 Real If the present-value changes by this amount or greater,

a change-of-value notification is sent to subscribed
devices. Not used at present.

description 9 Character string Occupied A description assigned to describe the object’s function.
Setpoint

event-state Enumerated Normal Always Normal

object-identifier BACnet_ Object_ AV 1 This property consists of the object-type property and
Identifier the object instance, which is a numeric code that
identifies the object of interest.

object-name Character string AV 1 Shows AV <instance>.

object-type Enumerated AV
out-of-service Boolean FALSE

present-value 9 Real 76.4 Range is +/−3 x 1038 (six significant digits of resolution).

status-flags Bit string <Bit string> A four-position bit string that indicates the status of the
AV. If a status bit =1, that status is TRUE.

units 9 Enumerated Deg F Indicates the unit of measure, in BACnet engineering

units, for the AV present-value.

Properties of BV objects
Ta ble 47 Properties of BV objects

Property W Type Example Remarks

description ¸ Character string Occupied A description assigned for the object’s function.
Setpoint

event-state Enumerated NORMAL

object-identifier BACnet_ Object_ BV 8413 This property consists of the object-type property and the
Identifier object instance, which is a numeric code that identifies
the object of interest.

object-name Character string BV 8413

object-type Enumerated BV Indicates a binary value (BV).

out-of-service Boolean FALSE

present-value ¸ Enumerated INACTIVE Either ACTIVE (ON) or INACTIVE (OFF).

status-flags Bit string In alarm = 0, A four-position bit string that indicates the status of the
fault = 0, object. If a status bit =1, that status is TRUE.
overridden =
0, out of
service = 0

priority-array BACnet <Array of An array of prioritized values (indexes 1-16) controlling

PriorityArray BACnet the present-value, index 1 having the highest priority.
PriorityValue> The value with the highest priority controls the present-
value. Possible values for priority-array indexes are
ACTIVE, INACTIVE, or NULL. A NULL value indicates
no command is issued at that priority-array index.

relinquish-default ¸ Enumerated Inactive Default value to be used for present-value property when
all priority-array indexes are NULL.

96 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix B: BACnet object and property reference

Properties of the device object

Ta ble 48 Properties of the device object

Property W Type Example Remarks

apdu-segment timeout ¸ Unsigned 6000 The time after transmission of a “segment” until the lack
of a reply means it was assumed to be lost (in
milliseconds, 1000 = 1 sec.). Default = 6000.

apdu-timeout ¸ Unsigned 6000 The time after transmission of an APDU until the lack of
a reply means it was assumed to be lost. The APDU
timeout value for this device in milliseconds (1000 = 1
sec.). Default = 6000.
application-software- Character string BCM-ETH Indicates the ROC file version.
version Controller
V1.00
daylight-savings- Boolean FALSE Indicates whether daylight savings is in effect (TRUE) or
status not (FALSE).

description ¸ Character string Second floor Assigned by the user to describe the device’s function.
controller

device-address- List Empty.

binding

firmware-revision Character string BCM-ETH Indicates the BCM boot code version.
Loader
v1.00

local-date ¸ Date Sunday, 09/ Indicates date: day of the week, month/day/year.
24/2003 Writable using Time Sync.

local-time ¸ Time 10:15:56.00 Indicates the time stored in the device. Writable using
am Time Sync.

location ¸ Character string East Wing Indicates the physical location of the device.

max-apdu-length- Unsigned 1476 The maximum message packet size that the device can
accepted handle.
max-info-frames ¸ Unsigned 60 Number of MS/TP messages the device will send per
token hold. Default = 60. Max. = 200.

max-master Unsigned 127 Highest MAC address above this unit's that another
MS/TP master should be set to.

model-name Character string BCM-ETH Assigned by the vendor to indicate the device model.
Controller
number-of-apdu- ¸ Unsigned 3 The number of times a message will be resent after it is
retries assumed to be lost.

object-identifier BACnet_ Object_ Device 200 This property consists of the object-type property and
Identifier the device instance (a numeric code that identifies the
device) of this device.

object-list Array An array whose elements list the object-identifier

properties of all objects the device supports.

object-name Character string Controller Every device must have a unique object name.
200
object-type Enumerated Device

protocol-object-types- Bit string <Bit string> An internally used bit string. Indicates which BACnet
supported object types reside in the device.

protocol-services- Bit string <Bit string> An internally used bit string. Indicates which BACnet
supported services the device can process.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 97

Installation and Operations Guide | BACtalk Control Modules

Ta ble 48 Properties of the device object (Continued)

Property W Type Example Remarks

protocol-version Unsigned 1 Indicates the version of the BACnet protocol supported
by the device.

protocol-revision unsigned 4

segmentation- Enumerated segmented Device is capable of segmenting both transmission and

supported both reply messages.

system-status Enumerated Operational Other possible values besides operational are

operational-read-only, download-required, download-in-
progress, and non-operational.

utc-offset ¸ Signed 0 Coordinated Universal Time offset, in minutes.

vendor-identifier Unsigned 18 A unique code assigned by ASHRAE to the

manufacturer, in this case, Alerton.

vendor-name Character string Alerton Indicates the device manufacturer.

98 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix B: BACnet object and property reference

Properties of event enrollment objects

Tab le 49 Properties of event enrollment objects

Property W Type Example Remarks

acked-transitions bit string To-offnormal Indicates whether the corresponding transitions have
=1, To-fault been acknowledged. 1 indicates that the transition was
= 1, To- acknowledged. Set in the Event Enrollment Editor at the
normal = 1 operator workstation.

description ¸ Character string Event A description assigned to describe the object’s function.
enrollment 0

event-enable ¸ bit string To-offnormal Indicates whether notifications are enabled for these
=1, To-fault event transition types. 1 indicates that the transition will
= 1, To- be reported. Set in the Event Enrollment Editor at the
normal = 1 operator workstation.

event-parameters BACnet Event change_of_

Parameter bitstring
event-state Enumerated NORMAL Indicates the current state of the event.

event-type ¸ Enumerated change_of_ Indicates the type of event algorithm to be used to detect
bitstring events.

notification-class Enumerated 1 Indicates the notification class to be used for event

transitions. Set in the Event Enrollment Editor at the
operator workstation.
notify-type Unsigned alarm Indicates whether the object is set up for alarms or
events.

object-identifier BACnet_ Object_ Event- This property consists of the object type property and the
Identifier enrollment object instance, which is a numeric code that identifies
0 the object of interest.

object-name Character string Alarm Assigned at the operator workstation.

object-property- ¸ Boolean FALSE Indicates whether the file has been saved for backup.
reference

object-type Event-
enrollment

Properties of file objects

Tab le 50 Properties of file objects

Property W Type Example Remarks

archive ¸ Boolean FALSE Indicates whether the file has been saved for backup.

description ¸ Character string BCM-ETH A description assigned to describe the object’s function.
ROC File

file-access-method Enumerated stream

access
file-size Unsigned 983040 The size of the file, in bytes.

file-type Character string BIN Also DDC or TRAP.

modification-date Time 4/29/2003 The date and time the file was last modified.
10:22:20:00a

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 99

Installation and Operations Guide | BACtalk Control Modules

Ta ble 50 Properties of file objects (Continued)

Property W Type Example Remarks

object-identifier BACnet_ Object_ file 0 This property consists of the object-type property and
Identifier the object instance, which is a numeric code that
identifies the object of interest.

object-name Character string File 0

object-type Enumerated file

read-only Boolean TRUE Indicates whether the file can be written to by BACnet
services.

100 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix B: BACnet object and property reference

Properties of notification class objects

Ta ble 51 Properties of notification class objects

Property W Type Example Remarks

ack-required ¸ Bit string To offnormal Indicates whether an acknowledgment is required for
= 1, to fault = event transitions. A 1 indicates that acknowledgment is
1, to normal required. Set up at the operator workstation.
=1
description ¸ Character string Alarm An editable description of the object’s location or
Handler function.

notification-class Unsigned 1 Echoes the object instance.

object-identifier BACnet_ Object_ Notification This property consists of the object-type property and the
Identifier -class 1 object instance, which is a numeric code that identifies
the object of interest.

object-name ¸ Character string Alarm

Handler 1

object-type Enumerated Notification-

class

recipient-list ¸ List <List of Lists the devices that will receive notification when the
BACnet notification class transitions. Set up at the operator
Destination> workstation.

priority ¸ Array of Unsigned Indicates the priority to be used for event notifications for
TO-OFFNORMAL, TO-FAULT, and TO-NORMAL
events, respectively.

Properties of program objects

Ta ble 52 Properties of program objects

Property W Type Example Remarks

description ¸ Character string Occupied A description assigned to describe the object’s function.
Setpoint

description-of-halt Character string Program

halted by
request

instance-of Character string alerton hq Header information for the file. Program 0 does not
alerBCM- support this property.
ETH
0*00000000*

object-identifier BACnet_ Object_ program This property consists of the object-type property and
Identifier 1024 the object instance, which is a numeric code that
identifies the object of interest.

object-name Character string Program

Object 1024

object-type Enumerated Program

out-of-service Boolean FALSE

program-change ¸ Enumerated READY Used to command the program state. A program can be
stopped using the HALT command, for example, and
started again with RESTART.

program-location Character string DDC Set when program stops.

Sequence =
60

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 101

Installation and Operations Guide | BACtalk Control Modules

Ta ble 52 Properties of program objects (Continued)

Property W Type Example Remarks

program-state Enumerated RUNNING Possible states include RUNNING, IDLE, HALTED.

reason-for-halt Enumerated PROGRAM

reliability Enumerated NO FAULT

DETECTED

status-flags Bit string In alarm = 0, A four-position bit string that indicates the status of the
fault = 0, object. If a status bit =1, that status is TRUE.
overridden =
0, out of
service = 0

Properties of schedule objects

Ta ble 53 Properties of schedule objects

Property W Type Example Remarks

description ¸ Character string Weekend A description assigned to describe the object’s function.
Gym

effective-period ¸ Sequence <BACnet Assigned in schedule setup at operator workstation.

DateRange>

exception-schedule ¸ Sequence <Array of Assigned in schedule setup at operator workstation.

BACnet
Special
Event>

list-of-object-property- ¸ List <List of The list of objects that this schedule commands.
references BACnet
Object
Property
Reference>

object-identifier BACnet_ Object_ schedule 0 This property consists of the object-type property and
Identifier the object instance, which is a numeric code that
identifies the object of interest.

object-name ¸ Character string schedule Assigned in schedule setup at operator workstation.

000

object-type Enumerated schedule

present-value ACTIVE Indicates the value most recently written to a referenced

object property. May be analog, binary, or other,
depending on the controlled property. Tracks schedule.

priority-for-writing ¸ Unsigned 16 Assigned in schedule setup at operator workstation.

weekly-schedule ¸ Sequence <Array of Assigned in schedule setup at operator workstation.

BACnetDaily
Schedule>

102 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix C: Virtual device object and property reference

Appendix C: Virtual device object and property reference

In addition to the BACnet objects and properties described in “Appendix B: BACnet object and
property reference” on page 95, the BCM-TUX supports the following virtual objects and
properties.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 103

Installation and Operations Guide | BACtalk Control Modules

Properties of virtual device objects

Ta ble 54 Properties of virtual device objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID <user defined base + index>

Object-Name Yes No Text 25 Device 'x'

Object-Type Yes No Enum {device}

System-Status Yes No Enum {operational}

Vendor-Name Yes No Text Alerton

Vendor-Identifier Yes No Unsigned 18

Model-Name Yes No Text <TUX model if known by FID>

Firmware-Revision Yes No Text

Application-Software-Version Yes No Text

Location Yes Yes Text 25 <empty>

Description Yes Yes Text 25 <empty>

Protocol-Version Yes No Unsigned 1

Protocol-Revision Yes No Unsigned defined

internally
Protocol-Object-Types- Yes No <defined internally>
Supported

Object-List Yes No <defined internally>

Max-APDU-Length-Accepted Yes No Unsigned 1476

Segmentation-Supported Yes No Enum {segmented both}

VT-Classes-Supported Not Not

Supported Supported

Active-VT-Sessions Not Not

Supported Supported
Local-Time Not Not
Supported Supported

Local-Date Not Not

Supported Supported

UTC-Offset Not Not

Supported Supported

Daylight-Savings-Status Not Not

Supported Supported

APDU-Segment-Timeout Yes No 6000

APDU-Timeout Yes No 0

Number-of-APDU-Retries Yes No 0

List-of-Session-Keys Not Not

Supported Supported

104 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix C: Virtual device object and property reference

Ta ble 54 Properties of virtual device objects (Continued)

Property Readable Writable Data Type Length Default on Hardware Reset

Time-Syncronization-Recipients Not Not
Supported Supported

Max-Master Not Not

Supported Supported

Max-Info-Frames Not Not

Supported Supported

Alerton-Gateway Not Not

Supported Supported

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 105

Installation and Operations Guide | BACtalk Control Modules

Properties of virtual AI objects

Ta ble 55 Properties of virtual AI objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID AI 'x'

Object-Name Yes No Text 25 AI 'x'

Object-Type Yes No Enum AI

Present-Value Yes Yes Real

Description Yes Yes Text 25 <empty>

Device-Type Not Not

Supported Supported

Status-Flags Fault Flag No BitString

Only

Event-State Yes No Enum {Normal}

Reliability Not Not
Supported Supported

Out-of-Service Always No Boolean

FALSE

Update-Interval Not Not

Supported Supported

Units No Enum Based on TUX type and point.

Min-Pres-Value Not Not
Supported Supported

Max-Pres-Value Not Not

Supported Supported

Resolution Not Not

Supported Supported
COV-Increment Not Not
Supported Supported

Time-Delay Not Not

Supported Supported

Notification-Class Not Not

Supported Supported
High-Limit Not Not
Supported Supported

Low-Limit Not Not

Supported Supported

Deadband Not Not

Supported Supported

Limit-Enable Not Not

Supported Supported

Event-Enable Not Not

Supported Supported

Acked-Transitions Not Not

Supported Supported

Notify-Type Not Not

Supported Supported

Alerton-Gateway Yes Yes 20

106 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix C: Virtual device object and property reference

Properties of virtual AO objects

Ta ble 56 Properties of virtual AO objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID AO ‘x’

Object-Name Yes No Text 25 AO ‘x’

Object-Type Yes No Enum AO

Present-Value Yes Yes Real

Description Yes Yes Text 25 <empty>

Device-Type Not Not

Supported Supported

Status-Flags Fault Flag No BitString

Only

Event-State Yes No Enum {Normal}

Reliability Not Not
Supported Supported

Out-of-Service Always No Boolean

FALSE

Units No Enum Based on TUX type and point.

Min-Pres-Value Not Not

Supported Supported
Max-Pres-Value Not Not
Supported Supported

Resolution Not Not

Supported Supported

Priority-Array Yes Yes All NULL

Relinquish-Default Yes Yes Retrieve value from TUX.

COV-Increment Not Not
Supported Supported

Time-Delay Not Not

Supported Supported

Notification-Class Not Not

Supported Supported

High-Limit Not Not

Supported Supported

Low-Limit Not Not

Supported Supported

Deadband Not Not

Supported Supported

Limit-Enable Not Not

Supported Supported

Event-Enable Not Not

Supported Supported

Acked-Transitions Not Not

Supported Supported

Notify-Type Not Not

Supported Supported

Alerton-Gateway Yes Yes 20

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 107

Installation and Operations Guide | BACtalk Control Modules

Properties of virtual AV objects

Ta ble 57 Properties of virtual AV objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID AV 'x'

Object-Name Yes No Text 25 AV 'x'

Object-Type Yes No Enum {Analog_Value}

Present-Value Yes Depends Real 0

on TUX
type and
point.

Description Yes Yes Text 25 <empty>

Status-Flags Fault Flag No BitString

Only
Event-State Yes No Enum {Normal}

Reliability Not Not

Supported Supported
Out-of-Service Always No Boolean
FALSE

Units Always No Enum

{empty}
Priority-Array Not Not
Supported Supported

Relinquish-Default Not Not

Supported Supported

COV-Increment Not Not

Supported Supported

Time-Delay Not Not

Supported Supported

Notification-Class Not Not

Supported Supported

High-Limit Not Not

Supported Supported

Low-Limit Not Not

Supported Supported

Deadband Not Not

Supported Supported

Limit-Enable Not Not

Supported Supported

Event-Enable Not Not

Supported Supported

Acked-Transitions Not Not

Supported Supported

Notify-Type Not Not

Supported Supported
Alerton-Gateway No No

108 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix C: Virtual device object and property reference

Properties of virtual BI objects

Ta ble 58 Properties of virtual BI objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID BI 'x'

Object-Name Yes No Text 25 BI 'x'

Object-Type Yes No Enum {Binary_Input}

Present-Value Yes Depends BinaryPV

on the
TUX type
and point.

Description Yes Yes Text 25 <empty>

Device-Type Not Not

Supported Supported
Status-Flags Fault Flag No BitString
Only

Event-State Yes No Enum {Normal}

Reliability Not Not

Supported Supported

Out-of-Service Always No Boolean

FALSE

Polarity Always No Enum

{Normal}

Inactive-Text Not Not

Supported Supported

Active-Text Not Not

Supported Supported

Change-of-State-Time Not Not

Supported Supported

Change-of-State-Count Not Not

Supported Supported

Time-of-State-Count-Reset Not Not

Supported Supported
Elapsed-Active-Time Not Not
Supported Supported

Time-of-Active-Time-Reset Not Not

Supported Supported

Time-Delay Not Not

Supported Supported
Notification-Class Not Not
Supported Supported

Alarm-Value Not Not

Supported Supported

Event-Enable Not Not

Supported Supported
Acked-Transitions Not Not
Supported Supported

Notify-Type Not Not

Supported Supported

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 109

Installation and Operations Guide | BACtalk Control Modules

Properties of virtual BO objects

Ta ble 59 Properties of virtual BO objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID BO 'x'

Object-Name Yes No Text 25 BO 'x'

Object-Type Yes No Enum {Binary_Output}

Present-Value Yes Yes BinaryPV

Description Yes Yes Text 25 <empty>

Device-Type Not Not

Supported Supported

Status-Flags Fault Flag No BitString

Only

Event-State Yes No Enum {Normal}

Reliability Not Not
Supported Supported

Out-of-Service Always No Boolean

FALSE

Polarity Always No Enum

{Normal}

Inactive-Text Not Not

Supported Supported

Active-Text Not Not

Supported Supported
Change-of-State-Time Not Not
Supported Supported

Change-of-State-Count Not Not

Supported Supported

Time-of-State-Count-Reset Not Not

Supported Supported

Elapsed-Active-Time Not Not

Supported Supported

Time-of-Active-Time-Reset Not Not

Supported Supported

Minimum-OFF-Time Not Not

Supported Supported
Minimum-ON-Time Not Not
Supported Supported

Priority-Array Yes Yes

Relinquish-Default Yes Yes

Time-Delay Not Not

Supported Supported

Notification-Class Not Not

Supported Supported

110 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix C: Virtual device object and property reference

Ta ble 59 Properties of virtual BO objects (Continued)

Property Readable Writable Data Type Length Default on Hardware Reset

Feedback-Value Not Not
Supported Supported

Event-Enable Not Not

Supported Supported

Acked-Transitions Not Not

Supported Supported

Notify-Type Not Not

Supported Supported

Properties of virtual BV objects

Ta ble 60 Properties of virtual BV objects

Property Readable Writable Data Type Length Default on Hardware Reset

Object-Identifier Yes No Object ID BV 'x'

Object-Name Yes No Text 25 BV 'x'

Object-Type Yes No Enum {Binary_Value}

Present-Value Yes Yes BinaryPV 0

Description Yes Yes Text 25 <empty>

Status-Flags Fault Flag No BitString

Only

Event-State Yes No Enum {Normal}

Reliability Not Not

Supported Supported

Out-of-Service Always No Boolean

FALSE
Inactive-Text Not Not
Supported Supported

Active-Text Not Not

Supported Supported

Change-of-State-Time Not Not

Supported Supported

Change-of-State-Count Not Not

Supported Supported

Time-of-State-Count-Reset Not Not

Supported Supported

Elapsed-Active-Time Not Not

Supported Supported

Time-of-Active-Time-Reset Not Not

Supported Supported

Minimum-OFF-Time Not Not

Supported Supported

Minimum-ON-Time Not Not

Supported Supported

Priority-Array Supported Supported

Relinquish-Default Not Not

Supported Supported

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 111

Installation and Operations Guide | BACtalk Control Modules

Ta ble 60 Properties of virtual BV objects (Continued)

Property Readable Writable Data Type Length Default on Hardware Reset

Time-Delay Not Not
Supported Supported

Notification-Class Not Not

Supported Supported

Alarm_Value Not Not

Supported Supported

Event-Enable Not Not

Supported Supported

Acked-Transitions Not Not

Supported Supported

Notify-Type Not Not

Supported Supported

112 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix D: Diagnostic AVs

Appendix D: Diagnostic AVs

The present-value property of the diagnostic AVs listed are reserved to provide operating
information about the BCM. You can reference these present values on data displays or in DDC
to assist in troubleshooting and fault detection.

The present value property of clearable points can be written with only zero. Any non-zero value
returns a VALUE_OUT_OF_RANGE error. Any attempt to write to a non-clearable point will
result in a WRITE_ACCESS_DENIED error.

Properties not applicable to a particular controller type will return an UNKNOWN_OBJECT

error.
Ta ble 61 Reserved diagnostic AVs

Object ID Meaning Remarks Clearable

AV-10000 Reboot Count YES

AV-10001 Fault Count YES

AV-10002 Last Fault Code YES

AV-10003 Last Fault Location YES

AV-10004

AV-10005

AV-10006
AV-10007

AV-10008

AV-10009

AV-10010 Free Memory NO

AV-10011 Free Object Memory NO

AV-10012 Free Network Memory NO

AV-10013

AV-10014

AV-10015

AV-10016

AV-10017

AV-10018

AV-10019

AV-10020 Ethernet Frames Received YES

AV-10021 Ethernet Frames Transmitted YES

AV-10022 Ethernet Bytes Received YES

AV-10023 Ethernet Bytes Transmitted YES

AV-10024 Ethernet Frames/Sec Received NO

AV-10025 Ethernet Frames/Sec Transmitted NO

AV-10026 Ethernet Bytes/Sec Received NO

AV-10027 Ethernet Bytes/Sec Transmitted NO

AV-10028 Ethernet Dropped Packets YES

AV-10029

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 113

Installation and Operations Guide | BACtalk Control Modules

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10030

AV-10031

AV-10032

AV-10033

AV-10034

AV-10035

AV-10036

AV-10037
AV-10038

AV-10039

AV-10040 IP Frames Received YES

AV-10041 IP Frames Transmitted YES

AV-10042 IP Bytes Received YES

AV-10043 IP Bytes Transmitted YES

AV-10044 IP Frames/Sec Received NO

AV-10045 IP Frames/Sec Transmitted NO

AV-10046 IP Bytes/Sec Received NO

AV-10047 IP Bytes/Sec Transmitted NO

AV-10048 IP Dropped Packets YES

AV-10049 IP Annex-J Dropped Packets YES

AV-10050

AV-10051

AV-10052

AV-10053
AV-10054

AV-10055

AV-10056
AV-10057

AV-10058

AV-10059

AV-10060 MS/TP-A Frames Received YES

AV-10061 MS/TP-A Frames Transmitted YES

AV-10062 MS/TP-A Bytes Received YES

AV-10063 MS/TP-A Bytes Transmitted YES

AV-10064 MS/TP-A Frames/Sec Received NO

AV-10065 MS/TP-A Frames/Sec Transmitted NO

AV-10066 MS/TP-A Bytes/Sec Received NO

AV-10067 MS/TP-A Bytes/Sec Transmitted NO

AV-10068 MS/TP-A Dropped Packets YES

114 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix D: Diagnostic AVs

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10069 MS/TP-A Invalid Packets YES

AV-10070 MS/TP-A Device Census NO

AV-10071 MS/TP-A Fast Reqs NO

AV-10072 MS/TP-A Fast Reqs/Sec NO

AV-10073 MS/TP-A Fast Cycle Time NO

AV-10074

AV-10075

AV-10076
AV-10077

AV-10078

AV-10079

AV-10080 MS/TP-B Frames Received YES

AV-10081 MS/TP-B Frames Transmitted YES

AV-10082 MS/TP-B Bytes Received YES

AV-10083 MS/TP-B Bytes Transmitted YES

AV-10084 MS/TP-B Frames/Sec Received NO

AV-10085 MS/TP-B Frames/Sec Transmitted NO

AV-10086 MS/TP-B Bytes/Sec Received NO

AV-10087 MS/TP-B Bytes/Sec Transmitted NO

AV-10088 MS/TP-B Dropped Packets YES

AV-10089 MS/TP-B Invalid Packets YES

AV-10090 MS/TP-B Device Census NO

AV-10091 MS/TP-B Fast Reqs NO

AV-10092 MS/TP-B Fast Reqs/Sec NO

AV-10093 MS/TP-B Fast Cycle Time NO

AV-10094

AV-10095
AV-10096

AV-10097

AV-10098

AV-10099

AV-10100 MS/TP-C Frames Received YES

AV-10101 MS/TP-C Frames Transmitted YES

AV-10102 MS/TP-C Bytes Received YES

AV-10103 MS/TP-C Bytes Transmitted YES

AV-10104 MS/TP-C Frames/Sec Received NO

AV-10105 MS/TP-C Frames/Sec Transmitted NO

AV-10106 MS/TP-C Bytes/Sec Received NO

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 115

Installation and Operations Guide | BACtalk Control Modules

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10107 MS/TP-C Bytes/Sec Transmitted NO

AV-10108 MS/TP-C Dropped Packets YES

AV-10109 MS/TP-C Invalid Packets YES

AV-10100 MS/TP-C Device Census NO

AV-10111 MS/TP-C Fast Reqs NO

AV-10112 MS/TP-C Fast Reqs/Sec NO

AV-10113 MS/TP-C Fast Cycle Time NO

AV-10014
AV-10015

AV-10015

AV-10016

AV-10017

AV-10018

AV-10019

AV-10120 MS/TP-D Frames Received YES

AV-10121 MS/TP-D Frames Transmitted YES

AV-10122 MS/TP-D Bytes Received YES

AV-10123 MS/TP-D Bytes Transmitted YES

AV-10124 MS/TP-D Frames/Sec Received NO

AV-11225 MS/TP-D Frames/Sec Transmitted NO

AV-10126 MS/TP-D Bytes/Sec Received NO

AV-10127 MS/TP-D Bytes/Sec Transmitted NO

AV-10128 MS/TP-D Dropped Packets YES

AV-10129 MS/TP-D Invalid Packets YES

AV-10130 MS/TP-D Device Census NO

AV-10131 MS/TP-D Fast Reqs NO

AV-10132 MS/TP-D Fast Reqs/Sec NO

AV-10133 MS/TP-D Fast Cycle Time NO

AV-10134

AV-10135

AV-10135

AV-10136

AV-10137
AV-10138

AV-10139

AV-10140 PTP Frames Received YES

AV-10141 PTP Frames Transmitted YES

AV-10142 PTP Bytes Received YES

116 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix D: Diagnostic AVs

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10143 PTP Bytes Transmitted YES

AV-10144 PTP Frames/Sec Received NO

AV-10145 PTP Frames/Sec Transmitted NO

AV-10146 PTP Bytes/Sec Received NO

AV-10147 PTP Bytes/Sec Transmitted NO

AV-10148 PTP Dropped Packets YES

AV-10149 PTP Invalid Packets YES

AV-10150
AV-10151

AV-10152

AV-10153

AV-10154

AV-10155

AV-10156

AV-10157

AV-10158

AV-10159

AV-10160 DDC State. Note: Clearing value with a YES

0 write indicates DDC not supported·

AV-10161 DDC Read/Exec/Write Time (mS) NO

AV-10162 DDC Expanded Size NO

AV-10163 DDC Temp RAM Storage NO

AV-10164 DDC Branch Points Used NO

AV-10165 DDC Temp Priority Arrays NO

AV-10166 DDC Property Access - Total NO

AV-10167 DDC Property Access - Reads NO

AV-10168 DDC Property Access - Writes NO

AV-10169

AV-10170

AV-10171
AV-10172

AV-10173

AV-10174

AV-10175

AV-10176

AV-10177

AV-10178

AV-10179

AV-10180 Alerton Trendlog Object Count NO

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 117

Installation and Operations Guide | BACtalk Control Modules

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10181 Event Enrollment Object Count NO

AV-10182 Schedule Object Count NO

AV-10183 Zone Object Count NO

AV-10184 Demand Limiter Object Count NO

AV-10185 Notification Class Object Count NO

AV-10186 Calendar Object Count NO

AV-10187 COV Object Count NO

AV-10188
AV-10189

AV-10190

AV-10191

AV-10192

AV-10193

AV-10194

AV-10195

AV-10196

AV-10197

AV-10198

AV-10199

AV-10200 Tux 0 Comm Errors YES

AV-10201 Tux 1 Comm Errors YES

AV-10202 Tux 2 Comm Errors YES

AV-10203 Tux 3 Comm Errors YES

AV-10204 Tux 4 Comm Errors YES

AV-10205 Tux 5 Comm Errors YES

AV-10206 Tux 6 Comm Errors YES

AV-10207 Tux 7 Comm Errors YES

AV-10208 Tux 8 Comm Errors YES

AV-10209 Tux 9 Comm Errors YES

AV-10210 Tux 10 Comm Errors YES

AV-10211 Tux 11 Comm Errors YES

AV-10212 Tux 12 Comm Errors YES

AV-10213 Tux 13 Comm Errors YES

AV-10214 Tux 14 Comm Errors YES

AV-10215 Tux 15 Comm Errors YES

AV-10216 Tux 16 Comm Errors YES

AV-10217 Tux 17 Comm Errors YES

AV-10218 Tux 18 Comm Errors YES

AV-10219 Tux 19 Comm Errors YES

118 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix D: Diagnostic AVs

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10221 Tux 20 Comm Errors YES

AV-10222 Tux 21 Comm Errors YES

AV-10223 Tux 22 Comm Errors YES

AV-10223 Tux 23 Comm Errors YES

AV-10224 Tux 24 Comm Errors YES

AV-10225 Tux 25 Comm Errors YES

AV-10226 Tux 26 Comm Errors YES

AV-10227 Tux 27 Comm Errors YES

AV-10228 Tux 28 Comm Errors YES

AV-10229 Tux 29 Comm Errors YES

AV-10230 Tux 30 Comm Errors YES

AV-10231 Tux 31 Comm Errors YES

AV-10232 Tux 32 Comm Errors YES

AV-10233 Tux 33 Comm Errors YES

AV-10234 Tux 34 Comm Errors YES

AV-10235 Tux 35 Comm Errors YES

AV-10236 Tux 36 Comm Errors YES

AV-10237 Tux 37 Comm Errors YES

AV-10238 Tux 38 Comm Errors YES

AV-10239 Tux 39 Comm Errors YES

AV-10240 Tux 40 Comm Errors YES

AV-10241 Tux 41 Comm Errors YES

AV-10242 Tux 42 Comm Errors YES

AV-10243 Tux 43 Comm Errors YES

AV-10244 Tux 44 Comm Errors YES

AV-10245 Tux 45 Comm Errors YES

AV-10246 Tux 46 Comm Errors YES

AV-10247 Tux 47 Comm Errors YES

AV-10248 Tux 48 Comm Errors YES

AV-10249 Tux 49 Comm Errors YES

AV-10250 Tux 50 Comm Errors YES

AV-10251 Tux 51 Comm Errors YES

AV-10252 Tux 52 Comm Errors YES

AV-10253 Tux 53 Comm Errors YES

AV-10254 Tux 54 Comm Errors YES

AV-10255 Tux 55 Comm Errors YES

AV-10256 Tux 56 Comm Errors YES

AV-10257 Tux 57 Comm Errors YES

AV-10258 Tux 58 Comm Errors YES

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 119

Installation and Operations Guide | BACtalk Control Modules

Ta ble 61 Reserved diagnostic AVs (Continued)

Object ID Meaning Remarks Clearable

AV-10259 Tux 59 Comm Errors YES

AV-10260 Tux 60 Comm Errors YES

AV-10261 Tux 61 Comm Errors YES

AV-10262 Tux 62 Comm Errors YES

AV-10263 Tux 63 Comm Errors YES

AV-10264

AV-10265

AV-10266
AV-10267

AV-10268

AV-10269

AV-10270

AV-10271

AV-10272

AV-10273

AV-10274

AV-10275

AV-10276

AV-10277

AV-10278

AV-10279

120 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix E: The alerton-gateway-setup property

Appendix E: The alerton-gateway-setup property

Each analog object in the BCM-TUX has a special property called the alerton-
gateway-setup property. Use this property to set operations you want performed
automatically when the BCM-TUX converts a TUX value (a fixed integer with
an assumed decimal place of one) to the present-value of a BACnet object, or
vice versa. For example, you can set this property so that the BCM-TUX
automatically divides a TUX value by 10 when converting to an AI object
present-value.

You set this property by placing a prompted item on a data display for the
alerton-gateway-setup property of the AI. You then use the prompted item to
assign a string to the property.

I MP O R TA N T The BCM-TUX uses default alerton-gateway-setup property

strings appropriate for most applications so customizing strings is usually not
required. Default strings are listed in “Appendix F: TUX data point to BACnet
object mappings” on page 123.

Customizing the alerton-gateway-setup property enables you to:

• Define an offset to apply when translating analog numeric values

• Convert a TUX input count for a 3K Ohm thermistor into a temperature
in either degrees F or degrees C
• Convert an air velocity value from a TUX-VAV to airflow in either CFM
or LPS
• Set the engineering-units property

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 121

Installation and Operations Guide | BACtalk Control Modules

Syntax for alerton-gateway-setup property

[B<real>][,V|T|D<object ID>][,TF][,TC][,C3K][,H][,M][,S][,P][,D]

• Items in [brackets] are optional

• Type items in boldface exactly as they appear
• A vertical line separates exclusive options
• Items set off in angle brackets and italics are variables

Argument Explanation
B<real> Indicates a divisor to apply when translating the TUX data point to a
BACnet property or vice versa. When reading a TUX data point to a
BACnet property, this is a divisor. When writing to a data point, this
is a multiplier. <real> can be any number with any number of
decimal places, though it is usually in the range 0-12.
If the C3K option is used, setting <real> = 10.0 indicates the TUX is
a programmable or general purpose TUX, setting <real>= 2.55
indicates an application-specific TUX. This accommodates different
conversion methods between TUX types.

V|T|D<object ID> Indicates whether the TUX data point represents a temperature (T),
velocity (V), or box-size diameter (D) measurement. <object ID>
defines an object that indicates units of measure, for example BO9.
This object must be associated with the same Virtual TUX Device
Instance, must be a BO, and must indicate Metric (ON) or English
(OFF). Use no punctuation or spaces in <object ID>. For the D
option, if <object ID> indicates metric measurement, units will be
blank because there is no BACnet setting for cm.

TF Use this argument to indicate the TUX data point represents a

temperature in degrees Fahrenheit. Use instead of T<object ID>
when a BO object is not available to control English/Metric units.
For example, B10.0,TF,C3K converts on input (with a 3K
thermistor) to degrees Fahrenheit.

TC Use this argument to indicate the TUX data point represents a

temperature in degrees Celsius. Use instead of T<object ID> when
a BO object is not available to control English/Metric units. For
example, B10.0,TC,C3K converts on input (with a 3K thermistor) to
degrees Celsius.

C3K Use this to have the BCM-TUX convert TUX input data (in raw
counts) to a temperature using a 3K Ohm lookup table.
H Applies only to time-based values. Sets the engineering-units
property to hours.

M Applies only to time-based values. Sets the engineering-units

property to minutes.

S Applies only to time-based values. Sets the engineering-units

property to seconds.
P Sets the engineering-units property to percent.

D Sets the engineering-units property to inches or cm, for box-size

diameter.

Example
Device Instance 10202, AI-1, alerton-gateway-setup = B10.0, TBO9,C3K
This argument converts AI-1 in the TUX to Device 10202, AI-1, present-value in
degrees celsius or fahrenheit as indicated by BO-9.

122 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Appendix F: TUX data point to BACnet object mappings

Keep the following things in mind when working with TUX data points in the BACtalk system:

• In the IBEX system, TUX AOs and DOs do not have priority arrays. However, when these points
are mapped to AOs and BOs in the BACtalk system, they do have priority arrays. Be careful
when writing to these points from global/building controller DDC.
• When you first connect a BCM-TUX to a BACtalk system, the BACtalk system gathers data
from the connected TUXs and maps data to the present-value property for AIs and BIs and the
relinquish-default property for AOs and BOs.
• If the BCM-TUX loses communications with a TUX, the virtual device on the BACnet network
disappears (appears as NR), the reliability property in diagnostic AV 10200 through AV 10263
changes to unreliable-other, and the fault flag, in the same diagnostic AVs, is set in the status-
flags property.

TX-450 (Rev 2)
Ta ble 62 TX-450 object mappings (Rev 2)

TUX BACnet TUX Data Default Gateway

Description BACnet Units
Point Object Range String
AI-1 AI-1 Physical Point No Units +/- 3276.7 B10.0

AI-2 AI-2 Physical Point No Units +/- 3276.7 B10.0

AI-3 AI-3 Physical Point No Units +/- 3276.7 B10.0

AI-4 AI-4 Physical Point No Units +/- 3276.7 B10.0

DI-1 BI-1 Physical Point

DI-2 BI-2 Physical Point

DI-3 BI-3 Physical Point

DI-4 BI-4 Physical Point

DO-1 BO-1 Physical Point

DO-2 BO-2 Physical Point

DO-3 BO-3 Physical Point

DO-4 BO-4 Physical Point

DO-5 BO-5 Physical Point

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 123

Installation and Operations Guide | BACtalk Control Modules

TX-16160
Ta ble 63 TX-16160 object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-2 AI-2 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-3 AI-3 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-4 AI-4 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-5 AI-5 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-6 AI-6 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-7 AI-7 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-8 AI-8 Physical Point Raw Counts No Units +/- 3276.7 B10.0
AI-9 AI-9 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-10 AI-10 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-11 AI-11 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-12 AI-12 Physical Point Raw Counts No Units +/- 3276.7 B10.0
AI-13 AI-13 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-14 AI-14 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-15 AI-15 Physical Point Raw Counts No Units +/- 3276.7 B10.0

AI-16 AI-16 Physical Point Raw Counts No Units +/- 3276.7 B10.0

DI-1 BI-1 Physical Point Binary Value

DI-2 BI-2 Physical Point Binary Value

DI-3 BI-3 Physical Point Binary Value

DI-4 BI-4 Physical Point Binary Value

DI-5 BI-5 Physical Point Binary Value

DI-6 BI-6 Physical Point Binary Value

DI-7 BI-7 Physical Point Binary Value

DI-8 BI-8 Physical Point Binary Value

DI-9 BI-9 Physical Point Binary Value

DI-10 BI-10 Physical Point Binary Value

DI-11 BI-11 Physical Point Binary Value

DI-12 BI-12 Physical Point Binary Value

DI-13 BI-13 Physical Point Binary Value

DI-14 BI-14 Physical Point Binary Value

DI-15 BI-15 Physical Point Binary Value

DI-16 BI-16 Physical Point Binary Value

DO-1 BO-1 Physical Point Binary Value

DO-2 BO-2 Physical Point Binary Value

DO-3 BO-3 Physical Point Binary Value

124 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 63 TX-16160 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-4 BO-4 Physical Point Binary Value

DO-5 BO-5 Physical Point Binary Value

DO-6 BO-6 Physical Point Binary Value

DO-7 BO-7 Physical Point Binary Value

DO-8 BO-8 Physical Point Binary Value

DO-9 BO-9 Physical Point Binary Value

DO-10 BO-10 Physical Point Binary Value

DO-11 BO-11 Physical Point Binary Value

DO-12 BO-12 Physical Point Binary Value

DO-13 BO-13 Physical Point Binary Value

DO-14 BO-14 Physical Point Binary Value

DO-15 BO-15 Physical Point Binary Value

DO-16 BO-16 Physical Point Binary Value

DO-17 BO-17 Physical Point Binary Value

DO-18 BO-18 Physical Point Binary Value

DO-19 BO-19 Physical Point Binary Value

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 125

Installation and Operations Guide | BACtalk Control Modules

TX-651 PULSE
Ta ble 64 TX-651 PULSE object mappings

TUX BACnet TUX Data Default Gateway

Description BACnet Units
Point object Range String
AI-1 AI-1 Input Raw Counts No Units +/- 3276.7 B10.0

AI-2 AI-2 Input Raw Counts No Units +/- 3276.7 B10.0

AI-3 AI-3 Input Raw Counts No Units +/- 3276.7 B10.0

AI-4 AI-4 Input Raw Counts No Units +/- 3276.7 B10.0

AI-5 AI-5 Input Raw Counts No Units +/- 3276.7 B10.0

AI-6 AI-6 Input Raw Counts No Units +/- 3276.7 B10.0

AI-11 AI-11 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0

AI-12 AI-12 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0
AI-13 AI-13 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0

AI-14 AI-14 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0

AI-15 AI-15 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0

AI-16 AI-16 Pulse width in 1/10 sec No Units +/- 3276.7 B10.0
AI-21 AI-21 Pulse count No Units +/- 3276.7 B10.0

AI-22 AI-22 Pulse count No Units +/- 3276.7 B10.0

AI-23 AI-23 Pulse count No Units +/- 3276.7 B10.0

AI-24 AI-24 Pulse count No Units +/- 3276.7 B10.0

AI-25 AI-25 Pulse count No Units +/- 3276.7 B10.0

AI-26 AI-26 Pulse count No Units +/- 3276.7 B10.0

AO-1 AO-1 Physical Point No Units +/- 3276.7 B10.0

DI-1 BI-1 Physical Point

DI-2 BI-2 Physical Point

DI-3 BI-3 Physical Point

DI-4 BI-4 Physical Point

DI-5 BI-5 Physical Point

DI-6 BI-6 Physical Point

DO-1 BO-1 Physical Point

DO-2 BO-2 Physical Point

DO-3 BO-3 Physical Point

DO-4 BO-4 Physical Point

DO-5 BO-5 Physical Point

DO-11 BO-11 Input 1 configuration

DO-12 BO-12 Input 2 configuration

126 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 64 TX-651 PULSE object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description BACnet Units
Point object Range String
DO-13 BO-13 Input configuration

DO-14 BO-14 Input configuration

DO-15 BO-15 Input configuration

DO-16 BO-16 Input configuration

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 127

Installation and Operations Guide | BACtalk Control Modules

TX-VAV
Ta ble 65 TX-VAV object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Space temperature in Temperaturea Temperaturea +/- 127 B1.0,TBO9
degrees

AI-2 AI-2 Setpoint in degrees Temperaturea Temperaturea +/- 127 B1.0,TBO9

AI-3 AI-3 Discharge temperature Temperaturea Temperaturea +/- 127 B1.0,TBO9

AI-4 AI-4 Air velocity (fpm/12 or Velocityb Velocityb 0 - 255 B12.0,VBO9

lps/12)
AI-5 AI-5 Need more air signal Numeric Percent +/- 127 B1.0,P
(0-99)

AI-6 AI-6 Need colder air signal Numeric Percent +/- 127 B1.0,P
(0-99)

AI-7 AI-7 Current heat signal Numeric Percent 0 - 255 B2.55,P

AI-8 AI-8 Current cool signal Numeric Percent 0 - 255 B2.55,P

AI-9 AI-9 Current heating Temperaturea Temperaturea +/- 127 B1.0,TBO9
setpoint in degrees

AI-10 AI-10 Current cooling Temperaturea Temperaturea +/- 127 B1.0,TBO9

setpoint in degrees

AI-11 AI-11 Box size (diameter in Inches/cm Inches/cm 0 - 255 B1.0,DBO9

inches or cm)

AI-12 AI-12 K Calibration Factor Numeric No Units 0 - 255 B1.0

AO-1 AO-1 Setpoint in degrees Temperaturea Temperaturea +/- 127 B1.0,TBO9

AO-2 AO-2 Maximum setpoint in Temperaturea Temperaturea +/- 127 B1.0,TBO9

degrees
AO-3 AO-3 Minimum setpoint in Temperaturea Temperaturea +/- 127 B1.0,TBO9
degrees

AO-4 AO-4 Heating offset in Temperaturea Temperaturea +/- 127 B1.0,TBO9

degrees

AO-5 AO-5 Cooling offset in Temperaturea Temperaturea +/- 127 B1.0,TBO9

degrees

AO-6 AO-6 Unoccupied heating Temperaturea Temperaturea +/- 127 B1.0,TBO9

setpoint

AO-7 AO-7 Unoccupied cooling Temperaturea Temperaturea +/- 127 B1.0,TBO9

setpoint

AO-8 AO-8 After hours timer Numeric Time (hours) 0 - 255 B10.0,H
(hours)

AO-9 AO-9 After hours limit Numeric Time (hours) 0 - 255 B10.0,H
(hours)

AO-10 AO-10 Demand offset in Numeric No units 0 - 255 B1.0

counts

AO-11 AO-11 OSA temperature Temperaturea Temperaturea +/- 127 B1.0,TBO9

AO-12 AO-12 Heating minimum Numeric Time (sec) 0 - 255 B10.0,S

pulse (seconds)

128 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 65 TX-VAV object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-13 AO-13 Reheat velocity Velocityb Velocityb 0 - 255 B12.0,VBO9

AO-14 AO-14 Maximum velocity Velocityb Velocityb 0 - 255 B12.0,VBO9

AO-15 AO-15 Minimum velocity Velocityb Velocityb 0 - 255 B12.0,VBO9

AO-16 AO-16 Not used

AO-17 AO-17 Not used

AO-18 AO-18 Heat control signal Numeric Percent 0 - 255 B2.55,P

AO-19 AO-19 Cool control signal Numeric Percent 0 - 255 B2.55,P

AO-20 AO-20 VAV damper minimum Numeric Time (sec) 0 - 255 B10.0,S
pulse (seconds)

DI-1 BI-1 ON = Occupied; OFF = Binary Value

Unoccupied

DI-2 BI-2 Heating status Binary Value

DI-3 BI-3 ON = Cooling required Binary Value

DI-4 BI-4 ON = Heating required Binary Value

DI-5 BI-5 HI space temperature Binary Value
alarm

DI-6 BI-6 LOW space Binary Value

temperature alarm

DI-7 BI-7 Not used

DI-8 BI-8 After-hours timer ON Binary Value

DI-9 BI-9 Box fan status Binary Value

DI-10 BI-10 Heating step-one Binary Value

status
DI-11 BI-11 Heating step-two Binary Value
status

DI-12 BI-12 Heating step-three Binary Value

status

DI-13 BI-13 ON = TUX in slave Binary Value

mode; OFF = TUX in
normal mode

DI-14 BI-14 ON = modulating heat; Binary Value

OFF = staged heat

DI-15 BI-15 ON = Software version Binary Value

1.21 and later

DO-1 BO-1 ON = Heating allowed Binary Value

DO-2 BO-2 ON = Cooling allowed Binary Value

DO-3 BO-3 ON = Occupied mode Binary Value

DO-4 BO-4 Control of physical Binary Value
DO-4, if available

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 129

Installation and Operations Guide | BACtalk Control Modules

Ta ble 65 TX-VAV object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-5 BO-5 Control of physical Binary Value
DO-5, if available

DO-6 BO-6 ON = warmup mode Binary Value

DO-7 BO-7 Drive VAV damper Binary Value

OPEN

DO-8 BO-8 Drive VAV damper Binary Value

CLOSED

DO-9 BO-9 ON = Metric display; Binary Value

OFF = English display
DO-10 BO-10 ON = Field service Binary Value
mode not available

DO-11 BO-11 ON = Heating vernier Binary Value

option

DO-12 BO-12 ON = Thermal valve Binary Value

option

DO-13 BO-13 Not used

DO-14 BO-14 Not used

DO-15 BO-15 Not used

DO-16 BO-16 Not used

DO-17 BO-17 ON = VVT heat mode; Binary Value

OFF = Normal cooling
mode
DO-18 BO-18 ON = VVT vent mode; Binary Value
OFF = Normal cooling
mode
DO-19 BO-19 Must be OFF Binary Value

DO-20 BO-20 ON = Force minimum Binary Value

airflow

DO-21 BO-21 ON = Force reheat Binary Value

airflow

DO-22 BO-22 ON = Force maximum Binary Value

airflow

DO-23 BO-23 ON = Select slave Binary Value

mode

DO-24 BO-24 ON = Select custom Binary Value

mode

AV-1 Serial number (part 1 Numeric No Units B1.0

of 3)

AV-2 Serial number (part 2 Numeric No Units B1.0

of 3)

AV-3 Serial number (part 3 Numeric No Units B1.0

of 3)

AV-4 Box type Numeric No Units B1.0

AV-5 Heating type Numeric No Units B1.0

130 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

a. Degrees F or degrees C according to BO 9.

b. The default gateway string converts this to CFM or LPS according to the units in BO 9.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 131

Installation and Operations Guide | BACtalk Control Modules

TX-SA
Ta ble 66 TX-SA object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Space temperature in Temperature Temperature +/- 127 B1.0,TBO9
degrees

AI-2 AI-2 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AI-3 AI-3 Input 3 in degrees Temperature Temperature +/- 127 B1.0,TBO9

(supply temperature)

AI-4 AI-4 Input 4 in counts Raw Counts No Units 0 - 255 B2.55

(OSA sensor)

AI-5 AI-5 Not used

AI-6 AI-6 Not used

AI-7 AI-7 Current heat signal Numeric Percent 0 - 255 B2.55,P

(0-102.0)

AI-8 AI-8 Current cool signal Numeric Percent 0 - 255 B2.55,P

(0-102.0)

AI-9 AI-9 Heating setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AI-10 AI-10 Cooling setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AI-11 AI-11 Heating valve position Numeric Percent 0 - 255 B2.55,P

(0-102.0)

AI-12 AI-12 Cooling valve position Numeric Percent 0 - 255 B2.55,P

(0-102.0)

AI-13 AI-13 Economizer position in Percent Percent 0 - 255 B1.0,P

percent

AI-14 AI-14 Not used

AI-15 AI-15 Not used

AI-16 AI-16 Heating attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AI-17 AI-17 Cooling attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AO-1 AO-1 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AO-2 AO-2 Maximum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-3 AO-3 Minimum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-4 AO-4 Heating offset in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-5 AO-5 Cooling offset in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-6 AO-6 Unoccupied heating Temperature Temperature +/- 127 B1.0,TBO9

setpoint in degrees

132 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 66 TX-SA object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-7 AO-7 Unoccupied cooling Temperature Temperature +/- 127 B1.0,TBO9
setpoint in degrees

AO-8 AO-8 After hours timer in Numeric Time (hours) 0 - 255 B10.0,H
hours

AO-9 AO-9 After hours limit in Numeric Time (hours) 0 - 255 B10.0,H
hours

AO-10 AO-10 Demand offset in Numeric No units 0 - 255 B1.0

counts

AO-11 AO-11 OSA temperature in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-12 AO-12 Fan hours total runtime Numeric Time (hours) 0 - 255 B1.0,H
(can be reset)
AO-13 AO-13 Heating hours Numeric Time (hours) 0 - 255 B1.0,H

AO-14 AO-14 Cooling hours Numeric Time (hours) 0 - 255 B1.0,H

AO-15 AO-15 Heating alarm Temperature Temperature +/- 127 B1.0,TBO9

(attained alarm)
setpoint in degrees

AO-16 AO-16 Cooling alarm Temperature Temperature +/- 127 B1.0,TBO9

(attained alarm)
setpoint in degrees

AO-17 AO-17 Heating valve motor Numeric Time (sec) 0 - 255 B1.0,S
stroke time in seconds
(closed to fully open)

AO-18 AO-18 Cooling valve motor Numeric Time (sec) 0 - 255 B1.0,S
stroke time in seconds
(closed to fully open)

AO-19 AO-19 Economizer lockout Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AO-20 AO-20 Economizer minimum Percent Percent 0 - 255 B1.0,P

position in percent

AO-21 AO-21 Economizer damper Numeric Time (sec) +/- 127 B1.0,S
motor stroke time in
seconds (closed to
fully open)

AO-22 AO-22 Heating stage-1 Temperature Temperature +/- 127 B1.0,TBO9

lockout temperature in
degrees / Heating
stage-2 (compressor 2
or auxiliary heat)
lockout temperature

AO-23 AO-23 Heating stage-2 Temperature Temperature +/- 127 B1.0,TBO9

lockout temperature in
degrees / Heating
stage-3 (auxiliary heat
1 or 2) lockout
temperature

AO-24 AO-24 Cooling stage-1 Temperature Temperature +/- 127 B1.0,TBO9

lockout temperature in
degrees

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 133

Installation and Operations Guide | BACtalk Control Modules

Ta ble 66 TX-SA object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-25 AO-25 Cooling stage-2 Temperature Temperature +/- 127 B1.0,TBO9
lockout temperature in
degrees

DI-1 BI-1 ON = Occupied; OFF = Binary Value

Unoccupied

DI-2 BI-2 ON = heating or Binary Value

cooling control signals
exceed 30%.

DI-3 BI-3 Heating stage-1 status Binary Value

DI-4 BI-4 Cooling stage-1 status Binary Value

DI-5 BI-5 Fan status Binary Value

DI-6 BI-6 Not used

DI-7 BI-7 Not used

DI-8 BI-8 After hours timer ON Binary Value

DI-9 BI-9 Fan status Binary Value

DI-10 BI-10 Cooling stage-1 status Binary Value

/ Reversing valve
(ON = Htg)

DI-11 BI-11 Cooling stage-2 status Binary Value

/ Compressor 1 status

DI-12 BI-12 Heating stage-1 status Binary Value

/ Compressor 2 status

DI-13 BI-13 Heating stage-2 status Binary Value

/ Auxiliary heat stage-1
status

DI-14 BI-14 Heating stage-3 status Binary Value

/ Auxiliary heat stage-2
status

DI-15 BI-15 Not used

DI-16 BI-16 Not used

DI-17 BI-17 Hi space temperature Binary Value
alarm

DI-18 BI-18 Low space Binary Value

temperature alarm

DI-19 BI-19 Unit alarm/attained Binary Value

alarm (attained temp
alarm)

DI-20 BI-20 Condensate alarm Binary Value

DI-21 BI-21 Low supply Binary Value

temperature alarm

DI-22 BI-22 Not used

DI-23 BI-23 Unit test in progress Binary Value

(version 1.11 and later)

134 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 66 TX-SA object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-24 BI-24 ON = DIP switches in Binary Value
an invalid setting

DI-25 BI-25 Economizer lockout Binary Value

(OSA above
economizer lockout
SP)

DI-26 BI-26 Cooling stage-1 Binary Value

lockout (OSA below
SP)

DI-27 BI-27 Cooling stage-2 Binary Value

lockout (OSA below
SP)

DI-28 BI-28 Heating stage-1 Binary Value

lockout (OSA above
SP) Not used for HP
DI-29 BI-29 Heating stage-2 Binary Value
lockout (OSA above
SP)

DI-30 BI-30 Heating stage-3 Binary Value

lockout (OSA above
SP—HP mode only)

DO-1 BO-1 ON = Heating allowed Binary Value

DO-2 BO-2 ON = Cooling allowed Binary Value

DO-3 BO-3 ON = Occupied; OFF = Binary Value

Unoccupied

DO-4 BO-4 Physical DO-4 control, Binary Value

if available

DO-5 BO-5 Physical DO-5 control, Binary Value

if available

DO-6 BO-6 ON = Warmup mode Binary Value

DO-7 BO-7 ON = Cooldown mode Binary Value

DO-8 BO-8 ON = Unit allowed to Binary Value

run

DO-9 BO-9 ON = Metric display; Binary Value

OFF = English display

DO-10 BO-10 ON = Field service Binary Value

mode not available

DO-11 BO-11 ON = Low temperature Binary Value

alarm enabled
DO-12 BO-12 ON = Manual reset of Binary Value
low temperature alarm;
OFF = Automatic reset

DO-13 BO-13 Momentary ON = Binary Value

Reset low temperature
alarm

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 135

Installation and Operations Guide | BACtalk Control Modules

Ta ble 66 TX-SA object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-14 BO-14 Controls fan operation Binary Value
during occupied mode.
OFF= Fan runs
continuously. ON =
Fan cycling enabled;
DO-16 then controls
the type of fan cycling.

DO-15 BO-15 ON = Condensate Binary Value

alarm turns off unit;
OFF = Condensate
alarm turns off cooling
only
DO-16 BO-16 Applies only if DO- Binary Value
14=ON. ON = Fan
cycles during heating
only. OFF = Fan cycles
during heating and
cooling.

DO-17 BO-17 ON = Unit Test Mode Binary Value

(version 1.11 and later)

DO-18 BO-18 Toggles night mode Binary Value

operation for the
heating valve. OFF=
heating valve opens at
night to prevent the coil
from freezing. ON=
valve remains closed
except on a call for
heat (version 1.19 and
later).

AV-1 Serial number (part 1 Numeric No Units B1.0

of 3)

AV-2 Serial number (part 2 Numeric No Units B1.0

of 3)

AV-3 Serial number (part 3 Numeric No Units B1.0

of 3)

AV-4 Heating Type Code Numeric No Units B1.0

AV-5 Cooling Type Code Numeric No Units B1.0

BV-1 HP / AC selected Binary Value

BV-2 Economizer Binary Value

BV-3 2/1 compressor count Binary Value

BV-4 RV cooling / RV Binary Value

heating

136 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

TX-SA-651
Ta ble 67 TX-SA-651object mappings

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
AI-1 AI-1 Space temperature in Temperature Temperature +/- 127 B1.0,TBO9
degrees

AI-2 AI-2 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AI-3 AI-3 Input 3 in degrees Temperature Temperature +/- 127 B1.0,TBO9

(supply temperature)

AI-4 AI-4 Input 4 in counts Raw Counts No Units 0 - 255 B2.55

(usually OSA
temperature)

AI-5 AI-5 Input 5 in counts Raw Counts No Units 0 - 255 B2.55

AI-6 AI-6 Input 6 in counts Raw Counts No Units 0 - 255 B2.55

AI-7 AI-7 Current heat signal (0– Numeric Percent 0 - 255 B2.55,P
102.0)
AI-8 AI-8 Current cool signal (0– Numeric Percent 0 - 255 B2.55,P
102.0)

AI-9 AI-9 Current heating Temperature Temperature +/- 127 B1.0,TBO9

setpoint in degrees
AI-10 AI-10 Current cooling Temperature Temperature +/- 127 B1.0,TBO9
setpoint in degrees

AI-11 AI-11 Heating valve position Numeric Percent 0 - 255 B2.55,P

(0–102.0)

AI-12 AI-12 Cooling valve position Numeric Percent 0 - 255 B2.55,P

(0–102.0)
AI-13 AI-13 Economizer position Numeric Percent 0 - 255 B2.55,P
(0–102.0) (SA in %)

AI-14 AI-14 Internal heating ramp Numeric Percent 0 - 255 B2.55,P

count (0–102.0)

AI-15 AI-15 Internal cooling ramp Numeric Percent 0 - 255 B2.55,P

count (0–102.0)

AI-16 AI-16 Heating attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AI-17 AI-17 Cooling attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AO-1 AO-1 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AO-2 AO-2 Maximum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-3 AO-3 Minimum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees
AO-4 AO-4 Heating offset Numeric Temperature +/- 127 B1.0,TBO9

AO-5 AO-5 Cooling offset Numeric Temperature +/- 127 B1.0,TBO9

AO-6 AO-6 Unoccupied heating Temperature Temperature +/- 127 B1.0,TBO9

setpoint in degrees

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 137

Installation and Operations Guide | BACtalk Control Modules

Ta ble 67 TX-SA-651object mappings (Continued)

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
AO-7 AO-7 Unoccupied cooling Temperature Temperature +/- 127 B1.0,TBO9
setpoint in degrees

AO-8 AO-8 After-hours timer Numeric Time (hours) 0 - 255 B10.0,H

(hours)

AO-9 AO-9 After-hours limit Numeric Time (hours) 0 - 255 B10.0,H

(hours)

AO-10 AO-10 Demand offset in Numeric No units 0 - 255 B1.0

counts

AO-11 AO-11 OSA temperature in Temperature Temperature +/- 127 B1.0,TBO9

degrees
AO-12 AO-12 Fan hours Numeric Time (hours) 0 - 255 B1.0,H

AO-13 AO-13 Heating hours Numeric Time (hours) 0 - 255 B1.0,H

AO-14 AO-14 Cooling hours Numeric Time (hours) 0 - 255 B1.0,H

AO-15 AO-15 Heating attained Temperature Temperature +/- 127 B1.0,TBO9

temperature alarm
setpoint in degrees

AO-16 AO-16 Cooling attained Temperature Temperature +/- 127 B1.0,TBO9

temperature alarm
setpoint in degrees

AO-17 AO-17 Heating valve speed in Numeric Time (sec) 0-102 B1.0,S
seconds

AO-18 AO-18 Cooling valve speed in Numeric Time (sec) 0-102 B1.0,S
seconds

AO-19 AO-19 Economizer lockout Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees
AO-20 AO-20 Economizer minimum Numeric Percent 0 - 255 B2.55,P
position (0–102.0)

AO-21 AO-21 Analog output zero Numeric No Units 0 - 255 B9,6

value (2.0–25.5mA;
e.g., 4.0=4mA)

AO-22 AO-22 Heating lockout Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AO-23 AO-23 Analog output Numeric No Units 0 - 255 B9,6

maximum value (2.0–
25.5mA; e.g.,
20.0=20mA)
AO-24 AO-24 Cooling lockout Temperature Temperature +/- 127 B1.0,TBO9
temperature in
degrees

AO-25 AO-25 Unit type code Encoded No Units 0 - 255 B1.0

AO-26 AO-26 Operating backup Encoded No Units 0 - 255 B1.0

mode code

AO-27 AO-27 Heating type code Encoded No Units 0 - 255 B1.0

AO-28 AO-28 Cooling type code Encoded No Units 0 - 255 B1.0

138 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 67 TX-SA-651object mappings (Continued)

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
AO-29 AO-29 Heating ramp time Numeric Time (min) 0 - 255 B1.0,M
(minutes)

AO-30 AO-30 Cooling ramp time Numeric Time (min) 0 - 255 B1.0,M
(minutes)

AO-31 AO-31 Program Mode: Numeric No Units 0 - 255 B2.55

Physical analog output
(0–102.0)

DI-1 BI-1 ON = Occupied; OFF = Binary Value

Unoccupied (with
Microset, ON =
Occupied. No
Microset, physical DI-
1)

DI-2 BI-2 Start hydronic loop Binary Value

pump—HP mode only
(with Microset: After-
hours ON. No
Microset, physical DI-
2)
DI-3 BI-3 Heat stage 1 status / Binary Value
Physical DI-3

DI-4 BI-4 Cooling stage 1 status Binary Value

/ Physical DI-4

DI-5 BI-5 Fan status / Physical Binary Value

DI-5
DI-6 BI-6 ON = External alarm Binary Value
on and shutdown
enabled / Physical DI-6

DI-7 BI-7 High or low space Binary Value

temperature alarm ON
/ Not used

DI-8 BI-8 After-hours timer on / Binary Value

After-hours on (with
Microset or
Microtouch)

DI-9 BI-9 Fan status Binary Value

DI-10 BI-10 Reversing valve Binary Value

status—HP only; ON =
Heat

DI-11 BI-11 Compressor 1 status— Binary Value

HP only

DI-12 BI-12 Compressor 2 status— Binary Value

HP only

DI-13 BI-13 Auxiliary heat stage 1 Binary Value

on—HP only

DI-14 BI-14 Auxiliary heat stage 2 Binary Value

on—HP only

DI-15 BI-15 Not used

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 139

Installation and Operations Guide | BACtalk Control Modules

Ta ble 67 TX-SA-651object mappings (Continued)

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
DI-16 BI-16 ON = HP mode; OFF = Binary Value
AC mode

DI-17 BI-17 High space Binary Value

temperature alarm

DI-18 BI-18 Low space Binary Value

temperature alarm

DI-19 BI-19 Attained temperature Binary Value

alarm

DI-20 BI-20 External alarm Binary Value

(condensate alarm on
SA)

DI-21 BI-21 Low supply Binary Value

temperature alarm

DI-22 BI-22 ON = Metric units; OFF Binary Value

= English units

DI-23 BI-23 ON = Bad space Binary Value

temperature sensor
DI-24 BI-24 Always ON Binary Value

DI-25 BI-25 Economizer lockout Binary Value

(OSA above
economizer lockout
setpoint)

DI-26 BI-26 Cooling lockout (OSA Binary Value

below setpoint)

DI-27 BI-27 Heating lockout (OSA Binary Value

above setpoint)

DO-1 BO-1 ON = Heating allowed / Binary Value

Physical control of DO-
1

DO-2 BO-2 ON = Cooling allowed / Binary Value

Physical control of DO-
2

DO-3 BO-3 ON = Occupied mode; Binary Value

OFF = Unoccupied
mode / Physical control
of DO-3

DO-4 BO-4 Physical control of DO- Binary Value

4, if available /
Physical control of DO-
4
DO-5 BO-5 Physical control of DO- Binary Value
5, if available /
Physical control of DO-
5

DO-6 BO-6 Warmup mode / ON = Binary Value

Occupied mode; OFF
= Unoccupied mode

140 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 67 TX-SA-651object mappings (Continued)

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
DO-7 BO-7 Cooldown mode / Not Binary Value
used

DO-8 BO-8 ON = Unit allowed; Binary Value

OFF = Not allowed /
Not used

DO-9 BO-9 ON = Metric display; Binary Value

OFF = English display

DO-10 BO-10 ON = Field service Binary Value

(FS) mode not
available; OFF = FS
mode available

DO-11 BO-11 ON = Low temperature Binary Value

alarm enabled
DO-12 BO-12 ON = Manual reset of Binary Value
low temp. alarm; OFF
= Automatic reset

DO-13 BO-13 Reset low temperature Binary Value

alarm (momentary on)

DO-14 BO-14 Controls fan operation Binary Value

during occupied mode.
OFF = Fan runs
continuously; ON =
Fan cycling enabled;
DO-16 then controls
the type of fan cycling.

DO-15 BO-15 Not used

DO-16 BO-16 Applies only if DO- Binary Value
14=ON. ON = Fan
cycles during heating
only; OFF = Fan cycles
during heating and
cooling.
DO-17 BO-17 ON = External alarm Binary Value
shutdown enabled;
DO-18 then controls
type of shutdown. OFF
= External alarm
shutdown disabled

DO-18 BO-18 Applies only if DO-17 = Binary Value

ON. ON = Alarm
shutdown turns off all
outputs; OFF = Alarm
shutdown turns off
cooling only

DO-19 BO-19 Not used

DO-20 BO-20 ON = Occupied—only Binary Value

when unoccupied
override control is set
to manual mode

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 141

Installation and Operations Guide | BACtalk Control Modules

Ta ble 67 TX-SA-651object mappings (Continued)

Description
TUX BACnet TUX Data Default Gateway
(stand-alone mode/ Data Type BACnet Units
Point object Range String
program mode)
AV-1 Serial number (part 1 Numeric No Units B1.0
of 3)

AV-2 Serial number (part 2 Numeric No Units B1.0

of 3)

AV-3 Serial number (part 3 Numeric No Units B1.0

of 3)

BV-1 Heating step 1 ON Binary Value

BV-2 Heating step 2 ON Binary Value

BV-3 Heating step 3 ON Binary Value

BV-4 Heating step 4 ON Binary Value

BV-5 Cooling step 1 ON Binary Value

BV-6 Cooling step 2 ON Binary Value

BV-7 Cooling step 3 ON Binary Value

BV-8 Cooling step 4 ON Binary Value

142 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

TX-HOST-R3
Ta ble 68 TX-HOST-R3 object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Space temperature in Temperature Temperature +/- 127 B1.0,TBO9
degrees

AI-2 AI-2 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AI-3 AI-3 Input 3 in counts if DO Raw Counts No Units 0 - 255 B2.55

6 is ON (version 1.03
or newer)

AI-4 AI-4 Input 4 in counts if DO Raw Counts No Units 0 - 255 B2.55

6 is ON (version 1.03
or newer)

AI-5 AI-5 Input 5 in counts if DO Raw Counts No Units 0 - 255 B2.55

6 is ON (version 1.03
or newer)

AI-6 AI-6 Input 6 in counts if DO Raw Counts No Units 0 - 255 B2.55

6 is ON (version 1.03
or newer)

AI-7 AI-7 Current heat signal Numeric Percent 0 - 255 B2.55,P

AI-8 AI-8 Current cool signal Numeric Percent 0 - 255 B2.55,P

AI-9 AI-9 Heating setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AI-10 AI-10 Cooling setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AI-11 AI-11 Motion timer (in Numeric Time (min) 0 - 255 B10.0,M
minutes)

AI-12 AI-12 Not used

AI-13 AI-13 Not used

AI-14 AI-14 Internal heating ramp Numeric Percent 0 - 255 B2.55,P

signal
AI-15 AI-15 Internal cooling ramp Numeric Percent 0 - 255 B2.55,P
signal

AI-16 AI-16 Heating attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AI-17 AI-17 Cooling attained Temperature Temperature +/- 127 B1.0,TBO9

temperature in
degrees

AO-1 AO-1 Setpoint in degrees Temperature Temperature +/- 127 B1.0,TBO9

AO-2 AO-2 Maximum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-3 AO-3 Minimum setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-4 AO-4 Heating deadband Temperature Temperature +/- 127 B1.0,TBO9

AO-5 AO-5 Cooling deadband Temperature Temperature +/- 127 B1.0,TBO9

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 143

Installation and Operations Guide | BACtalk Control Modules

Ta ble 68 TX-HOST-R3 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-6 AO-6 Unoccupied or not- Temperature Temperature +/- 127 B1.0,TBO9
rented mode heating
setpoint

AO-7 AO-7 Unoccupied or not- Temperature Temperature +/- 127 B1.0,TBO9

rented mode cooling
setpoint
AO-8 AO-8 Off mode heating Temperature Temperature +/- 127 B1.0,TBO9
setpoint

AO-9 AO-9 Off mode cooling Temperature Temperature +/- 127 B1.0,TBO9
setpoint

AO-10 AO-10 Demand offset in Numeric No units 0-255 B1.0

counts

AO-11 AO-11 OSA temperature in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-12 AO-12 Fan hours Numeric Time (hours) 0 - 32768 B1.0,H

AO-13 AO-13 Heating hours Numeric Time (hours) 0 - 32768 B1.0,H

AO-14 AO-14 Cooling hours Numeric Time (hours) 0 - 32768 B1.0,H

AO-15 AO-15 Heating alarm setpoint Temperature Temperature +/- 127 B1.0,TBO9
in degrees
AO-16 AO-16 Cooling alarm setpoint Temperature Temperature +/- 127 B1.0,TBO9
in degrees

AO-17 AO-17 Startup setpoint in Temperature Temperature +/- 127 B1.0,TBO9

degrees

AO-18 AO-18 Motion timer limit in Numeric Time (min) 0 - 255 B10.0,M
minutes
AO-19 AO-19 Maid timer limit in Numeric Time (min) 0 - 255 B10.0,M
minutes

AO-20 AO-20 Not used

AO-21 AO-21 Not used

AO-22 AO-22 Not used

AO-23 AO-23 Not used

AO-24 AO-24 Not used

AO-25 AO-25 Not used

AO-26 AO-26 Not used

AO-27 AO-27 Not used

AO-28 AO-28 Not used

AO-29 AO-29 Heating ramp time Numeric Time (min) 0 - 255 B10.0,M
(minutes)

AO-30 AO-30 Cooling ramp time Numeric Time (min) 0 - 255 B10.0,M
(minutes)

DI-1 BI-1 ON = Occupied; OFF = Binary Value

Unoccupied

144 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 68 TX-HOST-R3 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-2 BI-2 Heating desired (not Binary Value
disabled by DO-1)

DI-3 BI-3 Heat status Binary Value

DI-4 BI-4 Cooling status Binary Value

DI-5 BI-5 Physical DI-3 (smoke Binary Value

detector; ON = closure,
OFF = open)

DI-6 BI-6 Physical DI-4 (discrete Binary Value

motion detector)
DI-7 BI-7 Cooling desired (not Binary Value
disabled by DO 2)

DI-8 BI-8 Not used

DI-9 BI-9 Fan high speed status Binary Value

DI-10 BI-10 Fan medium speed Binary Value

status

DI-11 BI-11 Fan low speed status Binary Value

DI-12 BI-12 Cooling status Binary Value

DI-13 BI-13 Heating status Binary Value

DI-14 BI-14 Not used

DI-15 BI-15 Not used

DI-16 BI-16 Not used

DI-17 BI-17 High space Binary Value

temperature alarm

DI-18 BI-18 Low space Binary Value

temperature alarm
DI-19 BI-19 Attained temperature Binary Value
alarm

DI-20 BI-20 Not used

DI-21 BI-21 Not used

DI-22 BI-22 ON = Metric units; OFF Binary Value

= English units

DI-23 BI-23 ON = Bad space Binary Value

temperature sensor

DI-24 BI-24 Always ON Binary Value

DI-25 BI-25 Fan speed: ON = 2- Binary Value
speed; OFF = 1-speed

DI-26 BI-26 Fan speed: ON = 3- Binary Value

speed; OFF = 1 or 2-
speed

DI-27 BI-27 ON = Heat Pump Binary Value

mode; OFF = AC mode

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 145

Installation and Operations Guide | BACtalk Control Modules

Ta ble 68 TX-HOST-R3 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-28 BI-28 HP: ON = RV Binary Value
energized for cooling;
OFF = Heating / AC:
ON = Heating valve
NO; OFF = Heating
valve NC

DI-29 BI-29 ON = Motion detector Binary Value

logic enabled

DI-30 BI-30 ON = 2-pipe mode; Binary Value

OFF = Normal

DO-1 BO-1 ON = Heating allowed Binary Value

DO-2 BO-2 ON = Cooling allowed Binary Value

DO-3 BO-3 ON = Rented mode; Binary Value

OFF = Unoccupied
mode

DO-4 BO-4 ON = Occupied mode; Binary Value

OFF = Automatic
selection

DO-5 BO-5 Controls physical DO-5

when BO-7 is ON

DO-6 BO-6 ON = Enable inputs 3- Binary Value

6, disable internal Btu
meter; OFF = Enable
internal meter for Btu
monitoring

DO-7 BO-7 ON = DOs 1-5 control Binary Value

physical outputs

DO-8 BO-8 ON = Allow unit to run; Binary Value

OFF = shutdown

DO-9 BO-9 ON = Metric display; Binary Value

OFF = English display

DO-10 BO-10 ON = Microset Field Binary Value

Service Mode not
available; OFF =
Microset Field Service
Mode available
DO-11 BO-11 ON = Fan cycles with Binary Value
demand; OFF = Fan
continuous

DO-12 BO-12 ON = TMV valve for Binary Value

cooling; OFF = Staged
cooling

DO-13 BO-13 ON = TMV valve for Binary Value

heating; OFF = Staged
heating

146 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 68 TX-HOST-R3 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-14 BO-14 ON = Entry door switch Binary Value
closes when door
opens; OFF = Entry
door switch opens
when door opens

AV-1 Serial number (part 1 Numeric No Units B1.0

of 3)

AV-2 Serial number (part 2 Numeric No Units B1.0

of 3)

AV-3 Serial number (part 3 Numeric No Units B1.0

of 3)

BV-1 Alarm - smoke detector Binary Value

shutdown

BV-2 Maid override Binary Value

BV-3 Rented Binary Value

BV-4 Fan turned off Binary Value

BV-5 Patio door open Binary Value

BV-6 Cold water for 2 pipe Binary Value

BV-7 Hot water for 2 pipe Binary Value

BV-8 Patio door shutdown Binary Value

enabled

BV-9 N.O. patio door switch Binary Value

BV-10 Smoke shutdown Binary Value

enabled

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 147

Installation and Operations Guide | BACtalk Control Modules

TX-APLC
Ta ble 69 TX-APLC object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-2 AI-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-3 AI-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-4 AI-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-5 AI-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-6 AI-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-7 AI-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-8 AI-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-9 AI-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-10 AI-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-11 AI-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-12 AI-12 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-13 AI-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-14 AI-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-15 AI-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-16 AI-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-17 AI-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-18 AI-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-19 AI-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-20 AI-20 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-21 AI-21 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-22 AI-22 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-23 AI-23 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-24 AI-24 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-1 AO-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-2 AO-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-3 AO-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-4 AO-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-5 AO-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-6 AO-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-7 AO-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-8 AO-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-9 AO-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-10 AO-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-11 AO-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-12 AO-12 Logical Point Unknown No Units +/- 3276.7 B10.0

148 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 69 TX-APLC object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-13 AO-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-14 AO-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-15 AO-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-16 AO-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-17 AO-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-18 AO-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-19 AO-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-20 AO-20 Logical Point Unknown No Units +/- 3276.7 B10.0

DI-1 BI-1 Logical Point Binary Value

DI-2 BI-2 Logical Point Binary Value

DI-3 BI-3 Logical Point Binary Value

DI-4 BI-4 Logical Point Binary Value

DI-5 BI-5 Logical Point Binary Value

DI-6 BI-6 Logical Point Binary Value

DI-7 BI-7 Logical Point Binary Value

DI-8 BI-8 Logical Point Binary Value

DI-9 BI-9 Logical Point Binary Value

DI-10 BI-10 Logical Point Binary Value

DI-11 BI-11 Logical Point Binary Value

DI-12 BI-12 Logical Point Binary Value

DI-13 BI-13 Logical Point Binary Value

DI-14 BI-14 Logical Point Binary Value

DI-15 BI-15 Logical Point Binary Value

DI-16 BI-16 Logical Point Binary Value

DI-17 BI-17 Logical Point Binary Value

DI-18 BI-18 Logical Point Binary Value

DI-19 BI-19 Logical Point Binary Value

DI-20 BI-20 Logical Point Binary Value

DI-21 BI-21 Logical Point Binary Value

DI-22 BI-22 Logical Point Binary Value

DI-23 BI-23 Logical Point Binary Value

DI-24 BI-24 Logical Point Binary Value

DI-25 BI-25 Logical Point Binary Value

DI-26 BI-26 Logical Point Binary Value

DI-27 BI-27 Logical Point Binary Value

DI-28 BI-28 Logical Point Binary Value

DI-29 BI-29 Logical Point Binary Value

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 149

Installation and Operations Guide | BACtalk Control Modules

Ta ble 69 TX-APLC object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-30 BI-30 Logical Point Binary Value

DI-31 BI-31 Logical Point Binary Value

DI-32 BI-32 Logical Point Binary Value

DO-1 BO-1 Logical Point Binary Value

DO-2 BO-2 Logical Point Binary Value

DO-3 BO-3 Logical Point Binary Value

DO-4 BO-4 Logical Point Binary Value

DO-5 BO-5 Logical Point Binary Value

DO-6 BO-6 Logical Point Binary Value

DO-7 BO-7 Logical Point Binary Value

DO-8 BO-8 Logical Point Binary Value

DO-9 BO-9 Logical Point Binary Value

DO-10 BO-10 Logical Point Binary Value

DO-11 BO-11 Logical Point Binary Value

DO-12 BO-12 Logical Point Binary Value

DO-13 BO-13 Logical Point Binary Value

DO-14 BO-14 Logical Point Binary Value

DO-15 BO-15 Logical Point Binary Value

DO-16 BO-16 Logical Point Binary Value

DO-17 BO-17 Logical Point Binary Value

DO-18 BO-18 Logical Point Binary Value

DO-19 BO-19 Logical Point Binary Value

DO-20 BO-20 Logical Point Binary Value

DO-21 BO-21 Logical Point Binary Value

DO-22 BO-22 Logical Point Binary Value

DO-23 BO-23 Logical Point Binary Value

DO-24 BO-24 Logical Point Binary Value

DO-25 BO-25 Logical Point Binary Value

DO-26 BO-26 Logical Point Binary Value

DO-27 BO-27 Logical Point Binary Value

DO-28 BO-28 Logical Point Binary Value

DO-29 BO-29 Logical Point Binary Value

DO-30 BO-30 Logical Point Binary Value

DO-31 BO-31 Logical Point Binary Value

DO-32 BO-32 Logical Point Binary Value

150 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

TUX APLC-2
Ta ble 70 TX-APLC-2 object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-2 AI-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-3 AI-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-4 AI-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-5 AI-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-6 AI-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-7 AI-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-8 AI-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-9 AI-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-10 AI-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-11 AI-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-12 AI-12 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-13 AI-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-14 AI-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-15 AI-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-16 AI-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-17 AI-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-18 AI-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-19 AI-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-20 AI-20 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-21 AI-21 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-22 AI-22 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-23 AI-23 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-24 AI-24 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-1 AO-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-2 AO-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-3 AO-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-4 AO-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-5 AO-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-6 AO-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-7 AO-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-8 AO-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-9 AO-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-10 AO-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-11 AO-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-12 AO-12 Logical Point Unknown No Units +/- 3276.7 B10.0

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 151

Installation and Operations Guide | BACtalk Control Modules

Ta ble 70 TX-APLC-2 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-13 AO-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-14 AO-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-15 AO-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-16 AO-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-17 AO-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-18 AO-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-19 AO-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-20 AO-20 Logical Point Unknown No Units +/- 3276.7 B10.0

DI-1 BI-1 Logical Point Binary Value

DI-2 BI-2 Logical Point Binary Value

DI-3 BI-3 Logical Point Binary Value

DI-4 BI-4 Logical Point Binary Value

DI-5 BI-5 Logical Point Binary Value

DI-6 BI-6 Logical Point Binary Value

DI-7 BI-7 Logical Point Binary Value

DI-8 BI-8 Logical Point Binary Value

DI-9 BI-9 Logical Point Binary Value

DI-10 BI-10 Logical Point Binary Value

DI-11 BI-11 Logical Point Binary Value

DI-12 BI-12 Logical Point Binary Value

DI-13 BI-13 Logical Point Binary Value

DI-14 BI-14 Logical Point Binary Value

DI-15 BI-15 Logical Point Binary Value

DI-16 BI-16 Logical Point Binary Value

DI-17 BI-17 Logical Point Binary Value

DI-18 BI-18 Logical Point Binary Value

DI-19 BI-19 Logical Point Binary Value

DI-20 BI-20 Logical Point Binary Value

DI-21 BI-21 Logical Point Binary Value

DI-22 BI-22 Logical Point Binary Value

DI-23 BI-23 Logical Point Binary Value

DI-24 BI-24 Logical Point Binary Value

DI-25 BI-25 Logical Point Binary Value

DI-26 BI-26 Logical Point Binary Value

DI-27 BI-27 Logical Point Binary Value

DI-28 BI-28 Logical Point Binary Value

DI-29 BI-29 Logical Point Binary Value

152 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 70 TX-APLC-2 object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-30 BI-30 Logical Point Binary Value

DI-31 BI-31 Logical Point Binary Value

DI-32 BI-32 Logical Point Binary Value

DO-1 BO-1 Logical Point Binary Value

DO-2 BO-2 Logical Point Binary Value

DO-3 BO-3 Logical Point Binary Value

DO-4 BO-4 Logical Point Binary Value

DO-5 BO-5 Logical Point Binary Value

DO-6 BO-6 Logical Point Binary Value

DO-7 BO-7 Logical Point Binary Value

DO-8 BO-8 Logical Point Binary Value

DO-9 BO-9 Logical Point Binary Value

DO-10 BO-10 Logical Point Binary Value

DO-11 BO-11 Logical Point Binary Value

DO-12 BO-12 Logical Point Binary Value

DO-13 BO-13 Logical Point Binary Value

DO-14 BO-14 Logical Point Binary Value

DO-15 BO-15 Logical Point Binary Value

DO-16 BO-16 Logical Point Binary Value

DO-17 BO-17 Logical Point Binary Value

DO-18 BO-18 Logical Point Binary Value

DO-19 BO-19 Logical Point Binary Value

DO-20 BO-20 Logical Point Binary Value

DO-21 BO-21 Logical Point Binary Value

DO-22 BO-22 Logical Point Binary Value

DO-23 BO-23 Logical Point Binary Value

DO-24 BO-24 Logical Point Binary Value

DO-25 BO-25 Logical Point Binary Value

DO-26 BO-26 Logical Point Binary Value

DO-27 BO-27 Logical Point Binary Value

DO-28 BO-28 Logical Point Binary Value

DO-29 BO-29 Logical Point Binary Value

DO-30 BO-30 Logical Point Binary Value

DO-31 BO-31 Logical Point Binary Value

DO-32 BO-32 Logical Point Binary Value

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 153

Installation and Operations Guide | BACtalk Control Modules

TX-R3P
Ta ble 71 TX-R3P object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-2 AI-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-3 AI-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-4 AI-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-5 AI-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-6 AI-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-7 AI-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-8 AI-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-9 AI-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-10 AI-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-11 AI-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-12 AI-12 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-13 AI-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-14 AI-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-15 AI-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-16 AI-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-17 AI-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-18 AI-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-19 AI-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-20 AI-20 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-21 AI-21 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-22 AI-22 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-23 AI-23 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-24 AI-24 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-1 AO-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-2 AO-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-3 AO-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-4 AO-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-5 AO-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-6 AO-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-7 AO-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-8 AO-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-9 AO-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-10 AO-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-11 AO-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-12 AO-12 Logical Point Unknown No Units +/- 3276.7 B10.0

154 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 71 TX-R3P object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-13 AO-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-14 AO-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-15 AO-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-16 AO-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-17 AO-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-18 AO-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-19 AO-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-20 AO-20 Logical Point Unknown No Units +/- 3276.7 B10.0

DI-1 BI-1 Logical Point Binary Value

DI-2 BI-2 Logical Point Binary Value

DI-3 BI-3 Logical Point Binary Value

DI-4 BI-4 Logical Point Binary Value

DI-5 BI-5 Logical Point Binary Value

DI-6 BI-6 Logical Point Binary Value

DI-7 BI-7 Logical Point Binary Value

DI-8 BI-8 Logical Point Binary Value

DI-9 BI-9 Logical Point Binary Value

DI-10 BI-10 Logical Point Binary Value

DI-11 BI-11 Logical Point Binary Value

DI-12 BI-12 Logical Point Binary Value

DI-13 BI-13 Logical Point Binary Value

DI-14 BI-14 Logical Point Binary Value

DI-15 BI-15 Logical Point Binary Value

DI-16 BI-16 Logical Point Binary Value

DI-17 BI-17 Logical Point Binary Value

DI-18 BI-18 Logical Point Binary Value

DI-19 BI-19 Logical Point Binary Value

DI-20 BI-20 Logical Point Binary Value

DI-21 BI-21 Logical Point Binary Value

DI-22 BI-22 Logical Point Binary Value

DI-23 BI-23 Logical Point Binary Value

DI-24 BI-24 Logical Point Binary Value

DI-25 BI-25 Logical Point Binary Value

DI-26 BI-26 Logical Point Binary Value

DI-27 BI-27 Logical Point Binary Value

DI-28 BI-28 Logical Point Binary Value

DI-29 BI-29 Logical Point Binary Value

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 155

Installation and Operations Guide | BACtalk Control Modules

Ta ble 71 TX-R3P object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-30 BI-30 Logical Point Binary Value

DI-31 BI-31 Logical Point Binary Value

DI-32 BI-32 Logical Point Binary Value

DO-1 BO-1 Logical Point Binary Value

DO-2 BO-2 Logical Point Binary Value

DO-3 BO-3 Logical Point Binary Value

DO-4 BO-4 Logical Point Binary Value

DO-5 BO-5 Logical Point Binary Value

DO-6 BO-6 Logical Point Binary Value

DO-7 BO-7 Logical Point Binary Value

DO-8 BO-8 Logical Point Binary Value

DO-9 BO-9 Logical Point Binary Value

DO-10 BO-10 Logical Point Binary Value

DO-11 BO-11 Logical Point Binary Value

DO-12 BO-12 Logical Point Binary Value

DO-13 BO-13 Logical Point Binary Value

DO-14 BO-14 Logical Point Binary Value

DO-15 BO-15 Logical Point Binary Value

DO-16 BO-16 Logical Point Binary Value

DO-17 BO-17 Logical Point Binary Value

DO-18 BO-18 Logical Point Binary Value

DO-19 BO-19 Logical Point Binary Value

DO-20 BO-20 Logical Point Binary Value

DO-21 BO-21 Logical Point Binary Value

DO-22 BO-22 Logical Point Binary Value

DO-23 BO-23 Logical Point Binary Value

DO-24 BO-24 Logical Point Binary Value

DO-25 BO-25 Logical Point Binary Value

DO-26 BO-26 Logical Point Binary Value

DO-27 BO-27 Logical Point Binary Value

DO-28 BO-28 Logical Point Binary Value

DO-29 BO-29 Logical Point Binary Value

DO-30 BO-30 Logical Point Binary Value

DO-31 BO-31 Logical Point Binary Value

DO-32 BO-32 Logical Point Binary Value

156 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

TX-653P
Ta ble 72 TX-653P object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-2 AI-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-3 AI-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-4 AI-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-5 AI-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-6 AI-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-7 AI-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-8 AI-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-9 AI-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-10 AI-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-11 AI-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-12 AI-12 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-13 AI-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-14 AI-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-15 AI-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-16 AI-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-17 AI-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-18 AI-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-19 AI-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-20 AI-20 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-21 AI-21 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-22 AI-22 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-23 AI-23 Logical Point Unknown No Units +/- 3276.7 B10.0

AI-24 AI-24 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-1 AO-1 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-2 AO-2 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-3 AO-3 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-4 AO-4 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-5 AO-5 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-6 AO-6 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-7 AO-7 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-8 AO-8 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-9 AO-9 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-10 AO-10 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-11 AO-11 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-12 AO-12 Logical Point Unknown No Units +/- 3276.7 B10.0

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 157

Installation and Operations Guide | BACtalk Control Modules

Ta ble 72 TX-653P object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AO-13 AO-13 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-14 AO-14 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-15 AO-15 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-16 AO-16 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-17 AO-17 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-18 AO-18 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-19 AO-19 Logical Point Unknown No Units +/- 3276.7 B10.0

AO-20 AO-20 Logical Point Unknown No Units +/- 3276.7 B10.0

DI-1 BI-1 Logical Point Binary Value

DI-2 BI-2 Logical Point Binary Value

DI-3 BI-3 Logical Point Binary Value

DI-4 BI-4 Logical Point Binary Value

DI-5 BI-5 Logical Point Binary Value

DI-6 BI-6 Logical Point Binary Value

DI-7 BI-7 Logical Point Binary Value

DI-8 BI-8 Logical Point Binary Value

DI-9 BI-9 Logical Point Binary Value

DI-10 BI-10 Logical Point Binary Value

DI-11 BI-11 Logical Point Binary Value

DI-12 BI-12 Logical Point Binary Value

DI-13 BI-13 Logical Point Binary Value

DI-14 BI-14 Logical Point Binary Value

DI-15 BI-15 Logical Point Binary Value

DI-16 BI-16 Logical Point Binary Value

DI-17 BI-17 Logical Point Binary Value

DI-18 BI-18 Logical Point Binary Value

DI-19 BI-19 Logical Point Binary Value

DI-20 BI-20 Logical Point Binary Value

DI-21 BI-21 Logical Point Binary Value

DI-22 BI-22 Logical Point Binary Value

DI-23 BI-23 Logical Point Binary Value

DI-24 BI-24 Logical Point Binary Value

DI-25 BI-25 Logical Point Binary Value

DI-26 BI-26 Logical Point Binary Value

DI-27 BI-27 Logical Point Binary Value

DI-28 BI-28 Logical Point Binary Value

DI-29 BI-29 Logical Point Binary Value

158 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 72 TX-653P object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-30 BI-30 Logical Point Binary Value

DI-31 BI-31 Logical Point Binary Value

DI-32 BI-32 Logical Point Binary Value

DO-1 BO-1 Logical Point Binary Value

DO-2 BO-2 Logical Point Binary Value

DO-3 BO-3 Logical Point Binary Value

DO-4 BO-4 Logical Point Binary Value

DO-5 BO-5 Logical Point Binary Value

DO-6 BO-6 Logical Point Binary Value

DO-7 BO-7 Logical Point Binary Value

DO-8 BO-8 Logical Point Binary Value

DO-9 BO-9 Logical Point Binary Value

DO-10 BO-10 Logical Point Binary Value

DO-11 BO-11 Logical Point Binary Value

DO-12 BO-12 Logical Point Binary Value

DO-13 BO-13 Logical Point Binary Value

DO-14 BO-14 Logical Point Binary Value

DO-15 BO-15 Logical Point Binary Value

DO-16 BO-16 Logical Point Binary Value

DO-17 BO-17 Logical Point Binary Value

DO-18 BO-18 Logical Point Binary Value

DO-19 BO-19 Logical Point Binary Value

DO-20 BO-20 Logical Point Binary Value

DO-21 BO-21 Logical Point Binary Value

DO-22 BO-22 Logical Point Binary Value

DO-23 BO-23 Logical Point Binary Value

DO-24 BO-24 Logical Point Binary Value

DO-25 BO-25 Logical Point Binary Value

DO-26 BO-26 Logical Point Binary Value

DO-27 BO-27 Logical Point Binary Value

DO-28 BO-28 Logical Point Binary Value

DO-29 BO-29 Logical Point Binary Value

DO-30 BO-30 Logical Point Binary Value

DO-31 BO-31 Logical Point Binary Value

DO-32 BO-32 Logical Point Binary Value

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 159

Installation and Operations Guide | BACtalk Control Modules

TX-MQ-WSHP
Ta ble 73 TX-MQ-WSHP object mappings

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-1 AI-1 Space temperature Temperature Temperature +/- 3276.7 B10.0

AI-2 AI-2 Return air temperature Temperature Temperature +/- 3276.7 B10.0

AI-3 AI-3 Supply air temperature Temperature Temperature +/- 3276.7 B10.0

AI-4 AI-4 Water temperature Temperature Temperature +/- 3276.7 B10.0

AI-5 AI-5 Occupied setpoint as Temperature Temperature +/- 3276.7 B10.0

set by Microset

AI-6 AI-6 Minimum allowed Temperature Temperature +/- 3276.7 B10.0

setpoint

AI-7 AI-7 Maximum allowed Temperature Temperature +/- 3276.7 B10.0

setpoint

AI-8 AI-8 Heating offset, which is Temperature Temperature +/- 3276.7 B10.0
subtracted from the
occupied setpoint to
calculate the internally
used heating setpoint

AI-9 AI-9 Cooling offset, which is Temperature Temperature +/- 3276.7 B10.0
added to the occupied
setpoint to calculate
the internally used
cooling setpoint

AI-10 AI-10 Unoccupied heating Temperature Temperature +/- 3276.7 B10.0

setpoint

AI-11 AI-11 Unoccupied cooling Temperature Temperature +/- 3276.7 B10.0

setpoint
AI-12 AI-12 Current heating Temperature Temperature +/- 3276.7 B10.0
setpoint

AI-13 AI-13 Current cooling Temperature Temperature +/- 3276.7 B10.0

setpoint

AI-14 AI-14 Heating attained Temperature Temperature +/- 3276.7 B10.0

temperature, recorded
when the compressor
is ON in heating mode
for at least 2 minutes
AI-15 AI-15 Cooling attained Temperature Temperature +/- 3276.7 B10.0
temperature, recorded
when the compressor
is ON in cooling mode
for at least 2 minutes

AI-16 AI-16 Supply voltage in Percent Percent +/- 3276.7 B10.0

percent of nameplate
value

AI-17 AI-17 Drain pan signal in Percent Percent +/- 3276.7 B10.0
percent

AI-18 AI-18 Current internally used Percent Percent +/- 3276.7 B10.0
heating control signal
in percent

160 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
AI-19 AI-19 Current internally used Percent Percent +/- 3276.7 B10.0
cooling control signal
in percent

AI-20 AI-20 Reserved

AI-21 AI-21 After-hours limit in Numeric Time (hours) +/- 3276.7 B10.0
hours

AI-22 AI-22 Time remaining for Numeric Time (hours) +/- 3276.7 B10.0
after-hours operation

AI-23 AI-23 Fan hours Numeric Time (hours) +/- 3276.7 B10.0

AI-24 AI-24 Compressor 1 hours Numeric Time (hours) +/- 3276.7 B10.0

AI-25 AI-25 Compressor 1 starts Numeric No Units +/- 3276.7 B10.0

AI-26 AI-26 Compressor 2 hours if Numeric Time (hours) +/- 3276.7 B10.0
aux module present

AI-27 AI-27 Compressor 2 starts if Numeric No Units +/- 3276.7 B10.0

aux module present

AI-28 AI-28 Heating hours Numeric Time (hours) +/- 3276.7 B10.0

AI-29 AI-29 Cooling hours Numeric Time (hours) +/- 3276.7 B10.0

AI-30 AI-30 Filter hours Numeric Time (hours) +/- 3276.7 B10.0

AO-1 AO-1 Heating attained Temperature Temperature +/- 3276.7 B10.0

temperature alarm
setpoint
AO-2 AO-2 Cooling attained Temperature Temperature +/- 3276.7 B10.0
temperature alarm
setpoint

AO-3 AO-3 Outside air Temperature Temperature +/- 3276.7 B10.0

temperature for display
on Microset (write this
value in units of
degrees Farenheit or
degrees Celsius as
appropriate)

AO-4 AO-4 Reserved for future

use as hotel startup
temperature

AO-5 AO-5 Low water temperature Temperature Temperature +/- 3276.7 B10.0
alarm setpoint

AO-6 AO-6 High water Temperature Temperature +/- 3276.7 B10.0

temperature alarm
setpoint

AO-7 AO-7 For future use with

motion sensor—hotel
door switch timer in
minutes

AO-8 AO-8 Demand offset signal, Raw counts Temperature +/- 3276.7 B10.0
0.0-32.0 in counts;
forces heating and
cooling setpoints apart

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 161

Installation and Operations Guide | BACtalk Control Modules

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String

DI-1 BI-1 Fan Status: ON = Fan Binary Value

running, OFF = Fan
stopped

DI-2 BI-2 ON = Compressor 1 Binary Value

ON, reversing valve in
heating position; OFF
= Compressor OFF

DI-3 BI-3 ON = Compressor 1 Binary Value

ON, reversing valve in
cooling position, OFF =
Compressor OFF

DI-4 BI-4 (Applies with auxiliary Binary Value

module only) ON =
Compressor 2 ON,
reversing valve in
heating position; OFF
= Compressor 2 OFF

DI-5 BI-5 (Applies with auxiliary Binary Value

module only) ON =
Compressor 2 ON,
reversing valve in
cooling position; OFF =
Compressor 2 OFF

DI-6 BI-6 Auxiliary heat status, if Binary Value

present. ON = Auxiliary
heat ON; OFF =
Auxiliary heat OFF

DI-7 BI-7 Fresh air damper Binary Value

status, if present. ON =
Damper open, OFF =
Damper closed

DI-8 BI-8 Occupied status. ON = Binary Value

Unit in occupied mode,
OFF = Unit in
unoccupied mode

DI-9 BI-9 ON = Compressor 1 Binary Value

low temperature alarm

DI-10 BI-10 ON = Compressor 1 Binary Value

low pressure alarm
DI-11 BI-11 ON = Compressor 1 Binary Value
high pressure alarm

DI-12 BI-12 ON = Compressor 1 Binary Value

shut down due to
alarm condition

DI-13 BI-13 (Applies with auxiliary Binary Value

module only) ON =
Compressor 2 low
temperature alarm

162 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-14 BI-14 (Applies with auxiliary Binary Value
module only) ON =
Compressor 2 low
pressure alarm

DI-15 BI-15 (Applies with auxiliary Binary Value

module only) ON =
Compressor 2 high
pressure alarm

DI-16 BI-16 (Applies with auxiliary Binary Value

module only) ON =
Compressor 2 shut
down due to alarm
condition

DI-17 BI-17 ON = Brownout alarm Binary Value

DI-18 BI-18 ON = Condensate Binary Value

overflow alarm

DI-19 BI-19 ON = Low water Binary Value

temperature alarm

DI-20 BI-20 ON = High water Binary Value

temperature alarm

DI-21 BI-21 ON = High space Binary Value

temperature alarm
DI-22 BI-22 ON = Low space Binary Value
temperature alarm

DI-23 BI-23 ON = Attained Binary Value

temperature alarm

DI-24 BI-24 ON = Bad space Binary Value

temperature sensor
alarm

DI-25 BI-25 ON = Bad water Binary Value

temperature sensor
alarm

DI-26 BI-26 ON = Unit in self test Binary Value

mode

DI-27 BI-27 Loop flow request Binary Value

signal: ON = Heat
pump requesting water

DI-28 BI-28 Number of Binary Value

compressors: OFF =
Single compressor,
ON = Two
compressors (auxiliary
module present)

DI-29 BI-29 ON = Auxiliary heat Binary Value

selected for auxiliary
relay (DIP Switch 7
ON, DIP Switch 8 ON)

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 163

Installation and Operations Guide | BACtalk Control Modules

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DI-30 BI-30 ON = Fresh air damper Binary Value
selected for auxiliary
relay (DIP Switch 7
OFF, DIP Switch 8
ON)

DI-31 BI-31 Reserved for future Binary Value

use as hotel mode. ON
= Hotel mode selected

DI-32 BI-32 ON = After-hours timer Binary Value

ON

DO-1 BO-1 Occupied/unoccupied Binary Value

command. ON =
Occupied (day), OFF =
Unoccupied (night)
DO-2 BO-2 Heating allowed Binary Value
command. ON =
Heating allowed, OFF
= Heating disallowed
DO-3 BO-3 Cooling allowed Binary Value
command. ON =
Cooling allowed, OFF
= Cooling disallowed

DO-4 BO-4 Auxiliary heat allowed Binary Value

command. ON =
Auxiliary heating
allowed, OFF =
Auxiliary heating
disallowed

DO-5 BO-5 Fan allowed Binary Value

command. ON = Fan
operation allowed,
OFF = Fan operation
disallowed
DO-6 BO-6 Warmup mode Binary Value
command. ON =
Warmup mode, OFF =
Warmup mode inactive

DO-7 BO-7 Cooldown mode Binary Value

command. ON =
Cooldown mode, OFF
= Cooldown mode
inactive

DO-8 BO-8 Remote alarm reset; Binary Value

must transition from
OFF status to ON
status to reset
applicable alarms;
minimum ON time of 5
sec. recommended

164 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix F: TUX data point to BACnet object mappings

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-9 BO-9 Begin self-test mode Binary Value
command. Must
transition from OFF to
ON status to begin self
test, and must have
been OFF for a
minimum of 10 sec.

DO-10 BO-10 Reserved for future Binary Value

use as motion sensor
mode

DO-11 BO-11 OFF = English units, Binary Value

ON = Metric units

DO-12 BO-12 Off button feature; ON Binary Value

= Off button feature
enabled, OFF = Off
button feature disabled

DO-13 BO-13 Fan operation for Binary Value

occupied mode
heating; ON =
Continuous, OFF =
Cycles with
compressor operation
DO-14 BO-14 Fan operation for Binary Value
occupied mode
cooling; ON =
Continuous, OFF =
Cycles with
compressor operation
DO-15 BO-15 Fan operation during Binary Value
occupied mode
deadband; ON = Fan
operates during
deadband, OFF = Fan
OFF during deadband

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 165

Installation and Operations Guide | BACtalk Control Modules

Ta ble 73 TX-MQ-WSHP object mappings (Continued)

TUX BACnet TUX Data Default Gateway

Description Data Type BACnet Units
Point object Range String
DO-16 BO-16 Field service mode Binary Value
allowed command; ON
= Field service mode
allowed, OFF = Field
service mode
disallowed

DO-17 BO-17 (Applies only if DIP Binary Value

Switches 7 and 8 are
OFF) Auxiliary relay 1
control; ON = Auxiliary
relay ON, OFF =
Auxiliary relay OFF
DO-18 BO-18 (Applies only if Binary Value
auxiliary module
present) Auxiliary relay
2 control; ON =
Auxiliary relay 2 ON,
OFF = Auxiliary relay 2
OFF

DO-19 BO-19 (Applies only if Binary Value

auxiliary module
present) Auxiliary relay
3 control; ON =
Auxiliary relay 3 ON,
OFF = Auxiliary relay 3
OFF

166 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix G: Modbus function codes

Appendix G: Modbus function codes

The function codes used by the BCM-MDBS are provided here as a reference
only—you should not need them.

Function Code Description

01 Read Coil Status. Returns the status of a number of outputs in the
slave device. The BCM-MDBS always sets the number of coils read
as one. The data is either ON or OFF.

02 Read Input Status. Returns the status of a number of inputs in the

slave device. The BCM-MDBS always sets the number of inputs
read as one. The data is either ON or OFF.

03 Read Holding Registers. Returns the 16-bit data value of a number

of holding registers in the slave device. The BCM-MDBS always
sets the number of registers read as one.
NOTE: For floating point or long integer options, the BCM-MDBS
sets the number of registers written to two.

04 Read Input Registers. Returns the 16-bit data value of a number of

input registers in the slave device. The BCM-MDBS always sets the
number of inputs read as one.

05 Force Single Coil. Writes to a single coil (binary output). The data is
either ON or OFF.

06 Preset Single Register. Writes a 16-bit data value to a single data

register in the slave device.

15 Force Multiple Coils. Writes to a range of coils. The data is either ON

or OFF. The BCM-MDBS always sets the number of coils written to
as one. Some slaves will not accept function 05, so this function is
used instead if A or T is specified as the type.

16 Preset Multiple Registers. Writes multiple 16-bit data values to a

sequence of data registers in the slave device. The BCM-MDBS
always sets the number of register written to as one. (NOTE: For
floating point or long integer options, the BCM-MDBS sets the
number of registers written to two.)
Some slaves will not accept function code 06 so this function is used
instead if A or T is specified as the type.

20 Read General Reference. Returns the 16-bit data values of a

number of file-group references in the slave device. The BCM-
MDBS always sets the number of references read as one.

21 Write General Reference. Writes a number of 16-bit data values to a

group of file-group references in the slave device. The BCM-MDBS
always sets the number of references written as one.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 167

Installation and Operations Guide | BACtalk Control Modules

Appendix H: Error indicators

Connect to the BCM-MDBS using HyperTerminal to view diagnostic
information. For example, you can use the diagnostic information to verify that
valid messages are being sent and received, verify mappings are valid, and view
exceptions. Use option C on the Main Menu to view modbus diagnostic
information.

Modbus errors
The BCM-MDBS annunciates errors through the operator workstation and
through standard BACnet properties. Additionally, there are six diagnostic AVs
that can be placed directly on Envision for BACtalk displays or tracked in
Envision for BACtalk Trendlogs.

AV 10330 Modbus Requests Sent

AV 10331 Modbus Replies Received

AV 10332 Modbus Reply Timeouts

AV 10333 Modbus Serial Errors

AV 10334 Modbus Exceptions

AV 10335 Modbus Assigned Points

Modbus communication trace

The communication trace feature allows you to display the communication
stream in real-time and capture the data in a file to forward to Alerton technical
support. The captured communications can be invaluable in troubleshooting
modbus integration problems. Connect to the BCM-MDBS using
HyperTerminal and use the following procedures to start, stop, pause, or save a
trace.

X To start a trace
• In HyperTerminal, select option T on the Modbus Diagnostic
Information screen.

168 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix H: Error indicators

N o t e The message “Trace mode is now ON…” is displayed and

modbus messages (byte-by-bye and in hexadecimal notation) scroll
onto the screen.
Messages from the BCM-MDBS are preceded by the characters “-->”
Messages to the BCM-MDBS are preceded by the characters “<--”

X To save the trace to a file

1. On the Transfer menu, select Capture Text.

2. Type a name and select a location for the file.

3. Click Start.

4. When you have captured all of the data you need, select Capture Text >
Stop on the Transfer menu.

X To pause or stop a trace

• Press the Esc or Q key on the Envision for BACtalk workstation
keyboard.
N o t e The message “Trace mode is now OFF … Press ENTER to
return to menu” is displayed.

BACnet error indications

The AV and BV objects in the BCM-MDBS use the standard BACnet reliability
property to reflect their current status. If an AV or BV has a valid Modbus
description string mapping and is communicating correctly with a Modbus unit,
the reliability property reads NO_FAULT_DETECTED. If the description string
is invalid or the Modbus unit is not responding for any reason, the reliability
property reads UNRELIABLE_OTHER. In this instance, the BACnet status-
flags property for that AV or BV also reads FAULT.

Note You can use the reliability property to generate BACnet alarm
notifications. See your BACtalk operator workstation software manual for
instructions on setting up alarm notifications.

Operator workstation error indications

The BCM-MDBS provides visual feedback of errors. As each description string
is mapped and assigned, the BCM-MDBS verifies the validity of the string. If
the string is invalid, the BCM-MDBS adds an error indicator to the beginning of
the description string to alert the user. These error indicators are described in the
following table.

Error Indicator Description

Error 1, Slave Indicates the string contains a slave address that is either 0
(zero)—which is the Modbus broadcast address—or a value
above the Modbus slave address limit of 247.

Error 2, Reference Type Indicates the reference number is either invalid or is incorrect
for the selected message type. For example, you cannot write
to a reference type 1 or 3.

Error 3, T or A not The T or A options are not allowed with Type 0.

allowed

Error 4, Reg/Coil Indicates the register/coil number is invalid.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 169

Installation and Operations Guide | BACtalk Control Modules

Error Indicator Description

Error 5, File Group Indicates the file/group number is invalid.

Error 6, Float not allowed Indicates the floating point option is not allowed. The floating
point option is only allowed with reference types 3 or 4.

Error 7, Long not allowed Indicates the long integer option is not allowed. The long
integer option is only allowed with reference types 3 or 4.

Error 8, Bit Unpack Indicates the bit unpack field contains an invalid bit mask.

Note If the Operation field does not begin with I, O, A, W, or T, or if the 2nd
character is not a comma, it is assumed that the string is not a Modbus mapping
and is ignored.

Modbus exception codes

The BCM-MDBS provides visual feedback of errors through modbus
exceptions. Modbus exceptions are error messages returned by connected
modbus equipment when a request contained some kind of error. The exception
code indicates the type of error. For example, an invalid register address or data
that is out of range for the modbus device. These exceptions are described in the
following table.

Exception Description
01 Illegal Function The modbus message contains a function code not supported
by the modbus unit.

02 Illegal Data Address The data address received in a modbus request is not an
allowable address for the modbus unit.

03 Illegal Data Value The value received in a data field is not an allowable value for
the modbus unit.

04 Slave Device Failure An unrecoverable error occurred while the modbus unit was
attempting to perform the requested action.

05 Acknowledge The modbus unit has accepted and is processing the request
but it will take a long time.

06 Slave Device Busy The modbus unit is engaged in processing a long-duration

program request.

07 Negative Ack The modbus unit cannot perform the program function
requested.
08 Memory Parity The modbus unit detected a parity error in the memory.

Using the aler-diagnostics property

You can use aler-diagnostics to view diagnostic reports returned by the BCM-
MDBS or FLG MODBUS.

To view reports using aler-diagnostics

Place a read-only item on a data display and set the following properties:

BCM MODBUS object = program, instance = 0, property = aler-diagnostics

FLG MODBUS object = device, property = aler-diagnostics

170 © Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008

 Installation and Operations Guide | Appendix H: Error indicators

The following fields will be displayed:

Modbus Port Shows which hardware port is in use for Modbus interface,
the protocol used, the number of data bits, the parity, and the
number of stop bits.

Baud Rate Shows the baud rate the BCM-MDBS is using.

Protocol Choice (RTU/ Shows the protocol the BCM-MDBS is using.

ASCII)

Serial Protocol Shows the serial protocol parameters.

Parameters

Assigned points The number of valid point data mappings detected.

Xmit messages The number of Modbus requests transmitted.

This is useful to determine whether the BCM-MDBS is
sending messages.

Rcvd messages The number of Modbus replies received.

This is useful to determine whether the BCM-MDBS is
responding to messages.

No replies The number of transmitted requests that were not answered.

Exceptions The number of transmitted requests that were answered with

exception messages.
Modbus exceptions indicate an incorrect mapping or data
values that are out of range of Modbus device specifications.

Serial errors The number of serial interface errors.

Serial errors indicate hardware (wiring/shielding/ground) or
protocol assignment problems.

Reply Timeout Shows the timeout settings defined in the BCM-MDBS.

Poll Delay Shows the poll delay defined in the BCM-MDBS.

Enable status of multiple Shows whether multiple register requests are enabled for the
register requests BCM-MDBS.

© Honeywell. All Rights Reserved. LTBT-TM-BCMIOG Rev. 0008 171