FieldServer IR-148 ユーザーズマニュアル
FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual
Page 6 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
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).
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.
to communicate with a Honeywell Zellweger IR-148 Server having one or eight sensors.
4.1.
Data Arrays/Descriptors
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 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.
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 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.
default.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Data_Array_Name
Provide name for Data Array
Up to 15 alphanumeric
characters
characters
Data_Array_Format
Provide data format. Each Data
Array can only take on one format.
Array can only take on one format.
Float, Bit, UInt16, SInt16,
Packed_Bit,
Packed_Bit,
Byte,
Packed_Byte,
Swapped_Byte
Swapped_Byte
Data_Array_Length
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.
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
1-10,000
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
Data_Format,
Data_Array_Length
DA_R1,
Float,
100
DA_R2,
Float,
100
DA_CTL_R1,
Uint16,
1
DA_CTL_R2,
Uint16,
1