FieldServer Fike Cheetah FS-8700-48 Driver Manual Download

Page: 35 / 36

FS-8700-48 Fike Cheetah Manual

Page 36 of 36

FieldServer Technologies

1991 Tarob Court Milpitas, California 95035 USA

Web

: www.fieldserver.com

Tel

: (408) 262 2299

Fax

: (408) 262 2269

Toll Free

: (888) 509 1970

email

: [email protected]

# Description

Notes

208 vesda fault: minor

vesda detector trouble

209 vesda clear: minor

vesda detector trouble

210 vesda fault: isolate

vesda detector trouble

211 vesda clear: isolate

vesda detector trouble

212 vesda fault: system

vesda detector trouble

213 vesda clear: system

vesda detector trouble

214 vesda fault: zone

vesda detector trouble

215 vesda clear: zone

vesda detector trouble

216 vesda fault: urgent

vesda detector trouble

217 vesda clear: urgent

vesda detector trouble

218 vesda fault: power

vesda detector trouble

219 vesda clear: power

vesda detector trouble

220 vesda fault: network vesda detector trouble

221 vesda clear: network vesda detector trouble

222 vesda fault: airflow

vesda detector trouble

223 vesda clear: airflow

vesda detector trouble

224 vesda fault: filter

vesda detector trouble

225 vesda clear: filter

vesda detector trouble

226 vesda fault id = ---

227 vesda clear id = ---

228 invalid vesda zone

vesda zone configured but not present on the vesdanet.

229 invalid v-zone clear

clear message for above fault.

230 invalid vesda fault

fault code 201 message purpose unclear at this time.

231 invalid fault clear

clear message for above fault.

232 grnd fault disabled

ground fault detection has been disabled.

233 grnd fault enabled

clear message for above fault.

234 network clr: -------

network event message: zone-state has cleared

235 network act: -------

network event message: zone-state has activated

236 periph #aa reset

peripheral device of id#aa has active reset sw.

237 periph #aa silence

peripheral device of id#aa has active silence sw.

238 periph #aa acknowl peripheral device of id#aa has active acknowledge sw.

239 periph #aa trouble

peripheral device of id#aa has an active trouble.

240 periph #aa trb clear

peripheral device of id#aa trouble has cleared.

241 periph #aa zone err

peripheral device of id#aa has a zone mis-match with cheetah configuration

242 periph #aa zone clr

peripheral device of id#aa zone mis-match trouble has cleared

243

244 alert sect-n 0.000%

vesda detector has reached alert level in sector 'n'

245 periph #aa drill on

peripheral device of id#aa has active drill sw.

246 periph #aa drill off

peripheral device of id#aa has de-active drill sw.

247 network module trubl trouble detected on the network card

248 network module clear trouble restored from the network card

249 device needed reset output device required reset to restore its configuration

250 action sect-n 0.000% vesda detector has reached alert level in sector 'n'

Summary of Contents for Fike Cheetah FS-8700-48

Page 1: ...1 Document Revision 3 A Sierra Monitor Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after September 2011 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 48 Fike Cheetah ...

Page 2: ...rs 12 5 3 2 Driver Specific Map Descriptor Parameters 13 5 4 Map Descriptor Examples 14 5 4 1 Zone Status 14 5 4 2 Device Status 14 5 4 3 Panel Information 14 5 4 4 History Events 14 5 4 5 Acknowledging Alarms 15 5 4 6 Map Descriptor Example 1 All Zones Data 16 5 4 7 Map Descriptor Example 2 Specific Zone Data 16 5 4 8 Map Descriptor Example 3 Zone Status as a numeric value 17 5 4 9 Map Descriptor...

Page 3: ... Message 1 1 Newer Firmware 25 Appendix B 2 Fike XI Panel Limitations and capabilities 25 Appendix C Troubleshooting 26 Appendix C 1 Driver Error Messages 26 Appendix C 2 Driver Stats 28 Appendix C 3 Map Descriptor Specific Errors 28 Appendix C 4 Multiple Cheetah Panels 28 Appendix D Reference 29 Appendix D 1 Driver Scope 29 Appendix D 2 Panel Firmware Versions 29 Appendix D 3 Storing Panel Data 2...

Page 4: ...and device states The FieldServer can emulate either a Server or Client but it should be noted that it can only process unsolicited messages from the Cheetah devices Thus it does not provide an active Client driver It is best to consider this driver as a consumer only driver with the data being produced by a Cheetah controller 2 DRIVER SCOPE OF SUPPLY 2 1 Supplied by FieldServer Technologies for t...

Page 5: ...ee 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 Connection to Fike Cheetah Panel 8917 14 MODEL 5000 SENTRY RJ11 CONNECTOR PART 21797 FIKE CHEETAH CONNECTOR PART 23048 FIKE CHEETAH PANEL J4 FieldServer P1 1 8 RS 232 Port GND GND FG R1 R2 RS 232 RS 485 1 The co...

Page 6: ...r com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com 3 2 RS 485 Connection to Fike Cheetah Xi Panel SHIELD DACT 485 peripherals P6 Part of Cheetah XI panel Twisted pair to to Connect FieldServer No Connection SHIELD To other Devices For FieldServer RJ45 Ports Use RJ45 Pin1 for Use RJ45 Pin8 for ...

Page 7: ... Connection to Fike Cheetah Xi Panel RJ45 Connector CHEETAH XI PANEL Terminal Block FS 8917 16 P5 RJ45 FieldServer Tx Rx Gnd Rx Tx Gnd 4 2 1 P5 Cheetah XI 8 1 4 Pinouts FieldServer P1 1 8 RS 232 Port 3 3 1 Connection Notes Communication on the RS 232 port is untested We recommend that a RS 232 optical isolator is used on the connection between the FieldServer and the Cheetah XI panel to isolate an...

Page 8: ...4 Connecting the FieldServer to the MIM Multi Interface Module The RS 232 port of the FieldServer connects to the P5 RJ11 RS 232 port of the MIM board 3 4 1 Connection Notes The Peripherals menu of the Fike Panel needs to be updated Hit ESC until Top Level Menu is on the screen Hit F1 for Config Hit F6 for Menu 2 Hit F6 for Menu 3 Hit F1 for Periph Hit F1 for Device Choose address of MIM Set Type ...

Page 9: ...Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format The Cheetah driver always sets Data Array elements to a zero or one Thus the use of bit arrays is suggested but is not mandatory Float BIT UInt16 SInt16 Byte Data_Array_Length Number of Data Objects Must be larger than the data storage area required by...

Page 10: ...e declared in the Data Arrays section the destination device addresses need to be declared in the Server Side Nodes section and the data required from the Client needs to be mapped in the Server Side Map Descriptors section Details on how to do this can be found below Note that in the tables indicates an optional parameter with the bold legal value being the default 5 1 Client Side Connection Para...

Page 11: ...tah Example Client Side Nodes Nodes Node_Name Protocol Port PLC_Type Cheet_Master1 Cheetah P1 Cheetah 5 3 Client Side Map Descriptor Parameters 5 3 1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Data_Array_Name Name of Data Array where data is to be stored in the FieldServer One of...

Page 12: ... more Map Descriptors to store data from the 0 127 addressable devices Each Map Descriptor must have the Cheet_Zone set to None Devices belong to one of 4 possible loops Thus when Cheet_Device is set to All or to a specific device number the Cheet_Loop number must be set to a value from 1 to 4 If Cheet_Device is set to All then 128 states are stored The data for device 0 is stored in the first ele...

Page 13: ...ne state 9 possible The driver can store a number to indicate normal or abnormal state of each zone The value of the number indicates the states See section 5 4 8 All data is stored in a single Data Array and one Map Descriptor is required for all zones 5 4 2 Device Status There are two methods of storing Device status data The driver can store the state trouble alarm pre alarm of each device in a...

Page 14: ...r the most recent event any device or a specific device can be stored in the Data Array DA_HIST_EVENT which must be defined as described in Section 4 Appendix D 3 maps the layout of this data 5 4 5 Acknowledging Alarms There are significant limitations on the driver s ability to send alarm acknowledgements to the panel Refer to Appendix A 1 for more information Section 5 4 16 describes a Map Descr...

Page 15: ...S 0 Passive Panel_01 All None None Abort 256 CHEETAH02 ZONE_TROUBLES 0 Passive Panel_01 All None None Trouble 256 CHEETAH03 ZONE_SUPERS 0 Passive Panel_01 All None None Supervisory 256 CHEETAH04 ZONE_DISABLES 0 Passive Panel_01 All None None Disable 256 5 4 7 Map Descriptor Example 2 Specific Zone Data In this example the Map Descriptors store data for one zone each This variation allows the manip...

Page 16: ...heet_Zone Cheeet_Loop Cheet_Device Cheet_DT Length CHEETAH10 ZONE_STATES 0 Passive Panel_01 All None None Any 256 This data type tells the driver that this Map Descriptor must be used to store zone status data of any type The driver writes a number into the array location for each device The value of the number indicates the status of the zone The value is based on which bits in the binary number ...

Page 17: ...EV_L1_PREALMS 0 Passive Panel_01 None 1 All Pre Alarm 256 CHEETAH12 DEV_L1_ALARM 0 Passive Panel_01 None 1 All Alarm 256 CHEETAH13 DEV_L1_TRBLS 0 Passive Panel_01 None 1 All Trouble 256 CHEETAH14 DEV_L2_PREALMS 0 Passive Panel_01 None 2 All Pre Alarm 256 CHEETAH15 DEV_L2_ALARM 0 Passive Panel_01 None 2 All Alarm 256 CHEETAH16 DEV_L2_TRBLS 0 Passive Panel_01 None 2 All Trouble 256 A different array...

Page 18: ...ssive Panel_01 None 1 All Any 256 CHEETAH24 DEV_L2_STATE 0 Passive Panel_01 None 2 All Any 256 CHEETAH25 DEV_L3_STATE 0 Passive Panel_01 None 3 All Any 256 CHEETAH26 DEV_L4_STATE 0 Passive Panel_01 None 4 All Any 256 Each Map Descriptor in this example reads data for one device only Thus each Map Descriptor must point to a different Data Array or as is the case in this example to a different locat...

Page 19: ...and loop 2 s data is stored at an offset location of 240 max number of devices per loop in the Data Array The Device is set to ALL to tell the driver to process all devices on the loop using this Map Descriptor If a history event for device 100 on loop 3 is received then the driver will store the event code at location 480 base offset for loop 3 100 device address The event code will be stored as ...

Page 20: ...vent is stored using this Map Descriptor The full record is stored but is overwritten when a new event is received irrespective of the event s device address Client Side Map Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Cheet_Zone Cheet_DT Cheet_Device Cheet_Loop DA_Byte_Name Length Device1_L1_Hist DA_HIST 0 Passive Node_A None History ALL 1 DA_HIST_EVENT 256...

Page 21: ... the array named DA_ACK is used to send a signal to the Cheetah panel Client Side Map Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Cheet_Func Ack_Mapdesc DA_ACK 0 Passive Node_A Port Response This tells the driver that this Map Descriptor is to be used for acknowledging alarms The Map Descriptor must always be passive This is because this Map Descriptor is u...

Page 22: ... www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com 6 CONFIGURING THE FIELDSERVER AS A CHEETAH DEVICE SERVER This Driver cannot act as a Server i e it cannot write data to the Cheetah controller or devices Thus it cannot be used to acknowledge alarms or reset states ...

Page 23: ...er s response to the supervision poll from the panel The panel ignores unsolicited messages A consequence of this is that the driver cannot control the timing of when the ack reset silence message is sent to the panel In using this functionality you should also understand that the Cheetah panel protocol does not acknowledge message receipt so this driver cannot report whether the message was recei...

Page 24: ...minutes Appendix B 1 1 Message 6 0 limitations Can only report data for 127 zones Data is limited to Alarm Trouble Pre Discharge and Released states Can only report data for 127 devices on loops 1 4 Data is limited to Alarm Trouble states Appendix B 1 2 Message 1 1 Older firmware No useful information about zones or devices Appendix B 1 3 Message 1 1 Newer Firmware Supports zones 1 240 For zones t...

Page 25: ...etah 5 Protocol Error Chksum Incoming msg ignored Waiting for next msg Cheetah 6 Protocol Error Unknown Incoming msg ignored Waiting for next msg Report this error to FieldServer Technologies Cheetah 7a Err Zone d Max d Cheetah 7b MapDesc Error Zone value error d Cheetah 7c FYI Warning Zone d Max zone is panel type dependent Read Manual An invalid zone has been specified The zone causing the probl...

Page 26: ...rrect length otherwise please use 256 If you are unsure ask tech support to provide the template file server csv Cheetah 17 Err DIAG_USER_1 An internal diagnostic has been activated This should not happen on a live system Take a log and contact tech support Cheetah 18 Err Bad msg start x Messages are expected to begin with a Carriage return or SOH 0x01 The message has been rejected because it star...

Page 27: ...rease by three when viewed from the connection s point of view The driver ignores messages 0x0100 from Cybercat panels These lagacy messages contain contradictory information If the node is configured as a Cybercat panel then the driver ignores the messages and increases the Ignored Messages stat on the connection Appendix C 3 Map Descriptor Specific Errors Some errors produced by the driver are M...

Page 28: ...n contains panel zone device data Appendix D 3 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 Data Category Data stored at this location 0 Active Counter 0 65535 Active events in normal state 1 Active events in Process state 2 Active events in Trouble...

Page 29: ...ce Appendix D 4 How History Events are Stored History events records are send by the panel each time an event occurs The driver can parse these messages and store the data in either of two ways The event code is stored at an array location that is based on the device address and loop number See Section 5 4 13 Additional event data is stored in a secondary Data Array See Section 5 4 14 The array lo...

Page 30: ...urns canceling missing trouble 21 device missing addr device trouble device was polled but not found 22 commun restored addr device trouble communication to device has returned to normal 23 bad communication addr device trouble communication to device has errors parity checksum etc 24 restored multiple addr device trouble multiple devices trouble has cleared 25 multiple devices addr device trouble...

Page 31: ... analog data appended to this message 60 alarm active device has reached the alarm threshold analog data appended to this message 61 manual alarm manual pull function input present 62 manual pre discharge pre discharge function input present 63 manual release manual release function input present 64 waterflow active waterflow input function activated 65 waterflow restored waterflow input function ...

Page 32: ...ries 104 checksum ok zone configuration checksum error restored zone number appended to this message 105 checksum error zone configuration checksum error zone number appended to this message 106 network troubl unsil network command unsilence troubles 107 vesda not configured trouble event stored when the hli is present but no vesda is configured 108 vesda configur clear trouble clear event for the...

Page 33: ... configured analog devices on loop 2 have been calibrated 146 loop 3 calibration all configured analog devices on loop 3 have been calibrated 147 loop 4 calibration all configured analog devices on loop 4 have been calibrated 148 l1 open class a class a wiring has an open circuit trouble loop 1 149 l2 open class a class a wiring has an open circuit trouble loop 2 150 l3 open class a class a wiring...

Page 34: ...onfig error 5 watermist zone needs an srm zone number appended 187 cfg resto 6 w config error 6 restored zone number appended 188 cfg error 6 w config error 6 watermist zone has an abort zone number appended 189 cfg resto 7 on time config error 7 restored 190 cfg error 7 on time config error 7 srm assigned to watermist zone has no on time 191 cfg resto 8 zn type config error 8 restored 192 cfg err...

Page 35: ...or above fault 230 invalid vesda fault fault code 201 message purpose unclear at this time 231 invalid fault clear clear message for above fault 232 grnd fault disabled ground fault detection has been disabled 233 grnd fault enabled clear message for above fault 234 network clr network event message zone state has cleared 235 network act network event message zone state has activated 236 periph aa...

Page 36: ...262 2269 Toll Free 888 509 1970 email support fieldserver com Description Notes 251 fire 1 sect n 0 000 vesda detector has reached action level in sector n 252 fire 2 sect n 0 000 vesda detector has reached alarm level in sector n 253 event 253 reserved for the history module 254 event 254 reserved for the history module 255 event 255 reserved for the history module ...

Search results

Summary of Contents for Fike Cheetah FS-8700-48

Reviews:

Related manuals for Fike Cheetah FS-8700-48

Brands by name

Popular brands

FieldServer Fike Cheetah FS-8700-48, Driver Manual

Search results

Summary of Contents for Fike Cheetah FS-8700-48

Reviews:

Related manuals for Fike Cheetah FS-8700-48

Brands by name

Popular brands