FieldServer Computer Drive 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:  
Document Revision:  
1.02  
1
 
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  
Server  
0
1
This Driver cannot be used as a Client.  
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  
FS-8700-130  
Pigtail cable for RJ45 Port  
Driver Manual.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 4 of 22  
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.  
RJ45  
Notifier NCA2/NFS2-3030  
Rx (Brown)  
Com (Blue/White)  
Tx (Orange/White)  
Connection to TB5 Printer  
Port.  
Printer  
CRT  
TB5  
PTX PRX REF CTX CRX REF  
FieldServer Part #  
8917-16  
Pigtail for RJ45  
Port  
Connect to one of the RS-232  
Ports on the FieldServer  
8
1
FieldServer  
P1  
Connector Pinouts  
Function Receive  
Pin CRX  
Function Receive  
Pin PRX  
Function Transmit  
Pin  
Reference Transmit  
REF CTX  
Reference Transmit  
TB5 CRT  
TB5 Printer  
REF  
Com  
4
PTX  
Receive  
1
RJ-45  
8
Wire Color  
Orange/white Blue/white Brown  
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-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: (408) 262-2299 Fax: (408) 262-2269 Toll Free: (888) 509-1970 email: [email protected]  
 
 
FS-8700-130 Notifier NCA2/NFS-3030 Manual  
Page 6 of 22  
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  
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.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 7 of 22  
Parameter  
Addresses  
For each SLC loop per Node  
Memory Type : Detector ; Module  
Fire Alarm  
1 – 159  
Security Life  
Life Critical  
Medical Emergency  
Security Alarm  
Critical Process  
Supervisory  
Disabled  
Prealarm  
Active  
ON/OFF  
160 – 318  
319 – 477  
478 – 636  
637 – 795  
796 – 954  
955 - 1113  
1114 – 1272  
1273 – 1431  
1432 – 1590  
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  
Board 1 panel 1  
Board 1 panel 2  
Board 2 panel 1  
-----  
memory address  
1
2
9
-----  
Board 12 panel 8  
)
96  
Fire Alarm  
1 – 96  
Security Life  
Life Critical  
Medical Emergency  
Security Alarm  
Critical Process  
Supervisory  
Disabled  
Prealarm  
Active  
ON/OFF  
97 - 192  
193 - 288  
289 - 384  
385 - 480  
481 - 576  
577 - 672  
673 - 768  
769 - 864  
865 - 960  
961 - 1056  
Memory Type : Panel_Trouble  
Troubles/Faults  
1–96  
Memory Type : Bell_Trouble  
Troubles/Faults  
1-4  
Table 1 – Memory Mapping Address Structure.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 8 of 22  
4.2 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” 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.  
Section Title  
Data_Arrays  
Column Title  
Function  
Legal Values  
Up to 15 alphanumeric  
characters  
Data_Array_Name  
Provide name for Data Array  
Provide data format. Each Data Array can only take on one  
format.  
Data_Array_Format  
Bit, Sint16, Float1  
Number of Data Objects. Must be larger than the data  
Data_Array_Length storage area required by the Map Descriptors for the data 1-10,000  
being placed in this array.  
Example 1  
// Data Arrays  
Data_Arrays  
Data_Array_Name ,Data_Format ,Data_Array_Length  
DA_SYS_N2  
DA_N2L01D  
,SINT16  
,BIT  
,SINT16  
,BIT  
,SINT16  
,BIT  
,SINT16  
,SINT16  
,508  
,1749  
,159  
,1749  
,159  
,1056  
,96  
DA_N2L01D_T  
DA_N2L01M  
DA_N2L01M_T  
DA_N2_PANEL  
DA_N2_PANEL_T  
DA_N2_BELL_T  
,4  
1
Sint16 is recommended over Float, as Float is memory expensive format  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 9 of 22  
4.3 Client Side Connection Descriptions  
Section Title  
Connections  
Column  
Function  
Title  
Legal Values  
P1-P82  
Specify which port the device is connected to the  
Port  
FieldServer  
Protocol  
Specify protocol used  
nfs2-nca; nca2; nfs2-3030  
CRT Port  
4800; 9600; 19200; 38400; 57600; (Vendor  
limitation)  
Baud*  
Specify baud rate  
Printer Port  
9600 (Vendor limitation)  
None (Vendor limitation)  
8 (Vendor limitation)  
1 (Vendor limitation)  
Parity*  
Data_Bits*  
Stop_Bits*  
Specify parity  
Specify data bits  
Specify stop bits  
Example  
// Client Side Connections  
Connections  
Port ,Protocol ,Baud ,Stop_Bits ,Parity  
P8  
,nfs2-nca ,9600 ,1  
,None  
4.4 Client Side Node Descriptors  
Section Title  
Nodes  
Column Title  
Node_Name  
Function  
Provide name for Node  
Legal Values  
Up to 32 alphanumeric characters  
Station address of any physical Node on 1-240. Set unique Id for standalone Notifer-  
Node_ID  
Protocol  
Port  
network  
3030 Panel  
Specify protocol used  
Specify which port the device is connected  
to the FieldServer  
nfs2-nca or nca2 ; nfs2-3030  
P1-P8  
Example  
// Client Side Nodes  
Nodes  
Node_Name ,Node_ID ,Protocol ,Port  
Panel_1  
,2  
,nfs2-nca ,P8  
2 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: [email protected]  
 
     
FS-8700-130 Notifier NCA2/NFS-3030 Manual  
Page 10 of 22  
4.5 Client Side Map Descriptors  
4.5.1 FieldServer Related Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
Up to 32 alphanumeric characters  
Name of Data Array where data is to be One of the Data Array names from “Data  
Map_Descriptor_Name Name of this Map Descriptor  
Data_Array_Name  
stored in the FieldServer  
Array” section above  
Any integer value  
0 - one less than Data Array length  
Passive  
Data_Array_Offset  
Function  
Starting location in Data Array  
Function of Map Descriptor  
4.5.2 Driver Related Map Descriptor Parameters  
Column Title  
Node_Name  
Function  
Legal Values  
One of the Node names specified in  
“Client Node Descriptor” above  
Detector  
Name of Node to fetch data from  
Module  
Detector_Trouble  
Module_Trouble  
Panel  
Data_Type  
Specify memory area type  
Panel_Trouble  
Bell_Trouble  
Node_Trouble  
As per Data_type  
Detector  
Module  
1-1749  
Detector_Trouble  
Module_Trouble  
1-159 for point troubles  
Panel  
Address  
Starting address of block  
1-1056 for Panel circuits  
Panel_Trouble  
1-96 for Panel troubles  
Bell_Trouble  
1-4 for Bell circuits  
Node_Trouble  
1-509 for Node troubles  
Same as address value  
Length  
Length of Map Descriptor  
Specify whether driver should clear Node(s)  
Clear_on_Reset*  
memory area upon receipt of “SYSTEM RESET” No, Yes  
message from Panel.  
Specify whether driver should clear Node(s)  
Clear_on_Normal* memory area upon receipt of “SYSTEM NORMAL” Yes ,No  
message from Panel.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 11 of 22  
4.5.3 Map Descriptor Example: Standard example  
This shows the standard Map Descriptor setup for one Node with 1 loop and all 159 modules and 159 detectors installed. This Node also has all boards, panel  
and bell circuits  
//  
// Client Side Map Descriptor  
// Define Map Descriptors to capture just required data  
//  
// Node 2  
//  
Map_Descriptors  
Map_Descriptor_Name  
//  
,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Loop ,Data_Type  
,Address ,Length  
// Capture Node Events  
SMD_N2_Troubles  
SMD_N2_PANEL  
SMD_N2_PANEL_T  
SMD_N2_BELL_T  
,DA_SYS_N2  
,0  
,0  
,0  
,0  
,Passive  
,Passive  
,Passive  
,Passive  
,NODE2  
,NODE2  
,NODE2  
,NODE2  
,-  
,-  
,-  
,-  
,Node_Trouble  
,Panel  
,Panel_Trouble  
,Bell_Trouble  
,1  
,1  
,1  
,1  
,508  
,1056  
,96  
,DA_N2_PANEL  
,DA_N2_PANEL_T  
,DA_N2_BELL_T  
,4  
// Capture Loop 1 events  
SMD_N2L01D  
SMD_N2L01D_T  
SMD_N2L01M  
,DA_N2L01D  
,0  
,0  
,0  
,0  
,Passive  
,Passive  
,Passive  
,Passive  
,NODE2  
,NODE2  
,NODE2  
,NODE2  
,1  
,1  
,1  
,1  
,Detector  
,Detector_Trouble ,1  
,Module  
,Module_Trouble  
,1  
,1749  
,159  
,1749  
,159  
,DA_N2L01D_T  
,DA_N2L01M  
,DA_N2L01M_T  
,1  
,1  
SMD_N2L01M_T  
All Map Descriptors are  
Passive; waiting for a message  
from the Notifier panel.  
Identify the Loop id for  
which this Map Descriptor  
will store data  
Specify Data  
Type  
Specify range,  
starting address  
and length  
Select the array  
for data storage  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 12 of 22  
5
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: [email protected]  
 
 
FS-8700-130 Notifier NCA2/NFS-3030 Manual  
Page 13 of 22  
Appendix A. Advanced Topics  
Appendix A.1. Notifier NCA2/NFS2-3030 Message Types Recognized  
Event Keyword  
FIRE ALARM  
Clearing Event  
CLEARED  
ALARM  
Notes  
FIRE  
states: {1,0}  
SECURITY  
ALARM (LIFE)  
CLEARED SECURITY states: {1,0}  
ALARM (LIFE)  
LIFE  
CRITICAL CLEARED  
LIFE states: {1,0}  
ALARM  
CRITICAL ALARM  
MEDICAL  
EMERGENCY  
SECURITY  
ALARM  
CLEARED MEDICAL states: {1,0}  
EMERGENCY  
CLEARED SECURITY states: {1,0}  
ALARM  
CRITICAL  
PROCESS  
states: {1,0}  
CRITICAL PROCESS  
CLEARED  
SUPERVISORY  
CLEARED  
TROUBLE/ FAULT  
CLEARED  
DISABLED  
states: {1,0}  
SUPERVISORY  
TROUBLE/  
FAULT  
States: [counter}  
states: {1,0}  
DISABLED  
CLEARED  
states: {1,0}  
PREALARM  
PREALARM  
CLEARED ACTIVE  
OFF  
ACTIVE  
ON/ OFF  
states: {1,0}  
states: {1,0}  
Resets all addresses in all memory areas but only if data is previously set  
by driver and is not yet cleared by “Cleared” message and is configured  
to Clear_on_Normal. By default Clear_on_Normal is “yes”.  
Resets all addresses in all memory areas for a given Node but only if  
data is previously set by driver and is not yet cleared by “Cleared”  
message and is configured to Clear_on_Reset. By default  
Clear_on_Reset is ‘no’.  
SYSTEM  
NORMAL  
SYSTEM RESET  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 14 of 22  
Appendix A.2. System Trouble Messages  
The following table lists the system troubles theoretically recognized by this driver – only a selection have been  
tested.  
System Trouble  
Address  
1
2
3
4
5
6
7
8
System Trouble  
STYLE 4 SHORT A L6  
STYLE 4 SHORT B L6  
STYLE 4 SHORT A L7  
STYLE 4 SHORT B L7  
STYLE 4 SHORT A L8  
STYLE 4 SHORT B L8  
STYLE 4 SHORT A L9  
STYLE 4 SHORT B L9  
STYLE 4 SHORT A L10  
STYLE 4 SHORT B L10  
GENERAL PS FAULT  
INSTALLATION ERROR OR CPU/AVPS-24 FAULT  
INSTALLATION ERROR OR CPU/AVPS-24 FAULT  
INSTALLATION ERROR OR CPU/AVPS-24 FAULT  
EARTH FAULT DETECTED IN WIRING OR SYSTE  
EARTH FAULT DETECTED IN WIRING OR SYSTE  
EARTH FAULT DETECTED IN WIRING OR SYSTE  
COMM FAULT LOOP INTERFACE BOARD 1  
COMM FAULT LOOP INTERFACE BOARD 2  
COMM FAULT LOOP INTERFACE BOARD 3  
COMM FAULT LOOP INTERFACE BOARD 4  
COMM FAULT LOOP INTERFACE BOARD 5  
COMM FAULT LOOP INTERFACE BOARD 6  
COMM FAULT LOOP INTERFACE BOARD 7  
COMM FAULT LOOP INTERFACE BOARD 8  
COMM FAULT LOOP INTERFACE BOARD 9  
COMM FAULT LOOP INTERFACE BOARD 10  
CATASTROPHIC ISIB COMMUNICATIONS FAULT  
MEMORY PATTERN FAULT. SERVICE REQUIRED  
CATASTROPHIC CPU BOARD COMM FAULT  
Address  
255  
256  
257  
258  
259  
260  
261  
262  
263  
264  
265  
266  
267  
268  
269  
270  
271  
272  
273  
274  
275  
276  
277  
278  
279  
280  
281  
282  
283  
284  
GROUND FAULT LOOP 1  
GROUND FAULT LOOP 2  
GROUND FAULT LOOP 3  
GROUND FAULT LOOP 4  
GROUND FAULT LOOP 5  
GROUND FAULT LOOP 6  
GROUND FAULT LOOP 7  
GROUND FAULT LOOP 8  
GROUND FAULT LOOP 9  
GROUND FAULT LOOP 10  
GROUND FAULT PORT A  
GROUND FAULT PORT B  
GROUND FAULT  
STYLE 6 NEG LOOP 1  
STYLE 6 NEG LOOP 2  
STYLE 6 NEG LOOP 3  
STYLE 6 NEG LOOP 4  
STYLE 6 NEG LOOP 5  
STYLE 6 NEG LOOP 6  
STYLE 6 NEG LOOP 7  
STYLE 6 NEG LOOP 8  
STYLE 6 NEG LOOP 9  
STYLE 6 NEG LOOP 10  
STYLE 6 POS LOOP 1  
STYLE 6 POS LOOP 2  
STYLE 6 POS LOOP 3  
STYLE 6 POS LOOP 4  
STYLE 6 POS LOOP 5  
STYLE 6 POS LOOP 6  
STYLE 6 POS LOOP 7  
STYLE 6 POS LOOP 8  
STYLE 6 POS LOOP 9  
STYLE 6 POS LOOP 10  
STYLE 6 SHORT L1  
STYLE 6 SHORT L2  
STYLE 6 SHORT L3  
STYLE 6 SHORT L4  
STYLE 6 SHORT L5  
STYLE 6 SHORT L6  
STYLE 6 SHORT L7  
STYLE 6 SHORT L8  
STYLE 6 SHORT L9  
STYLE 6 SHORT L10  
STYLE 6 RING 1  
STYLE 6 ON LOOP 1  
STYLE 6 ON LOOP 2  
STYLE 6 ON LOOP 3  
STYLE 6  
ANNUN 1 TROUBLE  
ANNUN 2 TROUBLE  
ANNUN 3 TROUBLE  
ANNUN 4 TROUBLE  
ANNUN 5 TROUBLE  
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
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  
UPLOAD/DOWNLOAD COMMUNICATIONS FAULT 285  
STYLE \6\" WIRING OR LOOP #1 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #1 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #2 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #2 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #3 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #3 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #4 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #4 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #5 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #5 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #6 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #6 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #7 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #7 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #8 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #8 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #9 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #9 ABNORMAL"  
STYLE \6\" WIRING OR LOOP #10 ABNORMAL"  
STYLE \4\" WIRING OR LOOP #10 ABNORMAL"  
UNPROGRAMMED DEVICE ON LOOP 1  
286  
287  
288  
289  
290  
291  
292  
293  
294  
295  
296  
297  
298  
299  
300  
301  
302  
303  
304  
305  
306  
307  
UNPROGRAMMED DEVICE ON LOOP 2  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 15 of 22  
System Trouble  
ANNUN 6 TROUBLE  
ANNUN 7 TROUBLE  
ANNUN 8 TROUBLE  
ANNUN 9 TROUBLE  
ANNUN 10 TROUBLE  
ANNUN 11 TROUBLE  
ANNUN 12 TROUBLE  
ANNUN 13 TROUBLE  
ANNUN 14 TROUBLE  
ANNUN 15 TROUBLE  
ANNUN 16 TROUBLE  
ANNUN 17 TROUBLE  
ANNUN 18 TROUBLE  
ANNUN 19 TROUBLE  
ANNUN 20 TROUBLE  
ANNUN 21 TROUBLE  
ANNUN 22 TROUBLE  
ANNUN 23 TROUBLE  
ANNUN 24 TROUBLE  
ANNUN 25 TROUBLE  
ANNUN 26 TROUBLE  
ANNUN 27 TROUBLE  
ANNUN 28 TROUBLE  
ANNUN 29 TROUBLE  
ANNUN 30 TROUBLE  
ANNUN 31 TROUBLE  
ANNUN 32 TROUBLE  
REMOTE DISPLAY 1 TROUBLE  
REMOTE DISPLAY 2 TROUBLE  
REMOTE DISPLAY 3 TROUBLE  
REMOTE DISPLAY 4 TROUBLE  
REMOTE DISPLAY 5 TROUBLE  
REMOTE DISPLAY 6 TROUBLE  
REMOTE DISPLAY 7 TROUBLE  
REMOTE DISPLAY 8 TROUBLE  
REMOTE DISPLAY 9 TROUBLE  
REMOTE DISPLAY 10 TROUBLE  
REMOTE DISPLAY 11 TROUBLE  
REMOTE DISPLAY 12 TROUBLE  
REMOTE DISPLAY 13 TROUBLE  
REMOTE DISPLAY 14 TROUBLE  
REMOTE DISPLAY 15 TROUBLE  
REMOTE DISPLAY 16 TROUBLE  
REMOTE DISPLAY 17 TROUBLE  
REMOTE DISPLAY 18 TROUBLE  
REMOTE DISPLAY 19 TROUBLE  
REMOTE DISPLAY 20 TROUBLE  
REMOTE DISPLAY 21 TROUBLE  
REMOTE DISPLAY 22 TROUBLE  
REMOTE DISPLAY 23 TROUBLE  
REMOTE DISPLAY 24 TROUBLE  
REMOTE DISPLAY 25 TROUBLE  
REMOTE DISPLAY 26 TROUBLE  
REMOTE DISPLAY 27 TROUBLE  
REMOTE DISPLAY 28 TROUBLE  
REMOTE DISPLAY 29 TROUBLE  
REMOTE DISPLAY 30 TROUBLE  
REMOTE DISPLAY 31 TROUBLE  
REMOTE DISPLAY 32 TROUBLE  
Address  
54  
55  
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  
101  
102  
103  
104  
105  
106  
107  
108  
109  
110  
111  
112  
System Trouble  
Address  
308  
309  
310  
311  
312  
313  
314  
315  
316  
317  
318  
319  
320  
321  
322  
323  
324  
325  
326  
327  
328  
329  
330  
331  
332  
333  
334  
335  
336  
337  
338  
339  
340  
341  
342  
343  
344  
345  
346  
347  
348  
349  
350  
351  
352  
353  
354  
355  
356  
357  
358  
359  
360  
361  
362  
363  
364  
365  
366  
UNPROGRAMMED DEVICE ON LOOP 3  
UNPROGRAMMED DEVICE ON LOOP 4  
UNPROGRAMMED DEVICE ON LOOP 5  
UNPROGRAMMED DEVICE ON LOOP 6  
UNPROGRAMMED DEVICE ON LOOP 7  
UNPROGRAMMED DEVICE ON LOOP 8  
UNPROGRAMMED DEVICE ON LOOP 9  
UNPROGRAMMED DEVICE ON LOOP 10  
IR ENABLED ON LOOP 1  
IR ENABLED ON LOOP 2  
IR ENABLED ON LOOP 3  
IR ENABLED ON LOOP 4  
IR ENABLED ON LOOP 5  
IR ENABLED ON LOOP 6  
IR ENABLED ON LOOP 7  
IR ENABLED ON LOOP 8  
IR ENABLED ON LOOP 9  
IR ENABLED ON LOOP 10  
TX/RX ERROR ABOVE LIMIT ON LOOP 1  
TX/RX ERROR ABOVE LIMIT ON LOOP 2  
TX/RX ERROR ABOVE LIMIT ON LOOP 3  
TX/RX ERROR ABOVE LIMIT ON LOOP 4  
TX/RX ERROR ABOVE LIMIT ON LOOP 5  
TX/RX ERROR ABOVE LIMIT ON LOOP 6  
TX/RX ERROR ABOVE LIMIT ON LOOP 7  
TX/RX ERROR ABOVE LIMIT ON LOOP 8  
TX/RX ERROR ABOVE LIMIT ON LOOP 9  
TX/RX ERROR ABOVE LIMIT ON LOOP 10  
TOO MANY DEVICES ON LOOP 1  
TOO MANY DEVICES ON LOOP 2  
TOO MANY DEVICES ON LOOP 3  
TOO MANY DEVICES ON LOOP 4  
TOO MANY DEVICES ON LOOP 5  
TOO MANY DEVICES ON LOOP 6  
TOO MANY DEVICES ON LOOP 7  
TOO MANY DEVICES ON LOOP 8  
TOO MANY DEVICES ON LOOP 9  
TOO MANY DEVICES ON LOOP 10  
MISMATCHED LOOP TYPE ON LOOP 1  
MISMATCHED LOOP TYPE ON LOOP 2  
MISMATCHED LOOP TYPE ON LOOP 3  
MISMATCHED LOOP TYPE ON LOOP 4  
MISMATCHED LOOP TYPE ON LOOP 5  
MISMATCHED LOOP TYPE ON LOOP 6  
MISMATCHED LOOP TYPE ON LOOP 7  
MISMATCHED LOOP TYPE ON LOOP 8  
MISMATCHED LOOP TYPE ON LOOP 9  
MISMATCHED LOOP TYPE ON LOOP 10  
MAPPING IN PROGRESS LOOP 1  
MAPPING IN PROGRESS LOOP 2  
MAPPING IN PROGRESS LOOP 3  
MAPPING IN PROGRESS LOOP 4  
MAPPING IN PROGRESS LOOP 5  
MAPPING IN PROGRESS LOOP 6  
MAPPING IN PROGRESS LOOP 7  
MAPPING IN PROGRESS LOOP 8  
MAPPING IN PROGRESS LOOP 9  
MAPPING IN PROGRESS LOOP 10  
LIB #1 SCB RECEIVE ERROR  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 16 of 22  
System Trouble  
Address  
System Trouble  
LIB #2 SCB RECEIVE ERROR  
LIB #3 SCB RECEIVE ERROR  
LIB #4 SCB RECEIVE ERROR  
LIB #5 SCB RECEIVE ERROR  
LIB #6 SCB RECEIVE ERROR  
LIB #7 SCB RECEIVE ERROR  
LIB #8 SCB RECEIVE ERROR  
Address  
367  
368  
369  
370  
371  
372  
373  
374  
375  
376  
377  
378  
379  
380  
381  
382  
383  
384  
385  
386  
387  
388  
389  
390  
391  
392  
393  
394  
395  
396  
397  
398  
399  
400  
401  
402  
403  
404  
405  
406  
407  
408  
409  
410  
411  
ANALOG OUTPUT 1 TROUBLE  
ANALOG OUTPUT 2 TROUBLE  
ANALOG OUTPUT 3 TROUBLE  
ANALOG OUTPUT 4 TROUBLE  
AUXILIARY TROUBLE  
UDACT TROUBLE  
AVPS. TROUBLE  
MASTER BOX TROUBLE  
AUXIN TROUBLE  
DIGIN TROUBLE  
FFT TROUBLE  
REMOTE MIC TROUBLE  
LOCAL MIC TROUBLE  
LOCAL PHONE TROUBLE  
POWER SUPPLY TROUBLE  
FIM TROUBLE - FIELD INTERFACE MODULE  
LIM TROUBLE - LOOP INTERFACE MODULE  
NIM TROUBLE - NETWORK INTERFACE MODULE 130  
SYSTEM TROUBLE DEFAULT MESSAGE  
TROUBLE  
ANNUN 1 NO ANSWER  
ANNUN 2 NO ANSWER  
113  
114  
115  
116  
117  
118  
119  
120  
121  
122  
123  
124  
125  
126  
127  
128  
129  
LIB #9 SCB RECEIVE ERROR  
LIB #10 SCB RECEIVE ERROR  
LIB #1 SCB ACKNOWLEDGE ERROR  
LIB #2 SCB ACKNOWLEDGE ERROR  
LIB #4 SCB ACKNOWLEDGE ERROR  
LIB #5 SCB ACKNOWLEDGE ERROR  
LIB #6 SCB ACKNOWLEDGE ERROR  
LIB #7 ACKNOWLEDGE ERROR  
LIB #8 SCB ACKNOWLEDGE ERROR  
LIB #9 SCB ACKNOWLEDGE ERROR  
LIB #10 SCB ACKNOWLEDGE ERROR  
LIB #1 NIB COMMUNICATION ERROR  
LIB #2 NIB COMMUNICATION ERROR  
LIB #3 NIB COMMUNICATION ERROR  
LIB #4 NIB COMMUNICATION ERROR  
LIB #5 NIB COMMUNICATION ERROR  
LIB #6 NIB COMMUNICATION ERROR  
LIB #7 NIB COMMUNICATION ERROR  
LIB #8 NIB COMMUNICATION ERROR  
LIB #9 COMMUNICATION ERROR  
LIB #10 NIB COMMUNICATION ERROR  
LIB #1 NIB M/S PROGRAMMING ERROR  
LIB #2 NIB M/S PROGRAMMING ERROR  
LIB #3 NIB M/S PROGRAMMING ERROR  
LIB #4 NIB M/S PROGRAMMING ERROR  
LIB #5 NIB M/S PROGRAMMING ERROR  
LIB #6 NIB M/S PROGRAMMING ERROR  
LIB #7 NIB M/S PROGRAMMING ERROR  
LIB #8 NIB M/S PROGRAMMING ERROR  
LIB #9 NIB M/S PROGRAMMING ERROR  
LIB #10 NIB M/S PROGRAMMING ERROR  
INTERNAL RAM ERROR  
131  
132  
133  
134  
135  
136  
137  
138  
139  
140  
141  
142  
143  
144  
145  
146  
147  
148  
149  
150  
151  
152  
153  
154  
155  
156  
157  
158  
159  
160  
161  
162  
163  
164  
165  
166  
167  
168  
169  
170  
171  
ANNUN 3 NO ANSWER  
ANNUN 4 NO ANSWER  
ANNUN 5 NO ANSWER  
ANNUN 6 NO ANSWER  
ANNUN 7 NO ANSWER  
ANNUN 8 NO ANSWER  
ANNUN 9 NO ANSWER  
ANNUN 10 NO ANSWER  
ANNUN 11 NO ANSWER  
ANNUN 12 NO ANSWER  
ANNUN 13 NO ANSWER  
ANNUN 14 NO ANSWER  
ANNUN 15 NO ANSWER  
ANNUN 16 NO ANSWER  
ANNUN 17 NO ANSWER  
ANNUN 18 NO ANSWER  
ANNUN 19 NO ANSWER  
ANNUN 20 NO ANSWER  
ANNUN 21 NO ANSWER  
ANNUN 22 NO ANSWER  
ANNUN 23 NO ANSWER  
ANNUN 24 NO ANSWER  
ANNUN 25 NO ANSWER  
ANNUN 26 NO ANSWER  
ANNUN 27 NO ANSWER  
ANNUN 28 NO ANSWER  
ANNUN 29 NO ANSWER  
ANNUN 30 NO ANSWER  
ANNUN 31 NO ANSWER  
ANNUN 32 NO ANSWER  
REMOTE DISPLAY 1 NO ANSWER  
REMOTE DISPLAY 2 NO ANSWER  
REMOTE DISPLAY 3 NO ANSWER  
REMOTE DISPLAY 4 NO ANSWER  
REMOTE DISPLAY 5 NO ANSWER  
REMOTE DISPLAY 6 NO ANSWER  
REMOTE DISPLAY 7 NO ANSWER  
EXTERNAL RAM ERROR  
CPU EXTERNAL RAM TEST ERROR  
CATASTROPHIC CUP NONVOLATILE RAM  
DIB EXTERNAL RAM TEST ERROR  
CATASTROPHIC DIA NONVOLATILE RAM  
EPROM ERROR  
PRINTER SUPERVISORY PATH IS INTERRUPTED  
PRINTER SUPERVISORY  
PRINTER COVER OPEN  
412  
413  
414  
415  
416  
417  
418  
419  
420  
421  
422  
423  
424  
425  
PRINTER PAPER OUT  
PRINTER BUFFER FULL OR OUT OF PAPER  
AUX PRINTER BUFFER FULL OR OUT OF PAPER  
PRINTER OFF LINE  
PRINT QUEUE FULL  
FACP PRINT BUFFER FULL  
CORRUPT LOGIC EQUAT  
PROGRAM CORRUPTED  
DATABASE CORRUPTED  
AUDIO LIBRARY CORRUPTED  
LCD80 SUPERVISORY  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 17 of 22  
System Trouble  
Address  
System Trouble  
TERM SUPERVISORY  
CRT SUPERVISORY  
TERMINAL SUPERVISORY PATH IS INTERRUPTE  
NVRAM BATTERY TROUBLE  
NCM PIEZO BATTERY FAILURE  
BATTERY(S) NOT CONNECTED OR DEFECTIVE  
BATTERY CHARGER DETACHED  
BATTERY  
TM4 DISABLED  
UP/DOWN LOAD IN PROGRESS _ ACS DISABLED  
NO DEV INST ON L1  
ADV WALK TEST  
PROG MODE ACTIVATED  
LOADING..NO SERVICE  
BASIC WALK TEST  
NFPA 24HR REMINDER  
OPTION MODULE  
DRILL ACTIVATED  
MAN EVAC RECEIVED  
MANUAL MODE ENTERED  
POWER SUPPLY CABLE NOT CONNECTED  
NETWORK INCOMPATIBLE  
Address  
426  
427  
REMOTE DISPLAY 8 NO ANSWER  
REMOTE DISPLAY 9 NO ANSWER  
REMOTE DISPLAY 10 NO ANSWER  
REMOTE DISPLAY 11 NO ANSWER  
REMOTE DISPLAY 12 NO ANSWER  
REMOTE DISPLAY 13 NO ANSWER  
REMOTE DISPLAY 14 NO ANSWER  
REMOTE DISPLAY 15 NO ANSWER  
REMOTE DISPLAY 16 NO ANSWER  
REMOTE DISPLAY 17 NO ANSWER  
REMOTE DISPLAY 18 NO ANSWER  
REMOTE DISPLAY 19 NO ANSWER  
REMOTE DISPLAY 20 NO ANSWER  
REMOTE DISPLAY 21 NO ANSWER  
REMOTE DISPLAY 22 NO ANSWER  
REMOTE DISPLAY 23 NO ANSWER  
REMOTE DISPLAY 24 NO ANSWER  
REMOTE DISPLAY 25 NO ANSWER  
REMOTE DISPLAY 26 NO ANSWER  
REMOTE DISPLAY 27 NO ANSWER  
REMOTE DISPLAY 28 NO ANSWER  
REMOTE DISPLAY 29 NO ANSWER  
REMOTE DISPLAY 30 NO ANSWER  
REMOTE DISPLAY 31 NO ANSWER  
REMOTE DISPLAY 32 NO ANSWER  
UDACT NO ANSWER  
172  
173  
174  
175  
176  
177  
178  
179  
180  
181  
182  
183  
184  
185  
186  
187  
188  
189  
190  
191  
192  
193  
194  
195  
196  
197  
198  
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  
428  
429  
430  
431  
432  
433  
434  
435  
436  
437  
438  
439  
440  
441  
442  
443  
444  
445  
446  
447  
448  
449  
450  
451  
452  
453  
454  
455  
456  
457  
458  
459  
460  
461  
462  
463  
464  
465  
466  
467  
468  
469  
470  
471  
472  
473  
474  
475  
476  
477  
478  
479  
480  
481  
482  
483  
484  
SYSTEM INITIALIZATION  
LINK PROTECTOR PRIMARY STATUS  
LINK PROTECTOR SECONDARY STATUS  
LINK PROTECTOR PRIMARY NOT PRESENT  
EVENT BUFFER 80% FULL  
EBI STATUS  
SOFTWARE MISMATCH  
NO POWER SUPPLY INST  
TEST PROGRAM UPDATE  
HISTORY 80% FULL  
FLASH IMAGE ERROR  
AMPLIFIER LIMIT  
AMPLIFIER SUPERVISION  
DAA ADDRESS CONFLICT  
DEVICE SERVICING REQUIRED  
DATABASE INCOMPATIBLE  
AUDIO LIBRARY INCOMPATIBLE  
DAA DOWNLOAD IN PROGRESS  
PHONE CHANNEL LIMIT EXCEEDED  
CPU EXECUTIVE ROUTINE RE-ENTERED  
CPU RECEIVE QUE OVERFLOW  
CPU DATA MESSAGE RECEIVED ERROR  
CPU LEVEL QUE FULL  
CPU CODE MEMORY CHECKSUM ERROR  
CPU MESSAGE TRANSMITTED ERROR  
AVPS-24 PROBLEM  
DATABASE INCOMPLETE PLEASE REDOWNLOAD  
MPS-24 MONITOR CABLE DISCONNECTED  
TYPE ID CHANGED. SERVICE REQUIRED  
TYPE ID CHANGED. SERVICE REQUIRED  
PROG. CHANGE DET. SERVICE REQUIRED  
LIVE TEST - SIGNAL P  
DIB EXECUTIVE ROUTINE RE-ENTERED  
DIB RECEIVE QUE OVERFLOW  
DIB DATA MESSAGE RECEIVED ERROR  
DIB CODE MEMORY CHECKSUM ERROR  
INCOMPATIBLE SOFTWARE OR INVALID CBE  
MASTER BOX NO ANSWER  
DAA NO ANSWER  
NO ANSWER  
NETWORK FAILURE  
WORKSTATION FAN FAILURE  
UPS FAILURE  
NCM COMM FAILURE  
NODE COMMUNICATIONS FAILURE  
POWER SUPPLY COMM FAILURE  
LOOP 1-2 COMM FAILURE  
LOOP 3-4 COMM FAILURE  
LOOP 5-6 COMM FAILURE  
LOOP 7-8 COMM FAILURE  
LOOP 9-10 COMM FAILURE  
DAP PORT A FAILURE  
DAP PORT B FAILURE  
FIM COMM FAILURE  
LIM COMM FAILURE  
NIM COMM FAILURE  
CATASTROPHIC LCD FAILURE ON DIA  
CATASTROPHIC DUART FAILURE ON DIA  
ISIB SCB RECEIVE FAILURE  
COMMUNICATION LINK FAILURE IN PORT A  
COMMUNICATION LINK FAILURE IN PORT B  
LAN COMMUNICATIONS FAILURE  
FAILURE  
NETWORK FAIL PORT A  
NETWORK FAIL PORT B  
CHARGER FAIL  
SELF TEST FAILED  
WORKSTATION COMM FAIL  
LOOP CONTINUITY TEST FAIL LOOP 1  
LOOP CONTINUITY TEST FAIL LOOP 2  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 18 of 22  
System Trouble  
Address  
System Trouble  
WALK TEST - FIRE PROTECTION IS LIMITED  
REMOTE PROG MODE ACCESSED  
Address  
485  
486  
LOOP CONTINUITY TEST FAIL LOOP 3  
LOOP CONTINUITY TEST FAIL LOOP 4  
LOOP CONTINUITY TEST FAIL LOOP 5  
LOOP CONTINUITY TEST FAIL LOOP 6  
LOOP CONTINUITY TEST FAIL LOOP 7  
LOOP CONTINUITY TEST FAIL LOOP 8  
LOOP CONTINUITY TEST FAIL LOOP 9  
LOOP CONTINUITY TEST FAIL LOOP 10  
AMP FAIL  
231  
232  
233  
234  
235  
236  
237  
238  
239  
240  
241  
242  
DIA PROG. CHANGE DET. SERVICE REQUIRED  
ISIB DATA MESSAGE RECEIVED ERROR  
ISIB EXECUTIVE ROUTINE RE-ENTERED  
DIB TO SIB CABLE BAD OR MISSING  
UPLOAD/DOWNLOAD MESSAGE RECEIVED  
GLOBAL DATABASE MISMATCH  
SIB PROG. CHANGE DET. SERVICE REQUIRED  
HS-NCM SNIFFER MODE ACTIVE  
EXCEEDED CONNECTION LIMIT  
NAM CCBE. PROG LOST  
MEMORY LOSS  
DVC COMM LOSS  
A.C. POWER LOSS. BACK UP ACTIVATED  
BUZZER OFF-LINE  
PANEL DOOR OPEN  
OFF NETWORK  
INSTALL. ERROR  
OR AUDIO/TELEPHON  
EXPANDER MODULES  
MANUAL CONTROL  
CAT. COMM. FAULT  
UNKNOWN  
487  
488  
489  
490  
491  
492  
493  
494  
495  
496  
497  
498  
499  
500  
501  
502  
503  
504  
505  
506  
507  
508  
AC FAIL  
SCB ASSEM. COM. VERIFIED FAILED  
8255 PORT CHIP CONTROL WORD CHECK FAILE  
NETWORK COMMUNICATION LINK FAIL PORT A 243  
NETWORK COMMUNICATION LINK FAIL PORT B 244  
STYLE 4 SHORT A L1  
STYLE 4 SHORT B L1  
STYLE 4 SHORT A L2  
STYLE 4 SHORT B L2  
STYLE 4 SHORT A L3  
STYLE 4 SHORT B L3  
STYLE 4 SHORT A L4  
STYLE 4 SHORT B L4  
STYLE 4 SHORT A L5  
STYLE 4 SHORT B L5  
245  
246  
247  
248  
249  
250  
251  
252  
253  
254  
Appendix A.3. Node Status  
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.  
Node status offline/online (1/0) is stored in the 502nd address. It is important to read the Node status  
before reading any information about the Node.  
Node status data integrity itself depends upon system synchronization.  
Appendix A.4. FieldServer Synchronization  
There is currently no method of auto-synchronizing the FieldServer's Data Arrays with the Notifier NCA2/NFS2-  
3030 panel because there is no method for polling the panel through the printer or CRT port. Synchronization of  
the two devices can be achieved manually pressing the “System Reset” button on the panel while the FieldServer is  
connected and running. All current events will be re-sent to the FieldServer..  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 19 of 22  
Appendix A.5. Driver Limitations and Exclusions  
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  
All data related to non-event driven reports will not be recorded by the FieldServer  
This driver was written as a subset of NFS2-3030/NCA-2 EIA-232 Protocol & Data Formats 53219 Rev A  
1/3/2008. Any changes or additions by Notifier will not be reflected in this driver unless specifically  
revised.  
This driver will not record information about zone status that is incorporated with point status messages.  
There can only be one panel connected to any given FieldServer port.  
This driver records data as presented to the printer/CRT port by the Notifier panel, and can only be as  
accurate as this data.  
The driver cannot send messages to the Notifier panel.  
Driver will clear any data on “System Normal” only if this data is previously set by driver and is not yet  
cleared by “Cleared” message and is configured to Clear_on_Normal. By default Clear_on_Normal is  
“yes”.  
Driver will clear any Node data on “System RESET” only if this data is previously set by driver and is not yet  
cleared by “Cleared” message and is configured to Clear_on_Reset. By default Clear_on_Reset is “no”.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 20 of 22  
Appendix B. Troubleshooting tips  
Appendix B.1. Connection Tips & Hints  
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.  
If connecting the Panel to one of the FieldServer RS-232 ports causes the FieldServer to reboot, then an  
Optical Isolator is required to balance ground potential problems.  
Appendix B.2. Networking Tips  
By default FieldServer does not take any action on receiving a “SYSTEM RESET”. Normally when a Node  
initiates “SYSTEM RESET” by pressing the “RESET” button on the Panel, the panel sends an individual  
“CLEAR” message for every point, it clears in its memory area. The FieldServer therefore waits for the  
“CLEAR” message to clear a specific bit in its memory for a particular Node or for the “SYSTEM NORMAL”  
message to clear all bits in its memory for every Node. Use Clear_on_Reset parameter if required.  
It may be advisable to configure the Notifier panel to suppress less important “Supervisory” or “Trouble”  
messages which could prevent the generation of “SYSTEM NORMAL” messages. Consult Notifier for this  
configuration or recommendation.  
Ensure that every Node is working with a printer or HyperTerminal, before calling FieldServer for Support.  
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-130 Notifier NCA2/NFS-3030 Manual  
Page 21 of 22  
Appendix C. Error Messages  
Most error messages are associated with errors in parsing an incoming message from the Notifier panel. The most  
likely cause is a mismatch in expected message format. The driver will flag one of the following error messages  
and continue. In most cases the message currently being processed by the driver will also be printed so that any  
problems can be easily diagnosed.  
Two screens ‘System Errors’ and ‘Driver Messages’ exist for displaying errors.  
The System Error Screen displays the error number and the Driver messages screen displays the error number,  
description and the message received from the NCA/NCA2 Panel.  
In debug mode the System Error screen will also include Driver messages.  
The following Error Messages appear upon the ‘System Errors’ Screen  
%d means numeric number  
%s means string  
Messages number 1, 3, 4 and 5 will be displayed just once if generated after rebooting or power cycling the  
FieldServer.  
Error  
Description  
Action  
#1 FYI. Incoming data is  
being abandoned on The FieldServer got  
a
recognized  
Port<%d> Node<%u> message on this particular port, Node, To capture this data, add a new Map  
Loop<%d>  
Data_Type<%s>  
Address<%d>  
loop, Address_Type and Address but Descriptor with the required parameters.  
did not find a defined Map Descriptor.  
This driver keeps track of all non-zero  
memory locations per Map Descriptor. If the error occurs during installation or  
When the track queue is full, the oldest testing, it can be ignored. If the error  
offset is overwritten with the latest occurs during field operation, configure the  
one. This could be a problem on Map Descriptor with required address  
System_Reset and System_Normal ranges only and keep the Map Descriptor  
where memory locations get cleared as length smaller than the queue length.  
per this queue.  
#2 Err. Reset/Normal  
queue<%d> full on  
MD<%s>  
The  
FieldServer  
received  
an If the error occurs continuously, check that  
#3 FYI. Event<%s> not  
Supported.  
unrecognized event or corrupted connection parameters match with panel  
message.  
port settings.  
The FieldServer received  
Trouble event not listed under need this new trouble status, contact  
Appendix A.2 or a corrupted message.  
The FieldServer received a message  
a
Node If this error occurs continuously and you  
#4 Err. Unknown Node  
Trouble <%s>  
FieldServer.  
that  
a
Node either connected or  
#5 Err. Unknown OFF  
NETWORK Node <%s>  
disconnected from the network, but no Call Tech support.  
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: [email protected]  
 
 
FS-8700-130 Notifier NCA2/NFS-3030 Manual  
Page 22 of 22  
Error  
Description  
Action  
A
message was received from an  
#6 Err. Unsupported  
unsupported device or the address of  
the device is not in the correct  
format/location.  
Point  
Address  
Call Tech support.  
Format<%s>  
This occurs due to poor synchronization  
between the FieldServer and the Notifier  
panel or because a problem existed before  
#7 FYI. Attempt to The driver attempted to decrement the connection.3. It will rectify itself upon  
decrement below zero trouble counting number to a number “System Normal” message. Check the  
offset<%d> DA<%s>  
less than 0.  
configuration file to identify the address  
and memory area type mapped to this  
offset and the Data Array which is causing  
the error.  
3 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. Data from the FieldServer should not be considered reliable until the “System Normal”  
message has been returned.  
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]  
 
 

Euro Pro Vacuum Cleaner XSC410 User Manual
Freecom Technologies DVD Recorder DVD RW Recorder User Manual
Frymaster Fryer SR42G User Manual
FujiFilm Digital Camera S9600 User Manual
GE Convection Oven JT930 User Manual
GE Cordless Telephone 25922 Series User Manual
GE DVD Player DV 354 User Manual
GE Intercom System 25423 User Manual
Golden Technologies Mobility Aid Companion II User Manual
Goodman Mfg Furnace ACVC9 AMVC95 User Manual