FX-CU V4.

41 and FX Panel
Firmware V4.41 Release Notes

Content
Introduction 2
Operating system compatibility 2
What’s new in this release 2
Issues fixed in this release 2
Software versions and compatibility 2
Installation and upgrade notes 3
FX-CU downgrade notes 3
FX-CU Help 4
Installing FX-CU V4.41 and FX Panel Firmware V4.41 4
Security Guidelines 8
Known issues 9
Reminder of NFPA 72 testing requirements 16
Reminder of NFPA 720 16

Contacting support
Contact Technical Support if you encounter any difficulties during this installation.
Kidde: Tel +1 888 244 9979
Fax +1 866 226 2126
[email protected]
http://www.kidde-esfire.com/

© 2022 Carrier 1 / 16 P/N 3101832-EN • REV 008 • ISS 18AUG22

Introduction
These release notes contain a summary of the changes included with FX-CU version 4.41.
Please read the release notes in their entirety to become familiar with new panel functionality and
upgrade instructions.

Operating system compatibility

The FX-CU V4.41 was tested and found compatible with the following Microsoft Windows
operating systems: Windows 10 Professional, Windows 8.1 Professional, and Windows 7
Professional.

What’s new in this release

Addressed QIT issues.

Issues fixed in this release

QIT number Description
47168170 FX-CU V4.1 Communication Tab Blank
47312056 In the FX-CU if the panel name is changed in the panel properties, any unsaved changes
are removed
47663425 FX-CU v4.4, v4.3, v4.2 Device faults flyover window displays an internal fault for a device
that is not present in device history

47663421 FX-CU v4.4 Device internal trouble bit retained in FX-CU after device was replaced, device
history is cleared and then retrieved.

47663380 FX-CU v4.4 Error - Element "DeviceStatus" does not contain a single text node posts when
attempting to read Internal trouble bit information.

47263964 Sensitivity report from the FX-CU shows descriptions that either run off the edge of the
page, or overlap again onto the page

47229057 FX-CU does not allow .240 as a value in any octet of the Subnet Mask
47672639 Panel reports Internal fault trouble from UI CMS Device Menu Save with No Changes

Software versions and compatibility

FX-CU database compatibility
FX-CU V4.41 can be used to generate databases for panels that use the following versions of
firmware.

Table 1: Panel firmware supported by FX-CU V4.41

Version Feature description
4.0/4.01 Four loop expansion with 1000 addressable devices and RZI16-2RS module support

P/N 3101832-EN • REV 008 • ISS 18AUG22 2 / 16

Version Feature description
4.1/4.1x UL 864 10th Edition and CAN/ULC-S527, CAN/ULC-S559 features – Alarm ON functionality
4.11 RZI16-2RS module fix
4.2 Added support for new CO devices and FX-T3T4
4.3 Added Support for DHCP, USB, FSB, Sur-Gard Receivers
Panels with 2 loop FW version 2.X or lower are not supported by FX-CU version 4.30 or later. If you
want to use the projects from older panels, make sure they upgraded/migrated from 2 loop panel to 4
loop models.
4.4 Enhanced cyber security aspects
4.41 QIT and Defect fixes

To determine the firmware version on your panel:

1. Press the menu button, and then choose Reports.
2. Choose System Configuration.
3. Choose All.
Version is the first item listed after the time and date. It is listed in an XX.YY.ZZ format and
Version 4.30.00 is equivalent to Version 4.3.

Version 4.41 firmware compatibility

Panel firmware version 4.41 is not compatible with FX-CU 3.0, 3.1, 3.2, 3.31, 3.32, 3.4, 3.5, 4.0,
4.1, 4.11, 4.2, 4.3 or 4.4. If you have a panel with version 4.4 firmware, FX-CU version 4.4 or later
is required.
Version 4.0 or later firmware is not compatible with old loop (SLC) cards. Your panel must have
the FX-SLC1 or FX-SLC2 SLC interface cards installed.

Upgrading on panel firmware versions 4.0, 4.01, 4.1, 4.11, 4.2, 4.3 and 4.4
Panels with firmware versions 4.0, 4.01, 4.1, 4.11, 4.2, 4.3 and 4.4 can be updated to version 4.41
using the Firmware Update Utility (FUU) version 4.4. For more information on using the FUU, refer
to Firmware Update Utility Release Notes (P/N 3102144) and the FUU help.

Installation and upgrade notes

We recommend that you do not manually delete your previous version of the
FX-CU. Instead, let the installation program update that version to the current version.
The FX-CU is best run on a computer with a resolution of 1024 x 768 (or better) and small fonts. If
any other settings are used, some of the FX-CU dialog boxes are resized and may not display
properly.

FX-CU downgrade notes

Note: If you want a backup of projects added in newer versions of the FX-CU, then you should
export the project files before downgrading the CU. Once the CU is upgraded back to the newer
version, the exported project files can be imported.

P/N 3101832-EN • REV 008 • ISS 18AUG22 3 / 16

To downgrade the FX-CU:
1. Uninstall the newer version of the FX-CU.
2. Delete the installation folder manually.
3. Install the older version of the FX-CU.

FX-CU Help
FX-CU Help requires that you have Internet Explorer 6.0 or later installed. The HTML help file is not
compatible with other web browsers.

Installing FX-CU V4.41 and FX Panel Firmware V4.41

Follow the procedure below to install the configuration utility. You must have full administrator
rights to install the configuration utility.
Note: Your FX-CU version number may be different.
1. Right-click FX-CU_Setup.exe, and then click Run as administrator.
If asked whether you want this app to make changes to your computer, click Yes.
2. Select the language for installation, and then click OK.

3. Wait for the installation to initialize, and then click Next.

P/N 3101832-EN • REV 008 • ISS 18AUG22 4 / 16

4. After carefully reading the End-User License Agreement, select the I accept the terms in the
license agreement check box, and then click Next.

5. Select where you want to install the software, and then click Next.
We recommend that you use the default location.

P/N 3101832-EN • REV 008 • ISS 18AUG22 5 / 16

6. Select Install.

7. Wait while the setup wizard installs the configuration utility, and then click Finish.

To set up the Username and Password for the first time installation of the FX-CU:
1. The Add Administrator window displays with the User Details tab when you click on the
Launch FX-CU icon on the desktop.

P/N 3101832-EN • REV 008 • ISS 18AUG22 6 / 16

2. Provide a Username and Password which follows password policy and Click OK.

3. The Security Details tab is visible after providing user details.

P/N 3101832-EN • REV 008 • ISS 18AUG22 7 / 16

4. Select 5 unique Security questions and update answers to the selected questions.

5. Click OK to complete the registration and launch the FX-CU application.

The panel date must match with CU/FUU date for successful communication.

Security Guidelines
The computer running the Provisioning software needs to be secure. In order to not compromise
the security of the provisioning software, hardening of the operating systems running the
provisioning software must be used.
Common industry-accepted standards that include specific weakness-correcting guidelines are
published by the following organizations:
• Center for Internet Security (CIS)
• International Organization for Standardization (ISO)
• SysAdmin, Audit, Network, and Security (SANS) Institute
• National Institute of Standards and Technology (NIST) and DISA STIGS
Following STIGs should be applied in order to meet the NIST 800-53 control requirements which
govern the applied STIGs.
• Windows STIG
• Dotnet STIG
• Windows firewall STIG
• Windows explorer STIG
• If running chrome, the chrome STIG
To accomplish this hardening process, an industry recognized standardized security framework
should be employed, not limited to:
• A robust anti-virus installed
• Operating system and application security patches applied to protect the system

P/N 3101832-EN • REV 008 • ISS 18AUG22 8 / 16

• Inbound and outbound firewall rules that permit only required ports to enter and leave
• Applications and users running with least privileges
• Only authorized users may access the Provisioning software
• The operating system checks to verify programs installed on the operating system are signed
• Disable unused services and users
• Utilize secure boot
• Enable Data Execution Prevention (DEP)
• Utilize secure boot with TPM

Known issues
CMS FireWorks account configuration
Unique port number must be configured for every account which is configured as FireWorks.
By default, the port number is 3061 and it must be updated to a unique port number when
FireWorks accounts are configured.
Duplicate port numbers are not accepted in FireWorks accounts (Active or Inactive).

Installing over FX-CU 3.0, 3.1, 3.2, 3.31, 3.32, 3.4, 3.5, 4.0, 4.1, 4.11, 4.2, 4.3 or 4.4
This installation will upgrade any previous installation of the FX-CU. The upgrade will not delete
your projects. If you have a previous installation of the FX-CU, install FX-CU V4.41 into the same
folder as the previous installation or you will not be able to see your existing projects.
FX-CU versions 3.5 and earlier install in the C:\Program Files (x86) \GE\FX-CU folder.
FX-CU versions 4.0, 4.1, 4.11, 4.2, 4.3, 4.4 and 4.41 install in the C:\Program Files (x86)
\Kidde\FX-CU folder.

FX-CU 4.2 Installation on Windows 10 Operating System

Windows 10 Portuguese, Spanish, and French operating systems do not allow installation of
FX-CU 4.2.

System Event Programming – Common Monitor

When utilizing the Common Monitor event in Correlation Group programming, outputs will not
function properly if a delay is used. Do not use the Common Monitor event programming in a
Correlation Group with a delay.

System Event Programming – Signal Silence

When utilizing the Signal Silence event in Correlation Group programming, outputs will not
function properly if a delay is used and the Auto Signal Silence feature is enabled (Panel
Properties). Do not use the Signal Silence event programming in a Correlation Group with a delay
and the Auto Signal Silence feature enabled.

P/N 3101832-EN • REV 008 • ISS 18AUG22 9 / 16

FireWorks and FX panel backward compatibility
• When using this product with FireWorks versions prior to 8.3, the receiver status point
properties cannot be set.
• When using FireWorks version 8.1 with FX panel version 2.31, the following event type
activations will be displayed on FireWorks, however the restorations of these event types will
not. System Control must be restarted.
Common Supervisory, Waterflow, Common Monitor, CO Event, Ground Fault, Alarm On,
Battery Low, AC Power, and Panel Silence
• When using FireWorks version 8.2 with FX panel version 4.XX, the following event type
activation will be displayed on FireWorks, however the restorations of these event types will
not. System Control must be restarted.
• Versions of FireWorks earlier than 8.2 have an issue when importing larger project databases.
If the database import fails to work with FireWorks, review all point labels and determine if you
have duplicate labels. If so, modify the label to make each unique, and then attempt to import
the project again into FireWorks.

Reports>System Configuration>Device
When creating a device report using front panel programming, the panel UI does not list all of the
IP account numbers associated with the device event. The configuration utility must be used to
create correctly generated device reports.

Updating the configuration utility using a different language

If you attempt to update the configuration utility using a different language setting, the installation
dialog boxes will appear in the previous language. To prevent this, you must first uninstall the
previous CU version before installing the new version.

Diagnostics Loop Comm Check

When a Diagnostics > Loop Comm Check is executed from panel, diagnostics is performed on all
four SLC loops regardless of if all loops are present on the system or not. The CU
Status/Diagnostics windows displays "Query ready comm current test in operation" for the SLC
loops not available on the system. This issue is not seen when all four SLC loops are present.

Configuring PreAlarm and Alt PreAlarm on supervisory devices

In accordance with NPFA 72, 2013 edition, supervisory devices cannot be configured with
PreAlarm or Alt PreAlarm. If supervisory devices were configured using PreAlarm or Alt PreAlarm
in CU versions earlier than version 4.3, the selection will change to N/A when the database in
imported into CU version 4.3.

Dialer test time

Dialer test time gets reset to a default value (00.11) when the date is changed while the system is
running. Make sure to set the desired dialer test time and program the panel whenever a date
change is done.

P/N 3101832-EN • REV 008 • ISS 18AUG22 10 / 16

Dialer fault
Dialer Line-1 Fault is not cleared on Dialer configuration change from Dialer type Dual to Dialer
type Single.

Dialer message
Dialer Normal/Abnormal Test Message is not captured for 2 hours on Dialer Line fault in history
reports.

SA-USB
SA-USB card connected to Hyper Terminal; Panel printer mode needs to be set to Unsupervised
Printer.

Relay base Latched option

The Latched option in device properties is applicable only for relay bases. For the base to stay
latched during an activation, the base must be programmed as part of the correlation groups.

Device test fire

During test fire of devices with device type as “non latching,” it may not be possible to view the red
LED activation on the device as the restoration happens immediately after the activation because
of the non-latching property. Note that events are generated and processed as expected.

Event reporting as Zone or Zone/Device

In panel configurations with event reporting as Zone or Zone/Device – if you attempt to program
(configure/add/delete) the zones while a zone is in off normal state, it may result in the “common
trouble” relay being latched on the panel even with no active trouble. In such situations, it is
recommended to power cycle the panel to clear the latched state of the “common trouble” relay.

Events reporting to Printer/FSB

The following events will not be sent to printer/FSB due to system limitations even if configured.

Test Fire
Clear History
Date and Time
Zone Test event
Unconfigured Trouble
Normal Test
Abnormal Test
IP Dialer Account 1 Normal Test
IP Dialer Account 2 Normal Test
IP Dialer Account 3 Normal Test
IP Dialer Account 4 Normal Test
IP Dialer Account 5 Normal Test
IP Dialer Account 6 Normal Test
IP Dialer Account 7 Normal Test
IP Dialer Account 8 Normal Test
IP Dialer Account 1 abnormal Test
IP Dialer Account 2 abnormal Test
IP Dialer Account 3 abnormal Test

P/N 3101832-EN • REV 008 • ISS 18AUG22 11 / 16

IP Dialer Account 4 abnormal Test
IP Dialer Account 5 abnormal Test
IP Dialer Account 6 abnormal Test
IP Dialer Account 7 abnormal Test
IP Dialer Account 8 abnormal Test
Common Trouble Telco
Common Trouble Network

CU Diagnostics window – Device History tab

In the CU Diagnostics window, under the Device History tab, the device events are represented
with device status as trouble, fault, and normal. Since all off normal events are categorized in the
trouble or fault category, for better clarity, more details and categories are required to describe the
events. These updates to the CU will be implemented in the next release.

Administrator login
The CU software should be installed and run as Administrator. When opening the CU software
normally (not run as Administrator), the software does not save the username or password when
closed.

Importing of cross channel databases into FX-CU

Importing of cross channel (VS-CU, IO-CU) databases into FX-CU leads to access violation errors
and the FX-CU will not work as expected.

Device configuration
When device configuration is complete, you need to wait a minimum of thirty minutes to observe
the device programming status on the panel display or you can connect to the CU to observe the
status.

Diagnostic Window - List Index out of bounds (2) due to migrating a 2-loop panel to a
4-loop.
Solution:
1. Navigate to FX-CU installation path.
Default installation path is C:\Program Files (x86)\Kidde\FX-CU
2. Open projects folder-> Navigate to project name and project version folders.
3. Look for Panel_Name.DLP and Panel_Name.DLS files, where Panel Name is the name of the
panel where list index out of bound error appears.
4. Delete the files.
5. Open FX-CU and Read/Refresh Diagnostics data from panel.

What actions can be taken when there are system errors?

The FX-CU is a Windows-based application and in runtime the FX-CU application accesses many
Windows system variables. Due to computer property issues, Windows services can sometimes
be disabled making some of the FX-CU functions do not operate properly.

P/N 3101832-EN • REV 008 • ISS 18AUG22 12 / 16

Example 1: Whenever there is a problem with the Windows Print Spooler the below system error
displays when any of the CU reports are generated.

Example 2: The error message below displays occasionally while generating the validation report
when the CU configuration is being downloaded to the panel.

In these cases, it is recommended to close the FX-CU application, and then reopen it for correct
functionality.

Opening PDF file

When a report is opened in a PDF file from the FX-CU, the user will not be able to open another
PDF file until it is closed in Windows 8.1 OS.

Multiple account configuration

Network account configuration is not visible for events, zones, device, loops.

Device Status Report – Active Supervisory event

When a PCD device’s alternate device type (i.e. CO) is configured to CO Supervisory and the
device is put in acceleration mode, the device status reports shows Active Supervisory event even
though Primary and Alternate device types are restored. This occurs only when both primary and
alternate personalities are activated and restored. This supervisory event disappears from the
Device status report after some time. The time it takes depends on the number of devices
connected to panel. Also, this supervisory event disappears from the device status report once
acceleration mode is disabled.

Alarm events are not delivering within 70 seconds to DACT Receiver

When reset operation is in progress, panel takes up to 73 seconds to deliver alarm events to the
DACT receiver. This is observed when the Telco Dialer is configured with default settings.

P/N 3101832-EN • REV 008 • ISS 18AUG22 13 / 16

Events not reporting on CMS Backup Path
When CMS path is set to Telco/IP or IP/Telco, if the Primary path fails while delivering a specific
event, the same event may or may not be reported on the Backup path because of timing in
determining the Primary path fault. Subsequent events shall be reported on the Backup path once
the Primary path fault is reported on the panel.
Example: CMS path is configured to Telco/IP. A detector reported an event and is configured to
both IP and Telco accounts. The device event will be routed through the Primary path Telco. If
Telco fails while delivering the trouble, same trouble will not be attempted to report through the
Backup path IP. Once the panel reports the Primary path faults (Dialer line fault or Dialer Delivery
failure fault), subsequent events will be reported through the Back path IP.

Enabling RS-232 Communication

Before enabling RS-232 communication on panel to communicate with Configuration Utility,
Printer/FSB device type must be set to ‘None/FSCU’. Failing to set the Printer/FSB device type to
‘None/FSCU’ leads to Panel – Configuration Utility communication issues.

IP Dialer Delivering Normal (CID 602)/Abnormal (CID6 08) Events Twice

When IP Dialer account N is configured to Sur-Gard and test mode is enabled, abnormal test
event 608 or normal test event 602 will be delivered to the Sur-Gard receiver twice if same IP
account N is enabled for IP Dialer abnormal/normal event notification. To report abnormal or
normal event only once to the Sur-Gard receiver from IP account N, do not enable the same IP
account N in the event notification of IP Dialer abnormal/normal events. N is IP account 1 to 8.

Telco Dialer line trouble does not report as per Configured Line Cut Duration
With Line Cut Duration for lines 1 and 2 is set to the default setting of 120 seconds and when
tested this configuration by removing the line 1 and line 2 from the SA-DACT, it detects the
missing line 1 within 120 seconds, however it might take up to 190 seconds to detect missing line
2. In the cases where a ‘Reset’ operation is in progress, the panel configuration updates and there
are active events to be delivered, the panel takes more than 190 seconds to report line 1 and line
2 troubles.

Dialer report displays the wrong information

Event IDs are subject to change from release to release. For Event IDs corresponding to firmware
version, please reference the technical reference manual of that specific version.

Panel allows mapping with no devices connected

Currently, you can perform mapping with no detectors connected to the Panel. Mapping is
supposed to be performed only when devices connected to panel.

DHCP
In certain networks, if the panel is unable to fetch the IP address automatically when DHCP mode
is set to YES, it is recommended to set the mode as NO, and then set it back to YES.

DNS
In certain networks, where DNS supervision is set to YES and if the panel frequently reports a
supervision fault, it is recommended to set the supervision to NO.

P/N 3101832-EN • REV 008 • ISS 18AUG22 14 / 16

CU to Panel Communication
Connection timeout occurs when rapidly switching between Com port and TCP/IP.
To avoid these timeouts, ensure there is sufficient time gap between switching of interfaces.
If issue still occurs, close the CU, and then reopen and use the desired means of communication.

Subnet Mask Validation Issue

When you provide no value to the third or fourth cell of subnet mask field and then click OK on IP
Configuration window, a validation message appears as shown below instead of Invalid Subnet
Mask.

Printer Communication
When the SA-232 or SA-USB connection is used for the panel to CU communication first, and
later if the connection is changed to a printer, the panel fails to send events to printer.

Difference Report
Modified and newly added events will appear on the difference report for upgraded projects until
the FX-CU configuration is overwritten by the panel configuration.

FX-CU to panel communication

It is recommended not to perform any navigation within the FX-CU when read/write from/to panel
is in progress to avoid the CU going into an unresponsive state.

Intermittent Active Code supervision fault

While navigating though the panel’s Printer/FSB configuration menu, the panel reports an active
code supervision fault intermittently. This internal fault does not restore with panel reset operation,
so you must restart the panel. (ID 2552, 47702140)

P/N 3101832-EN • REV 008 • ISS 18AUG22 15 / 16

Reminder of NFPA 72 testing requirements
When changes are made to site-specific software, the following shall apply:
• All functions known to be affected by the change, or identified by a means that indicates
changes, shall be 100 percent tested.
• In addition, 10 percent of initiating devices that are not directly affected by the change, up to a
maximum of 50 devices, also shall be tested and correct system operation shall be verified.
• A revised record of completion in accordance with NFPA standards shall be prepared to reflect
these changes.
Changes to all control units connected or controlled by the system executive software shall
require a 10 percent functional test of the system, including a test of at least one device on each
input and output circuit to verify critical system functions such as notification appliances, control
functions, and off-premises reporting.

Reminder of NFPA 720

Installation, location, performance, inspection, testing, and maintenance of carbon monoxide
detection and warning equipment shall be in accordance with the requirements in NFPA 720
Standard for the Installation of Carbon Monoxide (CO) Detection and Warning Equipment – 2012.

P/N 3101832-EN • REV 008 • ISS 18AUG22 16 / 16