A great solution to the Notifier INA Communications Protocol driver allows the FieldServer to transfer data to and from Notifier INA device over RS-232 (with converter) serial ports using the Notifier INA protocol and provide that data on other protocol Networks like BACnet, Modbus, Lonworks, SNMP, Metasys N2 and others.
When the FieldServer is used with the Notifier INA additional Data Arrays need to be configured for each Panel connected to the INA
Due to the nature of the Notifier drivers and the adaptability of the FieldServer, configuration of
The Notifier side of the FieldServer is straight forward. The Notifier driver will always function as a
Client driver, thus the primary purpose is for the Notifier Fire Alarm Panel to write information to
The FieldServer to be passed on to another device.
|
DOWNLOADDATASHEET
|
Question/Purchase
FieldServer Hardware platforms supporting Notifier INA protocol
|
Device type
|
RS 485/232 ports
|
Lonworks Ports
|
Available Ethernet ports
|
Base Point count capacity
|
Extended Point count capacity
|
|
quick Server
|
2
|
0
|
1
|
250
|
1000
|
|
Quick Server Lonworks
|
1
|
1
|
1
|
250
|
1000
|
|
Enhanced quick Server
|
2
|
0
|
1
|
500
|
1000
|
|
Enhanced quick Server Lonworks
|
1
|
1
|
1
|
500
|
1000
|
How to configure the FieldServer Gateway?
We will configure the Gateway for you based on your requirement and support you during commissioning of the Gateway, so you do not have to worry about configuring the FieldServer Gateway. However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals with be provided completely free of cost with your purchase. Configuration of the FieldServer is done using a '.csv' file. This file can be edited using any text editor (example Microsoft excel).
In this file we need to enter information for the Client and Server side interfaces of the FieldServer. This includes but is not limited to:
o Node ids of the slave devices
o MSTP addresses/device address of the slave devices
o Baud rate, parity, stop bits for serial communication
o Scan rates
And finally we need to create an internal mapping that would map each data value read on the client side to a data value on the server side. For detailed information on configuration please get in touch with us and review the configuration manual on top of this page.