FieldServer FS-8700-40 User Manual

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-40 SBT-FSI

(Siemens Building Technologies – Foreign Systems Interface)

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after September 2008

Driver Version: 1.08
Document Revision: 3

FS-8700-40 SBT FSI Driver Manual Table of Contents

TABLE OF CONTENTS

1 SBT-FSI Description ........................................................................................................................................ 3

2 Driver 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

3 Hardware Connections ................................................................................................................................... 4

3.1 Using the NIM-1R or NIM-1W for MXL .......................................................................................................... 4

3.2 FSI Connection Notes ..................................................................................................................................... 5

4 Configuring the FieldServer as a SBT-FSI Client ............................................................................................... 6

4.1 Data Arrays .................................................................................................................................................... 8

4.2 Client Side Connection Descriptions .............................................................................................................. 9

4.3 Client Side Node Descriptors ....................................................................................................................... 10

4.4 Client Side Map Descriptors......................................................................................................................... 10

4.4.1 FieldServer Related Map Descriptor Parameters ................................................................................. 10

4.4.2 Driver Related Map Descriptor Parameters ......................................................................................... 11

4.4.3 Timing Parameters ............................................................................................................................... 11

4.4.4 Map Descriptor example 1 - Monitoring a MXL/XLS Device for Events ............................................... 12

4.4.5 Map Descriptor example 2 – Monitoring Analog Loop Devices ........................................................... 14

5 Advanced Client Configuration – Using Bidirectional capability ................................................................... 15

6 Configuring the FieldServer as a SBT-FSI Server ............................................................................................ 16

6.1 Server Side Connection Descriptors ............................................................................................................ 17

6.2 Server Side Node Descriptors ...................................................................................................................... 18

6.3 Server Side Map Descriptors........................................................................................................................ 18

6.3.1 FieldServer Specific Map Descriptor Parameters ................................................................................. 18

6.3.2 Driver Specific Map Descriptor Parameters ......................................................................................... 19

6.3.3 Map Descriptor example 1 - Emulating a MXL/XLS device with events ............................................... 20

6.3.4 Map Descriptor example 2 - Emulating a MXL/XLS device with analogs ............................................. 21

Appendix A. Advanced Topics .............................................................................................................................. 22

Appendix A.1. Specifying a Poller Map Descriptor length ....................................................................................... 22

Appendix A.2. Interpreting Panel Error Messages ................................................................................................... 23

Appendix A.3. Obtaining Point Addresses from the panel report ........................................................................... 23

Appendix A.4. Using Trouble Codes ......................................................................................................................... 24

Appendix A.5. Activating and De-activating Entities ............................................................................................... 27

Appendix A.6. Arming and De-Arming Entities ........................................................................................................ 28

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 3 of 29

FieldServer Mode

Nodes

Comments

10 (one Client per physical

500-699103

Siemens NIM-1W Network Interface Module ( for MXL usage )

1 SBT-FSI DESCRIPTION

The SBT-FSI (Siemens Building Technologies – Foreign Systems Interface) driver allows the FieldServer to transfer

1

data to and from Siemens MXL/XLS devices (NIM-1R

or NIM-1W or RPM2) over either RS-232 or RS-485 using

MXL/XLS to foreign system protocol. The FieldServer can emulate either a Server or a Client.

Max Nodes Supported

1-

Client

FieldServer serial port). Depends on

Only 1 Client node allowed on multidrop systems

FieldServer model and configuration.

Server 99 Panel numbers from 1 to 99 may be emulated

2 DRIVER 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-8700-40 SBT FSI Driver Manual

2.2 Provided by the Supplier 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 )

Siemens Cable P/N 555-193085 (For RS-232 connection)

2.2.2 Required 3

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

rd

Party Configuration

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.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 4 of 29

2

3
4

1

6
7
8

5

10
11
12

9

14
15
16

13

2
3
4

1

6
7
8

5

10
11
12

9

14
15
16

13

2

1

TB2

TB7

TB4

P3

DB9

2 Rx
3 Tx
5 GND
7 RTS
8 CTS

P3

14
13
16
12
15

COLOR

RED
GREEN
BLACK
BROWN
WHITE

CERBERUS CABLE

P/N 555-193085

FieldServer

8917-03

8915-10

Cerberus Cable

555-193085

SPA59132

1

1

3 HARDWARE CONNECTIONS

Configure the MXL/XLS device according to manufacturer’s instructions.

It is possible to connect a MXL/XLS device to any RS-232 or RS-485 port. The appropriate ports must be configured
for MXL/XLS in the configuration file.

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:

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

3

Note that NIM-1R is no longer supported by Siemens and is therefore considered to be legacy while NIM-1W is common.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 5 of 29

Configuration 1 – One FSI Panel per FieldServer per port, one Panel per FSI

Configuration 2 – One FSI Panel per FieldServer port, 3 panels connected in series to the FSI

FSI

FSI

FSI

Panel PanelPanel

Panel Panel

FieldServer

P1

18

FieldServer

P1

1818

P2

3.2 FSI Connection Notes

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

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 6 of 29

Array

Msg_Type

Array

Msg_Type

4 CONFIGURING 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

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:

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

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

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

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 7 of 29

Notes

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

2 When the customer receives a Communication FieldServer with the default driver installed, the configuration

is set to poll 2 MXL/XLS devices once per second.

3 In 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.

4 If 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.

5 While 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.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 8 of 29

Up to 15

ach Data Array can only take on one

// Data Arrays

4.1 Data Arrays

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.

Section Title

Data_Arrays

Column Title Function Legal Values

Data_Array_Name Provide name for Data Array

Data_Array_Format

Provide data format. E
format.

4

Number of Data Objects. Must be larger than the data storage

Data_Array_Length

area required by the Map Descriptors for the data being placed in
this array.

Example

Data_Arrays
Data_Array_Name ,Data_Format ,Data_Array_Length
Event_Counts ,Uint16 ,19
Fire ,Bit ,2048
Fire_UnAck ,Bit ,2048

alphanumeric
characters

Int16, Uint16, Bit

1-10,000

4

Format must be Uint16 or Int16 to see trouble codes.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 9 of 29

.. MXL panels do not currently

6

7

Port

,Protocol

,Baud

,Parity

,Data_Bits

,Poll_Delay

4.2 Client Side Connection Descriptions

Section Title

Connections

Column Title Function Legal Values

Port Specify which port the device is connected to the FieldServer P1-P8, R1-R25

Protocol Specify protocol used

Enables legacy or enhanced protocol

Enhanced_Protocol

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.

System_Type Specifies Siemens Panel type MXL, XLS

Block_Acks

Fire_Alarms_Hold

Specifies if the driver uses block or individual command acks Yes, No

Specifies if the driver should hold fire alarms until the system reset, or
clear on fire alarms going out

Baud* Specify baud rate

Parity* Specify parity

Data_Bits* Specify data bits

Stop_Bits* Specify stop bits

Handshaking

Specify hardware handshaking * None

Poll _Delay* Time between internal polls

Example

Cerberus,
SBT-FSI

Yes (XLS)
No (MXL)

Yes, No

19200
(Vendor
limitation)

Even (Vendor
limitation)

7 (Vendor
limitation)

1 (Vendor
limitation)

0-32000
seconds, 1
second

// Client Side Connections
Connections

P1 ,SBT-FSI ,19200 ,Even ,7 ,0.100s

5

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available

on specific hardware.

6

Refer to the Advanced Driver Manual for usage. This function not enabled on standard driver.

7

Handshaking is not supported.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 10 of 29

Specify on which port the device is connected to the

is to be stored in the

Fire, Fire_Ack, Trouble, Trouble_Ack, Secur,

4.3 Client 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

Port

FieldServer

Example

// Client Side Nodes

Nodes
Node_Name ,Node_ID ,Protocol ,Port
Panel1 ,1 ,SBT-FSI ,P1

P1-P8, R1-R2

1

4.4 Client Side Map Descriptors

4.4.1 FieldServer Related Map Descriptor Parameters

Column Title Function Legal Values

Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters

Name of Data Array where data

Data_Array_Name

FieldServer

Data_Array_Offset Starting location in Data Array

Function

Function of Client Map
Descriptor

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

0 to maximum specified in “Data Array” section
above

Rdbc for Msg_Type:
Poller, Analog_Volts, Analog_Sense, Analog_Thres

Passive for Msg_Type:

Secur_Ack, Super, Super_Ack, Status, Test Audible,
Reset

Awt for Msg_Type:
Entity_Arm_Disarm; Entity_Activate_Deact

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 11 of 29

Starting module number within
Sub module number for XLS

Component address for XLS

start address of a MXL or XLS

4.4.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 “Client Node
Descriptor” above

Block_Number

Sub_Module

Component_Address

Length

Msg_Type

Analog_Device

Block_Offset

Entity_Types

Entity_Energizations

panel. There are 256 points per
module.

systems only

systems only

Length of Map Descriptor
specifies number of points. There
are 256 points per module.

Indicates a “poller” Map
Descriptor or identifies the type
of event message this Map
Descriptor will handle.

Indicates range of device data to
be requested by analogs

This field allows you to set the

point in a Map Descriptor.

Used to indicate the type of Entity
on the panel.. . Refer to Appendix
A.6 for more information

Used to control the entity on the
panel. Refer to Appendix A.6 for
more information.

1 – 256

0 – 99

0 – 99

1 – 10000

Poller; Fire; Fire_Ack; Trouble; Trouble_Ack; Super;
Super_Ack; Secur; Secur_Ack; Status; Test; Audible;
Reset; Analog_Volts; Analog_Sense; Analog_Thres;

8

Entity_Arm_Disarm

; Entity_Activate_Deact9

0 : devices 1-60
1 : devices 61-121
2 : devices 122-182
3 : devices 183-243
4 : devices 244-252

0 - 255

Inputs, Outputs, (If all elements are Input or Output)
OR specify each element of the entity individually
e.g. IOIOIOO

De-energize, Energize, (If all elements are Energize
or De-energize)
OR specify each element of the entity individually,
e.g. EDED---DED

4.4.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.6

9

Refer to Appendix A.5

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 12 of 29

information.

Choose a

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

Specifies Data Array
that will hold event
counters. Data Array
length must be equal
or greater than Data
Array offset plus Map
Descriptor length.

CD – Client Descriptor

Specifies
offset into
event
counters
Data Array
where event
counts will be
stored.

Node_Name
from the
passive Map
Descriptors in
the next section
to specify the
port on which
this poller will
be active.

Specifies lowest panel
number from which
events will be
received. Refer to
Appendix A for more
information.

Specify length
in multiples of
19 events
according to
Block Number
used.

Refer to
Appendix A
for more

Specify poller
message type
for this Map
Descriptor.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 13 of 29

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

Node Name specifies the panel
number for which events will
be stored.

Notes:

Block Number specifies the
starting module number under
which points are mapped.

Length specifies the number of points. There
are 256 points per module. A length of 1024
holds points for 4 modules.

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

2 Passive 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.

Important Note about first alarm point and Data Array Offsets

3

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.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 14 of 29

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

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

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.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 15 of 29

5 ADVANCED CLIENT CONFIGURATION – USING BIDIRECTIONAL CAPABILITY

The driver has the ability to:

• Ack Fire, Trouble, Supervisory and Security Alarms.

• (Un)Silence the Audible.

• Reset the MXL/XLS system.

• Set the MXL/XLS system’s date and time.

Please refer to the Advanced Driver Manual for using and enabling these functions.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 16 of 29

6 CONFIGURING 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.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 17 of 29

11

waiting for the Client side to update data in Data_Array (if

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

Enables legacy or enhanced protocol.. MXL panels do not currently

Enhanced_Protocol

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.

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

Parity* Specify parity

Data_Bits* Specify data bits 7, 8

Stop_Bits* Specify stop bits

Handshaking

Specify hardware handshaking * None

Specifies time FieldServer will reserve Server side connection while

Server_Hold_Timeout

necessary)

Example

Yes (XLS)
No (MXL)

110 – 115200,
standard baud
rates only, 19200

Even, Odd, None,
Mark, Space

1 (Vendor
limitation)

>1.0s

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

11

Handshaking is not supported.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 18 of 29

Up to 32
Up to 32 alphanumeric

from “Data Array” section

6.2 Server Side Node Descriptors

Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for node

alphanumeric
characters

Node_ID Panel number 1-99

Protocol Specify protocol used Cerberus, SBT-FSI

Specifies time FieldServer will reserve Server side connection

Server_Hold_Timeout

while waiting for the Client side to update data in Data_Array (if

>1.0s

necessary)

Example

// Server Side Nodes

Nodes
Node_Name ,Node_ID ,Protocol ,12
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

Data_Array_Name

Data_Array_Offset Starting location in Data Array

Function Function of Server Map Descriptor Server

Server_Hold_Timeout*

12

Note that no port information is necessary on Server side.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

Name of Data Array where point data is to be fetched
from

Specifies time FieldServer will reserve Server side
connection while waiting for the Client side to update
data in Data_Array (if necessary)

characters

One of the Data Array names

above

0 to maximum specified in
“Data Array” section above

>1.0s

FS-8700-40 SBT FSI Driver Manual Page 19 of 29

Module number (Note that this only specifies one
module number as opposed to a starting module

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 “Client Node Descriptor” above

Block_Number

number as in the Client Map Descriptor)

Sub_Module Sub module in XLS system 0 – 99

Component_Address Component address in XLS system 0 – 99

Length of Map Descriptor

Length

Msg_Type

Specifies number of points for the indicated module.
Note that MXL systems typically has only 256 points
per module.

Type of event message
Note that a poller message type may not be used in
a Server Map Descriptor.

1 – 256

1 – 256

Fire; Fire_Ack; Trouble;
Trouble_Ack; Secur; Secur_Ack;
Super; Super_Ack; Status; Test;
Audible; Reset; Analog_Volts;
Analog_Sense; Analog_Thres

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 20 of 29

6.3.3 Map Descriptor example 1 - Emulating a MXL/XLS device with events

The following list of Map Descriptors emulates a MXL Server,

SD – Server Descriptor

// Server Side Map Descriptors

Map Descriptors
Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Length ,Msg_Type
SD_Fire1 ,Fire ,0 ,Server ,Panel1 ,1 ,256 ,Fire
SD_Fire_Ack1 ,Fire_Ack ,0 ,Server ,Panel1 ,1 ,256 ,Fire_Ack
SD_Trouble1 ,Trouble ,0 ,Server ,Panel1 ,1 ,256 ,Trouble
SD_Trouble2 ,Trouble ,256 ,Server ,Panel1 ,2 ,256 ,Trouble
SD_Trouble_Ack1 ,Trouble_Ack ,0 ,Server ,Panel1 ,1 ,256 ,Trouble_Ack
SD_Super1 ,Super ,0 ,Server ,Panel1 ,1 ,256 ,Super
SD_Super_Ack1 ,Super_Ack ,0 ,Server ,Panel1 ,1 ,256 ,Super_Ack
SD_Secur1 ,Secur ,0 ,Server ,Panel1 ,1 ,256 ,Secur
SD_Secur_Ack1 ,Secur_Ack ,0 ,Server ,Panel1 ,1 ,256 ,Secur_Ack
SD_Status1 ,Status ,0 ,Server ,Panel1 ,1 ,256 ,Status
SD_Audible1 ,Audible ,0 ,Server ,Panel1 ,- ,1 ,Audible
SD_Reset1 ,Reset ,0 ,Server ,Panel1 ,- ,1 ,Reset

Note that Trouble modules 1 and 2
on Panel 1 are emulated with two
separate Map Descriptors.

Specifies the panel number
being emulated by this Server
Map Descriptor.

Specifies the module
number. A typical
Cerberus Server has 256
points per module.

Specifies the number
of points represented
within the indicated
module.

Notes:

1 MXL/XLS Server Map Descriptor fields differ in many respects from MXL/XLS Client Map Descriptors. Please follow the examples clearly and read all notes

to ensure a working configuration. No poller Map Descriptors may be defined in a configuration file that is used to configure a MXL/XLS Server.

2 Only one module specified by Block_Number can be emulated with a Server Map Descriptor whereas a Client Map Descriptor specifies a starting module

number with one module for every 256 counts of the Map Descriptor length. You have to use separate Map Descriptors for each module to emulate when
doing a Server configuration.

3 More than one Msg_Type Map Descriptor may be used to represent other modules.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 21 of 29

6.3.4 Map Descriptor example 2 - Emulating a MXL/XLS device with analogs

The following list of Map Descriptors emulate a MXL Server:

// Server Side Map Descriptors

Map Descriptor
Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Length ,Msg_Type
SD_Analog_Volts1 ,Volts ,0 ,Server ,Panel1 ,1 ,252 ,Analog_Volts
SD_Analog_Sense1 ,Sense ,0 ,Server ,Panel1 ,1 ,252 ,Analog_Sense
SD_Analog_Thres1 ,Thres ,0 ,Server ,Panel1 ,1 ,252 ,Analog_Thres

Use Float Data Arrays for
the analog Map
Descriptors to get the full
analog value.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 22 of 29

Appendix A. Advanced Topics

Appendix A.1. Specifying a Poller Map Descriptor length

The poller Map Descriptor is responsible for checking a remote MXL/XLS device for events. When events are
received the poller Map Descriptor increments counters at various offsets in the Data Array specified by the poller
Map Descriptor. The offsets and their meanings are explained under the Client configuration section of this Driver
Manual.

The poller Map Descriptor’s Data Array contains sets of 19 elements or counters. Each set of counters represents
the events from a panel. The Block_Number is used to specify the lowest panel number from which events will be
received. The highest Node_ID of any passive Map Descriptor on the same port as the poller Map Descriptor
specifies the highest panel number from which events will be received. The poller Map Descriptor’s length has to
be at least 19 and has to incremented by 19 for every extra panel above the Block_Number from which events will
be received.

If a poller Map Descriptor length is set below 19 and for example, event “System Reset” is received which needs to
be mapped at offset 18 in the Data Array, the following kernel message will be printed:

“Cannot store alarm event type counts!”, 11010” ‘offset=%u,da=%s”

Example 1: Only receive events from panel 7

• Passive event Map Descriptor’s Node Id = 7 (X)

• Poller Map Descriptor’s Block_Number = 7 (Y)

• Poller Map Descriptor’s Length = (X – Y) * 19 + 19 = 19

• Event counters for panel 7 will reside in the first 19 elements.

Example 2: Receive events from panel 7 and 6

• Passive event Map Descriptor’s Node Id = 7 (X)

• Poller Map Descriptor’s Block_Number = 6 (Y)

• Poller Map Descriptor’s Length = (X – Y) * 19 + 19 = 38

• Event counters for panel 6 will reside in the first 19 elements and those for panel 7 in the next 19

elements.

Warning: An error will be generated when an event arrives from a panel with a number lower than the
Block_Number of the poller. The poller Map Descriptor’s Block_Number must equal the lowest panel number for
which a passive Map Descriptor exists on the same port.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 23 of 29

Checksum or Parity

Ensure connection baudrate, start, stopbits and parity match the panel's

Check integrity of physical connection to panel, route cables away from

Corresponds to Block Number 1

Corresponds to Block Array point 1

Appendix A.2. Interpreting Panel Error Messages

A NAK is sent by the panel when it is unable to respond to a message. The format will be as follows:

T02> DRV-> CER : Panel replied with NAK on last message!
T02> DRV-> CER : Reason: 1

The following table lists the reason for the failure and the suggested corrective action. Note that the messages are
generated by the panel, not the FieldServer.

Reason # Error Corrective Action

Reason 1

Reason 2 Receive buffer full Increase scan interval on the poller Map Descriptor.

Reason 3 Syntax Error

Reason 4

fail

Unrecognized
message failure

settings

electromagnetic sources that can generate noise.

Replace hardware?

Appendix A.3. Obtaining Point Addresses from the panel report

In order to configure the FieldServer to capture data from the Panel, the point addresses being used in the panel
need to be identified. The Panel report that can be printed out from the panel can be used for this purpose, but
matching the Report parameters with the FieldServer configuration parameters is not a trivial exercise. The
following notes should assist in identifying the addresses needed for FieldServer configuration

• The preamble to the report is not relevant to the FieldServer Driver.

• The first Module can be identified by the title NET Address =1. This corresponds to FieldServer’s “Block

1”.

• The Module Subaddress corresponds to individual points in the Block Array.

This information is depicted in the following file extract:

NET ADDR: 1 ==> ALD-2 2 Analog Loop Module Page: 5

===============================================================================

Module Subaddress ----------------> 1

DEVICE TYPE ----------------------> TRI-60/TRX-2/3 1 Switch Input

Usage --------------------------> TROUBLE

Message ------------------------> RCP-01 Trouble Input MM-1

Switch Contact Type -----------> N.O.

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 24 of 29

Appendix A.4. Using Trouble Codes

In order to see the trouble codes for incoming troubles it is necessary to use a Uint16 or Int16 data array for the
trouble instead of the normal Bit. When the driver stores a trouble code of for example 15 into a Bit data array, it
will be displayed as 1 since Bit only holds either a zero or a one value. Using a Uint16 or Int16 data array will
ensure the value of 15 is displayed.

The following information is taken from Siemens Fire Safety documentation

MXL/XLS Trouble Codes

These codes are sent in Field 5 of the Trouble in, Trouble out and Trouble Acknowledge messages 24H, 25H and
26H. Each code is sent as up to 3 ASCII bytes. Leading zeros are not sent. The Request Trouble Type message
(43H) can be used to obtain the text strings shown below for each of these codes. The trouble text string is
returned in the Trouble Type message (53H).

Trouble Type Trouble Type Text

0

1 Multiple Response

2 Communication Error

3 Input Dev. Response too low

4 Device Receive Error

5 Dev Detected Waveform Error

6 Not Responding

7 Not Responding

8 Unspecified Dev. Responding

9 Incorrect ID

10 INPUT DE-ISOLATED

11 INPUT ISOLATED

12 Input Disarmed

13 Addressable Relay disarmed

14 Relay Disarmed

15 Signal Circuit Disarmed

16 Solid State Output Disarmed

17 Relay Supervision Failure

18 Signal Circuit Loop Open

19 Loop Disarmed

20 Class A Trouble

21 Relay Driver Inoperative

22 Signal Circuit Shorted

23 ALD Reception Error

24 Coil Open

25 Zone Power Off

26 Power Cycling

27 Short Circuit

Trouble Type Trouble Type Text

28 Open Circuit

29 Voltage Low

30 Zone Power Loss

31 Loop Node

32 Not defined

33 Multiple Response

34 MOI-1 Local Trouble

35 MOI-1 Zone Trouble

36 No database – default in use

37 Too Many ALD-2’s

38 PSR-1 Driver Disarmed

39 Output Disarmed

40 Not Responding

41 Unspecified Module Responding

42 Communication Failure

43 RAM Failure

44 ROM Failure

45 A/D Convert Fail

46 Single Module Zone Code

47 Command Not Valid

48 Network A Pair Fail

49

50 Loss of 24V Input Power

51 Act Power Voltage Low

52 Default Trouble Active

53 Network Disabled

54 Alarm from Isolated Device

55 Printer off-line

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 25 of 29

Trouble Type Trouble Type Text

56 Warm Reset

57 Printer out of Power

58 Tamper Switch

59 Battery Backup Invalid

60 Positive Ground Fault

61 Negative Ground Fault

62 AC Fail/brownout

63 System Signal Power Failure

64 Battery Fuse/Wiring Open

65

66 24 Volt Supply Over/Under

67 High Battery Voltage

68 Battery Charger Off

69 24 Volts on Battery Backup

70 Low Battery voltage

71 Watchdog Triggered

72 Device LED Manually Activated

73 Alarm queue full

74 Supervisory queue full

75 Trouble queue full

76 Security queue full

77 Memory error in Ram text

78 Memory error in ROM text

79 Aux Pwr Class A Fail Pos

80 Aux Pwr Class A Fail Neg

81 Supervisory Point

82 Security Point

83 BELL 2 ISOLATED

84 BELL 2 DE-ISOLATED

85 Configuration Error

86 Addressable Relay Isolated

87 Relay Isolated

88 Single Circuit Isolated

89 Solid State Output Isolated

90 Class A Fault

91 Noise Fault

92 MOI-1 Local Fault

93 MOI-1 Zone Isolated

94 PSR-1 Driver Isolated

95 Fault queue full

96 Isolated Alarm queue full

97 Isolated Alarm point

98 Requires Service

99 MVP General Trouble

100 Valve Tamper queue full

Trouble Type Trouble Type Text

101 Valve Tamper Point

102 WALKTEST Activated

103 Function Recursion Limit Exceeded

104 Trouble Causing Input

105 Carrier Loss

106

107 Missing Device ID Response

108 Annunciator Trouble

109 CMI-300 general trouble

110 ROM SW version error

111 Lamp Supervision Trouble

112 Keyswitch Activated

113 Ancillary Cntrl Funcs Isolated

114 Ancillary Cntrl Funcs De-Isolated

115 Pre-dirty Analog volt reached

116 IEC limit reached. Service Req

117 IEC memory error

118 NET-7 General Trouble

119 Network B Pair Failure

120 MOI-1 Voice System Trouble

121 Style 4 Network mode

122 Aux. RS232 Transmit Fail

123 Module Address Buffer Fail

124 Incorrect Enclosure

125 OCC-1 General Trouble

126 OCC-1 Degrade Mode

127 Backup Tone Card (BTC)

128 Daily detector test abnormal

129 Event log 80% full

130 Event log 90% full

131 Log FULL, events will be lost

132 Audio Riser 1 Trouble

133 Audio Riser 2 Trouble

134 Audio Riser 3 Trouble

135 Mic Key Trouble

136 Mic Pre-amp Trouble

137 Tone Generator Trouble

138 Mic Input Trouble

139 Telephone Riser Trouble

140 Mic Key Trouble

141 Amplifier 1 Trouble

142 Amplifier 2 Trouble

143 Amplifier 3 Trouble

144 Amplifier 1 Backed Up

145 Amplifier 2 Backed Up

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 26 of 29

161

Amplifier 2 Signal Loss

174

Out of task – Call factory

187

+15volt fault

Trouble Type Trouble Type Text

146 Amplifier 3 Backed Up

147 Multiple Response

148 Communication Error

149 Not Responding

150 Unspecified Sub-module

Responding

151 Incorrect ID

152 Audio Riser 1 Class A Active

153 Audio Riser 2 Class A Active

154 Audio Riser 3 Class A Active

155 Backup Amplifier Trouble

156 Daily Detector Test Abnormal

157 Low IEC voltage. Service Req.

158 Audio Output Shorted

159 Audio Output Class A Active

160 Amplifier 1 Signal Loss

162 Amplifier 3 Signal Loss

163 Generic Input Terminal

164 DMU 1 Failure

165 DMU 2 Failure

166 Out of RAM. Call factory

167 Incorrect Node Address

168 Not Responding

169 Unspecified Node Responding

170 Node Disconnected

171 Network CSGM Upload Needed

172 Style 7 Network Mode

173 Network input disarmed

175 Stack Fault – Call factory

176 Software Key Violation

177 Airflow too low

178 Airflow too high

179 Detector Trouble

180 AnaLASER General Trouble

181 Pre1 level

182 Pre2 level

183 Incorrect library version

184 Out of calibration

185 AnaLASER Power Trouble

186 Pre-alarm

188 Strobe power fault

Trouble Type Trouble Type Text

189 Audio fault iso-St 7Tx

190 Audio fault iso-St 7Rx

191 Audio fault iso-St 4Tx

192 Audio fault iso-St 4Rx

193 Multiple Response

194 Global audio riser-St 7

195 Global audio riser-St 4

196 Local audio riser

197 Database Out of Date

298 ASD disabled for test

199 Sys halt – too many ALD/ACM

200 DMC-1 in record mode

201 DMC-1 tone trouble

202 DMC-1 phrase trouble

203 Troubles summarized

204

205 Incorrect custom phrase control

206 Remote node disconnected

207 History manually turned off

208 History manually turned on

209 History manually erased

210 Memory upgrade required

211 Event queue corrupt

212 Current sensor failure

213 EEprom error

214 No application firmware

215 Component disarmed

216 Zone 1 open

217 Zone 2 open

218 Zone 1 short

219 Zone 2 short

220 Zone 1 Class A return fault

221 Zone 2 Class A return fault

222 Input source malfunction

223 Over current fault

224 Log failure, events lost

225 24V 4amp supply shutdown

226 24V 12amp supply shutdown

227 Backplane power shutdown

228 No battery detected

229 Thermistor Trouble

230 Configuration process failure

231 Device(s) with no address

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 27 of 29

Map_Descriptors

PNL_1_Act_Entity

,0s

,Act_Ent

,0

,Awt

,Panel1

,1

,1

,10

,Entity_Activate_Deact

Port

,Baud

,Parity

,Data_Bits

,Line_drive_on

,Line_drive_off

,Enhanced_Protocol

,Protocol

,System_Type

Appendix A.5. Activating and De-activating Entities

These examples demonstrate the methodology to activate or de-activate equipment on the MXL/XLS panel as per the SBT-FSI protocol specification. This
relates to the opcode Activate/Deactivate Entity 0x7b/0x7c.

The configuration example in Section 4 can be modified as per the example below for Activating and De-activating Entities on the MXL Panel.

// Client Side Connections
//
Connections
Port ,Baud ,Parity ,Data_Bits ,Line_drive_on ,Line_drive_off ,Enhanced_Protocol ,Protocol ,System_Type
P1 ,19200 ,Even ,7 ,0.001 ,0.001 ,No ,Cerberus ,MXL

Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Block_Offset ,Length ,Msg_Type
POLLER_1 ,2.0s ,Counts_1 ,0 ,Rdbc ,Panel1 ,1 ,0 ,19 ,Poller
// this is for activation and deactivation of pseudo points

The configuration example in Section 4 can be modified as per the example below for Activating and De-activating Entities on the XLS panel.

// Client Side Connections
//
Connections

P1 ,19200 ,Even ,7 ,0.001 ,0.001 ,Yes ,Cerberus ,XLS

Map_Descriptors
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Sub_Module ,Block_Offset ,Length ,Msg_Type
POLLER_1 ,2.0s ,Counts_1 ,0 ,Rdbc ,Panel1 ,1 ,- ,0 ,19 ,Poller
// this is for activation and deactivation of pseudo points
PNL_1_Act_Entity ,0s ,Act_Ent ,0 ,Awt ,Panel1 ,1 ,1 ,1 ,10 ,Entity_Activate_Deact

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 28 of 29

Arm_Disarm_Ent

,Bit

,10

//

Map_Descriptors

Map_Descriptors

Appendix A.6. Arming and De-Arming Entities

This example demonstrates the methodology to arm or disarm equipment on the MXL/XLS panel as per the SBT-FSI protocol specification. This relates to the
opcodes Disarm/manuallycontrol entity – opcode 0x77; Arm entity – opcode 0x78,

The configuration example in Section 4 can be modified as per the example below for Arming and De-arming Entities on the MXL Panel.

// Data Arrays
//
Data_Arrays
Data_Array_Name ,Data_Format ,Data_Array_Length
Counts_1 ,Uint16 ,19

// Client Side Connections
//
Connections
Port ,Baud ,Parity ,Data_Bits ,Line_Drive_ On ,Line_Drive_Off ,Enhanced_Protocol ,Protocol ,System_Type
P1 ,19200 ,Even ,7 ,0.001 ,0.001 ,No ,Cerberus ,MXL

// Client Side Map Descriptors

Map_Descriptors
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Arra y_Offset ,Function ,Node_Name ,Block_Number ,Length ,Msg_Type
POLLER_1 ,2.0s ,Counts_1 ,0 ,Rdbc ,Panel1 ,1 ,19 ,Poller

Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function .Node_Name ,Block_Number ,Block_Offset ,Length ,Msg_Type ,Entity_Types
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_Ent ,0 ,Awt ,Pane l1 ,1 ,1 ,10 ,Entity_Arm_Disarm ,Inputs

Map_Descriptors
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,No de_Name ,Block_Number ,Block_Offset ,Length ,Msg_Type ,Entity_Types ,Entity_Energizations
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_Ent ,0 ,Awt ,Pane l1 ,1 ,1 ,10 ,Entity_Arm_Disarm ,Outputs ,De-energize

Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Block_Offset ,Length ,Msg_Type ,Entity_Types ,Entity_Energizations
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_Ent ,0 ,Awt ,Pane l1 ,1 ,1 ,10 ,Entity_Arm_Disarm ,Outputs ,Energize

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-40 SBT FSI Driver Manual Page 29 of 29

Data_Arrays

Connections

Map_Descriptor_Name

,Scan_Interval

,Data_Array_Name

,Data_Array_Offset

,Function

,Node_Name

,Block_Number

,Length

,Msg_Type

The configuration example in Section 4 can be modified as per the example below for Arming and De-arming Entities on the XLS panel.

// Data Arrays
//

Data_Array_Name ,Data_Format ,Data_Array_Length
Counts_1 ,Uint16 ,19
Arm_Disarm_Ent ,Bit ,10

// Client Side Connections
//

Port ,Baud ,Parity ,Data_Bits ,Line_Drive_On ,Li ne_Drive_Off ,Enhanced_Protocol ,Protocol ,System_Type
P1 ,19200 ,Even ,7 ,0.001 ,0.001 ,Yes ,Cerberus ,XLS

// Client Side Map Descriptors
//
Map_Descriptors

POLLER_1 ,2.0s ,Counts_1 ,0 ,Rdbc ,Panel1 ,1 ,19 ,Poller

Map_Descriptors
Map_Descriptor_Name ,Scan_I nterval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Sub_Module ,Component_Address ,Block_Offset ,Length ,Msg_Type ,Entit y_Types
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_Ent ,0 ,Awt ,Panel1 ,1 ,1 ,1 ,1 ,10 ,Entity_Arm_Disarm ,Inputs

Map_Descriptors
Map_Descriptor_ Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Funct ion ,Node_Name ,Block _Number ,Sub_Module ,C omponent_Address ,Block_Offset ,Leng th ,Msg_Type ,Entity_Types ,Entity_Energizations
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_ Ent ,0 ,Awt ,Pan el1 ,1 ,1 ,1 ,1 ,10 ,Entity_Arm_D isarm ,Outputs ,De-energize

Map_Descriptors
Map_Descriptor_ Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Funct ion ,Node_Name ,Block _Number ,Sub_Module ,C omponent_Address ,Block_Offset ,Leng th ,Msg_Type ,Entity_Types ,Entity_Energizations
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_ Ent ,0 ,Awt ,Panel1 ,1 ,1 ,1 ,1 ,10 ,Entity_Arm_ Disarm ,Outputs ,Energize

Map_Descriptors
Map_Descriptor_ Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Funct ion ,Node_Name ,Block _Number ,Sub_Module ,C omponent_Address ,Block_Offset ,Leng th ,Msg_Type ,Entity_Types ,Entity_Energizations
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_ Ent ,0 ,Awt ,Panel1 ,1 ,1 ,1 ,1 ,10 ,Entity_Arm_ Disarm ,IOIOIOIIOI , EDED---DED

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

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]