FieldServer FCI 7100 Series Computer Drive User Manual
Contents
1. ccceeeeeeeeee 18 FS 8700 112 FCI 7100 Series Driver Manual Page 3 of 24 1 FCI 7100 Series Serial Driver Description The FCI 7100 Series System Control Units are manufactured by Fire Control Instruments A 7100 with an enabled serial port can transmit data to a FieldServer which can in turn make the data available to other devices including those which communicate using different protocols e g BACnet This passive Client driver does not poll for data nor does it send data or commands to the 7100 Messages received from the 7100 are ignored or stored on the FieldServer depending on the status of the panel The method of message processing and location on the FieldServer is determined in the FieldServer configuration file Once stored in the FieldServer the data is available to be read or written using other protocols such as BACnet No automatic panel data synchronization technique exists The data in the FieldServer and the panel status have to be synchronized manually This typically requires a panel reset Since the driver cannot send data or commands to the 7100 it cannot be used to acknowledge silence or reset alarms and other events The driver can process the single line messages sent from 7100 firmware versions earlier than 2 20 and 3 line messages produced in firmware versions 2 20 and later Processing of 3 line messages requires the 20 character System ID label to be defined The driver can process messages from ne2. Sensor for specifies the events will be sensors starting Module stored number and the Length tells the Messages driver the range reporting other of Modules events will be ignored unless In this example other MD s are Module 1 to 99 defined that you allocate unique MD names FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 13 of 24 4 6 Map Descriptor Example 2 Bit Storage This example defines storage location for Relay Point events The example would work for all other point types In the example both primary and secondary storage Data Arrays have been specified The driver stores index values in the primary array Each new event for a particular relay will overwrite the value stored previously In the Bit Array the driver sets the bit corresponding to the event leaving other bits unchanged thus the 2ndary 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 Bay ne A A Address Length Clear_on_reset RelayData DA_RELAY 0 DB Relay Passive Client Panel 01 Any Relay ls 4 Yes MD s for storing Relay D
3. ccceeeecceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaeeeeeeesaaeeeeeeas 4 3 Client Side Node Descriptors s1sctac5 4 chadetcahtretee Oheendhechae ined Godan aaa 4 4 Client Side Map Descriptors cciisccsss scot tcttees Aucctani eel salads eae 10 4 4 1 FieldServer Related Map Descriptor Parameters ccccccccccccsteeteseteeeeeesseeeertees 10 4 4 2 Driver Related Map Descriptor Parameters 0 ceeccccccccenneteeeeeeteeeenteeeeeeeeeneeennee 10 44 3 4 TUG Paranee Soie ihe i ti a ace asc eh ANAL A ih nce ee RRN 11 4 5 Map Descriptor Example 1 Sensor Module Events ccccceeeeeeceeeeeeeeeeeeeeeeees 12 4 6 Map Descriptor Example 2 Bit Storage ccceceeeeeeeeeseceeeeeeeeeeeeeeseceeeeseeaeeeeneenaes 13 5 CONFIGURING THE FIELDSERVER AS A FCI 7100 SERIES SERIAL DRIVER oo gg MM me ek pr er por eS ire near Ser ry Se ark Suara ee saree ot hE Me reer ioe 14 APPENDIX A ADVANCED TOPICS eroinin an histo Hansa es 15 Appendix A 1 Events and Event Categories ecccccceeeeseeeeeeeeeeeeeeeeeeaeeeeeensaaeeeeensaaeeeeneas 15 Appendix A 2 Extending the Event Table iss sssccinciccecranheder edie ie seseintoontnent aadieels 16 Appendix A 3 How Data is stored evestcccfjiciteotavsenaeedieelonenietiastaveh aaeeaueeeaidioiiae Hewbaeveincee 16 Appendix A 4 Panel Synchronization cccccceeeeeseeeeeeeeeeeeeeeeeaeeeeeeeeaaeeeeeesaaaeeeesssaaeeeenaas 18 Appendix A 5 What happens when the panel sends a Reset Message
4. California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com
5. Client 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 Section Title Data_Arrays Column Title Function Legal Values Up to 15 alphanumeric Data_Array_Name Provide name for Data Array charactere Float Bit Ulnt16 SInt16 Provide data format Each Data Packed_Bit Byte Array can only take on one format Packed_Byte Swapped_Byte Data_Array_Format Number of Data Objects Must be larger than the data storage area Data_Array_Lengin required by the Map Descriptors for Ta 000 the data being placed in this array Example Data Arrays Data_Arrays Data_Array_Name Data_Array_Format Data_Array_Length DA Al_01 Ulnt16 200 DA_AO 01 Ulnt16 200 DA_DI_01 Bit 200 DA_DO 01 Bit 200 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 8 of 24 4 2 Client Side Connection Descriptions Section Title Connections Column Title Function Legal Values Specify which port the device is 1 Bass connected to the FieldServer pire ene FCI_ 7100 FCI 7100 series Protocol Specify protocol used FCI7100 Baud Specify baud rate 1200 Vendor Limi
6. FS 8700 112 FCI 7100 Series Driver Manual Page 22 of 24 Appendix B 1 Driver Stats Exposed In addition to the standard FieldServer operating statistics the driver exposes certain key stats in a Data Array if required An upstream device can then monitor these stats Add the following to your configuration file to activate these stats Expose Driver Operating Stats Data_Arrays Data_Array_Name Data_Format Data_Array_Length fci 7100 stats UINT32 200 The driver exposes stats based on a port handle The offset specified in the table below must be added to the handle number multiplied by 100 i e for port whose handle is 1 then the driver will store the 1 stat at 1 100 1 101 Stat Offset Description Increments each time point data is received but there is no Map define FCl_7100_ STAT NO PLACE_TO STORE 1 Descriptor to store the data any Increments each time point data define 2 is received but there is no Ma FCIL_7100_ STAT_NO_PLACE_TO_STORE_ZONE P Descriptor to store Zone data define Increments each time point data FCI_7100_STAT_NO_PLACE_TO_STORE_RELAY is received but there is no Map Descriptor to store Relay data Increments each time point data 4 is received but there is no MD to store the Loop data Increments each time point data 5 is received but there is no MD to store the Sensor data Increments each time point data 6 is received but there is no MD to store the Module data N
7. the Data Array offset and the length The driver also clears the relevant sections of a Data Array specified with the DA_Bit_Name parameter The process can take some time For this reason it is suggested that you take care not to set MD length to a value larger than necessary Additional considerations apply when panels are connected together in an FCI network See Appendix A 6 Networked Panels The driver can processes messages and store data from multiple panels provided that e The panels are connected in an FCI network and the panels are configured to report their events to the main panel e The main panel is configured to send the 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 E aSo ign eer Node02 MISSING PROJ MANG OFFICE Thermal Det L1S02 00 40 18 01 01 99 Roos EE Local RESET 00 40 18 01 01 99 The main panel is identified as Local The driver interprets this as Node_ID 0 To capture events from multiple networked panels you need one Node Descriptor for each panel with the appropriate Node_ID Each node requires a set of Map Descriptors FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408
8. 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 21 of 24 Message Description FCI7100 28 Invalid Sensor number Expected 1 99 Err FCI7100 29 Err Invalid Zone number Expected 1 255 FCI7100 30 Err Invalid Relay number Expected 1 3255 Correct the configuration file FCI7100 31 Err Point Type Invalid Valid Point Types are listed in Section 4 4 24 FCI7100 32 Err No MD Length Default to 1 You must specify the length of each Map Descriptor Refer to Section 4 4 2 FCI7100 33 Err Driver cant poll or write The driver can only listen passively for message from the panel Remove any active Map _ Descriptors from the configuration file FCI7100 36 Err Too Short Bytes d conn gt ux_iptr An event message is less than 80 bytes long If this error is repeated often it is possible that a FCI firmware update as made the driver unusable Take a log and contact tech support 4 Correct the configuration file download to the FieldServer and restart the FieldServer for the changes to take effect FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com
9. 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Appendix B Driver Error Messages Page 19 of 24 Message Description FCI7100 1 FYI Use a DA called lt s gt to expose diagnostic info FClL_7100 STATS DA Refer to Appendix B 1 FCI7100 2 FYI Added Event Desc lt s gt Index d Categ d new_event_desc new_event_desc_index_value new_event_desc_categ Printed for your info only No action required if it confirms your expectations FCI7100 3 Err No space Reject Event Desc lt s gt Index d new_event_desc new_event_desc_index_value There is only space for 60 event types FCI7100 4 FYI Duplicate Event Desc lt s gt new_event_desc You are adding an event type that already exists If you are updating the category ignore the message Otherwise correct the configuration file FCI7100 5 FYI Duplicate Event Desc lt s gt new_event_desc You are adding an event type that already exists If you are updating the index value ignore the message Otherwise correct the configuration file FCI7100 6 Err Event Index d Too big to set bit drv_bd gt event_index If the event index is greater than 64 then the data cannot be stored as bits as only 64 bits are reserved for events FCI7100 7a Err DA s too short Rad d dt gt buffer_name offset FCI7100 7b Err DA s t
10. 700 112 FCI 7100 Series Driver Manual Page 20 of 24 Message Description FCI7100 4 12a Err No MD s to store message data FCI7100 4 12b Err No MD s to store message data FCI7100 13 Err Msg was ignored MD Required for Storage FCI7100 13a Err Diagnostic 1 FCI7100 13b Err Diagnostic 2 FCI7100 13c Err Diagnostic 3 A message arrived and the driver could not find a place to store the data Perhaps you were not expecting this type of event this loop sensor If you are not interested in the data then ignore the message Otherwise update the configuration file Take a log Try and repeat the event that caused the message to be printed Then contact tech support FCI7100 14 Err lt s gt file not found md gt mapdesc_name FCI7100 15 Err Event Type lt s gt Not recognized drv_bd gt event_desc FCI7100 4 16 Err Point Type c x Not recognized drv_bd gt point_identifier 0 drv_bd gt point_identifier O If this error is repeated often it is possible that a FCI firmware update as made the driver unusable Take a log and contact tech support FCI7100 417 Err drv_bd gt loop Loop d lt 1 Rejected This message should only be printed if a byte in a message has been corrupted If you notice it more than once then take a log and contact tech support FCI7100 4 18 Err Loop Type c x Not recognized drv_bd g
11. 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 6 of 24 Top right hand side of TROUBLE ACKNOWLEDGE TT Connector J3 label on right FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 7 of 24 4 Configuring the FieldServer as a FCI 7100 Series Serial Driver Client For a detailed di7100ssion 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 7100 Series 7100 4 1 Data Arrays Descriptors The configuration file tells the FieldServer about its interfaces and the routing of data required In order to enable the FieldServer for FCI 7100 Series Serial Driver 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 Client Side Nodes section and the data required from the servers needs to be mapped in the
12. FieldServer Technologies A Sierra Monitor Company Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 112 FCI 7100 Series Serial Driver APPLICABILITY amp EFFECTIVITY Effective for all systems manufactured after May 1 2001 FS 8700 112_FCl_ 7100 Driver Manual Table of Contents TABLE OF CONTENTS 1 FCI 7100 SERIES SERIAL DRIVER DESCRIPTION s ecccseeeeeeseeeeeeeeeeeseeeseeeeeeseeeeees 2 DRIVER SCOPE OF SUPPLY ix iis cotet cis scscsrete hens st mtananhe Ea aaa iadaa tiid acta rae eae 2 1 Supplied by FieldServer Technologies for this driver ccccceeeeeeeeeeeeeeeeeeeeeeenaeeeteees 2 2 Provided by the Supplier of 3 Party EQUIDMENT ccccccscseseecsesseeescecscseeenecseseteneesees 2 2 1 Required 3 Party Hardware ciscivcic i acca estes Bivins 2 2 2 Required 3 Party Software scifi eck ccick ects hata ces tect aaa eee Bait ota tan out abi 2 2 3 Required 3 Party Configuration lt fcte cies rctl ee Shi Movs hel lake Nada cocks tc kM Zee ODUONAIMCTNS EF we seston teers aera Beh aria aa tate Coasts eo ren oad ot nahh oy G E 3 HARDWARE CONNECTIONS is sacscdesuccsassctasack dans dctecedsvcscudcacasescabeteawascavatcantoserecatreaveantiae 4 CONFIGURING THE FIELDSERVER AS A FCI 7100 SERIES SERIAL DRIVER 4 1 Data Arrays DESCriIPIONS a cece accuses cece accede shan ates Sag at ag ance Owens dudes cates aha nosaandineaaehees 4 2 Client Side Connection Descriptions 0
13. Technologies so PART Description FS 8915 10 UTP cable 7 foot for Ethernet connection RJ45 RJ11 12 Cable assembly for FS connection to FCI 23069 panel FS 8700 110 Driver Manual 2 2 Provided by the Supplier of 3 Party Equipment 2 2 1 Required 3 Party Hardware FCI Panel must be equipped with a RS 232 Serial Printer Port FCI Panel must be equipped with a PTRN module for isolation of the serial port 2 2 2 Required 3 Party Software None 2 2 3 Required 3 Party Configuration None known 2 2 4 Optional Items None FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual 3 Hardware Connections Page 5 of 24 The FieldServer is connected to the FCI panel as shown in the connection drawing 3 Wire Cable Tx Rx Gnd One Panel per Port FieldServer provide a pre fabricated cable NMWROID Panel FieldServer In this view the RJ12 and RJ45 converter clips are facing away from the viewer and are not visible Eee ee eae nee oan FCI 7100 Series Panel Raraserver Technologies 408 262 2299 FIELDSERVER FCI 7100 CONNECTION DIAGRAM DATE 3 1 05 BY MF BASE NAME FILE NAME FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262
14. ata_Array_Name is where the primary DA is specified Index values are stored here Loop Zone and Panel do not need the address specified DA_Bit_Name is where secondary storage is defined Events are stored by setting appropriate bits Remember that 2 elements per Relay Module Sensor Loop are used FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 14 of 24 5 Configuring the FieldServer as a FCI 7100 Series Serial Driver Server The server side of the driver is intended to support FieldServer s Quality Assurance program and is not intended to provide complete emulation of a 7100 and is thus not fully documented Should you require the Server side functionality to be documented and enhanced please contact FieldServer s sales group FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 15 of 24 Appendix A Advanced Topics Appendix A 1 Events and Event Categories The driver reports the event cause using the matching index value There are 4 event categories 1 Other 3 Alarm 2 Fault 4 Trouble The message category must match the Even
15. b www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 12 of 24 4 5 Map Descriptor Example 1 Sensor Module Events If messages from Loop 1 Module 1 to 99 are received then the MD in this example will be used for storage If you have modules on more than one loop then you will need one MD for each loop In this example the event type was set to Alarm This means that only Alarm events will be stored using this MD This could be useful if you are only interested one category of events If you want all events stored then change the Event Type to Any Example F S E C CR LF FIRST ALARM UP STAIRS N ENT Manual Station L1M21 00 37 28 01 01 99 CR LF _ Client Side Map Descriptors Map_ Descriptors Event Point Relay Loop Zone Type Type Number ModuleData1 DA_MODULE 0 Passive Client Panel 01 Alarm Module 1 il Address Length Clear_on_reset 99 Map_Descriptor Name Data_Array Name Data_Array_ Offset Function Node_Name Yes Tell the driver The the Data Array listens name and passively for starting location messages from that data should the Panel It be stored cannot poll for data The name of the Node defined in the Node Descriptor It is driver recommended In this example Change this to The address only Alarm
16. odifies the 2 bit 34 32 at offset 1 Thus driver calculates the offset for Bit Storage as 2 x 21 42 The driver sees that bit 34 is 2 2 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 the modified value back During the modification all other bits are left intact This using the Bit Storage method a single Module or sensor can keep track of multiple events FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 18 of 24 Appendix A 4 Panel Synchronization Manual synchronization is required Push the reset button on the panel This transmits a reset message to the FieldServer which clears the data in the FieldServer After a reset the panel sends messages to report all abnormal states When all these messages have been processed the FieldServer and panel will be synchronized This process can be repeated at any time Appendix A 5 What happens when the panel sends a Reset Message When a panel sends a reset message the driver processes every single Map Descriptor looking at the Clear on Reset parameter See section 4 4 2 If the parameter is set to yes then the driver sets all the Data Array elements referenced by the Map Descriptor to zero by looking up the DA Name
17. ogies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 11 of 24 Column Title Function Legal Values Address This parameter is only considered for those Map Descriptors whose Event Type is Module or Sensor It specifies the starting module or sensor number The length parameter the determines the range of the sensor module numbers Store As By default the driver stores using the Index Value Method Set this parameter to Bit to have the driver use the primary Data Array to store using the Bit Storage Method These methods are described in Appendix A 3 Bit Index_ Value DA_Bit_Name If the default Store As is specified or if the parameter is omitted then you can specify a secondary array using this parameter the driver will store event data as Bit Storage in the secondary array and as Index Values in the primary array These methods are described in Appendix A 3 One of the Data Array names from Data Array section above Clear on Reset If a reset if received you can prevent the driver resetting the Data Array Points associated with the Map Descriptor by specifying this parameter Yes No FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA We
18. one node connected per FieldServer serial descriptor for each panel setting port In networked configurations the Node_ID to the panel number specify whole numbers 0 1 2 3 f FCI_7100 FCI_7100_series Protocol Specify protocol used FCI7100 FCI Reset_ Acti Only required for networked configurations This parameter tells the driver what to do with Reset messages When not specified or set to Reset_by_any_Node then the driver will reset the data array points associated with the given Reset_by_any_Node on_Option node irrespective of the reset Reset_by_this Node_Only 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 Specify which port the device is g JSA onneaan connected to the FieldServer a a Example Client Side Nodes Nodes Node_Name Protocol Connection Panel 01 FCI_7100 P8 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 10 of 24 4 4 Client Side Map Descriptors 4 4 1 FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Name of this Map Up to 32 alphanumeric Map_Descriptor_Name Descripto
19. oo short Rqad d possible_md gt data gt buffer_name offset The MD in question has a length and offset which makes it run past the end of the Data Array Message 7b is printed when data is being stored as bits FCI7100 8 FYI Reset was rcvd and processed Stamped s s drv_bd gt time drv_bd gt date Printed for your info only No action required FCI7100 9 Err Reset was ignored FCI7100 10 FYI Reset of DA s Off d Len d possible _md gt data gt buffer_name possible_md gt bxi_data_buffer_offset 5 possible_md gt data_length This message is printed when a reset was received but for one or more reason the driver could not reset any data Have you set Clear_on_Reset to no on all MD s Printed for your info only No action required FCI7100 11 Err Cant reset DA s len d rqd d possible_md gt data gt buffer_name 7 da_get_length_in_items DAH_TYP possible_md gt data possible_md gt data_length possible_md gt bxi_data_buffer_offset The MD in question has a length and offset which makes it run past the end of the Data Array Correct the configuration file download to the FieldServer and restart the FieldServer for the changes to take effect FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8
20. p 1 Module 22 Since all the MD s in the example have a Point Type Module they are all considered for storage The driver looks in the Event Table and finds it has an index value of 34 and a category of 4 Trouble Only the MD s with Event Type set to Any and Trouble are now considered Since the value of the Relay Loop Zone parameter matches the Loop number in the message these MD s remain in contention The Module number of 22 is compared with the MD s Address and Length Parameters The Address is the starting number and the length defines the range Both MD s have addresses of 1 and length of 99 and thus both are still selected because the Module of 22 falls in this range The driver calculates an offset based on the offset specified in the MD and the Module number relative to the MD s address MD Offset 0 MD Address 1 Message Module 22 Module 1 s data is stored at offset 0 and hence Module 22 s data will be stored at offset 21 The driver stores the value 34 at offset 21 overwriting any data previously stored at that location This is Index Value Storage Seconday storage has been defined using the DA_Bit_Name Data Array The driver doubles the offset as two locations are used for each address Then the driver reads the value found in the Data_Array modifies it and writes it back As the index value is 34 the driver modifies the 34 bit or expressed another way the driver m
21. r characters ae eee fast One of the Data Array Data_Array_Name stored i the ieee Bole Data Array FieldServer Data_Array_Offset Starting location in Data Array 0 to maximum specified in Data Array section above Function of Client Map Function Descriptor Server Passive_ Client 4 4 2 Driver Related Map Descriptor Parameters Column Title Function Legal Values One of the node Node_ Name Name of Node to fetch data from names specified in Section 4 3 This driver uses this parameter to determine the suitability of a Map Descriptor when looking for a location to store data from an incoming message Event Type A Map Descriptor may be defined to store eer only Alarm Fault Trouble or Other events i Alternatively specify Any A table of events vs categories is provided in Appendix A 1 This driver uses this parameter to determine Point Type the suitability of a Map Descriptor when or Pils looking for a location to store data from an M f odule Panel incoming message Ignored when the Point Type is Panel Point Type Relay 1 255 Relay Loop Zone Point Type Zone 1 8 Whole Numbers Number Point Type Loop 1 2 1 2 etc Point Type Module 1 2 Point Type Sensor 1 2 Each Map Descriptor defines storage 1 2 3 etc Length locations for a series of addresses This Whole n mbers parameter specifies the length of the series FieldServer Technol
22. river_Table Event_Type_ Description Event_Type_Index_Value Event_Type Category Protocol TROUBLE 100 4 FCI_7200 Example 2 New Entry is added Since it has been added as category 3 only MD s 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_7200 For categories use the following values Other 1 Fault 2 Alarm 3 Trouble 4 Appendix A 3 How Data is stored All messages less than 102 characters long are discarded All other messages are processed as follows e The driver determines if the message is a Zone Relay Loop Sensor Module or Panel message e The driver finds all Map Descriptors with matching Point Type parameters e The event category is determined e Map Descriptor selection is refined based on whether the Event Type matches or has been defined as Any e 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 e The selected Map Descriptors are now used to determine a data array and offset at which to store the data e Finally the driver checks the Store As parameter If it hasn t been specified then Index Value storage is assumed If it has been
23. sed without errors Excludes Reset Messages define FCI_7100_STAT_PARSED_NO_ERRS_RESET Increments each time a reset message is parsed without errors define FCI_7100_STAT_PARSED_NO_ACTION Increments each time a message is parsed with no errors but the nature of the message doesnt require data to be stored eg empty msg lines define FCI_7100_STAT_PARSED_WITH_ERRS Increments each time a message produces an error when parsed define FCI_7100_STAT_INHIBIT_RESET Set to 1 to inhibit resets altogether define FCI_7100_STAT_INHIBIT_RESET_DA_PUT Set to 1 to inhibit resets from clearing arrays define FCI_7100_STAT_INHIBIT_RESET_WHILE Set to 1 to inhibit reset function from looping thru MD s define FCI_7100_STAT_NODE_INFO_MSG 20 Increments each time a message with node information is received define FCI_7100_STAT_NO_PLACE_TO_STORE_NODE 21 Increments each time an event needs to be stored the event contains node info and the node cannot be found so there is no match and the message was discarded FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 24 of 24 THIS PAGE INTENTIONALLY LEFT BLANK FieldServer Technologies 1991 Tarob Court Milpitas
24. 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 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 17 of 24 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 Point Type Relay Loop Zone Number Address Length Clear_on_reset DA _Bit_Name DA_MODU 0 ANY Module ile le 99 Yes DB_MODU DA_MODU _A 0 ALARM Module 1 i 99 Yes DB_MODU_A DA_MODU F 0 FAULT Module il Il 99 Yes DB_MODU_F DA_MODU_T 0 TROUBLE Module le le 99 Yes DB_MODU_T DA_MPODU_O 0 OTHER Module le ly 99 Yes DB_MODU_O Message FAULT AC Power 7100 0 00 04 1 01 92 This message does not report the status of a Zone Relay Loop Sensor or Module and is therefore assumed to be a panel message Since there is no MD with Point Type Panel the message is ignored Message TROUBLE QZUb L1M22 lt lt Chief s Office gt gt 5 24 00 3 03 93 This message reports status for Loo
25. t Type parameter specified on a Map Descriptor before that Map Descriptor can be considered for storage of the message data Index Category Event 1 2 Fault 2 1 Short 3 1 Disconnect 4 1 Comm Fault 5 1 Config Err 6 1 Eeprom Bad 7 1 Reset 8 1 Silence 9 1 Cross Zone 10 1 Acknwldgd 11 1 Walk Test 12 1 Alarm Test 13 1 SPVSN Test 14 1 Fault Test 15 1 Fire Drill 16 1 Batt Test 17 1 PRGM Mode 18 1 Action 19 1 Loop Break 20 3 Alarm 21 1 P A S 22 1 Off Normal 23 1 RZA Fault 24 1 Verify 25 1 CM SHort 26 1 Test Fail 27 1 Alert 28 1 Dirty 29 1 Very Dirty 30 1 Missing 31 1 Wrong Type 32 1 Extra Addr 33 1 Clock Err 34 4 Trouble 35 1 MLT Events 36 1 Alrm Ackd FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 16 of 24 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 D
26. t point_identifier 2 drv_bd gt point_identifier 2 If this error is repeated often it is possible that a FCI firmware update as made the driver unusable Take a log and contact tech support FCI7100 19 Err Relay d lt 1 Rejected drv_bd gt relay FCI7100 20 Err drv_bd gt zone Zone d lt 1 Rejected This message should only be printed if a byte in a message has been corrupted If you notice it more than once then take a log and contact tech support FCI7100 21 Err Point Type not recognized FCI7100 22 Err Undefined Point Type Valid Point Types are listed in section 4 4 2 FCI7100 23 Err Event Type not recognized FCI7100 24 Err Undefined Event Type Valid Event Types are listed in section 4 4 2 FCI7100 25a Err Address Length gt 99 Length Truncated Truncated FCI7100 25b Err Address Length gt 99 Length The maximum value for a sensor module is 99 The combination of address and length specified produce a number gt 99 FCI7100 26 Expected 1 99 Err Invalid Module number FCI7100 27a Err Invalid Loop number Expected 1 10 FCI7100 27b Err Invalid Loop number Expected 1 10 FCI7100 27c Err Invalid Loop number Expected 1 10 Correct the configuration file 3 Correct the configuration file download to the FieldServer and restart the FieldServer for the changes to take effect FieldServer Technologies
27. tation Parity Specify parity None Vendor Limitation Data_Bits Specify data bits 8 Vendor Limitation Stop_Bits Specify stop bits 1 Vendor Limitation Handshaking The 7100 series panels do not support hand shaking Poll_Delay _ This commonly used parameter has no meaning for this driver Example Client Side Connections Connections Port Protocol Baud Parity P8 FCI_7100 1200 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 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual 4 3 Section Title Nodes Client Side Node Descriptors Page 9 of 24 Column Title Function Legal Values Node_Name Provide name for node Up to 32 alphanumeric characters This parameter only has meaning The protocol is node less the for this driver when multiple messages do not contain panels are networked in an FCI information identifying a unique network In this case the source and or destination node Node_ ID NODE_ID is the panel number address Thus this parameter need Set the Node_ID of the local panel not be specified if only one 7100 is to zero and create
28. tworked 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 If the panel is configured to send 3 line messages then the source node information is sent in the line preceding the event and the driver uses this to determine the panel at which the event originated and to store data appropriately The driver provides both client and server emulation The server side of the driver is intended to support FieldServer s Quality Assurance program and is not intended to provide complete emulation of a 7100 and is thus not fully documented Should you require the Server side functionality to be documented and enhanced please contact FieldServer s sales group Max Nodes Supported FieldServer Mode Nodes Comments 1 Node per serial port If there is more than one alarm panel they can be networked and configured to send event cient data to the primary panel The driver can process messages which identify the node of origin Server 1 1 Node per serial port FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 4 of 24 2 Driver Scope of Supply 2 1 Supplied by FieldServer Technologies for this driver FieldServer
29. umber of times that a message define FCI_7100_ STAT EMPTY MSG 7 line was was zero bytes long excluding the terminator Number of times that a message define FCl_7100_ STAT SHORT MSG 8 line was was too short probably a system id tag line Increments each time a reset define FCI_7100_ STAT _NO_PLACE_TO_STORE_LOOP define FCI_7100_ STAT_NO PLACE_TO_STORE_SENSOR define FCI_7100_STAT_NO_PLACE_TO_ STORE MODULE define FCl_7100 STAT NO RESET 9 was rcvd but no DA was reset Increments each time point data define is received but there is no MD to 10 store data that cannot be attributed to a zone relay loop sensor module Increments each time a message is received FCI_7100_STAT_NO_PLACE_TO_STORE_PANEL define FCI_7100_STAT_RCVD_MSGS 11 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 112 FCI 7100 Series Driver Manual Page 23 of 24 Stat Offset Description define FCI_7100_STAT_RCVD_BYTES 12 Increments each time a character is recieved from the panel The bytes are only added when a message terminator is received Thus this count is equiv to the byte count in all FCI_7100_STAT_RCVD_ MSGS define FCI_7100_STAT_PARSED_NO_ERRS_EXCLD_RESET Increments each time a message is par
Download Pdf Manuals
Related Search