Summary of the content on the page No. 1
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction
Manual)
FS-8700-83 Gamewell Serial Driver
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Summary of the content on the page No. 2
FS-8700-83 Gamewell Index TABLE OF CONTENTS 1. GAMEWELL SERIAL DRIVER DESCRIPTION ...................................................................................1 2. DRIVER SCOPE OF SUPPLY ..............................................................................................................1 2.1 SUPPLIED BY FIELDSERVER TECHNOLOGIES FOR THIS DRIVER ............................................................1 2.2 PROVIDED BY USER.........................................
Summary of the content on the page No. 3
FS-8700-83 Gamewell Page 1 of 24 1. Gamewell Serial Driver Description The Gamewell Serial Driver allows the FieldServer to accept messages generated by a Gamewell 600 Series Panel as well as ‘Smartnet Data Stream’ messages generated by a Gamewell Smartnet terminal. All Gamewell 600 Series Fire Alarm panels are equipped with a serial port, which produces panel, circuit or device status messages. This driver is designed to process these messages and store this status informat
Summary of the content on the page No. 4
FS-8700-83 Gamewell Page 2 of 24 3. Hardware Connections The bridge is connected to the Gamewell panel as shown below. Configure the Gamewell panel according to manufacturer’s instructions FIELDSERVER RS232 PORT GAMEWELL SIM 232 RJ45-01 FS-8915-10 BOARD BROWN XMT COM COM2 RCV GND RJ45-04 BLUE/WHITE RJ45-08 ORANGE/WHITE (408)-262-2299 GAMEWELL CONNECTION DIAGRAM BASE NAME: DATE:6/4/02 FILE NAME: T28700-83 .VSD BY: MN FieldServer Technologies 1991 Tarob Court Milpitas
Summary of the content on the page No. 5
FS-8700-83 Gamewell Page 3 of 24 4. Configuring the FieldServer as a Gamewell Serial Driver 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” files on the driver diskette). This section documents and describes the parameters necessary for configuring the Field
Summary of the content on the page No. 6
FS-8700-83 Gamewell Page 4 of 24 4.2 Client Side Connections Section Title Connections Column Title Function Legal Values Port Specify which port the device is P1-P8, R1-R2 connected to the Bridge Baud Specify baud rate 2400 The driver supports all standard baud rates 110 – 115200. Gamewell panels only support a baud rate of 2400. Parity* Specify parity None The driver supports the following options. Even, Odd, None, Mark, Space The Gamewell panels only support t
Summary of the content on the page No. 7
FS-8700-83 Gamewell Page 5 of 24 4.3 Client Side Nodes Section Title Nodes Column Title Function Legal Values Node_Name Provide name for node Up to 32 alphanumeric characters Node_ID Gamewell panel node address. 0-256 The Node Id has no meaning when the FieldServer is connected directly to Gamewell panel. When connecting to a Gamewell panel directly always set the Node_ID to zero. When connecting to a Gamewell SmartNet terminal. The Node_ID is important and should
Summary of the content on the page No. 8
FS-8700-83 Gamewell Page 6 of 24 4.4 Client Side Map Descriptors FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Data_Array_Name Name of Data Array where data One of the Data Array names is to be stored in the Bridge from “Data Array” section above Data_Array_Location Starting location in Data Array 0 to maximum specified in “Data Array” section above Function Fun
Summary of the content on the page No. 9
FS-8700-83 Gamewell Page 7 of 24 Length Length of Map Descriptor 1 – 1000 Controls how many elements of the data array are controlled by the map descriptor. Address This commonly used parameter has no 0 meaning for this driver. If specified it is best set to zero. Ckt Specify the circuit number whose Panel , 1 ,2 , 3 …. 131 message will get stored using this map descriptor. Use the keyword ‘Panel’ if the you wish to store data from a panel. All messages which do not co
Summary of the content on the page No. 10
FS-8700-83 Gamewell Page 8 of 24 Map Descriptor Example 1 – Store data from incoming messages. This example illustrates typical map descriptor uses to store data from panel generated messaged. As all these map descriptors have their Clear_On_Reset field set to yes, when a panel reset message is received all the data in the controlled arrays will be set to zero When a point reports its own state as normal the driver will set the appropriate element of the appropriate array to zero
Summary of the content on the page No. 11
FS-8700-83 Gamewell Page 9 of 24 Map Descriptor Example 2 – Send a Reset / Ack / Silence Command. This example illustrates three map descriptors used to send commands to the panel. These are the only active map descriptors that can be used with the Gamewell Serial Driver. st These map descriptors use the WRBX function. When the 1 element (because Data_Array_Offset = 0 ) has its value updated, even if the value doesn’t change, then the driver will send the command to the panel.
Summary of the content on the page No. 12
FS-8700-83 Gamewell Page 10 of 24 5. Configuring the FieldServer as a Gamewell Serial Driver Server The Gamewell Serial Driver provides limited server functionality. This has been developed to allows for automated testing and Quality Assurance. It is not supported or documented however, at a client’s request it can be extended & documented (typically at an additional cost.) 6. Advanced Topics 6.1 Driver Limitations & Exclusions The driver does not support scaling when data
Summary of the content on the page No. 13
FS-8700-83 Gamewell Page 11 of 24 1. If the Data Type is ‘Any’ then the map descriptor will be used to store data from message with any status. 2. The state reported is filtered and must match the Data_Type for the associated array to be updated. For example, if the Data_Type of a MapDesc is ‘Alarms’ and a message is received that reports a Fault then the map descriptor will not be used to store the data from the message. 3. Normally, user’s are interested in the Status of
Summary of the content on the page No. 14
FS-8700-83 Gamewell Page 12 of 24 When comparing these keywords to the data in the Status field of the message the driver only compares the first three characters. The comparison is case insensitive. Adding a New Status Type The fragment of a CSV file displayed below illustrates how to change the value associated with ‘BUS’ to 9 and adds two new Status types, Fred and Ginger. Driver_Table Gamewell_Status_String, Gamewell_Status_Value, Protocol BUS ,
Summary of the content on the page No. 15
FS-8700-83 Gamewell Page 13 of 24 Based on the table below if a message contains the string ‘Fire Alarm in’ then the action number will be stored as 11. Value Action Description 255 Driver did not recognize action type System Setup 1 Skip System I/O Assignments System power up 2 Begin System I/O Assignments System programming itself Ignore any data from this point until "Exit Program 3 Programming Mode Entered Mode" is received 4 Exit Program Mode See Programming
Summary of the content on the page No. 16
FS-8700-83 Gamewell Page 14 of 24 33 New Card Detected @ System Problem 34 Out of Memory Assigning System Problem Supervisory or trouble in circuit that automatically 35 I/O Restored restore themselves 36 Trouble Tested in System Problem 37 Trouble in System Problem 38 Output Shorted in System Problem 39 Dup. Dev. in System Problem 40 Dev. Missing in System Problem 41 Type Mismatch System Problem 42 Dev. Dirty in System Problem 43 No Response from Analog CK
Summary of the content on the page No. 17
FS-8700-83 Gamewell Page 15 of 24 Adding new Action Types The following fragment from a CSV file shows how you can add two new action types. If a message is received and its action field contains the text ‘FRED’ then the action number will be stored as 100. Driver_Table Gamewell_Action_String, Gamewell_Action_Value, Protocol FRED , 100 , Gamewell GINGER , 101 , Gamewell The driver can store a m
Summary of the content on the page No. 18
FS-8700-83 Gamewell Page 16 of 24 6.6 Advanced Map Descriptor Examples Example 1 : Filtering Data You can direct the driver to filter the incoming messages so that data arrays are only updated for particular states. For example an incoming messge which reports a device in Ckt 1 to be in a FAULT state (Status:FAULT) will use the map descriptor ‘Ckt1_data03’ to store the data and the array DA_FAULTS1 will be updated. If however, the message reported an ALARM state (Status:ALARM) then
Summary of the content on the page No. 19
FS-8700-83 Gamewell Page 17 of 24 Example 2 : Action Numbers You can have the driver store a value corresponding to the contents of the action field reported in the incoming messages. Actions are brief descriptions of the event that caused the message to be generated. A table of values vs. descriptions is provided in section 6.5. The driver stores the most recent action number, overwriting the previously stored action numbers. The driver does not keep an event log. The action nu
Summary of the content on the page No. 20
FS-8700-83 Gamewell Page 18 of 24 Example 3 : Action Bits Instead of having the driver store a value to indicate the action, the driver can set a bit, whose offset indicates the underlying action. For example, if the string ‘Fire Alarm in’ is contained in the action field of the message the driver would set the array element at offset 11 (use table 6.5 to get the value vs. string) to 1. Important to note is that the driver does not clear a previously set bit when a new action i
