A Sierra Monitor Company Driver Manual (Supplement to the FieldServer Instruction Manual) FS-8700-48 Fike Cheetah APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after August 2008 Driver Version: 1.
FS-8700-48 Fike Cheetah Manual Table of Contents TABLE OF CONTENTS 1. CHEETAH DEVICE DESCRIPTION................................................................................. 3 2. 2.1. 2.2. DRIVER SCOPE OF SUPPLY ......................................................................................... 4 Supplied by FieldServer Technologies for this driver.................................................. 4 Provided by Supplier of 3rd Party Equipment ..................................................
FS-8700-48 Fike Cheetah Manual 1. Page 3 of 36 Cheetah Device Description The Cheetah Protocol driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS-485 using the Cheetah device protocol. The Cheetah system provides fire detection/monitoring equipment and is manufactured by the Fike Corporation (www.fike.com). The driver is also able to be used with the newer Fike XI panel.
FS-8700-48 Fike Cheetah Manual 2. Page 4 of 36 Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies PART # FS-8915-10 FS-8700-48 2.2. Description Flat 6 way cable (7 foot) for RJ11 connection UTP cable (7 foot) for RS-232 use RJ45 to DB25F connector adapter RJ11 to DB25M connection adapter Driver Manual. Provided by Supplier of 3rd Party Equipment PART # DESCRIPTION Fike Cheetah panel and power supply. RS-485 cable, if required.
FS-8700-48 Fike Cheetah Manual 3. Page 5 of 36 Hardware Connections1 The FieldServer is connected to the Cheetah panel's Peripheral Port (see below). This port is either a serial port (identified as jack 4) or RS-485 port (use the terminals adjacent to jack 4). Configure the Cheetah Panel according to manufacturer’s instructions 3.1. RS-232 Connection to Fike Cheetah Panel 1 The connection diagrams are for Non Cybercat Panels.
FS-8700-48 Fike Cheetah Manual Pwr Run A ct Sy s RS-485 Connection to Fike Cheetah Panel C om 3.2. Page 6 of 36 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll Free: 888-509-1970 email: support@fieldserver.
FS-8700-48 Fike Cheetah Manual 3.3. Page 7 of 36 RS-485 Connection to Fike Cheetah XI Panel - FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll Free: 888-509-1970 email: support@fieldserver.
FS-8700-48 Fike Cheetah Manual 3.4. Page 8 of 36 RS-232 Connection to Fike Cheetah XI Panel CHEETAH XI PANEL P5 Terminal Block Pinouts RJ45 FieldServer Tx 8 Rx 1 Gnd 4 P5 Cheetah XI 4 Rx 2 Tx 1 Gnd FS-8917-16 RJ45 to EIA232 Connector RJ45 Connector (408)-262-2299 FIELDSERVER RS-232 to CHEETAH XI PANEL CONNECTION DIAGRAM BASE NAME: FILE NAME: FS-8700-48.VSD 3.4.1. • • DATE: 4/29/08 BY: MC Connection Notes: Communication on the RS-232 port is untested.
FS-8700-48 Fike Cheetah Manual 4. Page 9 of 36 Configuring the FieldServer as a Cheetah Device Client For a detailed discussion on FieldServer configuration, please refer to the FieldServer configuration manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer. (See “.
FS-8700-48 Fike Cheetah Manual 4.2.
FS-8700-48 Fike Cheetah Manual 4.3. Page 11 of 36 Client Side Node Descriptors Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Provide name for node characters Modbus station address of This parameter is not physical Server node required for Cheetah devices. Specify protocol used Cheetah Specify which port the device is connected to the P1-P8, R1-R23 FieldServer This parameter tells the driver what type of panel you are connecting to.
FS-8700-48 Fike Cheetah Manual 4.4.2. Column Title Cheet_Zone Page 12 of 36 Driver Specific Map Descriptor Parameters Function You can use a Map Descriptor to store data for one, all or no zones. If you require data from multiple zones then you must define multiple Map Descriptors each specifying the zone of interest.
FS-8700-48 Fike Cheetah Manual Column Title Cheet_DT Cheet_Func Page 13 of 36 Function Legal Values Abort, Trouble, Supervisory, Disable, PreAlarm, Alarm, Pre-Dis, Release, Process, Any, Data Type. If you require multiple states to All, History, Panel be stored in one/more Data Arrays then you must make multiple Map Descriptors. Only Alarm and Trouble are valid when storing device data (Cheet_Device not equal to None).
FS-8700-48 Fike Cheetah Manual Page 14 of 36 Information over and above the device and zone states is available such as the number of events in alarm state, whether the alarm is silent or on … This data is stored in consecutive array locations. Appendix A.5 of this manual maps the layout of this data. See example 7 4. History Events Every time the panel sees an event it will place in its own history buffer it transmits a message.
Map Descriptor Example 1. (All Zones Data) Page 15 of 36 Function, Passive, The data is stored in Data Array DA_3. Data_Array_Offset, 0, Release state data is stored by the first Map Descriptor and Alarm state data is stored by the second Map Descriptor. Data_Array_Name, DA_3, Node_Name Node_A Starting at element zero. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.
Map Descriptor Example 2.(Specific Zone Data) Page 16 of 36 Data for the specified zone is stored. Cheet_DT, Release, Release, Release state data is stored. Data_Array_Name, DA_1, DA_2, The data is stored into a Data Array called DA_1 for zone 1 and DA_2 for zone 2... Data_Array_Offset, 0, 0, Node_Name Node_A Node_A Starting at element zero. Function, Passive, Passive, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.
Map Descriptor Example 3 – Zone Status as a numeric value Page 17 of 36 Data_Array_Name, DA_DI1, Function, Passive, Node_Name, Node_A, Cheet_Device, None Cheet_DT, Any, Example : Value = 32 indicates an alarm state Example : Value = 96 indicates an alarm & pre-discharge state Bit 0: Abort State Bit 1: Trouble State Bit 2: Supervisory State Bit 3: Zone is disabled Bit 4: Pre Alarm State Bit 5: Alarm State Bit 6: Pre-Discharge State Bit 7: Release State Bit 8: Process State The driver writes a number
Map Descriptor Example 4 – All Devices Page 18 of 36 A different array is used for each state. Another strategy could have been to use the same array but vary the offset. Data_Array_Offset, 0, 0, Since we are storing device data, the Cheet_Zone must be set to None. Data_Array_Name, DA_DI1, DA_DI2, Node_name, Node_A, Node_A, Cheet_Zone, None, None, The Data Type is different for these Map Descriptors so that the driver knows which Map Descriptor to use for each device state’s storage.
Map Descriptor Example 5 (Specific Device) Page 19 of 36 Function, Passive, They are passive because this driver is a data consumer. Data_Array_Offset, 20, Cheet_Loop 1 The Device number is 20. The device belongs to loop1 Cheet_Device, 20, The alarm state is being stored. Cheet_DT, Alarm, We are storing device data so the Cheet_Zone must be set to None.
Map Descriptor Example 6 - Device States as a Numeric Value Page 20 of 36 Data_Array_Name, DA_DI1, Function, Passive, Node_Name, Node_A, Cheet_Zone, None, Cheet_DT, Any, Cheet_Device, All, Map Descriptor Example 7 – Panel Data Example: Value 4 indicates the device is in a trouble state. Bit 0: Alarm Bit 1: Pre-Alarm Bit 2: Trouble The value of the number indicates the device state. The number is a binary number and its value is determined by which bits are set.
Map Descriptor Example 8 – History Data (All Devices) Page 21 of 36 Data_Array_Offset, 0, 240, 480, 720, History events relate to devices and thus the zone must be set to None.
Map Descriptor Example 9 – Full History Event Record – Specific Device Page 22 of 36 Data_Array_Name, DA_HIST, Function, Passive, Node_Name, Node_A, Cheet_Zone, None, Cheet_DT, History, Cheet_Loop, 1, DA_Byte_Name DA_HIST_EVENT Each event record uses at least 65 consecutive elements of the array so the choice of an offset must be made carefully. Event history records are stored in this Data Array. The contents of the Data Array locations are described in section 6.
Map Descriptor Example 11 – Alarm Ack Page 23 of 36 Data_Array_Name, DA_ACK, Function Passive, The Map Descriptor must always be passive. This is because this Map Descriptor is used to respond to the port supervision query. Data_Array_Offset, 0, Cheet_Func Port Response This tells the driver that this Map Descriptor is to be used for acknowledging alarms. Node_Name, Node_A, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.
FS-8700-48 Fike Cheetah Manual 5. Page 24 of 36 Configuring the FieldServer as a Cheetah Device Server This driver cannot act as a data Server, i.e. it cannot write data to the Cheetah controller or devices. Thus it cannot be used to acknowledge alarms or reset states. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll Free: 888-509-1970 email: support@fieldserver.
FS-8700-48 Fike Cheetah Manual Page 25 of 36 Appendix A. Driver Notes Appendix A.1. Driver Scope This driver has implemented cheetah command #6.0. These messages are produced by a Cheetah device controller and are consumed by this driver. The driver has no control on the frequency of the messages and thus cannot guarantee fresh data.
FS-8700-48 Fike Cheetah Manual Page 26 of 36 The event codes are defined in the table below.
FS-8700-48 Fike Cheetah Manual # Description 44 trouble silence supervisory 45 unsilence 46 supervisory silence 47 power-up reset 48 external reset 49 remote reset active 50 drill input restored 51 drill input active 52 alarm unsilence 53 alarm silence 54 abort pressed 55 abort released 56 palarm1 restore----57 palarm1 active ----58 palarm2 restore----59 palarm2 active ----60 alarm active ----- Page 27 of 36 Notes all troubles silenced for all zones. all supervisory unsilenced for all zones.
FS-8700-48 Fike Cheetah Manual # Description 85 network drill presnt 86 abort restored 87 abort present 88 pre-alarm1 restored 89 pre-alarm1 present 90 pre-alarm2 restored 91 pre-alarm2 present 92 network drill restor 93 alarm present 94 periph #aa missing 95 pre-discharge 96 periph #aa return 97 release 98 zone enabled 99 zone disabled 100 watermist inactive 101 watermist active 102 network alarm unsil 103 network superv unsil 104 checksum ok ----- 105 checksum error ----106 network troubl unsil 107 vesd
FS-8700-48 Fike Cheetah Manual Page 29 of 36 # Description 132 enabled loop 1 133 disabled loop 1 134 enabled loop 2 135 disabled loop 2 136 enabled loop 3 137 disabled loop 3 138 enabled loop 4 139 disabled loop 4 140 enabled zone ----141 disabled zone ----- Notes loop 1 has been enabled. loop 1 has been disabled. loop 2 has been enabled. loop 2 has been disabled. loop 3 has been enabled. loop 3 has been disabled. loop 4 has been enabled. loop 4 has been disabled. zone enabled.
FS-8700-48 Fike Cheetah Manual Page 30 of 36 # Description Notes 173 password level 4 password level 4 enterred. 174 password level 5 password level 5 enterred. 175 password expired password has timed-out. 176 software error erroneous interrupt source or illegal program instruction fetched. 177 keyword error erroneous program flow. 178 wiring fault restore frcm/som/srm wiring fault restored to normal.
FS-8700-48 Fike Cheetah Manual # Description 216 vesda fault: urgent 217 vesda clear: urgent 218 vesda fault: power 219 vesda clear: power 220 vesda fault: network 221 vesda clear: network 222 vesda fault: airflow 223 vesda clear: airflow 224 vesda fault: filter 225 vesda clear: filter 226 vesda fault id = --227 vesda clear id = --228 invalid vesda zone 229 invalid v-zone clear 230 invalid vesda fault 231 invalid fault clear 232 grnd fault disabled 233 grnd fault enabled 234 network clr: ------235 network a
FS-8700-48 Fike Cheetah Manual Page 32 of 36 Appendix A.5. Storing Panel Data Panel data is stored in consecutive locations as described in the map below. For additional explanations on the meaning of each data element contact FIKE directly. Array Location 0 Data Category Active Counter (0..
FS-8700-48 Fike Cheetah Manual Page 33 of 36 Appendix A.6. Acknowledging Alarms This driver can be used to acknowledge alarms, reset or silence the Cheetah panel. This functionality is limited. For this function to operate the Cheetah panel must be configured to supervise the port that the FieldServer is connected to. In addition to enabling this function, port supervision means that the panel will go into alarm if the FieldServer does not respond to the supervision messages.
FS-8700-48 Fike Cheetah Manual Page 34 of 36 Appendix B. Driver Error Messages Multiple protocol drivers may exist on a FieldServer. Each driver may produce its own error messages and the FieldServer itself may produce error messages. All messages produced by this driver begin "Cheetah:" Error Message Cheetah:#1 Unknown simulation function. Cheetah:#2 Simulation function unknown. Cheetah:#3 Protocol Error (Start), Incoming msg ignored - Waiting for next msg.
FS-8700-48 Fike Cheetah Manual Error Message Cheetah:#13 Data Array to short. MapDesc=<%s> RQD=%d. Cheetah:#15 Err. MD length is required - defaulting to 1 Cheetah:#17. Err. DIAG_USER_1 Cheetah:# 18 Err. Bad msg start= %#x Cheetah:#19 FYI. Ignoring 0x0100 messages from Cybercat. Cheetah:#20 Err. DA too short. Zone=%d MD=<%s> RQD=%d Cheetah:#21. Err. DA too short. MapDesc=<%s> RQD=%d DA=%s Cheetah:#22 FYI. Node=%s is a Cybercat panel. Cheetah:#23 FYI. Node=%s is a Cheetah panel.
FS-8700-48 Fike Cheetah Manual Page 36 of 36 Appendix B.1. Driver Stats Cheetah panels produce data messages for slave devices to consume. frequency of the messages depends on the Cheetah firmware revision. The type and The driver counts all incoming messages of interest as the PLC_READ_MSG_RECD statistic. Other legal messages which do not contain the data this driver is interested in are discarded and are counted as the MSG_IGNORED statistic.
