FieldServer FS-8700-83 User Manual

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

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........................................................................................................................... 1

3. HARDWARE CONNECTIONS.............................................................................................................. 2

4. CONFIGURING THE FIELDSERVER AS A GAMEWELL SERIAL DRIVER CLIENT........................ 3

4.1 DATA ARRAYS .................................................................................................................................. 3

4.2 CLIENT SIDE CONNECTIONS .............................................................................................................. 4

4.3 CLIENT SIDE NODES ......................................................................................................................... 5

4.4 CLIENT SIDE MAP DESCRIPTORS .......................................................................................................6

FieldServer Related Map Descriptor Parameters.................................................................................. 6

Driver Related Map Descriptor Parameters...........................................................................................6

Timing Parameters................................................................................................................................. 7

Map Descriptor Example 1 – Store data from incoming messages. ..................................................... 8

Map Descriptor Example 2 – Send a Reset / Ack / Silence Command................................................. 9

5. CONFIGURING THE FIELDSERVER AS A GAMEWELL SERIAL DRIVER SERVER .................... 10

6. ADVANCED TOPICS ..........................................................................................................................10

6.1 DRIVER LIMITATIONS & EXCLUSIONS................................................................................................ 10

6.2 DATA TYPES ................................................................................................................................... 10

6.3 STATUS TYPES AND VALUES............................................................................................................ 11

Adding a New Status Type .................................................................................................................. 12

6.4 WHEN DO DATA ARRAYS GET CLEARED (RESET) ..............................................................................12

6.5 ACTION TYPES................................................................................................................................12

Adding new Action Types .................................................................................................................... 15

6.6 ADVANCED MAP DESCRIPTOR EXAMPLES ........................................................................................ 16

Example 1 : Filtering Data....................................................................................................................16

Example 2 : Action Numbers ............................................................................................................... 17

Example 3 : Action Bits ........................................................................................................................ 18

Example 4 : Ignored Messages ........................................................................................................... 19

7. DRIVER NOTES .................................................................................................................................. 20

7.1 IC_TIMEOUT...................................................................................................................................20

7.2 DRIVER STATS................................................................................................................................20

8. REVISION HISTORY................................................................ ERROR! BOOKMARK NOT DEFINED.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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 information in numeric form. The numeric value will indicate the type of
event being reported and the storage location in the FieldServer’s data arrays is (configurable
&) dependent on the origin of the message (panel / circuit / device). Additional information such
as event date and time and descriptions are ignored.

The driver is capable of supporting a panel configured to supervise the port by responding to the
panel’s supervision queries.

This is a passive client driver. The driver listens passively for unsolicited messages produced by
the Gamewell panel. This definition is not strictly true because the driver is capable of sending
the panel three messages: Ack, Silence and Reset.

Design Basis: Gamewell serial port protocol specification “IF 600r7 Message Stream” (not
dated) and “SmartNet Data stream information” (not dated).

The driver is capable of exposing communication statistics in a FieldServer Data Array so that a
remote device can monitor them.

2. Driver Scope of Supply

2.1 Supplied by FieldServer Technologies for this driver

FieldServer

Technologies

PART #

FS-8917-16

RS-485/RS-232 Pigtail for RJ45 port
Driver Manual.

DESCRIPTION

2.2 Provided by user

PART # DESCRIPTION

Gamewell Panel with SIM232 interface

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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

FS-8915-10

RJ45-01
BROWN

RJ45-04

BLUE/WHITE

RJ45-08

ORANGE/WHITE

BASE NAME:
FILE NAME: T28700-83 .VSD

GAMEWELL

SIM 232
BOARD

FS-Rx

FS-COM

XMT

COM

RCV

FS-Tx

GND

COM2

(408)-262-2299

GAMEWELL

CONNECTION DIAGRAM

DATE:6/4/02
BY: MN

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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 FieldServer
to communicate with a Gamewell Serial Driver Server

The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Gamewell 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 “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.

4.1 Data Arrays

Section Title

Data_Arrays

Column Title Function Legal Values

Data_Array_Name Provide name for Data Array Up to 15 alphanumeric

characters

Data_Format Provide data format. Each data array can

only take on one format.

Data_Array_Length Number of Data Objects. Must be larger

than the data storage area required for
the data being placed in this array.

Example

// Data Arrays
//
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
DA_AI_01, UInt16, 200
DA_AO_01, UInt16, 200
DA_DI_01, Bit, 200
DA_DO_01, Bit, 200

FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte,
Packed_Byte,
Swapped_Byte
1-10,000

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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

connected to the Bridge

Baud Specify baud rate

The driver supports all standard
baud rates 110 – 115200.
Gamewell panels only support a
baud rate of 2400.

Parity* Specify parity

The driver supports the following
options. Even, Odd, None, Mark,
Space

The Gamewell panels only
support the use of no parity.

Data_Bits* Specify data bits

Stop_Bits* Specify stop bits

Protocol Specify protocol used Gamewell

Handshaking* Specify hardware handshaking
Poll _Delay* Time between internal polls 0-32000 seconds

IC_Timeout This driver does not use an inter

character timeout system. Failing
to set the IC_Timeout to zero will
result in driver errors.

Example

// Client Side Connections

Connections
Port, Baud, Parity, Protocol, Handshaking, Poll_Delay, IC_Timeout
P8, 9600, None, Gamewell, None , 0.100s , 0

P1-P8, R1-R2

2400

None

8

1

None

default 1 second

0

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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.

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 correspond to the
Node_ID’s of the panel’s
connected to the SmartNet
terminal.

Protocol Specify protocol used Gamewell
Port Specify which port the device is

connected to the FieldServer.

The use of R1 and R2 is only
appropriate when a 232/485
converter is used. The
Gamewell panels only have a
232 port available for
connection.

Example

// Client Side Nodes

Nodes
Node_Name, Node_ID, Protocol, Port
Panel1 , 0 , Gamewell, P8

0-256

P1-P8, R1-R2

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

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

is to be stored in the Bridge

Data_Array_Location Starting location in Data Array 0 to maximum specified in

Function Function of Client Map

Descriptor.

Reads (rdbc / rdb ) are not
allowed. The use of WRBX is
recommended for the ack /
silence / reset functions. A
message will be generated
each time the value in the
associated array is updated
(even if the value stays the
same.)

One of the Data Array names
from “Data Array” section above

“Data Array” section above
Passive, WRBC, WRBX

Driver Related Map Descriptor Parameters

Column Title Function Legal Values

Node_Name Name of Node to fetch data

from

Data_Type Data type

This parameter is only required
for passive / server map
descriptors.

The Data Type determines the
type of data that gets stored
when a message get received.
The Data Type corresponds to
the ‘Status’ field in a Gamewell
message.

Additional information is
provided in section 6.2

One of the node names
specified in “Client Node
Descriptor” above
Any

Alarms
Faults
Events
Bus
Comm
Control
Ack
Signal Silence
Troubles
Supervisories
Action_Numbers
Action_Bits
Dump

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]