FireWorks 8.

1
Release Notes
Content
Introduction 1
FW-UL6W workstations and FWUL6S servers 2
Major changes in version 8.1 2
System requirements 12
Installation notes 13
Before you begin 14
Installing FireWorks 8.1 15
Installing FireWorks on a domain 16
AutoCAD information 16
Application notes 17
Known Issues 18
History import operations 23
Language support 26
Compatible Edwards systems 26
Contact information 27

Introduction
This document outlines the changes made in FireWorks 8.1 since the previous
release (1.71). It also includes information that was not available in the technical
publications or the Help system at release time.
Please read these release notes in their entirety before attempting to install
FireWorks 8.1. For details on upgrading systems see FireWorks 8.1 Software
Upgrade Installation Sheet (P/N 3101872-EN).

P/N 3100569-EN VER 8.1 ISS 24SEP15

1 / 27

FW-UL6W workstations and FWUL6S servers

Due to the different configuration options now available for FireWorks software,
the software is no longer preinstalled on FireWorks FW-UL6 computers from
Edwards. For software installation instructions, refer to FireWorks 8.1 Software
Installation Guide (3100034-EN) and these release notes. Hardware installation
instructions for the FW-UL6W workstations and FWUL6S servers are provided in
their respective installation manuals.

Major changes in version 8.1

FireWorks network
In addition to the stand-alone version, FireWorks workstations can now be
configured in multiple workstation systems with nonredundant or redundant
server applications. For more information see FireWorks Life Safety Network
Application Guide (P/N 3102147-EN).
Xtralis VESDA Integration
FireWorks has an optional integration function that allows monitor and control of
a predefined set of Xtralis VESDA smoke detection devices that communicate on
a VESDAnet. Table 1 on page 3 lists the compatible Xtralis VESDA smoke
detectors and ancillary devices.
Note: FireWorks to VESDA integration is for VESDAnet devices only and does
not support Xtralis gas detection devices or other devices that do not
communicate with VESDAnet.

P/N 3100569-EN VER 8.1 ISS 24SEP15

2 / 27

Table 1: Compatible detectors and ancillary devices

Model

Firmware version

VLP-XXX [1]

3.17.00

VLS-XXX [2]

3.17.00

VLC-505

3.13.00

VEU-A00, VEU-A10

5.23.00

VLI-885

3.26.05

VLF-250-00

3.09.00

VLF-500-00

3.09.00

VFT-15-NP

4.05.00

VRT-300 [3]

N/A

[1] Where XXX equals 000, 002, 010, 012, or 400

[2] Where XXX equals 200, 204, 214, 300, 304, 310, 314, 600, or 700
[3] For temporary maintenance connections only. Permanent connection of any device to the
VRT-300 is not allowed.

For more information on integrating Xtralis VESDA smoke detection devices, see
FireWorks VESDA Application Guide (P/N 3102374-EN).
Releasing Service
FireWorks is UL 864 listed for use in EST3/EST3X releasing device service
applications that use Xtralis VESDA smoke detectors to activate releasing device
circuits.
FireWorks is only Listed as a communication transmission medium for passing
commands between the Xtralis VESDA detectors and the EST3/EST3X life
safety system. FireWorks may not control or display any releasing device service
features.
FM Approval
FireWorks and the entire MN Series of Ethernet appliances (MN-FVPN,
MN-NETRLY4, and MN-FNS Series) are now FM Approved collectively as a
system.
Addition of VM panel monitoring only
FireWorks now has the ability to make an IP connection to a VM panel for
monitoring and reporting only capabilities. VM panels cannot be issued
commands or controlled from FireWorks.

P/N 3100569-EN VER 8.1 ISS 24SEP15

3 / 27

Fire Automated System Technology (FAST) automatic programming

features
Two optional automatic programming features have been added to FireWorks
8.1. The Device Icon Auto-Drop feature reads properly configured AutoCAD
source drawings and creates well-defined FireWorks AutoCAD maps for both
new and existing systems. This feature reads device addresses from a properly
configured AutoCAD source drawing, compares the addresses with the device
addresses in your FireWorks project, and places device icons in close proximity
to the device address element on the AutoCAD map.
Device icons are placed on the FireWorks maps based on the closest
approximation to the device address and may be adjusted by the system
programmer.
The Pseudo Point Auto-Drop feature scans your FireWorks project and builds a
pseudo point map pool in the Map Browser for each panel, adding the pseudo
points to a panel map for each card in the panel. You can then drag and drop the
maps from the created panel pseudo point map pool to the map TSA of your
choice.
Please note that initial release of the FAST features, the panel rendering is
based on a generic EST3 panel and may not match the actual rendering of the
panel that is installed.
This feature works with AutoCAD version 2007 or earlier. Device addresses must
use a consistent format. The standard EST3/EST3X format is PPCCDDDD, but
custom formats are allowed, provided that they are used consistently throughout
the drawing.
As with any automated process, the output of the program needs to be checked.
With the FAST features, if the files being read are not consistent or complete, the
output may not be what you expect.
For more information, see About the Device Icon Auto-Drop feature in System
Builder Help.
FCC, IRC-3, and EST2 panel support has been removed
CIS Protocol systems (IRC-3, FCC, and EST2) are no longer supported in
FireWorks. If your upgraded project has a CIS node defined and enabled,
FireWorks System Control will not start. Legacy projects can still make use of the
types of nodes for Virtual Points but if the node is enabled in Communications
Manager, FireWorks System Control will not start.
Commands limited by EST3 panel network
FireWorks now has the ability to limit the commands a given user may issue to
specific nodes. This option is settable by user for multiple-node systems and can

P/N 3100569-EN VER 8.1 ISS 24SEP15

4 / 27

be adjusted via the User Manager. Figure 1 below shows where the option can
be found.
Figure 1: Node control option

Email enhancements
Email addresses can now include uppercase letters for customer sites that desire
this.
A useful stand-alone test email program is included with FireWorks 8.1. You can
launch the program from System Builder to test your email connection in real
time without having to change the system configuration, restart System Control
and test a point. Start the application by opening Applications > Test Email
Server. This program includes built-in Help information. Figure 2 on page 6
shows the Test Email window.

P/N 3100569-EN VER 8.1 ISS 24SEP15

5 / 27

Figure 2: Test Email window

Case sensitive passwords

FireWorks 8.1 can be configured to support case-sensitive passwords for more
secure operation. To enable the option (off by default) start System Builder, and
then click Applications > System Configuration. In System Configuration, on the
Basic tab under Property, select LOGIN_CASENSITIVE_ENABLE. In the Value
column, check the Enabled check box.
Failed logon attempts logged to history
For more security conscious sites, failed login attempts are now logged to history
and can easily be reviewed in the reporting application. An example is shown in
Figure 3 on page 7.

P/N 3100569-EN VER 8.1 ISS 24SEP15

6 / 27

Figure 3: Failed logon attempt record

Undefined events logged to history

Undefined events (usually the result of a panel SDU and gateway import
mismatch) are now logged to history. They can be reviewed, along with any other
events, in the reporting application.
User default timeouts set and applied correctly
Previously, in some circumstances, the user time out values did not work. This
function now operates correctly.
System configuration utility improvements
The System Configuration dialog box tabs have been reorganized and expanded
to make it easier to locate functions and commands.
Ctrl+A selects all items in the event queue
For properly authenticated Admin users, the keyboard shortcut Ctrl+A now
selects all events in your queue.
Note: This operation is not allowed in UL Listed systems, and is therefore
restricted to the default Admin users.

P/N 3100569-EN VER 8.1 ISS 24SEP15

7 / 27

Project merge
This feature is intended for advanced users only. It must only be used with standalone systems, and can only be used with systems that use FireWorks 8.1.
Further, the project files (FWKPRJ) used must be in FireWorks 8.1 format (the
files must be created in 8.1 or converted to 8.1).
Online Help is not yet available for this utility.
When building a large system, productivity can be increased by letting
technicians develop different system nodes simultaneously. Work done by
different programmers or installers at different workstations can be integrated into
one project. FireWorks nodes can be imported from a "donor" project into a main
or "host" project.
Note: Before using the merge utility, we recommend that you exit from System
Control and System Builder.
A donor project is nothing more than a standard FireWorks project. To create the
donor project use the File > Backup command. This creates several files, but the
only one needed for the merge has the FWKPRJ extension. Copy this file from
the donor machine to the host machine.
Nodes added to the donor project map tree are imported into the host project
map tree pool, and can then be relocated as required.
To merge projects:
1. Browse to C:\FireWorks\Exe and open mergenodesandmaps.exe.
The program opens a standard browse dialog box to let you select a donor
project from which nodes will be merged into your current project. (A project is
a file with the FWKPRJ extension.)
2. Select the donor project, and then click Open.
The donor project is the project that has the nodes you want to merge into the
current project.
After you specify the donor project, the utility displays a two-paned dialog box
that lets you select nodes from the donor project (shown in the right-hand
pane) and drag them into the host project (shown in the left-hand pane). See
Figure 4 on page 9 for an example of the dialog box.
3. Follow the dialog box instructions to replace or add to the host project nodes
by dragging from the right pane to the left pane.
4. Click Merge.
The utility displays a progress message box. When the merge is complete,
the utility displays the message Merge completed successfully.

P/N 3100569-EN VER 8.1 ISS 24SEP15

8 / 27

Figure 4: Select the Nodes for Merge dialog box

New Save/Restore COM Port utility

For customers using multiple nodes and multiple FireWorks workstations, each
operating in stand-alone mode, the database for the individual FireWorks
workstations is often exactly the same except for the IP addresses of the
FireWorks workstation MN-COM1S.
Because the databases are the same, it's convenient to copy an updated
database from one workstation to another; however, this overwrites the target
workstation COM port settings. We've created a new utility that lets you save and
then restore the target workstation COM port settings.
This utility cannot be used on encrypted ports.
Note: Before using the save/restore utility, we recommend that you exit from
System Control and System Builder.

P/N 3100569-EN VER 8.1 ISS 24SEP15

9 / 27

To use the Save/Restore COM Port utility:

1. Start the utility by browsing to the C:\FireWorks\EXE folder, and then doubleclicking SaveRestoreCommPorts.exe.
The following dialog box displays.

2. Click Save. The target workstation COM port settings are saved in
C:\Fireworks\CommPorts.txt.
3. Click Close to exit the utility.
4. Start System Builder and use the File > Restore command to copy the source
database onto the target workstation.
5. Exit System Builder, and then restart SaveRestoreCommPorts.
6. Click Restore to reinstate the original COM port settings on the target
workstation.
New custom reports
Three custom reports were added to the report application for audit purposes.
They are titled:

Account Changes for the last 30 days

History Report for SSDC devices

Partition Arming and Disarming

These can be used as-is or as templates for customized reports.

The reports are available in System Control > Applications > Report Application.
In the Category list, select History, and then click the Custom Reports tab.
Devices Tested Reporter utility for NPFA 72
To assist our customers with their NPFA-required periodic testing, FireWorks 8.1
includes a Devices Tested Report (DTR) utility. This utility lets you track, print,
troubleshoot, archive, and submit a report of all the required testing done at a
facility.
A sample Devices Tested Report is shown in Figure 5 on page 11.
The DTR utilizes and works hand-in-hand with the information FireWorks obtains
through the Edwards Service Group test methodology. In order for FireWorks to
have the information it needs about the Edwards Service Groups, a new gateway

P/N 3100569-EN VER 8.1 ISS 24SEP15

10 / 27

file has been added which must be exported from the SDU. The first version of
SDU to have such files will be 5.3.
The DTR is started from the System Control Applications menu and included its
own online Help.
When using the DTR, be sure to start System Builder, click Applications > Set
Filtering Parameters, and then clear the Monitor check box.
Figure 5: Devices Tested Report

Gateway settings
FireWorks only works with Gateway Type III. If a gateway COM port on the
EST3/3X panel is set to a different port type FireWorks now clearly indicates the
error.
Communications will not be established. A diagnostic message is displayed to
alert you to the port type conflict.
New History file import/export tool
We've created a utility program to provide a quick backup and restore function for
just history data.

P/N 3100569-EN VER 8.1 ISS 24SEP15

11 / 27

The import/export tool is intended for advanced users only. It must only be used
with stand-alone systems, and can only be used with systems that use
FireWorks 8.1.
To start the utility, open the C:\FireWorks\EXE folder, and then double-click
HistoryBackupRestore.exe.
For information on how the utility works, refer to the file
DBHistoryAppilcationDoc.docx, located in the C:\FireWorks\Documentation
folder.

System requirements
FireWorks 8.1 requires Windows 7 Professional, 64-bit, Service Pack 1. If you
have a previous version of FireWorks that ran on Windows 7 Ultimate, this is a
supported upgrade path. Windows XP is no longer supported and the installation
wizard prevents installation onto a Windows XP computer.
All FW-UL6 FireWorks computers come with Windows 7 Professional, 64-bit,
SP1 already installed. The only other Windows operating system that has been
tested or certified to work with this version of FireWorks is Windows 7 Ultimate
SP1 64-bit, in order to provide support for FWUL5W7 computers which were
shipped with this operating system installed.
Computers running FireWorks System Control software cannot be used for other
purposes, such as word processing, accounting, etc. Computers running
FireWorks Remote Client are considered ancillary, and may be used for multiple
purposes.
FireWorks 8.1 has been tested on the FW-UL6W and FW-UL6S workstations.
FireWorks 8.1 may run acceptably on FWUL5W7 and FWUL5RAIDW7
computers, and on FWUL5 and FWUL5RAID computers that have Windows 7
upgrade kits installed. Windows 7 upgrade kits are described below.
Note: FireWorks 8.1 will not run on a FWUL4 or earlier computer.
Model

Description

FWUL5RAIDUKW7

Upgrade for FWUL5RAID workstation. Includes Windows 7 Ultimate

64-bit SP1, two 500 GB hard drives, one 2 GB RAM module, plus
instructions.

FWUL5RAM2G

2 GB RAM module and instructions. For use in FWUL5,

FWUL5RAID, FWUL5W7, or FWUL5RAIDW7 workstations only.

FWUL5UKW7

Upgrade for FWUL5 workstation. Includes Windows 7 Ultimate 64bit SP1, one 500 GB hard drive, one 2 GB RAM module, plus
instructions.

P/N 3100569-EN VER 8.1 ISS 24SEP15

12 / 27

For unlisted applications using third-party computers, the computers must meet
or exceed the following minimum requirements:
Parameter

Requirement

Operating system

Windows 7 Professional 64-bit SP1

CPU

Intel i7-4770S processor

RAM

32 GB

Hard drive

500 GB

DVD drive

Required

USB port

Two free USB ports

Display

1280 1024 16-bit color display

Installation notes

Windows Automatic Updates must always be turned off. Updates may require
a restart or render the workstation unusable. Always apply updates and
patches manually, so you can retain supervision and control of the update
process. FW-UL6 computers are shipped with Automatic Updates turned off.
Third-party computers may not have Automatic Updates turned off. If so, you
may have updates pending, which will prevent SQL Server 2012 from
installing. Before installing FireWorks 8.1 on a third-party computer, turn off
Automatic Updates, and then restart the computer to clear all pending
updates.

To speed up the installation, we recommend that you disconnect the

computer from the network by unplugging the Ethernet cable or by disabling
the network adaptor. The FireWorks 8.1 installation offers to disable the
network adaptor for you, but this feature has only been tested on FW-UL6
computers. On third-party computers, you may have to do this manually.

FireWorks 8.1 requires Service Pack 1 for Windows 7 Professional 64-bit.

The installation wizard will not allow installation of FireWorks 8.1 if you dont
have this needed service pack.

FireWorks 8.1 makes use of many advanced SQL Server 2012 functions. For
instructions on installing SQL for a nonredundant or redundant FireWorks
network, refer to FireWorks Life Safety Network Application Guide
(P/N 3102147-EN). The guide also discusses how to configure your project
for operation on a FireWorks network.

FireWorks 8.1 will not run ACDB/KP Display. Cardholder information is no

longer displayed in the event action window.

P/N 3100569-EN VER 8.1 ISS 24SEP15

13 / 27

Security inputs such as the SIGA-SEC2 and SIGA-MD will be supported as

long as they are supported in active Edwards control panels.

SiteVision and SiteVision Plus (CCTV Manager) are no longer supported.

Before you begin

Cautions
Do not attempt to run any other programs, or have the computer perform any
other operations, when installing FireWorks 8.1.
If you install the wrong version of FireWorks (i.e., stand-alone or nonredundant
network instead of redundant network, or vice-versa) you will have to completely
uninstall and then reinstall FireWorks and SQL Server. For details, see
FireWorks Life Safety Network Application Guide (P/N 3102147-EN)
Follow the instructions given in:
FireWorks 8.1 Software Installation Guide (P/N 3100034-EN)
FireWorks 8.1 Software Upgrade Installation Sheet (P/N 3101872-EN)
Caution: For existing systems installed on FWUL5W7 computers, before
upgrading to FireWorks 8.1, be sure to run the System Size Calculation Program
(SSCP) utility.
To run the SSCP utility:
1. Navigate to the FireWorks DVD media, and then to the subdirectory
FireWorks for UL5 SSCP 1.7X.
2. Double-click FireWorksStatistics.exe to run the SSCP utility.
3. Click OK to start the utility.
A screen capture of the completed SSCP run for a large FireWorks system is
shown in Figure 6 on page 15.

P/N 3100569-EN VER 8.1 ISS 24SEP15

14 / 27

Figure 6: SSCP report example

If you plan to upgrade an existing FireWorks version or install a new version on

an FWUL5W7-class computer, then you must consider the constraints discussed
below. If you exceed any one of these, or have a combination of any two, your
computer hardware must be evaluated. The constraints are:

If the system has more than 20 FireWorks nodes.

If the system has more than 19,500 total points/objects (physical and/or
virtual).

If the system has the DARCOM option with more 1,000 points being
processed by the DARCOM program, including iO Series points.

If the system has AutoCAD maps that are 2 MB or larger, or has more than
20 TSAs, they will need to be converted to WMF format to run acceptably.

Installing FireWorks 8.1

If you are installing FireWorks 8.1 on an FWUL5W7 computer, refer to FireWorks
8.1 Software Upgrade Installation Sheet (P/N 3101872-EN).
While the base software upgrade is included with the purchase of FireWorks 8.1
DVD, hardware and software options are not.

P/N 3100569-EN VER 8.1 ISS 24SEP15

15 / 27

Installing FireWorks on a domain

FireWorks should install and run without issue under even the strictest domain IT
policies; however, there is no way to predict what policies might be crafted by the
local IT department. If you are running into trouble with a FireWorks workstation
on a domain, troubleshoot by installing FireWorks with the domain policy turned
off, verify that FireWorks is operating correctly, and then turn the domain policies
back on one-by-one until you find the policy that is causing the issue.
Note that if FireWorks is being installed on a computer that was not supplied by
Edwards, or is being installed on a nondedicated network, then Edwards cannot
provide high-level support. This is due to the wide variations in computers and
network topologies. We strongly recommend that you consult your local IT
professionals before you attempt to install FireWorks on a third-party computer or
on a nondedicated network.
On high security Windows 7 IT core loads, computers are typically set up to
prevent full control of the directories, which prevents the SQL databases from
installing properly, regardless of whether or not you are an authorized user.
This restriction to directory access makes attaching the FireWorks databases
during installation problematic, even when done manually. The symptoms are
that scripts will fail with Error 5: Access denied. To get around this you must
manually set the control to full for authorized users and then reinstall
FireWorks.

AutoCAD information
If the AutoCAD files are larger than 1 MB, there could be display performance
issues. If you are using AutoCAD, it is recommended that you:

Delete all nonessential layers

Purge files
Pay attention to the drawing scale

AutoCAD colors
FireWorks does read AutoCAD Version 2000 and 2007 files natively. However,
with large files, FireWorks response will be optimized by using minimized
AutoCAD files or by converting the files to WMF file formats.
The FireWorks AutoCAD drawing engine requires that the appropriate colors are
chosen from the AutoCAD palette. For more information, please refer to the
AutoCAD_font_Map.ini file located in the C:\FireWorks\Maps folder for more
information.

P/N 3100569-EN VER 8.1 ISS 24SEP15

16 / 27

AutoCAD rendering
The AutoCAD interpretation software module supports multiple AutoCAD
versions. This corrects issues that were seen in the past where a drawing would
work in one version, but not in another. AutoCAD formats 2000 and 2007 are
supported in FireWorks 1.71 and later.

Application notes
Attaching actions to First Alarm and other EST3 pseudo points
All points are created and treated equally in FireWorks by design. Keep in mind
that most EST3 pseudo points are not routed to cabinets. This means the points
will come into FireWorks as Message disabled and any desired response must
be attached to the message disabled substate in System Builder. EST3 pseudo
points can also be added to TSAs.
System Builder
If System Builder will not start due to database corruption, there is a command
script that will return the system to a known state. Make sure you have a valid
backup before executing this script. The script
RestoreOriginalEmptyDatabase.bat is in the C:\FireWorks\Database\Other
folder. To run this under Windows 7, you must right-click the file, and then run it
as an administrator.
Caution: Running RestoreOriginalEmptyDatabase.bat will purge your current
database. There is no Undo command in System Builder. Once an item is
deleted, it is gone and cannot be recovered.
FireWorks command priority
FireWorks issues commands with a low priority for all systems. If you need to
issue a command with a medium, high, latch, or set priority, you must use
command lists or other programming in the 3-SDU.
Test event filtering
When filtering active-test events (EST3 service groups) for System Control,
check the Trouble and Monitor event check boxes (from System Builder,
Applications > Set Filtering Parameters) to allow service group active events,
which are monitor events, and service group device activation events, which are
trouble events.
However, if you are using the new Devices Tested Reporter utility, you must
ensure that the Monitor event check box is cleared. See Devices Tested
Reporter utility for NPFA 72 on page 10 for more information on the DTR.

P/N 3100569-EN VER 8.1 ISS 24SEP15

17 / 27

Known Issues
The FW-UL6S HDMI output drops video signal
The HDMI video output on the FW-UL6S will sometimes require a reboot to send
a video signal to the monitor. If you unplug the video monitor or move it to a
different output, you may be required to reboot the computer, cycle the power on
the monitor, or both to bring the video back.
TSA positions for a missing map file
If a required map file is missing, the TSAs for that map will be displayed in an
accessible region of the FireWorks workspace, provided that the map was small
(for example, 640 480 pixels or smaller). However, if the missing map was
large, or was based on an AutoCAD vector file, the TSAs may be displayed
outside the normal viewing area. This issue disappears when the missing map is
replaced. Please note that you can access any device by clicking the Device Map
icon.
Com0Com tool updated
For FW-UL6-class computers, the Com0Com tool was updated to V3.0.0.0.
Instructions for using this tool are in the file Field Tech Note - IPMON1000
Virtual Null Modem Cable.pdf located in C:\FireWorks\Documentation. The
instructions are valid for V3.0.0.0, though some of the prompt text has been
altered slightly from previous versions.
Deleting logical objects
After a project has been imported into FireWorks, deleting a service group (or
any logical object) using the 3-SDU can cause an unwanted mismatch between
the group label and the addresses.
One workaround is to leave unused objects in place in the EST3 or EST3X
project. Another workaround is to delete all of the objects (of that type) from the
FireWorks device tree, and then reimport the EST3 or EST3X project file, using
Gateway > Import.
PT-1S USB printer troubles
PT-1S printer troubles for loss of power or data connection loss appear in
System Control as new events only when there are events in the printer queue.
FireWorks does not post the PT-1S out-of-paper trouble even if events are in the
print queue. It may be necessary to cycle the PT-1S power after the out-of-paper
trouble has been restored to resume printing.

P/N 3100569-EN VER 8.1 ISS 24SEP15

18 / 27

System startup
Large systems may exhibit one or two minutes delay during the startup process.
This is done by design, so that when point data handling begins, all of the
necessary initialization has been done previously and processing is optimized.
Printers
Any printer configured in Windows can be used for report or graphics printing.
The UL Listed printer is the PT-1S and this printer works very well for event
printing. If you need to use an unlisted printer for events (such as an ink-jet or
laser printer) be aware of the following:

When selecting a printer, especially one intended for automatic printing of

events, do not chose an XPS-based printer or any printer that requires user
input to select an output file name or location. The system will not update
properly and events will not post while FireWorks is waiting for a printer file
name or location to be specified.

The printer you choose must support PCL (printer control language).

Consider the amount of information required before a page is output. On

some printers you will get one event per page, while on others you will need
to fill the whole page before the printer outputs. You may have to adjust the
printer settings to get the desired output.

We recommend that the printer be set to draft or fast normal as the default
print setting; this will allow the unit to process and print the images very quickly
and use the minimum amount of ink/toner.
FireWorks can be configured to print events automatically using the Configure
Auto Print Events/Map command on the System Control Functions menu.
Note: The Configure Auto Print Events/Map command is not available on
FireWorks redundant networks. This feature may be included in a future release.
Configuring the system for automatic printing can decrease system
responsiveness. We recommend that you do not use this feature on systems with
a high volume of event messages. Automatic printing is intended only for
systems with an average of five events per minute, maximum.
Screen savers and power management
Under no circumstances should you use a screen saver or any power
management functions on a FireWorks workstation. This can have unexpected
life safety side effects such as the turning off of serial ports, network ports, etc.
The installation process includes an option to turn off screen saver and power
management functions. You should choose this option, and should not reinstate
the functions after installation.

P/N 3100569-EN VER 8.1 ISS 24SEP15

19 / 27

Image Display window does not play AVI files

There may be compatibility issues with some AVI files and FireWorks running
under Windows 7. To ensure that the AVI file will work with FireWorks and
Windows 7, play the AVI file in Windows Media Player. If the file plays correctly,
FireWorks will process the file correctly. If Windows Media Player will not play the
AVI, you may need to install updated codecs. The C:\FireWorks\Tools folder
includes a Windows 7 codec pack that you can use to update your codecs. The
file label for the codec pack is windows.7.codec.pack.v3.7.0.setup.exe.
Error loading image in Image Display window
The Image Display window cannot display 32-bit color (CMYK) images. Trying to
do so produces an invalid picture warning. To fix this issue, convert your 32-bit
color images to 24-bit (RGB) color.
History database issues restoring older projects
In FireWorks 1.7x, the history database was converted from a Microsoft Access
database to a Microsoft SQL Server database. If you install FireWorks 8.1 on top
of an existing FireWorks 1.7x project, the installation will handle the conversion
seamlessly for you.
If you are bringing over a database project from an existing system to a different
computer, the backup programs for the earlier versions (1.6x and earlier) cannot
and did not interpret this new functionality, so they do not automatically capture
the history access database files. This must be done manually by following these
steps:
1. Manually copy the C:\Fireworks\System\FWKhistory.mdb file from the source
computer to the target computer.
2. Manually copy all of the files in the C:\Fireworks\Archives\History folder from
the source computer to the target computer.
3. If you are restoring a FireWorks 1.6x project, open the C:\Fireworks\EXE
folder, and then double-click PrintHistoryDatabaseUtility.exe. When it has
finished, restore the project.
Storing history events
History events are now stored in an SQL Server database table where previously
they were stored in multiple MS Access files.
Previously, a FireWorks project backup did not include history event data, but
now the FireWorks Backup Project utility has the option to include history.
If the FireWorks operator wants to store history data with the project backup they
simply check the Full Backup check box during a project backup. Figure 7 on
page 21 shows the Full Backup check box.

P/N 3100569-EN VER 8.1 ISS 24SEP15

20 / 27

Figure 7: The Backup Project dialog box

Upon restoral, if FireWorks sees the history database, it will overwrite the current
history database with the history database from the backup.
EST3 security points
Use care when removing a Bypass from a security point. If the devices are in an
active condition when the Bypass is removed, the active devices may cause an
unwanted security event. The same care should be taken when reenabling a
disabled security device.
EST3 guard patrol
The guard patrol feature does not function properly when controlled from
FireWorks System Control (using the commands On or Off). If guard patrol is
being used, it must be controlled directly by an EST3 system.
MN-COM1S connection to a VESDAnet network hangs up
An MN-COM1S connection to a VESDA network may hang up after an extended
amount of time. To prevent this, set the DisConnTime option on the MN-COM1S
for 10 seconds (00:10).
MN-NETLRY4 and MN-FVPN relay status in Remote Client
MN-NETRLY4 and MN-FVPN relay status events do not post in the Remote
Client when a relay status request is made.
MN-NETRLY4 Application Setup page recovery
FireWorks 8.1 requires a firmware upgrade for any MN-NETRLY4 used in a
redundant FireWorks network. The upgrade allows supervision for the devices
when used in redundant server applications, and is described in the
MN-NETRLY4 Firmware Upgrade Installation Sheet (P/N 3102372-EN).
If you have configured specific applications, you need to record the settings on
the Application Setup page before the upgrade, and take additional steps after
the upgrade to recover the Application Setup page.

P/N 3100569-EN VER 8.1 ISS 24SEP15

21 / 27

To record Application Setup settings:

1. Open Internet Explorer on a PC with access to the MN-NETRLY4.
2. Enter the devices IP address to open the Device Status page.
3. Click Configuration to display the Settings page.
4. Click Application Setup to display the Application Setup page.
5. Take a screen shot of this page, or otherwise record the values.
To recover the Application Setup page:
1. Open Internet Explorer on a PC with access to the MN-NETRLY4.
2. Enter the devices IP address to open the Device Status page.
3. Click Configuration to open the Settings page.
4. Click Defaults to open the Defaults page.
5. Click the Factory defaults link to reset all but the network settings.
6. Click the Reboot link to complete the reset process.
The system will display a message when the process is complete.
7. Click Application Setup.
You can now access the Application Setup page and restore settings as
required for your application.
Nuisance application error message when running a report
FireWorks may display the following error message when running a report,
depending on the size of the database and the amount of computer resources
available.
Figure 8: Application error during reports

P/N 3100569-EN VER 8.1 ISS 24SEP15

22 / 27

If you get this error message, click the Ignore button. The report will run correctly
without any other errors.
SMTP email servers
Some SMTP email servers place email messages in a queue, which may cause
a delay when sending your emails. If you experience this issue, see your IT
department for the appropriate email settings.
SYSTEMCONTROL_SHOW_CLOSE property on 1.x upgrades
The SYSTEMCONTROL_SHOW_CLOSE property allows or prevents an
installer from closing System Control display windows at runtime. In prior
versions of FireWorks the property had the reverse affect, the upgrade will make
the function operate as intended but the opposite of what you had. After you
upgrade FireWorks, you may have to go in and manually change the property to
what you desire.
Application error when modifying or saving a scheduled report
You may get an application error message when you try to modify and save a
schedule report. If this happens close and then restart the reporting application.
Acknowledged Alarm:Error* events are not cleared on Remote Client
All Alarm:Error* events are passed to Remote Clients, even those that
were acknowledged prior to connecting the Remote Client to FireWorks.
Acknowledging these events on FireWorks does not clear them on the Remote
Client. For that, you must use the Clear or the Clear All button on the Remote
Client.
Assigning device icons to VESDA detectors
You can use the Assign/Import Icons dialog box to assign a different device icon
to a VESDA detector. However, the Assign/Import Icons dialog box lists 15 of the
same object type for each VESDA detector type. This means that to assign a
different device icon to a VESDA detector, you can:

Use the Assign/Import Icons command as you would with any other device,
except you must assign the icon to each VESDA detector object type listed

You can rename the default VESDA icon (e.g., vesda_vlp_OLD.bmp), and
then save the new VESDA icon in the C:\FireWorks\Icons folder with the
default VESDA icon file name (e.g., vesda_vlp.bmp)

P/N 3100569-EN VER 8.1 ISS 24SEP15

23 / 27

Mass assigning actions and commands to VESDA devices

Using the Find dialog box to mass assign actions and commands to statesubstates on VESDA devices is not supported. This means that you have to
assign actions and commands to state-substates on VESDA devices one at a
time.
VESDA command status may not update on client stations
When you send commands to VESDA detectors from a client station, sometimes
the Command Status dialog box fails to update properly and show that the
command was sent successfully. The Status column will still show Pending.
However, you will receive command-based feedback from the detector that the
command was sent successfully.
Warning message when unassigning a node
If you are trying to unassign any nodes from the Node Control portion of Access
Group Configuration under the User Manager application and you have an old
style IRC3 node defined you may see a warning An error occurred while saving
changes to database. Please contact technical support.. This warning can be
dismissed and the application restarted and will not impact your operation in any
other way.

History import operations

Opening a version 1.6x or later database
In FireWorks 8.1, opening a database from version 1.6x or later displays the
dialog box shown in Figure 9 on page 25.

P/N 3100569-EN VER 8.1 ISS 24SEP15

24 / 27

Figure 9: Version 1.6x import dialog box

The dialog box requires three decisions, set out in these areas:

Project Save
History Save
History Clear

Project save. The first Yes/No option determines whether your current project is
saved before you proceed.
If you select Yes, then the current project gets saved with name Project
Name.fwkprj.
If you select No, then the current project is not saved.
History save. The second Yes/No option determines whether the history
database for the current project is saved. Note that the this option is only enabled
if you select Yes for the Project Save option.
This option is useful if you need to have a copy of your current history database.
If you select Yes, then the current project history database is saved with the
name Project Name-History.DB in the same folder where the project is saved.
If you select No, then current project history database is not saved.

P/N 3100569-EN VER 8.1 ISS 24SEP15

25 / 27

History clear. The third Yes/No option determines whether to clear the current
project history. This option is useful if you want to start a completely new project
with no history database.
If you select Yes, then the records in the history database are removed.
If you select No, then the history database remains unchanged.

Language support
FireWorks 8.1 supports the following languages:

Chinese - Simplified
Chinese - Traditional
English - US
English - UK
English - Australian
French - Canadian
Polish
Russian
Spanish - LATAM
Portuguese - Brazilian
Turkish

Note: FireWorks does not provide translations of custom data, such as point
descriptors or labels. When the Alternate Language is selected, only the system
messages change to the selected language.

Compatible Edwards systems

FireWorks 8.1 is compatible with the Edwards products and systems shown in
Table 2 below.
Table 2: Compatible systems
Panel

Application
code

Comment

EST3

5.2

This is a mandatory update. New features, such as DTR,

require 3-SDU 5.3.

EST3X

1.3

This is a mandatory update. New features, such as DTR, the

3X-ETHx card, or IP Services require 3-SDU 5.3.

EST3X

1.2

If the 3X-ETHx card is not used, 3-SDU 5.2 is compatible.

VM

1.3

This is the first version to support the ECP protocol and to be

compatible with FireWorks. Requires VM-CU 1.3.

iO Series

2.2

This is the first version to export the CID strings into an XLS
file.

P/N 3100569-EN VER 8.1 ISS 24SEP15

26 / 27

Contact information
Contact technical support if you encounter any difficulties during this installation.
Please make sure you have the requested diagnostic or log files ready before
you contact us.
Tel +1 800 655 4497
Fax +1 866 226 2126
est.techsupport@fs.utc.com
www.edwardsfiresafety.com
2015 Walter Kidde Portable Equipment, Inc. All rights reserved.

P/N 3100569-EN VER 8.1 ISS 24SEP15

27 / 27