Fike Cheetah Gateway || Fike Cheetah Conversion
A great solution to The Fike Cheetah Protocol driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS-485 and provide that data on other protocol Networks like BACnet, Modbus, Lonworks, SNMP, Metasys N2  and others.

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 Fike Cheetah controller.

 
DOWNLOAD DATASHEET
 

                                                                                                                                                                                                                                    Question/Purchase


FieldServer Hardware platforms supporting Fike Cheetah protocol

Device type

RS 485/232 ports

Lonworks Ports

Available Ethernet ports

Base Point count capacity

Extended Point count capacity

QuickServer

2

0

1

250

1000

QuickServer Lonworks

1

1

1

250

1000

Enhanced QuickServer

2

0

1

500

1000

Enhanced QuickServer Lonworks

1

1

1

500

1000

How to configure the FieldServer Gateway?

  • We will configure the Gateway for you based on your requirement and support you during commissioning of the Gateway, so you do not have to worry about configuring the FieldServer Gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals with be provided completely free of cost with your purchase.
  • Configuration of the FieldServer is done using a '.csv' file. This file can be edited using any text editor (example Microsoft excel).
  • In this file we need to enter information for the Client and Server side interfaces of the FieldServer. This includes but is not limited to:

a.                     Node ids of the slave devices

b.                     MSTP addresses/device address of the slave devices

c.                     Baud rate, parity, stop bits for serial communication

d.                     Scan rates

  • And finally we need to create an internal mapping that would map each data value read on the client side to a data value on the server side.
  • For detailed information on configuration please get in touch with us and review the configuration manual on top of this page