4100 programming instructions-ver. 8 - fire alarm …...5 you can change the default event reporting...

4100 ProgrammingInstructions-Ver. 8.01

574-102Rev. A

Technical Manuals Online! - http://www.tech-man.com

i

INTRODUCTION TO 4100 PROGRAMMER VERSION 8....................... 1Introduction............................................................................................ 1Related Documentation......................................................................... 1

INSTALLATION........................................................................................ 24100 Programmer ................................................................................. 2

SERIAL DIGITAL ALARM COMMUNICATORTRANSMITTER (SDACT) ..................................................................... 3SDACT .................................................................................................. 3SDACT Programmer............................................................................. 3Adding the SDACT................................................................................ 3SDACT Event Reporting ....................................................................... 5

VERY EARLY SMOKE DETECTION APPARATUS (VESDA)INTERFACE ............................................................................................. 6

VESDA .................................................................................................. 6VESDA Interface ................................................................................... 6Adding a VESDA Peripheral.................................................................. 7VESDA Configuration............................................................................ 9

4 - 20MA ZAM (AMZ) ............................................................................. 104-20mA ZAM (AMZ) ............................................................................ 10Configuring 4-20mA ZAM Point Types................................................ 10Adding a 4-20mA ZAM........................................................................ 12

NEW POINT TYPES............................................................................... 15Style-C Monitor.................................................................................... 15Supervisory Duct Detector .................................................................. 15Priority 2 with Open Circuit Trouble..................................................... 16Generic Normally Open Fire/Supervisory............................................ 16

COMPUTER PORT PROTOCOL........................................................... 17SHOW Command ............................................................................... 17LIST Command................................................................................... 19PRINT Command................................................................................ 19TYPE Command ................................................................................. 20SELECT Command............................................................................. 20CLEAR Command............................................................................... 20WALKTEST Command....................................................................... 21Command Error Codes ....................................................................... 21

CUSTOM CONTROL EXAMPLES ........................................................ 224-20mA ZAM Custom Control ............................................................. 22VESDA Custom Control ...................................................................... 27

INDEX..................................................................................................... 30

Table of Contents


ii

Copyright � Simplex Time Recorder Co. 1997 All rights reserved.Printed in the United States of America.

Information in this document is subject to change without notice. No partof this document may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, for any purpose, without the expresswritten consent of Simplex Time Recorder Company.

MAPNET II Communication Net is protected by US Patent No. 4,796,025.TrueAlarm Analog Detection is protected by US Patent No. 5,155,468.TrueAlarm Detector Base is protected by US Patent No. 5,173, 683.

Windows� is a trademark of the Microsoft Corporation.

VESDA Scanner� and MiniVESDA�-50 are trademarks and the nameVESDA� and VESDA� E70-D are registered trademarks of VisionSystems. All other logos are trademarks of their respective companies.

SYSTEM REACCEPTANCE TEST AFTER SOFTWARE CHANGES:To ensure proper system operation, this product must be tested inaccordance with NFPA 72-1993, Chapter 7 after any programmingoperation or change in site-specific software. Reacceptance testing isrequired after any change, addition or deletion of system components, orafter any modification, repair, or adjustment to system hardware orwiring.

All components, circuits, system operations, or software functions knownto be affected by a change must be 100% tested. In addition, to ensurethat other operations are not inadvertently affected, at least 10% ofinitiating devices that are not directly affected by the change, up to amaximum of 50 devices, must also be tested and proper systemoperation verified.

Copyrights & Trademarks

Cautions & Warnings


1

This document describes all enhancements in the 4100 Programmer Version 8software. Some functional enhancements are included briefly, as they are detailedin separate installation instruction manuals.

Version 8 supports an interface to the Serial DACT (SDACT), VESDA sensors,the 20mA Monitor ZAM, and new point types. It also enhances the 4100Computer Port to provide full front panel functionality from a remote locationwith the exception of enabling a download.

Important: When making any change to a 4100 job, you must use the JobBuilder to build the job before uploading that job to the 4100panel.

The following is a list of related documentation that you should refer to foradditional information.

� Serial DACT - Installation & Configuration Instructions........... 574-090� 20 mA Monitor ZAM - Installation Instructions......................... 574-704� 4100 Custom Control Editor - Programming Instructions.. FA4-41-225� 4100 Programming Unit - Pocket Reference..................... FA4-41-216 4100+/4020/UT - Summary Guide for CRT

Operating Commands................................................. FA4-31-306� VESDA� Hardware Interface Configuration Instructions........ 574-050� VESDA� Systems Manual.............. Accompanies VESDA Equipment

Introduction to 4100 Programmer Version 8

Introduction

Related Documentation

�


2

The 4100 Programmer Unit software Version 8 is a DOS-based program. TheProgrammer Unit software comes on four 720 KB 3.5” diskettes. Follow Steps1 through 4 to install the 4100 Programmer Unit onto a PC.

Note: Please refer to FSB-1008 when installing the 4100 Programmer Unit on an HP Omnibook 5000C laptop computer.

1. Turn your PC on and boot-up to a DOS command line.

2. Insert Disk 1 of the 4100 Programmer Unit software Version 8 into the floppy drive.

3. From the C:\> prompt, type A: and then press Enter.

4. From the A:\> prompt, type install and then press Enter (Figure 1 appears).

Figure 1. 4100 Programmer Installation Screen

Follow the prompts to install all four diskettes. When the installation of theprogrammer is complete, you can then install any Executive Software (e.g.,, UT,4020, etc.).

When necessary, your Autoexec.bat and Config.sys files may need specificchanges in order for the 4100 Programmer to work properly. The installationprogram can make these changes for you when you answer Yes at theappropriate prompt.

Installation

4100 Programmer


3

The 4100-0155 SDACT allows per-point reporting of alarm and troubleconditions to a central station via the public telephone network. This device is anew 4100-family slave card and uses internal Serial communication tocommunicate with the host panel. To use the SDACT, you must have Version 8of the 4100 Programmer Unit and Master software.

The SDACT comes with its own programmer software. Refer to the SDACT -Installation Instructions (574-090) for more information. The SDACT softwareis Windows-based and is used independently of the 4100 Programmer. Althoughmost of the programming of the SDACT is done from its own programmer, youmust use the 4100 Programmer Version 8 to add an SDACT to a 4100. Thissection describes how to add an SDACT to a 4100.

The SDACT is configured in the 4100 Programmer as an Interface card type(similar to an RS232, Mapnet, etc.). Data entry for the card is also similar to theRS232 with certain limitations. The SDACT consumes one of the five availableRS232 ports in the 4100 system and one of the CRT/Computer ports.

Use Steps 1 through 6 below to add an SDACT to the 4100 Programmer.

1. Boot up the 4100 Programmer on your PC.

2. Create a new job or load a specific job from the Utilities menu.

3. After the job is successfully loaded, use the arrow keys to select the Configuration menu and press Enter (see Figure 2).

Figure 2. System Configuration Menu

Continued on next page

Serial Digital Alarm Communicator Transmitter (SDACT)

SDACT

SDACT Programmer

Adding the SDACT


4

4. Using the arrow keys, select the System Cards menu and press Enter (see Figure 3).

Figure 3. Card Configuration Editor

5. Press the letter A to add a card to the 4100. Using the arrow keys, selectthe Interface menu from the choices at the top of the screen and press Enter (see Figure 4).

Figure 4. Add an Interface Card

6. Using the arrow keys, select the Serial DACT Interface option and press Enter. The programmer now requests how many SDACTs you wish to add and whether or not the SDACT is being added locally. Enter the correct response for both of these choices.

After adding the SDACT, return to the Utilities menu. Use the arrow keysto select Save Current Job from the Utilities menu and press Enter.Type the appropriate information for saving the file and save the configuration.

Serial Digital Alarm Communicator Transmitter (SDACT) , Continued

Adding the SDACT , continued


5

You can change the default Event reporting categories to control whatinformation is reported from the 4100 to the SDACT (fire, pri2, supervisory,trouble, etc.). No other programming is required. The default settings areshown in Figure 5.

Follow Steps 1 through 5 below to choose those events you wish reported by the4100 to the SDACT.

1. Using the 4100 Programmer, select the Utilities menu and load the specific job that contains your SDACT.

2. After the job is successfully loaded, use the arrow keys to select the Configuration menu (Figure 2) and press Enter.

3. Using the arrow keys, select the System Cards menu (Figure 3) andpress Enter.

4. Using the arrow keys, select Serial DACT Interface from the list of available cards and press Enter (see Figure 5).

Figure 5. SDACT Interface Card Data Entry

5. Using the arrow keys, select the Port Annunciation category and use the space bar to toggle the Enabled status of each event you wish reported to the SDACT.

After completing the Event Reporting configuration, return to the Utilitiesmenu. Use the arrow keys to select Save Current Job from theUtilities menu and press Enter. Type the appropriate information forsaving the file and save the configuration. You can now build your job from theJob builder menu.

Serial Digital Alarm Communicator Transmitter (SDACT) , Continued

SDACT Event Reporting


6

The 4100 Programmer (Version 8) provides the ability to program VESDAsmoke detectors into the 4100-family systems. This programming provides fullalarm reporting capability, logging, annunciation, and display of selected analoginformation. To use the VESDA interface, you must have the VESDA Gatewayat Revision 400 as well as Version 8 of the 4100 Programmer Unit and Mastersoftware and Revision 1.01 of the VESDA interface slave.

When installing the VESDA interface, please refer to the VESDA Interface -Installation/Operating Procedures(574-050).

You must configure the VESDA sensor using the VESDA System Manualbefore programming the 4100. Although part of the configuration is done fromthe VESDA product, you must use the 4100 Programmer Version 8 to addVESDA devices to a 4100. This section describes how to add the VESDAdevices (shown in Table 1) to a 4100. Two new point types exist in order tosupport the VESDA devices (shown in Table 2).

Table 1. VESDA Devices

Device Type DescriptionVSCAN VESDA Scanner�VE70D VESDA� E70-DVMIN50 MiniVESDA�-50

Table 2. VESDA Point Types

Point Type DescriptionS3SMOKE Three stage smoke detectorS3UTIL Three stage utility monitor

Very Early Smoke Detection Apparatus (VESDA) Interface

VESDA

VESDA Interface


7

Each VESDA card type that is added to the 4100 consumes one of the availableMapnet channels. This means that the total number of Mapnet and VESDAcards cannot exceed ten.

Use Steps 1 through 6 below to add a VESDA peripheral to the 4100Programmer.








Very Early Smoke Detection Apparatus (VESDA) Interface, Continued

Adding a VESDA Peripheral


8



6. Using the arrow keys, select the VESDA Interface option and press Enter. The programmer now requests how many VESDAs you wish to add and whether or not the VESDA is being added locally. Enter the correct response for both of these choices.

After adding the VESDA, return to the Utilities menu. Use the arrow keysto select Save Current Job from the Utilities menu and press Enter.Type the appropriate information for saving the file and save the configuration.You can now build your job from the Job builder menu.


Adding a VESDA Peripheral,(continued)


9

This section describes how to select a device type, point type, and custom labelfor your VESDA device. Use the following steps to configure a VESDA within a4100.

Note: Each VESDA device consumes four MAPNET device addresses. Eventhough the VESDA Scanner uses all four, the MiniVESDA-50 andVESDA E70-D use only one each.

1. After successfully loading a job, select the Configuration menu andselect System Cards .

2. Scroll through the available cards and choose the VESDA Interface. Oncethe VESDA Interface is highlighted, press E to edit the configuration (seeFigure 9).

Figure 9. VESDA Interface Card Data Entry

3. Using the arrow keys, move the highlight field in the Dev-Type column tothe appropriate Mapnet address (e.g., M1-1). Press F2 for a list ofallowable device types (shown in Table 1).

4. Choose the device type that matches the VESDA unit that is installed fromthe list of allowable types. The 4100 Programmer automatically fills in thePoint Type column for you. If this is not the desired point type for thedevice chosen, use the arrow keys to highlight the Point Type field for thataddress and press F2. Select your desired point type (shown in Table 2) andpress Enter.

5. Press Tab to move the highlight field to the Custom Label column. Inthis field you can add or edit a label for the point. You can use up to 40alphanumeric characters for your label. All letters appear in uppercase.


VESDA Configuration


10

The 4-20mA ZAM (AMZ) is supported as a new Mapnet device in 4100 Version8. This device allows monitoring of various third party sensors including toxic,flammable, and explosive gas sensors. When adding the AMZ, the 4100Master/Programmer must be at Version 8 and Revision 6.01 Mapnet firmwaremust be used. Adding an AMZ to one Mapnet channel does not requireupgrading any other Mapnet channels in the same 4100 that do not have AMZsprogrammed.

When installing the AMZ, please refer to MAPNET II 20mA Monitor ZAM -Installation Instructions (574-704).

Before adding an AMZ to a 4100, you must know the types of devices you wishthe AMZ to monitor. In order for the AMZ to operate correctly, the point typesfor this device are user-definable. In other words, you will define the types ofpoints (CO sensor, flammable gas, etc.) the AMZ monitors.

This section describes how to configure several user-defined point types to beused by the 4-20mA ZAM.





4. Using the arrow keys, select ANALOG MONITOR POINT TYPES andpress Enter (see Figure 11).


4 - 20mA ZAM (AMZ)

4-20mA ZAM (AMZ)

Configuring 4-20mA ZAMPoint Types


11

Figure 11. Analog Monitor Point Types

5. Press the letter A to add a user-defined point type for the AMZ.

There are eight input fields available for your input. These fields are shown inFigure 12. The fields and the type of information each field must possess for theproper configuration of the AMZ point type are listed in Table 3. The 4100Programmer allows for a maximum of 100 user-defined AMZ point types.

Table 3. AMZ Input Fields

Input Field DescriptionAMZ Type: This field describes the type of device the AMZ monitors. In Figure 12 the AMZ Type is CO

(Carbon Monoxide sensor).Alm Type: This field specifies the type of alarm sent to the 4100 when a specified threshold is crossed. The

choices are FIRE, MPRI2 (Priority 2), TROUBLE, LATSUPV (Latching Supervisory), orUTILITY.

Eng Unit Text: This field defines the Engineering Unit text that is displayed by the 4100. Examples are PPM(Parts Per Million), PPB (Parts Per Billion).

Display: This field defines how many places to the left of the decimal you wish to display. For example:XXX. (whole numbers), XXX.X (tenths), or XXX.XX (hundredths). A total of five numbers isallowed with a range of 0 to 65535.

4 mA: This is the value, in Engineering Units, you wish to display when the sensor reading is at 4mA.20 mA: This is the value, in Engineering Units, you wish to display when the sensor reading is at 20mA.Alarm Threshold: Type a “Y” in this field to indicate you wish a threshold crossing to send an alarm condition

(defined in Alm Type above) to the 4100.Units: This field indicates the threshold value, in Engineering Units. The 4100 Programmer

automatically computes the Milli-amps and Sensor Counts.


4-20mA ZAM, Continued

Configuring 4-20mA ZAMPoint Types (continued)


12

Important: When choosing one alarm threshold, use Threshold 3 first. Whenchoosing two alarm thresholds, use Threshold 2 as your first choiceand Threshold 3 as your second choice.

Figure 12. Configuring the Analog Monitor Point Type

This section describes how to select a device type, point type, and custom labelfor the 4-20mA ZAM. Use the following steps to add a 4-20mA ZAM to a 4100.

Important: You must use the steps in the Configuring a 4-20mA ZAM sectionof this publication before you can add a 4-20mA ZAM to the 4100.Refer to the 4100 Front Panel Operation Addendum (574-121) toprogram the calibration date in the 4100 for all devices.



3. After the job is successfully loaded, use the arrow keys to select the Configuration menu and press Enter.




Configuring a 4-20mA(continued)

Adding a 4-20mA ZAM


13



Figure 14. Add an Interface Card

6. Using the arrow keys, select the MAPNET Interface option and press Enter. The programmer now requests how many Mapnets you wish to add and whether or not the Mapnet is being added locally. Enter the correct response for both of these choices. You now have to edit the Mapnet Interface.

7. Select the Configuration menu and select System Cards .

8. Using the arrow keys, select the MAPNET Interface and press E to editthe selection.



Adding a 4-20mA ZAM(continued)


14

9. With the highlight field in the Dev-Type column, press F2. From the list ofallowable types choose ANAMON (see Figure 15).

Figure 15. MAPNET Interface Card Data Entry (Dev-Type)

10. Press Enter after choosing the device type. Press Tab to move the highlightfield to the Point Type column and press F2 for allowable choices (seeFigure 16).

Figure 16. MAPNET Interface Card Data Entry (Point Type)

11. Use the arrow keys to select a point type that you have already defined inthe Configuring 4-20mA ZAM Point Types section of this publication.

After adding the Mapnet Interface, return to the Utilities menu. Use thearrow keys to select Save Current Job from the Utilities menu andpress Enter. Type the appropriate information for saving the file and save theconfiguration. You can now build your job from the Job builder menu.


Adding a 4-20mA ZAM(continued)


15

Four new point types are introduced in the 4100 Programmer Version 8. Thesepoint types include a Style-C Monitor Point, Supervisory Duct Detector, Priority2 with Open Circuit Trouble, and a Normally Open Generic Fire/Supervisorypoint type to connect remote panels.

The 4100 Version 8 supports a new Style-C fire monitor point. The point type(STYLEC ) has a FIRE MONITOR ZONE banner and maps physical states tothe logical states shown in Table 4.

Table 4. STYLEC Point Type Physical/Logical States

Physical State Logical State Status MessageNormal Normal NORMAL

Abnormal Fire FIRE ALARM

Open Circuit Trouble OPEN CKT TROUBLE

Short Circuit Trouble SHORT CKT TROUBLE

This point type may be programmed on any tri-state monitor point on anyeight-zone monitor card. The STYLEC point type is not supported on the 24 I/Oor Mapnet cards. The 4100 Programmer auto-generates this point into all listsappropriate for a general fire alarm point (e.g., L18, Walk Test lists, etc.). TheFire state latches until a system reset is performed, but both trouble conditionsclear immediately once the zone is restored to normal. Where a physical state ofShort Circuit an Alarm is the usual Logical State. With this point type, a ShortCircuit has the Logical State of Trouble.

The supervisory duct detector point type (SDUCT) has a DUCT DETECTORbanner and maps physical states to the logical states shown in Table 5.

Table 5. SDUCT Point Type Physical/Logical States


Abnormal Supervisory ABNORMAL


Short Circuit Supervisory ABNORMAL

This point type may be programmed on any monitor point on eight-zone monitorcards or on Mapnet devices. The supervisory and trouble conditions are non-latching and clear once the point is returned to normal.

Point Types

Style-C Monitor

Supervisory Duct Detector


16

Unlike previous Priority 2 (PRI2) points, the Generic Priority 2 (GENPRI2)monitor point is not designed for security applications. Instead, it is designedwith more generic applications in mind. This point type has a PRI2 MONITORbanner and maps an open circuit physical state to a logical trouble conditioninstead of a PRI2 alarm. The physical and logical states are shown in Table 6.

Table 6. GENPRI2 Point Type Physical/Logical States


Abnormal Priority 2 PRI2 ALARM


Short Circuit Priority 2 PRI2 ALARM

This point type may be programmed on any monitor point on eight-zone monitorcards or on Mapnet devices. The Priority 2 alarm state latches until a PRI2 resetis completed but the trouble condition only clears when the point is restored tonormal.

The Generic Normally Open Fire/Supervisory (GENFS) point type performsexactly as Water Flow/Sprinkler Open (WSO) point type but provides adifferent point type banner and different, more generic status messages. Thispoint type is used to connect a remote panel to a 4100 system with a contactclosure output. A supervisory/trouble condition (abnormal state) indicates thatthe remote panel is in trouble, while an open circuit trouble indicates that thewiring used to connect the two panels has failed. This point type has aFIRE/SUPV MONITOR banner and maps physical and logical states as shownin Table 7.

Table 7. GENFS Point Type Physical/Logical States


Abnormal Supervisory SUPERVISORY\TROUBLE


Short Circuit Fire FIRE ALARM

This point type may be programmed on any tri-state monitor point on any eight-zone monitor card. This point type is not supported on the 24 I/O or Mapnetcards. The 4100 Programmer auto-generates this point into the same lists as aWSO point. The fire state latches until the zone is restored to normal and asystem reset is performed. The supervisory state clears immediately when thezone is restored to normal.

Point Types, Continued

Priority 2 with Open CircuitTrouble

Generic Normally OpenFire/Supervisory


17

The 4100 computer port protocol has several enhancements with the release ofVersion 8. These enhancements are supplied to permit nearly every operationallowed from the front panel of the 4100. These enhancements include viewingand clearing of the historical logs, network diagnostic capability, Walk Test, etc.These enhancements require Version 8 of the master/programmer software andRevision 2.01 or later of the RS232 Interface firmware.

When referring to commands, the asterisk (* ) is a marker of the minimumamount of characters needed to execute a command. For example, SH*OW. Theletters SH are the only characters required for the command to be recognized.

If any form of the command line ends with a "/P", and the output is greater thanwhat can fit on one screen, the display stops with the screen full and prompts you to"Press Return For More Output.” While paused, unsolicited output is frozen. Atime delay allows the screen to be paused for no more than 30 seconds.

Unsolicited output is allowed only after the command has completed all outputapplicable. Without the "/P", text will scroll off the screen when screen fills up.

The SHOW command has two different input formats: SHOW <point> andSHOW <keyword>.

SHOW Point

This command followed by a point ID is the equivalent of using the FUNCTIONbutton on the front panel. It is a way of outputting to the computer port informationabout a point other than just the point’s status. The SHOW <point> form has onlyone input format, but the output format changes depending on the point category.A sample output is shown below.

Input Format:

SH*OW <point><CR> where <point> is a standard point ID in either zone oraddress format.

Example:

SHOW ZN1<CR>

MONITOR ZONE CUSTOM LABELZN1 PULL STATIONPOINT ADDRESS: 4-1-08 ZONE CLASS B MONITOR CARDLocal Unit - Main Panel


Computer Port Protocol

SHOW Command


18

UNIT NUMBER: 0 RUI NUMBER: LOCAL----------------------------------------PRIMARY STATUS ALARMPHYSICAL STATE SHORTRAW STATE SHORTACTIVE STATE ONARMED STATE ARMEDENABLED STATE ENABLEDUNVERIFIED 0

SHOW Keyword

The SHOW command followed by a valid keyword outputs information to thecomputer port appropriate to the keyword. The keywords are listed below.

� PORTS - Outputs a list of all ports configured and their device types. Whenno ports are present, a “No Ports Configured” message is returned.

� TOPOLOGY - Identical to the loop topology line of the DIAGNOSTICcommand without an argument. If there are no nodes, a “No network cardconfigured” message is returned.

� NODES - Outputs a listing of all nodes in the network showing the nodenumber, node name, and the online status of the node.

� COUNTS - Outputs the totals of off-normal conditions for the system lists.� CARDS - Outputs a list of all cards configured at the node.

Computer Port Protocol, Continued

SHOW Command (continued)


19

This command returns the current logical point status for the point requested inan easy-to-read format. The output format is a single line per reported statusformatted as follows: ZONE, CUSTOM LABEL, POINT BANNER, STATUS.If ACK is needed, the STATUS is followed by an asterisk. The four methods ofinput for the LIST command are shown below.

L*IST <point> - This command followed by only a point ID outputs one line foreach abnormal/on status for the point.

L*IST <point> [qualifier] - This command followed by both a point IDand a qualifier outputs only one line for the status described by the qualifier. Thefollowing is a list of qualifiers.

A - PrimaryF - FireP - Pri2S - SupervisoryT - TroubleU - UtilityC - ControlD - Disable trouble

L*IST [qualifier] - This command followed immediately by a qualifieroutputs one line for each point in the abnormal/on state described by the qualifier.

Note: LIST A<CR> is not allowed.

L*IST <CR> - This command followed only by <CR> outputs one line for eachabnormal/on status for each point in the system.

This command causes reports to be output via the currently selected reportsprinter in the same manner as is now possible via the front panel or the CRTmenus. The reports are as follows:

� ALOG - Sends the Alarm Historical Log to the currently selected printer.� TLOG - Sends the Trouble Historical Log to the currently selected printer.� TASTAT*US - Sends the TrueAlarm Status Report to the currently selected

printer.� TASERV*ICE - Sends the TrueAlarm Service Report to the currently

selected printer.

Note: See the SELECT command to change the currently selected report printer.



LIST Command

PRINT Command


20

This command causes reports to be output via the currently selected reportsprinter in the same manner as is now possible via the front panel or the CRTmenus. The reports are as follows:

� ALOG - Sends the Alarm Historical Log to the currently selected printer.� TLOG - Sends the Trouble Historical Log to the currently selected printer.� TASTAT*US - Sends the TrueAlarm Status Report to the currently selected

printer.� TASERV*ICE - Sends the TrueAlarm Service Report to the currently

selected printer.

This command stops at the end of each page of text automatically and promptsyou for further instructions from the CRT menus.

This command allows you to select a report printer. Typing "SELECT" by itselfreturns a list of printers available each with its device type. If no printers areconfigured, the message "No printers configured" is returned. The currentlyselected report printer is denoted by an asterisk. Typing "SELECT" followed bya number from 1 to 5 changes the currently selected printer to the port numberchosen. If an invalid port number is typed, an error message is returned.

This command clears the Alarm Historical Log or the Trouble Historical Logdepending on the argument passed. In order to execute this command, it isnecessary to be logged in. An access level of 3 is required by default, but can bechanged by the programmer. If an error occurs on the input line, an appropriateerror message is returned.

CLEAR ALOG - Clears the Alarm Historical Log.

CLEAR TLOG - Clears the Trouble Historical Log.

CLEAR TALLY <point identification> - Clears the Alarm Verification Tally forthe point specified.

CLEAR PEAK <point identification> - Clears the Peak Analog Value for the pointspecified.



TYPE Command

SELECT Command

CLEAR Command


21

This command initiates or stops Walk Test. The command must be followed by<arg1> (arg1 is the Walk Test group number) after which up to four qualifiers canbe passed in the command line in any order. The qualifiers are listed in Table 7.Typing "WALKTEST" followed by a number returns the current Walk Test statusfor the group specified. If an invalid group number is entered, an appropriate errormessage is returned. If any qualifier is omitted in the command line, the currentvalue remains in effect. Qualifiers are evaluated from left to right. If conflictingqualifiers are input, the right most qualifier is the one remaining in effect.

Table 7. Walk Test Qualifiers

Qualifier DescriptionON Initiates Walk TestOFF Terminates Walk TestLOG Causes Walk Test events to be loggedNOLOG Terminates Walk Test event loggingZONE Enables zone / disables zero coding during Walk TestZERO Enables zero / disables zone coding during Walk TestSIG Enables audible signal during Walk TestNOSIG Disables signal during Walk Test

Example:

WALK 1 ON<CR> initiates Walk Test on group 1.

When issuing commands to the computer port, error conditions may exist that causean error message to be returned. The following is a list of these error messages:

� %ERROR 1: Invalid command syntax� %ERROR 2: Invalid point� %ERROR 3: Operation invalid for point� %ERROR 4: Qualifier invalid for point� %ERROR 5: Insufficient access level� %ERROR 6: Insufficient port priority� %ERROR 7: Report printer in trouble� %ERROR 8: Report queue is full� %ERROR 9: No printers configured in the system� %ERROR 10: Reports generator is busy - try again later� %ERROR 11: Node not configured� %ERROR 12: Can not send messages to self� %ERROR 13: Invalid Walk Test group� %ERROR 14: Unable to Enter Walk Test - Alarms present� %ERROR 15: No Walk Test points configured� %ERROR 16: No Network Card Configured


WALKTEST Command

Command Error Codes


22

This section shows Custom Control programming examples for the 4-20mA ZAMand the VESDA devices. These are common applications to be used as referenceonly.

The following Custom Control input qualifiers are applicable to the AMZ points:

� ON� FIRE� DISABLE� TROUBLE� TBLACK� FIRE ALARM ACK� DETECT� SUPV� SUPVACK� PRIORITY 2 ALARM� PRI2 ALARM ACK� PRI2 ALARM DETECT

Note: The DETECT status is true only for the initial alarm brought in for eachAMZ point. It is not true for each time the AMZ reaches an alarmthreshold.

ANALOG VALUE

The value in engineering units of the AMZ point may be used as input to customcontrol equations. The full range of qualifiers may be used; 'equal to', 'not equal to','greater than', 'greater than or equal to', 'less than', and 'less than or equal to'.

Example:

COMMENTS: [END-OF-COMMENTS]INPUTS: If AMZ: M1-1 is greater than value: 15 ppm [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P256 UTILITY [END-OF-OUTPUTS]END:


Custom Control Examples

4-20mA ZAM Custom Control


23

AMZ THRESHOLD

With Version 8 a new Custom Control input qualifier for AMZ points exists. It iscalled 'AMZ THRESHOLD'. It is used in the same manner as 'SMOKE LEVEL' isused today, except user defined levels are assigned to the AMZ points.

Following is an example of a Custom Control equation using the AMZ threshold asan input:

COMMENTS: [END-OF-COMMENTS]INPUTS: The AMZ THRESHOLD at or above THRESHOLD 1 of: M1-X USRDEF CUSTOM LABEL [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P256 UTILITY [END-OF-OUTPUTS]END:

LED MODES

There are no new LED modes for the AMZ points. Many of the existing LEDmodes are applicable for these points. If it is desired to track the level of the AMZpoint through LEDs, Custom Control can be written to have a pseudo track thedesired level, and have the LED track the pseudo.

The following LED modes are applicable to AMZ points:

ON, OFF, FIRE, PRI2ALM, P2ALERT, SUPERV, SALERT, PALERT,TROUBLE, TALERT, and DISABLE.

SWITCH MODES

The only switch modes that are valid for the AMZ points are 'DE',(Disable/Enable), 'TDE', (Toggle Disable/Enable), and switch modes that controlthe LED.

Note: When an AMZ point is disabled, no 'SENSOR TROUBLE' will come infrom the device, (for example, the sensor is being calibrated), and power isnot removed from the device.


Custom Control Examples, Continued

4-20mA ZAM Custom Control(continued)


24

A PROGRAMMING EXAMPLE

Some sensors have an analog range denoting discrete occurrences. For instance, aflame detector may report a trouble by sending a value of 5 mA, a detection ofinfrared by a value of 10 mA, detection of UV by a value of 15 mA, and adetection of infrared and UV by a value of 20 mA. Custom programming would berequired to use this sensor to its full capacity.

1. Several pseudo points are defined as shown in Figure 17.

Figure 17. Digital Pseudo Card Data Entry Screen

2. The AMZ ZAM is programmed as shown in Figure 18 and 19.

Figure 18. Analog Monitor Point Types Screen





25

Figure 19. MAPNET Interface Card Data Entry Screen

3. Custom Control is written to bring the pseudos at the correct time under the correct events.

TROUBLE DETECTION CUSTOM CONTROL

COMMENTS: TROUBLE DETECTION [END-OF-COMMENTS]INPUTS: If AMZ: M1-1 is greater than value: 4 mA AND If AMZ: M1-1 is less than value: 7 mA [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P256 TROUBLE [END-OF-OUTPUTS]END:





26

INFRARED DETECTION CUSTOM CONTROL

COMMENTS: INFRARED DETECTION [END-OF-COMMENTS]INPUTS: If AMZ: M1-1 is greater than value: 7 mA AND If AMZ: M1-1 is less than value: 12 mA [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P257 FIRE [END-OF-OUTPUTS]END:

UV DETECTION CUSTOM CONTROL

COMMENTS: UV DETECTION [END-OF-COMMENTS]INPUTS: If AMZ: M1-1 is greater than value: 12 mA AND If AMZ: M1-1 is less than value: 17 mA [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P258 TROUBLE [END-OF-OUTPUTS]END:

INFRARED AND UV DETECTION CUSTOM CONTROL

COMMENTS: INFRARED AND UV DETECTION [END-OF-COMMENTS]INPUTS: If AMZ: M1-1 is greater than value: 17 mA [END-OF-INPUTS]OUTPUTS: TRACK points ON pri=9,9 P259 TROUBLE [END-OF-OUTPUTS]END:




27

This section contains some sample Custom Control equations that could helpprovide some flexibility in configuring the VESDA devices within the 4100.Two issues are addressed.

� Customizing logical states associated with the alert, action and fire states ofthe VESDA detector

� Providing a redundant detection system without having to annunciateduplicate alarm conditions

CUSTOMIZED LOGICAL STATES

In order to provide customized logical states for a VESDA device, the followingsteps must be taken.

1. Configure device with a point type of S3UTIL2. Reserve three digital pseudo points and configure them to provide the

desired logical state3. Write custom control equation(s) to turn on the pseudo points when the

appropriate VESDA device thresholds are crossed

Example

An application requires the alert, action, and fire thresholds of a VESDA deviceto map to Supervisory, Priority 2 alarm, and Fire alarm respectively. Assumethe VESDA device is addressed as M1-1.

1. Configure M1-1 with point type S3UTIL.

2. Reserve three digital pseudo points (P256, P257, P258 for this example).� P256 is configured as supervisory� P257 is configured as priority 2� P258 is configured as fire

3. Provide descriptive custom labels that tie the pseudos back to the VESDAdetector being customized.

4. Write three custom control equations (shown below) so the pseudos trackthe logical state of the VESDA device and cause Supervisory, Priority 2 andFire conditions when appropriate.

5. Insert the three digital pseudos into L73 (CONTROL POINTS OFF - ONSYSTEM RESET) so that the points turn off on a successful system reset.



VESDA Custom Control


28

COMMENTS: VESDA STAGE 1 ALARM [END-OF-COMMENTS]INPUTS: STAGE 1 ALARM M1-1 [END-OF-INPUTS]OUTPUTS: HOLD points ON PRI= 9,9 P256 SUPV [END-OF-OUTPUTS]END:

COMMENTS: VESDA STAGE 2 ALARM [END-OF-COMMENTS]INPUTS: STAGE 2 ALARM M1-1 [END-OF-INPUTS]OUTPUTS: HOLD points ON PRI= 9,9 P257 PRI2 [END-OF-OUTPUTS]END:

COMMENTS: VESDA STAGE 3 ALARM [END-OF-COMMENTS]INPUTS: STAGE 3 ALARM M1-1 [END-OF-INPUTS]OUTPUTS: HOLD points ON PRI= 9,9 P258 FIRE [END-OF-OUTPUTS]END:



VESDA Custom Control(continued)


29

REDUNDANCY WITHOUT DUPLICATE ALARMS

To provide a redundant detection system without creating duplicate alarms in theFACP, follow these steps:

1. Configure the redundant GENIAM device as a utility device.

2. Reserve a digital pseudo to annunciate the abnormal condition when theprimary means of alarm detection fails.

3. Write custom control equations to turn on the pseudo points when theprimary means of detection fails and a threshold level has been crossed.

Example

An application requires that a redundant means of alarm detection is present fora VESDA device. Duplicate alarm conditions are not permitted. AssumeVESDA device is addressed as M1-1 and the GENIAM device is addressed asM2-1.

1. Configure M1-1 with point type S3MOKE.

2. Configure M2-1 with point type UTILITY (device is monitoring the firethreshold only).

3. Reserve a digital pseudo point (P256 for this example).

4. P256 is configured as fire.

5. Provide a descriptive custom label that ties the pseudo back to the VESDAdetector being backed up with redundant system.

6. Write a custom control equation so the pseudo tracks the logical state of theVESDA device only when the primary means of detection is lost.

COMMENTS: REDUNDANT VESDA [END-OF-COMMENTS]INPUTS: ON state of M2-1

AND NOT ON of M1-1DELAY 5

[END-OF-INPUTS]OUTPUTS: TRACK ON PRI= 9,9 P256 FIRE [END-OF-OUTPUTS]END:


VESDA Custom Control(continued)


30

A

Add an Interface Card · 4Adding a 4-20mA ZAM · 12Adding the SDACT · 3AMZ · 10, 11, 22, 23, 24, 25, 26Analog Value · 22ANAMON Point type · 14

C

Card Configuration Editor · 4CLEAR Command · 20Command Error Codes · 21Computer Port · 1, 17, 18, 19, 20, 21Customized Logical States· 27

G

GENFS Point Type · 16GENPRI2 Point Type · 16

I

Infrared and UV Detection CustomControl · 26

Infrared Detection Custom Control · 26

L

LED MODES · 23LIST Command · 19

P

PRINT Command · 19

R

Redundancy without Duplicate Alarms· 29

S

SDACT Interface Card Data Entry · 5SDACT Programmer · 3SDUCT · 15SELECT Command · 20Serial DACT · 1, 4, 5SHOW Command· 17, 18STYLEC Point Type· 15Switch Modes · 23System Configuration Menu · 3

T

TYPE Command · 20

U

UV Detection Custom Control · 26

V

VESDA · 1, 6, 7, 8, 9, 22, 27, 28, 29VESDA Configuration · 9

W

WALKTEST Command · 21

Index


4100 programming instructions-ver. 8 - fire alarm …...5 you can change the default event reporting...

Documents