Embed Size (px)
Citation preview
EST3, Version 3.0 Software Release Notes
1 IntroductionThese 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 3-SDU. 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 VersionsTable 1 - Listing of New EST3 Software/MicroCode Versions
2.1 Description Version
3-ASU MicroCode 3.03-BPS MicroCode 3.03-CPU(1) MicroCode 3.03-FTCU MicroCode 3.03-IDC8/4 MicroCode 3.03-LDSM MicroCode 3.03-MODCOM MicroCode 3.03-OPS MicroCode 3.03-PPS MicroCode 3.03-SDU/K New Installation Kit 3.03-SDU Update Kit 3.03-SSDC/SDDC MicroCode 3.03-ZAxx MicroCode 3.0
3 Overview - What's New in Version 3.03-MODCOM Modem Communicator Module (Dialer) supportFireWorks 2000 SupportProgrammable Sounder/Relay Base SupportSupervisory Duct Detector Support3-ZAxx amplifiers provide backup 20 PPM march time on alert channel3-NSHM1/2 Network Short Haul Modem support (Refer to marketing release announcing availability)Full configuration support for M501 modulesCommand ListsMideast marketplaces added
Rail baud rate support has been increased from 9600 to 38400 baud.
4 Software Revisions and CompatibilityTo stay up to date, everyone should upgrade to 3-SDU version 3.0. There is no need to upgrade 3-CPU(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 CompatibilityLocal RailModule
Oldest Compatible Version
ShippingVersion
Media PartNumber
3-ASU 1.1 3.0 CD 3-SDU3-SSDC 1.0 3.0 CD 3-SDU3-SDDC 2.0 3.0 CD 3-SDU3-AADC 1.0 3.0 CD 3-SDU3-LDSM 1.0 3.0 Chip 1901533-FTCU 1.0 1.2 Chip 1901563-FTCU 1.4 3.0 Chip 1902543-MODCOM(P) 3.0 3.0 CD 3-SDU3-ZA15 1.1
1.3N/AN/A
ChipPAL Chip
190151190191
3-ZA20B 1.41.4
3.01.4
ChipPAL Chip
190252190191
3-ZA30 1.11.3
N/AN/A
ChipPAL Chip
190151190191
3-ZA40A 1.41.4
3.01.4
ChipPAL Chip
190252190191
3-ZA40B 1.41.4
3.01.4
ChipPAL Chip
190252190191
3-ZA90 1.41.4
3.01.4
ChipPAL Chip
190252190191
3-PPS 1.0 3.0 Chip 1901573-BPS 1.0 3.0 Chip 1901573-IDC8/4 1.1 3.0 Chip 1901593-OPS 1.0 3.0 Chip 1901583-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 3-SDU. 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 Compatibility3-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.03-SSDC/SDDC V1.0, V1.4, V1.5, V2.0, V3.03-ASU V1.0, V1.1, V1.4, V3.03-AADC V1.4, V3.03-MODCOM V3.0
4.2 Latest Compatible VersionThe following table identifies that most recent version of LRM MicroCode that is compatible with a 3-CPU MicroCode version. It is recommended that the latest compatible LRM of MicroCode be utilized.
3-CPU MicroCode VersionsLRM V1.33 V1.41 V1.52 V2.0 V3.03-SSDC/SDDC V1.5 V1.5 V1.5 V3.0 V3.03-ASU V1.4 V1.4 V1.4 V3.0 V3.03-AADC --- V1.4 V1.4 V3.0 V3.03-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 ConfigurationCommand 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 MarketplacesThe following Marketplaces are now supported by the 3-SDU
UL LocalUS ProprietaryCanadian LocalCanadian ProprietaryEuropeanAsian LocalAsian ProprietaryMideast 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 AddedIf 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 SupervisionThe 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) detectorAdded support in Canadian marketplaces.
5.6.1.2 5251F Fixed Temperature SensorAdded support for the 5251F fixed temperature sensor. Not enabled in the Canadian marketplaces.
5.6.1.3 1251F Ionization Smoke SensorAdded support for the 1251F ionization smoke sensor. Not enabled in the Canadian marketplaces.
5.6.1.4 2251F Photoelectric Smoke SensorAdded 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 commandsThese 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 CommandThe 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 CommandThe 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 OperationThe 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:ActivationCMSFirstTroubleDisabled
5.7.4 Support for the following new Output Commands/Device Types are added:SysTimeEnable/Disable/Activate/Restore for CommandListEnable/Disable/Send for McomAccountOn/Off for NSAudibleOutputOn/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 ReportThis 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 reportThis 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 reportNow displays both Detectors and Modules. Only Modules were being displayed on an earlier version.
5.8.3.6 Objects ReportThe 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 ToolsAudio 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.
5.11.1.4 Revised operation when changing the download baud rate to a 3-CPU.Download rates can now be changed without a waiting period, as long as the previous communications session completed without errors.
5.11.2 The Communications Function Screen has been updated
5.11.2.1 Added LRM Type Display Filter checkbox for 3-MODCOM(P).
5.11.3 LRM Communications (previously XCP Communications)
5.11.3.1 Redesigned the screen to provide additional information. The screen now displays the Device Address for the item being downloaded. The screen now displays the name and location of the file being downloaded. The screen now displays the counts for the number of modules selected for download, the number of
modules that have finished and the number of modules that have experienced errors.
The screen now displays communications details and provides a communication history that can be saved to a file by right clicking.
5.12 3-MODCOM SupportThe following new products are supported in V3.0
5.12.1 3-MODCOM(P) Modem Communicator Module (Digital Alarm Communicator Transmitter)Supervised Dual line Digital Alarm Communicator Transmitter with integral modem featuring:
Maximum of 10 3-MODCOM(P)s per network, 80 receivers & 255 accounts per 3-MODCOM(P). Formats include: SIA P2 (3/1), SIA P3 (4/2), SIA DCS, Contact ID, TAP (paging) for use with fire. Fully programmable standalone operation in the event of 3-CPU1 failure. TAP protocol receiver must be 300 baud, 7 bits, even parity (Bell 103 modem).
5.12.2 Signature Improvements
5.12.2.1 Relay and sounder bases are now programmable individually and in groups. Groups provide a high performance method of activating/restoring many bases simultaneously. Up to 32 groups are supported per Signature loop.
5.12.2.2 Improvements have been made to device communications under high-capacitance loop conditions.
5.13 Programming Tools
5.13.1 New Commands and Capabilities
5.13.1.1The use of duct detectors as supervisory devices is now supported.
5.13.1.2 Command ListsA Command List is a list of instructions that can be executed by a rule. Each network can support up to 2000 command lists. Command List controls include Activate, Restore, Disable, and Enable. Command lists allow responses (including delays) to finish, even when activated by a non-latching event.
5.13.1.3Time Controls Time Controls now support “Not Holiday” as well as the pre-existing holiday and “don’t care.”
5.13.1.4 Disabled Rule ResponseRules can now be run when a point is disabled, permitting an LED or other output to be set. This command may be used to send point disabled messages to a Central Monitoring Station.
6 V3.0 MicroCode Updates
6.1 GeneralAll Local Rail Modules and the 3-ASU(/FT) now support 38.4Kbaud internal communications. This will improve download time as well as system response.
6.2 New in 3-CPU(1) Version 3.0 MicroCode
6.2.1 New/Improved System Operation
6.2.1.1 Pressing the “Details” switch on an event from a physical device now displays the physical device states.
This feature may be used to determine the state of a disabled/bypassed device, or the current state of a security device prior to partition reset.
6.2.1.2 The 3-LCD message queue selection buttons and the scroll up/down button will now fast scroll through events (5 per second) when the buttons are held down longer than 2 seconds.
This feature reduces wear & tear on the 3-LCD, and your finger.
6.2.2 New 3-CPU Reports
6.2.2.1 Modcom ComplianceThis report indicates whether the 3-MODCOM configuration complies with NFPA 72 Remote Station and Central Station requirements.
6.2.3 Printer logs and history reports now identify the source of the command.
6.2.4 Printer protocol has been updated
6.2.4.1 CAUTION: V3.0 printer protocol is upward compatible with previous versions of the printer protocol. Do not use V3.0 with products other than EST printers, pager interfaces or 3-VDUT V2.0 unless you first verify compatibility of the third party product with the new protocol.
6.2.5 External Command Port (ECP) Protocol has been updated
6.2.5.1 CAUTION: V3.0 External Command Port (ECP) protocol is upward compatible with previous versions of the ECP protocol. Do not use V3.0 with products other than EST OS/2 Fireworks or FireWorks 2000, unless you first verify compatibility of the third party product with the new protocol.
6.3 New 3-ASU MicroCode
6.3.1 Added support for 19200 and 38400 rail baud rates.
6.3.2 Now provides ALL CALL MINUS pseudo point separate from ALL CALL.
6.3.3 Now provides download mode indication pseudo point.
6.4 New 3-FTCU Firmware
6.4.1 Added support for 19200 and 38400 rail baud rates.
6.4.2 Off-Hook timer supports timeouts greater than 2 minutes.
6.5 New 3-IDC8/4 Firmware
6.5.1 Added support for 19200 and 38400 rail baud rates.
6.6 New 3-LDSM Firmware
6.6.1 Added support for 19200 and 38400 rail baud rates.
6.7 New 3-OPS Firmware
6.7.1 Added support for 19200 and 38400 rail baud rates.
6.8 New 3-PPS/PSB Firmware
6.8.1 Added support for 19200 and 38400 rail baud rates.
6.8.2 Battery charger function modified to charge during Alarm or Drill condition if Alarm Silence is activated. Previous versions disabled battery charging during Alarm or Drill.
6.8.3 Battery charger function added for Power Supply Booster.
6.8.4 Correctly provides hystereses for Battery Troubles.
6.9 New 3-ZAxx Amplifier Firmware
6.9.1 Added support for 19200 and 38400 rail baud rates.
6.9.2 Improved open, overcurrent and DC fault supervision on amplifier circuits.
6.9.3 3-ZA20/40/90 amplifiers now offer improved standalone capabilities by supporting provide a 20 PPM march time alert signal in addition to the 3-3-3 evacuation signal as backup tones when the amplifier does not sense the digital audio network signal.
6.10 Text Messages
6.10.1 V2.0, V2.1, and V3.0, do NOT support extended messages. To continue to use 4K extended messages, you must use software V1.5 or earlier. To take advantages of the features provided in V3.0 and future versions, all 4K extended messages must be manually converted to Instructional Text Groups.
6.11 Installation NotesCaution: If you are installing the 3-SDU on a PC connected to a Local Area Network (LAN) using Borland products, call the Technical Services Department for additional installation information.
6.12 3-SDU Upgrade NotesIt is recommended that you do NOT manually delete a previous 3-SDU Installation. The install routine should be allowed to update the current version.
6.12.1 Run Time IssuesThe 3-SDU requires that a printer driver be installed for your Windows session. You do not need a printer physically connected to your computer, but a printer driver is required. If you try to start the 3-SDU and you get an error stating, "Cannot start application," this may be the cause.The 3-SDU is best run on a computer using 800x600 minimum resolution and small fonts. If any other settings are used, some of the 3-SDU screens will be resized.Only one version of the 3-SDU can be installed on your PC at any one time.
7 Running the 3-SDU
7.1 OverviewRemember to install your security key in your computer's parallel (LPT1) port. Any other devices that share this port such as printers and Zip disks must be plugged into the key.
Save your project periodically as you are working on it and to export it to disk on a regular basis to protect your work.
7.2 3-SDU Issues
7.2.1 ECP Gateway port selection:- Refer to external equipment manufacturer’s documentation for compatible ECP gateway
selection.- If ECP port is configured on the 3-CPU(1) then 38.4K Baud is not supported for download
via the Auxiliary Ports to the 3-CPU(1). However 19.2K Baud is supported.- If ECP gateway port is not configured on the 3-CPU then 19.2K Baud is not supported for
download via the Auxiliary Ports to the 3-CPU(1). (38.4K Baud is supported) The RJ-45 connector always supports 19.2K and 38.4 K baud for downloading.
7.2.2 Change in 3-SDU Function- Upgrading from V1.5 to V3.0 now recognizes the “M” series plug-in Signature modules. Simply accept the devices; no reprogramming is necessary.
8 MicroCode Version 3.0 Panel Upgrade Instructions
8.1 CPU Version 3.0The new application and boot code must both be downloaded to ALL panels in the system. Version 3.0 is not compatible with earlier versions of CPU MicroCode. Do not mix different versions of CPU MicroCode on the same network. By carefully following the steps below, an existing system can be upgraded.
Upgrade Instructions, V1.33 or lower (No network download option) to V3.0
Project version numbers are imbedded in each project file. Because the “Save As” function creates a new version number that is different than the imbedded version, you must use the following procedure to install V3.0. Please follow these steps in order to upgrade the hardware and software in your system
With 3-SDU version 3.0 installed:1. Save your project as a new version, using the "Save As" function in the file menu.2. Do a Signature Conversion, then Recompile your project, run db-conversion, and then “Save”
the project a second time.3. Remove nodes from the network.4. Select SINGLE STEP download, select 3-CPU1 database, 3-CPU1 application code, and
3-CPU1 bootstrap options. (Do NOT include the 3-SSDC/3-SDDC database, code or bootstrap). 5. Connect the laptop to the node CPU, and start the download.6. Connect the laptop directly to the 3-SSDC/3-SDDC and 3-ASU to update application and
bootstrap code as required.7. After all nodes are upgraded, reconnect the nodes to the network.8. Using the Command Menu, restart the system.
Upgrade Instructions, V1.4 or later (Network download option available) to V3.0
Project version numbers are imbedded in each project file. Because the “Save As” function creates a new version number that is different than the imbedded version, you must use the following procedure to install V3.0. Please follow these steps in order to upgrade the hardware and software in your system.
With 3-SDU version 3.0 installed:1. Save your project as a new version, using the "Save As" function in the file menu.2. Do a Signature Conversion, then Recompile your project, run db-conversion, and then “Save”
the project a second time.3. Select 3-CPU1 database and 3-CPU1 application code. DO NOT SELECT BOOTLOADER
CODE or ANY 3-SSDC/3-SDDC options!4. Connect the laptop to the “first” CPU on the network (any node for class A networks) and
NETWORK DOWNLOAD version 3.0 of the database and version 3.0 of the CPU Application code.
5. When complete, select all 3-CPU bootloader code. (Do NOT select 3-SSDC/3-SDDC bootstrap).6. NETWORK download the bootloader code to all nodes.
8.2 3-SSDC & 3-SDDC Signature Loop Controllers
8.2.1 You must upgrade the 3-CPU(1)s before upgrading the loop controllers.
8.2.2 To upgrade the loop controllers, you must:
8.2.2.1 Download the 3-SSDC/3-SDDC bootstrap to each LRM (bootstrap only, do not download application code or database).
8.2.2.2 Then issue a restart command for all panels from the 3-LCD menu.
8.2.2.3 Then download the 3-SSDC/3-SDDC application code.
8.2.2.4 Finally download the 3-SSDC/3-SDDC loop controller database(s).Notes:
Each of these steps must be completed in separate download sessions. This can be performed via a network download. If the bootstrap download fails, or if the sequence is taken out of order, then to recover the
power must be cycled on the panel and the download restarted with the bootstrap download.
8.3 3-AADCWhen updating the 3-AADC, follow the 3-SSDC/3-SDDC instructions, however you must download the Application Code and Bootstrap at the same time. This can be done over the network. After this is completed, download the database.
8.4 3-ASU Version 3.0
8.4.1 To upgrade the 3-ASU, you must:
8.4.1.1 First, download the 3-ASU bootstrap code.
8.4.1.2 Second, download the 3-ASU application code.Notes:
If both bootstrap and application code are selected in the 3-SDU for download, the 3-SDU will perform download in proper order.
8.5 Known Issues
8.5.1 Upgrade Issues
8.5.1.1 Under Windows NT, the communications port may lock up under certain conditions. This requires the reboot of your PC.
8.5.1.2 You may encounter timing errors during download. The download should complete even with these errors.
9 SDU Online HelpSDU Help requires that you have Internet Explorer 4.0 or later installed. The compiled HTML help file is not compatible with other web browsers.
If you have Internet Explorer but aren't sure of the version.1. Run Internet Explorer.2. Choose Help > About Internet Explorer.3. Look at the first line under the title graphic in the About Internet Explorer dialog. If the version number is less than 4.0, install Internet Explorer using the Windows 98 update function or download a copy from www.microsoft.com.windows/ie/.
10 Foreign Language Support
10.1 Printer use with Foreign Languages
10.1.1 When using a printer in support of foreign languages, single byte character set language printers must be able to support DOS code pages; double byte character language printers must be able to support the Windows code page listed below.
Since not all Windows characters are available on DOS printers, some characters are not supported.
The following are the DOS Code Page support required to have a printout in the local language.
Language Code PageChinese Simplified Windows Page Code 936 (GB)Chinese Traditional Windows Code Page 950 (Big 5)Korean Windows Code Page 949 (Extended
Wansung)Hebrew DOS Code Page 862Turkish DOS Code Page 857Dutch, French, Italian, Portuguese, Spanish, English
DOS Code Page 850
Polish, Slovak DOS Code Page 852Russian DOS Code Page 866
10.2 Bilingual Language Support
10.2.1 The EST3 system (3-LCD, 3-FTCU, KPDISP) provides bilingual operation. For any two languages to both be supported, they must both be supported by the same code page (font table). Refer to the table below to determine the system bilingual capabilities. Bilingual operation is not supported for Chinese and Korean.
Windows Code Page Languages Supported1250 (Eastern Europe) English, Polish, Slovak1251 (Cyrillic) English, Russian1252 (Western Europe) Dutch, English, French, Italian, Portuguese,
Spanish1254 (Turkish) English, Turkish1255 (Hebrew) English, Hebrew
10.2.1.1 Example: Bilingual operation between Polish and Slovak is supported. Bilingual operation between Polish and Russian is not supported, as they are not in the same Windows font table.
10.2.2 3-LCD Language Support Language
US
Mar
ketp
lace
s
Euro
pean
M
arke
tpla
ces
Asi
an
Mar
ketp
lace
Can
adia
n M
arke
tpla
ces
Mid
east
M
arke
tpla
ces
Chinese, traditional – Taiwan Chinese, simplified - PRC Dutch English (UK) English (US) 1 French Canadian Hebrew Italian Korean, Extended Wansung Polish Portuguese (Brazil) Russian Slovak Spanish (S. America) Turkish
1 For test & support purposes only
10.2.3 FTCU Language Support Language
US
Mar
ketp
lace
s
Euro
pean
M
arke
tpla
ces
Asi
an
Mar
ketp
lace
Can
adia
n M
arke
tpla
ces
Mid
east
M
arke
tpla
ces
Chinese, traditional – Taiwan 1
Chinese, simplified - PRC 1
Dutch English (UK) English (US) French Canadian Hebrew 1 1 1
Italian Korean, Extended Wansung 1
Portuguese (Brazil) Spanish (S. America) Turkish 1 1
Russian 1 1 1
Polish 1
Slovak 1
1 Only Western European character set is supported
08/22/01
