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.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 Example 4 – All Devices .............................................................................................. 18
5.4.10 Map Descriptor Example 5 (Specific Device) ........................................................................................ 19
5.4.11 Map Descriptor Example 6 - Device States as a Numeric Value .......................................................... 19
5.4.12 Map Descriptor Example 7 – Panel Data ............................................................................................. 20
5.4.13 Map Descriptor Example 8 – History Data (All Devices) ...................................................................... 20
5.4.14 Map Descriptor Example 9 – Full History Event Record – Specific Device ............................................ 21
5.4.15 Map Descriptor Example 10 – Full History Event Record – Any Device ................................................ 21
5.4.16 Map Descriptor Example 11 – Alarm Ack ............................................................................................. 22
6 Configuring the FieldServer as a Cheetah Device Server ............................................................................... 23
Appendix A. Useful Features ................................................................................................................................ 24
Appendix B. Vendor Information ......................................................................................................................... 25
Appendix B.1. Fike Cheetah Panel Firmware version sensitivity ............................................................................. 25
Appendix B.2. Fike XI Panel Limitations and capabilities ......................................................................................... 25
Appendix C. Troubleshooting ............................................................................................................................... 26
Appendix D. Reference ........................................................................................................................................ 29
Appendix D.3. Storing Panel Data ............................................................................................................................ 29
Appendix D.4. How History Events are Stored ........................................................................................................ 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The Cheetah Protocol driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS485 using the Cheetah device protocols (Legacy Cheetah Classic and the current Cheetah Xi).
The driver supports messages sent from the Cybercat panel. Specifically, the driver supports message 1.02 which
reports panel, zone 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 this driver
2.2 Provided by Supplier of 3
rd
Party Equipment
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
3.4 Connecting the Fiel dServer 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” to “Computer”
Set “Supervise” to “No”
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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.
Specify which port the device is
connected to the FieldServer
P1-P8, R1-R22
Baud*
Specify baud rate
9600 (Vendor limitation)
Parity*
Specify parity
None, (Vendor limitation)
Data_Bits*
Specify data bits
8 (Vendor limitation)
Stop_Bits*
Specify stop bits
1 (Vendor limitation)
Protocol
Specify protocol used
Cheetah (makes the port the exclusive domain of Cheetah
devices.) This keyword is not required when specifying the
port.
// Client Side Connections
Port
, Baud
, Protocol
, Parity
, Data_Bits
, Stop_Bits
P1
, 9600
, Cheetah
, None
, 8
, 1
5 CONFIGURING THE FIELDSERVER AS A CHEE TAH 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 Client.
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 “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 Parameters
Example
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