FieldServer FS-8700-52 Release note

A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Instruction Manual Part Number FS-8700-52
5/22/2002
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-52 Notifier AM6000

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page Index
TABLE OF CONTENTS
1. NOTIFIER AM6000 DESCRIPTION............................................................................................................................1
2. DRIVER SCOPE OF SUPPLY........................................................................................................................................2
2.1 SUPPLIED BY FIELDSERVER FOR THIS DRIVER...............................................................................................................2
2.2 PROVIDED BY USER.............................................................................................ERROR! BOOKMARK NOT DEFINED.
3. HARDWARE CONNECTIONS......................................................................................................................................3
4. CONFIGURING THE FIELDSERVER AS A NOTIFIER AM6000 CLIENT .................................................4
4.1 DATA ARRAYS....................................................................................................................................................................4
4.2 CLIENT SIDE NODES..........................................................................................................................................................5
4.3 CLIENT SIDE MAP DESCRIPTORS.....................................................................................................................................6
4.3.1 FieldServer Specific Map Descriptor Parameters.............................................................................................6
4.3.2 Driver Specific Map Descriptor Parameters......................................................................................................6
4.3.3 Timing Parameters..................................................................................................................................................7
Map Descriptor Example......................................................................................................................................................8
5. DRIVER NOTES ...............................................................................................................................................................10
5.1 MAP DESCRIPTOR KEYWORDS.......................................................................................................................................10
5.1.1 AM6000_TypeID...................................................................................................................................................10
5.1.2 AM6000_Status......................................................................................................................................................11
5.1.3 AM6000_Ackable..................................................................................................................................................11
5.1.4 AM6000_Simulation..............................................................................................................................................11
5.2 STATISTICS........................................................................................................................................................................12
5.3 LISTING OF SYSTEM TROUBLE MESSAGES...................................................................................................................15

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 1
1. Notifier AM6000 Description
The Notifier AM6000 driver is a seial driver. It allows the FieldServer to transfer data from a Notifier
AM6000 panel over either RS232 or RS485 using Notifier AM6000 protocol. There are eight RS232 and
two RS485 ports standard on the FieldServer. The FieldServer can only a passive Client.
The driver receives messages intended for a system printer, interprets these messages by filling in data
arrays in the FieldServer. This data is available for other devices or PLC's to read.

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 2
2. Driver Scope of Supply
2.1 Supplied by FieldServer for this driver
FieldServer
Technologies
PART #
DESCRIPTION
8915-10 UTP cable (7 foot) for RS232 use
UTP cable (7 foot) for Ethernet connection
8917-02 RJ45 to DB9F Connector adapter
8917-01 RJ45 to DB25M connection adapter
SPA59132 RS485 connection adapter
Driver Manual.

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 3
3. Hardware Connections
Configure the Notifier AM6000 according to manufacturer’s instructions.

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 4
4. Configuring the FieldServer as a Notifier AM6000 Client
For a detailed discussion on FieldServer configuration, please refer to the instruction manual for the
FieldServer. 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 Notifier AM6000 Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for Notifier AM6000 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. FLOAT, BIT, UInt16, SInt16, Packed_Bit, Byte, Packed_Byte,
Swapped_Byte
Data_Array_Length Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.
1-10,000
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

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 5
4.2 Client Side Connections
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the device is
connected to the FieldServer P1-P8, R1-R2
Baud* Specify baud rate 2400 (Only baud rate supported by
the Notifier port)
Parity* Specify parity Even
Data_Bits* Specify data bits 7
Stop_Bits* Specify stop bits 1
Protocol Specify protocol used AM6000
Handshaking* Specify hardware handshaking None
Poll Delay* Time between internal polls 0-32000 seconds
default 1 second
Example
// Client Side Connections
Connections
Port, Baud, Parity, Protocol, Data_bits, Handshaking, Poll_Delay
P8, 2400, Even, AM6000, 7, None, 0.100s
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 Modbus station address of physical
server node 1-255
Protocol Specify protocol used Modbus_RTU, Modbus/TCP, etc.
Port Specify which port the device is
connected to the FieldServer P1-P8, R1-R2
Example
// Client Side Nodes
Nodes
Node_Name, Protocol, Port
Panel1, AM6000, P8

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 6
4.4 Client Side Map Descriptors
4.4.1 FieldSe rver Specific 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 FieldServer One of the Data Array names from “Data Array” section above
Data_Array_Location Starting location in Data Array 0 to maximum specified in “Data
Array” section above
Function Function of Client Map Descriptor Passive
4.4.2 Driver Specific Map Descriptor Parameters
Column TitleFunction Legal Values
Node_Name Name of Node to fetch data from One of the node names
specified in “Client
Node Descriptor” above
Data_Type Data type Register, Coil, AI, DI
Length Length of Map Descriptor. This value is important
when a 'Block Ack' message is received as it tells
the driver how much of the data array to zeroise.
1 -1000
Address Loop/Device Address
In the format mmnn where mm is the loop number
and nn is the device number. Together they forma a
composite device number.
501, 302
AM6000 Driver
specific parameters &
keywords.
Am6000_typeID Used to differentiate between device and system
type messages. Device-only, System_trbl,
device&type.
system-Styl2,
catch-all
Additional notes are
provided in section 5.1
Am6000_Status Allows direction of alarm or trouble states to
different data arrays. Any, Alarm, trouble, erase, on , eraseon
Additional notes are
provided in section 5.2
AM6000_Ackable Tells the driver that the data area of this mapdesc
must be Zeroised when a block ack is received. Additional notes are provided in section 5.3
Am6000_simulation Provided for debugging and test purposes only.
Tells the driver which debug message to send. This
parameter is for use by FieldServer Technologies
only.

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 7
4.4.3 Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled >0.1s

FS-8700-52 Notifier AM6000 Driver Manual
FieldServer Technologies 1991Tarob Court, Milpitas, California 95035 [phone] fax: [phone]
Visit our website: www.fieldserver.com E-mail: [email protected]
Page 8
4.4.4 Map Descriptor Example.
Map_block_Name, scan_interval, Data_Array_Name, Data_Array_Offset, Function, node_name, AM6000_TypeID, Address , Length , am6000_Ackable
DEVICES_100_199, 1.0s, DEVICE_STATES_LOOP1, 0, passive, node_a, device-only, 500 , 100 , Yes
Name of the data
array that will be
updated when this
map descriptor is
used.
The position in the data
array that corresponds to
device whose number is
equalto the Address
Parameter.
In this example device
500's state will be strored
in the 0th element of the
data array called
DEVICE_STATES_LOOP1
All map
descriptors for the
AM6000 Notifier
driver must be
passive.
This keyword indicates that
this map descriptor will only
be used to process device
state messages. This makes
the address and length
parameters very important.
Connects this
map descriptor
to a node
whose name is
'node_a' and
thus connects
the map
descriptor to a
port.
The device address of the first
device to be processed by this map
descriptor. Devices are allocated to
loops. The device address consists
of a mmnn format where mm is the
loop number and nn is the device
number.
In this example the address is set to
500 this indicated that the first
device to be processed by this map
desc. Is on loop 5 and is device
zero.
The range of
device address is
determined by this
parameter.
Because address is
500 and length is
100 in this
example all
devices 500 to 599
will be
Processed using
When a Block
Acknowledge
or System
Reset message is received
the driver will set the
portion of the data array
DEVICE_STATES_LOO
P1 starting at
Data_Array_Offset for
Length number of
elements to zero.