FS-8700-68 – CEI-ABI

FieldServer Driver – Serial





This FieldServer driver can be used to poll or emulate EN.54 Exchanges.  The driver also supports a data tap mode to simply collect data from exchanges if another device is already polling the exchanges.  The driver can handle 5 exchanges in full configurations (80 zones, 16 loops per exchange).

The driver starts up in a configuration mode during which configuration data is fetched from the exchanges to determine the zone labels and point to zone mappings.  After finishing configuration mode, the driver proceeds to normally poll the exchanges for alarm, trouble or event data on points and zones.  The driver also supports the special event code 138 from exchanges which is used to indicate that a programming change has taken place on the exchange.  The driver will enter configuration mode again after receiving this event code to update the change i.e. a zone label has been changed.

The driver now also supports the sending of general resets.  The data tap looks for a command accepted response from an exchange or server before clearing the point status and point faults bitmap data arrays. The server will also clear point statuses when receiving the reset command.  The client or master driver will only reset its own point statuses and point faults bitmap data arrays when the server responds with a command accepted message.


Client and Data Tap Configuration File Structure

The client can poll exchanges or act as a data tap when specifying a node_type of Data_Tap in the connection setup.

Data from the exchanges can be stored in data arrays by specifying the cei data type in the map descriptors. The following cei data types can be used:

Cei data type Description
Points Point statuses ( 0=Normal, 1=Alarm, etc )
P_faults_bmp Point faults bitmap (0=Normal, 1=Fault).  Faults are alarms and troubles combined.
analogs Point analog values 0-255
P_devices Point devices that caused the event ( refer to CEI-ABI for list )
P_events Point event codes associated with statuses ( refer to CEI-ABI for list )
Zones Zone statuses ( 0=Normal, etc )
Z_devices Zone devices that caused the event ( refer to CEI-ABI for list )
Z_events Zone event codes associated with statuses ( refer to CEI-ABI for list )
Labels Zone labels ( 32 characters per zone )
Zone_points Point statuses per zone as defined in setup data
Setup Point to zone mappings setup data

Every map descriptor also maps to a specific exchange address’ data. The addresses may be 1,2,4,8 and 16 giving a total of 5 exchanges on a port.

The data arrays must be set up to provide enough storage space for a fully configured exchange. The needed space for data arrays can be calculated by noting an exchange’s setup:


Example: Loops

Exchanges have 16 loops each. Each loop contains 99 sensors and 99 modules. A loop therefore contains 99 * 2 = 198 points. The collection of all the sensors and all the modules on all the loops are collectively referred to as points. A total of 16 * 198 = 3,168 points exist on an exchange. Data arrays for point statuses, analog values, point device codes and point event codes need to be each at least 3,168 bytes long per exchange.


Example: Zones

Exchanges have 80 zones each. Each zone’s zone label consists of 32 characters (bytes) giving a total of 80 * 32 = 2,560 characters for the zone labels on one exchange. The zone statuses, zone device codes and zone event codes can each be stored in a data array of 80 bytes per exchange. Finally, the zone setup data is also stored on the client. The zone setup data consists of 64 bytes per zone on an exchange. This gives 80 * 64 = 5,120 bytes of storage needed. The zone setup data provides the mapping of points to zones. Each zone can have 32 points mapped into it.


Reset configuration:

A client only map descriptor with a cei data type of “reset” can be added to the configuration file. The client driver monitors the databit pointed to by the reset map descriptor. Whenever the databit goes high, the client will send a reset to the server. It will reset the databit to zero before sending the reset. No reset map descriptors must be added to the data tap and server configuration files.


Server Configuration File Structure

The driver can also be used to emulate an EN.54 Exchange. The following cei data types may be used to specify the type of data in storage data arrays:

Cei data type Description
points Point statuses ( 0=Normal, 1=Alarm, etc )
analogs Point analog values 0-255
devices Point or zone devices that caused the event ( refer to CEI-ABI for list )
events Point or zone event codes associated with statuses ( refer to CEI-ABI for list )
zones Zone statuses ( 0=Normal, etc )
labels Zone labels ( 32 characters per zone )
setup Point to zone mappings setup data


The driver server will respond to configuration (alignment) requests as well as normal polling from the client driver.


Formal Driver Type


Client or Server/Passive Client


Compatibility Matrix

FieldServer Model Compatible with this driver
FS-x2010 Yes, No
FS-x2011 Yes, No
FS-x40 Yes, No
FS-x30 No


Connection Information

Connection type: RS-232 or RS-485 (Two wire, Half-Duplex)
Baud Rates: 2400, 4800, 9600, 19200  (Vendor limitation)
Data Bits: 8
Stop Bits: 1
Parity: Even
Multidrop Capability Yes


Proprietary Physical Interfaces Supported

Fieldserver Model Adapter Model # Vendor Physical Medium


Devices tested

Device Tested (FACTORY, SITE)
EN.54 Exchanges, Models AM-6000, AM-2000, FSP-402 SITE


Connection configurations

Hardware Connections















TX RJ45-01


RX RJ45-08


GND RJ45-04













Note:          For wiring of maximum 25 meters use 232 serial line (terminals 4-5-6)

For wiring exceeding 15 meters use 485 serial line with IT-485 interface (terminals 7-11)


Connection Notes

If the FieldServer is to be connected to the Serial Printer Port of the AM6000 Panel, use the Driver “FS-8700-52 Notifier Italia AM6000″.  If the FieldServer is to be connected to the AM6000 panel using an SIB-600 device, use the Driver “FS-8700-68 CEI ABI

The FieldServer is connected to the En.54 exchange as shown below.  Configure the En.54 exchange according to manufacturer’s instructions.


If you liked this post;
  • Please consider subscribing to our RSS feed