FS-8700-25 - Notifier INA
Up one levelFieldServer Driver - Serial
FS-8700-25
Notifier INA
Description
Due to the nature of the Notifier drivers and the adaptability of the FieldServer configuration of the Notifier side of the FieldServer is quite simple. The Notifier driver will always function as a Server, thus the primary purpose is for the Notifier Fire Alarm Panel to write information to the FieldServer to be passed on to another device. When the FieldServer is used with the Notifier INA additional Data Arrays need to be configured for each Panel connected to the INA.. The operator must configure the Data Arrays with Node ID’s with addresses of station 1,2, er=tc. Following is an example that is in the default Notifier.
The driver is capable of parsing and storing zone alarm and trouble states. They are latched and cleared when a Network System Reset is received.
The Status Bits is the data string coming from Notifier to set or clear any one of 8209 bits of information in the following order:
|
Parameter |
Bits |
|
Detector Alarms |
0 – 1023 |
|
Detector Alarms Unacknowledged |
1024 – 2047 |
|
Module Alarms |
2048 – 3071 |
|
Module Alarms Unacknowledged |
3071 – 4095 |
|
Detector Trouble |
4096 – 5119 |
|
Detector Trouble Unacknowledged |
5120 – 6143 |
|
Module Trouble |
6144 – 7167 |
|
Module Trouble Unacknowledged |
7168 – 8191 |
|
Common Bits |
8192 – 8207 |
|
Control Bits |
8208 - 8209 |
|
Reserved for future use. |
8210 - 8299 |
|
Zone Alarms |
8220 – 8499 |
|
Zone Troubles |
8500 - 8699 |
|
‘Level’ Alarms |
8800-9099 |
|
‘Level’ Troubles |
9100-9399 |
The Control Bits are as follows:
|
Parameter |
Bit |
|
Ack/Step |
8208 |
|
System Reset |
8209 |
The TAC-Americas heartbeat bit:
|
Parameter |
Bit |
|
TAC-Americas Heartbeat |
8210 |
The Common Bits are as follows:
|
Parameter |
Bit |
|
Detector Alarms |
8192 |
|
Detector Alarms Unacknowledged |
8193 |
|
Module Alarms |
8194 |
|
Module Alarms Unacknowledged |
8195 |
|
Detector Trouble |
8196 |
|
Detector Trouble Unacknowledged |
8197 |
|
Module Trouble |
8198 |
|
Module Trouble Unacknowledged |
8199 |
|
Alarms |
8200 |
|
Alarms Unacknowledged |
8201 |
|
Trouble |
8202 |
|
Trouble Unacknowledged |
8203 |
|
Supervise Sent |
8204 |
|
Ignored Message |
8205 |
|
All Systems Normal |
8206 |
|
ESC X NUL |
8207 |
Text_Regs - This is the text string coming from Notifier that matches the information on the display of the 1010 or 2020 and contains two sets 400 16-bit registers which is equivalent to 10 lines by 80 characters for each set.
Supervise – This is a 2-character string from Notifier providing a “supervise” signal to the Notifier Fire Alarm Panel when hot standby is alive. It also appears to the Client as 2 single coil if it is being sent.
When the customer receives a FieldServer with the Notifier driver installed, the Data Array is already configured and ready to use with the 1010 or 2020. The customer only needs to configure the Server side of the FieldServer, the interface to the non-Notifier device. As an example, if the user were connecting to a device using Modbus RTU communications protocol, they would configure the interface as if the FieldServer were another Modbus PLC. They would have to configure the Modbus device to identify where to find the necessary Notifier information. Thus, they would find the alarm for loop 1 detector 5 in the Status_Bits Data Array at address number 105
Level Status – ‘Level’ Alarms are only set when ‘ALARM’ messages are received. ‘ACTIVE’ messages are treated as troubles for the purpose of ‘Level’ status.
Should you use the Notifier INA driver or the Notifier NFA/1010/2020 Driver ?
Use the INA driver if your FieldServer is connected to an INA device and in turn, the Notifier field panels are connected to the INA which serves as a gateway. One INA panel can be connected to each FieldServer port.
Use the NFA(/1010/2020) driver if your Fieldserver is connected to NFA/1010/2020 Panel directly. One panel can be connected to each FieldServer port.
Revision History
|
Date |
Driver Version |
Document Revision |
Resp
|
Comment |
|
12/21/02 |
1.05a |
1 |
MF |
Updated formatting |
|
7/23/03 |
1.05a |
1 |
JD |
Releasing |
