Installation and Startup Guide

Envision for BACtalk

© Honeywell LTBT-TM-ADMIN30 Rev. 05

User agreement and limited warranty
IMPORTANT - PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION (DEFINED BELOW) IS
SUBJECT TO LICENSE RESTRICTIONS AND LIMITED WARRANTY. CAREFULLY READ THIS AGREEMENT BEFORE USING ALERTON PRODUCTS, SOFTWARE,
FIRMWARE AND/OR DOCUMENTATION.
This is a legal "Agreement," concerning the purchase of Products and use of Software, Firmware and/or Documentation, between you, the "User" (either individually or as an
authorized representative of the company that is purchasing, has purchased, or is using the Products, Software, Firmware or Documentation) and Honeywell, 6670 - 185th
Avenue NE, Redmond, Washington 98052 USA. ("Honeywell").
PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION INDICATES USER'S COMPLETE AND
UNCONDITIONAL ACCEPTANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
Honeywell provides Alerton products ("Products"), software programs ("Software"), firmware, e.g., protocols, software program code, device drivers and related hardware
("Firmware") and accompanying documentation ("Documentation") and grants a non-exclusive and non-transferable license ("License") to User to use the Software and the
Firmware only on the following terms and conditions. Taken together, Products, licensed Software, licensed Firmware and accompanying Documentation are collectively
defined as "Alerton Product(s)" in this Agreement.
1. Copyright. The Software, Firmware and Documentation are copyrighted and protected by United States copyright laws and international treaty provisions and laws, contain
valuable proprietary products, information and trade secrets, and shall remain the property of Honeywell. User may not and shall not copy or otherwise reproduce or make
available to any other party any part or all of the Software, Firmware or Documentation nor decompile, disassemble, reverse engineer, manufacture or modify any portion of
the Products, Software, Firmware, Documentation or any portion of the same for any purpose or otherwise attempt to determine the underlying source code of the Software or
Firmware or permit any such action; provided however, User may either (a) make one (1) copy of the Software solely for backup or archival purposes, or (b) transfer one (1)
image of the Software to a single hard disk, CD or other comparable media, provided User keeps the original solely for backup or archival purposes.
2. License. User is hereby licensed to use one (1) copy of the Software for User's own use in operating the Products. User may not rent, lease or otherwise assign or transfer
all or any part of the Software, Firmware or Documentation. In addition, User may not sublicense, assign or transfer this License or Agreement, or any part thereof. Any
attempt to do so shall terminate this License and User's right to use the Software and Firmware and shall subject User to liability for damages to Honeywell. LICENSING TO
USER OF THE SOFTWARE AND FIRMWARE COMMENCES WHEN USER USES THE SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION.
3. Copies, Modification or Merger. Except as specifically set forth in Paragraph 1, User may not copy, modify, transfer all or any portion of the Software, Firmware or Documen-
tation or merge it or them into another program, unless expressly authorized in advance in writing by Honeywell. User must, as a condition of this License, reproduce and
include the identifying marks, copyright and proprietary notices on any permitted copy of the Software, Firmware and Documentation. "Copies" shall include, without limitation,
any complete or partial duplication on any media, adaptations, translations, compilations, partial copies within modifications, mergers with other material from whatever source
and updated works. User will use its best efforts to prevent any unauthorized copying or other activity with respect to the Software, Firmware and Documentation.
4. Third-Party Beneficiary. For any software or other technology under this Agreement licensed by Honeywell from Microsoft( or other licensors, Microsoft or the applicable
licensor is a third party beneficiary of this Agreement with the right to enforce the obligations set forth in this Agreement.
5. Warranty. Honeywell warrants Honeywell manufactured or produced Alerton Products to be materially free from defects and to substantially conform to Honeywell's pub-
lished specifications for a period of twenty-four (24) months from date of shipment from Honeywell (the "Product Warranty Period"). This entire Section 5 is defined as the
"Warranty."
Honeywell also warrants Alerton Products that it has previously repaired or replaced for the greater of ninety (90) days from the date of their shipment from Honeywell or the
remainder of the Product Warranty Period of the originally shipped Alerton Product (the "Repair/Replacement Warranty Period").
During the Product Warranty or Repair/Replacement Warranty Period, Honeywell will repair or replace the applicable Alerton Products without charge and will add applicable
engineering changes and upgrades.
This Warranty only applies to defective materials and workmanship of Alerton Products and excludes defects that result from misuse, neglect, improper installation, unauthor-
ized repair or alteration, damage during or after shipping, accident and/or misapplication of such products. This Warranty does not apply to parts, equipment, software, firm-
ware, components, documentation or any other item that Honeywell does not manufacture or produce. This Warranty is also voided by removal or alteration of Alerton Product
identification labels.
Honeywell's sole responsibility with respect to Alerton Products shall be, within the applicable Product Warranty Period, to furnish a replacement Alerton Product (FOB fac-
tory) or, at the option of Honeywell, to repair and return (FOB Factory) the defective Alerton Product. HONEYWELL HEREBY EXCLUDES ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES WHATSOEVER WITH RESPECT TO
ALERTON PRODUCTS. In no event shall Honeywell be liable for personal injury, loss of profit, loss of production, loss of business or goodwill, business interruption, loss of
business information or data, loss due to delays, any other pecuniary loss, any cost or liability of Users or any other parties, to themselves or to others, increased or uncovered
operating or fixed costs, inefficiency, or any other special, exemplary, consequential, incidental, indirect or remote damages in any manner, directly or indirectly, related to
design, manufacturing, supply, installation or use of, or inability to use, Alerton Products, or any other act or failure to act by Honeywell or its agents or contractors.
HONEYWELL MAKES NO CLAIMS OR WARRANTIES WITH RESPECT TO THE SOFTWARE OR THE FIRMWARE AND SPECIFICALLY DISCLAIMS ANY IMPLIED WAR-
RANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND EXPRESS OR IMPLIED WARRANTIES THAT THE OPERATION OF THE SOFT-
WARE OR FIRMWARE OR ANY PORTION THEREOF WILL BE INTERRUPTION OR ERROR FREE. Notwithstanding anything to the contrary contained in this Warranty,
Honeywell shall not be liable to Users or any other parties for any damages, including, but not limited to consequential, incidental, indirect, special, exemplary remote or pecu-
niary damages and any stated or express warranties set forth in this warranty are in lieu of all obligations or liability for any damages arising out of or in connection with the use
or performance of, or inability to use, Alerton Products and the licensed Software and Firmware.
User's exclusive remedy and Honeywell's entire liability arising from or in connection with the Alerton Products, Software, Firmware, Documentation and/or this License and
Agreement (including, without limitation, any breach of any warranty, express or implied) shall be, at Honeywell's option, the repair or replacement of the Products or Software
or Firmware as applicable, as stated above. ACCORDINGLY, HONEYWELL AND ITS DESIGNATED DEALERS AND THEIR DESIGNATED ASSOCIATE DEALERS HAVE
EXCLUDED AND DISCLAIM ANY AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER WARRAN-
TIES, EXPRESS OR IMPLIED, WHATSOEVER, WITH RESPECT TO THE PRODUCTS, THE SOFTWARE, THE FIRMWARE, THE DOCUMENTATION AND/OR THE
LICENSE. USER HEREBY ACKNOWLEDGES THE SAME.
6. Remedies of Honeywell. IF USER BREACHES THIS AGREEMENT, USER'S LICENSE HEREUNDER SHALL BE AUTOMATICALLY TERMINATED. Upon termination,
User shall return the Software, Firmware and all Documentation to Honeywell and destroy any copies of the Software, Firmware and the Documentation or any portions
thereof which have not been returned to Honeywell, including copies resident on electronic or digital media. If User breaches this Agreement, Honeywell shall be entitled to all
damages suffered by Honeywell resulting from such breach and Honeywell shall be entitled to equitable and injunctive relief in addition to all other remedies at law. In this
regard, User acknowledges that its breach of any provision of this Agreement will cause Honeywell immediate and irreparable injury for which there are inadequate remedies
at law. The prevailing party in any dispute concerning this Agreement shall be entitled to the costs of collection and enforcement, including but not limited to reasonable attor-
neys' fees, court costs and all necessary expenses, regardless of whether litigation is commenced.
7. Export. Alerton Products are subject to regulation by local laws and United States government agencies, which prohibit export or diversion of certain products, information
about the products, and direct products of the products to certain countries and certain persons. User agrees that User will not export in any manner any Alerton Product or
direct product of Alerton Product, without first obtaining all necessary approval from appropriate local and United States government agencies.
8. RESTRICTED RIGHTS NOTICE. Alerton Products, Software, Firmware and Documentation have been developed entirely at private expense and are commercially pro-
vided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions pursuant to
DFARS 227.72013 (October 1988) and DFARS 52.227-19 (June 1987), as amended and as applicable. Manufacturer, licensor and publisher is Honeywell, 6670 - 185th Ave-
nue NE, Redmond, Washington 98052 USA.
9. Statute of Limitations. No action for any breach of a warranty, if any, deemed or actual, may be commenced more than one (1) year following the expiration of such warranty.
10. Other. User further agrees that this Agreement is the complete and exclusive statement of the agreement between User and Honeywell and supersedes any proposal or
prior agreement or any other communications between Honeywell or any of its representatives and User relating to the use of the Software, Firmware, Documentation and
purchase of the Products. This Agreement may only be modified by a physically signed writing between User and Honeywell. Waiver of terms or excuse of breach must be in
writing and shall not constitute subsequent consent, waiver or excuse. If any provision of this Agreement is finally determined to be unenforceable, the remaining provisions
shall remain in effect. The laws of the State of Washington and the United States, including U.S. copyright laws, shall govern this Agreement. Venue in the event of any suit,
proceeding or claim shall be in the courts located in King County, Washington, USA. If User has any questions regarding this Agreement, User may contact Honeywell by writ-
ing Honeywell at the above address.
This Agreement shall inure to the benefit of and be binding upon the parties and their successors, administrators, heirs and permitted assigns. Notwithstanding any termina-
tion of this Agreement and not in limitation of any other provision of this Agreement, User shall specifically continue to be fully obligated to comply with all of the requirements
of paragraphs one (1) through four (4), as if the Agreement were not terminated and all remedy provisions hereunder shall apply to any breach of such obligations.

2 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Contents

Contents
About Envision for BACtalk and this guide 5
What’s new? 5
Using this guide 7
For more BACtalk information 9
For SQL Server information 9
Installation and upgrade quick steps 10
Important considerations: read this first 10
Quick steps–new Envision for BACtalk installation 12
Quick steps–upgrading single operator workstation sites 13
Quick steps–upgrading client/server sites 15
Quick steps–upgrading stand-alone controller sites 17
Installation detail 18
Documenting address numbering 18
Installing Visio 19
Compacting a BACtalk job database 19
Backing up BACtalk job data 20
Running the Envision for BACtalk installation program 21
Installing the Alerton/Honeywell BACtalk Driver 21
Configuring the Local Administrator 23
Installing the BACtalk software license key 24
Upgrading real-time operating code (ROC) 27
Client/server setup 29
Setting up a client/server relationship 29
Configuring servers and clients for a NAT environment 32
Setting up a large wide area network (WAN) 33
Connecting sites running different software versions 35
Scenario 1: Temporary connections 35
Scenario 2: Remote alarm logging 35
Scenario 3: Remote connections for point data exchange and
log gathering 36
Job setup and engineering 37
Local Administrator security scheme and directory structure 37
Saving displays and DDC 38
Logging in for the first time 40
Creating a default job 40
Using BACtalk for Windows job data in Envision for BACtalk 41
Verifying General System Setup 46
Creating user profiles 47
Understanding Device Manager 50
Defining device profiles 51
Populating the Device Manager table 61
Configuring controllers remotely 64
Renumbering VLCs 72
Assigning Alerton Standard applications to controllers 74
Envision for BACtalk v3.0 system requirements 76
Recommended system specifications 76
Minimum system requirements 77
BACtalk software license keys 78
Network key behavior 80
Remote site key behavior 80
Host device and automation feature compatibility 80
Sharing data displays in a client/server network 81
Verifying the client/server relationship 83

© Honeywell LTBT-TM-ADMIN30 Rev. 05 3

Installation and Startup Guide | Envision for BACtalk

4 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | About Envision for BACtalk and this guide

About Envision for BACtalk and this guide

Envision for BACtalk is an operator workstation software package for BACnet-
compliant systems. Envision, which runs on a Windows personal computer,
enables BACtalk operators and developers to monitor and control BACnet-
compliant devices in their building automation system (BAS). The Envision for
BACtalk operator workstation communicates with BACnet-compliant field
equipment using BACnet over local area networks (LANs) and wide area
networks (WANs).

From the Envision for BACtalk operator workstation, operators can access any
BAS data made available on the network using the BACnet protocol standard—
even if it originates in another manufacturer’s device. Developers can use the
Envision for BACtalk operator workstation to program custom direct digital
control (DDC) sequences that run locally in BACtalk controllers. They can also
configure other site operational details.

In addition to the Envision for BACtalk operator workstation, Alerton offers a

complete line of BACnet-compliant equipment controllers (VLCs) and global
controllers (BACtalk control modules). All BACtalk products exchange
messages in compliance with the BACnet protocol and communicate on LANs
as specified in ASHRAE Standard 135-2001, BACnet.

What’s new?
Envision for BACtalk v3.0 supports the following added features and
functionality:

• New Energy Dashboard Energy awareness dashboard Visually

provides energy consumption data on an easy-to-understand dashboard
display using a web browser. This educational dashboard shows energy
consumption compared to historical or other building data and visually
displays it. Studies show visually presenting this information can reduce
energy use by more than 5%. It integrates real-time building resource
data with Envision for BACtalk. The user-friendly design meets site
needs with customizable displays. Dashboard controls can be easily
navigated using a touchscreen monitor. This dashboard is ideal for
displaying in a lobby or other high-traffic area so visitors and other
occupants can see how energy is being used in the building.
• BACtalk Software License Key Eliminates the hardware key.
• Energy Logs Energy log meter data is now updated at 15-minute
intervals. Envision for BACtalk polls trendlogs assigned as meters every
15 minutes to display real-time data on the new energy dashboard.
• Enhanced Reporting New reports easily gather site data to be used as
site documentation. Device settings can also be exported in report
format for future use during troubleshooting. Now supports Crystal
Reports 2008 RPT file format. When a file is saved, the generated report
uses a system-specified filename. Enhanced Reporting is a mechanism
that allows the installation of new reports without a new release of

© Honeywell LTBT-TM-ADMIN30 Rev. 05 5

Installation and Startup Guide | Envision for BACtalk

BACtalk. Version 3.0 ships with the new Trendlog List Report (Add-ins
> Setup Reports > Trendlog).
• Multiple Trendlog Viewer Now supports wild card searches for
improved search results.
• VisualLogic v3.0 Enhanced user interface and toolkit. Compatible with
existing DDC drawings. Use with Visio 2007 or Visio 2010. Visio
2010* recommended. New features include:
• New Toolkit combines all tools into a dockable window that supports
auto-hide and is available on every drawing page—reduces DDC
development and testing time.
• New Compare feature allows you to compare two DDC drawings and
print a report of the differences—saving critical time for troubleshooting
warranty issues and service calls.
• New Auto Sequence DDC feature automatically sequences DDC as you
place functions on the drawing—saving DDC development time
• New Auto Connect DDC feature automatically connects functions as
you place functions on the drawing —saving time in developing DDC
• New Auto Edit DDC feature automatically opens function for editing
parameters when you place functions on the drawing—saving DDC
development time
• New Auto Propagate DDC feature automatically propagates parameters
when you connect DDC functions on a drawing—saving DDC
development time
• New Find and Replace feature saves DDC editing time
• Cross Reference Table can be sorted by columns—saving DDC editing
and troubleshooting time
• Cross Reference Table supports Object Name property —saving DDC
editing and troubleshooting time (BD6 DDC file only)
• Cross Reference Table object description column displays the point
description and the point type-instance. The format is <BACnet point
description property> (<point type-instance>). For example, Space

6 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | About Envision for BACtalk and this guide

Temp (AI-0)—saving DDC editing and troubleshooting time (BD4

DDC file only)
• Cross-Reference Table automatically updates after editing a DDC
function—saving DDC development time
• Send DDC and Save DDC Options can now be saved for each
drawing—saving DDC development and commissioning time
• Error checking now delineates between warnings and errors—saving
DDC development time and providing an option to report multiple
writes in the Options dialog box
• Statistics displays the size of DDC comments separately from geometric
info (BD6 DDC only)—saving DDC development time
• New enhanced VLC/VLCA Device Settings dialog box
• Propagate and update all drawing tabs with I/O references from
connected DDC functions page—saving DDC development and editing
time
• Collect point descriptors from drawing I/O tabs and populate Point
Setup descriptions page—saving DDC development and editing time
• Send point descriptors from Point Setup and populate drawing I/O tabs
page—saving DDC development and editing time
• Export all point setup parameters to Excel spreadsheet—saves time in
maintaining a library of applications
• Import all point setup parameters from Excel spreadsheet—saving DDC
development time
• Export and Import Microset Field Service Setup data (BD6 DDC Only)
• Visio 2010*
• Ribbon toolbar buttons repeat all menu functionality for convenience.
• Customize the ribbon toolbar to align tabs and save time during device
configuration.
As with all upgrades, reading and following these instructions will substantially
ease the upgrade. You will also find detailed background and conceptual
information about all Envision features in the Envision for BACtalk Operator’s
Manual (LTBT-OP-EBT). The online Help included with the software provides
procedural and context-sensitive information about each feature.

Using this guide

This guide provides critical information and step-by-step instructions for those
who will install a new BACtalk system or upgrade from an earlier version of
BACtalk operator workstation software to Envision for BACtalk. Perform
upgrade and install tasks in the order presented to ensure smooth installation and
sound system operation. Alerton dealers should perform the upgrade or
installation.

Note If you are running BACtalk for Windows v3.02 or v2.33, you must first
upgrade to v3.1x (available from Alerton) before attempting to upgrade to
Envision for BACtalk v3.0. See “Important considerations: read this first” on
page 10 for more information. The BACtalk database structure was changed for

© Honeywell LTBT-TM-ADMIN30 Rev. 05 7

Installation and Startup Guide | Envision for BACtalk

Envision for BACtalk versions 2.5, 2.6 and 3.0. Once a database is converted it
cannot be converted back.

Quick steps
After you identify the type of installation or upgrade you need to perform, start
with the quick steps for your installation type. Quick steps provide an overview
of the procedures you need to follow, with references to detailed instructions
later in this guide.

Installation detail
It is highly recommended that you read the detailed instructions. If you’re unsure
how to perform an operation, the detailed installation instructions will help.
Even if you’re an expert user who is familiar with BACtalk systems, you will
benefit from reading the detailed instructions.

Job setup and engineering

This section provides information about getting a site up and running, whether
you are performing an upgrade or a first-time BACtalk system installation. It
includes information about setting up new jobs and importing existing job
information from earlier versions of BACtalk software. You will also find
helpful information about defining devices and using Envision’s Device
Manager. Important information about pre-planning your engineering to
successfully merge older job data with Envision for BACtalk (Conventional and
SQL Server databases) is also included.

Appendix
The appendix contains additional background and reference information on
topics including system requirements, software license keys, feature
compatibility, and sharing data displays across a network.

Installing and upgrading Envision for BACtalk

Locate the information for your type of installation or upgrade:

Note Upgrading from Envision for BACtalk v2.x to v2.6 or later with
Enterprise support (SQL Server) may take a long time due to the database
conversion.

• Installing Envision for BACtalk at a new site (page 12)

• Upgrading single operator workstation sites (page 13)
• Upgrading client/server sites (page 15)
• Upgrading stand-alone controller sites (page 17)

Installing and accessing the Energy Dashboard

This section provides information about activating the Dashboard, accessing the
Dashboard Configurator, and accessing the Dashboard itself. While BACtalk is
running, see the Envision for BACtalk online help for more details about
configuring and working with Dashboard pages.

8 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | About Envision for BACtalk and this guide

For more BACtalk information

Several other documents are available for information about Envision for
BACtalk and BACtalk system architecture. Find these technical documents and
knowledge base articles (KBAs) on the Alerton Support Network (ASN).
Ta ble 1 Where to find answers in the Envision for BACtalk documentation set

Installation & Startup Operator’s Programmer’s Guide Display

Online Help
Guide (this guide) Manual & Reference Developer’s Guide
How do I install the What does a I need detailed I need an overview of the How do I get started
Envision for BACtalk particular feature do? information about concepts behind DDC designing data
software? Why would I use this using the Envision for programming. displays?
feature? BACtalk software.

How do I configure the What do I need to I need detailed What are some of the Are there some general
Envision for BACtalk know before I set up information about a considerations I need to guidelines or tips on
software? and use this feature? specific dialog box or think about before I start good data display
window. creating a DDC program? design?

How do I set up and How do I change the I need some help What do I need to know What are the steps for
engineer a job? settings for a feature figuring out what to before I begin using creating a new data
if it’s not working as I enter in this field on a VisualLogic? display?
expected? dialog box.

How do I enter or change I need an example of What are the steps What are BACnet objects How do I use Alerton
information in Device how I might use this for using a particular and properties? templates when
Manager? feature. feature? creating new displays?

How do I send What calculations is What does this term I need detailed How do I edit an
information or a DDC the system making mean? information about a existing display?
program to a controller? when I use this specific DDC function.
feature?

For SQL Server information

See the “SQL Server Guidelines” (LTBT-TM-SQL) manual for information
about SQL Server training resources.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 9

Installation and Startup Guide | Envision for BACtalk

Installation and upgrade quick steps

This section provides warnings and step-by-step instructions for those who will
install Envision for BACtalk. Perform all tasks in the order presented to ensure
smooth installation and sound system operation. Alerton dealers should perform
the upgrade or installation.

Because of the unique flexibility of Envision for BACtalk systems, there may be
portions of this guide that are not applicable to systems you deal with, as well as
portions that are not specifically detailed here. Use the quick steps in this section
to find information that applies to your installation.

Before you start the installation process, make sure you have the following:

• Envision for BACtalk v3.0 DVD

• BACtalk software license key
• Internet connection 
(IMPORTANT! See “Without an Internet connection” on page 26)
• Information about the site

Important considerations: read this first

Review the following information carefully to determine if any of these
considerations apply to your installation.

CAUTION Significant changes were made to the database structure for

Envision for BACtalk 2.5, 2.6, and 3.0 to improve system performance,
reliability, stability and security. For this reason, once a job is upgraded to 2.5 or
later, you cannot convert it back to an earlier version. Back up the current job
before upgrading.

CAUTION It is recommended that you compact the databases prior to backup.

For more information, see “Compacting a BACtalk job database” on page 19
and “Backing up BACtalk job data” on page 20.

CAUTION Upgrade the server first before upgrading the clients to avoid
locking users out from the server. Clients with newer BACtalk software cannot
log into earlier BACtalk servers.

CAUTION The Local Administrator user profile must be configured during the
initial launch of Envision for BACtalk on each workstation. It cannot be set up
later. Local Administrator provides access to special tasks requiring higher
privileges at the local workstation. If you lose the LocalAdministrator password,
you must reinstall Envision for BACtalk and set up a new LocalAdministrator
user ID. Vista users must run Envision for BACtalk as an Administrator to do
this step.

CAUTION Some controller ROC files must be updated to fully use Envision
for BACtalk features and functionality. See the Readme for a complete list of
new ROC files or visit the version histories on the ROCs download page on the
ASN at http://asn.alerton.com for a complete summary of ROC releases.

CAUTION If you install Envision for BACtalk on a computer running

Windows 2000, do not use the operating system’s standby or hibernate mode.

10 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation and upgrade quick steps

The system will not communicate and the protocol driver does not restart. You
must shut down and restart Envision for BACtalk.

CAUTION Significant changes were made between BACtalk for Windows

v3.02 and v3.1x. If you are running BACtalk for Windows v3.02 or v2.33, you
must first upgrade to v3.1x before attempting to upgrade to Envision for
BACtalk. For upgrade instructions, see the BACtalk Version 3.10 Upgrade
Installation Guide (LTBT-V310UPGRADE.pdf).

CAUTION Do not mix versions of BACtalk. Envision for BACtalk and

BACtalk for Windows v3.1x are not 100% compatible. Whenever possible,
connect workstations running the same version of BACtalk operator workstation
software. If you must connect workstations running different versions, some
unexpected errors may occur. In particular, do not edit schedules or make
changes in Device Manager. BACtalk for Windows v3.1x does not support
Envision for BACtalk features, including all the automation features that operate
according to schedules.

CAUTION If running BACtalk for Windows v3.1x, do not dial into a stand-
alone controller site without first saving and backing up data in BACtalk for
Windows v3.1x format.

Note Envision for BACtalk automatically installs some pre-requisites, if not

already installed. These include: Microsoft .Net 3.5 SP 1, Microsoft .Net 4.0
Client, Microsoft Data Access Components (MDAC) 2.8, Microsoft Office PIA
2007/2010, Microsoft SQL Server Native Client, Microsoft VSTO 2010
Runtime, Microsoft Silverlight, Windows Installer 4.5.

Note Depending on the size of the job, Envision for BACtalk v3.0 may take a
long time (possibly several hours) to initially launch when upgrading from an
earlier version due to a database conversion operation. Envision should launch
faster the next time it is started.

Note Upgrades on some operating systems may require you to update the
BACtalk communications driver. For more information, see “Installing the
Alerton/Honeywell BACtalk Driver” on page 21.

Note You must log in as an administrator to run Envision for BACtalk as a

service. Install the “Alerton/Honeywell BACtalk Driver 3.0,” start up the service
and then select the desired NIC.

Note Sharing data displays across slow networks is not recommended. It can
severely impact network performance. It is recommended that you copy job
displays and templates to client workstations. See “Client/server setup” on
page 29 for more detailed information.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 11

Installation and Startup Guide | Envision for BACtalk

Quick steps–new Envision for BACtalk installation

If this is a new installation where earlier versions of BACtalk operator
workstation software have not been installed, follow these steps.

Task See
1 Document the address-numbering scheme on installation drawings. page 18
2 Install Visio 2007 or Visio 2010 if you plan to use VisualLogic. See page 19
page 76 for system requirements required to run Visio and
VisualLogic.
3 Run setup.exe from the Envision for BACtalk DVD. page 21
Note: Default installation location is C:\Alerton\BACtalk\3.0.
4 Verify that the Alerton/Honeywell BACtalk driver did install. page 21

5 Start Envision for BACtalk and set up the Local Administrator’s page 23
password.

6 Log in with “LocalAdministrator” and the password you just created. page 23

7 Enter the BACtalk software license key. page 24

8 Create the default job, and then create the site key. page 40

9 Create the Default User profile.  page 47

IMPORTANT! Required to launch the Dashboard.

10 Perform General System Setup. page 46

• On the Identification tab, set the device instance, device name and
device description for the operator workstation.
• On the Network tab, verify the Primary Ethernet adapter.
• Verify that either the Ethernet BACnet Protocol or Annex J 
BACnet/IP is enabled. Caution: DO NOT enable both.
• Verify the Client/Server Communications Protocol setting.
• Configure the site BACtalk client/server and host device.
• Configure the database options for Enterprise servers.

11 Restart Envision for BACtalk and log in to the default rep/job created page 40
in the preceding step.

12 Create user profiles, including security level, start display, device page 47
access and privileges, and group membership.

13 Set up the Device Manager table and send all data to devices. page 50

14 Perform client/server setup, if necessary. page 29

15 Enable the Require client/server authentication option on the --

Network tab in General System Setup to provide secure
communication capabilities between all clients and the BACtalk the
server.

16 If applicable, configure the Alerton Energy Dashboard. See the

Envision for
BACtalk
Operator’s
Manual

12 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation and upgrade quick steps

Quick steps–upgrading single operator workstation sites

Task See
1 Save Point Data and Device Configuration in Device Manager. page 63

2 Back up the existing job. page 19

3 Close the current BACtalk software. page 20

4 Compact the existing job database. --
Note: Shut down BACtalk before compacting the database.
5 Run setup.exe from the Envision for BACtalk DVD. page 21
Note: Default installation location is C:\Alerton\BACtalk\3.0. This is
a different location than earlier BACtalk default locations. Caution:
Do not overwrite earlier BACtalk versions unless you no longer
need them.

6 Enter the BACtalk software license key. page 24

7 Start Envision for BACtalk. page 37

8 Configure the Default User in General System Setup.

IMPORTANT! Only the Default User can access the Dashboard.

9 If necessary, restore the job you backed up in step 2. page 41

10 Restart Envision for BACtalk, and log into the job. --

11 Verify General System Setup. page 46

• On the Identification tab, set the device instance, device name and
device description for the operator workstation.
• On the Network tab, verify the Primary Ethernet adapter.
• Verify that either the Ethernet BACnet Protocol or Annex J
BACnet/IP is enabled. Caution: Do not enable both.
• Verify the Client/Server Communications Protocol setting.
• Configure the site BACtalk client/server and host device.
• Configure the database options for Enterprise servers.
• If converting to an Enterprise server, restart BACtalk to convert the
databases from Access/Jet to SQL Server format.

12 Upgrade the ROC file in all host devices. page 27

13 Verify the Device Manager table and send all data to devices. page 50
• Verify that this computer’s device instance is listed in the table.
• Verify that all known devices connected to the same network are
listed in the table.
• IMPORTANT! Verify that the appropriate device capabilities are
selected, especially for host devices, on the Capabilities tab
(BACtalk > Device Manager > Add/Edit > Capabilities). Correctly
set device capabilities by polling by device.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 13

Installation and Startup Guide | Envision for BACtalk

Task See
14 Verify that all objects (for example, trendlogs and schedules) were --
successfully sent to all host devices.

15 Update BACtalk user profiles to add a start display, authorized page 47

period, device access and privileges, and group membership(s),
and log into Envision for BACtalk again to access these new
features.

16 If it is no longer needed, you can remove older versions of BACtalk --

through the Control Panel.

17 If applicable, configure the Alerton Energy Dashboard. See the

Envision for
BACtalk
Operator’s
Manual

14 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation and upgrade quick steps

Quick steps–upgrading client/server sites

WARN ING Understand client/server setup in Envision for BACtalk. If you
upgrade a site with more than one operator workstation on site, confirm that the
site is configured correctly. Incorrect configuration can lead to data corruption.
For more information, see “Client/server setup” on page 29.

Steps to upgrade the server

Task See
1 Save Point Data and Device Configuration in Device Manager on the page 63
server.

2 Back up the existing job on the server. page 19

3 Close BACtalk on all operator workstations, if possible. (See the page 20

warning at the beginning of this section.)

4 Compact the existing job database on the server. --

5 Run setup.exe from the Envision for BACtalk DVD. page 21

Note: Default installation location is C:\Alerton\BACtalk\3.0. This is a
different location than the BACtalk for Windows default location.
Caution: Do not overwrite BACtalk for Windows unless you no
longer need it.

6 Enter the BACtalk software license key. page 24

7 If necessary, restore the job you backed up in step 2. page 42

Note: If Step 8 is not completed, the BACtalk system displays a
prompt asking if you want to import BACtalk.INI. If you click Yes, all
your password text boxes are greyed out because you are attempting
to sign into a non-existent Rep job.

8 Start Envision for BACtalk, set the Local Administrator’s password page 23
and log in to the job for this site.

9 Verify General System Setup. page 46

• Set the device instance for the operator workstation on the
Identification tab.
• Verify the Primary Ethernet adapter on the Network tab.
• Verify that either the Ethernet BACnet Protocol or Annex J 
BACnet/IP is enabled on the Network tab. Caution: DO NOT
enable both.
• Identify this operator workstation as the server, using Site
Configuration on the Network tab.
• After all clients have been upgraded, verify that “Require client/
server authentication” is checked on the server’s Network tab to
enable secure communication between all BACtalk workstations.
• Configure the database options for Enterprise servers.
• If converting to an Enterprise server, restart BACtalk to convert the
databases from Access/Jet to SQL Server format.

10 Configure the Default User in General System Setup. IMPORTANT! page 38

Only the Default User can access the Dashboard.

11 Upgrade the ROC file in all host devices. page 27

© Honeywell LTBT-TM-ADMIN30 Rev. 05 15

Installation and Startup Guide | Envision for BACtalk

Task See
13 Verify the Device Manager table and send all data to devices. page 50
• Verify that this computer’s device instance is listed in the table.
• Verify that all known devices connected to the same network are
listed in the table.
• Verify that the appropriate device capabilities are selected,
especially for host devices; poll by device.

14 Verify that all objects (for example, trendlogs and schedules) were --
successfully sent to all host devices.

15 Update BACtalk user profiles to add a start display, authorized page 47

period, device access and privileges, and group membership(s), and
log into Envision for BACtalk again to access these features.

16 After all clients are upgraded, enable the Require client/server --

authentication option on the Network tab in General System Setup to
provide secure communication capabilities between all clients and
the BACtalk the server.

17 If applicable, configure the Alerton Energy Dashboard. See the

Envision for
BACtalk
Operator’s
Manual

Steps to upgrade client operator workstations

Task See
1 On each client operator workstation, verify that a rep/job directory page 30
exists that matches the rep/job directory on the Envision server using
General System Setup.

2 If already installed, uninstall the Alerton/Novar Ethernet Driver. page 21

3 Run setup.exe from the Envision for BACtalk DVD. page 21

4 If necessary, restore the job used in the earlier version of Envision for page 42
BACtalk. (This must be the same job set as the default on the server.)
5 Start the upgraded Envision for BACtalk, set the Local page 37
Administrator’s password and log into the job.

6 Verify General System Setup. page 46

• Set the device instance for the operator workstation on the
Identification tab.
• Verify the Primary Ethernet adapter on the Network tab.
• Verify that the Ethernet BACnet Protocol or Annex J BACnet/IP or
both are enabled on the Network tab.
• Identify this operator workstation as a client, using Site
Configuration on the Network tab.

7 Verify the Device Manager table. page 50

• Verify that this computer’s device instance is listed in the table.
• Verify that the server’s device instance is listed in the table.
• Verify that all known devices connected to the same network are
listed in the table and the appropriate device capabilities are
selected. Correctly set device capabilities by polling by device.

8 If it is no longer needed, you can remove the previous version of --

Envision for BACtalk through the Control Panel.

16 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation and upgrade quick steps

Quick steps–upgrading stand-alone controller sites

WARN ING Do not dial into a stand-alone controller site without first saving
and backing up data.

Note For more information about connecting to remote sites, see the Envision
for BACtalk Operator’s Manual (LTBT-OP-EBT).

Task See
1 Connect to the remote site with the currently installed version of --
BACtalk software and perform the reverse engineering function
(save data from devices to the operator workstation hard disk).

2 Disconnect. --

3 Back up the existing job. page 19

4 Compact the existing job database. page 20

5 Run setup.exe from the Envision for BACtalk DVD. page 21

6 If necessary, restore the job used in the previous version of page 42
Envision for BACtalk.

7 Connect to the site, and log in to the job for the remote site. --
Do not perform reverse engineering at this time.

8 Upgrade the ROC file in all host devices. page 27

9 Verify the Device Manager table and send all data to devices. page 50

10 Verify device capabilities; set correctly by polling by device. --

11 Verify that all objects (for example, trendlogs and schedules) --

were successfully sent to all host devices.

12 Configure the Default User in General System Setup. page 38

IMPORTANT! Only the Default User can access the
Dashboard.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 17

Installation and Startup Guide | Envision for BACtalk

Installation detail
This section provides more detailed instructions for the tasks listed in the
preceding quick steps sections. There may be portions of this section that are not
applicable to your installation. Use the quick steps tables (beginning on page 10)
as a guide to determine which of the following procedures you need to complete.

Documenting address numbering

Your address numbering scheme is critical. You must ensure that any connected
network, such as Ethernet, MS/TP, and PTP connections, has a unique address
number. Unique address numbers identify BACnet devices on a network to any
other device and ensure that your system routes information correctly.

Designate and document the address numbering scheme on installation

drawings. Make sure you include:

• Networks Every LAN on the BACtalk system has a unique numerical

identifier, a network number, in the range 1 to 65,534. No two
interconnected networks can have the same network number.
• MAC addresses Media Access Control (MAC) addresses uniquely
identify a device on its network. A device (such as a BCM) that exists
on two LANs has two MAC addresses, one for each LAN to which it
belongs. The MS/TP MAC address range is 0 to 127. (Ethernet MAC
addresses are preassigned by the manufacturer.) For a VLC, the MAC
address is set with DIP switches on the VLC unit. For host devices, set
MS/TP MAC addresses using HyperTerminal or Remote Configuration.
• Device Instances The device instances range from 0 to 4,194,302. Each
device that communicates on the BACnet system (including other
manufacturers’ devices) must have a unique device instance. (BACnet
reserves device instance 4194303 for special purposes; do not use this
device instance.) When setting up devices, adopt a hierarchical
addressing scheme. Plan device instances for the following:
• Workstations
• PTP virtual device instance
• Global controllers
• BACtalk control modules
• Expandable controllers
• BACtalk routers
• BACtalk ports
• VisualLogic controllers
• Other manufacturers’ devices
N o t e Each BACtalk control module (BCM), except the BCM-PWS
and BCM-MDM, must have its own device instance. The BCM-TUX
also has some special addressing requirements compared to other
BCMs. For detailed information, see the BACtalk Control Modules
Installation and Operations Guide (LTBT-TM-BCMIOG).
For more detailed information about device addressing, see the BACtalk System
Design Guide (LTBT-TM-SYSDSGN).

18 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation detail

Installing Visio
Install Visio 2007 or Visio 2010 if you plan to use VisualLogic. Alerton
recommends you install Visio in the default installation directory. For detailed
installation procedures, see your Visio documentation.

IMPORTANT Always install Visio before installing Envision for BACtalk. The
VisualLogic macro will not run if Visio is installed after BACtalk. The remedy is
to uninstall and reinstall Envision for BACtalk.

IMPORTANT Set the Macro security level to “Low” before installing Envision
for BACtalk.

IMPORTANT Visio users, set up a trusted location. Read the following

knowledge base article for more information:
http://asn.alerton.com/knowledgebase/technicalissue/01-0122-01-00.aspx

CAUTION If you upgrade from Visio version 5.0 or 2000 to Visio 2007 or
Visio 2010, you must completely uninstall the older version before installing a
newer version. Otherwise, VisualLogic will not work properly.

Note Computers that meet only the minimum system requirements should not
use Visio and VisualLogic. See page 76 for more information.

Compacting a BACtalk job database

To reduce database size, Envision for BACtalk 3.0 automatically repairs and
then compacts a job database in the background. BACtalk software does include
a tool you can use to manually compact and repair all the database files
associated with your site if you want to manually perform the operation.
Operating conditions may cause database file performance to degrade over time
and the compact and repair tool can help improve performance.

About the repair operation

The repair operation repairs a database that was marked as possibly corrupt by
an incomplete write operation. This can occur if an application is closed
unexpectedly because of a power outage or a computer hardware problem. The
repair operation validates all system tables and indexes.

About the compact operation

Compacting your database is similar to defragmenting: it consolidates database
files on the hard disk, rearranging how the files are stored so they use disk space
more efficiently.

 To compact and repair BACtalk database files

1. Close BACtalk.

2. In the BACtalk program group (Programs > Alerton > Envision for
BACtalk), select Compact BACtalk Access Database. 
The Compact and Repair Databases dialog box opens.

3. Enter the Rep/Job to repair, and then click Compact/Repair.

BACtalk lists the files that it works on and notifies you when it is
complete.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 19

Installation and Startup Guide | Envision for BACtalk

Backing up BACtalk job data

Backing up a BACtalk job creates a zip file of all job information, which can be
restored later if necessary. If you are upgrading from an earlier version and will
install Envision for BACtalk on a new computer, use the Backup utility to move
existing job files to the new computer. You can copy the zip file to the
appropriate media, and then use the Restore utility on the new computer. See
“Restoring a BACtalk job” on page 42 for more information.

If you have upgraded the job from a previous version of BACtalk or have
successfully merged another job into this one using the Restore BACtalk Job
Utility and restarted Envision for BACtalk, you may safely remove the unused
files prior to backing up the job to save backup time and disk space. For a list of
files you may safely remove see the following knowledge base article on the
Alerton Support Network (ASN): White paper 08-0061-01-00

Note The Backup utility cannot span multiple disks. If you have a large job,
back up to the hard drive, and then write the zip file(s) to the appropriate media.

 To back up a BACtalk job

1. Start BACtalk and log in.

2. From Device Manager, select all devices, and then save all device data
to disk.
N o t e Choosing to save trendlog data may take a long time.

3. If you are backing up a BACtalk for Windows v3.1x job, on the

BACtalk menu, point to Backup, and then click Backup Job.
-or-
If you are backing up an Envision for BACtalk job, on the Tools menu,
point to Backup, and then click Backup Job.
The Backup dialog box opens.

4. Under Job, select the rep/job that you want to back up. (The current
default rep/job appears in the BACtalk title bar.)

5. Under Archive File Name, type a path and file name for the backup file.
-or-
Click Browse and then select the folder and type the file name you want
to save to. Click Save to return to the Backup dialog box.
N o t e BACtalk automatically adds a zip file extension to the file name
you type when performing a backup.

6. Click Backup.
BACtalk creates a zip file with the name you specify in the folder you
select. Progress messages appear in the Output list.

7. Click OK, and then click Close.

20 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation detail

Running the Envision for BACtalk installation program

By default, Envision for BACtalk v3.0 is installed in C:\Alerton\BACtalk\3.0,
which is a different default directory than previous versions.

CAUTION Do not install Envision for BACtalk to the same directory where
BACtalk for Windows is installed if you plan to continue using BACtalk for
Windows on this computer. If installed in the same directory, Envision for
BACtalk will fully replace BACtalk for Windows.

CAUTION Do not install newer versions of Envision for BACtalk in the same
directory where earlier versions of Envision for BACtalk are installed. Envision
for BACtalk versions 2.5, 2.6, and 3.0 have new database structures and the
databases get automatically converted during startup. A 2.5, 2.6 or 3.0 job cannot
be converted back to a previous version. Before upgrading to v2.5 or later, back
up your current job.

1. Insert the DVD.

The setup program launches automatically. Some computers may have
auto-start disabled. In this case, open Windows Explorer and double-
click the Setup.exe program on the DVD.

2. Follow the instructions that appear on your screen.

Read the readme

The readme (.rtf) file appears in a viewing pane during setup. It covers important
late-breaking technical issues. You can also view the readme from the DVD at
any time.

Viewing Help on new Envision for BACtalk features

Setup includes an option to view a short help topic on the new features in
Envision for BACtalk.

Installing the Alerton/Honeywell BACtalk Driver

Envision for BACtalk v2.5 SP1 and later automatically installs the Alerton/
Honeywell BACtalk driver. These instructions are provided in case you need to
manually install the driver.

Installing the Alerton/Honeywell BACtalk Driver is required for all new

installations. If already installed, uninstall the previous version, named “Alerton/
Novar Ethernet Driver.” The old BACtalk Protocol for Envision driver does not
need to be removed; it can still be used for Envision for BACtalk v1.0-1.2. Use
the Table on the following page as a guide.

Note Windows NT and 9x are no longer supported platforms. Drivers for

Windows NT and 9x do not work with Envision for BACtalk v1.3 and later.

Ta ble 2 Alerton/Honeywell BACtalk Driver

Required for
Operating systems Name Location
upgrades
Windows XP, Windows Alerton/Honeywell BACtalk Driver 3.0 C:\Alerton\BACtalk\3.0\Drivers\Win2 Yes
2000, Windows Server (ETHUIO.SYS) 000-XP
2003, Vista, and Win 7.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 21

Installation and Startup Guide | Envision for BACtalk

If you do not have the correct protocol driver installed, the following message is
displayed after you log into Envision for BACtalk. This message appears during
initial installation and every time a new job is created. The Ethernet Adapter
field on the Network tab will also have a blank list until the protocol is installed.

• Click OK and then install the Alerton/Honeywell BACtalk Driver.

Once the Primary Ethernet Adapter is specified on the Network tab, the
issue causing this message will be resolved.

 To install the Alerton/Honeywell BACtalk Driver

Note If Envision for BACtalk has not already been installed, start with Step 3.

1. Open a command prompt, type “net stop ethuio”, and then press Enter.
This stops the existing Alerton/Novar Ethernet Driver from running and
allows it to be uninstalled without re-booting Windows. 
The following message is displayed: “The Alerton/Honeywell BACtalk
Driver service was stopped successfully.”

2. Close the Command Prompt window.

3. Open the Windows Control Panel, select Network Connections, and

then uninstall the Alerton/Novar Ethernet Driver.
Depending on your operating system, the Network Connections option
may have another name, such as Network and Dial-up Connections.

4. Install Envision for BACtalk.

5. Open the Windows Control Panel, and then click Network

Connections.

6. Double-click Local Area Connection, click Properties, and then click

Install.

7. In the Select Network Component Type dialog box, click Protocol, and
then click Add.

8. Click Have Disk, click Browse, and then locate and select the updated
Alerton/Honeywell BACtalk Driver 3.0. The drivers are typically
located at C:\Alerton\BACtalk\3.0\Drivers.

9. Ignore the message “This driver is not digitally signed” and click OK.

10. In the network connection properties dialog box, make sure that
Alerton/Honeywell BACtalk Driver is enabled (checked).
N o t e If you have both Envision for BACtalk and BACtalk for
Windows installed on an operator workstation running Windows 2000
or Windows XP, you must have both protocol drivers installed and
enabled.

22 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation detail

11. Click Close, click Close again, and then close the Network Connections
dialog box.

Note The primary Ethernet adapter entry initially appears as None when you
start Envision for BACtalk with the new driver. You must select your Ethernet
adapter on the Network tab in the General System Setup dialog box.

Note The Ethernet Adapter field will have a blank drop-down device list until
the protocol is installed or the driver may not have been started.

Configuring the Local Administrator

“LocalAdministrator” was a new user ID in Envision for BACtalk v2.0 and the
name of this user cannot be changed. It is the only user who can perform special
high-privilege tasks at the local workstation related to job management and user
profiles, including:

• Install Envision for BACtalk and configure a new job

Only the Local Administrator has privileges to add the initial user to a
new Envision for BACtalk job. The Local Administrator sets up the
initial user’s user profile immediately following installation. Then, the
initial user (if they have the “Configure Job Data Folder” privilege) or
the Local Administrator may configure a new BACtalk job.
• Configure user profiles in any job on the current workstation
The Local Administrator must be logged into a job before he/she can
reset the password of any user in that job.
N o t e Any user that is logged in and who has the “User and Group
Setup” privilege can reset user passwords; add modify, or delete users;
set user security levels and privileges; and set user start displays.
• Configure a local BACtalk workstation
This includes workstations in General System Setup and Connection
Manager.
When Envision for BACtalk launches for the first time, the system checks for an
existing Local Administrator user ID and prompts you to create the Local
Administrator’s password if the profile is not already found. Only a user who is a
member of the Windows Administrator group can configure the Envision for
BACtalk Local Administrator user ID.

IMPORTANT! Failing to configure the Local Administrator during initial

startup will result in users being locked out from special job management and
user profile tasks until Envision for BACtalk is removed, reinstalled, and the
Local Administrator is set up.

The Local Administrator always logs in in offline mode to protect BACtalk

server data. The Local Administrator can not change job data remotely.

Like other user IDs, all “Local Administrator” user activity is recorded in the
User Activity Log.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 23

Installation and Startup Guide | Envision for BACtalk

Installing the BACtalk software license key

Starting with version 3.0, Envision for BACtalk now uses a software license key
instead of a physical hardware key connected to the computer. After purchasing
Alerton Building Suite 3.0, you will receive an email from Alerton that contains
your BACtalk software license code.

Figure 1 Email from Alerton Customer Service containing a sample BACtalk software license key

Depending on the job size, Envision for BACtalk supports a different number of
operator workstations and BACnet devices. If you are setting up a client/server
site, you must first set up the server. Software license should be installed on the
server; client installations do not require a software license. License files are not
required to work in offline mode.

The Alerton Building Suite startup processes require software license files that
are specific to the computer on which they are installed. During installation you
will be prompted to enter your software license key which activates the licensing
process. It is strongly recommended that the host computer/server be connected
to the Internet during installation.

IMPORTANT! Software license keys are non-transferable. Once a license key

is bound to a Host Id, it cannot be bound to another Host Id. It is strongly
recommended that you physically record the license key directly on the
computer to which it is bound.

24 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation detail

With an Internet connection

If the host computer has an Internet connection it should seamlessly connect to
the licensing server and download the license files directly. See “Without an
Internet connection” on page 26 if you cannot connect to the Internet during
installation.

1. Type your license key into the HostId field on the Install BACtalk
License dialog box. NOTE: Type capital letters only.

2. Click Install. 
The licensing process should complete within seconds.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 25

Installation and Startup Guide | Envision for BACtalk

Without an Internet connection

IMPORTANT! It is strongly recommended that you connect the host computer
to the Internet to install Envision for BACtalk to avoid having to contact Alerton
Technical Support to complete the process.

The Install BACtalk License dialog box will display every time you launch
Envision for BACtalk if the system has not been properly licensed.

 To license your system without an Internet connection

1. Send your original email detailing your license key and your Host Id to
Alerton Technical Support at tech.support@alerton.com.

2. Use the Copy to clipboard button on the Install BACtalk License

dialog box to easily copy and paste your Host Id and guard against
typing errors.

3. Alerton Technical Support will email you your license files. Copy the
license files to your desktop.

26 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Installation detail

4. Click Browse on the Install BACtalk License dialog box.

The Select license and certificate files dialog box opens.

5. Click your <HostId>.lar file, click Open.

6. Click Install on the Install BACtalk License dialog box.

Envision for BACtalk will continue installing/launching completely.

Note If you experience an error message when installing the software license,
search for “license” in Envision for BACtalk Help for an explanation.

Protecting your BACtalk license key

Once your BACtalk software order has been processed, Alerton will send you
your BACtalk software license key. See Figure 1 on page 24.

IMPORTANT! Keep a copy of your license key in a safe place for future
reference. You must have your license key in order to get it replaced if your host
computer must be replaced. It is strongly recommended that you physically
record the license key on the computer to which it is bound.

Upgrading real-time operating code (ROC)

For a list of the ROC files included with Envision for BACtalk v3.0, see the
Readme.

Using the appropriate ROC file for your job is extremely important. The ROC
file is integral to Device Manager operations and device capabilities. See
“Understanding Device Manager” on page 50 and “Device capabilities” on

© Honeywell LTBT-TM-ADMIN30 Rev. 05 27

Installation and Startup Guide | Envision for BACtalk

page 52 for more information.

Note Any new ROC files are copied to the operator workstation during
Envision installation and stored in the <BACtalk root>\System folder.

 To upgrade a ROC file

1. Start Envision for BACtalk.

2. On the BACtalk menu, click Device Manager.

Sending a dissimilar ROC file clears the device memory (including
DDC, setup information, and data). You should do a point data save and
remote configuration if the device supports it from the device before
sending the ROC file.

3. In the list of devices, select the devices you want to update, and then
click Send.
N o t e If you want to update more than one device, you can select and
send the ROC file to all of them at the same time.

4. In the Send Data from Disk to Devices, select ROC (OMF/BIN).

5. Click Send or Send All if the “Read new device capabilities after
sending ROC” option is selected.
You can check the User Request Monitor (View > User Request
Monitor) to verify that the ROC was sent successfully.

6. To send previously saved objects, select all and then click Send.
N o t e The Save All button is intended for use with stand-alone sites.

28 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Client/server setup

Client/server setup
When more than one operator workstation is used on a site, one of the computers
must be configured as a server for the other workstations. This is done using the
General System Setup option on the Envision for BACtalk Tools menu. For
more information, see “Verifying General System Setup” on page 46.

Note It is recommended that you copy job displays and templates to client
workstations. Sharing data displays across a network is not recommended. It can
severely impact network performance. If your network has the bandwidth to
support sharing data displays this way, see “Sharing data displays in a client/
server network” on page 81 for more information about how to set it up.

Setting up a client/server relationship

Before setting up a client/server relationship, it is highly recommended that you
review Windows documentation for setting up shared network resources for the
version of Windows you are using.

The operator workstation you choose to be the server should have the best
hardware setup among operator workstations. A large hard disk and fast
processor are of particular importance. For more information, see
“Recommended system specifications” on page 76.

Setting up the Envision server

When you set up the Envision server, you perform these tasks:

• Install Envision for BACtalk and set up the Local Administrator user
profile.
• Configure the active rep/job directory on the server.
• Identify the operator workstation as the server.
• Configure user profiles.

 To install BACtalk and establish the rep\job directory

1. Install Envision for BACtalk on a computer connected to the Ethernet
network that will serve all operator workstations.

2. Start Envision for BACtalk and set the Local Administrator’s password
to allow for special tasks requiring higher privileges at the local
workstation.

3. Log in with “LocalAdministrator” and the password you just created. 

Note: The “localadministrator” user ID is not case-sensitive.

4. On the Tools menu, click Set Rep and Job.

5. Type a rep name and job name. Make a note of these; you will need
them later in this procedure whenever <repname> and <jobname> are
used.

6. Click Options to expand the dialog box, click Create Dir., and then
click OK to create the directory key for the current job.
This creates a job directory named <repname>/<jobname> and makes it
active. All support and database files will be created within this job

© Honeywell LTBT-TM-ADMIN30 Rev. 05 29

Installation and Startup Guide | Envision for BACtalk

directory. For example, a job directory might be

C:\Alerton\BACtalk\3.0\Myrep\Myjob.
N o t e Click Make Key (site key) if you want to allow users to modify
job display files and DDC. The default job must have a site key.

7. Click Select.

8. Set up a Default User profile.

9. Set up an Initial User profile. (See page 37 for more information)

10. Close and restart Envision for BACtalk, and then log in with the initial
user’s user name and password.

 To identify this workstation as the server

1. Start Envision for BACtalk, and then log in to the job created in the
preceding procedure.

2. On the Tools menu, click General System Setup.

3. On the Network tab, click Site Configuration.

4. Select This computer is the BACtalk server.

5. Select the primary host device for this installation.

6. Select the Archive directory if you want to store archived databases in a

location other than the default location in the Rep/Job directory.

7. Click OK to close the Site Configuration dialog box, and then click OK
to close the General System Setup dialog box.

8. Close and restart Envision for BACtalk for the setup to take effect.

Setting up a client operator workstation

There are two options for connecting a workstation, an “always on” option and a
“temporary” option.

Always on connection
For the always on option, set up Annex J on the Network tab of General System
Setup in Envision for BACtalk. This option allows BACnet messages to pass
over the IP network in the same way as any other application data: data displays,
schedules, trendlogs, and alarms can reference device instances and properties
anywhere on the internetwork. They appear to the Envision for BACtalk
operator workstation as though they were locally connected. Envision for
BACtalk initiates the connection on startup.

Temporary connection
For a temporary connection, set up Annex J in the Connection Manager for a
Remote Site. You can set up the connection type in a remote site profile to use
Annex J, just as you would normally use a modem or a serial cable. In this way,
you can temporarily connect to a remote site over the BACnet/IP network. Once
you establish your connection to the network—plugging into an available
Ethernet jack, dialing in through an Internet Point-to-Point Protocol (PPP) or
Windows Remote Access Service (RAS) connection, and so on—you can open

30 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Client/server setup

Envision for BACtalk and then use Connection Manager to initiate a BACtalk
session by registering with the BBMD.

You must perform the following steps for each client workstation:

• Start Envision for BACtalk and set the Local Administrator’s password.
• Log in with “LocalAdministrator” and the password you created.
• Configure the active rep/job directory.
• Identify the operator workstation as the client.

 To install Envision for BACtalk and establish the rep\job

1. Install Envision for BACtalk on a computer connected to the same
network that the server is on.

2. Start Envision for BACtalk and set the Local Administrator’s password
to allow for special tasks requiring higher privileges at the local
workstation.

3. Log in with “LocalAdministrator” and the password you just created.

4. On the Tools menu, click Set Rep and Job.

5. Type the rep name and job name. These must match the <repname> and
<jobname> you established on the Envision server.

6. Click Options to expand the dialog box, click Create Dir., and then
click OK to create the directory key for the current job.
This creates a job directory named <repname>/<jobname> and makes it
active. All support and database files will be created within this job
directory. For example, a job directory might be
C:\Alerton\BACtalk\3.0\Myrep\Myjob.

7. Click Make Key if you want to allow users not logged in with a rep
name and password to modify job display files.

8. Click Select.

9. Restart Envision for BACtalk and log in to the new rep/job using the
LocalAdministrator credentials.

10. Set up the Default User profile.

11. Set up an Initial User profile. (See page 37 for more information)

12. Restart Envision for BACtalk and log in with the initial user’s name and
password.

13. Copy job templates, displays, and bitmaps to the job subdirectory you
created. See Figure 2 on page 39 for the correct locations for these files.

Note If your network supports it and you want to share displays across the
network, follow the instructions in “Sharing data displays in a client/server
network” on page 81. Be aware that display sharing across a network may
increase network traffic and slow network performance.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 31

Installation and Startup Guide | Envision for BACtalk

 To identify a workstation as a client

1. Start Envision for BACtalk.

2. Log in to the job created in the preceding procedure.

3. On the Tools menu, click General System Setup.

4. On the Network tab, click Site Configuration.

5. Select This computer is a BACtalk client.

6. Type the device instance assigned to the Envision for BACtalk server.

7. Click OK to close the Site Configuration dialog box, and then click OK
to close the General System Setup dialog box.

8. Close and restart Envision for BACtalk for your changes to take effect.

Configuring servers and clients for a NAT environment

When a NAT firewall separates the Envision for BACtalk server and one or more
client workstations, you must edit the bactalk.ini file of the server and each client
to enable communication across the firewall. Envision for BACtalk and Alerton
web applications use the HostName and HttpPort settings in BACtalk.ini to
address messages to the web server.

 To configure a server
1. Open bactalk.ini in a text editor.

2. Add two entries to the Niagara section:

PublicHttpPort=
PublicHostName=

3. Set the value of PublicHttpPort to match the public port configured in

the NAT firewall.

4. Set the value of PublicHostName to match the public host name or

public IP address configured in the NAT firewall.

5. Save and close the bactalk.ini file.

6. Restart Envision for BACtalk.

 To configure a client outside the NAT firewall

1. Open bactalk.ini in a text editor.

2. Add two entries to the Niagara section:

PublicHttpPort=
PublicHostName=

3. Set the value of PublicHttpPort to match the PublicHttpPort value of the

server.

4. Set the value of PublicHostName to match the PublicHostName value

of the server.

5. Save and close the bactalk.ini file.

32 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Client/server setup

6. Restart Envision for BACtalk.

 To configure a client inside the NAT firewall

1. Open bactalk.ini in a text editor.

2. Add two entries to the Niagara section:

PublicHttpPort=
PublicHostName=

3. Set the value of PublicHttpPort to match the local IP port of the server.

4. Set the value of PublicHostName to match the local host name of the
server.

5. Save and close the bactalk.ini file.

6. Restart Envision for BACtalk.

Setting up a large wide area network (WAN)

 To install Envision for BACtalk in a large wide area network
1. Shut down all client operator workstations, if practical.

2. Upgrade the BACtalk server.

For detailed instructions, see “Steps to upgrade the server” on page 15.

3. Travel to each client location and upgrade the client workstations.

For detailed instructions, see “Steps to upgrade client operator
workstations” on page 16.

4. Set up each client with the same job directory as the server.

5. Copy job templates and displays to the job directory you created.
N o t e If your network supports sharing displays across the network,
see “Sharing data displays in a client/server network” on page 81.

6. Restart client operator workstations.

WARN ING Significant changes were made to the BACtalk database structure
in versions 2.5, 2.6, and 3.0 to improve system performance, stability and
security. Once a job is upgraded to 2.5 or later, it cannot convert back to an
earlier version of BACtalk. Back up the current job before upgrading.

WARN ING Do not mix versions of BACtalk. For a large WAN upgrading to
Envision for BACtalk, you may not be able to upgrade all operator workstations
at the same time. If you must connect workstations running different versions of
BACtalk operator workstation software, some unexpected errors may occur. In
particular, do not edit schedules, trendlogs, alarms or make changes in Device
Manager from a workstation running BACtalk for Windows 3.1x. BACtalk for
Windows v3.1x does not support Envision for BACtalk features.

Note When you dial into a remote site, always save data from devices first.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 33

Installation and Startup Guide | Envision for BACtalk

Note On the server, you can leave the Secure Communication Capabilities
check box unchecked, until all clients are upgraded. If upgrading from BACtalk
v2.0 or later, you are already running the correct protocol used by v3.0.

34 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Connecting sites running different software versions

Connecting sites running different software versions

In some situations, you may have Envision for BACtalk installed on the same
computer with an earlier version of BACtalk for Windows. For example, if you
provide support to multiple sites, some may be using Envision for BACtalk
while others use BACtalk for Windows v3.11 or earlier versions. When you
connect to another computer, you should use the same version of BACtalk
operator workstation software whenever possible.

WARN ING Significant changes were made to the BACtalk database structure
in versions 2.5, 2.6, and 3.0 to improve system performance, stability and
security. Once a job is upgraded to 2.5 or later, it cannot convert back to an
earlier version of BACtalk. Back up the current job before upgrading.

Note You can install Envision for BACtalk and BACtalk for Windows on the
same computer, but you can’t open and run both programs at the same time.

Use the following scenarios as a guide when connecting to sites running different
versions of BACtalk operator workstation software.

Scenario 1: Temporary connections

Terry works for AlerRep Inc., which supports several BACtalk sites. Some have
upgraded to Envision for BACtalk and some continue to run BACtalk for
Windows. After installing Envision for BACtalk on his laptop computer, Terry
connects to Remote Site 1, which is a stand-alone installation with a global
controller, but no permanent operator workstation. When he connects with the
site, he reads data from the host device, which is automatically converted to
Envision format. This has no effect on the remote site.

Note To work with new features, such as optimum start, tenant activity,
demand limiting, or multistate objects, you must upgrade the host device with
the latest real-time operating code (ROC) file.

The next day, Terry connects to Remote Site 2, which is a server-based site,
running BACtalk for Windows v3.11. To ensure compatibility, Terry uses the
same version of the software when he connects to this site. Fortunately, he had
the foresight to keep a copy of BACtalk for Windows 3.11 on his operator
workstation for just this purpose.

Scenario 2: Remote alarm logging

Zdot, Inc. provides a remote alarm logging service to several sites running
BACtalk operator workstation software. Zdot recently upgraded to Envision for
BACtalk v3.0. Several of Zdot’s customers have also upgraded to this latest
release, but some still use earlier versions of BACtalk operator workstation
software. Because alarms are generated by the host device, which sends the
alarm notifications to Zdot’s host device, the different versions of software
running on operator workstations at each customer site need not be a concern.

This scenario could be different if the workstation used to provide remote alarm
logging services is running BACtalk for Windows v3.1x and a customer site is
using Envision for BACtalk. If the customer had alarms set for Envision’s new
features, such as demand limiting, the remote alarm logging service would not
be able to view those alarms. In this scenario, it is recommended that you
upgrade the operator workstation before performing alarm logging.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 35

Installation and Startup Guide | Envision for BACtalk

Scenario 3: Remote connections for point data exchange and log

gathering
The Citytown School District has been using Envision for BACtalk v2.5 in five
of its schools as well as its district administrative offices. A centralized operator
workstation is located at the administration office. The school district uses
BACtalk’s remote dialing features to exchange point data. One of the schools,
PS5, recently updated to Envision for BACtalk v3.0. Dialout schedules from the
administration office should be disabled until Envision for BACtalk v3.0 has
been installed there as well.

The administration office also dials a stand-alone global controller at the

district's central plant to gather log data once a day. The log gathering setup
should be disabled until the global controller has been updated with a ROC file
compatible with Envision for BACtalk v3.0.

36 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

Job setup and engineering

Before customers can use Envision for BACtalk for their day-to-day operations,
certain startup tasks must be completed, including setting up a job, defining user
profiles, and defining device profiles. This section describes those tasks for both
a new installation and an upgrade. Information about pre-planning your job
engineering is also included to ensure an older BACtalk job will successfully
merge with an upgraded Envision for BACtalk job.

Local Administrator security scheme and directory structure

There are two login scenarios to choose from: you can log in as the Local
Administrator or a user. When logged in as the Local Administrator, you can
only work in offline mode and you are limited to the installing and configuring
new Envision for BACtalk jobs and setting up users on the local workstation.
The user that installs Envision for BACtalk on a computer becomes the Local
Administrator for that workstation and only that workstation. They cannot access
jobs on other workstations.

When logged in as a user, your access is limited to the capabilities configured in

your user profile. For example, you may or may not have a high enough security
level to edit DDC and displays.

Following are some key points and terms to keep in mind when creating jobs and
users:

• When you start Envision for BACtalk for the first time, you must set up
the Local Administrator for the local BACtalk workstation to perform
special tasks that no other user can perform.
• When you create a new job, there are no user profiles; you must create
them or users will not be able to log in. Create the Default User profile
for all jobs that will use the Dashboard.
• Each job has a unique system setup, specifying addressing information
for the operator workstation and devices on the BACtalk system.
The following list includes key terms used when discussing job setup.

Local The user profile that allows for special tasks requiring higher privileges at the
Administrator local workstation and provides stronger security. The Local Administrator
must be configured during initial setup. The Local Administrator is the user
that installs BACtalk on the local computer. Each computer has its own local
administrator. See “Configuring the Local Administrator” on page 23 and
“Logging in for the first time” on page 40 for more information.
Initial User By logging in with the Initial User ID and password assigned by the Local
Administrator, the initial user can work with new jobs and create user profiles,
displays, DDC, and security files that go with them. The Initial User should
have high access privileges if this user will finish setting up the job where the
Local Administrator left off. This Installation Guide assumes the Initial User
has high privileges. For example, give the Initial User a higher security level
and the “Configure Job Data Folder” and “Users and Group Setup” privileges.
Whereas the Local Administrator is limited to working in offline mode only,
the Initial User may work in online mode.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 37

Installation and Startup Guide | Envision for BACtalk

Default User The Dashboard Application uses the Default User to silently authenticate with
the Envision for BACtalk web server. It is recommended that the Default User
have the minimum privileges. The Default User does not have to be logged
into Envision for BACtalk for the Dashboard to work. Configure and enable
the Default User at Tools > General System Setup > Startup/Shutdown. The
Default User should not be the user who configures the dashboard.
Job Term used to describe a set of displays, DDC, and databases used for a specific
application or site. Displays and DDC for a job are stored in the job folder
beneath the representative folder. Displays and DDC saved in the job folder
cannot be modified from within Envision for BACtalk unless a user is
authorized to do so.
Default Job The job name last specified by the representative in the Set Rep and Job dialog
box, which appears only to privileged users. The default job name appears in
the Envision for BACtalk title bar when you log in.
Site Key A software file that enables users with sufficient security to edit and then
overwrite DDC and displays in a job folder. If the key is not created for a job,
that job cannot be the default job for Envision for BACtalk.
Alerton The displays and templates that are shipped with Envision for BACtalk and are
Standard stored in a special Alerton Standard job folder of the Alerton root folder.
applications Displays and DDC stored here cannot be overwritten by a representative or
user. They can be copied, then modified and saved to a job folder that has a site
key.
Generic Job The factory default job. A keyed job that provides a repository for DDC and
displays that can be modified. A representative or user can also use this job to
access Envision for BACtalk if something has gone wrong with the default
representative and job (for example, the user authorization file has been
deleted or corrupted, or the job folder has been renamed or deleted). For this
reason, do not delete the Generic job folder or any files in it on any operator
workstation.

Saving displays and DDC

To enable a user to save displays or DDC to a job folder, the Local Administrator
must make a site key for that folder. A user with high security can save displays
and DDC to any job folder under that user’s folder, regardless of whether a site
key is present.

You can use any displays, templates, and DDC files from any job folder on any
other job. If these are modified, however, they can only be saved to the default
job or by those logged in as a privileged user.

Settings in the Users and Groups dialog box still govern a user’s ability to edit
displays and templates. See “Creating user profiles” on page 47 for more
information about user privileges.

File locations
Displays and DDC files created for a particular job are saved in a subfolder of
the Alerton root folder (specified during installation) as shown in Figure 2.

38 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

Figure 2 Envision for BACtalk directory structure

Root directory
Alerton Standard directory
• Factory-standard displays and graphics and DDC.
• If displays and templates are modified, they must be saved to a job folder.
• Any job can use displays, bitmaps, DDC, and documentation from Alerton Standard.
• Documentation directory stores sequences and point list for standard applications.
Bitmaps directory
• Stores bitmaps used by data displays and templates in the displays directory. If not in
this location, Envision for BACtalk will not find bitmaps for displays and templates.

DDC directory
• Stores all DDC files for the job.

Displays directory
• Stores all displays and templates for the job.

Stores communications protocol drivers

Generic directory (with Generic job within it)
• Provides a default login if rep/job is lost or corrupt.
• Do not delete.

System directory
• Stores core operating files for BACtalk system and ROC files for host devices.

Stores software license keys

Device data directories

• One for each device, named Dev<devinst> where <devinst> is the device instance of
the controller.
• Stores device setup data for device manager and applicable object images (schedules,
trend logs, demand limiters, etc.) for the device.

More user job directories

• In this case, two jobs for remote sites.

VisualLogic directory
• Stores core operating files for VisualLogic.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 39

Installation and Startup Guide | Envision for BACtalk

Logging in for the first time

When you log in to Envision for BACtalk for the first time, configure the Local
Administrator user ID and log in as the Local Administrator. This enables you to
create job folders in which you can store custom displays, DDC, and a user
authorization file. See “Configuring the Local Administrator” on page 23 for
more information about the Local Administrator.

 To log in to BACtalk for the first time

1. Start Envision for BACtalk and set the Local Administrator’s password.

2. Log in with “LocalAdministrator” and the password you just created.

Make sure that the letters you type are the correct case because the
password is case sensitive. For security reasons, asterisks appear instead
of the letters you type.

3. If a Tech Key is detected, the system will display a code. Type the code
in the field provided.

Figure 3 Login/Logout dialog box with sample code displayed.

4. Click Login.
You are now logged in to the Generic job with the highest security level.
Create a default job, set up user profiles, and configure the workstation.

Creating a default job

When you first log in, you are in the Envision for BACtalk default job called
GENERIC/GENERIC. Create your own default job for the operator workstation
where you are working. Because you are logged in as the LocalAdministrator,
you can create your new default job now. This tells Envision for BACtalk to
store any files or DDC you edit to your default job folder as you work with your
job. Only the Local Administrator has the ability to change the default job or
create a new job upon initial launch. A user logging in with a user name and
password that has high privileges and the appropriate capabilities can also
perform some job management tasks after the Local Administrator has created
the new job. For example, give an advanced user a higher security level than a

40 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

novice user and the “Configure Job Data Folder” and “Users and Groups Setup”
privileges.

You can create as many job folders as you want, but only one job can be the
default. To change the default job, select it in the Set Rep and Job dialog box,
and then restart Envision for BACtalk.

Note If you upgraded from BACtalk for Windows v3.1x, you can use the job
data from that version in Envision for BACtalk. See “Using BACtalk for
Windows job data in Envision for BACtalk” on page 41 for more information.

 To create the default job

1. Log in to Envision for BACtalk as Local Administrator.

2. On the Tools menu, click Set Rep and Job.

N o t e The Set Rep and Job item on the Tools menu appears only when
logged in with the appropriate privileges.

3. Type a Rep name and Job name according to the following guidelines:
Rep Name This is the name of the job directory. 
IMPORTANT! Do not use numbers in the rep name.
Job Name The name of the subfolder (up to eight characters) that will
be created under your Rep name to store job information.

4. Click Options to expand the dialog box.

5. Click Create Directory.

This creates a job directory for your new job. For example, a job
directory might be C:\Alerton\BACtalk\3.0\Myrep\Myjob.

6. Click Make Key.

This allows users to modify data displays and DDC on this computer.

7. Click Select and restart Envision for BACtalk to activate your changes.
N o t e You can create as many jobs as you want in one session, but the
job that appears in the Set Rep and Job dialog box is the default when
Envision restarts.

8. Set up an Initial User profile. (See page 37 for more information)

9. Restart Envision for BACtalk and log in with the initial user’s name and
password.

10. On the Tools menu, click Users and Groups, and then create at least
one user profile so users who are not the Local Administrator or do not
have the initial user’s name and password can log in to the job.

Using BACtalk for Windows job data in Envision for BACtalk

WARN ING Significant changes were made to the BACtalk database structure
in versions 2.5, 2.6, and 3.0 to improve system performance, stability and
security. Once a job is upgraded to 2.5 or later, it cannot convert back to an
earlier version of BACtalk. Back up the current job before upgrading.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 41

Installation and Startup Guide | Envision for BACtalk

If you upgraded to Envision for BACtalk from BACtalk for Windows v3.1x, you
can use the job data from the previous installation.

• If you installed Envision for BACtalk on the same operator workstation

that was running BACtalk for Windows, use the Import button in the Set
Rep and Job dialog box.
• If you installed Envision for BACtalk on a different operator
workstation, copy the job backup file to the new computer, and then use
the BACtalk Restore Utility in the Envision for BACtalk program
group.

Importing an existing job

If Envision for BACtalk is installed on the same operator workstation that was
used to run a previous BACtalk version, you can save time by importing the
existing job files. Import is available when Envision for BACtalk is running;
otherwise, you restore data. Import is only for jobs running in the default
location, it is not for jobs installed to a custom location.

1. Start Envision for BACtalk, configure the Local Administrator user ID

and log in.

2. On the Tools menu, click Set Rep and Job.

3. Click Options to expand the dialog box.

4. Click Import.
The Import Rep/Job dialog box displays a list of previous BACtalk
versions.

5. Select a previous BACtalk version from the list.

6. In the list of Rep/Jobs, select the job you want to import, and then click
OK.

Restoring a BACtalk job

The enhanced Restore Utility (BACtalk > Device Manager > [select a device] >
Advanced > Restore Devices) allows you to choose what you want to restore: an
entire backup, only those files needed by a client workstation, or merge a smaller
new job with a larger job. These new capabilities may reduce the time it takes to
restore your data.

WARN ING Read this section before attempting to back up and restore job data
and follow the instructions carefully to ensure successful data migration.

Before you begin restoring

• Merging BACtalk data into an upgraded Envision for BACtalk job is
both a backup and a restore process so it may take an entire shift or
longer, depending on the job. Plan ahead so you start the backup at the
end of one day and the restore at the start of the next day. For planning
purposes, expect the process to take about 1 hour per GB. Remember,
BACtalk jobs will be much larger after the conversion from legacy
versions.
• You can only restore conventional (Access/Jet) data in BACtalk. Do not
attempt to back up and restore SQL Server data using Envision for

42 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

BACtalk. Back up and restore conventional data and then configure the
restored job for SQL Server.
• Always merge a smaller job into a larger job. For example, merge a new
school building into the school district job and not the school district
into a single school building.
• Do not back up a job to a mapped network drive. Performance will be
slow due to other users on the same network.
• You must use unique device instances. The Restore Utility will not
overwrite existing files with the same name in newer versions of
Envision for BACtalk. Make sure all the files you need to add to an
existing upgraded database have a unique name or the restore process
will skip over them.
N o t e Merge data into an upgraded Envision for BACtalk job only
since some legacy databases may have files that will be overwritten.
• Make sure the job you are going to back up does not have any extra files
you don’t want to back up in it or you may restore files you do not need
or want into another job.
• Only data you backed up gets merged. DDC does not get merged.

Figure 4 The Restore a BACtalk Job dialog box

Restore Entire Backup

Use this feature to restore an entire server backup to the target job on an
upgraded BACtalk server or an entire client backup to the target job on an
upgraded BACtalk client workstation. This option restores all data that was

© Honeywell LTBT-TM-ADMIN30 Rev. 05 43

Installation and Startup Guide | Envision for BACtalk

backed up from the original job. SQL Server data is not backed up nor restored
by Envision for BACtalk. The database administrator must handle the SQL
Server backup and restore operations.

The BACTALK.INI and REP.INI files do not get backed up or restored because
they contain settings that apply to all jobs on a workstation and not individual
job settings. Manually copy these files if you want to configure an identical
workstation.

Restore Client Components

Use this option to restore only those files used by BACtalk client workstations.
You may use this option if the backup was made at either client or a server.
Databases not directly used by client workstations are not restored nor are the
device or archive directories. This enables a single backup of an entire job on the
server to be used to initialize or update client workstations. In particular,
displays, bitmaps and remote connections are restored. Restoring only the files
you need should significantly reduce the time it takes to restore your data.

This restore option restores the following BACtalk client components only:

• Application database (Appdb.mdb)

• Displays directory content
• Bitmaps directory content
• DDC directory content
• site.key
• Remote site setup (localconfig.mdb)

Restore Merge Components

Use this option to restore merged job data from a backed up smaller BACtalk job
into a larger upgraded BACtalk job. It restores only the files that do not already
exist in the target job and components merging into the target job. Files that
already exist in the target job are not overwritten.

After the Restore Merge Components function completes, restart Envision for
BACtalk in the job you want to merge into and the new data will merge from the
backup into the target job.

44 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

This restore option merges the following BACtalk components only:

• User profile setup

• Device manager setup
• Trendlog Setup
• Energy Log Setup
• Alarm History
• Remote Alarm History
• Cross-reference database
• Bitmap files that do not exist in the target job
• DDC files that do not exist in the target job
• Display files that do not exist in the target job
• All defined objects for devices that do not exist in the target job
(schedules, calendars, zones, notification classes, EEOs, etc.)
• Point data for devices that do not exist in the target job (pointdata.mdb)

This restore option does not restore the following files, some of which could
break the configuration settings of an upgraded Envision for BACtalk job:

• Remote site setups (localconfig.mdb)

• profile.ini
• site.key
• device.cfg
• Custom Process IDs
• Tenant activity setups
• Event logs (energy log calculation errors, database archive log, tenant
activity diagnostic log, backup status log)
• Trendlog sample data
• Energy log calculation data
• Report setups
• User Activity log data
• Point data for devices that already exist in the target job
• Data objects for devices where the object already exists for that device
N o t e New objects for devices that already exist will be restored.

 To merge new data with a conventional Envision for BACtalk job

Note Server1 is Online and running a conventional Envision for BACtalk

database. Server2 is Offline and running BACtalk.

1. Back up the target job on Server1 (Online).

2. Restore it to Server2 (Offline) for development.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 45

Installation and Startup Guide | Envision for BACtalk

3. Create a new conventional BACtalk job on Server2 (for example, new

devices or a new school building to add to an existing school district
job) and merge it with the backed up target job from Server1.

4. Back up the new merged conventional job.

5. Restore the backup of the merged conventional job to Server1.

6. If desired, convert to SQL Server and then complete the job

configuration.

 To merge new data with a SQL Server Envision for BACtalk job

Note Server1 is Online and running a SQL Server Envision for BACtalk
database. Server2 is Offline and running BACtalk.

1. Create a new conventional BACtalk job on Server2 (for example, add

new devices or a new school building to an existing school district job,
or add a new building to an existing campus job).

2. Back up the new job on Server2.

3. Merge the backed up job with the target job on Server1and then restart
Envision for BACtalk in the target job to complete the merge process. 
Data automatically gets stored to the SQL Server database.

4. Complete job configuration on Server1.

Verifying General System Setup

Use the General System Setup dialog box to define settings that apply to a
particular operator workstation and how it is used within the BACtalk system.
Depending on the installation type, verifying system setup may include the
following. See the quick steps (beginning on page 10) for your installation type
for a list of the tasks that apply.

• Set the device instance for the operator workstation. This determines
how this operator workstation is identified to other devices on the
BACnet network.
• Verify the Ethernet setup. This determines how this operator
workstation communicates with other devices on the BACnet network.
• Identify the operator workstation as a server or client. See “Setting up a
client/server relationship” on page 29 for detailed instructions.

 To set the device instance for the operator workstation

1. Start Envision for BACtalk and log in.

2. On the Tools menu, click General System Setup.

3. On the Identification tab, type a device instance for this operator

workstation.

4. Type a name and a description for the operator workstation.

5. Click OK, or continue with the next procedure.

46 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

 To verify Ethernet setup

1. In the General System Setup dialog box, click the Network tab.
N o t e If there is no Ethernet Adapter to select in the drop-down device
list on the Network tab, the BACtalk communications protocol has not
yet been installed. See page 21.

2. Select the primary Ethernet adapter from the list.

N o t e If you installed the BACtalk communications protocol driver,
the primary Ethernet adapter entry initially appears as None.

3. If necessary, select the Enable BACnet protocol option.

This option must be selected to allow this operator workstation to use
the BACnet protocol to communicate with other BACnet devices.
-OR-
Select the Enable “Annex J” BACnet/IP option if this operator
workstation communicates with other BACnet devices over an IP
network.

Creating user profiles

When you log in as the Local Administrator and create a new job, the job does
not have any user profiles created for it; you must create them from scratch.
Until the Local Administrator creates user profiles, only the Local Administrator
can access the job (in offline mode). For more information about user profiles,
see the Envision for BACtalk Operator’s Manual (LTBT-OP-EBT). See
“Configuring the Local Administrator” on page 23 for more information about
the Local Administrator user ID.

IMPORTANT! Do not edit user profiles in previous versions of Envision for

BACtalk for use in later versions since not all capabilities are available in
previous versions.

Managing user privileges

User privileges determine features, activities, and devices a user can access and
groups to which they are members. For example, you may allow some users to
perform several tasks related to alarms, including setting up new alarms. Other
users may be given permissions to view and acknowledge alarms, but not to
create new ones. Some users will have certain device privileges while others do
not. Users may be assigned to multiple groups.

Using security levels

The security level of a user profile determines the access each user has to items
on data displays such as pushbuttons. For example, items on a data display may
require a security level of 5 or above. If a user is assigned a security level less
than 5, the item on a data display will be unavailable or appear not to work.
However, the Effective Security Level (displayed next to the user Security Level
on the Add/Edit User dialog box) takes into account the security level defined
for the user and the security levels defined in all groups of which this user is a
member. The Effective Security Level is the highest of all of those and is the
security level that will actually be used when BACtalk determines whether to
allow the user access to certain display items. So, if one of the user’s groups has

© Honeywell LTBT-TM-ADMIN30 Rev. 05 47

Installation and Startup Guide | Envision for BACtalk

a security level of 7, the user will be able to access data display items that are
security level 7 and below.

Using an authorized period

Use the Authorized Period feature to give users with assigned privileges access
to a BACtalk system or set the date when you know a trustworthy user should be
automatically locked out of BACtalk. Unrestricted access allows valid users to
use the system at any time after successfully logging in.

Set up the system to automatically lock out trusted users when they are
scheduled to be off the job for a period of time and are expected to have future
access. You want to preserve their user profile. Once the authorized period is
scheduled, BACtalk will automatically lock the user out of the system when the
server registers midnight on the expiration date.

For a user you want to permanently lock out of BACtalk, delete the user’s
profile. Deleting the user ID does not impact records in the User Activity Log.
Deleted user IDs can be reused but no previous user settings are preserved.

Using group memberships

Users may be managed by group assignment. Users are assigned privileges and
data access through their user profiles, and they can gain additional privileges
and access through group memberships. Trendlog, alarm history, schedules and
all other items associated with BACnet device items can be filtered by group. Set
up groups by floor, building, campus, city or any other categorization strategy
and then switch data views as you work to see different groups’ data.

 To create new user profiles for a job

1. On the Tools menu, click Users and Groups.
The Users and Groups dialog box appears with a list of current users. If
the job is a new one, no users will be listed.

2. Click Add.

3. On the General tab, type a User ID, name, and description in the boxes
provided.
User IDs must be from 1 to 40 characters. Spaces, numbers, lower and
upper case letters are all valid characters.

4. In the Security Level box, type a security level from 0 to 10 (0 is the

lowest level of access; 10 is the highest).

5. Type a password in the box provided.

Passwords must be 3 to 20 characters, numbers and letters only, and
they are case-sensitive.

6. Click the Starting Display command button, select a starting display or

device template for this user, and then click OK. If you do not specify a
start display, and the user is not assigned to a primary group with a
specified start display, the system default start display (1) will be used.

7. Specify the user’s authorized time to access the system.

This can be used to lock a user out during personal time off, especially
when their departure and return dates are known. 
NOTE: Users that should no longer have access to the job should be

48 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Job setup and engineering

deleted, not expired. Deleting a user ID does not affect records in the
User Activity Log.

8. On the User Device Access and Privileges tab, specify the range of
devices this user shall have access to and then select privileges for this
user. Click the plus (+) symbol to expand the level of detail. Select
check boxes beside a feature to enable access for this user. A check
mark indicates full access. A grayed box indicates partial access within
a feature category. A cleared box indicates no access.

9. On the Group Membership tab, assign this user to a group, if desired. 

The Primary Group column displays which group start display this user
will use if their user profile doesn’t have an assigned start display.

10. On the Effective Device Access and Privileges tab, specify which
devices for which this user has access and privileges. The Effective
Device List displays a complete list of all the devices this user has
access to, even devices he can access due to group membership that
exceed his/her individual user access.

11. Click OK to save the user profile.

12. Repeat steps 2 through 11 for each user profile you want to create.

13. Click Close when you have finished adding user profiles.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 49

Installation and Startup Guide | Envision for BACtalk

Understanding Device Manager

Device Manager stores and displays relevant information about the devices
installed in a building. Understanding Device Manager entries and the tasks you
can perform there will help you make maximum use of this tool.

Device Manager is the master database of all of the BACnet devices in a

building. Using Device Manager, you can view and change device properties,
update information identifying a device, and configure device settings.

Device Manager serves as an engineering tool to set up a job with all the devices
used in that job. Use this guide to learn how to add a device to Device Manager
by providing the following descriptive information about the device:

• A unique identifier for the device, the device instance

• The device type, for example, operator workstation, global controller, or
unitary controller
• A description of the device, for example, SUB: ACU-21-501 Kitchen
• Device capabilities, such as the features it supports
• DDC application that controls the device
• Host controller where schedules, trendlogs, and alarms are stored

Once the system and devices are installed and set up, Device Manager serves as
a site management tool. See the Envision for BACtalk Operator’s Manual
(LTBT-OP-EBT) for more information about using Device Manager to:

• Add, edit, copy, or delete a device profile

• Send data between the Device Manager table and devices
• Save point data to reflect changes at controllers
• Scan the BACnet internetwork for BACnet-compliant devices and then
add them to the Device Manager table
• Change property descriptions
• Download a ROC file
• View a list of new devices
• Back up a device
• Restore a device
• Restart/control a device
• Renumber VLCs
• Send DDC files or save the DDC rep, job, and application name
• Perform time synchronizations
• Check the online or offline status of a device
• Print the Device Manager table
• Configure an Alerton configurable device from a remote location

50 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Defining device profiles

Each device in a BACnet network must have an entry in Device Manager. If a
BACnet device does not appear in Device Manager, Envision for BACtalk will
not communicate with it, and certain features will not be available for the device.

Device Manager is a database, a master table of the BACnet devices in a system.

Each record in the database is a device profile. The device profiles consists of
three major components:

• Identification includes the information that describes and distinguishes

one device from another, such as its device instance, MAC address,
location, object name, and description.
• Capabilities are the attributes and features that a device supports, such
as schedules, trendlogs, and DDC.
• Preferences include the UTC setting, the DDC application that controls
the device, and the host device that stores trendlogs, schedules, and
communication alarms for the device.

Identification
You set up device profiles in Device Manager using the Add/Edit Device Profile
dialog box. The Identification tab allows you to enter or display the following
information about a device.

Device instance A unique identifier for the device. Each device on

the BACnet internetwork must have a unique
device instance. Device instances appear in lists
and are referenced throughout Envision for
BACtalk. Read only.
Unit type Identifies the type of the device - workstation,
global controller, building controller, advanced
unitary controller, unitary controller, viewport,
gateway, or router. What you select here appears
under Unit Type in the Device Manager window.
Description Additional descriptive information that helps users
identify a device and its function.
Object name A unique name for the device, which along with
the device instance, identifies the device
throughout the BACnet internetwork.
Device location Additional descriptive information that identifies
the device location, for example, “Air handler on
roof.”
Network The Ethernet or MS/TP network where the device
resides. Each individual BACnet network must
have a unique address number throughout the
internetwork.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 51

Installation and Startup Guide | Envision for BACtalk

MAC address The unique MAC address for this device. All
devices on a BACnet internetwork must have a
unique MAC address/Network number
combination. For global controllers, BACtalk
control modules, expandable controllers, and
operator workstations, this number is hard-coded
in the network interface card.
Device model The model name assigned by the manufacturer.
Read only.
Firmware version The firmware version assigned by the
manufacturer. Read only.
Application software The application software (ROC file) loaded on the
device. Read only.
Commissioning status The date this device was commissioned and the
technician who commissioned it.

Note Each BACtalk control module (BCM) has its own device instance and
each is set up separately as a global controller in Envision for BACtalk. (The
BCM-PWS and BCM-MDM are exceptions; they do not have device instances
and do not appear in Envision for BACtalk’s Device Manager.)

Device capabilities
A device profile also includes the capabilities or attributes that a device supports.
If a particular capability isn’t selected for a device in Device Manager, the device
cannot support it in Envision for BACtalk. On the Capabilities tab in the Add/
Edit Device Profile dialog box, you can select attributes for devices in one of
four ways:

• Poll the device to automatically assign capabilities that apply

(recommended for Alerton devices)
• Assign capabilities based on the device type by scanning for the device
• Manually select the applicable capabilities that the device and ROC
version support
• Assign default capabilities by selecting one of the device types from the
Auto-Select menu

Capabilities tell Envision for BACtalk how to talk to connected devices. Default
capabilities are assigned when you select a device type from the Auto-Select
menu on the Capabilities tab in the Add/Edit Device Profile dialog box. These
are the minimum capabilities for the device type selected. You may need to
modify the selections, depending on the specific device you are defining. Default
capabilities are used when upgrading from BACtalk for Windows 3.1x.
Capabilities are assigned based on the device unit type previously defined in the
Device Manager table. Incorrectly selected capabilities results in inoperable
schedules, trendlogs and alarms. Make sure you are using the correct ROC
version. See “Device capability descriptions” on page 53 for a brief description
of each capability.

Note The most accurate method to set capabilities for any device is to either
scan or poll the device. If working offline, poll the device once you are
connected to ensure that the correct capabilities are selected.

52 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Device capability descriptions

Table 3 gives a brief description of device capabilities.
Ta ble 3 Device capability descriptions

Device capability Description How to use When checked, it does this

Prefers UTC time Worldwide standard for time and Use this option when devices Envision for BACtalk sends a
sync over local time date. This standard is span multiple time zones. notification to each UTC
sync coordinated universal time, Normally you would not check recipient and the controllers will
abbreviated UTC. This was use their preset UTC offset to
(BACnet - UTC Time this option even though a Device
formerly known as Greenwich determine its local time itself.
Synchronization Manager auto-scan of device
Service) mean time (GMT). It is important capabilities may check this item.
to ensure that all devices on the
Normally unchecked as most
BACnet network have the
sites use local time.
correct time.
Causes Envision for BACtalk to
NOTE: The UTC offset for your
send a UTC time sync instead of
time zone is normally set within a local time sync (PC clock
the Alerton global controllers
time).
and in Device Manager's
preferences. BACnet says its
purpose is to notify the recipients
of the correct UTC so that
devices may synchronize their
internal clock.

Send UTC offset UTC time offset is a property of The UTC offset for your time Sending UTC will cause the UTC
property to device the device object. It is used to zone is normally set within the offset value from Device
(BACnet-Device denote the geographic location Alerton global controller and in Manager>Preference>UTC
and its corresponding time. It is Device Manager's preferences. offset to be used. This will
Object>UTC_Offset
used to synchronize clocks in The UTC offset is taken from overwrite the controller setting.
property
network devices. Device Managers Preference
settings tab.
The UTC offset can be set in the
following ways:
1) Sent using Device Manager
using the value entered on the
Preferences tab.
2) Adjusted using HyperTerminal
when connected to the global
controller.
3) Remote device configuration
editor.
4) From a Data Display (BACnet
property).
5) General System Setup>Time
Sync.
NOTE: UTC is internally linked
to the Tenant Billing program
and if UTC is not implemented
for your time zone, Tenant Billing
will not be calculated and display
the correct data.

Supports schedules The Schedule Object type Create schedules that reference Checking this capability allows
(BACnet Schedule defines a standard object used points within the selected you to create schedules that
to describe a periodic schedule device. An example controller of reference points within the
Object
that may recur during a range of this type includes the VLCP, selected device. This capability
dates, with optional exceptions which did not support additional may not be set when “Supports
at arbitrary times on arbitrary MSTP controllers. schedules with external points”
dates. is checked.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 53

Installation and Startup Guide | Envision for BACtalk

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Supports schedules The Schedule Object type Create schedules that reference Checking this capability allows
with external points defines a standard object used points within the selected device you to create schedules that
to describe a periodic schedule (e.g. global controller) or points reference points within the
(BACnet Schedule
that may recur during a range of on other network devices (e.g. selected device or points on
Object)
dates, with optional exceptions VLC controllers). other network devices. This
at arbitrary times on arbitrary capability may not be set when
dates. “Supports Schedules” is
checked.

Supports BACnet par- Device supports schedules as Envision for BACtalk adds partial Identifies the device as
tial-day scheduling day scheduling to the schedule supporting BACnet Protocol
defined in the BACnet Protocol
(BACnet) object. Version 1, Revision 4 schedules.
Version 1, Revision 4. This setting is used in
conjunction with the “Supports
schedules” or “Supports
schedules with external points”
device capabilities

Supports calendar The Calendar object type Envision for BACtalk does not Checking this capability allows
defines a standardized object use the calendar object in its the Envision for BACtalk server
(BACnet Calendar
used to describe a list of standard schedule interface, to create calendar objects in the
Object)
calendar dates, which might be rather the schedule object is selected device (disk file or
thought of as “holidays,” “special used. Alerton global controllers global controller).
events” or simply a list of dates. such as the BCM-ETH, BCM-
MSTP, etc. do support these cal-
endar objects (See PICS for
supported BIBBs and Objects).
To use the calendar object the
user must use
Tools>Advanced>Calendars
and set the parameters there.

Supports alarms The Event Enrollment object Create alarms that reference Checking this capability allows
(EEO) type defines an event points within the selected you to create alarms that
(BACnet Event
Enrollment Object) (e.g. Alarm) and provides a device. The EEO will monitor the reference points within the
connection between the alarm state and provide a selected device. This capability
occurrence of an event and the notification to the alarm handler may not be set when “Supports
transmission of a notification for distribution to alarm alarms with external points” is
message. recipients. checked.

Supports alarms with The Event Enrollment object Create alarms that reference Checking this capability allows
external points (EEO) type defines an event points within or without the you to create alarms that
(e.g. Alarm) and provides a selected device. The EEO will reference points within the
(BACnet Event
connection between the monitor the alarm state and selected device or points on
Enrollment Object)
occurrence of an event and the provide a notification to the other network devices. This
transmission of a notification Alarm handler for distribution to capability may not be set when
message. alarm recipients. “Supports alarms” is checked.

Supports alarm dia- Identifies the device as a BCM modules support alarm dial Enables dial out communication
lout controller with modem dial-out out via the BCM-MDM. BTI- capabilities.
support. MDM (on board modem), BTI-
(Alerton proprietary
100 and VLX support alarm dial
out via serial communication
port to a connected modem. BTI-
Smoke does not support alarm
dial-out.

54 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Supports BACnet The Event Enrolment object type Create alarm that reference Select this option to enable the
event enrollment defines an event (e.g. Alarm) points within or outside the device to host an event
object and provides a connection selected device. The EEO will enrollment object (BACnet rev
between the occurrence of an monitor the alarm state and 4,alarm setup).
(BACnet)
event and the transmission of a provide a notification to the
notification message. Alarm handler for distribution to
alarm recipients. When used in
combination with the Alerton
Alarm capability option, the
combined result is an EEO setup
that is formatted as defined in
the BACnet Standard Protocol
revision 4

Supports current Device supports the BACnet Indicates the device will support Allows the device to be scanned
alarms report Get-Event-Summary service. Envision for BACtalk's “Current for current alarm
Alarms” feature.

Supports alarms for Device communication failure The Device Comm fail object is Selecting this option allows Aler-
communication failure alarms notify users with a pop- created in the global controller. Dev-Comm-Fail objects to be
up alarm message that The global controller hosting the sent to devices. For example, to
(Alerton proprietary)
communication between the object will periodically poll to see monitor communication between
server and a device has been if the devices are present. If one global controller and the device.
lost. is detected as absent, a Further setup is required to fully
notification is popped-up on the deploy this feature; refer to
workstation. online Help.

Supports Alerton pro- The Process ID is a component Alerton global controllers use Select this option to indicate that
cess IDs of the BACnet Destination used these process IDs in a the device can send, receive,
(Alerton proprietary) by the Notification Class Object predictable way. The same and support pre-defined or
to deliver a notification to a process IDs are used repeatedly custom Alerton process IDs for
recipient. For example, pop-up, when a user adds new pagers or event notifications
log, page, or e-mail the alarm, e-mail recipients; the new
etc. process IDs are created
dynamically. Also, some 3rd
party controllers may create
these process IDs manually, so
the user may have to configure
this in the BACtalk server to get
3rd party alarms to pop-up,
annunciate, and log to alarm
history.

Supports alarm poll- Not Used Not Used Not Used

ing rate
NOT USED...Feature
not implemented

Initiates event notifi- Controls EBT Event Summary Auto-select this option and leave If the device generates event
cations UI drop down lists showing only it at the default setting. notifications (alarms or
devices checked. trendlogs), the user will now be
(BACnet)
able to use Event Summary,
Alarms and Trendlogs features.

Supports trend log Alerton trendlogs (proprietary Create trendlogs that reference Checking this capability allows
objects format). Alerton created a trend- points within the selected you to create trendlogs setup
log format in advance of the device. that reference points within the
(Alerton proprietary or
BACnet standard definition. This selected device. This capability
BACnet) If this capability is used without
proprietary object is used to log the “Supports BACnet Trendlog” may not be set when “Supports
data within Alerton controllers. trendlog objects with external
capability, an Alerton log is
points” is checked
May or may not be an Alerlog created (proprietary format).
(See Supports BACnet trendlog
capabilities setting).

© Honeywell LTBT-TM-ADMIN30 Rev. 05 55

Installation and Startup Guide | Envision for BACtalk

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Supports trend log Alerton trendlogs (proprietary Create trendlogs that reference Checking this capability allows
objects with external format). Alerton created a trend- points within the selected device you to create trendlogs that
points log format in advance of the (e.g. global controller) or points reference points within the
BACnet standard definition. This on other networks (e.g. VLC selected device or points on
(Alerton proprietary or
BACnet) proprietary object is used to log controllers). another network. This capability
data within Alerton controllers. may not be set when “Supports
If this capability is used without
trendlog objects” is checked.
May or may not be an Alerlog the “Supports BACnet trendlog”
(See Supports BACnet trendlog capability, an Alerton log is
capabilities setting) created (proprietary format).

Supports BACnet A trendlog object monitors a When used in combination with Select this option to configure
trendlog capabilities property of a referenced object the Alerton Trendlog option, the the device for BACnet trendlog
and, when predefined conditions combined result is a trendlog reporting.
(BACnet-Trend Log
Object) are met, saves the value of the setup that is formatted as
logged property and a defined in the BACnet Standard
timestamp in an internal buffer Protocol revision 4.
for subsequent retrieval.

Supports trend log Trendlog samples are logged COV trendlogs show changes in Enabling this feature tells the log
objects with COV when the value of the monitored the values of monitored handler to subscribe to the
capabilities point changes. Can be properties. COV logging reduces monitored point. When the value
configured to log samples the total number of samples in of the point changes, the device
periodically in addition to COV the database. notifies the log handler and the
samples. value is logged.

Supports Alerton The Zone object is an Alerton A zone object pulls together the Checking this capability allows
zone objects proprietary object with an individual properties and you to create zone objects that
associated set of properties. references required to support reference points within the
(Alerton proprietary)
optimum start or tenant activity selected device. This capability
in a single object. It handles the may not be set when “Supports
user-defined inputs specified zone objects with external
during the zone setup to monitor points” is checked.
and control schedules, optimum
start, and tenant activity.

Supports Alerton The Zone object is an Alerton A zone object pulls together the Checking this capability allows
zone objects with proprietary object with an individual properties and you to create zone objects that
external points associated set of properties. references required to support reference points within the
(Alerton proprietary) optimum start or tenant activity selected device or points on
in a single object. It handles the another network. This capability
user-defined inputs specified may not be set when “Supports
during the zone setup to monitor zone objects” is checked.
and control schedules, optimum
start, and tenant activity

Supports Alerton The Demand Limiting object is Envision for BACtalk enables Checking this capability allows
demand limiter an Alerton proprietary object you to monitor energy demand you to create demand limiter
objects with an associated set of and then automatically adjust objects that reference points
(Alerton proprietary) properties. equipment operation to limit the within the selected device. This
demand and reduce costs. This capability may not be set when
NEVER USED... is known as demand limiting. Supports demand limiter objects
because demand with external points is checked.
limiter refers to I/O in
external devices

Supports Alerton The Demand Limiting object is Envision for BACtalk enables Checking this capability allows
demand limiter an Alerton proprietary object you to monitor energy demand you to create demand limiter
objects with external with an associated set of and then automatically adjust objects that reference points
points properties. equipment operation to limit the within the selected device or
demand and reduce costs. This points on another network. This
(Alerton proprietary)
is known as demand limiting. capability may not be set when
Supports demand limiter objects
is checked.

56 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Acts as primary Specifies primary controller for Displays the device instance of For features that need a host
controller the job. the host device that hosts device (trendlogs, schedules,
trendlogs, schedules and alarms alarms), if the host device is not
for properties in this device. For configured for a particular device
VLCs, choose the controller (say device 10), when adding a
physically closest to the device new trendlog from device 10, the
to reduce communication errors primary host device would be
and improve performance. For selected as the default value.
expandable controllers and
global controllers, select the
controller itself

Supports Viewport Viewport displays are used by Envision for BACtalk has a Checking this capability allows
displays the Alerton Viewport Controller Viewport Display editor that the Envision for BACtalk server
(Alerton proprietary) and permits the user to logically allows the user to create Device Manager to send/save
group elements that are displays for the Viewport Viewport Displays to a
displayed on a multi-line product, and those displays can connected device
controller with a LCD display. later be sent via Device Manager
directly to the Viewport

Acts as operator Controls EBT user interface Auto-select this option and leave The operator workstation will
workstation drop-down lists showing only it at the default setting. appear in the related drop down
(Alerton proprietary) workstations. list, like e-mail workstation.

Supports Device Identifies VLCs that allow the To renumber VLCs. Enables user to renumber VLC
Instance renumbering device instance (BACnet-Device NOTE: Global controller device device instance (BACnet-Device
object identifier) to be changed. object identifier) with Device
(Alerton proprietary) instances are changed using
Manager: Advanced-
HyperTerminal or the remote
device configuration editor. >Renumber VLCs.

Supports Alerton BACnet service used by a Alerton workstations (server or When this capability is selected,
read/write multiple BACtalk operator workstation client) and global controller DDC the “Send device properties”
properties (server or client) to request can issue RPM/WPM messages option in Device Manager sends
values of one or more specified to VLCs or global controllers the current RPM/WPM settings
(BACnet)
properties of one or more which support the RPM/WPM as in Envision for BACtalk's Gen-
BACnet objects. noted on the respective PICS. eral System Setup to the
selected device. This specifies
the policy for the selected device
on whether or not to use RPM/
WPM (even when the device
indicates it does not support
those) when issuing a request to
non-Alerton devices and older
Alerton devices.
Some 3rd party BACnet
controllers may not support the
Read/Write Property Multiple
service. Refer to the PICS to
determine if it supports this
feature. If it does not, ensure this
capability is not selected.

Supports Alerton TUX IBEX TUX (.tdc) controller binary The .tdc files are created from Enables you to send/save your
DDC file format of a DDC application. IBEX VisualLogic, Envision for TUX DDC applications for IBEX
IBEX software>TUX DDC editor, programmable TUX controllers
(Alerton proprietary)
and TDS (TUX Development listed in Device Manager.
Software).
NOTE: The Save operation
NOTE: Only Alerton IBEX saves the DDC file *.tdc to the
programmable controllers ...\Rep\Job\DDC\ folder.
(APLC, 653P, etc.) support this
device capability.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 57

Installation and Startup Guide | Envision for BACtalk

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Supports Alerton Alerton global controller binary The .bd3 files are created from Enables you to send/save your
DDC type bd3 file format (.bd3) of a DDC VisualLogic DDC drawings or by DDC applications for global con-
application. using the Global/Building DDC trollers listed in Device Manager.
(Alerton proprietary)
editor. The files can be retrieved
NOTE: Header information only
from a controller and re- is saved; not the actual files. Use
engineered as needed.
global controller DDC or
VisualLogic to retrieve the files.

Supports Alerton Alerton VLC (Visual Logic The .bd4 files are created from Enables you to send/save your
DDC type bd4 Controller) controller binary file VisualLogic DDC drawings or by DDC applications for VLC con-
(Alerton proprietary) format (.bd4) of a DDC using the VLC DDC editor. The trollers listed in Device Manager.
application. files can be retrieved from a
NOTE: Header information only
controller and re-engineered as
is saved; not the actual files. Use
needed. global controller DDC or
VisualLogic to retrieve the files

Supports Alerton Alerton Advanced VLC (Visual The .bd6 files are created from Enables you to send/save your
DDC type bd6 Logic Controller) controller VisualLogic DDC drawings or by DDC applications for VLC con-
binary file format (.bd6) of a using the Advanced VLC DDC trollers listed in Device Manager.
(Alerton proprietary)
DDC application. (green) editor. The files can be NOTE: Header information only
retrieved from a controller and
is saved; not the actual files. Use
re-engineered as needed.
global controller DDC or
VisualLogic to retrieve the files

Supports Alerton Real-time-Operating-Code Download these files using Allows users to use Device
ROC (OMF/BIN) (ROC) is the helper application Device Manager. Alerton con- Manager to download ROC files
(Alerton proprietary) that defines the controller trollers are pre-loaded with a for this device
characteristics and features. It is ROC file. The latest ROCs are
downloaded to the controller in available on the ASN. Be sure to
advance of any control logic. use the correct ROC files for the
The file extensions are *.omf and front-end software. See KBA
*.bin. http://asn.alerton.com/Products/
downloads-rocs.aspx
NOTE: Identify the ROC file in a
global controller or VLC by
reading the Device Object>
Application Software Version.

Supports remote con- Enables users to scan and Configuration settings such as Enables users to send/save
figuration configure this device from a Device instance, Ethernet net- configuration settings to the
remote location. work, MSTP network, BACnet IP selected device using
(Alerton proprietary)
settings, etc. can be set via an EBT>Device
Envision workstation (server or Manager>Configure
client). Optionally, these set-
tings can be configured using
HyperTerminal via null modem
cable and a serial port connec-
tion.
The controller configuration
settings can be set, written, read
and saved as a data file. The
default file location\name is
\rep\job\devnnn*\devconfig.dcf.
The devconfig.dcf can be
opened using Notepad. *nnn is
the device instance (e.g.
\\\dev1234...).

58 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Ta ble 3 Device capability descriptions (Continued)

Device capability Description How to use When checked, it does this

Supports Alerton VAV VLCs such as VAV-xx or VAVi- Device Managers Send/Save NOTE: All Alerton VLCs auto
flow sensor setup xx each have an on-board flow writes/reads the VAV flow configure this setting as checked
sensor (velocity sensor), this sensor’s parameters to/from by default. However, the
(Alerton proprietary)
sensor has setup parameters pointdata.mdb to/from the practical application for this is
used for balancing and device. Writing/reading these VAV controllers. It is acceptable
reporting. values to/from a VLC does not to leave the default set for all
cause any system issues. VLCs.

Supports BACnet Enables the Envision server to To save and restore a BACnet Back up devices that have the
backup and restore back up BACnet compliant compliant devices configuration BACnet backup device capability
devices that have the BACnet data. A password is required selected in their device profile.
(BACnet- Backup and
Restore) backup device capability when backing up devices. You Device Manager: Select
selected in their device profile. can also select a character set (if
Advanced->Back up Devices...
necessary) and define a timeout
Or -> Restore Devices...
period after which the back up
process is stopped.
Password: Type the password
defined for the selected
device(s). The default password
for all Alerton controllers is
ALERcomm (case-sensitive).
Character set: This is the char-
acter set recognized by the
selected devices. ANSI X3.4 is
selected by default. You can
select ISO 8859-1 if appropriate.
Timeout: This is the amount of
time, in seconds, in which
Envision for BACtalk attempts to
back up a selected device before
stopping. If all of the devices use
the same timeout value, the
value is displayed here by
default. A valid timeout value is
between 10 and 65535 seconds.

Acts as a smoke Password protects the controller Select this capability and then Forces the user to enter a
controller so users can only download set the password. Remember password to send DDC, device
DDC to it if they enter the the password so you can configuration or Point Data to the
password. Protects some download DDC to this smoke device. Prevents unauthorized
systems from being modified in controller. users from modifying controllers
ways that prevent them from that have been configured as
functioning appropriately during part of a smoke system.
a smoke event.

Preferences
Use the Preferences tab in the Add/Edit Device Profile dialog box to identify the
DDC application that will control this device. You also use the Preferences tab to
identify the host controller for the device. This is where the trendlogs, schedules,
and alarms for the device are stored and run.

Do Not select the Auto Download option to automatically send a ROC file from
the operator workstation hard disk to controllers if it is different than the file on
the device. This automatic download occurs once a day at midnight. Instead,
ROC file downloads should be done under the direct supervision of a trained
technician only.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 59

Installation and Startup Guide | Envision for BACtalk

WARN ING Auto Download does not send DDC or objects. Safeguard your
DDC, schedules, trendlogs, alarms and other objects.

Setting the UTC offset

You also use the Preferences tab to set the UTC offset for a device. This setting is
sent to devices when Device Manager sends device properties. If this value is
incorrect it can cause the device’s clock to be incorrect which would cause tenant
activity and trendlog data to have incorrect time stamps. Before you can enter a
setting, you must select “Send UTC offset property to device” on the
Capabilities tab.

Coordinated Universal Time (UTC) is the international time standard. UTC

starts on the Prime Meridian in Greenwich, England. The Prime Meridian is an
invisible line that runs between the North Pole and the South Pole. Midnight in
Greenwich is zero (0) hours because it lies on the zero longitudinal meridian.
Locations to the East of the Prime Meridian are positive and locations to the
West of the Prime Meridian are negative.

Note Some Envision for BACtalk features may not work properly if the UTC
offset is not set correctly.

Ta ble 4 UTC offsets for time zones

Local Zone UTC Offset BACnet UTC

Local Zone Areas
Code (hours) Offset (minutes)
AST Atlantic Standard Time -4 240

EST Eastern Standard Time -5 300

CST Central Standard Time -6 360

Central America

MST Mountain Standard Time -7 420

PST Pacific Standard Time -8 480

NOTE: This is the
default setting.

ALA Alaska Standard -9 540

HAW Hawaii Standard -10 600

GMT Greenwich Mean Time 0 0

CET Central European +1 -60

MET Middle European

EET Eastern European +2 -120

 USSR Zone 1
SAST South Africa Standard

USZ2 USSR Zone 2 (Moscow) +3 -180

USZ3 USSR Zone 3 +4 -240

USZ4 USSR Zone 4 +5 -300

USZ5 USSR Zone 5 +6 -360

WAST Western Australian Standard +7 -420

CCT China Coast +8 -480

HKT Hong Kong Time

60 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Ta ble 4 UTC offsets for time zones

Local Zone UTC Offset BACnet UTC

Local Zone Areas
Code (hours) Offset (minutes)
JST Japan Standard Time +9 -540

SAST Southern Australian +9.5 -570

Standard

EAST Eastern Australian Standard +10 -600

IDLE International Date Line +12 -720

NZST New Zealand Standard

You can calculate the UTC setting directly from your location’s longitude with
respect to Greenwich, England. Therefore BACnet UTC is:

BACnet UTC offset = -((longitude/15)*60)

(since 360 degrees/24 hours = 15 degrees/hr)

Example
Moscow, Russia is approximately +45 degrees longitude (East of Greenwich), so
its BACnet UTC is -((45/15)*60 = -180.

Hawaii, USA is a bit further than -150 degrees longitude (West of Greenwich),
so its BACnet UTC is -((-150/15)*60) = +600.

Populating the Device Manager table

Once you’ve planned your site—created riser diagrams, determined controller
configuration settings, and generated point lists—you can begin populating your
Device Manager table. Use this data to set up Device Manager.

There are a couple of different ways to set up the Device Manager table for a
site: while online at the site (communicating with devices) or while offline
(offline engineering). Offline engineering is the most common method and is
explained here.

Practical application
Terry is a technician for AlerRep Inc. One of his projects for the week is to set up
the Device Manager table for State University. His supervisor gave him the riser
diagrams and configuration worksheets for the site so he’s ready to begin.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 61

Installation and Startup Guide | Envision for BACtalk

State University is a mid-sized site with 14 buildings:

• Student Union
• Health Sciences
• Administration
• Athletics
• Central Plant (facilities)
• Engineering
• 3 Dormitories
• Library
• Theatre/Auditorium
• Liberal Arts
• Fisheries/Forestry
• Math Sciences

The Student Union is fairly small with only 10 rooftop air conditioning units so
Terry begins there. According to the site documentation, each air conditioning
unit is controlled by a VLC-550. The documentation also shows the device
descriptions were created using the building name (SUB), unit type (ACU)
building number (21), floor number (5 for the rooftop), and a number to indicate
the number of the device (01-10). For example, the first device description is
SUB: ACU-21-501.

Terry quickly determines that he can create one device profile and then use the
Copy feature in Device Manager to create the other nine.

Terry uses an “x” in place

of characters that change
for each device instance
he will create.

Figure 5 Add/Edit Device Profile dialog box

62 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Since each VLC-550 is identical, Terry uses the Capabilities and Preferences
tabs to define the attributes, application, and host device for the controller before
copying the device profile.

After Terry copies the device profile, he can then edit each profile to replace any
“x” with a unique character.

Use the File menu to exit out

of Device Manager or to print
the Device Manager table.

Use the Advanced menu to

auto download data to a
controller, view new devices,
back up devices, restore
devices, restart/control
devices, and renumber
devices.

Figure 6 Device Manager table

You can also use the Renumber VLCs feature to help populate the Device
Manager table. See “Renumbering VLCs” on page 72 for more information.

Sending and saving data

You can use Device Manager to save device parameters to your operator
workstation’s hard disk or to send device parameters from your hard disk to the
actual device. The Send button in Device Manager sends data from the operator
workstation hard disk to one or more devices. The Save button in Device
Manager saves point data and object setup data currently stored in the device to
the operator workstation hard disk.

See the Envision for BACtalk Operator’s Manual (LTBT-OP-EBT) for more
information about the send and save features.

Using Device Scan

After setting up and saving data to the Device Manager table, use Device Scan to
scan for all devices and save to Device Manager once more. This populates the
Device model field on the Identification tab in the Add/Edit Device Profile
dialog box.

Device Scan does not allow you to save scan results if multiple devices are found
with the same device instance. Duplicate device entries are not permitted. If
duplicate device instances are found, correct them, back up the job, and then
compact and repair the database. For more information about Device Scan, see
the Envision for BACtalk Operator’s Manual (LTBT-OP-EBT).

© Honeywell LTBT-TM-ADMIN30 Rev. 05 63

Installation and Startup Guide | Envision for BACtalk

Configuring controllers remotely

Scan for and configure Alerton configurable devices from a remote location
using Device Scan or Device Manager. This feature eliminates the need for
HyperTerminal or any other type of direct connection method

Note Currently, only BCMs (ROC v2.0 and later) and VLXs (ROC v2.3 and
later) support remote configuration.

Configuring a remote device from Device Scan

Use Device Scanner to locate, renumber and reconfigure already configured
controllers from a remote location.

Opens the Edit

Device
Configuration
dialog box.
Only available Disabled if
when Scan multiple devices
Configurable are selected.
Alerton Devices
Select a single
is selected.
device instance
to activate.

Click to view all

BCMs in an array.

Figure 1.1 Use Device Scan to locate, renumber, and reconfigure pre-configured BCMs and VLXs.

When you scan for configurable Alerton controllers, the output will look the
same as any other device scan with the following exceptions.

Scan Configurable Alerton Devices now appears on the Device Scan dialog
box. The Show Non-configured Devices Only option is only available when
Configurable Alerton Devices is selected. Results include only controllers that
match at least one of the following: a) device instance = 200 (factory default for
configurable Alerton devices), b) devices that do not have firmware loaded.

Any device that can be reached using BACnet services (through a series of
properly configured BACnet routers, BACnet over Ethernet, BACnet over IP,
Annex J, PTP, MS/TP, etc) will also show in scan results. Under these
circumstances, misconfigured devices may or may not show up in scan results.

Double-click a BCM in the list that is the only BCM in its array to open the Edit
Device Configuration dialog box. Or, select a device and then click Configure to
open the Edit Device Configuration dialog box.

Working in the View Array dialog box All BCMs may not show up in search
results if, for example, there are multiple BCM-MS/TPs. Select a BCM in the

64 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

scan results list and then click View Array to see a complete list of BCMs in the
array. The View Array dialog box shows the position of each BCM in the array.

Figure 1.2 The View Array dialog box.

Working in the Select Device dialog box Double-click a BCM in the list that
has other BCMs in its array to open the Select Device dialog. The same behavior
occurs if you select a device and then click Configure.

Figure 1.3 The Select Device dialog box.

Double-click a BCM in the Select Device dialog box to open the Edit Device
Configuration dialog box. The same behavior occurs if you select a device and
then click OK.

Working in the Edit Device Configuration dialog box

The Edit Device Configuration dialog box is displayed when you select a device
to configure from either the Device Scan window or the Select Device dialog
box. After changing the device configuration, click OK to return to Device Scan.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 65

Installation and Startup Guide | Envision for BACtalk

The Edit Device Configuration dialog box displays configurable options from
the devconfig.dcf file.

Click an entry in the left

pane to show configurable
options in the right pane.
Main Configuration is
selected by default.

Click to save or discard your changes and close the dialog box.
Click to save any changes to the currently displayed settings and leave the dialog box open.

Figure 1.4 The Edit Device Configuration dialog box.

Working in the Send Device Configuration Wizard The Send Device

Configuration Wizard (BACtalk>Device Manager>Device Scan>[Select a
BCM]>Send to Device) assists you in sending a previously configured device
configuration file from the server to a device. It also provides the added option of
sending a ROC file or other objects and data from the job’s server to the device.
The Wizard is primarily design to help you:

• Add or replace a device for which the configuration and device entry
has already been configured in Envision for BACtalk
• Add a new device that does not yet exist in Device Manager

66 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Net is blank because the device

is found on the local network.

The MAC address and

description are pulled from
the scan results.

No data is required. Click Next

to start.
Click to close
the Wizard.

Figure 1.5 Send Device Configuration Wizard: Welcome/start page

Shows the current device Includes all

instance. You may change devices
the device instance now, if currently in
desired. Device
Manager that
have the
device
capability for
Supports
Sending
Device
Configuration.
Click to send the configuration file.

Close the
Click to return to the previous Wizard without
screen without sending the sending the
configuration file. configuration
file.

Figure 1.6 Send Device Configuration Wizard: Step 1a

© Honeywell LTBT-TM-ADMIN30 Rev. 05 67

Installation and Startup Guide | Envision for BACtalk

If there is an entry in Device Manager with the same net/MAC address as the
device being processed, it is used as the default device. Otherwise, it is shown as
blank.

Click to move to step 2 and

send a ROC file.

Close the
Click to return to the previous Wizard.
screen without sending the
configuration file.

Figure 1.7 Send Device Configuration Wizard: Step 1b

68 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

NOTE: All steps beyond this

point are optional. Click Finish
to close the Wizard or Next to
continue.

Figure 1.8 Send Device Configuration Wizard: (Optional) Step 2a

If you select Send ROC Now If It Is Different Than Server Copy or Send ROC
Now (even if there is no difference) and then click Next, Envision for BACtalk
attempts to send the ROC file. If the device is not yet defined in Device
Manager, the wizard prompts you to define the device.

The Back and Next buttons are disabled while the send operation is in progress.

CAUTION Objects are discarded when a new ROC file is sent so always send
objects (schedules, trendlogs, alarms, zones, etc.) when sending a ROC file.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 69

Installation and Startup Guide | Envision for BACtalk

Figure 1.9 Send Device Configuration Wizard: Step 2b

A confirmation message is displayed after the ROC file is successfully sent.

Click Next to send additional configuration data.

70 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

Figure 1.10 Send Device Configuration Wizard: (Optional) Step 3a

Select the additional data options you want to send the files from the server to
the device. Click Next to start the transfer. Click Finish to close the wizard.

Note: It is good practice

to view the User
Progress window when
sending data.

Figure 1.11 Send Device Configuration Wizard: Step 3b

© Honeywell LTBT-TM-ADMIN30 Rev. 05 71

Installation and Startup Guide | Envision for BACtalk

Configuring a device from Device Manager

Use Device Manager to locate and reconfigure one controller at a time from a
remote location. You cannot renumber devices while configuring them remotely
through Device Manager.

To configure a device from Device Manager, select the device and then click
Configure.... The Edit Device Configuration dialog box appears.

Note The Configure... button is disabled if a controller is not configurable or

more than one controller is selected.

Envision for BACtalk loads the current device configuration file from disk and
displays it in the Edit Device Configuration dialog box. The device instance field
is read-only when the Edit Device Configuration dialog box is opened directly
from Device Manager.

When sending device data to disk, all target devices must be locatable by device
instance so do not change device instances when this operation is in progress.

BACtalk will
automatically read the
device capabilities
from the device after it
successfully sends the
ROC file to the device.

Open the User

Request Monitor to
view the progress of
Send operation.

Selected by default

Renumbering VLCs
Use the Renumber VLCs feature (BACtalk > Device Manager > Renumber
VLCs) to set up device instances for a group of VLCs. This is useful when
setting up very large sites. The Results Preview pane shows you the results of the
changes you make before you make them to help you identify potential conflicts.

WARN ING Renumbering devices without sufficient knowledge can have

adverse affects on your system. If DDC or other software components (such as
dynamic display items) reference data in a VLC, and you subsequently renumber

72 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

the VLC, DDC and display items must be manually updated to reflect the new
device instance.

You have 2 options for renumbering VLCs: Renumber based on device manager
records or Renumber based on VLC Network Number and MAC Address.

 To select VLCs in Device Manager and then renumber them

1. From the BACtalk menu, click Device Manager.

2. Add a device profile for each unitary controller (VLC) whose device
instance you want to set.

3. Click each record to select it individually. Use Shift + click to select a

range of devices. Use Ctrl + click to add and remove individual records
to a highlighted range.

4. On the Advanced menu, click Renumber VLCs.

5. Select Renumber the device instances of field VLCs based on device

manager records, and then choose only the VLCs you selected in the
Device Manager dialog box. The Results Preview pane shows the
device instances that will be assigned.
N o t e Only devices with the Supports Device Instance Renumbering
capability are shown. If you selected any other devices, they will not be
renumbered. You can change a device’s capabilities from Device
Manager (BACtalk > Device Manager > [Device] > Edit).

6. Click Apply.

7. Click Close.

 To renumber VLCs based on MAC address and network number

N o t e Use this option if you are using the Renumber VLCs feature to
help you populate the Device Manager table for a new job.
1. From the BACtalk menu, click Device Manager.

2. On the Advanced menu, click Renumber VLCs.

3. In the Renumber Devices dialog box, select Renumber the device

instances of field VLCs using information I provide.

4. Under Identify VLCs to Renumber, provide the MS/TP network

number that the devices are on, the total number of VLCs you want to
renumber, the MAC address of the first VLC in the sequence, and an
incremental counter added to the original MAC address for each
successive VLC.

5. Under Set New Device Instances, type the new Device Instance you
want applied to the first Net/MAC combination and the increment by
which that Device Instance increases for each successive device you
want to renumber.

6. Click Update Preview to see the effect your changes have. Look for
any warnings in the Status column of the Results Preview. This column
can also indicate Net/MAC conflicts. A conflict occurs when two or
more device profiles use the same Net/MAC address combination.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 73

Installation and Startup Guide | Envision for BACtalk

7. Select Apply to Device Manager Records Only to update device

profiles on the disk only. Clear this option to update the device profiles
on the disk and send to the device.
N o t e Select this check box if you are using this feature to populate the
Device Manager table for a new job.

8. Click Apply.

Assigning Alerton Standard applications to controllers

Alerton Standard applications allow you to assign DDC to a controller and copy
all application related data to the current rep/job from the Alerton Standard
repository. You can also modify the standard applications to meet your specific
needs. For more information, see the BACtalk Systems Programmer’s Guide and
Reference (LTBT-TM-PRGRMR).

Note You need to create a Documentation folder in the rep/job directory for
templates and displays that you copy from Alerton Standard applications.

74 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Understanding Device Manager

 To assign an Alerton Standard application to a controller

1. On the BACtalk menu, click Device Manager.

2. In the Device Manager dialog box, click the device profile you want to
work with, and then click Edit.

3. On the Preferences tab, click App Database.

4. Select the criteria you want to search on, and then click Search. For
example, you can search for applications for a particular unit type, such
as a main air handler or fan coil.
The first application that meets your search criteria is displayed. If there
is more than one, use the arrows under Go to Record to browse through
them and select the one you want to use.

5. When the application you want to use is displayed, click Copy

Application.

6. In the Copy Application dialog box, note the application file name and
destination path, and then click Save. All application materials are
copied to the active rep/job folder.

7. Click OK, and then click Cancel.

8. Click Close, and then click Cancel to return to the Add/Edit Device
Profile dialog box.

9. Click Browse, and then select the rep/job to which you just copied the
application.
N o t e If the Browse button is dimmed, click the Capabilities tab and
ensure that one of the “Supports Alerton DDC type bd3 (or bd4 or bd6)”
capabilities is selected.

10. Select the DDC file from the list, and then click Select.

11. Click OK to return to Device Manager.

12. Click OK to save your changes.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 75

Installation and Startup Guide | Envision for BACtalk

Appendix
This section contains reference information and forms that may be useful during
Envision for BACtalk installations and upgrades.

Envision for BACtalk v3.0 system requirements

Site requirements vary widely, and the system components and
recommendations made in this section are only guidelines. Large sites with
demanding data processing requirements may place a greater demand on servers
and operator workstations.

The server is the most important BACtalk component on site and should have
hardware capable to meet these demands. Performance of the server depends
mostly on available RAM, processor speed, and hard disk space.

Recommended system specifications

These specifications seek a balance between cost and performance. Although
these recommendations will provide sufficient performance on most sites, some
sites may benefit from a computer that exceeds these recommendations.

Install an extra, dedicated CPU to handle auto-archiving, which is a powerful yet

processor-intensive feature. For Enterprise jobs, more processing power is better.
Alerton recommends using two dual-core processors to enable your system to
operate at optimal performance and to provide some growing room.

Site using MS Access

Use the recommended system requirements for your Envision for BACtalk
server running MS Access:

• 2.0 GHz Core 2 Duo

• 2 GB RAM
• USB port
• 52 GB hard disk or better (large jobs may require more, especially those
with many trendlogs)
• High-performance graphics adapter
• Network Interface Card (100/1000 Mbps)
• Printer access
• Keyboard, monitor, mouse, DVD drive
• Windows XP Professional SP3, Windows Server 2003 SP1, Windows
Server 2008, Windows Server 2008 R2, Vista, or Win 7
• Visio 2010 (optional)

Note Installing more hardware may help a slow Envision for BACtalk
conventional job speed up. However, the total performance is limited by reliance
on the Access/Jet database technology. Auto-archiving may slow down
conventional BACtalk jobs because Jet runs auto-archiving and job operations
such as trendlogs, the user interface, the opening of lists, and client/server

76 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Envision for BACtalk v3.0 system requirements

communications. Auto-archiving is designed for SQL Server jobs and still

allows SQL jobs to perform quickly. Upgrade a slow Envision for BACtalk
conventional job to SQL Server.

Site using SQL Server

Use the recommended system requirements for your Envision for BACtalk
server running SQL Server:

• Core i7-860
• 6 GB RAM
• USB port
• 90 GB hard disk or better (large jobs may require more)
• High-performance graphics adapter
• Network interface card (100/1000 Mbps or better)
• Printer access
• Keyboard, monitor, mouse, DVD drive
• Windows XP Professional SP3, Windows Server 2003 SP1, Windows
Server 2008, Windows Server 2008 R2, Vista, or Win 7
• Visio 2010 (optional)

Note Multiple SQL Server computers may be used in a cluster to ensure

optimal performance and to prevent database access from becoming the
throughput bottleneck.

Minimum system requirements

These requirements reflect the absolute minimum threshold for running Envision
for BACtalk. Performance will be limited and may be noticeably poor. If your
computer does not meet these minimum requirements, you must upgrade it to
run the latest version of Envision for BACtalk.

CAUTION Windows 95 and Windows ME are not supported operating systems

for running Envision for BACtalk. Upgrade to one of the supported operating
systems listed.

Site using MS Access

• 1.6 GHz Core 2 Duo
• 2 GB RAM
• USB port
• 37 GB hard disk
• SVGA adapter with 2MB RAM
• Network interface card (10/100 Mbps)
• Printer access
• Keyboard, monitor, mouse, DVD drive
• Windows XP Professional SP3, Windows Server 2003 SP1, Windows
Server 2008, Windows Server 2008 R2, Vista, or Win 7

© Honeywell LTBT-TM-ADMIN30 Rev. 05 77

Installation and Startup Guide | Envision for BACtalk

Note For Envision for BACtalk, use the Aler-Modem, BCM-MODEM or the
MDM-100 to meet your modem needs.

Site using SQL Server

• Core i3-2100
• 4 GB RAM
• USB port
• 58 GB hard disk or better (large jobs may require more)
• High-performance graphics adapter
• Network interface card (100/1000 Mbps or better)
• Printer access
• Keyboard, monitor, mouse, DVD drive
• Windows XP Professional SP3, Windows Server 2003 SP1, Windows
Server 2008, Windows Server 2008 R2, Vista, or Win 7
• Visio 2010

For Envision for BACtalk, use the Aler-Modem, BCM-MODEM or the MDM-
100 to meet your modem needs.

BACtalk software license keys

The software key is a critical component of the Envision for BACtalk software
package. Envision for BACtalk uses a scaled software key system that enables
operator workstations to run the Envision for BACtalk software without a key
locally installed. BACtalk software license keys are non-transferable, are
digitally bound to a single host computer, and do not expire.

Depending on the key level, Envision for BACtalk supports a different number
of operator workstations and devices. Devices are defined as BACnet devices
other than the BACtalk operator workstations.

You can check which software key is installed and the number of devices
supported by choosing About Envision on the Help menu.

Tab le 5 System requirements for Alerton Building Suite 3

PRODUCT AND SOFTWARE LICENSE

CPU RAM FREE DISK SPACE
SIZE
Supported Feature Minimum Minimum Minimum
(Part Number) Recommended Recommended Recommended

Alerton Building Suite 3 – Small 1.6 GHz Core 2 Duo 2.0 GB 37 GB

1 workstation + 50 devices + 1 2.0 GHz Core 2 Duo 2.0 GB 52 GB
WEBtalk VM
(ABS-3-SMALL)

78 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | BACtalk software license keys

Tab le 5 System requirements for Alerton Building Suite 3

PRODUCT AND SOFTWARE LICENSE

CPU RAM FREE DISK SPACE
SIZE
Alerton Building Suite 3 – Medium 2.2 GHz Core 2 Duo 2.5 GB 54 GB
3 workstations +150 devices + 1 2.66 GHz Core 2 Duo 4 GB 86 GB
WEBtalk VM
(ABS-3-MEDIUM)
Alerton Building Suite 3 – Medium 2.2 GHz Core 2 Duo 2.5 GB 54 GB
3 workstations +150 devices + 1 2.66 GHz Core 2 Duo 4 GB 86 GB
WEBtalk VM + Dashboard
(ABS-3-D-MEDIUM)
Alerton Building Suite 3 – Large Core i3-2100 4 GB 58 GB
Unlimited workstation and devices + 1 Core i7-860 6 GB 90 GB
WEBtalk VM
(ABS-3-LARGE)*
Alerton Building Suite 3 – Large Core i3-2100 4 GB 58 GB
Unlimited workstation and devices + 1 Core i7-860 6 GB 90 GB
WEBtalk VM + Dashboard
(ABS-3-D-LARGE)*

Alerton Building Suite 3 – Enterprise Core i3-2100 4 GB 58 GB

Unlimited workstations, devices and Core i7-860 6 GB 90 GB
WEBtalk VMs + SQL Server interface
(ABS-3-ENTERPRISE)*

Alerton Building Suite 3– Enterprise

with Dashboard
Unlimited workstations, devices and
WEBtalk VMs + SQL Server interface +
Dashboard
(ABS-3-D-ENTERPRISE)*

Alerton Tech Key: Times out after 8 continuous hours. Use the tech key to do design work offline. The tech
key enables all functionality including SQL support and dashboards and is intended for Dealers only.
(ABS-3-TECH)**


* This recommended configuration for a Large or Enterprise job requires a 64-bit
operating system.

**The Alerton Building Suite Tech license accompanying this release works in
the same way as the older tech key. The only difference is that the Tech license is
non-transferable; once it is used it cannot be used with a different computer
because it gets associated to that host device only.

Envision for BACtalk uses Device Manager to enforce key level conformance.
When Envision for BACtalk starts, it checks the number of device records in
Device Manager and compares this count with the software key found. If more
records than are allowed are present in Device Manager, a message is displayed
and the first 11, 50, or 150 devices (depending on the key) appear. Envision for
BACtalk counts devices and monitors conformance on an ongoing basis. Any
time a device is added to Device Manager, Envision for BACtalk checks for
software key conformance.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 79

Installation and Startup Guide | Envision for BACtalk

If the device count is greater than the key allows, a message appears that a key
upgrade is required. This upgrade message is repeated once daily. Data from
devices in excess of what the key supports return “no entry” in lieu of system
data.

Network key behavior

When Envision for BACtalk starts up, it checks the number of devices in Device
Manager and compares that number to the software key version present on the
Envision for BACtalk server.

If no key is found on startup, Envision for BACtalk starts in offline mode for the
default rep and job. All data display points show “no entry” in lieu of system
data.

Envision for BACtalk periodically checks for a valid key during operation. If a
key is not found, Envision for BACtalk generates a message and then goes
offline. To bring Envision for BACtalk back online or to re-enable key detection,
restart Envision for BACtalk.

Remote site key behavior

An operator workstation used for temporary connections to stand-alone
controller sites (no operator workstation permanently connected onsite) must
have at least a small key or a Tech Key. The key on the remote operator
workstation determines the number of allowable devices. If the number of
devices at the remote site exceeds the key level on the remote operator
workstation, Envision generates an error message and devices above the number
allowed read “no entry.”

For temporary connections to a server-based system, the key found at the remote
site’s Envision server determines the device limit. Temporarily connected
operator workstations are not included in the device count.

Alarms dialed in from remote systems are not subject to the device count check.
However, receiving alarms at a workstation is disabled without a key.

Host device and automation feature compatibility

Envision for BACtalk provides some automation features that enhance the
capabilities of your control system. If you are upgrading an existing system, not
all equipment supports these new features. Consider the following:

• A BTI must have ROC file v3.20 or later to host optimum start, tenant
activity, or demand limiting. A BTI-100 must have ROC file v1.00 or
later. BCMs support the automation features.
• A BCM or BTI must have ROC file v3.21 or later to support multistate
objects. A BTI-100 must have ROC file v1.01 or later. BCMs support
the automation features.
• LSIs don’t support the automation features and may generate errors if
you try to use them.
• Envision for BACtalk automation features use the Coordinated
Universal Time (UTC) to start and complete operations accurately. See

80 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Sharing data displays in a client/server network

“Setting the UTC offset” on page 60.

Sharing data displays in a client/server network

It is recommended that you copy job displays and templates to client
workstations. Sharing data displays across a network can severely impact
network performance. If your network has the bandwidth to support sharing data
displays this way, follow these setup instructions.

When a site is set up in this way, trendlog data, energy log data, alarms, reports,
data displays, and bitmaps on a single computer—the Envision server—are
referenced by all other operator workstations. Edits or updates performed as the
result of actions at one workstation are immediately reflected at other
workstations.

Shared Network Resource

(Envision Server)

Operator Workstation Operator Workstation

Operator Workstation

Figure 2 Envision for BACtalk runs on each operator workstation locally and
accesses selected job data over the network.

The procedures described here involve sharing the Displays directory on the
server and then mapping to that directory from client operator workstations.
Variations on this procedure are possible for the purposes of flexibility. For
example, you may choose to share at a higher level than the Displays directory.
These variations are not addressed and require a thorough understanding of
Windows sharing and Envision for BACtalk.

 To share the <Displays> directory on the server

1. Start Windows Explorer.

2. Right-click the <Displays> directory, and then click Sharing on the

shortcut menu. (If Sharing does not appear, Windows sharing is not set
up correctly. See your Windows documentation for more information.)

3. On the Sharing tab, click Share this folder.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 81

Installation and Startup Guide | Envision for BACtalk

4. In the Share Name box, type a name for the directory. Make a note of
this name; you will need it later in this procedure, whenever
<sharename> is referenced.

5. Set up permissions, if desired. (See your Windows documentation for

more detailed instructions).

6. Click OK.

82 LTBT-TM-ADMIN30 Rev. 05 © Honeywell

 Installation and Startup Guide | Sharing data displays in a client/server network

 To map the server's shared directory to a drive letter on the client

operator workstation
1. Under My Network Places on the client operator workstation, locate the
<computername> and <sharename> you set up on the Envision server.

2. Right-click at the <sharename> level, and then click Map Network

Drive on the shortcut menu.
In the Map Network Drive dialog box, the Path should read
\\<computername>\<sharename>.

3. From the Drive list, select an unused drive letter and make a note of it.
You will need it later in this procedure whenever <mapdrive> is
referenced.

4. Make sure Reconnect at Logon is selected, and then click OK.

Under My Computer in Explorer, the mapped drive should be listed as
<sharename> on '<computername>' (<mapdrive>). For example,
BACtalk on 'MyCmptr' (L:).

 To set rep/job custom location

1. Start Envision for BACtalk, and log in using your user name and
password.
N o t e You may need to select the Generic/Generic rep/job the first time
you log in.

2. On the Tools menu, click Set Rep and Job.

3. If necessary, type the rep and job name exactly as they were entered on
the server.

4. Click Options to expand the dialog box.

5. Click Create Directory.

6. Under Data Location, select Custom Location.

7. Type or select the mapped drive to the server’s Displays directory (for
example, L:<sharename>).

8. Click Select.

Verifying the client/server relationship

You can verify the integrity of your client/server setup by editing a display on the
Envision server so that it has a unique characteristic—for example, a plain text
message that says, “Hello Clients” — and then confirming that this display
appears as edited at client operator workstations.

© Honeywell LTBT-TM-ADMIN30 Rev. 05 83

Installation and Startup Guide | Envision for BACtalk

84 LTBT-TM-ADMIN30 Rev. 05 © Honeywell