A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-102 Honeywell Zellweger IR-148
Manual
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version:
1.01
Document Revision: 9
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 3 of 19
1.
Honeywell Zellweger IR-148 Description
The Honeywell Infrared Gas Monitor (Model IR-148) detects solvents and gases such as
HCFCs, HFCs and PFCs. IR-148 can have 1, 4 or 8 sampling points. This InfraTox driver
reports gas values, alarms and troubles from IR-148 having either 1 or 8 sampling points.
The serial driver can emulate a client or a server. The FieldServer and IR-148 device are
connected using a RS-485 network.
As a Client: The driver listens passively for messages from the Honeywell Zellweger IR-148
t
and stores data extracted from the messages. The driver cannot poll the IR-148 device for
data. The driver records some additional data age information (which is stored in the
FieldServer’s Data Arrays) because messages do not always contain information about all
sensors and depending on the IR-148 operational mode (e.g. Locked mode.), may never
contain information other than for one sensor.
As a Server: The Server side of this driver has been developed primarily to test the Client side
driver as part of FieldServer’s QA program. The driver sends messages reporting the state of
the samples. The Server driver can also be locked to report the status/value of one particular
sample channel.
It is possible to connect two Honeywell Zellweger units (IR-148) on one RS-485 network
provided that one unit is configured as a single point unit (IR-148 1 point) and the other as an 8
point unit (IR-148 8 point). At this stage only one device with 8 points has been tested.
To allow for the possibility that the device is connected on a RS-485 network with other devices
(such as the relay module option) messages that are not 49 bytes long and which do not begin
with 0xB1 will be ignored. The Driver will, however, provide statistics for the ignored as well as
the processed messages.
To see supported messages and the way the Driver stores Data, refer to Appendix A.2
Max Nodes Supported
FieldServer Mode
Client
Server
Nodes
2
2
Comments
Tested only 1 node (IR-148 8 Point) per port
Developed to test Client side of the Driver.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 4 of 19
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
Description
FS-8917-16
FS-8700-102
RJ45 to terminal connector cable.
Driver Manual.
2.2.
Provided by the Supplier of 3rd Party Equipment
Required 3rd Party Hardware
2.2.1.
Part #
Description
NONE
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 5 of 19
3.
Hardware Connections
The FieldServer is connected to the Honeywell Zellweger IR-148 Device as shown in
connection drawing.
Configure the device according to manufacturer’s instructions
OR
FS-X40
INFRATOX UNIT
+
-
G
OTHER DEVICES
Serial
ORANGE/WHITE
BROWN
FS-X20
INFRATOX UNIT
FS-8917-16
+
-
G
BLUE/WHITE
(408)-262-2299
Honeywell Zellweger
IR-148 Device FieldServer
Connection Diagram
BASE NAME:
FILE NAME: VisioDocument
DATE: 03/07/07
BY: MC
*Other devices must not transmit Honeywell Zellweger IR-148 49 byte messages
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 6 of 19
4.
Configuring the FieldServer as a Honeywell Zellweger IR-148 Client
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 communicate with a Honeywell Zellweger IR-148 Server having one or eight sensors.
4.1.
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
Data Arrays/Descriptors
communications, the driver independent FieldServer buffers need to be declared in the
“Data Arrays” section, the destination device addresses need to be declared in the “Client
Side Nodes” section, and the data required from the Servers needs to be mapped in the
“Client 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.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Float, Bit, UInt16, SInt16,
Provide data format. Each Data Packed_Bit,
Byte,
Data_Array_Format
Array can only take on one format.
Packed_Byte,
Swapped_Byte
Number of Data Objects. Must be
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
Data_Array_Length
1-10,000
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
DA_R1,
DA_R2,
DA_CTL_R1,
DA_CTL_R2,
Data_Format,
Float,
Float,
Uint16,
Uint16,
Data_Array_Length
100
100
1
1
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 7 of 19
4.2.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Function
Legal Values
Specify which port the device is P1-P8 (with 232/485 converter), R1-
Port
connected to the FieldServer
Specify protocol used
Specify baud rate
Specify parity
Specify data bits
R21
Protocol
Baud*
Parity*
Data_Bits*
Stop_Bits*
Handshaking*
InfraTox or Infra-Tox
19200 (Vendor limitation)
None (Vendor limitation)
8 (Vendor limitation)
1
Specify stop bits
Specify hardware handshaking
None (Vendor limitation)
Example
// Client Side Connections
Connections
Port,
R1,
Protocol,
InfraTox,
Baud,
19200, None,
Parity,
Stop_Bits
1
4.3.
Section Title
Nodes
Client Side Node Descriptors
Column Title
Function
Legal Values
Node_Name
Provide name for node
Up to 32 alphanumeric characters
Irrelevant for this driver as long
as only one Node is connected.
Otherwise the Node-ID should be
the number of points/sensors for
Node_ID
which the Zellweger unit is 0-255
configured. A unique Node_ID is
recommended for each Zellweger
Unit as it may be useful in
exposing Node status information
Protocol
Port
Specify protocol used
InfraTox, Infra-Tox.
Specify at which port the device is
connected to the FieldServer
Ports P1-P8 can be with 232/485
converter.
P1-P8 (with 232/485 converter),
R1-R21
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 8 of 19
Example
// Client Side Nodes
Nodes
Node_Name,
DEV1,
Node_ID,
1,
Protocol,
InfraTox,
Port
R1
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Name of this Map Up to 32 alphanumeric
Map_Descriptor_Name
Data_Array_Name
Descriptor
Name of Data Array
where data is to be
stored
FieldServer
characters
One of the Data Array
names from “Data Array”
section above
in
the
Starting location in Data 0 to maximum specified in
Data_Array_Offset
Function
Array
“Data Array” section above
Function of Client Map
Descriptor.
Passive_Client
4.4.2.
Driver Related Map Descriptor Parameters
Column Title
Function
Legal Values
One of the node names
specified in “Client Node
Descriptor” above
Name of Node to fetch
data from
Node_Name
0-Maximum of Data Array
length.
Length
Length of Map Descriptor
Expand Storage per point
Refer to 0.
‘YES’ every thing else
considered as ‘NO’
Extended_Storage*
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 10 of 19
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
Specify which port the device is P1-P8
connected to the FieldServer
Specify protocol used
(with
232/485
Port
converter), R1-R22
InfraTox or Infra-Tox
Protocol
110 – 115200, standard
baud rates only
9600
Even, Odd, None, Mark,
Space
Baud*
Specify baud rate
Specify parity
Parity*
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,
R1,
Protocol,
InfraTox,
Baud,
19200,
Parity,
None,
Data_Bits
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.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 11 of 19
5.2.
Server Side Node Descriptors
Section Title
Nodes
Column Title
Node_Name
Function
Legal Values
Up to 32 alphanumeric
characters
Provide name for node
Commonly used parameter but
irrelevant for this driver as
Protocol is node-less.
A unique Node_ID is, however,
Node_ID
recommended
for
each 1-255
Honeywell Zellweger IR-148
Unit as it may be useful in
exposing
Node
status
information
Protocol
Port
Specify protocol used
Specify at which port the device
is connected to the FieldServer P1-P8
Ports P1-P8 can be used with converter), R1-R2
232/485 converter.
InfraTox, Infra-Tox.
(with
232/485
Example
// Server Side Nodes
Nodes
Node_Name,
DEVR1,
Node_ID,
1,
Protocol,
InfraTox,
Port
R1
5.3.
5.3.1.
Server Side Map Descriptors
FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
of this
Name
Descriptor
Map Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where One of the Data Array
data is to be stored in the names from “Data Array”
Data_Array_Name
FieldServer
section above
Starting location in Data 0 to maximum specified in
Data_Array_Offset
Function
Array
“Data Array” section above
Wrbc
Function of Server Map
Descriptor
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 12 of 19
5.3.2.
Driver Specific Map Descriptor Parameters
Column Title
Function
Legal Values
One of the node names
specified in “Server Node
Descriptor” - section 5.2
1-Maximum of Data Array
length.
Name of Node to which data
has to be sent.
Node_Name
Length
Length of Map Descriptor
Name of Data Array used to
lock the sensor. Driver will
report data for the locked
sensor only.
One of the Data Array
names from “Data Array”
section above
Da_Byte_Array_Name*
Specifies
Da_Byte_Array_Name
Data array. This memory
offset
for
location will be checked every
time if the user has locked a
sensor.
1-Maximum of Data Array
length.
Data_Byte_Offset*
If this parameter is not
specified, the driver will use the
Data_Array_Offset value.
For quality assurance this
parameter is used to send a
message to a Client from a
Map_Descriptor_Name*.ini file.
With the use of this function
Data_Array_Offset value will be
used as line number from INI to
send.
INFRA_SIMULATION:
only
numbered line will be sent to
Client by the Map Descriptor.
INFRA_SIMULATION_ALL:
Starting at the numbered line all
lines will be sent one by one to
the Client until the end of the
file is reached.
INFRA_SIMULATION
INFRA_SIMULATION_ALL
INFRA_SIM_ALL_REPEAT
Infra_Func
INFRA_SIM_ALL_REPEAT:
Repeatedly
Starting
from
numbered line to end of the file
all lines will be sent to Client
one by one by this single Map
Descriptor.
Note: Ini must show all bytes as
two
character
hex
representation and first line of
should be
// FILE_IN_HEX_FORMAT
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 15 of 19
Appendix A. Advanced Topics
Appendix A.1. Supported Functions at a glance
Message Types
Gas Value Message
Trouble Message
Notes
Message reports a gas value and units.
Message reports a trouble for one sensor
Message used to flash Honeywell Zellweger
IR-148 display
Message reports an alarm (C/W/A) for one
sensor
Blank Message
Alarm Message
Locked Point Message
Unit is locked onto a single sample.
Other 49 byte messages beginning 0xb1
Other 49 byte messages
Other messages
Discarded but driver report stats on these
messages see 0.
Appendix A.2. How Data is stored by the Driver.
The Driver can be configured to store data in one of two ways:
a) Default: One Set of consecutive Data Array elements is used for each Honeywell
Zellweger IR-148-8.8-Channel Unit. One set per point/sensor.
Offset Sensor Contents
Description
Alarm
Trouble
or Set non-zero if alarm or a trouble has been reported. Set to
0
1
zero if neither are currently being reported.
0 = None
1 = Caution
2 = Warning
1
1
Alarm Type
3 = Alarm
0 = None
1 = Trouble
2
3
1
1
Trouble
Gas value multiplied by 100 is stored here. When stored, if
configured, scaling will be applied.
Gas Value
4
5
6
1
1
1
Gas Units
Gas Units
Gas Units
1st 3 bytes of gas units are written here as ASCII characters.
0 = Enabled
1 = Disabled
7
8
9
1
1
1
State
Gas
Valid
Gas
Age
Value 1 = Gas Value updated with most recent message.
0 = Gas Value not updated.
Value In seconds since last update.
Initial (and max) value = 0xffff
Time since last message containing data about this sensor.
In seconds since last update.
Initial (and max) value = 0xffff
Sensor Data
Age
10
1
11..21
22..32
33..43
44..54
55..65
66..76
77..87
2
3
4
5
6
7
8
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 16 of 19
b) Extended storage : If the FieldServer is configured to use extended storage then data
will be stored as below
Offset
Sensor Contents
Description
Non-zero if alarm or a trouble has been reported.
Zero if neither are currently being reported.
0 = None, 1 = Caution, 2 = Warning, 3 = Alarm
0=None, 1=Trouble
0
1
Alarm or Trouble
1
2
1
1
Alarm Type
Trouble
Gas value multiplied by 100 is stored here. When
stored, if configured, scaling will be applied.
3
1
Gas Value
4
5
6
7
1
1
1
1
Gas Units
Gas Units
Gas Units
State
1st 3 bytes of gas units are written here as ASCII
characters.
0 = Enabled, 1 = Disabled
1 = Gas Value updated with most recent message.
0 = Gas Value not updated.
In seconds since last update.
8
1
1
1
1
Gas Value Valid
Gas Value Age
Sensor Data Age
I/O State
9
Initial (and max) value = 0xffff
Age since last message, containing data from this
sensor in seconds. Initial (and max) value = 0xffff
255 = unknown, 0=Warm up, 1 = Ready, 2 = Trouble,
3= Cal/Setup
10
11
Alarm
Status
Audion On Status
Alarm Latching
Preference
Latched
12
13
14
1
1
1
0=No, 1=Yes
0=No, 1= Yes
On Caution (0=No, 1= Yes)
Alarm
Preference
Alarm
Preference
Audio
Preference
Audio
Preference
Audio
Preference
Audio
Preference
Audio
Preference
Spare
Latching
15
16
17
18
19
20
21
1
1
1
1
1
1
1
On Warning(0=No, 1= Yes)
On Alarm(0=No, 1= Yes)
On Caution (0=No, 1= Yes)
On Warning(0=No, 1= Yes)
On Alarm(0=No, 1= Yes)
On Trouble(0=No, 1= Yes)
On Auxilary(0=No, 1= Yes)
Latching
On
On
On
On
On
22-24
1
2
3
4
5
6
7
25..49
50.-74
75.- 99
100-124
125..149
150.-174
175.-
8
199
The Driver expects similar a Data array format to send data to the Client when acting as a
Server.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Appendix A.3. Driver stats
Page 17 of 19
In addition to the standard FieldServer operating statistics the driver can expose certain key
stats in a Data Array which can then be monitored by an upstream device. Adding the
following to the configuration file will activate these stats for a driver configured as a Client.
// Expose Driver Operating Stats.
Data_Arrays
Data_Array_Name,
Infra-stats,
Data_Format,
UINT32,
Data_Array_Length
200
Stat
Stats
#
Description
0
1
2
3
INFRA_TROUBLE_MSG_RECV
Number of trouble messages received
Number of Alarm as well as Trouble
messages reported
Number of Alarm messages reported
Number of Gas Value messages
reported
INFRA_TROUBLE_WITH_ALARM_MSG_RECV
INFRA_ALARM_MSG_RECV
INFRA_GAS_VALUE_MSG_RECV
Number of Gas value as well as Alarm
messages reported.
4
INFRA_GAS_VALUE_WITH_ALARM_MSG_RECV
5
6
INFRA_LOCK_MSG_RECV
INFRA_BLANK_MSG_RECV
Number of Lock messages reported
Number of Blank messages reported
Number of discarded messages
starting with 0xB1 with length 49 bytes
Number of discarded messages not
starting with 0xB1 with length 49 bytes
Number of discarded messages with
length not 49 bytes.
Length of the latest discarded
message with length not 49 bytes.
Number of messages discarded
because of bad checksum.
10
11
12
13
20
INFRA_ST_0xB1_49_RECV_DISC
INFRA_BAD_ST_49_RECV_DISC
INFRA_NOT_49_RECV_DISC
INFRA_NOT_49_RECV_BYTES_DISC
INFRA_BAD_CRC_MSG_DISC
For the node connected at R1; Offset = Stat number
Example: The number of messages discarded because of bad start can be found at Offset 11
in Infra-Stats Data Array.
For the node connected at R2; Offset = 100 + Stat number
Example: The number of messages discarded because of bad start can be found at Offset
111 in Infra-Stats Data Array.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Appendix B. Driver Error Messages
Page 18 of 19
Some configuration errors might produce an error every time a poll is generated. This will fill the
error buffer quickly and not add any clarity. For this reason the driver suppresses subsequent
similar messages. Thus it is possible for the same error produced by multiple Map Descriptors
to produce only one error message. Subsequent error messages can be seen on the driver
message screen.
Note : In the actual message you will see that %d has been replaced by an integer, %s by text
indicating a data array name or map descriptor name and %x by two hex characters.
Error Message
INFRA: #1 Err. Da <%s>
length Reqd/exist <%d/%d>
Md <%s> where md offset
<%d>ψ
Description and Action Required
This error will be generated when the driver tries to store data for a
sensor but the corresponding Data Array is not long enough. Set the
Data Array length as indicated..
Honeywell Zellweger IR-148-8.8-Channel or another unit is connected
at the indicated port of the FieldServer but the Configuration file does
not define a Map Descriptor to capture data from this unit. Change the
CSV file to define a Map Descriptor to communicate with this device if
required.
INFRA:#2 Err. Incoming data
is being abandoned on port R-
P%d ψ
INFRA:#3
Node_id %d, Valid 1-8
ERR.
Invalid If there are multiple nodes then make the Node_ID the number of
points (sensors) for which Zellweger units are configured.
In Simulation mode the driver can send messages from files indicated
by the Map Descriptor name. Check that the required file exists and
that it is not in use by another application, or change the mode from
simulation to operation by deleting the parameter
“INFRA_SIMULATION” from .the CSV file.
Infra:#4 Err. Test file <%s> not
found.
INFRA:#11 Err. Illegal MD
Function for Md <%s>ψ
INFRA:#12 Err. Illegal MD
length <%s>ψ
Set Map Descriptor’s function to Passive_Client if driver is configured
as a Client or wrbc if configured as a Server.
The Map Descriptor length parameter is either not defined or set to 0.
Set the Map Descriptor length to 100.
INFRA:#13
Err.
Illegal
This error will be generated if you are using the Infra_func parameter
with an incorrect value. See section 0 for legal values.
This error will be generated when the driver tries to send a message to
the Client, but the Data Array used to compose the message is
insufficiently long to hold information for all 8 sensors. Set the Data
Array length as indicated.
Infra_func for Md <%s>ψ
INFRA:#21 Err. Da <%s>
length Reqd/exist <%d/%d>
Md <%s> where md offset
<%d>ψ
In Server mode the driver does not send messages from lines starting
with # or //. Change the Data_Array_Offset parameter for the indicated
line in the ini file.
INFRA:#22 Err. Diagnostic line
<%d> ignored.ψ
If an Upstream Device writes a value at a memory location under the
influence of the given Map Descriptor, the Write-thru operation will be
cancelled as the Driver cannot write to an UnfraTox unit..
INFRA:#41 FYI. Write-thru not
Possible On MD <%s>
Infra:#51 FYI. You could use
an Array called <%s> to
expose diagnostic info.
It is possible to define a Data Array known as “Infra-stats” (see 0) This
Data Array is very useful for statistics purposes.
ψ Edit CSV file, download the modified file and reset the FieldServer to have the changes take effect.
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 19 of 19
THIS PAGE INTENTIONALLY LEFT BLANK
|