FieldServer NCA2-NFS2-3030, FS-8700-130 User Manual

-

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-130 Notifier NCA2-NFS2-3030

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after January 2009

Driver Version: 1.02
Document Revision:

1

FS-8700-130 Notifier NCA2/NFS-3030 Manual Table of Contents

TABLE OF CONTENTS

1 Notifier NCA2/NFS2-3030 Description ............................................................................................................ 3

2 Driver Scope of Supply ................................................................................................................................... 3

2.1 Supplied by FieldServer Technologies for this driver ..................................................................................... 3

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

3.1 Hardware Connection Tips / Hints ................................................................................................................. 5

4 Configuring the FieldServer as a Notifier NCA2/NFS2-3030 Client .................................................................. 6

4.1 Panel Status - Memory Mapping ................................................................................................................... 6

4.2 Data Arrays/Descriptors ................................................................................................................................ 8

4.3 Client Side Connection Descriptions .............................................................................................................. 9

4.4 Client Side Node Descriptors ......................................................................................................................... 9

4.5 Client Side Map Descriptors......................................................................................................................... 10

4.5.1 FieldServer Related Map Descriptor Parameters ................................................................................. 10

4.5.2 Driver Related Map Descriptor Parameters ......................................................................................... 10

4.5.3 Map Descriptor Example: Standard example ...................................................................................... 11

5 Configuring the FieldServer as a Notifier NCA2/NFS2-3030 Server ............................................................... 12

Appendix A. Advanced Topics .............................................................................................................................. 13

Appendix A.1. Notifier NCA2/NFS2-3030 Message Types Recognized .................................................................... 13

Appendix A.2. System Trouble Messages ................................................................................................................ 14

Appendix A.3. Node Status ...................................................................................................................................... 18

Appendix A.4. FieldServer Synchronization ............................................................................................................. 18

Appendix A.5. Driver Limitations and Exclusions ..................................................................................................... 19

Appendix B. Troubleshooting tips ........................................................................................................................ 20

Appendix B.1. Connection Tips & Hints ................................................................................................................... 20

Appendix B.2. Networking Tips ............................................................................................................................... 20

Appendix C. Error Messages ................................................................................................................................ 21

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-130 Notifier NCA2/NFS-3030 Manual Page 3 of 22

1 NOTIFIER NCA2/NFS2-3030 DESCRIPTION

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.4 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 4.1. A detailed table presented
in Appendix A.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

2 DRIVER SCOPE OF SUPPLY

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.

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-130 Notifier NCA2/NFS-3030 Manual Page 4 of 22

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

3 HARDWARE CONNECTIONS

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.

Connector Pinouts

TB5 CRT

TB5 Printer

RJ-45

Wire Color Orange/white Blue/white Brown

Function Receive Reference Transmit

Pin CRX REF CTX

Function Receive Reference Transmit

Pin PRX REF PTX

Function Transmit Com Receive

Pin 8 4 1

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-130 Notifier NCA2/NFS-3030 Manual Page 5 of 22

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.

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-130 Notifier NCA2/NFS-3030 Manual Page 6 of 22

SUPERVISORY

4 CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2/NFS2-3030 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 receive
information from a Notifier Panel.

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

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.

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-130 Notifier NCA2/NFS-3030 Manual Page 7 of 22

Medical Emergency

478 – 636

Troubles/Faults

1-4

Parameter Addresses

For each SLC loop per Node

Memory Type : Detector ; Module

Fire Alarm 1 – 159

Security Life 160 – 318

Life Critical 319 – 477

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

Table 1 – Memory Mapping Address Structure.

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

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