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
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
Flat 6 way cable (7 foot) for RJ11 connection
FS-8915-10 UTP cable (7 foot) for RS-232 use
RJ45 to DB25F connector adapter
RJ11 to DB25M connection adapter
FS-8700-48 Driver Manual.
Description
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
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.
is connected to the
FieldServer
This parameter tells the
driver what type of panel you
PLC_TYPE
are connecting to. If not
specified, the driver expects
that you are connecting to a
legacy Cheetah panel.
Example
// Client Side Nodes
Nodes
Node_Name, Protocol, Port
Cheet_Master1, Cheetah, P8
Up to 32 alphanumeric
characters
This parameter is not
required for Cheetah devices.
P1-P8, R1-R23
'Cybercat' , 'Cheetah'
4.4. Client Side Map Descriptors
4.4.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
Data_Array_Name
data is to be stored in the
FieldServer
Data_Array_Location Starting location in Data Array
Function
Function of Client Map
Descriptor
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.
Up to 32 alphanumeric
characters
One of the Data Array names
from “Data Array” section
above
0 to maximum specified in
“Data Array” section above
RDBC, WRBC, WRBX,
PASSIVE
Only the keyword passive may
be used for Cheetah devices.
Up to 32 alphanumeric
characters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com