background image

 

FS-8700-130 Notifier NCA2-NFS2-3030 Manual 

Page 4 of 23 

 

NOTIFIER NCA2/NFS2-3030 DESCRIPTION  

1

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 

This Driver cannot be used as a Client. 

Server 

Each FieldServer port can connect to only 1 Notifier panel port 

 
 

 

DRIVER SCOPE OF SUPPLY 

2

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 

Summary of Contents for FieldServer FS-8700-130

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

Page 2: ...k 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 1...

Page 3: ...r 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...

Page 4: ...cy 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 th...

Page 5: ...s 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 REF PTX PRX RE...

Page 6: ...dware 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 Pa...

Page 7: ...ta 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 Numb...

Page 8: ...ng 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...

Page 9: ...s 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...

Page 10: ...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 S...

Page 11: ...ce is connected to the FieldServer P1 P8 Node_Inactivity_Timeout Used to monitor the connection to the panel for inactivity Should there be no response from the panel for the set number of seconds the...

Page 12: ...m One of the Node names specified in Section 5 3 Data_Type Specify memory area type Detector Module Detector_Trouble Module_Trouble Panel Panel_Trouble Bell_Trouble Node_Trouble Address Starting addre...

Page 13: ...NODE2 Panel 1 1056 SMD_N2_PANEL_T DA_N2_PANEL_T 0 Passive NODE2 Panel_Trouble 1 96 SMD_N2_BELL_T DA_N2_BELL_T 0 Passive NODE2 Bell_Trouble 1 4 SMD_N2L01D DA_N2L01D 0 Passive NODE2 1 Detector 1 1749 S...

Page 14: ...FS 8700 130 Notifier NCA2 NFS2 3030 Manual Page 14 of 23 CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2 NFS2 3030 6 SERVER This driver cannot be configured as a Server...

Page 15: ...hronize 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...

Page 16: ...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 it...

Page 17: ...states 1 0 SUPERVISORY CLEARED SUPERVISORY states 1 0 TROUBLE FAULT CLEARED TROUBLE FAULT States counter DISABLED CLEARED DISABLED states 1 0 PREALARM CLEARED PREALARM states 1 0 ACTIVE CLEARED ACTIVE...

Page 18: ...OARD 7 278 STYLE 6 POS LOOP 2 25 COMM FAULT LOOP INTERFACE BOARD 8 279 STYLE 6 POS LOOP 3 26 COMM FAULT LOOP INTERFACE BOARD 9 280 STYLE 6 POS LOOP 4 27 COMM FAULT LOOP INTERFACE BOARD 10 281 STYLE 6...

Page 19: ...MANY DEVICES ON LOOP 3 338 REMOTE DISPLAY 5 TROUBLE 85 TOO MANY DEVICES ON LOOP 4 339 REMOTE DISPLAY 6 TROUBLE 86 TOO MANY DEVICES ON LOOP 5 340 REMOTE DISPLAY 7 TROUBLE 87 TOO MANY DEVICES ON LOOP 6...

Page 20: ...ATION ERROR 394 ANNUN 9 NO ANSWER 141 LIB 1 NIB M S PROGRAMMING ERROR 395 ANNUN 10 NO ANSWER 142 LIB 2 NIB M S PROGRAMMING ERROR 396 ANNUN 11 NO ANSWER 143 LIB 3 NIB M S PROGRAMMING ERROR 397 ANNUN 12...

Page 21: ...CTOR PRIMARY NOT PRESENT 451 MASTER BOX NO ANSWER 198 EVENT BUFFER 80 FULL 452 DAA NO ANSWER 199 EBI STATUS 453 NO ANSWER 200 SOFTWARE MISMATCH 454 NETWORK FAILURE 201 NO POWER SUPPLY INST 455 WORKSTA...

Page 22: ...C POWER LOSS BACK UP ACTIVATED 499 STYLE 4 SHORT B L1 246 BUZZER OFF LINE 500 STYLE 4 SHORT A L2 247 PANEL DOOR OPEN 501 STYLE 4 SHORT B L2 248 OFF NETWORK 502 STYLE 4 SHORT A L3 249 INSTALL ERROR 503...

Page 23: ...2 or a corrupted message If this error occurs continuously and you need this new trouble status contact FieldServer 5 Err Unknown OFF NETWORK Node s The FieldServer received a message that a Node eit...

Reviews: