User Guide
FS-8700-132 Gamewell FCI-E3 Driver Manual            Page 14 of 20 
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com 
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970  email: support@fieldserver.com 
Appendix A.2.  Extending the Event Table 
New event causes may be added to the Event Table and the index value or category of existing event 
causes modified by adding a section to the configuration CSV file. The examples below illustrate this: 
Example 1: Index value of 'Trouble' is updated to a new value of 100 
Driver_Table       
Event_Type_Description,
Event_Type_Index_Value,
Event_Type_Category ,  Protocol 
TROUBLE,  100,  4,  FCI_E3 
Example 2: New Entry is added 
Since  it  has  been  added  as  category=3,  only  Map  Descriptors  with  'Event  Type'  set  to  “Alarm”  or 
“Any” will capture messages with this event description 
Driver_Table       
Event_Type_Description,  Event_Type_Index_Value,  Event_Type_Category,  Protocol 
DESTROYED,  51,  3,  FCI_E3 
For categories use the following values 
'Other' = 1 
'Fault' = 2 
'Alarm' = 3 
'Trouble' = 4 
Appendix A.3.  How Data is stored 
All  messages  shorter  than  102 characters  are discarded  unless  they contain  information  identifying 
the networked/local panel. All other messages are processed as follows: 
•  The driver determines if the message is a Zone, Relay, Loop, Sensor, Module or Panel message. 
•  The driver finds all Map Descriptors with matching ‘Point Type’ parameters. 
•  The event category is determined. 
•  Map  Descriptor  selection  is  refined  based  on  whether  the  ‘Event  Type’  matches  or  has  been 
defined as “Any” 
•  The  driver  determines  the  Loop.  Relay, Zone,  Sensor  and  Module  numbers  from  the  message 
and refines its selection of Map Descriptors by selecting those that match the values determined 
from the message. 
•  The  selected  Map  Descriptors  are  now  used  to  determine  a  Data  Array  and  offset  at  which  to 
store the data. 
•  Finally the driver  checks  the  ‘Store  As’ parameter. If it hasn’t been  specified  then  ‘Index  Value’ 
storage is assumed.  If it has been specified as ‘Bits’ then the driver will perform ‘Bit Storage’.  In 
cases where the Map Descriptor has both a primary and secondary Data Array, the driver will use 
‘Index Value’ storage using the primary data array and ‘Bit Storage’ using the secondary array. 










