manualshive.com logo in svg

FieldServer NCA2-NFS2-3030, Instruction Manual

Share
Download
FieldServer NCA2-NFS2-3030 Instruction Manual Download Page 10

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

 

 

 

 

 

Page 10 of 22 

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] 

4.5

 

Client Side  Map Descriptors 

4.5.1

 

FieldServer Related  Map Descriptor Parameters 

Column Title 

Function 

Legal Values 

Map_Descriptor_Name  Name of this Map Descriptor 

Up to 32 alphanumeric characters 

Data_Array_Name 

Name of Data Array  where data is to be 
stored in the FieldServer 

One of the Data Array names from “Data 
Array” section above 

Data_Array_Offset 

Starting location in Data Array 

Any integer value 
0 - one less than Data Array length 

Function 

Function of Map Descriptor 

Passive 

4.5.2

 

Driver Related Map Descriptor Parameters 

Column Title 

Function 

Legal Values 

Node_Name 

Name of Node to fetch data from 

One of the Node  names specified in 
“Client Node Descriptor” above 

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

Length 

Length of Map Descriptor 

Same as address value 

Clear_on_Reset* 

Specify whether driver should clear Node(s) 
memory area upon receipt of “SYSTEM RESET” 
message from Panel.  

No

, Yes 

Clear_on_Normal* 

Specify whether driver should clear Node(s) 
memory area upon receipt of “SYSTEM NORMAL” 
message from Panel.  

Yes

 ,No 

Summary of Contents for NCA2-NFS2-3030

Page 1: ...ITY EFFECTIVITY Effective for all systems manufactured after January 2009 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 130 Notifier NCA2 NFS2 3030 Driver Version 1 02 Document Revision 1 ...

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

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: ...ing 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 O...

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

Page 9: ...its 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 4 4 Client Side Node Descriptors 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 netwo...

Page 10: ...riptor Passive 4 5 2 Driver Related Map Descriptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from One of the Node names specified in Client Node Descriptor above 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...

Page 11: ...fset Function Node_Name Loop Data_Type Address Length Capture Node Events SMD_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 Capture Loop 1 events SMD_N2L01D DA_N2L01D 0 Passive NODE2 1 Detector 1 1749 SMD_N2L01D...

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

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

Page 14: ...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 15: ...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 16: ...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 17: ...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 18: ...L PORT B 244 DVC COMM LOSS 498 STYLE 4 SHORT A L1 245 A 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 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 SHOR...

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

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

Page 21: ... d Node u Loop d Data_Type s Address d The FieldServer got a recognized message on this particular port Node loop Address_Type and Address but did not find a defined Map Descriptor To capture this data add a new Map Descriptor with the required parameters 2 Err Reset Normal queue d full on MD s This driver keeps track of all non zero memory locations per Map Descriptor When the track queue is full...

Page 22: ...n 0 This occurs due to poor synchronization between the FieldServer and the Notifier panel or because a problem existed before connection 3 It will rectify itself upon System Normal message Check the 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 rebo...

Reviews:

No comments

Brands by name

Popular brands

Load more brands