background image

FS-8700-130 Notifier NCA2/NFS-3030 Manual 

 

 

 

 

 

Page 13 of 21 

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] 

Appendix A.

 

Useful Information 

Appendix A.1.

 

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

 

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

Appendix A.3.

 

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

 

Summary of Contents for FS-8700-130

Page 1: ...cument Revision 3 A Sierra Monitor Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after March 2010 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 130 Notifier NCA2 NFS2 3030 ...

Page 2: ... Mapping 7 5 2 Client Side Connection Parameters 9 5 3 Client Side Node Parameters 9 5 4 Client Side Map Descriptor Parameters 10 5 4 1 FieldServer Related Map Descriptor Parameters 10 5 4 2 Driver Related Map Descriptor Parameters 10 5 4 3 Map Descriptor Example Standard example 11 6 Configuring the FieldServer as a Notifier NCA2 NFS2 3030 Server 12 Appendix A Useful Information 13 Appendix A 1 N...

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

Page 4: ...n 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 REF PTX PRX REF TB5 Printer CRT Rx Brown Tx Orange White Com Blue White 1 8 Connector Pinouts TB5 CRT Function Receive Reference Transmi...

Page 5: ...l 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com 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 ...

Page 6: ...ion 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 be...

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

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

Page 9: ...ts 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 5 3 Client Side Node Parameters Section Title Nodes Column Title Function Legal Values Node_Name Provide name for Node Up to 32 alphanumeric characters Node_ID Station address of any physical Node on network...

Page 10: ...iptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from 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 address of block As per Data_type Detector Module 1 1749 Detector_Trouble Module_Trouble 1 159 for point troubles...

Page 11: ..._N2_Troubles DA_SYS_N2 0 Passive NODE2 Node_Trouble 1 508 SMD_N2_PANEL DA_N2_PANEL 0 Passive 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 SMD_N2L01D_T DA_N2L01D_T 0 Passive NODE2 1 Detector_Trouble 1 159 SMD_N2L01M DA_N2L01M 0 Passive NODE2 1 Modu...

Page 12: ...logies 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 6 CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2 NFS2 3030 SERVER This driver cannot be configured as a Server ...

Page 13: ...Appendix A 3 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 ...

Page 14: ...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 fo...

Page 15: ...ates 1 0 SECURITY ALARM CLEARED SECURITY ALARM states 1 0 CRITICAL PROCESS CRITICAL PROCESS 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 states 1 0 ON OFF OFF states 1 0 SYSTEM NORMAL Resets all addresses in all memory areas but only if data is...

Page 16: ...D 5 276 STYLE 6 NEG LOOP 10 23 COMM FAULT LOOP INTERFACE BOARD 6 277 STYLE 6 POS LOOP 1 24 COMM FAULT LOOP INTERFACE BOARD 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 POS LOOP 5 28 CATASTROPHIC ISIB COMMUNICATIONS FAULT 282 STYLE 6 POS LOOP 6 29 MEM...

Page 17: ...BOVE LIMIT ON LOOP 10 335 REMOTE DISPLAY 2 TROUBLE 82 TOO MANY DEVICES ON LOOP 1 336 REMOTE DISPLAY 3 TROUBLE 83 TOO MANY DEVICES ON LOOP 2 337 REMOTE DISPLAY 4 TROUBLE 84 TOO 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 341 REMOTE DISPLAY 8 TRO...

Page 18: ...NNUN 6 NO ANSWER 138 LIB 8 NIB COMMUNICATION ERROR 392 ANNUN 7 NO ANSWER 139 LIB 9 COMMUNICATION ERROR 393 ANNUN 8 NO ANSWER 140 LIB 10 NIB COMMUNICATION 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 NO ANSWER 144 LIB 4 NIB M S PROGRAMMING ERROR 398 A...

Page 19: ...R SECONDARY STATUS 450 UDACT NO ANSWER 197 LINK PROTECTOR 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 WORKSTATION FAN FAILURE 202 TEST PROGRAM UPDATE 456 UPS FAILURE 203 HISTORY 80 FULL 457 NCM COMM FAILURE 204 FLASH IMAGE ERROR 458 NODE COMMUNICATIONS FAI...

Page 20: ...R OPEN 501 STYLE 4 SHORT B L2 248 OFF NETWORK 502 STYLE 4 SHORT A L3 249 INSTALL ERROR 503 STYLE 4 SHORT B L3 250 OR AUDIO TELEPHON 504 STYLE 4 SHORT A L4 251 EXPANDER MODULES 505 STYLE 4 SHORT B L4 252 MANUAL CONTROL 506 STYLE 4 SHORT A L5 253 CAT COMM FAULT 507 STYLE 4 SHORT B L5 254 UNKNOWN 508 Appendix C 3 Error Messages Most error messages are associated with errors in parsing an incoming mes...

Page 21: ... and you need this new trouble status contact FieldServer 5 Err Unknown OFF NETWORK Node s The FieldServer received a message that a Node either connected or disconnected from the network but no Node number was received it is likely that the message was corrupted Call Tech support 6 Err Unsupported Point Address Format s A message was received from an unsupported device or the address of the devic...

Reviews: