Installation and Startup Guide | Envision for BACtalk

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 database structure between
v2.0 and 2.5 to improve system performance, stability and security. 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 to v2.6.

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 v2.6. 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.

30 © Honeywell. All Rights Reserved. LTBT-TM-ADMIN26 Rev. A