4100 Programming Instructions-Ver. 8.01

Transcription

1 4100 Programming Instructions-Ver Rev. A

2 Table of Contents INTRODUCTION TO 4100 PROGRAMMER VERSION Introduction... 1 Related Documentation... 1 INSTALLATION Programmer... 2 SERIAL DIGITAL ALARM COMMUNICATOR TRANSMITTER (SDACT)... 3 SDACT... 3 SDACT Programmer... 3 Adding the SDACT... 3 SDACT Event Reporting... 5 VERY EARLY SMOKE DETECTION APPARATUS (VESDA) INTERFACE... 6 VESDA... 6 VESDA Interface... 6 Adding a VESDA Peripheral... 7 VESDA Configuration MA ZAM (AMZ) mA ZAM (AMZ) Configuring 4-20mA ZAM Point Types Adding a 4-20mA ZAM NEW POINT TYPES Style-C Monitor Supervisory Duct Detector Priority 2 with Open Circuit Trouble Generic Normally Open Fire/Supervisory COMPUTER PORT PROTOCOL SHOW Command LIST Command PRINT Command TYPE Command SELECT Command CLEAR Command WALKTEST Command Command Error Codes CUSTOM CONTROL EXAMPLES mA ZAM Custom Control VESDA Custom Control INDEX i

3 Copyrights & Trademarks Copyright Simplex Time Recorder Co All rights reserved. Printed in the United States of America. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written 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 name VESDA and VESDA E70-D are registered trademarks of Vision Systems. All other logos are trademarks of their respective companies. Cautions & Warnings SYSTEM REACCEPTANCE TEST AFTER SOFTWARE CHANGES: To ensure proper system operation, this product must be tested in accordance with NFPA , Chapter 7 after any programming operation or change in site-specific software. Reacceptance testing is required after any change, addition or deletion of system components, or after any modification, repair, or adjustment to system hardware or wiring. All components, circuits, system operations, or software functions known to be affected by a change must be 100% tested. In addition, to ensure that other operations are not inadvertently affected, at least 10% of initiating devices that are not directly affected by the change, up to a maximum of 50 devices, must also be tested and proper system operation verified. ii

4 Introduction to 4100 Programmer Version 8 Introduction This document describes all enhancements in the 4100 Programmer Version 8 software. Some functional enhancements are included briefly, as they are detailed in 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 4100 Computer Port to provide full front panel functionality from a remote location with the exception of enabling a download. Important: When making any change to a 4100 job, you must use the Job Builder to build the job before uploading that job to the 4100 panel. Related Documentation The following is a list of related documentation that you should refer to for additional information. Serial DACT - Installation & Configuration Instructions ma Monitor ZAM - Installation Instructions Custom Control Editor - Programming Instructions.. FA Programming Unit - Pocket Reference... FA /4020/UT - Summary Guide for CRT Operating Commands... FA VESDA Hardware Interface Configuration Instructions VESDA Systems Manual... Accompanies VESDA Equipment 1

5 Installation 4100 Programmer The 4100 Programmer Unit software Version 8 is a DOS-based program. The Programmer Unit software comes on four 720 KB 3.5 diskettes. Follow Steps 1 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 Programmer Installation Screen Follow the prompts to install all four diskettes. When the installation of the programmer 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 specific changes in order for the 4100 Programmer to work properly. The installation program can make these changes for you when you answer Yes at the appropriate prompt. 2

6 Serial Digital Alarm Communicator Transmitter (SDACT) SDACT The SDACT allows per-point reporting of alarm and trouble conditions to a central station via the public telephone network. This device is a new 4100-family slave card and uses internal Serial communication to communicate with the host panel. To use the SDACT, you must have Version 8 of the 4100 Programmer Unit and Master software. SDACT Programmer The SDACT comes with its own programmer software. Refer to the SDACT - Installation Instructions ( ) for more information. The SDACT software is Windows-based and is used independently of the 4100 Programmer. Although most of the programming of the SDACT is done from its own programmer, you must use the 4100 Programmer Version 8 to add an SDACT to a This section describes how to add an SDACT to a Adding the SDACT 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 the RS232 with certain limitations. The SDACT consumes one of the five available RS232 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 3

7 Serial Digital Alarm Communicator Transmitter (SDACT), Continued Adding the SDACT, continued 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 Using the arrow keys, select the 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 keys to select Save Current Job from the Utilities menu and press Enter. Type the appropriate information for saving the file and save the configuration. 4

8 Serial Digital Alarm Communicator Transmitter (SDACT), Continued SDACT Event Reporting You can change the default Event reporting categories to control what information is reported from the 4100 to the SDACT (fire, pri2, supervisory, trouble, etc.). No other programming is required. The default settings are shown in Figure 5. Follow Steps 1 through 5 below to choose those events you wish reported by the 4100 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) and press 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 Utilities menu. Use the arrow keys to 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. 5

9 Very Early Smoke Detection Apparatus (VESDA) Interface VESDA The 4100 Programmer (Version 8) provides the ability to program VESDA smoke detectors into the 4100-family systems. This programming provides full alarm reporting capability, logging, annunciation, and display of selected analog information. To use the VESDA interface, you must have the VESDA Gateway at Revision 400 as well as Version 8 of the 4100 Programmer Unit and Master software and Revision 1.01 of the VESDA interface slave. When installing the VESDA interface, please refer to the VESDA Interface - Installation/Operating Procedures ( ). VESDA Interface You must configure the VESDA sensor using the VESDA System Manual before programming the Although part of the configuration is done from the VESDA product, you must use the 4100 Programmer Version 8 to add VESDA devices to a This section describes how to add the VESDA devices (shown in Table 1) to a Two new point types exist in order to support the VESDA devices (shown in Table 2). Table 1. VESDA Devices VSCAN VE70D VMIN50 Device Type Description VESDA Scanner VESDA E70-D MiniVESDA-50 Table 2. VESDA Point Types S3SMOKE S3UTIL Point Type Description Three stage smoke detector Three stage utility monitor 6

10 Very Early Smoke Detection Apparatus (VESDA) Interface, Continued Adding a VESDA Peripheral Each VESDA card type that is added to the 4100 consumes one of the available Mapnet channels. This means that the total number of Mapnet and VESDA cards cannot exceed ten. Use Steps 1 through 6 below to add a VESDA peripheral 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 6). Figure 6. System Configuration Menu 4. Using the arrow keys, select the System Cards menu and press Enter (see Figure 7). Figure 7. Card Configuration Editor Continued on next page 7

11 Very Early Smoke Detection Apparatus (VESDA) Interface, Continued Adding a VESDA Peripheral, (continued) 5. Press the letter A to add a card to the Using the arrow keys, select the Interface menu from the choices at the top of the screen and press Enter (see Figure 8). Figure 8. Card Configuration Editor 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 keys to 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. 8

12 Very Early Smoke Detection Apparatus (VESDA) Interface, Continued VESDA Configuration This section describes how to select a device type, point type, and custom label for your VESDA device. Use the following steps to configure a VESDA within a Note: Each VESDA device consumes four MAPNET device addresses. Even though the VESDA Scanner uses all four, the MiniVESDA-50 and VESDA E70-D use only one each. 1. After successfully loading a job, select the Configuration menu and select System Cards. 2. Scroll through the available cards and choose the VESDA Interface. Once the VESDA Interface is highlighted, press E to edit the configuration (see Figure 9). Figure 9. VESDA Interface Card Data Entry 3. Using the arrow keys, move the highlight field in the Dev-Type column to the appropriate Mapnet address (e.g., M1-1). Press F2 for a list of allowable device types (shown in Table 1). 4. Choose the device type that matches the VESDA unit that is installed from the list of allowable types. The 4100 Programmer automatically fills in the Point Type column for you. If this is not the desired point type for the device chosen, use the arrow keys to highlight the Point Type field for that address and press F2. Select your desired point type (shown in Table 2) and press Enter. 5. Press Tab to move the highlight field to the Custom Label column. In this field you can add or edit a label for the point. You can use up to 40 alphanumeric characters for your label. All letters appear in uppercase. 9

13 4-20mA ZAM (AMZ) 4-20mA ZAM (AMZ) The 4-20mA ZAM (AMZ) is supported as a new Mapnet device in 4100 Version 8. This device allows monitoring of various third party sensors including toxic, flammable, and explosive gas sensors. When adding the AMZ, the 4100 Master/Programmer must be at Version 8 and Revision 6.01 Mapnet firmware must be used. Adding an AMZ to one Mapnet channel does not require upgrading any other Mapnet channels in the same 4100 that do not have AMZs programmed. When installing the AMZ, please refer to MAPNET II 20mA Monitor ZAM - Installation Instructions ( ). Configuring 4-20mA ZAM Point Types Before adding an AMZ to a 4100, you must know the types of devices you wish the AMZ to monitor. In order for the AMZ to operate correctly, the point types for this device are user-definable. In other words, you will define the types of points (CO sensor, flammable gas, etc.) the AMZ monitors. This section describes how to configure several user-defined point types to be used by the 4-20mA ZAM. 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 10). Figure 10. System Configuration Menu 4. Using the arrow keys, select ANALOG MONITOR POINT TYPES and press Enter (see Figure 11). Continued on next page 10

14 4-20mA ZAM, Continued Configuring 4-20mA ZAM Point Types (continued) 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 in Figure 12. The fields and the type of information each field must possess for the proper configuration of the AMZ point type are listed in Table 3. The 4100 Programmer allows for a maximum of 100 user-defined AMZ point types. Table 3. AMZ Input Fields Input Field Description AMZ 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), or UTILITY. Eng Unit Text: This field defines the Engineering Unit text that is displayed by the 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 is allowed with a range of 0 to 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 Units: This field indicates the threshold value, in Engineering Units. The 4100 Programmer automatically computes the Milli-amps and Sensor Counts. Continued on next page 11

15 4-20mA ZAM, Continued Configuring a 4-20mA (continued) Important: When choosing one alarm threshold, use Threshold 3 first. When choosing two alarm thresholds, use Threshold 2 as your first choice and Threshold 3 as your second choice. Figure 12. Configuring the Analog Monitor Point Type Adding a 4-20mA ZAM This section describes how to select a device type, point type, and custom label for the 4-20mA ZAM. Use the following steps to add a 4-20mA ZAM to a Important: You must use the steps in the Configuring a 4-20mA ZAM section of this publication before you can add a 4-20mA ZAM to the Refer to the 4100 Front Panel Operation Addendum ( ) to program the calibration date in the 4100 for all devices. 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. 4. Using the arrow keys, select the System Cards menu and press Enter (see Figure 13). Continued on next page 12

16 4-20mA ZAM, Continued Adding a 4-20mA ZAM (continued) Figure 13. Card Configuration Editor 5. Press the letter A to add a card to the Using the arrow keys, select the Interface menu from the choices at the top of the screen and press Enter (see Figure 14). 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 edit the selection. Continued on next page 13

17 4-20mA ZAM, Continued Adding a 4-20mA ZAM (continued) 9. With the highlight field in the Dev-Type column, press F2. From the list of allowable 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 highlight field to the Point Type column and press F2 for allowable choices (see Figure 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 in the Configuring 4-20mA ZAM Point Types section of this publication. After adding the Mapnet Interface, return to the Utilities menu. Use the arrow keys to 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. 14

18 Point Types Four new point types are introduced in the 4100 Programmer Version 8. These point types include a Style-C Monitor Point, Supervisory Duct Detector, Priority 2 with Open Circuit Trouble, and a Normally Open Generic Fire/Supervisory point type to connect remote panels. Style-C Monitor 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 to the logical states shown in Table 4. Table 4. STYLEC Point Type Physical/Logical States Physical State Logical State Status Message Normal 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 any eight-zone monitor card. The STYLEC point type is not supported on the 24 I/O or Mapnet cards. The 4100 Programmer auto-generates this point into all lists appropriate for a general fire alarm point (e.g., L18, Walk Test lists, etc.). The Fire state latches until a system reset is performed, but both trouble conditions clear immediately once the zone is restored to normal. Where a physical state of Short Circuit an Alarm is the usual Logical State. With this point type, a Short Circuit has the Logical State of Trouble. Supervisory Duct Detector The supervisory duct detector point type (SDUCT) has a DUCT DETECTOR banner and maps physical states to the logical states shown in Table 5. Table 5. SDUCT Point Type Physical/Logical States Physical State Logical State Status Message Normal Normal NORMAL Abnormal Supervisory ABNORMAL Open Circuit Trouble OPEN CKT TROUBLE Short Circuit Supervisory ABNORMAL This point type may be programmed on any monitor point on eight-zone monitor cards or on Mapnet devices. The supervisory and trouble conditions are nonlatching and clear once the point is returned to normal. 15

19 Point Types, Continued Priority 2 with Open Circuit Trouble Unlike previous Priority 2 (PRI2) points, the Generic Priority 2 (GENPRI2) monitor point is not designed for security applications. Instead, it is designed with more generic applications in mind. This point type has a PRI2 MONITOR banner and maps an open circuit physical state to a logical trouble condition instead of a PRI2 alarm. The physical and logical states are shown in Table 6. Table 6. GENPRI2 Point Type Physical/Logical States Physical State Logical State Status Message Normal Normal NORMAL Abnormal Priority 2 PRI2 ALARM Open Circuit Trouble OPEN CKT TROUBLE Short Circuit Priority 2 PRI2 ALARM This point type may be programmed on any monitor point on eight-zone monitor cards or on Mapnet devices. The Priority 2 alarm state latches until a PRI2 reset is completed but the trouble condition only clears when the point is restored to normal. Generic Normally Open Fire/Supervisory The Generic Normally Open Fire/Supervisory (GENFS) point type performs exactly as Water Flow/Sprinkler Open (WSO) point type but provides a different point type banner and different, more generic status messages. This point type is used to connect a remote panel to a 4100 system with a contact closure output. A supervisory/trouble condition (abnormal state) indicates that the remote panel is in trouble, while an open circuit trouble indicates that the wiring used to connect the two panels has failed. This point type has a FIRE/SUPV MONITOR banner and maps physical and logical states as shown in Table 7. Table 7. GENFS Point Type Physical/Logical States Physical State Logical State Status Message Normal Normal NORMAL Abnormal Supervisory SUPERVISORY\TROUBLE Open Circuit Trouble OPEN CKT TROUBLE Short Circuit Fire FIRE ALARM This point type may be programmed on any tri-state monitor point on any eightzone monitor card. This point type is not supported on the 24 I/O or Mapnet cards. The 4100 Programmer auto-generates this point into the same lists as a WSO point. The fire state latches until the zone is restored to normal and a system reset is performed. The supervisory state clears immediately when the zone is restored to normal. 16

20 Computer Port Protocol The 4100 computer port protocol has several enhancements with the release of Version 8. These enhancements are supplied to permit nearly every operation allowed from the front panel of the These enhancements include viewing and clearing of the historical logs, network diagnostic capability, Walk Test, etc. These enhancements require Version 8 of the master/programmer software and Revision 2.01 or later of the RS232 Interface firmware. When referring to commands, the asterisk (*) is a marker of the minimum amount of characters needed to execute a command. For example, SH*OW. The letters 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 than what 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. A time delay allows the screen to be paused for no more than 30 seconds. Unsolicited output is allowed only after the command has completed all output applicable. Without the "/P", text will scroll off the screen when screen fills up. SHOW Command The SHOW command has two different input formats: SHOW <point> and SHOW <keyword>. SHOW Point This command followed by a point ID is the equivalent of using the FUNCTION button on the front panel. It is a way of outputting to the computer port information about a point other than just the point s status. The SHOW <point> form has only one 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 or address format. Example: SHOW ZN1<CR> MONITOR ZONE CUSTOM LABEL ZN1 PULL STATION POINT ADDRESS: ZONE CLASS B MONITOR CARD Local Unit - Main Panel Continued on next page 17

21 Computer Port Protocol, Continued SHOW Command (continued) UNIT NUMBER: 0 RUI NUMBER: LOCAL PRIMARY STATUS ALARM PHYSICAL STATE SHORT RAW STATE SHORT ACTIVE STATE ON ARMED STATE ARMED ENABLED STATE ENABLED UNVERIFIED 0 SHOW Keyword The SHOW command followed by a valid keyword outputs information to the computer port appropriate to the keyword. The keywords are listed below. PORTS - Outputs a list of all ports configured and their device types. When no ports are present, a No Ports Configured message is returned. TOPOLOGY - Identical to the loop topology line of the DIAGNOSTIC command without an argument. If there are no nodes, a No network card configured message is returned. NODES - Outputs a listing of all nodes in the network showing the node number, 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. 18

22 Computer Port Protocol, Continued LIST Command This command returns the current logical point status for the point requested in an easy-to-read format. The output format is a single line per reported status formatted as follows: ZONE, CUSTOM LABEL, POINT BANNER, STATUS. If ACK is needed, the STATUS is followed by an asterisk. The four methods of input for the LIST command are shown below. L*IST <point> - This command followed by only a point ID outputs one line for each abnormal/on status for the point. L*IST <point> [qualifier] - This command followed by both a point ID and a qualifier outputs only one line for the status described by the qualifier. The following is a list of qualifiers. A - Primary F - Fire P - Pri2 S - Supervisory T - Trouble U - Utility C - Control D - Disable trouble L*IST [qualifier]- This command followed immediately by a qualifier outputs 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 each abnormal/on status for each point in the system. PRINT Command This command causes reports to be output via the currently selected reports printer in the same manner as is now possible via the front panel or the CRT menus. 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. Continued on next page 19

23 Computer Port Protocol, Continued TYPE Command This command causes reports to be output via the currently selected reports printer in the same manner as is now possible via the front panel or the CRT menus. 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 prompts you for further instructions from the CRT menus. SELECT Command This command allows you to select a report printer. Typing "SELECT" by itself returns a list of printers available each with its device type. If no printers are configured, the message "No printers configured" is returned. The currently selected report printer is denoted by an asterisk. Typing "SELECT" followed by a number from 1 to 5 changes the currently selected printer to the port number chosen. If an invalid port number is typed, an error message is returned. CLEAR Command This command clears the Alarm Historical Log or the Trouble Historical Log depending on the argument passed. In order to execute this command, it is necessary to be logged in. An access level of 3 is required by default, but can be changed by the programmer. If an error occurs on the input line, an appropriate error message is returned. CLEAR ALOG - CLEAR TLOG - Clears the Alarm Historical Log. Clears the Trouble Historical Log. CLEAR TALLY <point identification> - Clears the Alarm Verification Tally for the point specified. CLEAR PEAK <point identification> - Clears the Peak Analog Value for the point specified. Continued on next page 20

24 Computer Port Protocol, Continued WALKTEST Command 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 can be 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 status for the group specified. If an invalid group number is entered, an appropriate error message is returned. If any qualifier is omitted in the command line, the current value remains in effect. Qualifiers are evaluated from left to right. If conflicting qualifiers are input, the right most qualifier is the one remaining in effect. Table 7. Walk Test Qualifiers Qualifier ON OFF LOG NOLOG ZONE ZERO SIG NOSIG Description Initiates Walk Test Terminates Walk Test Causes Walk Test events to be logged Terminates Walk Test event logging Enables zone / disables zero coding during Walk Test Enables zero / disables zone coding during Walk Test Enables audible signal during Walk Test Disables signal during Walk Test Example: WALK 1 ON<CR> initiates Walk Test on group 1. Command Error Codes When issuing commands to the computer port, error conditions may exist that cause an 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 21

25 Custom Control Examples This section shows Custom Control programming examples for the 4-20mA ZAM and the VESDA devices. These are common applications to be used as reference only. 4-20mA ZAM Custom Control 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 each AMZ point. It is not true for each time the AMZ reaches an alarm threshold. ANALOG VALUE The value in engineering units of the AMZ point may be used as input to custom control 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: Continued on next page 22

26 Custom Control Examples, Continued 4-20mA ZAM Custom Control (continued) AMZ THRESHOLD With Version 8 a new Custom Control input qualifier for AMZ points exists. It is called 'AMZ THRESHOLD'. It is used in the same manner as 'SMOKE LEVEL' is used today, except user defined levels are assigned to the AMZ points. Following is an example of a Custom Control equation using the AMZ threshold as an 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 LED modes are applicable for these points. If it is desired to track the level of the AMZ point through LEDs, Custom Control can be written to have a pseudo track the desired 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 control the LED. Note: When an AMZ point is disabled, no 'SENSOR TROUBLE' will come in from the device, (for example, the sensor is being calibrated), and power is not removed from the device. Continued on next page 23

27 Custom Control Examples, Continued 4-20mA ZAM Custom Control (continued) A PROGRAMMING EXAMPLE Some sensors have an analog range denoting discrete occurrences. For instance, a flame detector may report a trouble by sending a value of 5 ma, a detection of infrared by a value of 10 ma, detection of UV by a value of 15 ma, and a detection of infrared and UV by a value of 20 ma. Custom programming would be required 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 Continued on next page 24

28 Custom Control Examples, Continued 4-20mA ZAM Custom Control (continued) 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: Continued on next page 25

29 Custom Control Examples, Continued 4-20mA ZAM Custom Control (continued) 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: 26

30 Custom Control Examples, Continued VESDA Custom Control This section contains some sample Custom Control equations that could help provide some flexibility in configuring the VESDA devices within the Two issues are addressed. Customizing logical states associated with the alert, action and fire states of the VESDA detector Providing a redundant detection system without having to annunciate duplicate alarm conditions CUSTOMIZED LOGICAL STATES In order to provide customized logical states for a VESDA device, the following steps must be taken. 1. Configure device with a point type of S3UTIL 2. Reserve three digital pseudo points and configure them to provide the desired logical state 3. 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 device to map to Supervisory, Priority 2 alarm, and Fire alarm respectively. Assume the VESDA device is addressed as M 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 VESDA detector being customized. 4. Write three custom control equations (shown below) so the pseudos track the logical state of the VESDA device and cause Supervisory, Priority 2 and Fire conditions when appropriate. 5. Insert the three digital pseudos into L73 (CONTROL POINTS OFF - ON SYSTEM RESET) so that the points turn off on a successful system reset. Continued on next page 27

31 Custom Control Examples, Continued VESDA Custom Control (continued) 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: Continued on next page 28

32 Custom Control Examples, Continued VESDA Custom Control (continued) REDUNDANCY WITHOUT DUPLICATE ALARMS To provide a redundant detection system without creating duplicate alarms in the FACP, follow these steps: 1. Configure the redundant GENIAM device as a utility device. 2. Reserve a digital pseudo to annunciate the abnormal condition when the primary means of alarm detection fails. 3. Write custom control equations to turn on the pseudo points when the primary means of detection fails and a threshold level has been crossed. Example An application requires that a redundant means of alarm detection is present for a VESDA device. Duplicate alarm conditions are not permitted. Assume VESDA device is addressed as M1-1 and the GENIAM device is addressed as M Configure M1-1 with point type S3MOKE. 2. Configure M2-1 with point type UTILITY (device is monitoring the fire threshold 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 VESDA detector being backed up with redundant system. 6. Write a custom control equation so the pseudo tracks the logical state of the VESDA 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-1 DELAY 5 [END-OF-INPUTS] OUTPUTS: TRACK ON PRI= 9,9 P256 FIRE [END-OF-OUTPUTS] END: 29

33 Index A Add an Interface Card 4 Adding a 4-20mA ZAM 12 Adding the SDACT 3 AMZ 10, 11, 22, 23, 24, 25, 26 Analog Value 22 ANAMON Point type 14 C Card Configuration Editor 4 CLEAR Command 20 Command Error Codes 21 Computer Port 1, 17, 18, 19, 20, 21 Customized Logical States 27 R Redundancy without Duplicate Alarms 29 S SDACT Interface Card Data Entry 5 SDACT Programmer 3 SDUCT 15 SELECT Command 20 Serial DACT 1, 4, 5 SHOW Command 17, 18 STYLEC Point Type 15 Switch Modes 23 System Configuration Menu 3 G GENFS Point Type 16 GENPRI2 Point Type 16 I Infrared and UV Detection Custom Control 26 Infrared Detection Custom Control 26 L LED MODES 23 LIST Command 19 P T TYPE Command 20 U UV Detection Custom Control 26 V VESDA 1, 6, 7, 8, 9, 22, 27, 28, 29 VESDA Configuration 9 W WALKTEST Command 21 PRINT Command 19 30