Binary Input (BI) Object

Transcription

1 Metasys etwork Technical Manual 636 Objects Section Technical Bulletin Issue Date 1199 Binary Input (BI) Object Introduction Page 3 Quick Start *3 Engineering Overview 9 Overview of Operation *9 Hardware Interface *12 Input Processing *23 Triggers and History *38 Reference Tables 43 BI Attribute Table *43 BI Command Table *53 * Indicates those sections where changes have occurred since the last printing 1999 Johnson Controls, Inc. 1 Code o. LIT

2 2 Objects Binary Input (BI) Object

3 Introduction A Binary Input (BI) object is the software representation of a hardware sensor that is monitoring a 2-state (on/off) field condition. The primary function of a BI object is to convert the raw hardware signal (i.e., changes in contact condition) from a binary input device to data that can be used in operator displays, alarm analysis, and control processes. Typical applications for a BI object include a water flow switch, a filter differential pressure switch, a level switch, auxiliary contacts from a chiller control panel, a motion detector, and a door switch. Quick Start Defining the BI This section tells you how to quickly define the BI from the Operator Workstation. Since most of the fields in the Definition window are already filled in with default values, all you need to do is fill in the fields without defaults, and make any necessary changes. The BI object can be defined: online, using the Operator Workstation BI Object Definition window. See the Operator Workstation User s Manual (FA 634) for instructions. offline, using the Graphic Programming Language (GPL) Database Template. See the GPL Programmer s Manual (FA 631) for instructions. offline, using the Data Definition Language (DDL). See the DDL Programmer s Manual (FA 630) for instructions. To define a BI object online at the workstation: 1. Go to the summary of the system in which you want to add the object. 2. Select Item from the Menu bar. Then select ew from the Item menu. A dialog box for selecting object type appears. 3. Select Binary Input from the list of object types. Then, in the Hardware System and Hardware Object fields, type the system/object name of the device the BI object will be mapped to. This must be an already defined device. (If the device is not defined, you must define it before you define the BI. See the device s technical bulletin for more information.) 4. Click OK. The Binary Input (XM) Definition window appears (as shown in Figure 1). Objects Binary Input (BI) Object 3

4 Binary Input (XM) Definition Help BLDG-1 AHU-1 AHU-1 System ame Object ame Expanded ID AHU-1 Comm. Disabled Graphic Symbol # Operating Instr. # 0 0 Hardware: XB, XRM, XRL System ame C5 Object ame XB1 Point Type SIGLE 1 Slot umber 24 Debounce Filter Y LED On when Relay Closed Flags Auto Dialout Enable PT History Save PT History Latching Point Y Parameters ormal State OE Alarm Delay (sec) 30 Alarm Delay Active Y Delay All Alarms Engineering Data State 0 (STOP) units State 1 (START) units off on Report Type ORMAL ALARM OVERRIDE OE OE OE Messages ALARM # 0 bieng1 Figure 1: BI Input (XM) Definition Window Displaying Default Settings ote that some of the fields are blank and some are already filled in. You must fill in the blank attribute fields (e.g., Object ame) because they do not have default settings. The attribute fields that are already filled in contain default settings, which you can either accept or change. Table 1 explains the attributes without default settings. Table 3 describes all BI object attributes. The Operator Workstation User s Manual (FA 634) tells you how to enter and change data. 4 Objects Binary Input (BI) Object

5 Table 1: Attributes without Default Settings Attribute Label Description Entry System ame Object ame Expanded ID (optional) H/W System ame H/W Object ame Has to be the name of an existing system, such as AHU_1 or AIR_SYS. When using GPL or DDL, you must define the System ame. When using the BI Object Definition window, the System ame contains a default setting. The object name cannot already exist under the given system name. This name defines the object, such as AIR_FLOW (for air flow switch). This is an expanded version of the object name. Appears at the Object Focus window, GPL template, and summaries. More clearly identifies the object. For example, AIR FLOW SWITCH. Must be the name of an existing DCM, DCM140, XM, ASC, System 9100 Controller, LOWORKS compatible device, IAC-600, DSC8500, or FPU System ame. Must be the name of an existing DCM, DCM140, XM, ASC, System 9100 Controller, LOWORKS compatible device, IAC-600, DSC8500, or FPU Object ame. Once the H/W System ame and Object ame are entered, the Definition window will display the appropriate default values in the remaining H/W fields, including Point Type, Slot umber, Subslot, Debounce Filter, and LED On. 8 alphanumeric characters 8 alphanumeric characters 24 alphanumeric characters 8 alphanumeric characters 8 alphanumeric characters 5. To save the new BI object, select Item from the Menu bar. Then select Save. The new BI object is added to the operational database in the etwork Controller (C). Objects Binary Input (BI) Object 5

6 GPL Template Default attribute settings are also available in the GPL template. Figure 2 shows the GPL Database Template for the BI object. BIARY IPUT OBJECT (BI) IDETIFICATIO EGIEERIG DATA System ame = State 0 Units = OFF Object ame = State 1 Units = O Expanded ID = HARDWARE System ame Object ame H/W Type Slot umber Point Type Debounce Filter LED On When Relay CLO = = = = = = = DCM 1 BI 2 sec Y F10 - SAVE, ESC/mouse click - CACEL, PGD - PAGE BIARY IPUT OBJECT (BI) FLAGS REPORT TYPE Auto Dialout = ormal = OE Enable PT History = Y Alarm = OE Save PT History = Override = OE Comm Disabled = Latching Point = MESSAGES PARAMETERS ormal State Alarm Delay = = OE 30 sec Alarm # = Graphic Symbol # = Operating Instr. # = F10 - SAVE, ESC/mouse click - CACEL, PGUP - PAGE bieng2 Figure 2: BI GPL Database Template Displaying Default Settings 6 Objects Binary Input (BI) Object

7 Modifying and Monitoring the BI Once the BI is defined, you can modify its attributes using the BI Focus window. You also use the Focus window to monitor and command the BI. You ll find information on using Focus windows in the Operator Workstation User s Manual (FA 634). You can modify the BI object: online, using the Operator Workstation BI Object Focus window offline, using the Graphic Programming Language (GPL) Database Template offline, using the Data Definition Language (DDL) This is the end of the Quick Start section. If you need more information on data entry procedures, see the Operator Workstation User s Manual (FA 634) and GPL Programmer s Manual (FA 631). For additional information on BI attributes, see the remainder of this document, which explains the relationship between various BI attributes from an applications perspective. In addition, you ll find an alphabetized listing of all BI attributes and commands (with descriptions and acceptable entries) at the end of this document. ote: Refer to the Control System (CS) Object Technical Bulletin (LIT ) for corresponding point mapping tables. Objects Binary Input (BI) Object 7

8 8 Objects Binary Input (BI) Object

9 Engineering Overview Overview of Operation Functional Flow Diagram BI software functions can be divided into four basic categories: Hardware Interface--A binary input device, such as a switch, is connected to one of the following hardware devices: Digital Control Module (DCM101 or DCM140), Point Multiplex Module (XM), 2OPE Application Specific Controller (AHU, UT, VAV, VMA, PHX, MIG, VD), System 9100 Controller (LCP, DX9100, DX91ECH, DC9100, DR9100, TC9100, XT9100, XTM), LOWORKS Device (LOTCU, LOTCUA, LOVMA, LOVMAA), Access Control System (IAC-600), FPU, or DSC8500. The device, in turn, is connected to the etwork Control Module through the 2 or S2 Bus. When the input device physically changes state (e.g., switching from an open to a closed condition), this information is detected by the hardware. ote: LOWORKS Devices LOTCUA and LOVMAA apply to American sites only. All other sites use LOTCU and LOVMA. Input Processing--The hardware input is processed by software functions, such as the debounce filter and Override command. Alarm Analysis--The BI current value is compared against a user-defined normal state to determine the object s ormal or Alarm status. A BI mapped to an 2OPE device that supports Trouble, or FPU BIF101, BIS101, or SST102 point modules, also has Trouble status, determined by supervised monitoring of the device circuit. The status (a COS [Change-of-State] report) and associated message is routed to operator devices. Triggers and History--BI attribute changes can be used for other purposes, including triggering control processes and historical archiving. Figure 3 illustrates the general operation of a BI object. The blocks represent the functions performed by the software. Each major block is summarized after the figure and explained in detail in this document. Objects Binary Input (BI) Object 9

10 Hardware Input Hardware Interface Debounce Filter Override Command Current Value Point History Alarm Analysis Control Process Triggering Alarm Delay Latch Function Change-of-State Reporting bieng3 Figure 3: Binary Input Functional Flow Diagram Hardware Interface Hardware Input--A binary input device, such as a switch, changes state, (e.g., switching from an open to closed contact condition.) This contact change is sensed by the XM, DCM, DCM140, 2OPE ASC, System 9100 Controller, IAC-600, DSC8500, or FPU. On a LOWORKS compatible device, the hardware input is a etwork Variable (V) in the device. Input Processing Debounce Filter--XM, DCM, and DCM140 only. Changes resulting from fluttering of contacts or process noise may be ignored by using a debounce filter. The filter is actually a time period set in software. The BI contact value is read only after this period has lapsed. 10 Objects Binary Input (BI) Object

11 Override Command--You can issue a manual Override command from an Operator Workstation (OWS). If you override the BI, you tell the system to ignore the actual physical open/closed condition of the object. The software will treat the BI as though it is in the state specified by the Override. Software processing of the Override command occurs at the etwork Control Module (CM). (ot available for BIs mapped to System 9100 or LOWORKS compatible devices.) Current Value--The BI current contact value becomes either: the data coming in from the field, filtered or unfiltered; or the value set with an Override command. Alarm Analysis Alarm Analysis--You may define a ormal State (attribute) for the binary input during database generation. Alarm analysis compares the BI contact value against the user-defined ormal State. (If the BI is used as feedback for a BO, the BO can also alter the ormal State attribute of the BI.) For BIs mapped to 2OPE devices that support Trouble, or FPU BIF101, BIS101, or SST102 point modules, supervised monitoring detects when the device circuit is abnormal and flags the status as Trouble. Alarm Delay--This function delays alarm reporting of the BI object for a user-specified period of time. The purpose of alarm delay is to prevent nuisance reports that could result from a BI current value change when the BI object is used as feedback for a BO object, or when the source value of the BI comes from a contact that may change its state either momentarily or several times before settling to the new condition (flutter contact). The alarm delay is not activated by an Override command from an operator to the BI object. See the Binary Output (BO) Object Technical Bulletin (LIT ) in the Metasys etwork Technical Manual (FA 636) for information on feedback. Latch Function--This function causes the BI object to stay in Alarm or Trouble once it changes to an Alarm or Trouble state. (The latching of the Trouble state applies only to BIs mapped to FPU BIF101 point modules.) Latching ensures that BI Alarm or Trouble states are acted upon by an operator or control process before the object returns to a normal state. Only an Unlatch command from an operator or control process can release the latched state. In the case of a BI mapped to an FPU BIF101, the Unlatch command is sent to the hardware. Change-of-State (COS) Reporting--If an alarm is detected, it may be reported at one or more Operator Workstations or printers. Operator Workstations and printers only receive the alarm report if they were defined as report destinations for that particular report type during the database generation process. Objects Binary Input (BI) Object 11

12 Triggers and History Control Process Triggering--An Alarm condition and other attribute changes can trigger (cause) a control process to run. Point History--Attributes of the BI object may be sent to a point history file. Hardware Interface The BI can map to the following hardware devices: DCM, DCM140, 2OPE ASCs (AHU, UT, VAV, VMA, MIG, PHX, VD), System 9100 Controller (LCP, DX9100, DX91ECH, DC9100, DR9100, TC9100, XT9100, XTM), LOWORKS compatible device (LOTCU, LOTCUA, LOVMA, LOVMAA), Smart Terminal Interface (IAC-600 system), FPU, and DSC8500. ote: LOWORKS compatible devices LOTCUA and LOVMAA apply to American sites only. All other sites use LOTCU and LOVMA. Mapping means: The binary input device is connected to a specific place on a specific controller. This place is referenced in software so that the BI object knows where to receive input signals. Figure 4 is a flow diagram of BI hardware interface. The blocks represent software functions. The dashed boxes represent the attributes that define or control the functions. 12 Objects Binary Input (BI) Object

13 Function Attribute Hardware Input Hardware System ame HVAC Application Specific Controller Point Type Point Address XM Hardware Object ame Slot umber LED On When Relay Closed IAC-600 Access Control System RDR umber BI Point Input Type System 9100 or LOWORKS Controller Point Type Hardware Reference Hardware Interface PT Enabled FPU Slot umber Binary Type Slot umber DCM and DCM140 LED On When Relay Closed Point Type DSC8500 Logical Point Type Logical Point umber bieng4 Figure 4: Binary Input Hardware Interface This section explains the attributes you ll use to establish the hardware interface between the BI and the appropriate device. The following two attributes, Hardware System ame and Hardware Object ame, are common to all devices: Hardware System ame must be of an existing system, such as C5. It might represent the control panel or etwork Control Module that s handling the BI. Hardware Object ame is the name of the hardware object (e.g., the name of the XM, DCM, DCM140, ASC, IAC-600, DSC8500, or FPU) that the object is mapped to. This object must be already defined. If it is not defined, define it before you define the BI. The remaining hardware interface attributes depend on which type of device you specify for the Hardware Object. For example, if you specify a DCM, the Slot umber attribute is applicable. If you specify a DSC8500, Logical Point Type and Logical Point umber attributes are applicable. Objects Binary Input (BI) Object 13

14 Mapping to a DCM and DCM140 A BI maps to any one of the ten universal inputs on the Digital Control Module (DCM101 and DCM140). (If an IB is used, 20 BIs can be mapped to the 10 universal inputs on the DCM.) ote: For the BI object, the DCM101 and DCM140 operate the same. Therefore, in this section, DCM indicates both DCM101 and DCM140. The DCM reads the BI hardware input, debounces filtering, and determines the current contact value of the BI. This contact value is then sent to the CM where alarm analysis, report routing, triggering, and historical data gathering take place. An Input Function Module (FM) provides the interface between the binary input and DCM. Each FM accepts one input, except for the IB FM, which accepts two inputs. See the Control Modules and Function Modules sections of this manual for additional DCM and FM information. Attributes Linking the DCM and the BI Object Besides the Hardware System and Object names, four attributes link the BI and the DCM: Point Type Slot umber Subslot umber LED On When Relay Closed Point Type identifies the type of FM used by the DCM. Enter BI for a single input FM. Enter MBI for a double input FM. The default is BI. An IB FM accepts two binary inputs. All other FMs accept only one. Slot umber represents the Function Module slot (1 through 10) where the BI device is connected. The BI is actually wired to a terminal on the terminal strips. This terminal is electrically connected to a specific FM slot. Enter a value from 1 to 10. The default is 1. Subslot umber only applies if the BI is connected to an IB Function Module at the DCM. An IB Function Module accepts two binary inputs. The subslot numbers (1 and 2) represent the two inputs on the IB. (Both 1 and 2 reside in the same FM slot.) The default setting is 1. LED On When Relay Closed determines if the input Light-Emitting Diode (LED) of the DCM is on or off when the BI relay is closed. Enter Y (yes) if you want the LED on when the relay is closed. Enter (no) if you want the LED off when the relay is closed. The default setting is Y (yes). This attribute setting does not apply when the BI is connected to an IB Function Module. The IB contains its own two LEDs, which are On when the relay is closed. 14 Objects Binary Input (BI) Object

15 Mapping to an XM A BI maps to any of the: 32 inputs on the XB Point Multiplex Module 8 inputs on the XRM Point Multiplex Module 8 inputs on the XRL Point Multiplex Module 8 inputs on the XRE Point Multiplex Module ote: An XRE is defined as an XRL. Point Multiplex Modules (XMs) read the BI hardware input, perform debounce filtering, and determine the current contact value of the Binary Input. This contact value is then sent to the etwork Control Module where alarm analysis, report routing, triggering, and historical data gathering take place. XMs in Slots 1 and 5 of a 5-slot CM, and in Slot 1 of a 2-slot CM, require Function Modules (FM). Otherwise, XMs do not require Function Modules. If FMs are not used, the binary input devices connect directly to XMs via terminal strips on the CU or EU. For further hardware information, see the Control Modules and Function Modules sections of this manual. Attributes Linking the BI and XM Besides Hardware System and Object names, three attributes link the BI and XM: Point Type Slot umber LED On When Relay Closed Point Type signifies the type of contact. Enter Single for a single input, Form A contact. Enter Formc for a double input, Form C contact. The default setting is Single. Slot umber represents the input address (terminal strip location) where the BI is connected. For the XB, enter For the XRM, XRL, or XRE, enter 1-8. The default setting is 1. (If an IU Function Module is required, the slot number represents one of the two FM subslots.) LED On When Relay Closed determines if the input LED (of the XM) is on or off when the BI relay is closed. Enter Y (yes) if you want the LED on when the relay is closed. Enter (no) if you want the LED off when the relay is closed. The default setting is Y (yes). This attribute setting does not apply when the BI is connected to an IB Function Module. The IB contains its own two LEDs, which are on when the relay is closed. Objects Binary Input (BI) Object 15

16 Mapping to 2OPE ASCs BI objects can map to the following 2OPE Application Specific Controllers: AHU, UT, VAV, VMA, MIG, PHX, and VD. Attributes Linking the BI Object and the 2OPE ASC Besides the Hardware System and Object ames, two attributes link the BI object and the 2OPE ASC: Point Type Point Address Point Type identifies the type of point in the controller the BI is mapped to. It must be a Binary Input (BI) point. Point Address specifies the address of the BI point in the controller that the BI will map to. The range depends on the type of ASC the BI is mapped to: AHU: BI 1 to 8 UT: BI 1 to 12 VAV: BI 1 to 12 VMA:BI 1 to 3 MIG: 1 to 256 PHX: 1 to 37 VD: 1 to 256 IMPORTAT: If you are mapping a CS object attribute and a standard object to the same hardware reference (the hardware reference is the combination of the point type and point address), make sure the Override and Adjust flags are set to o (False) for the CS object attribute. This is to ensure that there is only one command path to the hardware reference. Mapping to a System 9100 Controller BI objects can map to System 9100 Application Specific Controllers (LCP, DX9100, DX91ECH, DC9100, DR9100, TC9100, XT9100, XTM). ote: A BI can map to a System 9100 Controller that is connected to a Fire or Access CM200. However, a BI cannot map to a System 9100 Controller that is connected to a Fire CM101. A System 9100 CM101 does not support the TC9100. The Echelon 2E Bus version of the DX controller (DX91ECH) must be connected to an CM300 or CM Objects Binary Input (BI) Object

17 Attributes Linking the BI Object and the System 9100 Controller Besides the Hardware System and Object ames, two attributes link the BI object and the System 9100 Controller: Hardware Device Type Hardware Reference Hardware Device Type identifies the type of System 9100 Controller the BI is mapped to. The options are LCP, DX9100, DX91ECH, DC9100, DR9100, TC9100, XT9100, and XTM. Hardware Reference specifies the address of the point in the controller the BI is mapped to. The range depends on the type of System 9100 Controller. Valid System 9100 device types and hardware references are: LCP\DC9100 DI1-8, LCM1-4 DX9100 DI1-8, LRS1-32, XT1-8DI1-8 DX91ECH DI1-8, LRS1-64, XT1-8DI1-8 DR9100 WI, OCC, AIRQ TC9100 WI, OCC, AIRQ, ALM, AFM, L1A, L3A XT9100 1DI1-8, 2DI1-8 XTM 1DI1-8, 2DI1-8 Mapping to a LOWORKS Compatible Device BI objects can map to LOWORKS devices. ote: LOWORKS devices must be connected to a CM350. Attributes Linking the BI Object and the LOWORKS Compatible Device Besides the Hardware System and Object ames, two attributes link the BI object and the LOWORKS compatible device: Hardware Device Type Hardware Reference Hardware Device Type identifies the type of LOWORKS compatible device the BI is mapped to. At present, device types include LOTCU, LOTCUA, LOVMA, and LOVMAA. ote: LOWORKS compatible devices LOTCUA and LOVMAA apply to American sites only. All other sites use LOTCU and LOVMA. Objects Binary Input (BI) Object 17

18 Hardware Reference specifies the address of the point in the controller the BI is mapped to. The range depends on the type of LOWORKS device. Valid LOWORKS compatible device hardware references are: xxbixxx (the xs are placeholders for specific addressing numbers and characters; see the device s technical bulletin for details) Mapping to an IAC-600 Access Control System BI objects can map to an IAC-600 Access Control System. More specifically, a BI object represents a binary alarm point circuit located within a Smart Terminal Interface (STI). ote: Before defining BI objects, you should be familiar with the main components of the IAC-600 system and how they function (i.e., D600 Controller, STIs, card readers, and binary inputs). Each STI has eight binary input circuits. These eight circuits monitor any type of alarm detector that provides a normally closed dry contact that opens to indicate an Alarm state. While input points are typically used for alarm detectors, they can also be used to monitor status changes for any device that provides a normally closed, dry contact output. For more information about STIs and Card Reader objects, refer to the Access Control System Objects Technical Bulletin (LIT ) in the Metasys etwork Technical Manual (FA 636). 18 Objects Binary Input (BI) Object

19 Attributes Linking the BI Object and the IAC-600 System Besides the Hardware System and Object ames, four attributes link the BI object to an STI. For information on other IAC-600 system attributes, see the Alarm Analysis section of this document. RDR umber BI Point umber Input Type PT Enabled RDR umber identifies the STI/card reader for which you wish to define this binary alarm point. The range is 1 to 16. The number you enter corresponds to the physical connection of the STI to the D600 Controller (i.e., 1 to 8 on MTI Board 1, 9 to 16 on MTI Board 2). BI Point umber identifies the terminal in the STI that the binary input circuit connects to. The range is 1 to 8. Input Point 1 at each STI is factory set for use as a door open detector because it works in conjunction with the Access Timer, Alarm Shunt Delay, and the Anti-Tailgate Check attributes of the Card Reader object. ote that if you wish to use Input Point 1 for any other purpose, an abnormal COS at that input point still generates a Door Open report. In addition, if you use this input point for other uses, be sure the Card Reader object s Alarm Shunt Delay attribute is set to zero, and its facility code on Backup attribute is set to o. Input Point 2 at each STI is factory terminated to the tamper switch of the STI enclosure. However, Input Point 2 is not different than Input Points 3 to 8, and may be used for any other purpose if an enclosure tamper is not required. Input Points 3 to 8 are intended for general purpose alarm detection. Input Type identifies the type of input--2-state. This attribute is predefined and cannot be changed. PT Enabled identifies whether the binary alarm point is recognized (enabled) or ignored (disabled) by the D600 Controller. Once enabled (Y), the binary alarm point status changes are always reported to the D600 Controller unless you use a time zone to suppress it. The settings for this attribute are Y (enabled) or (disabled). For a definition of an Alarm Suppression Time Zone, see the Alarm Analysis section of this document. Objects Binary Input (BI) Object 19

20 Mapping to an FPU BI objects can map to an FPU. More specifically, a BI object represents one of the following binary point contacts in the FPU: BI101, BIF101, BIS101, SST101, or SST102. Attributes Linking the BI Object and the FPU Besides the Hardware System and Object ames, two attributes link the BI and FPU: Slot umber Binary Type Slot umber identifies the input address on the FPU where the field device is connected. The range is Binary Type specifies the type of contact in the FPU. The Binary Type can be BI101, BIF101, BIS101, SST101, or SST102. If the Binary Type is BIF101, BIS101, or SST102, the object s ormal State attribute must be State 0. If the Binary Type is BIF101, the Latching Point attribute must be set to Y (yes) to accommodate supervised monitoring of the Alarm and Trouble state at the point module hardware. For more information, see the Supervised Monitoring and Trouble Status section, under Alarm Analysis, later in this document. Mapping to a DSC8500 BI objects can map to a DSC8500. ote: When using CAL1 to define a DSC8500 point that will be mapped to a Metasys etwork object, enable status reports to the Facility Management System (FMS) for the point. Conversely, if the point will not be mapped to a Metasys object, disable status reports to the FMS for the point. Attributes Linking the BI Object and the DSC8500 Besides the Hardware System and Object ames, two attributes link the BI object and the DSC8500: Logical Point Type Logical Point umber Logical Point Type identifies the type of point in the DSC8500 the BI will be mapped to. For the BI, the LPT can be BSP, BDP, CO, or MA. Logical Point umber identifies the number of the specified LPT on the DSC8500 where the field device is connected. The range is Objects Binary Input (BI) Object

21 Unreliable and Communication Status Unreliable Status The BI object may become unreliable due to an offline condition (communication break) or faulty field hardware. When the BI object is unreliable, the following attributes that are derived from the contact value also become unreliable: Current Value Status Display ASCII Representation Value ormal Status * Alarm Status * Trouble Status * * These attributes are hidden. They do not appear as fields at the BI Object Focus window or T display. However, you might use them in control process programming. Keep in mind that if these attributes become unreliable, they can affect the results of the control process. See Table 3 at the end of this document for additional information on these attributes. You can determine if a Binary Input is unreliable by looking at its Focus window or any summary containing information about the object. When the object is unreliable, the Current Value and Status attributes will display???? (question marks) rather than a value in the BI Focus window and in summaries. Figure 5 shows a Focus window for an unreliable, offline object. Communication Status The Comm. Status field in the object Focus window is used for both online/offline status and disconnect status. (Disconnect status applies to 2 Dialer Module (DM) applications only.) An object is offline when there is a communications break between the controller the object is mapped to and the CM or DM the controller is connected to. If an object is offline, OFFLIE appears in the Comm. Status field of the object s Focus window. Figure 5 shows a Focus window for an object that is offline and unreliable. In addition, an offline object appears in the Offline summary. In DM applications, if the remote DM is disconnected from the local DM, DISCOCT appears in the Comm. Status field. If the DMs are connected, either OLIE or OFFLIE appears in the field, depending on whether the controller the object is mapped to is online. Objects Binary Input (BI) Object 21

22 Binary Input (XM) Focus Item Edit View Action GoTo Accessory Help BLDG-1 AHU-1 SF-STS Supply Fan Status AHU-1 Point History Current Trend System ame Object ame Expanded ID Current Value???? AHU-1 SF-STS SUPPLY FA STATUS Reports Locked Trigger Locked Comm. Disabled Comm. Status S/W Override Status OFFLIE???? Graphic Symbol # Operating Instr. # 0 15 Hardware: XB, XRM, XRL System ame FLOOR1 Object ame BI1 Point Type SIGLE Slot umber 1 Debounce Filter 24 LED On when Y Relay Closed Flags Auto Dialout Save PT History Latching Point Alarm Latched Parameters ormal State Alarm Delay (sec) Delay All Alarms off 30 Engineering Data State 0 (STOP) units State 1 (START) units off on Report Type ORMAL ALARM OVERRIDE OE CRIT2 CRIT3 bieng5 Figure 5: Focus Window of an Offline, Unreliable Binary Input 22 Objects Binary Input (BI) Object

23 Input Processing The figure below is a flow diagram of BI object input processing. The blocks represent software functions. The dashed boxes represent the attributes that define or control the functions. Hardware Input Function DCM, DCM140, and XM Debounce Filter Debounce Filter Attribute Override command from operator Override Command Current Value Status S/W Override State 0 (Off) Units State 1 (On) Units Current Value Current Value Alarm Analysis bieng6 Figure 6: BI Input Processing Functional Flow Debounce Filter ote: The following information on debounce filtering applies only to a BI mapped to a DCM, DCM140, or XM. Mechanical contacts often bounce a few times when they close. This contact flutter can cause excessive alarm reporting. An optional software debounce filter function may be used to avoid analyzing these nuisance contact changes, and to prevent unnecessary communication traffic on the 2 Bus. The debounce filter is an attribute of the BI object that is set when the object is defined. You specify the debounce filter as a time period. Contact fluctuations are ignored and, thus, filtered during this time period. Objects Binary Input (BI) Object 23

24 Attributes to Set for Debounce Filter The Debounce Filter attribute affects the Debounce Filter function: Debounce Filter defines the period of time the software waits before reading the value of a fluttering (bouncing) contact. If the BI device is wired to a DCM or DCM140, enter the time period in seconds (1-255). If the BI is wired to an XM, enter the time period in milliseconds ( ), in multiples of 12 such as 12, 24, 36, and 48. ote: If you don t want to use a debounce filter, specify 1 second for the DCM/DCM140 or 12 milliseconds for the XM. How the Debounce Filter Works Debounce filter processing takes place at the DCM, DCM140, or XM, where the BI device is connected. Debouncing works as shown in Figure 7. Actual Contact Debounce Time Debounce Time bieng7 Filtered Output Figure 7: Debounce Filter Timing Diagram The debounce filter works as follows: 1. A Binary Input object is assigned a debounce filter time of, for example, 24 milliseconds. 2. When the contact changes state, the debounce timer starts. 3. The contact may be fluttering during the debounce time period of 24 milliseconds. The software ignores the contact value during this period. 4. When the debounce filter times out at 24 milliseconds, the contact value is read by the software. 5. This filtered contact reading becomes the current contact value of the BI object. This value is sent to the CM where alarm analysis occurs. 24 Objects Binary Input (BI) Object

25 Override Command The following information on the Override command and S/W Override attribute does not apply to a BI mapped to a System 9100 Controller or LOWORKS compatible device. Use the Override command to set the BI contact to a specific value, such as Opened, Closed, On, or Off. An Override command can be issued from an Operator Workstation Command Action menu (input objects cannot be overridden from the etwork Terminal). You might decide to execute an Override command if there is faulty or offline hardware, or if you want to simulate a field condition. For example, a device that s monitoring a filter may become defective and start generating nuisance changes-of-state. In this situation, you could issue an Override to force the contact to a closed (dirty) value. What Attributes Are Affected by the Override Command? Three attributes are affected by this command: Current Value Status S/W Override Current Value is updated to reflect the new contact value you specified with the Override command. This is displayed at the BI Focus window. For example, the Current Value field could show On, Off, Open, or Closed. Status is updated to reflect the results of alarm analysis. Alarm analysis occurs because you set a new Current Value with the Override command. The Current Value is compared against a user-defined ormal state. The new status is displayed at the BI Focus window. S/W Override is changed to Y to indicate that the object is software overridden. This is displayed at the BI Focus window. If the Override command hasn t been used, this field displays an. Figure 8 shows the Focus window of a BI object that has been overridden to a Current Value of Off. Objects Binary Input (BI) Object 25

26 Binary Input (XM) Focus Item Edit View Action GoTo Accessory Help BLDG-1 AHU-1 SF-STS Supply Fan Status AHU-1 Point History Current Trend System ame Object ame Expanded ID Current Value AHU-1 SF-STS SUPPLY FA STATUS OFF Reports Locked Trigger Locked Comm. Disabled Comm. Status S/W Override Status OLIE Y ORMAL Graphic Symbol # Operating Instr. # 0 15 Hardware: XB, XRM, XRL System ame FLOOR1 Object ame BI1 Point Type SIGLE Slot umber 1 Debounce Filter 24 LED On when Y Relay Closed Flags Auto Dialout Enable PT History Save PT History Latching Point Alarm Latched Parameters ormal State Alarm Delay (sec) Alarm Delay Active Delay All Alarms off Engineering Data State 0 (STOP) units State 1 (START) units off on Report Type ORMAL ALARM OVERRIDE OE CRIT2 CRIT3 bieng8 Figure 8: BI Focus Window Displaying Status and Current Value What Happens When an Override Command Is Executed? A contact change resulting from an Override command is always processed immediately. The Commanded state becomes the current contact value, taking priority over the field contact condition. An Override command will also cancel any alarm delay timing that may be in effect. While the BI object is in an Overridden state, the software continues to monitor the physical condition of the object. However, change-of-state reporting and control process triggering from these changes are suppressed. When the Override command is released with the Auto command, the last field change that had been reported to the etwork Control Module becomes the current contact value. 26 Objects Binary Input (BI) Object

27 Current Value The current contact value read by the software is either: the actual field contact condition (filtered or unfiltered) or the contact condition set with an operator Override command--this takes priority Attributes Associated with the Current Value Three attributes are associated with the Current Value: Current Value State 0 (Off) Units State 1 (On) Units Current Value is the attribute that represents the present condition of the object, such as On or Off. This attribute is not definable. State 0 (Off) Units are ASCII alphanumeric characters that are used to represent the open contact condition. The default setting is Off. State 1 (On) Units are ASCII alphanumeric characters that are used to represent the closed contact condition. The default setting is On. Enter up to six ASCII alphanumeric characters for each of the units above. Examples include On/Off, Open/Closed, Clean/Dirty, and so on. The BI Current Value is displayed as one of these two engineering units (e.g., Off or On) at the BI Focus window, T screen, and object summaries. Objects Binary Input (BI) Object 27

28 Alarm Analysis Figure 9 is a flow diagram of BI alarm analysis. The blocks represent software functions. The dashed boxes represent the attributes that define or control the functions. Function Current Value Attribute ormal State Alarm Analysis and Supervised Monitoring Status Delay All Alarms Alarm Delay Alarm Delay Active Latch Point Latch Function Status Alarm Latched Trouble Latched Alarm if Set Quiet if Reset Local Alarm Annunciation Status Report Type ormal Report Type Alarm Report Type Override Message Alarm # Change-of-State Reporting Reports Locked Auto Dial-Out Alarm Suppression Time Zone bieng9 Figure 9: BI Alarm Analysis Functional Flow 28 Objects Binary Input (BI) Object

29 Alarm analysis is a software process that compares the BI Current Value against a user-defined ormal State attribute. The purpose of alarm analysis is to determine the BI status. The status can be: ormal--the BI contact condition matches what has been user-defined as the ormal State. Alarm--The BI contact condition doesn t match what has been user-defined as normal. Trouble-- The BI contact is experiencing abnormality in the device circuit. This status only applies to BIs mapped to FPU BIF101, BIS101, or SST102 point modules, or to 2OPE devices that support Trouble. Attributes to Set for Alarm Analysis ormal State specifies the contact value that you consider normal (State 0, State 1, or one). If the BI is mapped to an FPU BIF101, BIS101, or SST102 point module, the object s ormal State attribute must be State 0. When you specify the ormal State, instead of State 0 or State 1, you use the units assigned to these states, such as On, Off, Clean, Dirty. The three entries for ormal State are explained below: State 0 (Off) or State 1(On) Units--When you define the BI, you set two attributes--state 0 and State 1--that define the open and closed physical condition of the contact. Possibly you named them Off and On, or Stop and Start. ow you are specifying which of these physical conditions is ormal. This creates two possible logical states for the BI: Alarm or ormal. (BIs mapped to devices that support supervised monitoring have an additional state, Trouble, which is explained in this section, under Supervised Monitoring and Trouble Status.) one--this means the BI is a status-only object. Although the current contact value, such as On or Off, is reported to operator devices, alarm analysis is not performed. The status is always shown as ormal in the Focus window and on summaries. For example, let s assume you have a normally open contact monitoring air flow across a filter. You set the State 0 Units to Clean, the State 1 Units to Dirty, and the ormal State to Clean. When the contact closes, the air flow switch is in the State 1 condition--dirty. Alarm analysis compares this condition (Dirty) to what you defined as normal, which is Clean. These values don t match, so the object is considered in Alarm. Objects Binary Input (BI) Object 29

30 When Does Alarm Analysis Occur? Alarm analysis begins when: The contact value changes due to a field change. A new value is received from an operator Override command. You modify the BI ormal State attribute at an object Focus window, through an associated BO object, or within a control process. ote: An associated BO changes the BI ormal State when the Binary Input object is used as feedback for the BO object. This is explained later. Supervised monitoring of an FPU BIF101, BIS101, or SST102 point module detects device circuit trouble. Supervised Monitoring and Trouble Status For BIs mapped to devices that support Trouble status (2OPE and FPU BIF101, BIS101, and SST102 point modules), three states are possible: ormal, Alarm, and Trouble. The Trouble state indicates a problem detected in the device circuit. ote: For information on how Alarm and Trouble states can trigger processes for BI objects mapped to devices that support Trouble status, see the Triggers and History section in this document. Metasys system support of supervised monitoring and Trouble status works as follows: Status of the object (Read, ormal, Alarm, or Trouble) is returned. If the BI object s status is Trouble, the object is displayed in the online Trouble summary. Trouble status is triggerable. The Trouble Report Type is the same as the Alarm Report Type defined for the BI. For example, if the Alarm Report Type is Follow-up for the BI, the Trouble Report Type is also Follow-up. The trouble message is the same as the alarm message defined for the BI. Metasys software is not UL 864 or UL 1076 Listed as a result of support of supervised monitoring. 30 Objects Binary Input (BI) Object

31 The following additional points apply to BIs mapped to FPU BIF101, BIS101, or SST102 point modules: In the case of the BIF101, the Alarm or Trouble status is latched at the hardware. Only an Unlatch command can release the Alarm or Trouble status. If latched into Trouble and an alarm occurs, the hardware latches into Alarm. For BIs mapped to BIF101 point modules, the Unlatch command is sent to the hardware. For BIs mapped to FPU BIF101, BIS101, or SST102 point modules, the ormal State attribute must be set to State 0. For BIs mapped to FPU BIF101 point modules, the Latching Point attribute must be set to Y (yes). Do not use BIs mapped to FPU BIF101, BIS101, or SST102 point modules as feedback for any BO. If you must use the SST102 as feedback, make sure the BI mapped to the SST102 has its latch flag set to o. For the BIS101, the Access/Secure JC/85/40 function can be implemented on a Metasys system using the Lock Reports command. Specifically, when reports are locked for the BI mapped to a BIS101, the BI functions similar to the Access mode of the JC/85/40. When reports are unlocked, the BI functions similarly to the Secure mode. Alarm Delay This function delays alarm reporting of the BI object for a user-specified period of time. The purpose of the alarm delay is to prevent nuisance reports that could result from a BI current value change when the BI object is used as feedback for a Binary Output object, or when mapped to flutter contact. The alarm delay timer is started when the BI ormal State attribute is modified by an associated BO object. When the Delay All Alarms attribute is set, the alarm delay timer is started whenever the BI current value changes from the normal to the Alarm state except when caused by an Override command to the BI object. ote: Alarm delay processing at the etwork Control Module is different than debounce filtering at the DCM, DCM140, or XM. The debounce filter eliminates mechanical contact fluctuations from being processed by the system at a very low level. Alarm delay timing eliminates a legitimate physical change from being considered an alarm--allowing a whole mechanical system to stabilize first. Alarm Delay When the BO is Mapped to a System 9100 Controller If the BO is mapped to a System 9100 Controller and the BO s Local Control attribute is set to yes, regardless of the commanding feature, the BI used as feedback has its alarm delay activated in two situations: when the BI receives a new ormal State from the BO, and when the BI changes state as a result of polling the hardware. Objects Binary Input (BI) Object 31

32 Attributes to Set for Alarm Delay The Alarm Delay attribute affects alarm delay. It specifies the time that the software will wait before issuing an Alarm COS report. You can specify a delay time of 0 to 255 seconds. The Delay All Alarms attribute specifies if the alarm delay function should be active for all COS transitions from the normal to the Alarm state except those caused by an Override command to the BI object. Alarm Delay Active Alarm Delay Active is an output flag indicating the delay timer is running. Since this is not a configuration parameter, the user cannot change it. Application Example of Alarm Delay An application for alarm delay is shown below. The BI object has been defined with an alarm delay time of 15 seconds. CM BO BO Object DCM, XM, ASC, FPU, or DSC8500 Starter BI BI Object Fan Status Pressure Switch bieng10 L H Figure 10: Application of BI Alarm Delay In this figure, there are two separate objects: a Binary Output (supply fan), and a Binary Input (air flow switch). Although these are two distinct objects, they work together to perform one function. The BO starts the fan. The BI monitors airflow in the duct after the fan starts. This is how it works: 1. When this BO was defined, a Feedback attribute was specified. This feedback represents the Binary Input object that s monitoring airflow in the duct. 2. The BO object issues a Start command to the fan. When this happens, the BI receives a new ormal State value from the BO. The ormal state was previously defined as Open. The BO now changes it to Closed (i.e., the air flow switch closes when the fan is commanded to start). 3. When the BO sends out the new BI ormal State, the BI alarm delay timer starts. Without the timer, the BI would immediately go into Alarm. 32 Objects Binary Input (BI) Object

33 4. After the alarm delay times out, the contact value of the BI is read by the software. 5. If the contact is closed, air is flowing, and the BI status is considered ormal. If the contact is open, air is not flowing, and the BI is in Alarm. Latch Function Latching is a function that causes the BI object to stay in Alarm (or Trouble) once it changes to an Alarm (or Trouble) condition. The purpose of Latching is to ensure that BI Alarm changes are acted upon by an operator or control process before the object returns to a ormal State. For a BI mapped to a BIF101 point module, the hardware itself is latched into Alarm or Trouble. Only an Unlatch command can release the latched hardware. ote: If a ormal State isn t defined for the BI, the object can t go into Alarm. (It s a status-only object.) Under these conditions, the Latch function has no meaning and is not operational. Attributes to Set for the Latch Function The Latching Point affects latching. Enter Y (yes) to make the BI object a latching point, or (no) to not. The default setting is o. If the BI is mapped to an FPU BIF101, the Latching Point attribute must be set to Y (yes). If the BI is mapped to an FPU BIS101, setting the Latching Point attribute to Y (yes) is optional. If the BI is mapped to an SST102, setting the Latching Point attribute to Y (yes) is not recommended. How the Latch Function Works If you define a BI object as a latching point, the following occurs when the Status attribute changes to Alarm or Trouble: The Status attribute is locked (latched) into Alarm. (In the case of a BI mapped to an FPU BIF101 point module, the status attribute will also latch into Trouble. If latched into Trouble and an Alarm occurs, the object will be latched into Alarm.) ote: This also means that the hidden attributes--ormal status, Alarm status, and Trouble status--are locked. The ormal status attribute is set to false and the Alarm status or Trouble status attribute is set to true. These attributes are considered hidden because they do not appear at the BI Object Focus or Definition windows. ormal status, Alarm status, and Trouble status are mentioned here because this information may be helpful for Troubleshooting or control process programming. Field changes, as well as Override commands, don t alter the Status, ormal Status, Alarm Status, and Trouble Status attributes. Objects Binary Input (BI) Object 33

34 The Current Value continues to update. o further Alarm analysis is performed (except in the case of a BIF101 latched into Trouble. If latched into Trouble and an Alarm occurs, the object will be latched into Alarm.) Unlatch Command Only an Unlatch command from an operator or control process can release the latched state. You can issue an Unlatch command at any time. However, the object s status will not return to ormal until the Current Value (contact value) changes to what is defined as ormal. See Figure 11. When a BI object is Unlatched, the following occurs: The Status, ormal Status, and Alarm or Trouble Status attributes are unlocked. Field changes and Override commands can alter the value of these attributes. In the case of a BI mapped to an FPU BIF101 point module, the unlatch command is sent to the hardware (as a Reset Latched Point command). Alarm analysis resumes. Operator Unlatch command has no effect. Operator Unlatch command has an effect because current value = user-defined normal state. Open Contact Current Value = Off Status = ormal Latch Status = o Current Value = On Status = Alarm Latch Status = Yes Current Value = Off Status = Alarm Latch Status = Yes Current Value = Off Status = ormal Latch Status = o Closed Contact ormal state is user-defined as Off. Operator Unlatch command has no effect. bieng11 Figure 11: Timing Diagram of the Latch Function Local Alarm Annunciation This function only applies to BI objects mapped to the IAC-600 Access Control System. When a binary input is set into alarm, you may also program a normally open relay on the D600 Controller main circuit board to be switched. If this relay is switched, a COS for the BI object is reported to Operator Workstations. This relay can also be used for sounding a bell or other types of annunciating devices. When the alarm is acknowledged, the bell is also silenced. 34 Objects Binary Input (BI) Object