Accton Technology Server FS 8700 48 User Manual

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.03  
Document Revision: 7  
 
FS-8700-48 Fike Cheetah Manual  
Page 3 of 36  
1.  
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.  
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.  
The driver supports messages sent from the Cybercat panel. Specifically, the driver supports  
message 1.02 which reports panel, zone and device 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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 4 of 36  
2.  
Driver Scope of Supply  
2.1. Supplied by FieldServer Technologies for this driver  
FieldServer Technologies  
PART #  
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.  
FS-8915-10  
FS-8700-48  
2.2.  
Provided by Supplier of 3rd Party Equipment  
PART #  
DESCRIPTION  
Fike Cheetah panel and power supply.  
RS-485 cable, if required.  
Longer UTP cable, if required.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Hardware Connections1  
The FieldServer is connected to the Cheetah panel's Peripheral Port (see below).  
Page 5 of 36  
3.  
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
T
he connection diagrams are for Non Cybercat Panels. Connection info was not available at the time  
this document was last updated.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 6 of 36  
3.2.  
RS-485 Connection to Fike Cheetah 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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 7 of 36  
3.3.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 8 of 36  
3.4.  
RS-232 Connection to Fike Cheetah XI Panel  
CHEETAH XI  
PANEL  
P5  
Terminal  
Block  
Pinouts  
P5  
RJ45  
Cheetah XI  
4 Rx  
FieldServer  
8
1
4
Tx  
Tx  
Rx  
2
Gnd  
1 Gnd  
FS-8917-16  
RJ45 Connector  
(408)-262-2299  
FIELDSERVER  
RS-232 to CHEETAH XI PANEL  
CONNECTION DIAGRAM  
BASE NAME:  
FILE NAME: FS-8700-48.VSD  
DATE: 4/29/08  
BY: MC  
3.4.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 any potential ground differential  
issues.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 9 of 36  
4.  
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 “.csv” sample  
files provided with the FieldServer)  
This section documents and describes the parameters necessary for configuring the FieldServer  
to communicate with a Cheetah Device Server.  
The configuration file tells the FieldServer about its interfaces, and the routing of data required.  
In order to enable the FieldServer for Cheetah Device communications, the driver independent  
FieldServer buffers need to be declared in the “Data Arrays” section, the destination device  
addresses need to be declared in the “Client Side Nodes” section, and the data required from  
the Servers needs to be mapped in the “Client 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.  
4.1.  
Data Arrays  
Section Title  
Data_Arrays  
Column Title  
Function  
Provide name for Data  
Array  
Legal Values  
Data_Array_Name  
Data_Format  
Up to 15 alphanumeric characters  
FLOAT,  
Packed_Bit,  
BIT,  
UInt16,  
SInt16,  
Byte,  
Packed_Byte,  
Swapped_Byte  
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.  
Number of Data Objects.  
Must be larger than the  
Data_Array_Length data storage area required  
for the data being placed in  
this array.  
1-10,000. If you use the 'All' keyword  
when  
setting  
the  
parameter  
Cheet_Zone/Device then the minimum  
length is 128.  
Example  
// Data Arrays  
Data_Arrays  
Data_Array_Name,  
DA_AI_01,  
DA_AO_01,  
DA_DI_01,  
Data_Format,  
UInt16,  
UInt16,  
Bit,  
Data_Array_Length  
200  
200  
200  
200  
DA_DO_01,  
Bit,  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 10 of 36  
4.2.  
Client Side Connection Descriptors  
Section Title  
Connections  
Column Title  
Function  
Legal Values  
Specify which port the  
device is connected to P1-P8, R1-R22  
the FieldServer  
Port  
Baud*  
Parity*  
Data_Bits*  
Specify baud rate  
Specify parity  
Specify data bits  
9600  
None, (Vendor limitation)  
8 (Vendor limitation)  
1 (Vendor limitation)  
Stop_Bits*  
Specify stop bits  
Cheetah (makes the port the exclusive domain  
of Cheetah devices.) This keyword is not  
required when specifying the port.  
Protocol  
Specify protocol used  
Specify  
hardware  
Handshaking*  
Poll Delay*  
None  
handshaking  
Time between internal  
polls  
0-32000 seconds, 1 second  
Example  
// Client Side Connections  
Connections  
Port,  
P8,  
Baud,  
9600,  
Protocol,  
Cheetah,  
Poll_Delay  
0.100s  
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction  
manual for details of the ports available on specific hardware.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 11 of 36  
4.3.  
Nodes  
Client Side Node Descriptors  
Section Title  
Column Title  
Function  
Legal Values  
Up to 32 alphanumeric  
characters  
Node_Name  
Provide name for node  
Modbus station address of This  
parameter  
is  
not  
Node_ID  
Protocol  
physical Server node  
required for Cheetah devices.  
Specify protocol used  
Cheetah  
Specify which port the device  
Port  
is  
connected  
to  
the P1-P8, R1-R23  
FieldServer  
This parameter tells the  
driver what type of panel you  
are connecting to. If not  
specified, the driver expects  
that you are connecting to a  
legacy Cheetah panel.  
PLC_TYPE  
'Cybercat' , 'Cheetah'  
Example  
// Client Side Nodes  
Nodes  
Node_Name,  
Cheet_Master1,  
Protocol,  
Cheetah,  
Port  
P8  
4.4.  
Client Side Map Descriptors  
4.4.1.  
Column Title  
Map_Descriptor_Name Name of this Map Descriptor  
FieldServer Specific Map Descriptor Parameters  
Function Legal Values  
Up to 32 alphanumeric  
characters  
Name of Data Array where One of the Data Array names  
data is to be stored in the from “Data Array” section  
Data_Array_Name  
FieldServer  
above  
0 to maximum specified in  
“Data Array” section above  
Data_Array_Location  
Starting location in Data Array  
RDBC,  
WRBC,  
WRBX,  
PASSIVE  
Function of Client Map  
Descriptor  
Function  
Only the keyword passive may  
be used for Cheetah devices.  
Up to 32 alphanumeric  
characters  
Node_Name  
Provide name for node  
3
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction  
manual for details of the ports available on specific hardware.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 12 of 36  
4.4.2.  
Driver Specific Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
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. When  
specifying “All”, the data for zone 0 is  
stored in the first element of the Data Array  
pointed to by the Data_Array_Name &  
Data_Array_Location and the data for  
None, All, 0-127  
zone 127 in the 128th element of the Data Must be None when  
Array.  
Cheet_Device is not equal  
Cheet_Zone  
Depending on the firmware version of the to None.  
Cheetah panel some or all of the following  
states are available. To have the driver  
store data for multiple states you must  
define multiple Map Descriptors - One per  
state of interest.  
Abort, Trouble, Supervisory, Zone Disable,  
Pre-Alarm, Alarm, Pre-Discharge, Release,  
Process.  
Define one or 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 you set Cheet_Device to All or  
None, All, 0-127  
to a specific device number you must also  
set the Cheet_Loop number to a value  
from 1 to 4.  
Cheet_Device  
Must be None when  
Cheet_Zone is not equal  
to None.  
If you set Cheet_Device to All then 128  
states are stored. The data for device 0 is  
stored in the first element of the Data Array  
pointed to by the Data_Array_Name &  
Data_Array_Location and the data for  
device 127 in the 128th element of the  
Data Array.  
None, 1-3  
Specify this parameter when the value of Must be None when  
Cheet_Loop  
Cheet_Device is not equal to none.  
Cheet_Zone is not equal  
to None.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Column Title  
Page 13 of 36  
Function  
Legal Values  
Trouble,  
Abort,  
Supervisory, Disable, Pre-  
Alarm, 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  
Cheet_DT  
you must make multiple Map Descriptors.  
Only Alarm and Trouble  
are valid when storing  
device data  
(Cheet_Device not equal  
to None).  
Port Response  
These additional keywords  
are valid but are used for  
testing the driver and must  
not be used in  
a
configuration to be used  
for communication with a  
Cheetah panel.  
Cheet_Func  
Use for active Map Descriptors only  
Iscan_g_update  
Panel Status  
History Event  
Port Supervision  
4.5.  
Map Descriptor Examples  
The driver processes messages from the panel that relay the panel’s current status as well  
as new history events. These messages contain composite data and the contents cannot  
simply be stored in a Data Array and then be read by some downstream device.  
The Map Descriptors tell the driver how to store portions of this composite data from the  
following categories. At least one Map Descriptor is required for each category.  
1. Zone Status  
The driver can store the state (trouble, alarm, pre-alarm...) of each zone in a separate array  
as a 1 or zero state. See examples 1 & 2. The driver can also store a number in a separate  
Data Array to indicate normal or abnormal state of each zone. (The value of the number  
indicates the states.) See example 3.  
2. Device Status  
The driver can store the state (trouble, alarm, pre-alarm...) of each device in a separate  
array as a bit state (1 or 0) . See examples 4 & 5  
The driver can also store a number in a separate Data Array to indicate normal or abnormal  
state of each device. See example 6  
3. Panel Information  
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: [email protected]  
 
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. This driver processes the message and stores the event code (most recent) in a  
location based on the source device’s address. This gives an array of the most recent  
events for all devices. See example 8  
The driver can also store the entire history event record in a Data Array. Appendix A.4 maps  
the layout of this data. This record includes data such as the time and date. See examples  
9 & 10  
5. Acknowledging Alarms  
There are significant limitations on the driver’s ability to send alarm acknowledgements to  
the panel. Refer to Appendix A.6 this manual for more information. See example 11 for a  
Map Descriptor which can be used to get the driver to acknowledge alarms.  
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: [email protected]  
 
 
 
 
 
 
 
 
 
 
FS-8700-48 Fike Cheetah Manual  
Page 24 of 36  
5.  
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: [email protected]  
 
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. In addition the protocol  
has no method for acknowledging messages so that in the event of this driver having to  
discard a corrupt message, the message producer does not know and will not re-send.  
Appendix A.2. Map Descriptor Specific Errors  
Some errors produced by the driver are Map Descriptor specific. They can only be seen  
when using the Ruidebug program and looking at the Map Descriptor debugging screens.  
For more information on how to do this please refer to the FieldServer Utilities manual.  
Appendix A.3. Multiple Cheetah Panels  
Some of the broadcast messages produced by the Cheetah panel are node-less. This  
means that these messages do not identify the node of origin. Unfortunately, the message  
this driver uses to determine zone and device alarms is a node-less message. This limits  
the number of Cheetah panels per port to one. (If there were more than one the driver would  
not be able to determine the node of origin.)  
Appendix A.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 first method stores the event code at an array location that is based on the device  
address and loop number. See Map Descriptor example 8  
The second method stores a large number of additional event data such as the time &  
date in a secondary Data Array. See Map Descriptor example 9  
The array locations of the additional data are indicated below  
Location Contents  
Notes  
0
Month  
1
Day of Month  
2
3
4
Year less 1900  
Day of Week (1..7)  
Hour (0-12)  
5
AM-PM (A,P)  
6
Minute  
7
Second  
8
9
Event Data (0-65535)  
Custom Message  
Fire Point  
Zero Point  
Device Type  
Device Function  
Zones device belongs to  
Current History Counter (0-65535)  
20 bytes  
29  
30  
31  
32  
33  
65  
32 bytes. Bit 0 -> Zone1 …. Bit 17->zone 18 …  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 26 of 36  
The event codes are defined in the table below.  
#
0
1
2
3
4
5
6
7
8
9
Description  
no record  
Notes  
-
aux power unconfig auxiliary power module present but unconfigured.  
aux power corrected auxiliary power module replaced after being missing.  
aux power missing auxiliary power module not present but configured.  
ac1 power restored ac for main board input restored.  
ac1 power trouble  
ac2 power restored ac for power module input restored.  
ac2 power trouble  
batttery1 restored  
batttery1 trouble  
ac for main board input missing/brownout.  
ac for power module input missing/brownout.  
battery for main board input restored.  
battery for main board input missing.  
battery for power module input restored.  
battery for power module input missing.  
audible #1 restored.  
audible #1 open circuit.  
audible #1 short circuit.  
audible #2 restored.  
audible #2 open circuit.  
audible #2 short circuit.  
ground fault trouble restored to normal.  
ground fault present.  
addr device trouble: device returns canceling missing trouble  
addr device trouble: device was polled but not found  
addr device trouble: communication to device has returned to normal  
addr device trouble: communication to device has errors (parity checksum  
etc.)  
10 battery2 restored  
11 battery2 trouble  
12 aud1 trb restored  
13 aud1 open trouble  
14 aud1 short trouble  
15 aud2 trb restored  
16 aud2 open trouble  
17 aud2 short trouble  
18 gnd fault restored  
19 gnd fault present  
20 device present  
21 device missing  
22 commun restored  
23 bad communication  
24 restored multiple  
25 multiple devices  
addr device trouble: multiple devices trouble has cleared  
addr device trouble: multiple devices detected at this address  
addr device trouble: correct kind of device has been restored to this  
address  
26 restored device kind  
27 wrong device kind  
addr device trouble: wrong kind of devices has been found  
28 contaminated device addr device trouble: analog device is contaminated  
29 loop module restored loop mod missing trouble has cleared  
30 loop module missing loop module not in place but there are configured devices on the loops.  
config  
accessed  
menu  
31  
trouble stored when the configuration menu has been entered  
32 factory initialized  
33 uart failure  
history stored when a factory initialization has been invoked  
history stored when the uart has been corrupted by esd and then re-  
initialized.  
34 uart restored  
35 system reset  
36 trouble restored  
history stored when preceding trouble has cleared.  
complete reset including power-down of loops for ten seconds.  
trouble function input restore.  
37 trouble input active trouble function input present.  
38 process restored process control function input restored.  
39 process input active process control function input present.  
40 supervisory restored supervisory function input restore.  
41 supervisory active  
42 remote reset release remote reset function input released.  
43 trouble unsilence all troubles unsilenced for all zones.  
supervisory function input present.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 27 of 36  
#
Description  
Notes  
44 trouble silence  
all troubles silenced for all zones.  
supervisory  
unsilence  
45  
all supervisory unsilenced for all zones.  
46 supervisory silence all supervisory silenced for all zones.  
47 power-up reset  
48 external reset  
reset record when panel is powered up  
reset record when external reset switch pressed or esd hit causes reset  
49 remote reset active remote reset switch activated  
50 drill input restored  
51 drill input active  
52 alarm unsilence  
53 alarm silence  
54 abort pressed  
55 abort released  
drill function input restore.  
drill function input present.  
all alarm states unsilenced for all zones.  
all alarm states silenced for all zones.  
abort function input present.  
abort function input restored.  
device restored below pre-alarm1 threshold. analog data appended to this  
message  
56 palarm1 restore-----  
57 palarm1 active -----  
58 palarm2 restore-----  
59 palarm2 active -----  
device above pre-alarm1 threshold.  
message  
analog data appended to this  
device restored below pre-alarm2 threshold. analog data appended to this  
message  
device above pre-alarm2 threshold.  
message  
analog data appended to this  
device has reached the alarm threshold.  
message  
manual pull function input present.  
analog data appended to this  
60 alarm active -----  
61 manual alarm  
manual  
discharge  
pre-  
62  
pre-discharge function input present.  
63 manual release  
64 waterflow active  
65 waterflow restored  
manual release function input present.  
waterflow input function activated.  
waterflow input function restored to normal.  
66 invalid abort active abort switch pressed in zone without an alarm present  
67 inv abort restored  
68 cfg resto 9: mr-----  
69 cfg error 9: mr-----  
70 network reset  
abort switch released in zone without an alarm present  
config error #9 restored. zone number appended to this message.  
config error #9: manual release is in an alarm only zone.  
history stored when a reset command is recorded from cheetah net  
history stored when an acknowledge command is recorded from cheetah  
net  
network  
71  
acknowledge  
72 process restored  
73 process present  
74 trouble restored  
75 trouble present  
process state for this zone de-activated.  
process state for this zone activated.  
trouble state for this zone de-activated.  
trouble state for this zone activated.  
76 supervisory restored supervisory state for this zone de-activated.  
77 supervisory present supervisory state for this zone activated.  
78 drill restored  
79 drill present  
drill state for this zone de-activated.  
drill state for this zone activated.  
net  
missing  
member#a  
80  
network member #a is missing.  
81 net member#a return network member #a has returned on line.  
82 net manager missing network manager is missing.  
83 net manager return network manager has returned on line.  
84 network silence  
history stored when a silence command is recorded from cheetah net  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 28 of 36  
#
Description  
Notes  
85 network drill presnt drill state activated from network - all zone only.  
86 abort restored  
87 abort present  
abort state for this zone de-activated.  
abort state for this zone activated.  
88 pre-alarm1 restored pre-alarm 1 state for this zone de-activated.  
89 pre-alarm1 present pre-alarm 1 state for this zone activated.  
90 pre-alarm2 restored pre-alarm 2 state for this zone de-activated.  
91 pre-alarm2 present pre-alarm 2 state for this zone activated.  
92 network drill restor  
93 alarm present  
drill state restored from network - all zone only.  
alarm state for this zone activated.  
94 periph #aa missing peripheral device of id#aa is missing.  
95 pre-discharge  
96 periph #aa return  
97 release  
pre-discharge state for this zone activated.  
peripheral device of id#aa has returned on line.  
release state for this zone activated.  
98 zone enabled  
99 zone disabled  
100 watermist inactive  
101 watermist active  
zone disable state for this zone de-activated.  
zone disable state for this zone activated.  
not used since release state never clears  
watermist state for this zone activated  
102 network alarm unsil network command - unsilence alarms  
103 network superv unsil network command - unsilence supervisories  
zone configuration checksum error restored. zone number appended to  
this message.  
104 checksum ok -----  
105 checksum error -----  
zone configuration checksum error.  
message.  
zone number appended to this  
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 above trouble.  
109 config menu exited trouble clear event when the configuration menu has been exited  
110 aux1 power restored auxiliary power input trouble restored - main board  
111 aux1 power trouble auxiliary power input trouble - main board  
112 aux2 power restored auxiliary power input trouble restored - power module  
113 aux2 power trouble auxiliary power input trouble - power module  
114 aud switch disabled enable/disable switch for audibles is in the disable position  
115 aud switch restored enable/disable switch for audibles has returned to the enable position  
116 diagnostics entered indicates the operator has accessed the diagnostic menu selections  
117 zone disable restore frcm assigned to zone disable function has cleared  
118 zone disable active frcm assigned to zone disable function has activated  
119 internal fault  
device trouble from the 0x08 polling command  
trouble restored from the 0x08 polling command  
open circuit fault on supervised circuit: frcm/som/srm  
short circuit fault on frcm/som/srm  
120 int fault restored  
121 wiring fault-open  
122 wiring fault-short  
123 acknowledge switch acknowledge switch pressed.  
124 test point bad  
analog device fire test point is out of hochiki specified range.  
125 calibration restored calibration fault has been restored. device now has valid calibration data.  
126 calibration fault  
127 configure restored  
128 configure fault  
fault detected during calibration of this device.  
fault restored from som/r2m/srm configuration trouble.  
fault detected when configuring som/r2m/srm.  
129 reconfigured device addressable device has been configured  
130 enabled device  
131 disabled device  
addressable device has been enabled.  
addressable device has been disabled.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 29 of 36  
#
Description  
Notes  
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  
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.  
140 enabled zone ----- zone enabled. zone number appended to this message.  
141 disabled zone ----- zone disabled. zone number appended to this message.  
board level output circuit enabled. circuit number appended to this  
message.  
board level output circuit disabled. circuit number appended to this  
message.  
142 enabled ckt -----  
143 disabled ckt -----  
144 loop 1 calibration  
145 loop 2 calibration  
146 loop 3 calibration  
147 loop 4 calibration  
148 l1 open class a  
149 l2 open class a  
150 l3 open class a  
151 l4 open class a  
152 l1 class a restored  
153 l2 class a restored  
154 l3 class a restored  
155 l4 class a restored  
156 walktest active  
all configured analog devices on loop 1 have been calibrated.  
all configured analog devices on loop 2 have been calibrated.  
all configured analog devices on loop 3 have been calibrated.  
all configured analog devices on loop 4 have been calibrated.  
class a wiring has an open circuit trouble - loop 1.  
class a wiring has an open circuit trouble - loop 2.  
class a wiring has an open circuit trouble - loop 3.  
class a wiring has an open circuit trouble - loop 4.  
class a wiring trouble has restored to noramal - loop 1.  
class a wiring trouble has restored to noramal - loop 2.  
class a wiring trouble has restored to noramal - loop 3.  
class a wiring trouble has restored to noramal - loop 4.  
panel has enterred the walktest mode.  
157 walktest expired  
walktest mode has expired.  
config error #1 restored.  
message.  
config error #1 (no manrel in this zone). zone number appended to this  
message.  
zone number appended to this  
158 cfg resto 1: mr-----  
159 cfg error 1: mr-----  
160  
cheetah network device clear  
161  
cheetah network device activation  
162 config resto 3: al v  
config error #3 restored.  
config error #3 (alarm verification on device in a suppression zone)  
trouble.  
163 config error 3: al v  
164 system power low  
165 system power ok  
system power below voltage level for reliable operation.  
system power low trouble restored.  
config checksum error trouble:  
appended).  
config checksum error trouble restored: devices & loops (loop number  
devices & loops (loop number  
166 checksum error -----  
167 checksum ok -----  
168 checksum ok -----  
169 checksum error -----  
appended).  
board level output config checksum restored. circuit number appended to  
this message.  
board level output config checksum error.  
this message.  
circuit number appended to  
170 password level 1  
171 password level 2  
172 password level 3  
password level 1 enterred.  
password level 2 enterred.  
password level 3 enterred.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 30 of 36  
#
Description  
Notes  
173 password level 4  
174 password level 5  
175 password expired  
176 software error  
password level 4 enterred.  
password level 5 enterred.  
password has timed-out.  
erroneous interrupt source or illegal program instruction fetched.  
erroneous program flow.  
177 keyword error  
178 wiring fault restore  
frcm/som/srm wiring fault restored to normal.  
179 config resto 4: sens config error #4 restored  
180 config error 4: sens config error #4 (analog phot has too high alarm sensitivity)  
181 bat1 charge volt low battery #1 charger has a low voltage output  
182 bat1 charge restored battery #1 chrager has returned to normal voltage output  
183 bat2 charge volt low battery #2 charger has a low voltage output  
184 bat2 charge restored battery #2 chrager has returned to normal voltage output  
185 cfg resto 5: w------  
186 cfg error 5: w------  
187 cfg resto 6: w------  
188 cfg error 6: w------  
config error #5 restored. zone number appended.  
config error #5 (watermist zone needs an srm). zone number appended.  
config error #6 restored.  
zone number appended.  
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 error 8: zn-type config error #8 (srm assigned to watermist & alarm type of zone).  
193 pc configuring panel configuration is currently being changed by the pc  
194 pc configuring done the pc has finished configuring the panel  
195 history is erased  
the history buffers have been erased  
196 cfg resto 10: vesda# config error #10 restored  
197 vesda commun error communication to the vesda hli device has failed  
vesda  
restore  
commun  
198  
communication to the vesda hli device has restored to normal  
199 cfg error 10: vesda# config error #10 (two vesda's with the same unit number)  
vesda detector alert level restored.  
message  
vesda detector alert level activated.  
message  
vesda detector action level restored.  
message  
analog data appended to this  
200 alert level restore  
201 alert 0.000%/0.000%  
202 action level restore  
analog data appended to this  
analog data appended to this  
action  
203  
vesda detector action level activated. analog data appended to this  
message  
0.000%/0.000%  
fire-1  
0.000%/0.000%  
vesda detector fire 1 level activated. analog data appended to this  
message  
204  
fire-2  
0.000%/0.000%  
vesda detector fire 2 level activated. analog data appended to this  
message  
205  
206 vesda fault: major  
207 vesda clear: major  
208 vesda fault: minor  
209 vesda clear: minor  
vesda detector trouble  
vesda detector trouble  
vesda detector trouble  
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  
215 vesda clear: zone  
vesda detector trouble  
vesda detector trouble  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 31 of 36  
#
Description  
Notes  
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  
225 vesda clear: filter  
226 vesda fault id = ---  
227 vesda clear id = ---  
228 invalid vesda zone  
vesda detector trouble  
vesda detector trouble  
vesda zone configured but not present on the vesdanet.  
229 invalid v-zone clear clear message for above fault.  
230 invalid vesda fault  
231 invalid fault clear  
232 grnd fault disabled  
233 grnd fault enabled  
234 network clr: -------  
235 network act: -------  
236 periph #aa reset  
237 periph #aa silence  
fault code 201 message purpose unclear at this time.  
clear message for above fault.  
ground fault detection has been disabled.  
clear message for above fault.  
network event message: zone-state has cleared  
network event message: zone-state has activated  
peripheral device of id#aa has active reset sw.  
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.  
peripheral device of id#aa has a zone mis-match with cheetah  
configuration  
241 periph #aa zone err  
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  
246 periph #aa drill off  
peripheral device of id#aa has active drill sw.  
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'  
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  
254  
255  
event 253 reserved for the history module  
event 254 reserved for the history module  
event 255 reserved for the history module  
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: [email protected]  
 
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 Data Category  
Data stored at this location  
Active events in normal state  
Active events in Process state  
Active events in Trouble state  
Active events in Supervisory state  
Active events in Drill state  
0
Active Counter (0..65535)  
1
2
3
4
5
Active events in ? state  
6
Active events in ? state  
7
Active events in ? state  
8
9
Active events in Abort state  
Active events in Pre-Alarm1 state  
Active events in Pre-Alarm2 state  
Active events in Alarm state  
Active events in Pre-Discharge state  
Active events in Release state  
Active events in Zone Discharge state  
Active events in Water Mist state  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
33  
34  
35  
36  
37  
38  
39  
40  
Board Status Indicators (0 or 1) Alarm silence active 1=yes  
Supervisory Silence Active 1=yes  
Trouble Silence Active 1=yes  
AC Power on Main Board 1=ok  
AC Power on Aux Board 1=ok  
Walk test Condition 1=on  
Ground Fault Condition 1=ok  
Ack Condition 1=on  
Month  
Day of Month  
Year  
Day of Week  
Hour  
Date & Time  
AM/PM  
Minute  
Second  
Current Event Counter  
LED Status Indicators  
Number of current events present on cheetah  
Pre-Alarm  
Fire Alarm  
Supervisory Alarm  
Trouble  
AC Power  
Alarm Silence  
Supervisory Silence  
Trouble Silence  
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: [email protected]  
 
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. In fact the request to ack /reset/ silence the panel  
is included in the driver’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  
received by the panel and whether it was acted on.  
The port supervision response message is sent even if you do not define a Port Response  
Map Descriptor in the CSV file. In this case the command data will always be zero. Once  
you define a Map Descriptor then the driver uses one Data Array element to determine the  
command data to send to the panel. The value from this array element determines the  
action the panel will take.  
Bit Action  
Decimal Value  
0
1
2
Reset  
Silence  
Acknowledge 4  
1
2
Example: If you wish to Silence the Panel, then set the value of the Data Array element to 2.  
Appendix A.7. Panel Firmware Versions  
The driver supports older versions of panel firmware which transmit a shorter version of the  
Panel Status command. This shorter version contains only panel data whereas the newer  
version contains panel, zone & device data.  
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: [email protected]  
 
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  
Action Required  
Cheetah:#1 Unknown  
simulation function.  
Cheetah:#2 Simulation  
function unknown.  
Cheetah:#3 Protocol Error  
(Start), Incoming msg  
ignored - Waiting for next  
msg.  
Report these messages to FieldServer Technologies.  
Warning messages only. An incoming message was discarded  
because the identifiers which mark the beginning of a message could  
not be found. You cannot take any action to correct this message. If it  
occurs often check wiring, noise and installation.  
Cheetah:#4 Protocol Error  
(Stop), Incoming msg  
ignored - Waiting for next  
msg.  
Cheetah:#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 An invalid zone has been specified. The zone causing the problem is  
Max=%d  
printed in parenthesis.4  
Cheetah:#7b  
MapDesc The largest possible zone number is 255. Only Cybercat panels support  
Error. Zone value error. this number of zones. Legacy panels support up to zone 239. Very old  
(%d)  
panels that can only send message #6 can only report information for  
127 panels.  
If you are connected to a Cybercat panel and you get the FYI message  
Cheetah:#7c FYI. Warning.  
Zone=%d. Max zone is  
panel type dependent. Read you can ignore it. If you are connected to some other panel and you get  
Manual.  
Cheetah:#8 MapDesc Error.  
Device value error. (%d)  
either the Err or FYI message then you will need to correct the CSV file.  
An invalid device has been specified. The device causing the problem  
is printed in parenthesis.4  
An invalid loop has been specified. The loop causing the problem is  
Cheetah:#9 MapDesc Error.  
Loop value error. (%d)  
printed in parenthesis.4  
One Map Descriptor cannot be used to store data for zones and  
devices. Either the keyword Cheet_Zone or Cheet_Device must be set  
to None4.  
Cheetah:#10 MapDesc  
Error. Zone & Device  
Specified.  
Cheetah:#11 MapDesc  
Error. With devices only  
alarm & trouble available.  
Cheetah:#12 Message on  
Cheetah port but no  
mapDesc found.  
For devices only the alarm & trouble states are available. Set the  
Cheet_DT values appropriately in the configuration file.4  
A port has been reserved for the Cheetah protocol and a message has  
been received on this port but there is no Map Descriptor defined for this  
port.5  
4
Modify the CSV file, download to the FieldServer and restart the FieldServer for the changes to take  
effect.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Page 35 of 36  
Error Message  
Action Required  
The Data Array associated with the Map Descriptor in question is too  
short. Adjust the length as required by the error message. Note that the  
error may be repeated for a single Map Descriptor when a new zone or  
device is stored because the storage location may be based on the  
zone or device number. Generally for zone storage the array must have  
at least 240 locations (and 128 for older Cheetah firmware.)5  
The Map Descriptor length must be sufficient to store all the data. The  
maximum device number is 255 and the maximum zone number is 255,  
therefore to store all zones and devices the MD's must be 256 elements  
long. Some legacy panels and message don’t support the full number  
of devices/zones. For example some panels only support 241 zones.  
Try and determine the correct length otherwise please use 256. If you  
are unsure ask tech support to provide the template file server.csv  
An internal diagnostic has been activated. This should not happen on a  
live system. Take a log and contact tech support  
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  
Messages are expected to begin with a Carriage return or SOH (0x01).  
The message has been rejected because it starts with the reported byte.  
Perhaps the vendor has changed firmware. If this error occurs  
repeatedly then take a log and contact tech support. If it occurs rarely  
then assume it is noise and ignore it if you are satisfied you are getting  
good data updates.  
Cheetah:# 18 Err. Bad msg  
start= %#x  
Cybercat panels transmit lagacy message which must be ignored. This  
message confirms the driver is ignoring them. No corrective action is  
required. If you are connected to a Cybercat panel and never see this  
message printed (checked the system and driver error message screen)  
then please take a log and contact Tech support.  
Cheetah:#19 FYI. Ignoring  
0x0100 messages from  
Cybercat.  
The driver is attempting to store zone status information from a  
Cybercat panel. The Data Array is too short. Adjust the length of the  
Data Array and the length of the Map Descriptor.5  
Cheetah:#20 Err. DA too  
short. Zone=%d MD=<%s>  
RQD=%d  
The driver is attempting to store device status information from a  
Cybercat panel. The Data Array is too short. Adjust the length of the  
Data Array and the length of the Map Descriptor.5  
Cheetah:#21. Err. DA too  
short. MapDesc=<%s>  
RQD=%d DA=%s  
Cheetah:#22 FYI. Node=%s These messages report the type of panel that the configuration is  
is a Cybercat panel.  
Cheetah:#23 FYI. Node=%s  
is a Cheetah panel.  
suitable for. If this isn’t what you expect, review the configuration  
against the manual and make changes as required. Refer to section 4.3  
for more information.5  
5
Modify the CSV file, download to the FieldServer and restart the FieldServer for the changes to take  
effect.  
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: [email protected]  
 
FS-8700-48 Fike Cheetah Manual  
Appendix B.1. Driver Stats  
Page 36 of 36  
Cheetah panels produce data messages for slave devices to consume. The type and  
frequency of the messages depends on the Cheetah firmware revision.  
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.  
The PLC_READ_MSG_RECD statistic is incremented once by each Map Descriptor which  
extracts data from an incoming message. Thus, one incoming message and three  
associated Map Descriptors would cause the statistic to increase 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.  
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: [email protected]  
 

Abocom Network Card WMB2000 User Manual
ADC Power Supply Power Distribution Products User Manual
ADIC Network Card 4000 User Manual
AEG Washer Dryer 14820 User Manual
Agri Fab Lawn Aerator 45 0346 User Manual
Avenview TV Cables HDMI C5SP 4 User Manual
Axis Communications Security Camera axis fixed dome network camera User Manual
Baby Einstein Bouncy Seat 30886 User Manual
Behringer Car Speaker MS20 User Manual
Behringer Music Pedal UM300 User Manual