EST3, Version 3.0 Software Release Notes
1 Introduction
These release notes contain a summary of the version 3.0 release and additional information that was not available in time for inclusion in the system manuals at the time of printing.
Note: Please read these notes in their entirety before attempting to install your new version of the 3SDU. Section 8 provides detailed instructions on how to upgrade systems using the network download feature.
Note: The 3-SDU contains many selections, controls, reports, help, and other features intended for use with integrated Fire/Security/Access Control systems releasing in the next months. These items will be explained in upcoming announcements, release notes, and other materials.
2 New Software Versions
Table 1 - Listing of New EST3 Software/MicroCode Versions
2.1 Description Version
3-ASU MicroCode 3.0
3-BPS MicroCode 3.0
3-CPU(1) MicroCode 3.0
3-FTCU MicroCode 3.0
3-IDC8/4 MicroCode 3.0
3-LDSM MicroCode 3.0
3-MODCOM MicroCode 3.0
3-OPS MicroCode 3.0
3-PPS MicroCode 3.0
3-SDU/K New Installation Kit 3.0
3-SDU Update Kit 3.0
3-SSDC/SDDC MicroCode 3.0
3-ZAxx MicroCode 3.0
3 Overview - What's New in Version 3.0
3-MODCOM Modem Communicator Module (Dialer) support
FireWorks 2000 Support
Programmable Sounder/Relay Base Support
Supervisory Duct Detector Support
3-ZAxx amplifiers provide backup 20 PPM march time on alert channel
3-NSHM1/2 Network Short Haul Modem support (Refer to marketing release announcing availability)
Full configuration support for M501 modules
Command Lists
Mideast marketplaces added
Rail baud rate support has been increased from 9600 to 38400 baud.
4 Software Revisions and Compatibility
To stay up to date, everyone should upgrade to 3-SDU version 3.0. There is no need to upgrade 3CPU(1) Application Code or Bootstrap to version 3.0 unless you wish to take advantages of the new features offered in version 3.0. All previously supported versions inV2.x of software are supported by V3.0.
Table 3 - EST3 3-SDU Version 3.0 Software Compatibility /Local Rail
Module / Oldest Compatible Version / Shipping
Version / Media / Part
Number /
3-ASU / 1.1 / 3.0 / CD / 3-SDU
3-SSDC / 1.0 / 3.0 / CD / 3-SDU
3-SDDC / 2.0 / 3.0 / CD / 3-SDU
3-AADC / 1.0 / 3.0 / CD / 3-SDU
3-LDSM / 1.0 / 3.0 / Chip / 190153
3-FTCU / 1.0 / 1.2 / Chip / 190156
3-FTCU / 1.4 / 3.0 / Chip / 190254
3-MODCOM(P) / 3.0 / 3.0 / CD / 3-SDU
3-ZA15 / 1.1
1.3 / N/A
N/A / Chip
PAL Chip / 190151
190191
3-ZA20B / 1.4
1.4 / 3.0
1.4 / Chip
PAL Chip / 190252
190191
3-ZA30 / 1.1
1.3 / N/A
N/A / Chip
PAL Chip / 190151
190191
3-ZA40A / 1.4
1.4 / 3.0
1.4 / Chip
PAL Chip / 190252
190191
3-ZA40B / 1.4
1.4 / 3.0
1.4 / Chip
PAL Chip / 190252
190191
3-ZA90 / 1.4
1.4 / 3.0
1.4 / Chip
PAL Chip / 190252
190191
3-PPS / 1.0 / 3.0 / Chip / 190157
3-BPS / 1.0 / 3.0 / Chip / 190157
3-IDC8/4 / 1.1 / 3.0 / Chip / 190159
3-OPS / 1.0 / 3.0 / Chip / 190158
3-CPU(1) / 1.33 / 3.0 / CD / 3-SDU
Note 1: 3-CPU(1) V3.0 MicroCode can not reside on the same network as earlier 3-CPU(1) MicroCode; to use V3.0, all panels must be upgraded to V3.0. Networks with 3-CPU MicroCode version 1.4 or later can be upgraded with 3-SDU using the network download function. (See Section 8 for instructions.)
Note 2: Do NOT import version 1.0, 1.1, or 1.2 of the 3-CPU(1) MicroCode into version 3.0 of the 3SDU. 3-SDU version 3.0 is shipped with 3-CPU(1) Versions 1.33, 1.41, 1.52, 2.0 and version 3.0. Earlier versions of MicroCode cannot be imported into 3-SDU 3.0.
Note 3: The 3-CPU1 is 100% backward compatible with, and can be installed on the same network as the 3-CPU. The 3-CPU requires at least V1.33 MicroCode.
Note 4: 3-FTCU firmware comes in two non-interchangeable forms. Part 190254 cannot be used to update Part 190156, and visa versa.
4.1 3-SDU Database Compatibility
3-SDU V3.0 can be used to generate databases for the following LRMs:
LRM / 3-SDU supported MicroCode Versions3-CPU / V1.33, V1.41, V1.52, V2.0, V3.0
3-SSDC/SDDC / V1.0, V1.4, V1.5, V2.0, V3.0
3-ASU / V1.0, V1.1, V1.4, V3.0
3-AADC / V1.4, V3.0
3-MODCOM / V3.0
4.2 Latest Compatible Version
The following table identifies that most recent version of LRM MicroCode that is compatible with a 3CPU MicroCode version. It is recommended that the latest compatible LRM of MicroCode be utilized.
/ 3-CPU MicroCode Versions /LRM / V1.33 / V1.41 / V1.52 / V2.0 / V3.0 /
3-SSDC/SDDC / V1.5 / V1.5 / V1.5 / V3.0 / V3.0
3-ASU / V1.4 / V1.4 / V1.4 / V3.0 / V3.0
3-AADC / --- / V1.4 / V1.4 / V3.0 / V3.0
3-MODCOM / --- / --- / --- / --- / V3.0
5 New in 3-SDU Version 3.0
5.1 General Improvements
5.1.1 Added additional OEM support
5.1.2 CUSTOMIZE CHANGE FONT now permits a user to select a font such as Arial, then select a ‘Script’ to decide which letters are used. This allows the viewing of text messages in the local language.
5.1.3 New Screens/Functions
5.1.3.1 Command List Configuration
Command Lists provide a method of creating a rule that can be executed from other rules, or across gateway connections.
5.1.3.2The size and position of most screens is now retained upon exiting, and restored when reopened.
The Customize screen may be used to reset all screen sizes and positions to the default values.
5.1.4 Marketplaces
The following Marketplaces are now supported by the 3-SDU
UL Local
US Proprietary
Canadian Local
Canadian Proprietary
European
Asian Local
Asian Proprietary
Mideast Local (new)
Mideast Proprietary (new)
5.2 Project Functions
5.2.1 Export and Change Password menu items are disabled when there are no projects.
5.2.2 During open and save operations the name of the files are now displayed.
5.2.3 The Save As function message now indicates the new version number.
5.3 Cabinet Configuration
5.3.1 LRM Support
5.3.1.1 Added 3-MODCOM(P) and configuration screens.
Used when configuring MODCOM(P)s.
5.3.2 Rail Baud Rate Selection Improved
5.3.2.1 The cabinet Rail Baud Rate selection may be by individual cabinet or all cabinets at once.
Available selections are 9600, 19200 and 38.4K. NOTE: To use baud rates over 9600, select the ‘All LRM firmware (MicroCode) is V3.0 or later’ checkbox to verify that the project’s LRM Firmware can process the high rail baud rate.
5.3.3 New ECP (Gateway) Warning Added
If an ECP (Gateway) port is configured, a warning message indicating that inserting or deleting a cabinet alters the addressing of objects that may have already been exported.
5.3.4 Class A ASU Supervision
The SDU permits selecting ‘Class A Supervision’ when there is an ASU in the cabinet. By default, supervision is Class B.
5.4 Object Configuration
5.4.1 Logic Group Processing updated
5.4.1.1 User verification added when removing and clearing devices from logic groups.
5.4.1.2 The Save function is now enabled when a guard patrol group is deleted.
5.4.1.3 Logic Group label on the top left of the screen has been revised to show the group index.
5.4.2 Logics now have a new Pick Devices button. This button selects the member devices on the Object tab. For example, this allows all of the devices in a Zone group to be quickly selected and then added to a new Service Group. Once the objects have been selected, do not use any filters in the Object tab, as this will reset previous selections. There is also a new “Additive” checkbox that allows selections to be accumulative.
5.5 Signature Configuration/Status/Diagnostics/Mapping
5.5.1 Standalone alarm selection is now available for the SIGA-IO and SIGA-MIO.
NOTE: Do not use the device type”NSCOMMONTROUBLEOUTPUT” for SIGA-IO and SIGA-MIO devices. Once the timer has been activated, the trouble has been activated, the trouble can only be reset with a panel restart.
5.5.2 The SIGA-CC1S and SIGA-MCC1S now support personality 5 (signal power or audio riser selection).
5.5.3 Relay/Sounder Base Group support has been added.
This feature allows individual and grouped control of Signature sensor relay and sounder bases from rules. This provides much greater control and flexibility of these outputs.
5.5.3.1The system now displays “Determining Status” whenever a system detects a processing new starts condition.
5.5.3.2 Signature trouble bits with no predefined messages now display byte and bit information.
5.5.3.3 The Accept/Commit process has been improved to eliminate personality problems with the second address.
5.5.3.4 Refer to the SIGA-REL manual for programming instructions. The SIGA-REL must be programmed as instructed in the manual for V2.0 of the EST3.
5.6 3-AADC Configuration/Status/Diagnostics
5.6.1 Device Support
5.6.1.1 7251A (Pinnacle) detector
Added support in Canadian marketplaces.
5.6.1.2 5251F Fixed Temperature Sensor
Added support for the 5251F fixed temperature sensor. Not enabled in the Canadian marketplaces.
5.6.1.3 1251F Ionization Smoke Sensor
Added support for the 1251F ionization smoke sensor. Not enabled in the Canadian marketplaces.
5.6.1.4 2251F Photoelectric Smoke Sensor
Added support for the 2251F photoelectric smoke sensor. Not enabled in the Canadian marketplaces.
5.6.2 New Features
5.6.2.1 Pre-alarm selection added for sensors.
Prealarm sensitivity values are directed to the sensitivity level selected for the sensor.
Prealarm selections are mutually exclusive to alarm verification.
5.6.2.2 A Maintenance Alert column has been added to the diagnostic Trouble Tables for Canadian Marketplaces to support Pinnacle devices.
5.7 Rules Compile
5.7.1 Rules Operation
5.7.1.1 Added “+” and “-“ command qualifiers to output commands
These qualifiers define whether the command is executed on the activation (+) or upon the restoration (-) of an event. This feature provides greater programming flexibility by allowing the creation of non-symmetrical responses i.e. Controls can restore in a different order than activated.
5.7.1.2 Added the “h”-variable.
The h-variable is similar to the n-variable, but uses hexadecimal values. This feature is used when programming MODCOM DACT/DACR protocols that use hexadecimal notation.
5.7.1.3 Added a “width qualifier” for the n-variable and h-variable.
On the left (input) side of a rule the format is <n:1-10:w> where the w is a digit representing the width (number of digits) to assign to the variable. EXAMPLE: If the value of w is set at 4, then the n-variable value will have leading zeros attached to keep the width at 4 digits. On the right (output) side of the rule the format is <n:w> for the same purpose.
5.7.1.4 Added the SysTime Command
The SysTime command is used to set the System clock. The format is: SysTime HH:MM:SS. The SysTime command can be used with a Time Control it can be used to provide automatic Daylight Savings Time programming.
5.7.1.5 Added the SEND Output Command
The SEND output command is used to send DACT/DACR messages to a central station account. The SEND command supports various substitutions depending on the receiver protocol.
5.7.1.6 Added the ability to define responses for Command List activation via the Activation input event.
5.7.1.7 Added the ability to execute responses associated with a Command List via the Activate and Restore commands.
5.7.2 Compiler Operation
5.7.2.1 Added the option to perform a 'Convert all databases' or ‘Convert 3-CPU databases’ after rules compile.
5.7.2.2 After Rules Compile, the SDU will identify any Guard Patrol group, Emergency, Alarm, Supervisory, or Trouble device activation that doesn't activate a CMS Account, if a CMS Account exists.
5.7.2.3 The SDU will warn the user when trying to disable a NSCOMMONALARMOUTPUT device.
5.7.2.4 Canadian Marketplaces Operation
The SDU will prevent the user from performing 3-CPU dB Conversion if there are Alarm devices that do not activate a signaling output. This condition is indicated as an Error instead of as the Warning in other marketplaces.
5.7.3 Support for the following new Input Events are added:
Activation
CMSFirstTrouble
Disabled
5.7.4 Support for the following new Output Commands/Device Types are added:
SysTime
Enable/Disable/Activate/Restore for CommandList
Enable/Disable/Send for McomAccount
On/Off for NSAudibleOutput
On/Off for NSVisibleOutput
5.8 Reports
5.8.1 General
5.8.1.1 Reports are now listed in alphabetical order in the menu for quicker location
5.8.1.2 The SDU now checks for the existence of a printer before attempting to run any report.
If a printer isn't configured on the computer, no attempt will be made to generate the report. All that is required to generate a report is an installed printer driver. A printer does NOT need to be connected to the computer.
5.8.1.3 Various report formats have been revised to improve readability, use and description.
5.8.2 New SDU Reports
5.8.2.1 Modcom Accounts
5.8.2.2 Modcom Receivers Where Used
5.8.2.3 Modcom Central Monitoring Station Messaging Report
This printed reports design is ideal for CMS use to identify system points
5.8.3 Revised SDU Reports
5.8.3.1 The 3-AADC report now displays sensor prealarm values.
5.8.3.2 Added a criteria selection screen to the Logic Group Membership report
This feature permits selection of which types of Logic Groups will be included in the report.
5.8.3.3 Added a Group Number to the Logic Group Membership report.
5.8.3.4 Added Command Lists, and Time Controls to the Logic Group Membership report.
5.8.3.5 The Signature Barcode Worksheet report
Now displays both Detectors and Modules. Only Modules were being displayed on an earlier version.
5.8.3.6 Objects Report
The annunciator selection provides data on the annunciator and no longer reports the LRM beneath it.
5.9 DB Conversion
5.9.1 DB Conversion screens redesigned and combined into a single screen.
5.9.2 Added a 'Create All Database' selection to the Tools->DB Conversion menu. This feature performs the DB Conversion process on all LRMs in the project.
5.9.3 Added the ability to DB Convert all databases in the project, all databases for a particular LRM type or select individual databases.
5.9.4 Added Hebrew language support
5.10 Audio Tools
Audio Tools now allows imports from a CD-ROM or read only file.
5.11 Communications
5.11.1 Operations
5.11.1.1 Single Step downloads can now be canceled.
5.11.1.2 Autobaud operation has been enhanced to better identify LRM communications.
5.11.1.3 A status bar has been added to indicate the progress of preparing data for download.