manualshive.com logo in svg

FieldServer Gamewell FCI E3 Series, Driver Manual

Share
Download
FieldServer Gamewell FCI E3 Series Driver Manual Download Page 6

FS-8700-132 Gamewell FCI-E3 Driver Manual 

 

 

 

 

 

Page 6 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

: [email protected] 

5

 

CONFIGURING THE FIELDSERVER AS A GAMEWELL FCI-E3 SERIES SERIAL 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 FCI Series E3.  

5.1

 

Client Side Connection  Parameters 

Section Title 

Connections 

Column Title 

Function 

Legal Values 

Port 

Specify  which  port  the  device  is  connected  to  the 
FieldServer 

P1-P8

1

 

Protocol 

Specify protocol used 

FCI_E3 

Baud* 

Specify baud rate 
Vendor  documentation  indicated  that  the  only  supported 
Baud  rate  was  9600.  During  testing  we  learned  this  was 
not  true.  The  driver  was  tested  at  57600  and  9600  baud. 
Testing  at  115200  Baud  produced  intermittent  result  and 
should not be used. 

9600

, 

57600 

(Vendor Limitation)  

Parity* 

Specify parity 

None

 

(Vendor 

Limitation) 

Data_Bits* 

Specify data bits 

8

 

(Vendor 

Limitation) 

Stop_Bits* 

Specify stop bits 

1

 

(Vendor 

Limitation) 

FCI_Max_Len_for_Node_line 

If  the  driver  is  allocating  an  alarm  sent  by  one  panel 
(device)  to  more  than  one  panel  inside  the  FieldServer 
then  use  this  parameter.    Increase  the  length  to  a 
maximum of 79 until the problem is resolved. 

Positive 

integer 

<80,

 68 

 

Example 

//    Client Side Connections 
 
Connections 
Port  , Protocol  , Baud  , Parity     
P1 

, FCI_E3 

, 9600  , None 

   

 

 

                                                                 

1

 Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available 

on specific hardware. 

Summary of Contents for Gamewell FCI E3 Series

Page 1: ...evision 5 A Sierra Monitor Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after September 2010 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 132 Gamewell FCI E3 Series Serial Driver ...

Page 2: ...t 6 5 1 Client Side Connection Parameters 6 5 2 Client Side Node Parameters 7 5 3 Client Side Map Descriptor Parameters 7 5 3 1 FieldServer Related Map Descriptor Parameters 7 5 3 2 Driver Related Map Descriptor Parameters 8 5 4 Map Descriptor Example 1 Sensor Module Events 9 5 5 Map Descriptor Example 2 Bit Storage 10 Appendix A Useful Features 11 Appendix A 1 Extending the Event Table 11 Appendi...

Page 3: ... status have to be synchronized manually This typically requires a panel reset The driver can process messages from networked panels The driver connects to the main panel Subsidiary panels are configured to send event data to the main panel which then sends messages to the FieldServer Node information is sent in the line preceding the event and the driver uses this to determine the panel at which ...

Page 4: ...NECTIONS The FieldServer is connected to the FCI E3 panel as shown in the connection drawing TB6 4 3 2 1 FieldServer FieldServer Part FS 8917 16 Pigtail for RJ45 Port RJ45 Connect to one of the RS 232 Ports on the FieldServer P1 Brown Blue white Orange White 1 8 Part of FCI E3 Panel ILI MB E3 Board Connector Pinouts Wire Color RJ 45 Gamewell FCI E3 Pin Signal Signal Pin Brown 1 Rx ve 2 White Orang...

Page 5: ...rays to facilitate correct storage of the relevant data Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format FLOAT BIT UInt16 SInt16 Byte Data_Array_Length Number of Data Objects Must be larger than the data storage area required by ...

Page 6: ...ort Specify which port the device is connected to the FieldServer P1 P8 1 Protocol Specify protocol used FCI_E3 Baud Specify baud rate Vendor documentation indicated that the only supported Baud rate was 9600 During testing we learned this was not true The driver was tested at 57600 and 9600 baud Testing at 115200 Baud produced intermittent result and should not be used 9600 57600 Vendor Limitatio...

Page 7: ... reset message s origin When set to Reset_by_this_Node_Only then the driver only resets the data associated with the given node if the reset originated from the same node Reset_by_any_Node Reset_by_this_Node_Only Connection Specify which port the device is connected to the FieldServer P1 P8 2 Example Client Side Nodes Nodes Node_Name Protocol Connection Panel 01 FCI_E3 P1 5 3 Client Side Map Descr...

Page 8: ...n the Point Type is Panel Point Type Relay 1 255 Point Type Zone 1 8 Point Type Loop 1 2 Point Type Module 1 2 Point Type Sensor 1 2 Whole Numbers 1 2 etc Length Each Map Descriptor defines storage locations for a series of addresses This parameter specifies the length of the series 1 2 3 etc Whole numbers Address This parameter is specific to Map Descriptors with Event Type Module or Sensor It sp...

Page 9: ... to suit the required data If all events are required the parameter should be set to Any Example Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Event Type Point Type Relay Loop Zone Number Address Length Clear_on_Reset ModuleData1 DA_MODULE 0 Passive_Client Panel 01 Alarm Module 1 1 99 Yes Unique Map Descriptor Names are recomme...

Page 10: ...usly In the Bit Array the driver sets the bit corresponding to the event leaving other bits unchanged thus the secondary storage can be used to determine if more than one event is active at a time Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset DA_Bit_Name Function Node_Name Event Type Point Type Relay Loop Zone Number Address Length Clear_on_Reset...

Page 11: ...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 2 Panel Synchronization Manual synchronization is required When the Reset button on the panel is pressed a message is transmitted to the FieldServer which clears the data in the FieldServer After a reset the panel sends messages to report all abnormal ...

Page 12: ...he Node of origin in a message preceding the event message Consult with FCI for information on how to achieve this Example of message sent by a panel that is networked The driver is dependent on seeing the node of event origin included in parenthesis before each event message Node02 MISSING Acclimate L1S041 00 17 06 01 01 06 Node55 1st Floor Lobby DISCONNECT RSTRD Ion Detector L1S024 09 51 44 01 1...

Page 13: ...fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com Appendix B Troubleshooting If the driver is sending the same alarm to a number or external nodes an error may be reported In this case specify the connection parameter FCI_Max_Len_for_Node_line Refer to Section 5 1 for more information ...

Page 14: ... 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 Appendix C 1 1 Example The following fragment is part of a Map Descriptor definition some parameters have been omitted for the purposes of clarity Map_Descriptors Data_Array_Name Data_Array_Offset Event Type Po...

Page 15: ...Array modifies it and writes it back Since the index value is 34 the driver modifies the 34 th bit or expressed another way the driver modifies the 2 nd bit 34 32 at offset 1 Thus the driver calculates the offset for Bit Storage as 2 x 21 42 The driver sees that bit 34 is 2 2 nd bit in the next offset and so the driver reads DB_MODU 43 modifies the value by setting the 2nd bit on and then writing ...

Page 16: ...ENT_TYPE_OTHER RZA Fault 3 24 FCI_EVENT_TYPE_OTHER Verify 3 25 FCI_EVENT_TYPE_OTHER CM Short 3 26 FCI_EVENT_TYPE_OTHER Test Fail 27 FCI_EVENT_TYPE_OTHER Alert 28 FCI_EVENT_TYPE_OTHER Dirty 29 FCI_EVENT_TYPE_OTHER Very Dirty 30 FCI_EVENT_TYPE_OTHER Missing 31 FCI_EVENT_TYPE_OTHER Wrong Type 32 FCI_EVENT_TYPE_OTHER Extra Addr 33 FCI_EVENT_TYPE_OTHER Clock Err 3 34 FCI_EVENT_TYPE_TRBLE Trouble 3 35 F...

Page 17: ...CI_E3 8 FYI Reset was rcvd and processed Stamped s s drv_bd time drv_bd date Printed for information only No action required FCI_E3 9 Err Reset was ignored A reset was received but the driver could not reset any data Clear_on_Reset possibly set to no on all Map Descriptors FCI_E3 10 FYI Reset of DA s Off d Len d possible_md data buffer_name possible_md bxi_data_buffer_offset possible_md data_lengt...

Page 18: ...nized Valid Event Types are listed in section 5 3 2 5 FCI_E3 24 Err Undefined Event Type FCI_E3 25a Err Address Length 99 Length Truncated The maximum value for a sensor module is 99 The combination of address and length specified produce a number 99 5 FCI_E3 25b Err Address Length 99 Length Truncated FCI_E3 26 Err Invalid Module number Expected 1 99 Correct the configuration file 5 FCI_E3 27a Err...

Page 19: ...escriptor to store Relay data FCI_E3_STAT_NO_PLACE_TO_STORE_LOOP 4 Increments each time point data is received but there is no Map Descriptor to store the Loop data FCI_E3_STAT_NO_PLACE_TO_STORE_SENSOR 5 Increments each time point data is received but there is no Map Descriptor to store the Sensor data FCI_E3_STAT_NO_PLACE_TO_STORE_MODULE 6 Increments each time point data is received but there is ...

Page 20: ...ty message lines FCI_E3_STAT_PARSED_WITH_ERRS 16 Increments each time a message produces an error when parsed FCI_E3_STAT_INHIBIT_RESET 17 Set to 1 to inhibit resets altogether FCI_E3_STAT_INHIBIT_RESET_DA_PUT 18 Set to 1 to inhibit resets from clearing arrays FCI_E3_STAT_INHIBIT_RESET_WHILE 19 Set to 1 to inhibit the reset function from looping through Map Descriptors FCI_E3_STAT_NODE_INFO_MSG 20...

Reviews:

No comments

Brands by name

Popular brands

Load more brands