SMC Networks FieldServer FS-8700-130 Release note

Driver Version:
1.03
Document Revision:
0
FieldServer
FS-8700-130 Notifier NCA2-NFS2-3030
Driver Manual
(Supplement to the FieldServer Instruction Manual)
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after March 2015

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Contact Information
Contact Information:
Thank you for purchasing the FieldServer.
Please call us for Technical support of the FieldServer product.
Contact Information:
Sierra Monitor Corporation
1991 Tarob Court
Milpitas, CA 95035
Contact number:
[phone]
[phone]
Email: [e-mail]
Website: www.sierramonitor.com

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Table of Contents
TABLE OF CONTENTS
Notifier NCA2/NFS2-3030 Description...............................................................................................41
Driver Scope of Supply .......................................................................................................................422.1 Supplied by FieldServer Technologies for this driver.....................................................................4
Hardware Connections........................................................................................................................533.1 Hardware Connection Tips / Hints..................................................................................................6
Data Array Parameters........................................................................................................................74
Configuring the FieldServer as a Notifier NCA2/NFS2-3030 Client ................................................855.1 Panel Status - Memory Mapping ....................................................................................................8
5.2 Client Side Connection Parameters .............................................................................................10
5.3 Client Side Node Parameters.......................................................................................................11
5.4 Client Side Map Descriptor Parameters.......................................................................................12
5.4.1 FieldServer Related Map Descriptor Parameters .................................................................12
5.4.2 Driver Related Map Descriptor Parameters ..........................................................................12
5.4.3 Map Descriptor Example: Standard example........................................................................13
Configuring the FieldServer as a Notifier NCA2/NFS2-3030 Server.............................................146
Appendix A. Useful Information ..............................................................................................................15
Appendix A.1. Node Status .....................................................................................................................15
Appendix A.2. FieldServer Synchronization............................................................................................15
Appendix A.3. Driver Limitations and Exclusions....................................................................................15
Appendix B. Troubleshooting..................................................................................................................16
Appendix B.1. Connection Tips & Hints ..................................................................................................16
Appendix B.2. Networking Tips...............................................................................................................16
Appendix C. Reference.............................................................................................................................17
Appendix C.1. Notifier NCA2/NFS2-3030 Message Types Recognized.................................................17
Appendix C.2. System Trouble Messages..............................................................................................18
Appendix C.3. Error Messages ...............................................................................................................22
LIST OF FIGURES
Figure 1 - Connection Diagram .............................................................................................................................5

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 4 of 23
NOTIFIER NCA2/NFS2-3030 DESCRIPTION1
The NCA2/NFS2-3030 Serial driver allows the FieldServer to record data from Notifier NCA2 or NFS2-
3030 panels over RS-232 as per NFS2-3030/NCA-2 EIA-232 Protocol & Data Formats 53219 Rev A
1/3/2008. There is no active polling by this driver; the communications are one-way through the panel's
printer or CRT port. The FieldServer acts as a Client; receives messages and records the status of a
Panel. The panel MUST output messages in160 characters ASCII format in English.
This driver is not capable of emulating a Notifier NCA2 or NFS2-3030 panel.
The NCA2 controls all the devices (e.g. 3030, 640 panels) connected on the Notifier network. Each Fire
Alarm Panel on Network is considered as a Node. 240 Nodes can exist on one network. NFS2-3030 can
exist on a network or be self-standing.
NCA2 interacts with other Fire Alarm Panels, records the status of the panels and sends the events to
printer and CRT ports. FieldServer captures these events in text form, parses and stores them in Data
Arrays. These Data Arrays can be monitored by third party tools. Since the FieldServer does not actively
poll for data, the accuracy and timeliness of the stored data is limited to the frequency of update
messages that the Notifier Fire Panel issues.
If a networked panel does not send the 'CLEARED' message for latched points via the NCA2 it is not
possible to detect cleared points unless a system reset is done. It is possible to configure the FieldServer
to clear on reset message from NCA2. See Appendix A.2 for more detail.
Please note that the FieldServer can be configured with a large number of points. The point limits
purchased with the FieldServer prevent the entire database from being accessed in any one application.
It is therefore strongly advisable to ensure that only the point addresses of interest are configured, and
that the FieldServer is purchased with the correct point count.
The types of Notifier messages supported by this driver are summarized in Section 5.1. A detailed table
presented in Appendix C.1 shows each type of NCA2/NFS2-3030 message the FieldServer recognizes
and the effect that it has on the status of the points in the Data Array.
Max Nodes Supported
FieldServer Mode
Nodes
Comments
Client
0
This Driver cannot be used as a Client.
Server
1
Each FieldServer port can connect to only 1 Notifier panel port
DRIVER SCOPE OF SUPPLY2
2.1 Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
Description
FS-8917-16
Pigtail cable for RJ45 Port
FS-8700-130
Driver Manual

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 5 of 23
Figure 1 - Connection Diagram
HARDWARE CONNECTIONS3
The FieldServer is connected to the Notifier NCA2/NFS2-3030 Fire Panel as shown in the following
connection drawing.
Configure the Notifier Panel according to manufacturer’s instructions.
FieldServer
FieldServer Part #
8917-16
Pigtail for RJ45
Port
RJ45
Connection to TB5 Printer
Port.
Notifier NCA2/NFS2-3030
Connect to one of the RS-232
Ports on the FieldServer
P1
CTX CRX REFPTX PRX REF
TB5
Printer CRT
Rx (Brown)
Tx (Orange/White)
Com (Blue/White)
18
Connector Pinouts
TB5 CRT
Function
Receive
Reference
Transmit
Pin
CRX
REF
CTX
TB5 Printer
Function
Receive
Reference
Transmit
Pin
PRX
REF
PTX
RJ-45
Function
Transmit
Com
Receive
Pin
8
4
1
Wire Color
Orange/white
Blue/white
Brown

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 6 of 23
3.1 Hardware Connection Tips / Hints
The FieldServer should preferably be connected to the TB5 Printer port. It is theoretically
possible to connect to the TB5 CRT port, but this has not been fully tested.
The Panel’s port must be enabled and set to 80 Columns Not Supervised.

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 7 of 23
DATA ARRAY PARAMETERS4
Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is
necessary to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant
data.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Data_Array_Name
Provide name for Data Array
Up to 15 alphanumeric
characters
Data_Array_Format
Provide data format. Each Data Array can only
take on one format.
FLOAT, BIT, UInt16, SInt16,
Byte, Packed_Byte,
Swapped_Byte
Data_Array_Length
Number of Data Objects. Must be larger than the
data storage area required by the Map
Descriptors for the data being placed in this
array.
1-10, 000
Example 1
// Data Arrays
Data_Arrays
Data_Array_Name
, Data_Format
, Data_Array_Length
DA_SYS_N2
, Sint16
, 508
DA_N2L01D
, BIT
, 1749
DA_N2L01D_T
, Sint16
, 159
DA_N2L01M
, BIT
, 1749
DA_N2L01M_T
, Sint16
, 159
DA_N2_PANEL
, BIT
, 1056
DA_N2_PANEL_T
, Sint16
, 96
DA_N2_BELL_T
, Sint16
, 4

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 8 of 23
CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2/NFS2-30305CLIENT
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for Notifier NCA2/NFS2-3030 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 required data from Notifier Panels 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.
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
receive information from a Notifier Panel.
5.1 Panel Status - Memory Mapping
The primary purpose of this driver is to record the status of devices connected to the Notifier panel by
interpreting the text messages sent to the printer or CRT port. Not all messages will be interpreted, as
many messages do not directly pertain to device status, or are not currently supported. The following
subset of event messages is recognized:
Active Events:
FIRE ALARM
SECURITY ALARM (LIFE)
LIFE CRITICAL ALARM
MEDICAL EMERGENCY
SECURITY ALARM
CRITICAL PROCESS
SUPERVISORY
TROUBLE/ FAULT
DISABLED
PREALARM
ACTIVE
ON/ OFF
This Driver divides the memory into various types. Each location in each memory type is assigned an
address. It is therefore possible to map an address to a particular offset in a Data Array and make it
accessible for reading by other connected devices. The address structure is provided in Table 1.
Most of these addresses will only contain binary information to represent an active or inactive state.
Where multiple troubles are associated with a single device the addressed register corresponding to that
device will be incremented as a counter for each trouble message and decremented when a trouble is
cleared. These addresses should preferably be stored in SINT16 format in the Data Array.

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 9 of 23
Parameter
Addresses
For each SLC loop per Node
Memory Type : Detector ; Module
Fire Alarm
1 –159
Security Life
160 –318
Life Critical
319 –477
Medical Emergency
478 –636
Security Alarm
637 –795
Critical Process
796 –954
Supervisory
955 - 1113
Disabled
1114 –1272
Prealarm
1273 –1431
Active
1432 –1590
ON/OFF
1591 –1749
Memory Type : Detector_Trouble; Module_Trouble
Troubles/Faults
1 –159
Parameter
Addresses
For each Node
Memory Type : Node_Trouble
Troubles/Faults
1 –508
Memory Type : Panel
Panel (Maximum12 Boards and 8 Panel circuits per Board )
Hardware address memory address
Board 1 panel 1 1
Board 1 panel 2 2
Board 2 panel 1 9
-----
-----
Board 12 panel 8 96
)
Fire Alarm
1 –96
Security Life
97 - 192
Life Critical
193 - 288
Medical Emergency
289 - 384
Security Alarm
385 - 480
Critical Process
481 - 576
Supervisory
577 - 672
Disabled
673 - 768
Prealarm
769 - 864
Active
865 - 960
ON/OFF
961 - 1056
Memory Type : Panel_Trouble
Troubles/Faults
1–96
Memory Type : Bell_Trouble
Troubles/Faults
1-4
Table 1 –Memory Mapping Address Structure.

FS-8700-130 Notifier NCA2-NFS2-3030 Manual
Page 10 of 23
5.2 Client Side Connection Parameters
Section Title
Connections
Column Title
Function
Legal Values
Port
Specify which port the device is connected to
the FieldServer
P1-P81
Protocol
Specify protocol used
nfs2-nca; nca2; nfs2-3030
Baud*
Specify baud rate
CRT Port
4800; 9600; 19200; 38400; 57600;
(Vendor limitation)
Printer Port
9600 (Vendor limitation)
Parity*
Specify parity
None (Vendor limitation)
Data_Bits*
Specify data bits
8(Vendor limitation)
Stop_Bits*
Specify stop bits
1(Vendor limitation)
Example
// Client Side Connections
Connections
Port
, Protocol
, Baud
, Stop_Bits
, Parity
P8
, nfs2-nca
, 9600
, 1
, None
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports
available on specific hardware.