FieldServer FS-8700-40 Release note

Driver Version:
1.12
Document Revision:
1
A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after October 2011
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-40 SBT-FSI
(Siemens Building Technologies –Foreign Systems Interface)

FS-8700-40 SBT FSI Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
TABLE OF CONTENTS
1SBT-FSI Description ........................................................................................................................................ 3
2Driver Scope of Supply ................................................................................................................................... 3
2.1 Supplied by FieldServer Technologies for this driver.....................................................................................3
2.2 Provided by the Supplier of 3rd Party Equipment .........................................................................................3
2.2.1 Hardware ...............................................................................................................................................3
2.2.2 Required 3rd Party Configuration ...........................................................................................................3
3Hardware Connections................................................................................................................................... 4
3.1 Using the NIM-1R or NIM-1W for MXL ..........................................................................................................4
3.2 RS-232 Connection to the XLS Panel..............................................................................................................6
3.3 FSI Connection Notes.....................................................................................................................................7
4Data Array Parameters................................................................................................................................... 8
5Configuring the FieldServer as a SBT-FSI Client............................................................................................... 9
5.1 Client Side Connection Parameterss............................................................................................................11
5.2 Client Side Node Parameters .......................................................................................................................12
5.3 Client Side Map Descriptor Parameters.......................................................................................................12
5.3.1 FieldServer Related Map Descriptor Parameters .................................................................................12
5.3.2 Driver Related Map Descriptor Parameters.........................................................................................13
5.3.3 Timing Parameters...............................................................................................................................13
5.3.4 Map Descriptor example 1 - Monitoring a MXL/XLS Device for Events ...............................................14
5.3.5 Map Descriptor example 2 –Monitoring Analog Loop Devices ...........................................................16
6Configuring the FieldServer as a SBT-FSI Server............................................................................................ 17
6.1 Server Side Connection Descriptors ............................................................................................................18
6.2 Server Side Node Descriptors ......................................................................................................................19
6.3 Server Side Map Descriptors........................................................................................................................19
6.3.1 FieldServer Specific Map Descriptor Parameters .................................................................................19
6.3.2 Driver Specific Map Descriptor Parameters .........................................................................................20
6.3.3 Map Descriptor example 1 - Emulating a MXL/XLS device with events ...............................................21
6.3.4 Map Descriptor example 2 - Emulating a MXL/XLS device with analogs.............................................22
Appendix A. Useful Features................................................................................................................................ 23
Appendix A.1. Specifying a Poller Map Descriptor length .......................................................................................23
Appendix A.2. Interpreting Panel Error Messages...................................................................................................24
Appendix A.3. Obtaining Point Addresses from the panel report ...........................................................................24
Appendix A.4. Activating and De-activating Entities ...............................................................................................25
Appendix A.5. Arming and De-Arming Entities........................................................................................................26
Appendix A.6. Request ASD or Sensitivity ...............................................................................................................28
Appendix A.7. Request % Compensation Used / % Dirty ........................................................................................29
Appendix A.8. Opcode 45 –Request List Map Descriptors that trigger at Startup or Node Offline and stop at
Node Online.............................................................................................................................................................30
Appendix B. Troubleshooting............................................................................................................................... 31
Appendix B.1. Checksum Errors...............................................................................................................................31
Appendix B.2. Recording Active Events –XLS Panel ................................................................................................31
Appendix B.3. Using Trouble Codes.........................................................................................................................31

FS-8700-40 SBT FSI Driver Manual Page 3 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
1SBT-FSI DESCRIPTION
The SBT-FSI (Siemens Building Technologies –Foreign Systems Interface) driver allows the FieldServer to transfer
data to and from Siemens MXL/XLS devices (NIM-1R
1
or NIM-1W or RPM
2
) over either RS-232 or RS-485 using
MXL/XLS to foreign system protocol. The FieldServer can emulate either a Server or a Client. Note that the Driver
does not support MXL and XLS panels networked together.
Max Nodes Supported
FieldServer Mode
Nodes
Comments
Client
1-10 (one Client per physical
FieldServer serial port). Depends on
FieldServer model and configuration.
Only 1 Client node allowed on multidrop systems
Server
99
Panel numbers from 1 to 99 may be emulated
2DRIVER SCOPE OF SUPPLY
2.1 Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
Description
FS-8917-03
RJ45 to DB9F connector adapter
FS-8917-16
Pigtail cable for RJ45 Port for RS-232 use
2.2 Provided by the Suppl ier of 3rd Party Equipment
2.2.1 Hardware
Part #
Description
Siemens MXL/XLS System
Siemens NIM-1R Network Interface Module ( for MXL usage )
Siemens RPM Network Interface Module ( for XLS usage )
500-699103
Siemens NIM-1W Network Interface Module ( for MXL usage )
Siemens Cable P/N 555-193085 (For RS-232 connection)
2.2.2 Required 3rd Party Configuration
The SBT-FSI System must be set up for remote monitoring with the MXL or XLS to foreign systems
protocol.
The ports on the RPM must be configured by the XLS panel. The RPM can be configured for RS-232 or RS-
485, but not both together. Connection to the RS-485 port has not been tested and is not supported.
1
Note that NIM-1R is no longer supported by Siemens and is therefore considered to be legacy while NIM-1W is common.
2
The ports on the RPM need to be configured by the XLS panel. Configuration can be set up for either RS-232 or RS-485, but not both together.
Connection to the RS-485 port of the RPM has not been tested and is not supported.

FS-8700-40 SBT FSI Driver Manual Page 4 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
3HARDWARE CONNECTIONS
3.1 Using the NIM-1R or NIM-1W for MXL
Configure the NIM-1R
3
or NIM-1W for Foreign System Interface (FSI) by setting all of the switches in SW2
to open (or OFF). See connection diagram below:
Connect the NIM-1R to an RS-232 port on the Fieldserver as depicted in the fiagram below (brown circle)
Connect the NIM-W to an RS-485 port on the FieldServer as depeicted in the diagram below.
FieldServer P1
18
2
3
4
1
6
7
8
5
10
11
12
9
14
15
16
13
TB4
Gnd
_
+
Gnd
FG
_
+
RS-485
Opto
Isolated
FS-8917-03
RJ45 to
DB9M
Connector
RJ45 CAT 5 Cable
FS8915-10
Cerberus Cable
P/N 555-193085
FS-8917-03
NIM-1R
Connection
3
Note that NIM-1R is no longer supported by Siemens and is therefore considered to be legacy while NIM-1W is common.

FS-8700-40 SBT FSI Driver Manual Page 5 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
Pinouts
FS Function
RJ45 Pin#
DB9F Pin#
Cerberus Cable Pin
Color
RX
1
2
14
Red
GND
4
5
16
Black
TX
8
3
13
Green
RTS
7
12
Brown
CTS
8
15
White

FS-8700-40 SBT FSI Driver Manual Page 6 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
3.2 RS-232 Connection to the XLS Panel
Configure the NIM-1R
4
or NIM-1W for Foreign System Interface (FSI) by setting all of the switches in SW2
to open (or OFF).
The ports on the RPM can be configured for either RS-232 or RS-485, but not both together. Connection
to the RS-485 port of the RPM has not been tested and is not supported.
The FieldServer can be connected to either Port 1 or Port 3 on the XLS Panel as described in the
connection drawing. Pins 6 and 7 on the Port 2 Connector must be jumpered to enable RS-232 Port 3.
FieldServer P1
18
2
3
4
1
6
7
8
5
10
9
RXD
TXD
RTS (Do not use)
CTS (Do not use)
GND
RXD
TXD
RTS (Do not use)
CTS (Do not use)
GND
Port 1
RS-232
Port 3
RS-232
2
3
4
1
6
7
5
Port 2
RS-485
RS-232 Port
FieldServer Part #
8917-16
Pigtail for RJ45
Port
Connect to one of the RS-232
Ports on the FieldServer
Brown Blue/white
Orange/White
GND
TX
RX
Pins 6 and 7
must be
jumpered to
enable Port 3
Connector Pinouts for RS-232 Ports
Wire Color
RJ-45
XLS Panel Port 1 (3)
Pin
Signal
Signal
Pin
Brown
1
Rx
TXD
2 (7)
White/Orange
8
Tx
RXD
1 (6)
Blue/white
4
GND
GND
3 (8)
4
Note that NIM-1R is no longer supported by Siemens and is therefore considered to be legacy while NIM-1W is common.

FS-8700-40 SBT FSI Driver Manual Page 7 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
3.3 FSI Connection Notes
It is possible to connect a MXL/XLS device to any RS-232 or RS-485 port. These ports simply need to be
configured for MXL/XLS in the configuration file.
The driver does not support MXL and XLS panels networked together.
One FSI panel may be connected per FieldServer port, but multiple panels may be connected per FSI. The
following diagram illustrates two possible connection configurations.
Configuration 1 –One FSI Panel per FieldServer per port, one Panel per FSI
FSI
FSI
Panel Panel
Configuration 2 –One FSI Panel per FieldServer port, 3 panels connected in series to the FSI
FSI
Panel PanelPanel
FieldServer P1
18
FieldServer P1
18
18
P2

FS-8700-40 SBT FSI Driver Manual Page 8 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
4DATA ARRAY PARAMETERS
Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary
to declare the data format of each of the Data Arrays 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.5
Int16, Uint16, Bit
Data_Array_Length
Number of Data Objects. Must be larger than the data storage
area required by the Map Descriptors for the data being placed in
this array.
1-10, 000
Example
// Data Arrays
Data_Arrays
Data_Array_Name
, Data_Format
, Data_Array_Length
Event_Counts
, Uint16
, 19
Fire
, Bit
, 2048
Fire_UnAck
, Bit
, 2048
5
Format must be Uint16 or Int16 to see trouble codes.

FS-8700-40 SBT FSI Driver Manual Page 9 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
5CONFIGURING THE FIELDSERVER AS A SBT-FSI 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 SBT-FSI Server.
In FSI mode, the NIM-1R or NIM-1W or RPM allows the FieldServer to gather data from up to 63 MXL/XLS Panels
connected via an MXL/XLS network. The default configuration shipped with the FieldServer will monitor two
panels (1 and 2) with 8 modules (1 to 8) each.
When the FieldServer is configured as a Client, two sets of data are collected by a “poller” Map Descriptor.
The first is a collection of 19 counters per panel. Each 16-bit counter is incremented by the poller Map Descriptor
whenever the corresponding event occurs. An external Client can read these counters to quickly determine
whether a new event has been reported to the Server. The counters are mapped into the Data Array specified for
the poller Map Descriptor. Counter offsets into the Data Array per event type are indicated below:
Event
Counter Offset
Fire Alarm In
0
Fire Alarm Out
1
Fire Alarm Acknowledge
2
Trouble In
3
Trouble Out
4
Trouble Acknowledge
5
Supervisory In
6
Supervisory Out
7
Supervisory Acknowledge
8
Security Alarm In
9
Event
Counter Offset
Security Alarm Out
10
Security Alarm Acknowledge
11
Status In
12
Status Out
13
Test In
14
Test Out
15
Audible Silenced
16
Audible Unsilenced
17
System Reset
18
The second set of data is a collection of bit maps that can be queried to identify the device that has reported the
event. When an alarm event arrives from a device, the corresponding bit is set in two separate arrays. The bit in
one array indicates the alarm has occurred, and the bit in the other array indicates that the alarm has not yet been
acknowledged. When an “alarm clear” event arrives, the bit in the alarm array is cleared. If an “alarm
acknowledge” event arrives, the bit in the un-acknowledged array is cleared. All event arrays in a Client driver
configuration are optional. To enable an event array, a Map Descriptor must be defined in the configuration using
a Map Descriptor message type that corresponds to the array as shown in the following table:
Array
Msg_Type
Fire Alarm
Fire
Fire Alarm Un-Acknowledged
Fire_Ack
Trouble Alarm
Trouble
Trouble Un-Acknowledged
Trouble_Ack
Supervisory Alarm
Super
Supervisory Un-Acknowledge
Super_Ack
Array
Msg_Type
Security Alarm
Secur
Security Alarm Un-Acknowledged
Secur_Ack
Status
Status
Test
Test
Audible (Un)Silenced
Audible
System Reset
Reset

FS-8700-40 SBT FSI Driver Manual Page 10 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
Notes
1Map Descriptors are used to determine which bit to set in the Data Array. When an event arrives from a
panel, the FieldServer will scan for a Map Descriptor with a Node_ID matching the panel number reported in
the event. This Map Descriptor will point to the Data Array to be modified. The location can be further
refined if a starting module within the panel is specified in the Block_Number field. Each module represents
256 bits that can be set or reset by an event. A Map Descriptor that is 512 bits long with a starting module
(Block_Number) of 3 represents the events for Modules 3 and 4. A Map Descriptor that is 10 bits long will
only map the first 10 devices for that module. The combination of Block_Number and Data_Array_Location
can be used to map multiple panels with various numbers of modules into a packed array to be read by the
Server side of the FieldServer.
2When the customer receives a Communication FieldServer with the default driver installed, the configuration
is set to poll 2 MXL/XLS devices once per second.
3In addition to the two sets of event counters, alarm bit arrays are set up for 8 modules (1 to 8) per device. If
the required configuration falls within this size, only the Server side of the FieldServer needs to be configured.
To connect to a device using Modbus RTU protocol, configure the interface as if the FieldServer were another
Modbus PLC and create a Map Descriptor to assign a Modbus address (such as 40001) to the Counts Data
Array so that it can be read by the Modbus bus master.
4If the customer has different panel numbers, the Nodes section of the configuration file will need to be
changed. To add more panels, add Node entries and Map Descriptors by copying the original ones and
modifying the Panel number entries and Data Array offsets. To access panels with more modules, first
increase the Data Array lengths. If the extra modules are contiguous, the Map Descriptors for that panel can
have their lengths increased also. If there are large gaps in the numbering of the module, it will be more
efficient to add additional Map Descriptors by copying the ones that are given and modifying the
Block_Number to start at the next existing module number.
5While the creation of passive Client-side Map Descriptors is optional, error messages will appear when events
arrive for which Map Descriptors cannot be found. It is therefore recommended that Map Descriptors
(especially ack mapdescs) be allocated even if only as dummies to prevent nuisance error messages.

FS-8700-40 SBT FSI Driver Manual Page 11 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for SBT-FSI 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.
5.1 Client Side Connection Parameterss
Section Title
Connections
Column Title
Function
Legal Values
Port
Specify which port the device is connected to the FieldServer
P1-P8, R1-R26
Protocol
Specify protocol used
Cerberus,
SBT-FSI
Enhanced_Protocol
Enables legacy or enhanced protocol.. MXL panels do not currently
support Enhanced_Protocol, so this parameter must be set to “No” for
MXL. The parameter is normally set to “Yes” for XLS, but may be set to
“No” if problems are being experienced.
Yes (XLS)
No (MXL)
System_Type
Specifies Siemens Panel type
MXL, XLS
Block_Acks7
Specifies if the driver uses block or individual command acks
Yes, No
Fire_Alarms_Hold*
Specifies if the driver should hold fire alarms until the system reset, or
clear on fire alarms going out
Yes, No
Baud*
Specify baud rate
19200
(Vendor
limitation)
Parity*
Specify parity
Even (Vendor
limitation)
Data_Bits*
Specify data bits
7(Vendor
limitation)
Stop_Bits*
Specify stop bits
1(Vendor
limitation)
Poll _Delay*
Time between internal polls
0-32000
seconds, 1
second
Example
// Client Side Connections
Connections
Port
, Protocol
, Baud
, Parity
, Data_Bits
, Poll_Delay
P1
, SBT-FSI
, 19200
, Even
, 7
, 0.100s
6
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
7
Refer to the Advanced Driver Manual for usage. This function not enabled on standard driver.

FS-8700-40 SBT FSI Driver Manual Page 12 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
5.2 Client Side Node Parameters
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for Node
Up to 32 alphanumeric characters
Node_ID
Panel number
1-999
Protocol
Specify protocol used
Cerberus, SBT-FSI
Port
Specify on which port the device is connected to the
FieldServer
P1-P8, R1-R21
Example
// Client Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
, Port
Panel1
, 1
, SBT-FSI
, P1
5.3 Client Side Map Descriptor Parameters
5.3.1 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
FieldServer
One of the Data Array names from Section 4.
Data_Array_Offset
Starting location in Data Array
0 to (Data_Array_Length-1) as specified in Section 4.
Function
Function of Client Map
Descriptor
Rdbc for Msg_Type:
Poller, Analog_Volts, Analog_Sense, Analog_Thres
Passive for Msg_Type:
Fire_Alarm, Fire_Ack, Trouble, Trouble_Ack, Secur,
Secur_Ack, Super, Super_Ack, Status, Test Audible,
Reset
Awt for Msg_Type:
Entity_Arm_Disarm; Entity_Activate_Deact

FS-8700-40 SBT FSI Driver Manual Page 13 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
5.3.2 Driver Related Map Descriptor Parameters
Column Title
Function
Legal Values
Node_Name
Name of Node to fetch or store
data from
One of the Node names specified in Section 5.2
Block_Number
Starting module number within
panel. There are 256 points per
module.
1 –256
Sub_Module
Sub module number for XLS
systems only
0 –99
Component_Address
Component address for XLS
systems only
0 –99
Length
Length of Map Descriptor
specifies number of points. There
are 256 points per module.
1 –10000
Msg_Type
Indicates a “poller” Map
Descriptor or identifies the type
of event message this Map
Descriptor will handle. If this is
configured, the driver will store a
value that indicates the point type
of the event if the Data Array
used on the Map Descriptor is not
of a bit type
Poller; Fire_Alarm; Fire_Ack; Trouble; Trouble_Ack;
Super; Super_Ack; Secur; Secur_Ack; Status; Test;
Audible; Reset; Analog_Volts; Analog_Sense;
Analog_Thres; Entity_Arm_Disarm8;
Entity_Activate_Deact9
Analog_Device
Indicates range of device data to
be requested by analogs
0 : devices 1-60
1 : devices 61-121
2 : devices 122-182
3 : devices 183-243
4 : devices 244-252
Block_Offset
This field allows you to set the
start address of a MXL or XLS
point in a Map Descriptor.
0 - 255
Entity_Types
Used to indicate the type of Entity
on the panel.. . Refer to Appendix
A.5 for more information
Inputs, Outputs, (If all elements are Input or Output)
OR specify each element of the entity individually
e.g. IOIOIOO
Entity_Energizations
Used to control the entity on the
panel. Refer to Appendix A.5 for
more information.
De-energize, Energize, (If all elements are Energize
or De-energize)
OR specify each element of the entity individually,
e.g. EDED---DED
5.3.3 Timing Parameters
Column Title
Function
Legal Values
Scan_Interval*
Rate at which data is polled
≥0.001s , 1.0s
8
Refer to Appendix A.5
9
Refer to Appendix A.4

FS-8700-40 SBT FSI Driver Manual Page 14 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: supp[email protected]
5.3.4 Map Descriptor example 1 - Monitoring a MXL/XLS Device for Events
To monitor a MXL/XLS device we need only one “poller” Map Descriptor as shown below. The function of this Map Descriptor’s is to continuously check the
MXL device for events from panels. Only one poller Map Descriptor per FieldServer port is required when monitoring more than one MXL/XLS device. The
Node_Name will indicate on which port this Map Descriptor resides.
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Block_Number
, Length
, Msg_Type
CD_Poller1
, Event_Counts1
, 0
, RDBC
, Panel1
, 1
, 19
, Poller
CD –Client Descriptor
Specifies lowest panel
number from which
events will be
received. Refer to
Appendix A.2for more
information.
Specify length
in multiples of
19 events
according to
Block Number
used.
Refer to
Appendix A.2
for more
information.
Specify poller
message type
for this Map
Descriptor.
Specifies Data Array
that will hold event
counters. Data Array
length must be equal
or greater than Data
Array offset plus Map
Descriptor length.
Specifies
offset into
event
counters
Data Array
where event
counts will be
stored.
Choose a
Node_Name
from the
passive Map
Descriptors in
the next section
to specify the
port on which
this poller will
be active.

FS-8700-40 SBT FSI Driver Manual Page 15 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: supp[email protected]
Passive Map Descriptors must be added for each event per panel to be monitored:
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Block_Number
, Length
, Msg_Type
CD_Fire1
, Fire
, 0
, Passive
, Panel1
, 1
, 1024
, Fire
CD_Fire_Ack1
, Fire_Ack
, 0
, Passive
, Panel1
, 1
, 1024
, Fire_Ack
CD_Trouble1
, Trouble
, 0
, Passive
, Panel1
, 1
, 1024
, Trouble
CD_Trouble_Ack1
, Trouble_Ack
, 0
, Passive
, Panel1
, 1
, 1024
, Trouble_Ack
CD_Super1
, Super
, 0
, Passive
, Panel1
, 1
, 1024
, Super
CD_Super_Ack1
, Super_Ack
, 0
, Passive
, Panel1
, 1
, 1024
, Super_Ack
CD_Secur1
, Secur
, 0
, Passive
, Panel1
, 1
, 1024
, Secur
CD_Secur_Ack1
, Secur_Ack
, 0
, Passive
, Panel1
, 1
, 1024
, Secur_Ack
CD_Status1
, Status
, 0
, Passive
, Panel1
, 1
, 1024
, Status
CD_Test1
, Test
, 0
, Passive
, Panel1
, 1
, 1024
, Test
CD_Audible1
, Audible
, 0
, Passive
, Panel1
, -
, 1
, Audible
CD_Reset1
, Reset
, 0
, Passive
, Panel1
, -
, 1
, Reset
CD –Client Descriptor
Notes:
1All passive Map Descriptors are optional. Specific Map Descriptors may be defined for particular events to be monitored as per the Msg_Type. Should
events happen for which no Map Descriptors are defined, error messages will occur on the FieldServer. It may therefore be useful to add dummy Map
Descriptors especially for ack responses to prevent nuisance error messages.
2Passive Map Descriptors with Node_Name the same as the poller Map Descriptor will only be able to store events from a panel with the same Node_ID
e.g. Node_ID of 1 will only store events from panel 1. To store events from panel 2, it is necessary to add passive Map Descriptors with Node ID of 2 etc.
Do not add poller Map Descriptors for other panels.
3Important Note about first alarm point and Data Array Offsets
Most SBT-FSI panels have device point numbers starting at one instead of zero. The FieldServer MXL driver reserves Data Array offset zero for points with
device numbers of zero although they are currently not used. Triggering the first alarm point on a MXL panel will thus result in a point status change at
Data_Array_Offset of one instead of zero.
Length specifies the number of points. There
are 256 points per module. A length of 1024
holds points for 4 modules.
Block Number specifies the
starting module number under
which points are mapped.
Node Name specifies the panel
number for which events will
be stored.

FS-8700-40 SBT FSI Driver Manual Page 16 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: supp[email protected]
5.3.5 Map Descriptor example 2 –Monitoring Analog Loop Devices
Analog devices on a loop can be monitored for detector voltage, sensitivity voltage and threshold voltage using three analog Map Descriptors:
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Block_Number
, Length
, Msg_Type
, Analog_Device
, Scan_Interval
CD_Analog_Volts1
, Analog_Volts
, 0
, Rdbc
, Panel1
, 1
, 60
, Analog_Volts
, 0
, 300s
CD_Analog_Sens1
, Analog_Sense
, 0
, Rdbc
, Panel1
, 1
, 60
, Analog_Sense
, 0
, 300s
CD_Analog_Thres1
, Analog_Thres
, 0
, Rdbc
, Panel1
, 1
, 60
, Analog_Thres
, 0
, 300s
Note: If necessary, use more analog Map Descriptors with other Analog_Device numbers to poll other devices on the loop.
Scan Interval on analog
pollers may not be shorter
than 300s to prevent
flooding the Foreign
Systems Interface.
Use Float Data Arrays for
the analog Map
Descriptors to get the
full analog value.
0 : devices 1-60
1 : devices 61-121
2 : devices 122-182
3 : devices 183-243
4 : devices 244-252

FS-8700-40 SBT FSI Driver Manual Page 17 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
6CONFIGURING THE FIELDSERVER AS A SBT-FSI SERVER
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 provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate
with a SBT-FSI Client.
The driver can be used to emulate a MXL/XLS Server device. Other protocol drivers could then poll other remote
devices and access the local MXL/XLS Server data to set or clear events. In this configuration an existing SBT-FSI
system could be replaced with an MXL/XLS emulation. Existing Clients could poll the emulation driver on the
FieldServer to get the same data as from a conventional MXL/XLS Server.
Up to 99 panels can be emulated with the driver. A Map Descriptor has to be defined for each type of remote
device that would normally exist in a MXL/XLS Server. The following types can be used:
Device Type
Fire Alarm In
Fire Alarm Out
Fire Alarm Acknowledge
Trouble In
Trouble Out
Trouble Acknowledge
Supervisory In
Supervisory Out
Supervisory Acknowledge
Security Alarm In
Security Alarm Out
Security Alarm Acknowledge
Status Event
Test Event
Analog Voltage
Analog Sensitivity Voltage
Analog Threshold Voltage
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for SBT-FSI communications, the driver independent FieldServer buffers need to be declared in the
“Data Arrays” section, the FieldServer virtual node(s) needs to be declared in the “Server Side Nodes” section, and
the data to be provided to the Clients needs to be mapped in the “Server 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.

FS-8700-40 SBT FSI Driver Manual Page 18 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
6.1 Server Side Connection Descriptors
Section Title
Connections
Column Title
Function
Legal Values
Port
Specify which port the device is connected to the FieldServer
P1-P8, R1-R210
Protocol
Specify protocol used
Cerberus, SBT-FSI
Enhanced_Protocol
Enables legacy or enhanced protocol.. MXL panels do not currently
support Enhanced_Protocol, so this parameter must be set to “No”
for MXL. The parameter is normally set to “Yes” for XLS, but may be
set to “No” if problems are being experienced.
Yes (XLS)
No (MXL)
System_Type
Specifies Siemens Panel type
MXL, XLS
Echo
Specifies if the server should echo the client’s polls
Yes, No
Baud*
Specify baud rate
110 –115200,
standard baud
rates only, 19200
Parity*
Specify parity
Even, Odd, None,
Mark, Space
Data_Bits*
Specify data bits
7, 8
Stop_Bits*
Specify stop bits
1 (Vendor
limitation)
Server_Hold_Timeout
Specifies time FieldServer will reserve Server side connection while
waiting for the Client side to update data in Data_Array (if
necessary)
>1.0s
Example
// Server Side Connections
Connections
Port
, Protocol
, Baud
, Parity
, Data_Bits
P1
, SBT-FSI
, 19200
, Even
, 7
10
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.

FS-8700-40 SBT FSI Driver Manual Page 19 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
6.2 Server Side Node Descriptors
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for node
Up to 32
alphanumeric
characters
Node_ID
Panel number
1-99
Protocol
Specify protocol used
Cerberus, SBT-FSI
Server_Hold_Timeout
Specifies time FieldServer will reserve Server side connection
while waiting for the Client side to update data in Data_Array (if
necessary)
>1.0s
Example
// Server Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
, 11
Panel1
, 1
, SBT-FSI
6.3 Server Side Map Descriptors
6.3.1 FieldServer 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 point data is to be fetched
from
One of the Data Array names
from “Data Array” section
above
Data_Array_Offset
Starting location in Data Array
0 to maximum specified in
“Data Array” section above
Function
Function of Server Map Descriptor
Server
Server_Hold_Timeout*
Specifies time FieldServer will reserve Server side
connection while waiting for the Client side to update
data in Data_Array (if necessary)
>1.0s
11
Note that no port information is necessary on Server side.

FS-8700-40 SBT FSI Driver Manual Page 20 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]m
6.3.2 Driver Specific Map Descriptor Parameters
Column Title
Function
Legal Values
Node_Name
Name of Node or panel for which this Map
Descriptor holds points
One of the node names specified
in Section 6.2.
Block_Number
Module number (Note that this only specifies one
module number as opposed to a starting module
number as in the Client Map Descriptor)
1 –256
Sub_Module
Sub module in XLS system
0 –99
Component_Address
Component address in XLS system
0 –99
Length
Length of Map Descriptor
Specifies number of points for the indicated module.
Note that MXL systems typically has only 256 points
per module.
1 –256
Msg_Type*
If this is configured, the driver will store a value that
indicates the point type of the event if the Data
Array used on the Map Descriptor is not of a bit type
Note that a poller message type may not be used in
a Server Map Descriptor.
Fire_Alarm; Fire_Ack; Trouble;
Trouble_Ack; Secur; Secur_Ack;
Super; Super_Ack; Status; Test;
Audible; Reset; Analog_Volts;
Analog_Sense; Analog_Thres, -