Filter
Top Products
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual Page 10 of 19
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldServer.com
5. Configuring the FieldServer as a Honeywell Zellweger IR-148 Server
For a detailed discussion on FieldServer configuration, please 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).
This section documents and describes the parameters necessary for configuring the FieldServer
to report sensor data to Honeywell Zellweger IR-148 Client. As a Server this driver sends Gas
value, Alarm, Trouble and Lock point messages. The driver can be locked to send data for only
one particular sensor.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Honeywell Zellweger IR-148 communications, the driver
independent FieldServer buffers need to be declared in the “Data Arrays” section, the
FieldServer virtual node(s) needs to be declared in the “Server Side Nodes” section, and the
data to be provided to the Clients needs to be mapped in the “Server Side 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.
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Port
Specify which port the device is
connected to the FieldServer
P1-P8 (with 232/485
converter), R1-R2
2
Protocol
Specify protocol used InfraTox or Infra-Tox
Baud* Specify baud rate
110 – 115200, standard
baud rates only
9600
Parity* Specify parity
Even, Odd, None, Mark,
Space
Data_Bits*
Specify data bits
7, 8
Stop_Bits*
Specify stop bits
1
Handshaking* Specify hardware handshaking
RTS, RTS/CTS, None
Example
// Server Side Connections
Connections
Port, Protocol, Baud, Parity, Data_Bits
R1, InfraTox, 19200, None, 8
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.