Driver Manual FS-8700-95 Notifier NFS-3030 APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after March 2021. Driver Revision: 1.05 Document Revision: 3.A Notifier Onyx Driver Manual 0 MSAsafety.
MSA Safety 1991 Tarob Court Milpitas, CA 95035 Website: www.MSAsafety.com U.S. Support Information: +1 408 964-4443 +1 800 727-4377 Email: smc-support@msasafety.com EMEA Support Information: +31 33 808 0590 Email: smc-support.emea@msasafety.
Contents 1 Description ........................................................................................................................................ 4 2 Driver Scope of Supply .................................................................................................................... 4 2.1 Supplied by MSA Safety ........................................................................................................... 4 3 Hardware Connections .........................................
Description 1 Description The NFS-3030 Serial driver allows the FieldServer to record data from Notifier Onyx Series NFS-3030 Fire Panels over RS-232. The FieldServer acts as a Passive Client receiving messages and recording the status of a Notifier-3030 Fire Alarm Panel. There is no active polling by this driver; the communications are one-way through the panel's printer port.
Installing the FieldServer 3 3.1 Hardware Connections Notifier Onyx NFS-640 Panel The FieldServer is connected to the Notifier NFS-3030 Fire Panel as shown in the connection drawings below. Configure the Notifier NFS-3030 Fire Panel according to manufacturer’s instructions. 3.2 Connecting the Notifier-3030 Panel to a FieldServer Notifier Mother Board Terminal Block 5 ONYX SERIES NFS-3030 Tx Rx REF TB5 PC/CRT PORT Rx Tx GND FieldServer Use PTX, PRX, and REF to connect to the QuickServer. 3.
Configuring the FieldServer 4 Configuring the FieldServer as a (Notifier NFS-3030) Client For detailed information on FieldServer configuration, 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).
Configuring the FieldServer 4.2 Calculating Array Offset for a Panel Each Notifier 3030 Loop has a separate Data Array. There can be up to 10 loops per panel, and the status of the detectors and modules on any particular loop is recorded in the appropriate section of the Data Array according to the device address. e.g. For a detector L02D054 in PREALARM, the address would be 1054 in the Data Array for loop 2.
Configuring the FieldServer 4.4 Client Side Connection Descriptors Section Title Connections Column Title Port Protocol Baud* Parity* Data_Bits* Stop_Bits* Supervision_Mode*2 Function Specify which port the device is connected to the FieldServer. Specify protocol used. Specify baud rate. Specify parity. Specify data bits. Specify stop bits. The driver is able to process port supervision queries sent by the panel. Refer to Section 5.1 for more information.
Configuring the FieldServer Client Side Map Descriptors 4.6 4.6.1 FieldServer Related Map Descriptor Parameters Column Title Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function 4.6.2 Function Name of this Map Descriptor. Name of Data Array where data is to be stored in the FieldServer. Starting location in Data Array. Function of Client Map Descriptor. Driver Related Map Descriptor Parameters Column Title Node_Name Function Name of Node to fetch data from.
Additional Information 5 5.1 Useful Features FieldServer Synchronization To synchronize the FieldServer's Data Arrays with the Notifier NFS-3030 fire panel, the fire panel must be in the SYSTEM NORMAL state, and then the FieldServer can be restarted. There is no method of autosynchronizing the two devices because there is currently no method for polling data from the NFS-3030 panel through the printer port.
Additional Information 5.2.1 Port Supervision in Hot Standby A strategy that can be employed is the following. The Primary FieldServer is set to Mode=1 and always responds to Port supervision Requests. The Secondary FieldServer is normally set to Mode=3 and will not respond to Port Supervision request but is capable of transition. If the primary fails, the secondary becomes active but does not respond which causes a trouble at the panel.
Additional Information 6 Troubleshooting Connection Tips & Hints 6.1 • Trouble connecting to the Notifier printer port may occur if the port has not been enabled. By default, this port is disabled. Please check the Notifier Manuals on how to enable this port and ensure that it is set to 80 columns no supervision unless port supervision is enabled in the driver configuration.
Additional Information 6.3 Error Messages Most error messages are associated with errors parsing an incoming message from the NFS-3030. 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 problems can be easily diagnosed. Message NFS3030:#1 Err. Incoming data is being abandoned on port %d.
Additional Information Message NFS3030:#17 Err. No polling allowed. Presumed write thru abandoned! NFS3030:#18 Err. Internal Diagnostic. Call Tech Support. 6.4 Explanation Polling is not supported by this driver. The write is not performed and the Map Descriptor is returned producing a Protocol Error. To avoid the problem, reconfigure the upstream driver so that it does not write data into the Data Arrays associated with this Driver’s Map Descriptors. The driver performed a poll.
Additional Information Statistic Description NFS_STAT_SLAVE_BYTES_RCVD NFS_STAT_SLAVE_MSGS_RCVD NFS_STAT_SLAVE_BYTES_REJECTED_BY_COMPLETE NFS_STAT_SLAVE_OCCURRENCES_REJECTED_BY_COMPLETE NFS_STAT_SLAVE_BYTES_REJECTED_BY_PARSE_KEYWORD NFS_STAT_SLAVE_OCCURRENCES_REJECTED_BY_PARSE_KEY WORD NFS_STAT_SLAVE_ADDRESS_PARSE_FAILURE NFS_STAT_SLAVE_PARSE_KEYWORD_FOUND_BUT_NOT_ HANDLED.
Additional Information 7 Reference 7.1 Message to Data Array Mapping This driver was designed to be connected to the Notifier Onyx NFS-3030 printer port and listen for incoming messages. The panel's default setting for the printer port is off. To utilize this driver, the printer must be enabled on the unit and set to 80 columns with NO supervision unless port supervision is enabled in the driver configuration. Refer to Section 5.1 for more information on port supervision.
Additional Information 7.1.2 System Trouble Messages A detailed mapping of message interaction System Trouble messages provided by Notifier at the time this driver was written is tabulated below. Any changes or additions by Notifier will not be reflected in this driver unless specifically revised. Because of the patterns of the messages, the search string has been truncated to permit message recognition with device address.
