3-SDU Version 5.

10
Release Notes
Content
1 Introduction 1
2 Operating system compatibility 2
3 Whats new in 3-SDU 5.10 2
4 Language support 8
5 Software versions and compatibility 10
6 Microcode updates for 3-CPU V3.05, V3.65, V3.75 14
7 Microcode updates for 3-CPU V4.05, V5.03 14
8 Microcode updates for C-CPU V1.06 15
9 Microcode updates for C-CPU V1.10 16
10 Installing and upgrading to 3-SDU 5.10 18
11 Upgrading microcode versions 24
12 Reminder of NFPA 72 testing requirements 28
13 Known issues 28
A. Features in 3-SDU V5.02 36

1 Introduction
These release notes document the changes in 3-SDU version 5.10. Please read
these release notes in their entirety before installing 3-SDU 5.10. For details on
upgrading systems using the network download feature see 10 Installing and
upgrading to 3-SDU 5. on page 18.
Note: Version 5.02 represented a significant enhancement to 3-SDU features.
For your convenience, we have appended a description of the 5.02 feature set at
the end of this document for reference. The full release notes, 3-SDU Version
5.02 Release Notes, are also available at https://est.edwardsutcfs.com/
catalog/login/.
We may use x in a model number to indicate several generations of the
product. For example, 3-CPUx represents the 3-CPU, 3-CPU1, and 3-CPU3.
2012 UTC Fire & Security. All rights reserved.
P/N 270729 ISS 02MAY12

1 / 45

1.1 New software versions

3-SDU 5.10 includes updated firmware for the products listed in Table 1.
Table 1: New software and microcode versions for 5.10
Description

Version

3-CPU microcode (for EST3)

3.05, 3.65, 3.75, 4.05, 5.03

C-CPU microcode (for EST3X)

1.06, 1.10

3-SxDC1 microcode

4.02, 4.10

1.2 Contacting support

Contact technical support if you encounter any difficulties during this installation.
Please make sure you have diagnostic or log files ready before you contact us.
Edwards
8985 Town Center Parkway
Bradenton, FL 34202
Tel +1 800 655 4497
Fax +1 866 226 2126
est.techsupport@fs.utc.com
est.edwardsutcfs.com

2 Operating system compatibility

3-SDU 5.10 is compatible with the following versions of Microsoft Windows:

Windows XP (32-bit), Service Pack 3

Windows Vista (32-bit), Service Pack 1

Windows 7 (32-bit)

Windows 7 (64-bit)

Note: 3-SDU 5.10 must be run as administrator, and requires full elevated
rights and privileges.

3 Whats new in 3-SDU 5.10

3-SDU 5.10 includes new features, as well as most of the features in all
previously released versions.
Additional new features and updates from 3-SDU 5.02 in this release include:

Personality code changes

Full support for SIGA2 detectors and modules, including CO support

P/N 270729 ISS 02MAY12

2 / 45

Support of the CDR-3 Bell Coder for EST3X

Support of the new 3X-FIB network fiber optic card
Support of the new DS and DH nonmapping devices
New NACCO command
R-Series password update
Security device type removal for EST3X
Partition group removal for EST3X
3-CPU versions earlier than V3.05 removal
SDU bug fixes
Additional miscellaneous bug fixes
SDU Help updates

For details on the features offered in 3-SDU 5.02, see Appendix A. Features in
3-SDU V5.02 on page 36. Also, the full release notes, 3-SDU Version 5.02
Release Notes, are available at https://est.edwardsutcfs.com/catalog/login/.
3.1 Personality code changes
When using C-CPU version 1.10 or SxDC1 version 4.02, the SDU automatically
makes the following personality code changes for the SIGA-PCOS:

Personality code 68 (photo nonlatching - CO nonlatching) changes to

personality code 56 (photo nonlatching - CO nonlatching). This allows you to
use personality code 68 in the future for the SIGA-HCOS.

Personality code 51 (photo nonlatching - CO latching) changes to personality

code 55 (photo nonlatching - CO latching). This allows the PCOS CO element
to activate in the same manner as other CO devices (SIGA-PHCOS,
SIGA-COS, and SIGA-HCOS), with respect to how the sounder-relay base
operates. If you must control the sounder-relay base when a CO element
activates, set the Group Name option to a different group than None, and use
rules to program the base. See the Programming Signature Detector Bases
topic in the 3-SDU Help for more details.

3.2 Full support for SIGA2 detectors and modules

Previously, 3-SDU 5.02 provided partial support for SIGA2 PCOS and PHS
devices. 3-SDU 5.10 now provides full support equal to the support in
3-SDU 4.01.
For details on the partial support that was in 3-SDU 5.02, see A.1 Support for
SIGA2 detectors and modules on page 37.

P/N 270729 ISS 02MAY12

3 / 45

Table 2: SIGA2-PCOS feature support differences

Photo: Latching

Photo: Latching

Photo: Nonlatching Photo: Nonlatching

CO: Latching

CO: Nonlatching

CO: Latching

CO: Nonlatching

(Personality 64)

(Personality 67)

(Personality 55 --

(Personality 56

was 51)

was 68)

Device type/CO Setting

V5.02

V5.10

V5.02

V5.10

V5.02

V5.10

V5.02

V5.10

Smoke/CO Alarm

Smoke/CO Supervisory *

Smoke/CO Monitor

Supervisory/CO Alarm

Supervisory/CO Supervisory

Supervisory/CO Monitor

* Default configuration

3.3 Support of the CDR-3 Bell Coder on EST3X

Previously, 3-SDU 5.02 did not support the CDR-3 Bell Coder. 3-SDU 5.10 now
provides full support of the CDR-3. For further details on setting the CDR-3 parity
for extended digit operation on an EST3X panel, see 13.15 CDR-3 Bell Coder
parity on page 34.
3.4 Support of the new 3X-FIB network fiber optic card
The new 3X-FIB card gives an EST3X panel the ability to network via fiber optic
cable with EST3 systems, up to a maximum of 64 nodes. The card supports
Class A or Class B network and Class A or Class B audio data, and provides
single- or multiple-mode network and digital audio fiber optic connections.
This card replaces the 3-FIBMB2 card for EST3X. The 3-FIBMB2 generates a
network compatibility fault when used on an EST3X panel.
3.5 Support of new DS and DH nonmapping detectors
This release supports two new nonmapping detectors DS (photoelectric smoke)
and DH (fixed temperature heat) for the International or China marketplaces only.
These models are similar to other Signature series detectors, except:

Any Signature data circuit that contains either of these new devices does not
support the traditional Signature mapping. Note however that users still have
to reconcile actual versus expected devices using the Mapping window in
the 3-SDU.

The device LEDs do not flash to indicate communication. This is called the
inhibit normal flash mode; users can bypass it temporarily to use the normal
flash, for example, while performing a visual inspection during service tests.

P/N 270729 ISS 02MAY12

4 / 45

They support three prealarm or alternate prealarm thresholds: None, 50%, or

75%.

The DS supports two sensitivity or alternate sensitivity levels: least and

normal.

In the China marketplaces, the panel turns on the LED to a steady red pattern
for the first 32 active/alarm state activations; for subsequent activations it
turns on the LED to a flashing red pattern.

They are supported on EST3 panels only.

Note: For DS or DH devices you must use a 3-SSDC1(C) or 3-SDDC1(C) loop

controller running application code version 04.10 and bootloader code version
04.00.00 or later, in an EST3 cabinet.
3.6 New NACCO command
Version 5.10 adds the following new command for the PS10-4B in EST3X
cabinets only:

NACCO: Sets the notification appliance circuit's output to the CO alarm signal
pattern: 1/10th second on, 1/10th second off, 1/10th second on, 1/10th
second off, 1/10th second on, 1/10th second off, 1/10th second on, 5-1/10th
seconds off.

3.7 R-Series password update

We have corrected common control password operation on the R-Series
annunciator. Previously, when adding an EST3X panel to an existing EST3
project, the panel could prevent a user from entering a password to enable
common controls on the R-Series RLCD-C.
3.8 Security device type removal for EST3X
We have removed the Security device type in the Add Modules for Signature
Loop Configuration dialog box for EST3X panels. When you open an existing
5.02 project for the first time in SDU 5.10, the SDU converts the Security device
type to the Supervisory device type. This could require a change to existing rules,
and the SDU notifies the user of this possibility.
3.9 Partition group removal for EST3X
Partition groups are not supported in EST3X. When you open a project in
SDU 5.10, the SDU removes any existing partition groups from projects that
contain only EST3X cabinets (CAB6s). On combination networks, the SDU does
not remove partition groups.

P/N 270729 ISS 02MAY12

5 / 45

3.10 Removal of 3-CPU versions earlier than V3.05

If you are using the 3-CPU, SDU V5.10 requires that you use V3.05 or later, and
therefore no longer includes versions of the 3-CPU microcode earlier than V3.05.
Once you have decided which new 3-CPU version to use, download the new
microcode to the panel(s). In some cases you may also have to download the
bootloader and/or the database.
To determine what you need to download:
1. Refer to Table 3 to determine exactly what version you need to download to
each panel in your EST3 project. This table assumes you are using
SDU V5.10.
2. Perform the applicable downloads.
3. Save the project. Note that when you perform a software download, you must
also conduct the appropriate upgrade testing on the system. See NFPA 72
National Fire Alarm and Signaling Code for details on retest requirements for
site-specific software (database) and executive software (application or boot
code).
Table 3: New 3-CPU downloads required, per existing 3-CPU version
Current
3-CPU
application
microcode
version

New application microcode version downloads

03.05.00

03.65.00

03.75.00

04.05.00

05.03.00

<3.0

A, B, D

A, B, D

A, B, D

A, B, D

A, B, D

03.00.00

A, B, D

A, B, D

A, B, D

A, B, D

03.10.00

A, B, D

A, B, D

A, B, D

A, B, D

03.20.00

A, B, D

A, B, D

A, B, D

A, B, D

03.41.00

A, B, D

A, B, D

A, B, D

A, B, D

03.50.00

A, B, D

A, B, D

A, B, D

A, B, D

03.60.00

A, B

A, B, D

A, B, D

A, B, D

A, B

A, B, D

A, B, D

03.80.00

A, B, D

A, B, D

03.82.00

A, B, D

A, B, D

03.83.00

A, B, D

A, B, D

04.00.00

A, B, D

03.70.00

05.02.00

A, B, D

A Application Code (download)

B Bootloader Coder (download)
D Database (compile, convert, download)

P/N 270729 ISS 02MAY12

6 / 45

3.11 3-SDU bug fixes

The two previous 3-SDU releases (4.01 and 5.02) had an issue concerning the
writing of rules for SIGA2 PHS, PCOS, and PHCOS devices; those releases
allowed the user to write rules for input events that were not valid for the
configuration of the device. In this situation, it was possible that the panel would
run the wrong rule response when an event occurred on the SIGA2 device.

ALARM events were allowed for PHS devices configured without a

Photo/Heat is Alarm operation

ALARMSMOKE events were allowed for PCOS and PHCOS devices

ALARMHEAT events were allowed for PCOS and PHCOS devices

3.12 Additional miscellaneous bug fixes

Drill routing is now enabled to all cabinets.

Various report fixes, including a fix to the Input/Output Correlations report (it
had been quadrupling the number of responses).

Communication fixes including: an access violation caused when selecting

the wrong comm port, a disconnect issue with the power supply diagnostics, a
panel reboot caused by a single-step download to an incorrect cabinet, and
an access violation that sometimes occurred while canceling
communications.

Deviations for 4.01 have been included that fixed issues with the Hebrew,
Chinese, and Arabic languages.

24 Hour Retry counter has been fixed in the EST3X Loop Controller Status
and Diagnostic dialog boxes, where the counter was not updating correctly.
This fix requires an upgrade of the EST3X CPU firmware.

The AADC can now be converted in the Mid-East marketplace. Previously the
SDU prohibited this conversion; we have added the missing default
configuration files for the AADC to correct this problem.

For the European marketplace, 3-SDU release V4.0 used incorrect EADC
default configuration tables. V5.10 corrects this by providing updated EADC
default configuration files for the European marketplace.

3.13 SDU Help updates

For all existing and new features, the 3-SDU 5.10 provides context sensitive Help
topics. Pressing the F1 key displays a Help topic that corresponds to the location
and task being performed.
The 3-SDU 5.10 Help requires that you have Internet Explorer 6 or later installed.
The compiled HTML Help file is not compatible with other Web browsers.

P/N 270729 ISS 02MAY12

7 / 45

4 Language support
The following tables detail the language support available in 3-SDU version 5.10.

Arabic
(United Arab Emirates)

International

Arabic

New Zealand

Australia AS7240

Singapore

China

Australia AS4428

Middle East

Europe

Canada

Language

US

Table 4: Language support on projects containing EST3 panels only

Chinese
(Simplified PRC)

Chinese
(Traditional Taiwan)
Dutch
(Standard - Netherlands)

English
(Australia)

English
(Britain)
English
(USA)

X
X

Finnish
(Finland)
French
(Canada)

X
X

X
X

German
(Standard - Germany)

X
X

Hebrew
(Israel)

Italian
(Italy)

X
X

X
X

Korean
(Extended Wansung Korea)
Polish
(Poland)
Portuguese
(Brazil)

P/N 270729 ISS 02MAY12

X
X

8 / 45

Portuguese
(Standard - Portugal)

International

Arabic

New Zealand

Australia AS7240

Singapore

China

Australia AS4428

Middle East

Europe

Canada

US

Language

Russian
(Russia)

Slovak
(Slovakia)

Spanish
(Mexico)

Spanish
(Modern Sort - Spain)

Turkish
(Turkey)

Language

US

Canada

Table 5: Language support on

projects containing EST3X panels
only, or a combination of EST3X
and EST3 panels

English (USA)

French (Canada)

Portuguese (Brazil)

Spanish (Mexico)

Note: The KPDISP provides a single layout for use in the markets and languages
served by the American, European, Middle East, and Australian marketplaces.
4.1 Bilingual language character sets (for EST3 panel only projects)
When selecting a primary and secondary language, both languages must be
supported in the same font table.

P/N 270729 ISS 02MAY12

9 / 45

Table 6: Bilingual character sets

EST3 code page

Bilingual language sets

1250 (Eastern Europe)

Croatian, Czech, English, Hungarian, Polish, Slovak

1251 (Cyrillic)

English, Russian

1252 (Western Europe)

Danish, Dutch, English, Finnish, French, German, Italian,

Norwegian, Portuguese, Spanish, Swedish

1254 (Turkish)

English, Turkish

1255 (Hebrew)

English, Hebrew

Note: When using English as one of the languages in a code page, it must be set
as the secondary language on the Configure Project > Operations tab. The
exception to this is the Western Europe code page, where English can be set as
the secondary or the primary language.
4.2 Printer code pages
The following table shows the DOS code page support required to allow you to
print in the local language. Since not all of Windows characters are available on
the DOS printer, some characters may not be supported.
Table 7: Printer code pages
EST3 code page

Printer code page

936 (Chinese Simplified)

Windows Code Page 936 (GB)

949 (Korean)

Windows Code Page 949 (Extended Wansung)

950 (Chinese Traditional )

Windows Code Page 950 (Big 5)

1250 (Eastern Europe)

DOS Code Page 852

1251 (Cyrillic)

DOS Code Page 866

1252 (Western Europe)

DOS Code Page 850

1254 (Turkish)

DOS Code Page 857

1255 (Hebrew)

DOS Code Page 862

1256 (Arabic UL)

DOS Code Page 864

5 Software versions and compatibility

5.1 LRM compatible versions
You must upgrade all applicable microcode versions to take full advantage of the
new features offered in 3-SDU 5.10.

P/N 270729 ISS 02MAY12

10 / 45

Table 8: 3-SDU 5.10 software compatibility

LRM

Oldest
version [1]

Latest
version

Medium

Part
number

3-ASU

1.4

3.4

Web

3-SDU

3-AADC

1.4

3.41

Web

3-SDU

3-AADC1

1.4

3.71

Web

3-SDU

3-CPUx

3.05

5.03

Web

3-SDU

3-EASC/3-EADC

3.61

4.0

Web

3-SDU

3-FTCU

1.0

1.2

Chip

190156

3-FTCU

1.4

3.4

Chip

190254

3-IDC8/4

1.1

3.6

Chip

190159

3-LDSM

1.0

3.0

Chip

190153

3-MODCOM(P)

3.0

3.6

Web

3-SDU

3-OPS

1.0

3.0

Chip

190158

3-PPS

1.0

3.63

Chip

190157

3-BPS

1.0

3.63

Chip

190157

3-BBC

3.0

3.63

Chip

190157

1.5

PAL Chip

190271

3-RS485-A/B
3-RS485-R
3-SSDC/3-SDDC

1.52

3.32

Web

3-SDU

3-SSDC1/3-SDDC1

1.52

4.02, 4.10 [2]

Web

3-SDU

3-SAC

3.1

3.6

Web

3-SDU

3-ZA15

1.1 [3]

N/A

Chip

190151

1.3

N/A

PAL Chip

190191

1.4

3.6

Chip

190252

1.4

1.4

PAL Chip

190191

1.0

1.0

PAL Chip

7400068

1.4

3.6

Chip

190252

1.4

1.4

PAL Chip

190191

1.0

1.0

PAL Chip

7400068

1.1 [3]

N/A

Chip

190151

1.3

N/A

PAL Chip

190191

1.4

3.6

Chip

190252

1.4

1.4

PAL Chip

190191

1.0

1.0

PAL Chip

7400068

1.4

3.6

Chip

190252

3-ZA20A

3-ZA20B

3-ZA30

3-ZA40A

3-ZA40B

P/N 270729 ISS 02MAY12

11 / 45

LRM

Oldest
version [1]

Latest
version

Medium

Part
number

1.4

1.4

PAL Chip

190191

1.0

1.0

PAL Chip

7400068

1.4

3.6

Chip

190252

1.4

1.4

PAL Chip

190191

1.4

3.6

Chip

190252

1.0

1.0

PAL Chip

7400068

C-CPU

1.03

1.10

Web

3-SDU

CRC

1.3

1.7

Web

3-SDU

KPDISP

1.0

1.6

Web

3-SDU

CDR-3

2.0

3.5

Chip

190071

RLCD

2.0

2.02

Chip

RLCD

RLCD-C

2.0

2.02

Chip

RLCD-C

RLED

2.0

2.02

Chip

RLED

GCI

2.0

2.02

Chip

GCI

3-ZA90

3-ZA95

[1] Oldest version still compatible with the current version of SDU
[2] International and China markets only.
[3] Version 1.12 required for stand-alone mode disabled feature. To obtain V1.12, request a
deviation version for part number 190151 from Technical Support.

Notes

All 3-CPUx panels on a network must use the same version of microcode.
Networks with 3-CPU microcode version 3.0 or later can be upgraded with the
SDU by using the network download function. See 11 Upgrading microcode
versions on page 24.

The 3-CPU3 is 100 percent backward compatible with, and can be installed
on the same network as, 3-CPU1 and 3-CPU.

3-FTCU firmware comes in two noninterchangeable forms. Part 190254

cannot be used to update Part 190156, and vice versa.

5.2 SDU database compatibility

Use the 3-SDU 5.10 to generate databases for the LRMs listed in Table 9.
Table 9: LRM microcode supported by 3-SDU 5.10
LRM

SDU supported microcode versions

3-AADC

V1.4, V3.0, V3.1, V3.41

3-AADC1

V1.4, V3.0, V3.1, V3.41, V3.6, V3.7, V3.71

P/N 270729 ISS 02MAY12

12 / 45

LRM

SDU supported microcode versions

3-ASU

V1.4, V3.0, V3.1, V3.4

3-CPU

V3.05, V3.65, V3.75, V4.05, V5.02, V5.03

3-EADC/EADC

V3.61, V4.0

3-MODCOM(P)

V3.0, V3.1, V3.11, V3.12, V3.6

3-SAC

V3.1, V3.5, V3.6

3-SSDC/SDDC

V1.52, V2.1, V3.32

3-SSDC1/SDDC1

V1.52, V2.1, V3.32, V3.6, V3.7, V3.71, V3.83, V4.0, V4.02, V4.10

C-CPU

V1.06, V1.10

CRC

V1.3, V1.4, V1.5, V1.6, V1.7

KPDISP

V1.0, V1.1, V1.2, V1.3, V1.4, V1.5, V1.6

5.3 LRM and 3-CPU V5.02 or V5.03 microcode compatibility

The following table identifies the latest version of LRM microcode that is
compatible with 3-CPUx V5.02 and V5.03 microcode. We recommend that you
use the latest version of LRM microcode.
Table 10: LRM and 3-CPU V5.02 or V5.03
microcode compatibility
LRM

Microcode version

3-AADC

V3.41

3-AADC1

V3.71

3-ASU

V3.4

3-EASC

V4.0

3-EADC

V4.0

MODCOM(P)

V3.6

3-SAC

V3.6

3-SSDC/
3-DSDC

V3.32

3-SDDC

V3.32

3-SSDC1/
3-DSDC1

V4.02, V4.10 [1]

3-SDDC1

V4.02, V4.10 [1]

C-CPU

V1.06, V1.10

CRC

V1.7

KPDISP

V1.6

[1] For China and International marketplaces only

P/N 270729 ISS 02MAY12

13 / 45

6 Microcode updates for 3-CPU V3.05, V3.65, V3.75

The 3-CPU V3.05, V3.65, and V3.75 microcode includes EST3 data network
improvements. These improvements include detection of a disconnected panel
during momentary network line faults upon network startup, and improved
network supervision to increase reliability of delivery of events across the
network.

7 Microcode updates for 3-CPU V4.05, V5.03

The 3-CPU V4.05 and V5.03 microcode:

Includes EST3 data network improvements

Corrects ground fault LED operation

Updates restoration on the SIGA2-PHS heat and smoke alarm

Shows output messages in the Status report

Updates printer port restoration

Adds new commands to support the ECP protocol: SensorBypass,

GasAccelResponse, RemoteReadLock, RemoteWriteUnlock

Prevents scroll speed configuration from generating a reboot of the panel, in

the China marketplace.

Updates the Fireworks Revision Report (V5.03 only)

7.1 EST3 data network improvements

We have implemented improvements to the EST3 data network. These
improvements include detection of a disconnected panel during momentary
network line faults upon network startup, and improved network supervision to
increase reliability of delivery of events across the network.
7.2 Ground fault LED correction
Previously in the New Zealand and Australian 4428 marketplaces, when service
groups activated the panel turned on the ground fault LED intermittently. This
release corrects that operation.
7.3 SIGA2-PHS restoration updates
This release updates the alarm queue mechanism to ensure that Heat Alarm and
Smoke Alarm events restore in the proper order.
7.4 Output messages in Status report
This release displays output messages in the Status report, when output devices
are active.

P/N 270729 ISS 02MAY12

14 / 45

7.5 Printer port restoration

This release directs restoration messages to printer 2 (port 2). Also restoration
events now follow the message routing settings.
7.6 New command support for FireWorks
This release adds new commands to support the ECP protocol: SensorBypass,
GasAccelResponse, RemoteReadLock, and RemoteWriteUnlock. By adding
these commands to 3-CPU V4.05 and V5.03 now, we enable FireWorks users to
execute them as soon as they become available in a future FireWorks release.
For more details on these commands, see the 3-SDU Help.
7.7 Scroll speed
In the China marketplaces, configuring the scroll speed no longer generates a
reboot of the panel.
7.8 Fireworks Revision report (V5.03)
The V5.03 release eliminates random characters that appeared in the Fireworks
Revision report.

8 Microcode updates for C-CPU V1.06

The C-CPU V1.06 microcode:

Removes self-restore on database supervision fault

Generates trouble event when panel in download mode

Improves reliability of RJ-11 and RS-232 communication

8.1 Database supervision self-restore

When a database supervision fault occurs on the internal loop controller, the fault
no longer automatically restores. To restore the fault, download the loop
controller database again. If the fault remains, replace the SFS1-ELEC.
8.2 Panel in Download event
With this release, when the panel enters the download mode it generates a
trouble event to other nodes on the network.
For details on how the panel can enter download mode, see 13.11 Failure to
load CPU database on page 33.
8.3 Improved communication
This version of the C-CPU improves the reliability of RJ-11 and RS-232
communication.

P/N 270729 ISS 02MAY12

15 / 45

9 Microcode updates for C-CPU V1.10

The C-CPU V1.10 microcode:

Supports SIGA2 functionality equivalent to 3-SDU 4.01

Enhances LCD menu operations

Supports detail reports on the R-Series for logical groups

Improves robustness of database and firmware downloads

Improves robustness of LRM communication

Broadcasts task failure events across the network

Improves integrity supervision to reduce load on CPU

Reduces network overflow errors

Processes large number of events without fault

Corrects issue with loop controller 24-hour counter

Prevents exception events after downloading the CPU database only

Corrects CO End of Life trouble restoration

Updates the SIGA2 photo nonlatching personality

Improves the boot up process

Removes self-restore on database supervision fault

Generates trouble event when panel in download mode

Improves communication with EST3X internal loop controller

9.1 Supports SIGA2 functionality equivalent to 3-SDU 4.01

The C-CPU V1.10 microcode now supports full SIGA2 functionality. See 3.2 Full
support for SIGA2 detectors and modules on page 3 for more details.
9.2 Enhances LCD menu operations
C-CPU V1.10 includes the following LCD menu enhancements:

Adds a new menu option to clear history of all panels

Displays the warning message "continuing to arm partition" when using an

EST3X combination system (with security enabled) to arm a partition

Updates the detail reports to allow scrolling to next queue item without
jumping to top of queue

Corrects an issue with the delete a holiday menu, where the LCD was
automatically deleting first holiday entry

P/N 270729 ISS 02MAY12

16 / 45

9.3 Supports detail reports on the R-Series for logical groups

In conjunction with R-Series firmware V2.02 or higher, the C-CPU now allows the
R-Series to support detailed LCD reports for ZONE, AND, and MATRIX groups.
9.4 Improves robustness of database and firmware downloads
This version of the C-CPU improves robustness of storing the database and
firmware images into nonvolatile memory. It also improves RJ-11 and RS-232
communication.
9.5 Improves robustness of LRM communication
C-CPU V1.10 improves the robustness of LRM communication, reducing the
likelihood of rail communication faults.
9.6 Broadcasts task failure trouble events across network
The panel supervises internal tasks and generates a trouble if there are any
failures. When this occurs, the C-CPU now broadcasts the task ID of the specific
task failure across the network to all panels, and no longer generates an internal
fault.
9.7 Improves integrity supervision to reduce load on CPU
This version of the C-CPU updates the scheduling of background integrity
supervision in order to reduce the load on the CPU and nonvolatile memory.
9.8 Reduces network overflow errors
We have made updates that reduce the possibility of generating network
overflow errors when processing a large number of events and transmitting them
across the network.
9.9 Processes large number of events without fault
The C-CPU firmware no longer generates an internal fault when processing a
large number of events.
9.10 Corrects issue with loop controller 24-hour counter
The loop controller now updates the 24-hour counter correctly and, in conjunction
with the 3-SDU V5.10, properly displays the 24-hour counter.
9.11 Prevents exception events after downloading the CPU database only
The C-CPU no longer produces an exception event which causes the EST3X
panel to continually reboot when the SLC field wires are still connected.

P/N 270729 ISS 02MAY12

17 / 45

9.12 Corrects CO End of Life trouble restoration

The CO End of Life trouble event is no longer inadvertently restored by
background supervision. It is restored only if the CO device itself has restored the
fault.
9.13 Updates the SIGA2 photo nonlatching personality
When the SIGA2-PHS is set to the photo nonlatching personality (51), the photo
element latches when the heat element is active.
9.14 Improves the boot-up process
Bootloader version 1.10 improves the reliability of booting up the C-CPU
application. C-CPU V1.10 of the application also improves the boot up process
and reduces the CPU Fail events experienced in the previous version.
9.15 Removes self-restore on database supervision fault
When a database supervision fault occurs on the internal loop controller, the fault
no longer automatically restores. To restore the fault, download the loop
controller database again. If the fault remains, replace the SFS1-ELEC.
9.16 Generates Panel in Download event
With this release, when the panel begins the download mode it generates a
trouble event and sends it to other nodes on the network. For details on one of
the ways that the panel can enter the download mode, see 13.11 Failure to load
CPU database causes download mode on page 33.
9.17 Improves communication on EST3X
This release adds more error checking to the Signature communication on the
EST3X internal loop controller, thus improving reliability.

10 Installing and upgrading to 3-SDU 5.10

10.1 Upgrading
You must uninstall previous versions of the 3-SDU before installing
3-SDU V5.10, either by using the shortcut in the Windows Start menu or by using
the Control Panel. As a best practice, always export and save all projects to a
backup location before uninstalling the 3-SDU.
The 3-SDU does not remove the Projects folder during the uninstall process;
however the location to which you install the new version affects the list of
projects shown by 3-SDU V5.10.

If you are installing into the same directory as the previous installation, the
3-SDU does not overwrite the old Projects folder, so your existing projects

P/N 270729 ISS 02MAY12

18 / 45

remain intact. Then when you open an existing project, the 3-SDU converts
that projects internal database format to work with 3-SDU V5.10.

If you are installing into a different directory than the previous installation, the
Projects folder will be empty. Your old projects still exist in the Projects folder
of your previous installation directory, but are not accessible from the V5.10
installation of the 3-SDU. To correct this, after you have finished upgrading to
3-SDU V5.10, import your existing projects from your backup location.

10.2 Installation prerequisites

The only prerequisite for installing the SDU is the HASP device driver. The
HASP4 installs if you are running on a 32-bit system, while the Sentinel HASP
installs if you are running on a 64-bit system.
To begin loading the requirements, double-click the SDU setup.exe file. When
the Requirements window appears, click the Install button and step through the
HASP installation.
Figure 1: The Requirements window

The HASP requirement only appears during a first-time installation. Any

subsequent installations of the SDU application do not display the HASP
requirement, because it has been installed previously.

The SDU application begins installing immediately after the HASP is

completely installed.

P/N 270729 ISS 02MAY12

19 / 45

The HASP does not uninstall if you uninstall the SDU. If you need to uninstall
the HASP, use the Control Panel.

10.3 Installing the SDU

The SDU application begins installing immediately after the HASP requirement
has installed completely.
To install the SDU:
1. Finish loading the HASP requirement, if you have not previously loaded it.
2. The 3-SDU installation wizard starts, and displays the welcome page. Click
Next.

3. The License Agreement page appears. Click Yes to accept the license.

P/N 270729 ISS 02MAY12

20 / 45

4. The Choose Destination Location page appears. Click Browse to select

another folder or click Next to choose the default path C:\FAST\3-SDU\.

5. The Ready to Install page appears. Click Install to begin transferring files.

P/N 270729 ISS 02MAY12

21 / 45

10.4 Installing the Borland Database Engine

The Borland Database Engine installs as a part of the SDU installation. You can
click Browse to select another folder, or click OK to choose the default path
C:\Program Files\Common Files\Borland Shared\BDE. While you can install the
BDE in any location, we do not recommend changing the default path.
To install the Borland Database Engine:
1. Do not click the Cancel button, because any attempt to cancel the BDE
installation generates an error.

2. If the BDE is already installed in the default directory, it overwrites the

previous installation. You can also install the BDE in multiple directories.
Neither of these scenarios affects the operation of the SDU application.
3. If you have another application window open while you are installing the SDU,
the BDE installation window goes behind other active windows. When this

P/N 270729 ISS 02MAY12

22 / 45

happens, the SDU installation remains in a wait mode until you activate the
BDE dialog box again. To do so, select the BDE task from the taskbar and
continue the installation. The best practice is to close all applications and
monitor the SDU installation.

Note: Increase the Zoom in this PDF if you want to see details in this screen
shot.
4. Click on Borland Database Engine in the taskbar to activate it, and then click
OK.

P/N 270729 ISS 02MAY12

23 / 45

5. After the Borland Database Engine finishes installing, the Finish page
appears. Click Finish to complete the SDU installation.

11 Upgrading microcode versions

11.1 3-CPUx version 5.03
Project version numbers are embedded in each project file. Because the Save As
command creates a new version number that is different than the embedded
version, you must use the following procedure to install V5.02. Please follow
these steps in the correct order to upgrade the hardware and software in your
system.
Notes

When adding an EST3X panel to an EST3 Network, upgrade your EST3

microcode to 5.03 before connecting EST3X nodes to the EST3 network.

Do not mix different versions of 3-CPUx microcode on the same network.

Upgrade an existing system by carefully following this procedure.

To upgrade V3.0 or later to V5.03:

1. Install SDU version 5.10.
2. Click Project > Open and select your project from the Open Project dialog
box. Click OK to open the project.
Note: When you open a project, the SDU may give you a warning that states
Some or all of this projects selected MicroCode versions do not exist or are
incompatible with the Brand or Marketplace. Click OK to update to the latest

P/N 270729 ISS 02MAY12

24 / 45

versions or click Ignore and fix the problem manually. If you click Ignore and
do not select valid versions of microcode, errors can occur when configuring
the LRMs. Therefore, if you click Ignore, also go to the Project Parameters >
MicroCode tab and verify that the selected microcode versions are all
supported; the SDU highlights in red those versions that are no longer
supported.
3. Click OK to upgrade the microcode of your project.
4. Save your project as a new version, using the Save As command on the File
menu.
5. Click Rules > Compile to recompile your project.
6. Click Tools > DB Conversion > All Databases to create databases for the loop
controllers and cabinets.
7. Click Project > Save to save the recompiled project.
8. Click Tools > Communications and select Network for the Download mode.
9. From the LRM Type Display Filter group, select 3-CPU. From the File Display
Filter group, select three options, Boot loader code, Application code, and
Database for each panel. (Do not select any other option.)
10. On Class B networks, connect the SDU to the first CPU (sometimes called
the service panel). On Class A networks you can connect the SDU to any
node on the network.
11. Click Download and Start to begin the network download.
11.2 Upgrading firmware on 3-DSDC(1)(C), 3-SDDC(1)(C), and 3-AADC(1)
loop controllers
You must upgrade the 3-CPUxs before upgrading the loop controllers.
You can upgrade the loop controllers using network downloads.
If the bootstrap download fails, or if the steps are performed out of order, you
must cycle the power on the panel and restart the upgrade by downloading the
bootstrap code again.
You must complete each of the following steps in separate download sessions.
To upgrade the loop controllers:
1. Download the 3-SSDC/3-SDDC/3-AADC bootstrap to each LRM. (Download
the bootstrap only; do not download the application code or database.)
2. From the 3-LCDXL1C, issue a restart command for all panels.
3. Download the 3-SSDC/3-SDDC/3-AADC application code.
4. Download the 3-SSDC/3-SDDC/3-AADC loop controller databases.

P/N 270729 ISS 02MAY12

25 / 45

11.3 Upgrading the 3-ASU

When upgrading the 3-ASU, we recommended that you do so in the following
order:
1. Download the boot code
2. Download the application code
3. Download the database
11.4 Upgrading the CRC
When upgrading the CRC/CRCXM, we recommend that you do so in the
following order:
1. Download the SDU application code
2. Download the SDU database
3. Download the ACDB database (from the CRC Administration tab, select the
Destination DB Init task)
Note: Upgrading the code to a CRC disables the access functionality for the door
being controlled, until you use the ACDB to download its corresponding
database.
11.5 Upgrading from C-CPU V1.03 to V1.06
Caution: If you have C-CPU V 1.03 loaded in your panel, you must upgrade to
either V1.06 or V1.10.
V1.06 is compatible with all 1.0x databases, and therefore does not require you
to download the database again.
Steps to upgrade C-CPU to 01.06:
1. Install 3-SDU V5.10.
2. Click File > Open and select your project from the Open Project dialog box.
Click OK to open the project.
3. On the Project/Microcode tab, select the 01.06 version for C-CPU.
4. Click Tools > Communications and select Network for the download mode.
5. Select the CPU application code and bootstrap for each panel.
6. Connect your PC to any CPU node on the network.
7. Click Download and Start to begin the network download.

P/N 270729 ISS 02MAY12

26 / 45

11.6 Upgrading C-CPU to version 01.10

Firmware 01.10.00 is not compatible with older databases (V1.03 and V1.06).
The new application and all databases must be downloaded to all panels in the
system. Do not mix different versions of C-CPU microcode on the same network;
upgrade an existing system by carefully following these steps.
Steps to upgrade C-CPU to 01.10:
1. Install 3-SDU V5.10.
2. Click File > Open and select your project from the Open Project dialog box.
Click OK to open the project.
3. On the Project/Microcode tab, select the 01.10 version for C-CPU.
4. Save your project as a new version, using the Save As command on the File
menu.
5. Click Rules > Compile to recompile your project.
6. Click Tools > DB Conversion > All Databases to create databases for the loop
controllers and cabinets.
7. Click File > Save to save the recompiled project.
8. Click Tools > Communications and check Network for the download mode.
9. Select the CPU Application code, bootstrap, C-CPU database, and the
internal loop controller database (slot 3) for each panel.
10. Connect your PC to any CPU node on the network.
11. Click Download and Start to begin the network download.
12. After the download finishes and the panels start up, the LCD shows the
following internal fault:
"xx000604Internal Fault", where xx is the panel address
Restart the network to restore the fault. From any panel in the network, select
Program Menu > Restart and perform a restart of all panels.
11.7 Downgrading C-CPU from V1.10 to V01.0x
You may want to downgrade a C-CPU version from 1.10 to 1.0x in certain
situations.
To downgrade the C-CPU version, follow these steps.
1. Install V5.10 of 3-SDU.
2. Click File > Open and select your project from the Open Project dialog box.
Click OK to open the project.
3. On the Project/Microcode tab, select the 01.0x version for C-CPU.

P/N 270729 ISS 02MAY12

27 / 45

4. Save your project as a new version, using the Save As command on the File
menu.
5. Click Rules > Compile to recompile your project.
6. Click Tools > DB Conversion > All Databases to create databases for the loop
controllers and cabinets.
7. Click File > Save to save the recompiled project.
8. Click Tools > Communications and check Network for the download mode.
Select the C-CPU application code, the C-CPU database, and the internal
loop controller database (slot 3) for each panel.
9. Connect your PC to any CPU node on the network.
10. Click Download and Start to begin the network download.

12 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 tested 100 percent.

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.

13 Known issues
The following known issues exist for SDU version 5.10.
13.1 Windows Vista and Windows 7
Some features in the SDU require you to run the program with higher privileges
in the execution level scheme for Windows Vista or Windows 7. However, when
you run at the higher privilege level, the User Account Control dialog box
appears.

P/N 270729 ISS 02MAY12

28 / 45

Figure 2: User Account Control

This appears because the SDU is not currently certified with electronic signature
verification software. Click Allow to run your SDU with full functionality.
13.2 Changes before DB Conversion and download to the panel
Many changes, such as changing or deleting devices, DACT accounts, etc. that
are used in a rule, can cause serious panel operation problems if you download
the database directly to the panel. Always compile the rules after you have made
changes to objects, and before you run a DB Conversion and download the
database to the panel.
13.3 Changes made after installation
If you copy files into the installation directories after the installation, or create files
while running the SDU, the system will not uninstall those files and the directory
tree containing them during the uninstall process. This includes all project files
(by design) and settings used relating to projects. We recommend exporting your
project files to another location before uninstalling the SDU.
13.4 QuickStart concurrent installation
If you install the 3-SDU 5.10 after installing the QuickStart QS-CU, the SDU
installation overwrites the C:\WINDOWS\system32\dunzip32.dll and
C:\WINDOWS\system32\dzip32.dll files. The SDU uses newer versions of these
files that the QS-CU cannot use, so if this happens the import of QuickStart
projects into the QS-CU will fail. QuickStart will be rebuilt to use the correct files
in a future release. Either of the following workarounds will solve the issue:

P/N 270729 ISS 02MAY12

29 / 45

Before installing the 3-SDU 5.10, copy the C:\WINDOWS\system32\

dunzip32.dll and C:\WINDOWS\system32\dzip32.dll from the Windows
directory to the QuickStart directory.

Manually delete C:\WINDOWS\system32\dunzip32.dll and C:\WINDOWS\

system32\dzip32.dll, and reinstall QuickStart after installing the SDU.

13.5 Fonts and resolution

You must run the SDU on a computer with a resolution of 1024 x 768 or greater
and use normal size fonts, that is, DPI setting: Normal size (96 DPI). If you use
any other font setting the SDU buttons may not be accessible.
13.6 Using time controls to disable zone groups
Members of a zone group are not disabled if the zone group is disabled via a
time control. Do not use time controls to disable a zone group.
13.7 Time synchronization
3-CPU Version 03.10.00 has a known issue with the time synchronization
command. If your system has Time Synchronization > System Time Source set
to 3-LCD User Interface, then any communication with the 3-CPU will cause the
system to reboot. We recommend that when you use 3-SDU 5.10 you set Time
Synchronization > System Time Source to Input Circuit.
13.8 Compatibility with FireWorks version 1.60.xx and earlier
FireWorks versions 1.60.xx and earlier have a compatibility issue with 3-SDU
version 4.01 and later, regarding data imported from CO devices and split
configuration modes on SIGA2 model detectors only. Since FireWorks does not
recognize the CO devices or elements in a split configuration, it reports
undefined errors for those devices/elements. Note: Split configurations are
selected in the Operations option on the Signature Series Configuration
Detectors tab.
The device/element activation produces the following results:

SIGA2-HCOS activations import as a normal Heat detector activation. CO

activations import as undefined errors.

SIGA2-PHCOS activations import as a normal Photo detector activation. CO

activations import as undefined errors.

SIGA2-PCOS activations import as a normal Photo detector activation. CO

activations and supervisory activations import as undefined errors.

SIGA2-PHS activations import as a normal Photo detector activation. If the

device is configured as anything other than Photo/Heat is Alarm activations
import as undefined errors.

P/N 270729 ISS 02MAY12

30 / 45

SIGA2-COS activations import as undefined errors.

You can verify the data in your import file from the SDU Import window. Click the
Verify OXP File button to view data in the OXP file that FireWorks cannot
understand. See Figure 3.
Figure 3: SDU Import errors (types 141 and 142)

When the import finishes, FireWorks lists the devices that it could not define. See
Figure 4.
Figure 4: SDU Import undefined device messages

P/N 270729 ISS 02MAY12

31 / 45

Since FireWorks cannot understand these devices, it does not include them in
the System Builder tree. Therefore, the device list may no longer be numbered
logically. See Figure 5.
Figure 5: System Builder sequence interruption due to unrecognized devices/elements

When one of these devices activates, FireWorks annunciates the event as

undefined in the System Control window. The messages appear in red in the
Event Action and Event List Action panes, are similar to an alarm event, and
identify the event as undefined alarm or undefined error.
13.9 R-Series remote annunciator group details
The following functions for R-Series remote annunciators are not enabled at this
time:

Matrix details

Service group details

P/N 270729 ISS 02MAY12

32 / 45

13.10 Rate of rise not available for SIGA-HCOS

Configure the HCOS to use only fixed temperature personalities by selecting
either the 69 Fixed CO Active 3 non-latching or the 69 Fixed CO Active
3 non-latching personality code option in the SDU. The rate of rise personality
is not available at this time for the SIGA-HCOS.
13.11 Failure to load CPU database causes download mode
An issue can occur when downloading C-CPU version 1.10 to an EST3X panel
containing a database that was previously compiled or converted with C-CPU
V1.0x.
When the database in the panel is not compatible with the CCPU microcode
version, the panel enters the download mode and displays the following
messages on its LCD:
Download Mode
Failed to load CPU database
Please download a new CPU database
When the EST3X panel is in this condition, the Ethernet connection is no longer
available for the panel.
To get the panel out of download mode:
1. Select the appropriate microcode for the CPU.
2. Compile and convert the database.
3. Download the database to the CPU using an RS-232 or RJ-11 connection, or
via another panel on the network.
If an EST3X panel that resides in a network combined with EST3 panels enters
this state, all EST3X panels in that network generate a XX000684Network
Compatibility Fault. The XX represents the address of the EST3X panel that
generated the fault.
13.12 Saving 3-SDU reports to XLS format in Windows 7
When displaying a report in the 3-SDU, clicking the Save Report button on the
top of the screen offers the ability to save the report data in several formats. Due
to a conflict with Windows 7 and our third-party reporting tool, saving a report to
XLS (Excel) format produces a corrupt XLS file that cannot be viewed. We
recommend saving the report to CSV format and then opening the file in Excel.
13.13 Auto Generate Events CID option requires 3X panels only
When configuring a 3-MODCOM, the Auto Generate Events option (which
creates CID events without the need to write rules) only functions for projects

P/N 270729 ISS 02MAY12

33 / 45

containing eight or less EST3X panels. Once you exceed eight EST3X panels or
add an EST3 panel, you have to write rules for all CID events.
13.14 Guard patrol acknowledge fault in proprietary marketplaces
When using proprietary marketplaces in EST3X with 3-CPU firmware (4.0 or
later) or C-CPU firmware, the acknowledge action of a Guard Patrol Late event
generates an internal fault. Restart the panel to restore the Internal Fault event.
Note: This is not an issue in nonproprietary marketplaces (e.g., US Local).
13.15 CDR-3 Bell Coder parity
When using the CDR-3 on an EST3X panel, set the CDR-3 to no parity" if you
need extended digit operation. See the CDR-3 Bell Coder Installation Sheet
(P/N 3100023) for details on the switch options.
13.16 Help topic on positive alarm sequencing in 3-SDU Help
The positive alarm sequence topic contains a misstatement in the example of
AND Group 3 (labeled AND_Group_PAS3). The Activation Event for the third
AND group in this configuration example should be set to Q4 Monitor (All
Others). Therefore the positive alarm sequence example in the Help topic should
appear as follows:
AND Group 1

Label: AND_Group_PAS1
Activation Number: 2
Activation Event: Q1 - Alarm
Devices in Selected Group: For all PAS devices, check Q1 and then clear Q2,
Q3, and Q4.

AND Group 2

Label: AND_Group_PAS2
Activation Number: 1
Activation Event: Q1 - Alarm
Devices in Selected Group: For all PAS devices, check Q1 and then clear Q2,
Q3, and Q4.

AND Group 3

Label: AND_Group_PAS3
Activation Number: 2
Activation Event: Q4 Monitor (All Others).
Devices in Selected Group: None

In addition, set the message routing options for the switches and AND Group 3 to
the no message routing group. Set the message routing options for AND Group 1
and AND Group 2 to the all message routing group. If you do not the SDU
compiler may stop, depending on your marketplace setting.
We will correct the positive alarm sequence Help topic in the next release of the
3-SDU Help.

P/N 270729 ISS 02MAY12

34 / 45

13.17 Asia marketplaces not supported

3-SDU V5.10 does not include support for the Asia Local and Asia Proprietary
marketplaces. If you must use an Asia marketplace, use 3-SDU V4.01 instead.

P/N 270729 ISS 02MAY12

35 / 45

Appendix A
Features in 3-SDU V5.02
Version 5.02 represented a significant enhancement to 3-SDU features. For
users who have not previously upgraded to 5.02, we include here as a
convenience the description of features from the 5.02 release notes. The full
document, 3-SDU Version 5.02 Release Notes, is also available at
https://est.edwardsutcfs.com/catalog/login/.

A. Features in 3-SDU V5.02

3-SDU 5.02 includes new features, as well as most of the features in all
previously released versions. Additional new features and differences between
earlier releases are as follows:

Support for SIGA2 detectors and modules

Enhanced microcode support
Support for the new EST3X panels
SDU Help

Support for the new EST3X panels includes:

Enhanced audio
Configurable NAC/AUX circuits
Power supply diagnostics
SFS1-CPU support (C-CPU in the SDU)
R-Series remote annunciators
New operator layer configuration with four-color LEDs
Advanced Signature loop controller diagnostics
Automatic Contact ID
IP communications

P/N 270729 ISS 02MAY12

36 / 45

A.1 Support for SIGA2 detectors and modules

3-SDU 5.02 supports SIGA2 detectors and modules, except that PCOS and PHS
detectors do not have the same level of support as in 3-SDU 4.01.
For SIGA2-PHS detectors, 3-SDU 5.02 does not support setting the value of the
Operation and Alt Operation options for: Photo is AlarmSmoke | Heat is
AlarmHeat. Table 11 lists the differences in support for SIGA2-PCOS detectors.
Full support for these detectors will be available in a future release.
Table 11: SIGA2-PCOS feature support differences
Photo: Latching

Photo: Latching

Photo: Nonlatching Photo: Nonlatching

CO: Latching

CO: Nonlatching

CO: Latching

CO: Nonlatching

(Personality 64)

(Personality 67)

(Personality 51)

(Personality 68)

Device type/CO Setting

V4.01

V5.02

V4.01

V5.02

V4.01

V5.02

V4.01

V5.02

Smoke/CO Alarm

Smoke/CO Supervisory *

Smoke/CO Monitor

Supervisory/CO Alarm

Supervisory/CO Supervisory

Supervisory/CO Monitor

* Default configuration

Please see the 3-SDU Version 4.01 Release Notes, available at

https://est.edwardsutcfs.com/catalog/login/.
A.2 Enhanced microcode support
The process of selecting versions of microcode (application code and bootloader
code) has changed. The MicroCode tab is now in the Project Parameters dialog
box (Configure > Project) instead of in the Cabinet Configuration dialog box.
Previously, you had to select a valid version of application and bootloader code
for each potential LRM. Now, you only have to select versions for the LRMs that
exist in the project. Because of this, when you create a new project, the
MicroCode tab is not visible until after you add a panel to the project.
The new MicroCode tab contains a table on the left that lists each LRM type in
the project that has microcode. The table also shows the currently-selected
versions of application code and bootloader code for each LRM type. When you
select an LRM type the list on the right side of the tab changes to show the
available versions of application code for that LRM. The SDU lists the newest
version on top and highlights the currently-selected version. Like the previous
MicroCode tab, the SDU selects the bootloader code version based on the
version of the selected application code.
P/N 270729 ISS 02MAY12

37 / 45

When you open a project, the SDU examines the currently-selected versions of
microcode. If the selected versions are not the most current versions, the SDU
produces this warning message: Some or all of this projects selected
MicroCode versions are out of date! and offers an opportunity to automatically
change to the latest versions, depending on the MicroCode Version Updates
option setting (Options > Customize > Behavior tab).
It is also possible that some of the currently-selected microcode versions are no
longer supported. If this is the case, the SDU produces this warning: Some or all
of this projects selected Microcode versions do not exist or are incompatible with
the Brand or Marketplace. You can ignore this warning, but certain processes
(DB Conversion for example) will not execute while you have invalid microcode
versions selected. On the MicroCode tab, the invalid selections appear in red and
are enclosed in parentheses.
A.3 Support for the new EST3X panels
The new EST3X panels represent the latest generation of life safety control
panels for mid-to-large size applications. With large multiple-message displays,
innovative controls, intuitive interface, and bold colored cabinets, these systems
capture the imagination and catch the eye. But behind the LCD display is where
they really shine.
New microprocessors and chipsets take full advantage of the latest advances in
computing technology, leading to smarter, faster, higher-capacity processing and

P/N 270729 ISS 02MAY12

38 / 45

more efficient designs. For example, the patented Voltage Boost technology
delivers consistent voltage even at low battery power resulting in lighter
cable requirements, longer wire runs, or both. This saves time and money.
High performance processing also leads to powerful networking features and
versatile digital audio functionality. The wide range of EST3X configurations
includes stand-alone operation, networked operation with up to eight EST3X
nodes, or integration with an EST3 life safety network comprising as many as
64 nodes complete with EST360 mass notification capabilities and display of
security events.
A.3.1 Enhanced audio
EST3X panels provide a full eight channels of integrated digital audio with up to
two minutes of on-board programmable message storage. The 3X-PMI Paging
Microphone Interface gives live access to local as well as remote audio functions.
Auxiliary inputs are available for mass notification operations, and you can mount
amplifiers directly on the EST3X rail assembly.
A.3.2 Configurable NAC/AUX circuits
The EST3X power supply provides four output circuits that you can individually
configure as notification appliance circuits or as auxiliary power circuits. The four
output circuits are configured using these device types:

DamperControl

G_Audible (Genesis Audible)

DoorControl

G_Visible (Genesis Visible)

FanControl

Audible

G_AudibleVisible (Genesis Audible

Visible)

CommonAlarmOutput

G_CommonAlarmOutput (Genesis
Common Alarm Output)

CommonMonitorOutput

CommonSupervisoryOutput

SupervisedOutput

G_CommonSupervisoryOutput
(Genesis Common Supervisory
Output)

Visible

ControlledAuxOutput (Controlled
Auxiliary Output)

G_CommonMonitorOutput
(Genesis Common Monitor Output)

City_Tie

Note: PS10-4B NAC/AUX circuits configured as auxiliary power outputs must be

turned on using a startup rule. A rule is needed to turn them off during an AC
power failure if, for example, they are powering non-life safety devices and you
want to preserve battery life.

P/N 270729 ISS 02MAY12

39 / 45

A.3.3 Power supply diagnostics

The Power Supply Diagnostics dialog box (Tools > Power Supply > Diagnostics)
displays information in the following fields:

Total Current

Maximum Current in Alarm

Each of the following fields shows the actual, minimum, maximum, previous
1-hour average, and 24-hour average over the time that the power supply
diagnostics has been connected:

NAC/AUX Current

Input AC Voltage

Battery Current

The Battery tab displays the actual, minimum, and maximum voltages of the
standby batteries.
A.3.4 SFS1-CPU support
The SFS1-CPU (C-CPU in the SDU) supports the following network cards:

3X-NET8: Gives an EST3X panel the ability to network via copper wire with a
maximum of eight EST3X nodes (no EST3 nodes). The card supports Class
A and Class B wiring. The 3X-NET8 adapter card provides two independent
RS-485 circuits; one for network data communications and one for digital
audio communications.

3X-NET: Gives an EST3X panel the ability to network via copper wire with
EST3 Systems, up to a maximum of 64 nodes. The card supports Class B
and Class A wiring. The 3X-NET adapter card provides two independent
RS-485 circuits; one for network data communications and one for digital
audio communications.

3X-FIB8: Gives an EST3X panel the ability to network via fiber optic cable
with a maximum of eight EST3X nodes only (no EST3 nodes). The card
supports Class A or Class B network and Class A or Class B audio data, and
provides single or multiple-mode network and digital audio fiber optic
connections.

3-FIBMB2: Gives an EST3X panel the ability to network via fiber optic cable
with EST3 systems, up to a maximum of 64 nodes. The card supports Class
A or Class B network and Class A or Class B audio data, and provides single
or multiple-mode network and digital audio fiber optic connections.
Note: 3-SDU V5.10 replaces the 3-FIBMB2 network card with the 3X-FIB
network card. See 3.4 Support of the new 3X-FIB network fiber optic card on
page 4 for more details.

P/N 270729 ISS 02MAY12

40 / 45

A.3.5 R-Series Annunciator support

Each EST3X panel supports the connection of up to 30 R-Series remote
annunciators (RLCD, RLCD-C, or RLED-C), up to 30 GCI graphic annunciator
cards, or a combination of both. Each R-Series remote annunciator can have two
RLED24 expanders that contain an additional 48 LED indicators per expander.
Each GCI card can have two GCIX expanders for an additional 48 LED indicators
and 24 input switches per GCI.
Note: R-Series annunciator firmware version 2.0 or later is required. You can
verify the firmware version on RLCD(-C) annunciators by pressing the Lamp Test
button. On RLED-C annunciators and GCI card, the firmware version is marked
on the product carton.
Remote annunciators are managed by a modified 3-SAC built into the EST3X
panel. This card always has a slot position of 7 and a card address of 4. To fit
30 annunciators and all of their LEDs, switches, and pseudo points onto a single
card, the system assigns device addresses in ranges. Each annunciator is
assigned a range of 300 addresses.
A.3.6 Enhanced internal Signature loop controller
The EST3X CPU Main board includes a single Signature loop controller (card
address 3) that you can expand to two loops by installing an additional 3-SDC1
card.
The CPU Main Board loop controller:

Generates new pseudo point events to signal when there are more than the
allowed number of detectors or modules installed on a Signature loop. The
two events are Too_Many_Devices_DataCard1_PP_03 and
Too_Many_Devices_DataCard2_PP_03.

Generates new pseudo point events to signal when the expected map does
not match the actual map. The two events are
Map_Mismatch_DataCard1_PP_03 and
Map_Mismatch_DataCard2_01_03.

Does not support security devices (i.e., SIGA-SEC2 and SIGA-MD).

Does not support stand-alone alarm operation. Outputs connected to the

CPU main board loop controller that are configured for stand-alone alarm do
not automatically activate if an alarm occurs while the CPU and loop
controller are not communicating.

Supports SIGA2 devices as per version 4.0 of the 3-SxDC, except you cannot
program PHS detectors with the Photo is AlarmSmoke | Heat is AlarmHeat
operation, or the Photo is Supervisory | Heat is Supervisory operation.

P/N 270729 ISS 02MAY12

41 / 45

A.3.7 Advanced diagnostics for the CPU main board loop controller
We have expanded the Trouble Tables tab on the Signature Series Status /
Diagnostics dialog box to show a % Dirty Analysis graph, and to allow you to
enter comments on the selected device. For this graph, if you attempt to connect
to the panel and download information while devices are still initializing, the
graph will show invalid data. Always wait until the devices have finished
initializing before retrieving data from the panel (i.e., the Sensor Initialization LED
and the Device Supervision LED on the Current Status tab are both off.)
In addition, we have added the following columns to the table on this tab. These
columns apply to the EST3X CPU internal loop controllers only.

1 Hr Retry Counter: The number of unsuccessful communication queries

with the device within a one hour period.

24 Hr Retry Counter: The number of unsuccessful communication queries

with the device within a 24 hour period.

Base Type Fault: Indicates that the device base type in the loop controller's
expected data table does not match the device base type in the actual data
table.

Riser Fault: Indicates a fault on the input riser of the module (i.e., 24 V riser
of a UM configured as a two-wire smoke).

Sensitivity Fault: Indicates that the device sensitivity has changed unexpectedly.

Device Init Fault: Indicates that the device failed the initialization process at
startup.

Configuration Fault: Indicates that the device has a configuration that is not
valid. Go into the configuration tool and review and update the devices
configuration.

Invalid Address: Indicates that the device has an address that is beyond the
allowable limit.

IL Feedback: Interlock feedback has timed out on a device (Chinese

marketplace feature).

A.3.8 Automatic Contact ID

Depending on the configuration of your project, the SDU can automatically
generate Contact ID strings to send to a central monitoring station (CMS).
To use this feature your project must contain:

Eight or less EST3X (CAB6) panels. The Network Type option on the Project
Parameters Network tab must be set to 3X Only.

A 3-MODCOM(P) with at least one account configured for Contact ID.

P/N 270729 ISS 02MAY12

42 / 45

When you add an account and attach it to a receiver configured for Contact ID,
the SDU displays the Auto Generate Events check box in the Account
Properties dialog box. This check box is checked by default. If you do not want
the SDU to automatically generate your Contact ID strings for this account, then
clear this check box.
If your project meets the criteria above, after you successfully run a rules compile
the SDU generates the necessary Contact ID strings for the project. The SDU
inserts these strings before all of the written rules. This assures that the Contact
ID strings are sent to the CMS before any delays in the rules are encountered.
It is possible to override an automatically generated Contact ID string by writing a
rule. For example, suppose there are four NACs on the EST3X power supply,
and the SDU automatically generates a unique string for each. The SDU sends a
137312001 string for the trouble activation of the first NAC and 137312002 for
trouble activation of the second NAC. If you want to send the same CID string for
all four NACs then you could use the following rule:
[change message rule]
Trouble PS/NAC_01_02_* : +send account1 137312000;
We included only the activation portion of the send command because if you
check Auto Generate events and your rule includes only a send activation, the
SDU automatically generates the restore using the same string (337312000 in
the example).
Run the CMS Messaging Report for a complete list of the Contact ID strings sent
for each device. You can now export this report into an Excel spreadsheet file.
Once you run the report, click the Save Report button and select Microsoft Excel
Worksheet (*.xls) in the Save as type dropdown list.
A.3.9 TCP/IP communications
The ETH1 Ethernet card on CAB6 cabinet models lets you use Internet Protocol
connectivity for remote programming and diagnostics.
We have added the Cabinet Configuration IP Configuration tab to let you to
configure IP connectivity.
The following fields were added in the Communications Functions and the Select
a Signature Loop for Mapping dialog boxes to support TCP/IP communications:

Connection Type

IP Address

Port Address

Cabinet

P/N 270729 ISS 02MAY12

43 / 45

A.3.10 Remote write unlock

To download application, database, and boot loader code using an IP
connection, you must first unlock the panel. You can do this by activating a write
unlock for the panel.
To activate a remote write unlock via the panels menu:
1. Go to the Activate menu on the panel.
2. Select Remote Write Unlock.
3. Select the panel (or select ALL).
4. Start the download.
The panel automatically times out the unlock if there is no download activity for
15 minutes.
To restore a remote write unlock via the panels menu:
1. Go to the Restore menu on the panel.
2. Select Remote Write Unlock.
3. Select the panel (or select ALL).
You can also activate and restore an unlock using correlations (see the SDU
Help for information on the ActivateRemoteWriteUnlock and
RestoreRemoteWriteUnlock commands).
A.3.11 Remote read lock
The panel allows you to lock out remote reads (i.e., diagnostics information) via
the IP connection. This is designed to prevent unauthorized access to the panel.
To activate a remote read lock via the panels menu:
1. Go to the Activate menu on the panel.
2. Select Remote Read lock.
3. Select the panel (or select ALL).
You can restore the lock via the panel.
To restore a remote read unlock via the panels menu:
1. Go to the Restore menu on the panel.
2. Select Remote Read lock.
3. Select the panel (or select ALL).

P/N 270729 ISS 02MAY12

44 / 45

Programmers can also activate and restore the lock using correlations (see the
SDU Help for information on the ActivateRemoteReadLock and
RestoreRemoteReadLock commands).
A.3.12 New commands
Version 5.02 adds the following new commands for EST3X cabinets only:

ActivateRemoteReadLock: Disables IP read communications between the

SDU and the panel.

ActivateRemoteWriteUnlock: Allows write capability using IP

communications between the SDU and the panel.

RestoreRemoteReadLock: Allows IP read communications between the CU

and the panel.

RestoreRemoteWriteUnlock: Disables the write capability using IP

communications between the SDU and the panel.

NAC20: Sets the audible tone pattern on a specified NAC to the 20 pattern:
audio sounds at 20 beats per minute (1-1/2 seconds on, 1-1/2 seconds off).

NAC120: Sets the audible tone pattern on a specified NAC to the 120 pattern:
audio sounds at 120 beats per minute (1/4 second on, 1/4 second off).

NACTemporal: Sets the audible tone pattern on a specified NAC to the

temporal pattern: audio sounds in a 3-3-3 pattern.

A.3.13 Items incompatible with EST3X panels

The new EST3X panels are not designed to support security and access control.
You cannot add 3-SAC, CRC, CRCXM, or KPDISP hardware to an EST3X panel.
You cannot add SIGA-SEC2 and SIGA-MD modules to loop controllers on
EST3X panels.
However, if your project has a mix of EST3X and EST3 panels, the EST3X
panels can support security and access control points indirectly in that they are
displayed on, and can be controlled from, the EST3X panels.
Note: Do not use partitions on EST3X panels.
A.4 SDU Help
For all features, the 3-SDU 5.02 provides context sensitive Help topics. Pressing
the F1 key displays a Help topic that corresponds to the location and task being
performed.
The 3-SDU 5.02 Help requires that you have Internet Explorer 6 or later installed.
The compiled HTML Help file is not compatible with other Web browsers.

P/N 270729 ISS 02MAY12

45 / 45