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:  
Document Revision:  
1.08  
3
FS-8700-40 SBT FSI Driver Manual  
Page 3 of 29  
1
SBT-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-1R1 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  
FieldServer Mode  
Nodes  
Comments  
1-10 (one Client per physical  
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  
FS-8700-40  
RJ45 to DB9F connector adapter  
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 )  
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.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
               
FS-8700-40 SBT FSI Driver Manual  
Page 4 of 29  
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-1R3 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.  
TB2  
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
TB7  
1
2
TB4  
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
P3  
14  
15  
16  
CERBERUS CABLE  
P/N 555-193085  
1
Cerberus Cable  
8917-03  
COLOR  
RED  
DB9  
2 Rx  
P3  
14  
555-193085  
1
GREEN  
BLACK  
BROWN  
WHITE  
3 Tx  
13  
16  
12  
15  
SPA59132  
5 GND  
7 RTS  
8 CTS  
8915-10  
FieldServer  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
     
FS-8700-40 SBT FSI Driver Manual  
Page 5 of 29  
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.  
Panel  
Panel  
Panel  
FSI  
8
1
FieldServer  
P1  
Configuration 2 – One FSI Panel per FieldServer port, 3 panels connected in series to the FSI  
Panel  
Panel  
FSI  
FSI  
8
1 8  
1
FieldServer  
P1  
P2  
Configuration 1 – One FSI Panel per FieldServer per port, one Panel per FSI  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Page 6 of 29  
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  
Fire Alarm In  
Fire Alarm Out  
Fire Alarm Acknowledge  
Trouble In  
Trouble Out  
Trouble Acknowledge  
Supervisory In  
Supervisory Out  
Supervisory Acknowledge  
Security Alarm In  
Counter Offset  
Event  
Security Alarm Out  
Security Alarm Acknowledge 11  
Status In  
Status Out  
Test In  
Test Out  
Audible Silenced  
Audible Unsilenced  
System Reset  
Counter Offset  
10  
0
1
2
3
4
5
6
7
8
9
12  
13  
14  
15  
16  
17  
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  
Fire Alarm  
Msg_Type  
Fire  
Array  
Security Alarm  
Msg_Type  
Secur  
Fire Alarm Un-Acknowledged  
Trouble Alarm  
Trouble Un-Acknowledged  
Supervisory Alarm  
Supervisory Un-Acknowledge  
Fire_Ack  
Trouble  
Trouble_Ack  
Super  
Security Alarm Un-Acknowledged Secur_Ack  
Status  
Test  
Status  
Test  
Audible (Un)Silenced  
System Reset  
Audible  
Reset  
Super_Ack  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Notes  
Page 7 of 29  
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
3
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.  
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
5
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.  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-40 SBT FSI Driver Manual  
Page 8 of 29  
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  
Up to  
15  
Data_Array_Name  
Provide name for Data Array  
alphanumeric  
characters  
Provide data format. Each Data Array can only take on one  
format.4  
Data_Array_Format  
Int16, Uint16, Bit  
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 1-10,000  
this array.  
Example  
// Data Arrays  
Data_Arrays  
Data_Array_Name ,Data_Format ,Data_Array_Length  
Event_Counts  
Fire  
Fire_UnAck  
,Uint16  
,Bit  
,Bit  
,19  
,2048  
,2048  
4Format must be Uint16 or Int16 to see trouble codes.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
   
FS-8700-40 SBT FSI Driver Manual  
Page 9 of 29  
4.2 Client Side Connection Descriptions  
Section Title  
Connections  
Column Title  
Port  
Function  
Legal Values  
Specify which port the device is connected to the FieldServer  
P1-P8, R1-R25  
Cerberus,  
SBT-FSI  
Protocol  
Specify protocol used  
Enables legacy or enhanced protocol.. MXL panels do not currently  
support Enhanced_Protocol, so this parameter must be set to “No” for Yes (XLS)  
MXL. The parameter is normally set to “Yes” for XLS, but may be set to No (MXL)  
“No” if problems are being experienced.  
Enhanced_Protocol  
System_Type  
Block_Acks6  
Specifies Siemens Panel type  
MXL, XLS  
Yes, No  
Specifies if the driver uses block or individual command acks  
Specifies if the driver should hold fire alarms until the system reset, or  
clear on fire alarms going out  
Fire_Alarms_Hold  
Yes, No  
19200  
Baud*  
Specify baud rate  
(Vendor  
limitation)  
Even (Vendor  
limitation)  
Parity*  
Specify parity  
7
(Vendor  
Data_Bits*  
Specify data bits  
limitation)  
1
(Vendor  
Stop_Bits*  
Specify stop bits  
limitation)  
None  
Handshaking7*  
Specify hardware handshaking  
0-32000  
seconds,  
second  
Poll _Delay*  
Time between internal polls  
1
Example  
// Client Side Connections  
Connections  
Port ,Protocol ,Baud  
,Parity ,Data_Bits ,Poll_Delay  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
       
FS-8700-40 SBT FSI Driver Manual  
Page 10 of 29  
4.3 Client Side Node Descriptors  
Section Title  
Nodes  
Column Title Function  
Node_Name Provide name for node  
Legal Values  
Up to 32 alphanumeric characters  
1-99  
Node_ID  
Protocol  
Panel number  
Specify protocol used  
Cerberus, SBT-FSI  
Specify on which port the device is connected to the  
FieldServer  
Port  
P1-P8, R1-R21  
Example  
// Client Side Nodes  
Nodes  
Node_Name ,Node_ID ,Protocol ,Port  
Panel1  
,1  
,SBT-FSI  
,P1  
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  
Name of Data Array where data  
Up to 32 alphanumeric characters  
One of the Data Array names from “Data Array”  
section above  
Data_Array_Name  
is to be stored in the  
FieldServer  
0 to maximum specified in “Data Array” section  
above  
Data_Array_Offset  
Starting location in Data Array  
Rdbc for Msg_Type:  
Poller, Analog_Volts, Analog_Sense, Analog_Thres  
Passive for Msg_Type:  
Function of Client Map Fire, Fire_Ack, Trouble, Trouble_Ack, Secur,  
Function  
Descriptor  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
     
FS-8700-40 SBT FSI Driver Manual  
Page 11 of 29  
4.4.2 Driver Related Map Descriptor Parameters  
Column Title  
Node_Name  
Function  
Legal Values  
Name of Node to fetch or store One of the node names specified in “Client Node  
data from  
Descriptor” above  
Starting module number within  
Block_Number  
panel. There are 256 points per 1 – 256  
module.  
Sub module number for XLS  
systems only  
Sub_Module  
0 – 99  
Component address for XLS  
systems only  
Component_Address  
0 – 99  
Length of Map Descriptor  
specifies number of points. There 1 – 10000  
are 256 points per module.  
Length  
Indicates  
a
“poller”  
Map Poller; Fire; Fire_Ack; Trouble; Trouble_Ack; Super;  
Descriptor or identifies the type Super_Ack; Secur; Secur_Ack; Status; Test; Audible;  
of event message this Map Reset; Analog_Volts; Analog_Sense; Analog_Thres;  
Descriptor will handle.  
Msg_Type  
Entity_Arm_Disarm8; Entity_Activate_Deact9  
0 : devices 1-60  
1 : devices 61-121  
2 : devices 122-182  
3 : devices 183-243  
Indicates range of device data to  
be requested by analogs  
Analog_Device  
4 : devices 244-252  
This field allows you to set the  
Block_Offset  
Entity_Types  
start address of a MXL or XLS 0 - 255  
point in a Map Descriptor.  
Used to indicate the type of Entity Inputs, Outputs, (If all elements are Input or Output)  
on the panel.. . Refer to Appendix OR specify each element of the entity individually  
A.6 for more information  
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  
Used to control the entity on the  
Entity_Energizations panel. Refer to Appendix A.6 for  
more information.  
4.4.3 Timing Parameters  
Column Title  
Function  
Legal Values  
Scan_Interval* Rate at which data is polled ≥0.001s ,1.0s  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
       
FS-8700-40 SBT FSI Driver Manual  
Page 12 of 29  
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  
Specify length  
in multiples of  
19 events  
according to  
Block Number  
used.  
Choose a  
Node_Name  
from the  
passive Map  
Descriptors in  
the next section  
to specify the  
port on which  
this poller will  
be active.  
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  
Specifies lowest panel  
number from which  
events will be  
received. Refer to  
Appendix A for more  
information.  
Specify poller  
message type  
for this Map  
Descriptor.  
counters  
Data Array  
where event  
counts will be  
stored.  
Refer to  
for more  
information.  
CD – Client Descriptor  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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  
,0  
,0  
,0  
,0  
,0  
,0  
,0  
,0  
,0  
,0  
,0  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Passive  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,1  
,1  
,1  
,1  
,1  
,1  
,1  
,1  
,1  
,1  
,-  
,1024  
,1024  
,1024  
,1024  
,1024  
,1024  
,1024  
,1024  
,1024  
,1024  
,1  
,Fire  
CD_Fire_Ack1  
CD_Trouble1  
CD_Trouble_Ack1  
CD_Super1  
CD_Super_Ack1  
CD_Secur1  
CD_Secur_Ack1  
CD_Status1  
CD_Test1  
,Fire_Ack  
,Trouble  
,Trouble_Ack  
,Super  
,Super_Ack  
,Secur  
,Secur_Ack  
,Status  
,Test  
,Fire_Ack  
,Trouble  
,Trouble_Ack  
,Super  
,Super_Ack  
,Secur  
,Secur_Ack  
,Status  
,Test  
CD_Audible1  
CD_Reset1  
,Audible  
,Reset  
,Audible  
,Reset  
,-  
,1  
CD – Client Descriptor  
Node Name specifies the panel  
number for which events will  
be stored.  
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.  
Notes:  
1
2
3
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.  
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  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
CD_Analog_Sens1  
CD_Analog_Thres1  
,Analog_Volts  
,Analog_Sense  
,Analog_Thres  
,0  
,0  
,0  
,Rdbc  
,Rdbc  
,Rdbc  
,Panel1  
,Panel1  
,Panel1  
,1  
,1  
,1  
,60  
,60  
,60  
,Analog_Volts  
,Analog_Sense ,0  
,Analog_Thres ,0  
,0  
,300s  
,300s  
,300s  
0 : devices 1-60  
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.  
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.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Page 17 of 29  
6.1 Server Side Connection Descriptors  
Section Title  
Connections  
Column Title  
Port  
Protocol  
Function  
Legal Values  
Specify which port the device is connected to the FieldServer  
Specify protocol used  
P1-P8, R1-R210  
Cerberus, SBT-FSI  
Enables legacy or enhanced protocol.. MXL panels do not currently  
support Enhanced_Protocol, so this parameter must be set to “No” Yes (XLS)  
for MXL. The parameter is normally set to “Yes” for XLS, but may be No (MXL)  
set to “No” if problems are being experienced.  
Enhanced_Protocol  
System_Type  
Echo  
Specifies Siemens Panel type  
Specifies if the server should echo the client’s polls  
MXL, XLS  
Yes, No  
110 – 115200,  
standard baud  
rates only, 19200  
Even, Odd, None,  
Mark, Space  
7, 8  
1 (Vendor  
limitation)  
None  
Baud*  
Specify baud rate  
Parity*  
Specify parity  
Data_Bits*  
Stop_Bits*  
Handshaking11*  
Specify data bits  
Specify stop bits  
Specify hardware handshaking  
Specifies time FieldServer will reserve Server side connection while  
Server_Hold_Timeout waiting for the Client side to update data in Data_Array (if >1.0s  
necessary)  
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.  
11 Handshaking is not supported.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
     
FS-8700-40 SBT FSI Driver Manual  
Page 18 of 29  
6.2 Server Side Node Descriptors  
Section Title  
Nodes  
Column Title  
Function  
Legal Values  
Up to  
32  
Node_Name  
Provide name for node  
alphanumeric  
characters  
Node_ID  
Protocol  
Panel number  
Specify protocol used  
1-99  
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  
Panel1 ,1 ,SBT-FSI  
,
6.3 Server Side Map Descriptors  
6.3.1 FieldServer Specific Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
Up to 32 alphanumeric  
characters  
Map_Descriptor_Name Name of this Map Descriptor  
One of the Data Array names  
from “Data Array” section  
above  
Name of Data Array where point data is to be fetched  
from  
Data_Array_Name  
0 to maximum specified in  
“Data Array” section above  
Server  
Data_Array_Offset  
Function  
Starting location in Data Array  
Function of Server Map Descriptor  
Specifies time FieldServer will reserve Server side  
Server_Hold_Timeout* connection while waiting for the Client side to update >1.0s  
data in Data_Array (if necessary)  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
       
FS-8700-40 SBT FSI Driver Manual  
Page 19 of 29  
6.3.2 Driver Specific Map Descriptor Parameters  
Column Title  
Node_Name  
Function  
Legal Values  
Name of Node or panel for which this Map One of the node names specified  
Descriptor holds points  
in “Client Node Descriptor” above  
Module number (Note that this only specifies one  
Block_Number  
Sub_Module  
Component_Address Component address in XLS system  
Length of Map Descriptor  
module number as opposed to a starting module 1 – 256  
number as in the Client Map Descriptor)  
Sub module in XLS system  
0 – 99  
0 – 99  
Specifies number of points for the indicated module.  
Note that MXL systems typically has only 256 points  
per module.  
Length  
1 – 256  
Fire;  
Fire_Ack;  
Trouble;  
Type of event message  
Trouble_Ack; Secur; Secur_Ack;  
Msg_Type  
Note that a poller message type may not be used in Super; Super_Ack; Status; Test;  
a Server Map Descriptor.  
Audible; Reset; Analog_Volts;  
Analog_Sense; Analog_Thres  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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  
,0  
,0  
,256  
,0  
,0  
,0  
,0  
,0  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Server  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,Panel1  
,1  
,1  
,1  
,2  
,1  
,1  
,1  
,1  
,1  
,1  
,-  
,256  
,256  
,256  
,256  
,256  
,256  
,256  
,256  
,256  
,256  
,1  
,Fire  
SD_Fire_Ack1  
SD_Trouble1  
SD_Trouble2  
SD_Trouble_Ack1  
SD_Super1  
SD_Super_Ack1  
SD_Secur1  
SD_Secur_Ack1  
SD_Status1  
,Fire_Ack  
,Trouble  
,Trouble  
,Trouble_Ack  
,Super  
,Super_Ack  
,Secur  
,Secur_Ack  
,Status  
,Fire_Ack  
,Trouble  
,Trouble  
,Trouble_Ack  
,Super  
,Super_Ack  
,Secur  
,Secur_Ack  
,Status  
,0  
,0  
,0  
SD_Audible1  
SD_Reset1  
,Audible  
,Reset  
,Audible  
,Reset  
,-  
,1  
Specifies the number  
of points represented  
within the indicated  
module.  
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.  
Notes:  
1
2
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.  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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  
SD_Analog_Sense1  
SD_Analog_Thres1  
,Volts  
,Sense  
,Thres  
,0  
,0  
,0  
,Server  
,Server  
,Server  
,Panel1  
,Panel1  
,Panel1  
,1  
,1  
,1  
,252  
,252  
,252  
,Analog_Volts  
,Analog_Sense  
,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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
   
FS-8700-40 SBT FSI Driver Manual  
Page 23 of 29  
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  
Checksum or Parity Ensure connection baudrate, start, stopbits and parity match the panel's  
Reason 1  
fail  
settings  
Reason 2 Receive buffer full  
Increase scan interval on the poller Map Descriptor.  
Check integrity of physical connection to panel, route cables away from  
electromagnetic sources that can generate noise.  
Reason 3 Syntax Error  
Unrecognized  
Reason 4  
Replace hardware?  
message failure  
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  
Corresponds to Block Number 1  
Page: 5  
===============================================================================  
Corresponds to Block Array point 1  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
   
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
Trouble Type Trouble Type Text  
28  
29  
30  
31  
32  
33  
34  
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
Open Circuit  
Voltage Low  
Zone Power Loss  
Loop Node  
1
2
3
4
5
6
Multiple Response  
Communication Error  
Input Dev. Response too low  
Device Receive Error  
Dev Detected Waveform Error  
Not Responding  
Not defined  
Multiple Response  
MOI-1 Local Trouble  
MOI-1 Zone Trouble  
No database – default in use  
Too Many ALD-2’s  
PSR-1 Driver Disarmed  
Output Disarmed  
Not Responding  
Unspecified Module Responding  
Communication Failure  
RAM Failure  
ROM Failure  
A/D Convert Fail  
7
Not Responding  
8
9
Unspecified Dev. Responding  
Incorrect ID  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
INPUT DE-ISOLATED  
INPUT ISOLATED  
Input Disarmed  
Addressable Relay disarmed  
Relay Disarmed  
Signal Circuit Disarmed  
Solid State Output Disarmed  
Relay Supervision Failure  
Signal Circuit Loop Open  
Loop Disarmed  
Single Module Zone Code  
Command Not Valid  
Network A Pair Fail  
Class A Trouble  
Relay Driver Inoperative  
Signal Circuit Shorted  
ALD Reception Error  
Coil Open  
Zone Power Off  
Power Cycling  
Loss of 24V Input Power  
Act Power Voltage Low  
Default Trouble Active  
Network Disabled  
Alarm from Isolated Device  
Printer off-line  
Short Circuit  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Page 25 of 29  
Trouble Type Trouble Type Text  
Trouble Type Trouble Type Text  
Valve Tamper Point  
56  
57  
58  
59  
60  
61  
62  
63  
64  
65  
66  
67  
68  
69  
70  
71  
72  
73  
74  
75  
76  
77  
78  
79  
80  
81  
82  
83  
84  
85  
86  
87  
88  
89  
90  
91  
92  
93  
94  
95  
96  
97  
98  
99  
100  
Warm Reset  
101  
102  
103  
104  
105  
106  
107  
108  
109  
110  
111  
112  
113  
114  
115  
116  
117  
118  
119  
120  
121  
122  
123  
124  
125  
126  
127  
128  
129  
130  
131  
132  
133  
134  
135  
136  
137  
138  
139  
140  
141  
142  
143  
144  
145  
Printer out of Power  
Tamper Switch  
Battery Backup Invalid  
Positive Ground Fault  
Negative Ground Fault  
AC Fail/brownout  
WALKTEST Activated  
Function Recursion Limit Exceeded  
Trouble Causing Input  
Carrier Loss  
Missing Device ID Response  
Annunciator Trouble  
CMI-300 general trouble  
ROM SW version error  
Lamp Supervision Trouble  
Keyswitch Activated  
Ancillary Cntrl Funcs Isolated  
Ancillary Cntrl Funcs De-Isolated  
Pre-dirty Analog volt reached  
IEC limit reached. Service Req  
IEC memory error  
NET-7 General Trouble  
Network B Pair Failure  
MOI-1 Voice System Trouble  
Style 4 Network mode  
Aux. RS232 Transmit Fail  
Module Address Buffer Fail  
Incorrect Enclosure  
System Signal Power Failure  
Battery Fuse/Wiring Open  
24 Volt Supply Over/Under  
High Battery Voltage  
Battery Charger Off  
24 Volts on Battery Backup  
Low Battery voltage  
Watchdog Triggered  
Device LED Manually Activated  
Alarm queue full  
Supervisory queue full  
Trouble queue full  
Security queue full  
Memory error in Ram text  
Memory error in ROM text  
Aux Pwr Class A Fail Pos  
Aux Pwr Class A Fail Neg  
Supervisory Point  
OCC-1 General Trouble  
OCC-1 Degrade Mode  
Backup Tone Card (BTC)  
Daily detector test abnormal  
Event log 80% full  
Security Point  
BELL 2 ISOLATED  
BELL 2 DE-ISOLATED  
Configuration Error  
Addressable Relay Isolated  
Relay Isolated  
Single Circuit Isolated  
Solid State Output Isolated  
Class A Fault  
Event log 90% full  
Log FULL, events will be lost  
Audio Riser 1 Trouble  
Audio Riser 2 Trouble  
Audio Riser 3 Trouble  
Mic Key Trouble  
Mic Pre-amp Trouble  
Tone Generator Trouble  
Mic Input Trouble  
Telephone Riser Trouble  
Mic Key Trouble  
Amplifier 1 Trouble  
Amplifier 2 Trouble  
Amplifier 3 Trouble  
Noise Fault  
MOI-1 Local Fault  
MOI-1 Zone Isolated  
PSR-1 Driver Isolated  
Fault queue full  
Isolated Alarm queue full  
Isolated Alarm point  
Requires Service  
MVP General Trouble  
Valve Tamper queue full  
Amplifier 1 Backed Up  
Amplifier 2 Backed Up  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-40 SBT FSI Driver Manual  
Page 26 of 29  
Trouble Type Trouble Type Text  
Trouble Type Trouble Type Text  
Audio fault iso-St 7Tx  
146  
147  
148  
149  
150  
Amplifier 3 Backed Up  
Multiple Response  
Communication Error  
Not Responding  
Unspecified  
189  
190  
191  
192  
193  
194  
195  
196  
197  
298  
199  
200  
201  
202  
203  
204  
205  
206  
207  
208  
209  
210  
211  
212  
213  
214  
215  
216  
217  
218  
219  
220  
221  
222  
223  
224  
225  
226  
227  
228  
229  
230  
231  
Audio fault iso-St 7Rx  
Audio fault iso-St 4Tx  
Audio fault iso-St 4Rx  
Multiple Response  
Global audio riser-St 7  
Global audio riser-St 4  
Local audio riser  
Database Out of Date  
ASD disabled for test  
Sys halt – too many ALD/ACM  
DMC-1 in record mode  
DMC-1 tone trouble  
DMC-1 phrase trouble  
Troubles summarized  
Sub-module  
Responding  
151  
152  
153  
154  
155  
156  
157  
158  
159  
160  
161  
162  
163  
164  
165  
166  
167  
168  
169  
170  
171  
172  
173  
174  
175  
176  
177  
178  
179  
180  
181  
182  
183  
184  
185  
186  
187  
188  
Incorrect ID  
Audio Riser 1 Class A Active  
Audio Riser 2 Class A Active  
Audio Riser 3 Class A Active  
Backup Amplifier Trouble  
Daily Detector Test Abnormal  
Low IEC voltage. Service Req.  
Audio Output Shorted  
Audio Output Class A Active  
Amplifier 1 Signal Loss  
Amplifier 2 Signal Loss  
Amplifier 3 Signal Loss  
Generic Input Terminal  
DMU 1 Failure  
Incorrect custom phrase control  
Remote node disconnected  
History manually turned off  
History manually turned on  
History manually erased  
Memory upgrade required  
Event queue corrupt  
Current sensor failure  
EEprom error  
No application firmware  
Component disarmed  
Zone 1 open  
DMU 2 Failure  
Out of RAM. Call factory  
Incorrect Node Address  
Not Responding  
Unspecified Node Responding  
Node Disconnected  
Network CSGM Upload Needed  
Style 7 Network Mode  
Network input disarmed  
Out of task – Call factory  
Stack Fault – Call factory  
Software Key Violation  
Airflow too low  
Airflow too high  
Detector Trouble  
AnaLASER General Trouble  
Pre1 level  
Pre2 level  
Zone 2 open  
Zone 1 short  
Zone 2 short  
Zone 1 Class A return fault  
Zone 2 Class A return fault  
Input source malfunction  
Over current fault  
Log failure, events lost  
24V 4amp supply shutdown  
24V 12amp supply shutdown  
Backplane power shutdown  
No battery detected  
Incorrect library version  
Out of calibration  
AnaLASER Power Trouble  
Pre-alarm  
+15volt fault  
Strobe power fault  
Thermistor Trouble  
Configuration process failure  
Device(s) with no address  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-40 SBT FSI Driver Manual  
Page 27 of 29  
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  
P1  
,Baud  
,19200 ,Even  
,Parity ,Data_Bits ,Line_drive_on ,Line_drive_off ,Enhanced_Protocol ,Protocol  
,System_Type  
,7 ,0.001 ,0.001 ,No ,Cerberus ,MXL  
Map_Descriptors  
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Block_Offset ,Length ,Msg_Type  
POLLER_1  
// this is for activation and deactivation of pseudo points  
PNL_1_Act_Entity ,0s ,Act_Ent  
,2.0s  
,Counts_1  
,0  
,Rdbc  
,Panel1  
,1  
,0  
,19  
,Poller  
,0  
,Awt  
,Panel1  
,1  
,1  
,10  
,Entity_Activate_Deact  
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  
Port  
P1  
,Baud  
,19200 ,Even  
,Parity ,Data_Bits ,Line_drive_on ,Line_drive_off ,Enhanced_Protocol ,Protocol  
,System_Type  
,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  
// this is for activation and deactivation of pseudo points  
PNL_1_Act_Entity ,0s ,Act_Ent  
,2.0s  
,Counts_1  
,0  
,Rdbc  
,Panel1  
,1  
,-  
,0  
,19  
,Poller  
,0  
,Awt  
,Panel1  
,1  
,1  
,1  
,10  
,Entity_Activate_Deact  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Page 28 of 29  
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  
Counts_1  
Arm_Disarm_Ent  
,Data_Format  
,Uint16  
,Bit  
,Data_Array_Length  
,19  
,10  
// Client Side Connections  
//  
Connections  
Port  
P1  
,Baud  
,19200  
,Parity  
,Even  
,Data_Bits  
,7  
,Line_Drive_On  
,0.001  
,Line_Drive_Off  
,0.001  
,Enhanced_Protocol  
,No  
,Protocol  
,Cerberus  
,System_Type  
,MXL  
// Client Side Map Descriptors  
//  
Map_Descriptors  
Map_Descriptor_Name  
POLLER_1  
,Scan_Interval  
,2.0s  
,Data_Array_Name  
,Counts_1  
,Data_Array_Offset  
,0  
,Function  
,Rdbc  
,Node_Name  
,Panel1  
,Block_Number  
,1  
,Length  
,19  
,Msg_Type  
,Poller  
Map_Descriptors  
Map_Descriptor_Name  
PNL_1_Arm_Disarm  
,Scan_Interval  
,0s  
,Data_Array_Name  
,Arm_Disarm_Ent  
,Data_Array_Offset  
,0  
,Function  
,Awt  
.Node_Name  
,Panel1  
,Block_Number  
,1  
,Block_Offset  
,1  
,Length  
,10  
,Msg_Type  
,Entity_Arm_Disarm  
,Entity_Types  
,Inputs  
Map_Descriptors  
Map_Descriptor_Name  
PNL_1_Arm_Disarm  
,Scan_Interval  
,0s  
,Data_Array_Name  
,Arm_Disarm_Ent  
,Data_Array_Offset  
,0  
,Function  
,Awt  
,Node_Name  
,Panel1  
,Block_Number  
,1  
,Block_Offset  
,1  
,Length  
,10  
,Msg_Type  
,Entity_Arm_Disarm  
,Entity_Types  
,Outputs  
,Entity_Energizations  
,De-energize  
Map_Descriptors  
Map_Descriptor_Name  
PNL_1_Arm_Disarm  
,Scan_Interval  
,0s  
,Data_Array_Name  
,Arm_Disarm_Ent  
,Data_Array_Offset  
,0  
,Function  
,Awt  
,Node_Name  
,Panel1  
,Block_Number  
,1  
,Block_Offset  
,1  
,Length  
,10  
,Msg_Type  
,Entity_Arm_Disarm  
,Entity_Types  
,Outputs  
,Entity_Energizations  
,Energize  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
 
FS-8700-40 SBT FSI Driver Manual  
Page 29 of 29  
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_Arrays  
Data_Array_Name  
Counts_1  
Arm_Disarm_Ent  
,Data_Format  
,Uint16  
,Bit  
,Data_Array_Length  
,19  
,10  
// Client Side Connections  
//  
Connections  
Port  
P1  
,Baud  
,19200  
,Parity  
,Even  
,Data_Bits  
,7  
,Line_Drive_On  
,0.001  
,Line_Drive_Off  
,0.001  
,Enhanced_Protocol  
,Yes  
,Protocol  
,Cerberus  
,System_Type  
,XLS  
// Client Side Map Descriptors  
//  
Map_Descriptors  
Map_Descriptor_Name  
POLLER_1  
,Scan_Interval  
,2.0s  
,Data_Array_Name  
,Counts_1  
,Data_Array_Offset  
,0  
,Function  
,Rdbc  
,Node_Name  
,Panel1  
,Block_Number  
,1  
,Length  
,19  
,Msg_Type  
,Poller  
Map_Descriptors  
Map_Descriptor_Name  
PNL_1_Arm_Disarm  
,Scan_Interval  
,0s  
,Data_Array_Name  
,Arm_Disarm_Ent  
,Data_Array_Offset  
,0  
,Function  
,Awt  
,Node_Name  
,Panel1  
,Block_Number  
,1  
,Sub_Module  
,1  
,Component_Address  
,1  
,Block_Offset  
,1  
,Length  
,10  
,Msg_Type  
,Entity_Arm_Disarm  
,Entity_Types  
,Inputs  
Map_Descriptors  
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Sub_Module ,Component_Address ,Block_Offset ,Length ,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  
,De-energize  
Map_Descriptors  
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Block_Number ,Sub_Module ,Component_Address ,Block_Offset ,Length ,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 ,Function ,Node_Name ,Block_Number ,Sub_Module ,Component_Address ,Block_Offset ,Length ,Msg_Type  
PNL_1_Arm_Disarm ,0s ,Arm_Disarm_Ent ,0 ,Awt ,Panel1 ,1 ,1 ,1 ,1 ,10  
,Entity_Types ,Entity_Energizations  
,Entity_Arm_Disarm ,IOIOIOIIOI  
, EDED---DED  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  

Motorola MC9S12DT128B User Manual
HTC DROID Eris PB00100 User Manual
Harman Kardon CDR 30 User Manual
Hamilton Beach Commercial coffeemaker User Manual
Clarion iDXZ775USB User Manual
Butler 645 260 User Manual
Bosch Appliances GSM Com 608 User Manual
Bloomfield 9102A User Manual
Black & Decker DLX1050B User Manual
Aiwa XP V733 User Manual