Summary of Contents for FieldServer FS-8700-130 Notifier NCA2-NFS2-3030
Page 1
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:...
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.
FS-8700-130 Notifier NCA2/NFS-3030 Manual Page 4 of 22 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. RJ45 Notifier NCA2/NFS2-3030 Rx (Brown)
Page 5 of 22 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. •...
Page 6 of 22 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”...
Page 8 of 22 Data Arrays/Descriptors 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”...
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available on specific hardware. 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: support@fieldserver.com...
Map Descriptor Type starting address for data storage from the Notifier panel. will store data and length 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: support@fieldserver.com...
Page 12 of 22 CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2/NFS2-3030 SERVER This driver cannot be configured as a Server. 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: support@fieldserver.com...
Data for any particular Node is valid while that Node is online and the system is synchronized. Integrity of data for any Node will be lost if the Node goes offline or if synchronism between the FieldServer and the NCA2 Panel is lost.
• Zone information will not be recorded. • To synchronize the FieldServer with the panel, connect the running FieldServer and press the “System Reset” button on the panel. All current events will be re-sent to the FieldServer. • The port must be enabled on the unit and set to 80 columns with NO supervision •...
Communication errors will be experienced if the port is disabled at the panel. Please check the Notifier Manuals on how to enable the panel port connected to the FieldServer and ensure that it is set to 80 columns NO supervision.
Call Tech support. NETWORK Node <%s> Node number was received - it is likely that the message was corrupted 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: support@fieldserver.com...
Page 22
All Data Arrays on the FieldServer are initialized to zero on rebooting or starting up. A zero value in the Data Array assumes no problems with the devices, but if a problem existed before the startup and the device comes out of problem, the FieldServer will attempt to decrease the number of problems by 1 and this generates the error.