FieldServer Honeywell Zellweger IR-148 Driver Manual Download Page 16

FS-8700-102 Honeywell Zellweger IR-148-8_8-Channel Manual 

 

 

Page 16 of 17

 

FieldServer Technologies

 1991 Tarob Court Milpitas, California 95035 USA   

Web

: www.fieldserver.com 

Tel

: (408) 262 2299   

Fax

: (408) 262 2269   

Toll Free

: (888) 509 1970   

email

[email protected] 

Appendix B.

 

Reference 

Appendix B.1.

 

Supported Functions at a glance  

Message Types 

Notes 

Gas Value Message 

Message reports a gas value and units. 

Trouble Message 

Message reports a trouble for one sensor 

Blank Message 

Message used to flash Honeywell Zellweger IR-148 display 

Alarm Message 

Message reports an alarm (C/W/A) for one sensor 

Locked Point Message 

Unit is locked onto a single sample. 

Other 49 byte messages beginning 0xb1 

Discarded but driver report stats on these messages as described 
in Appendix B.3. 

Other 49 byte messages 
Other messages 

Appendix B.2.

 

Driver Error Messages  

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 

Description and Action Required 

INFRA: #1 Err. Da <%s> length 
Reqd/exist <%d/%d> Md <%s> 
where md offset <%d>

 

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.. 

INFRA:#2 Err. Incoming data is 
being abandoned on port R-P%d 

 

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:#3 ERR. Invalid Node_id 
%d, Valid 1-8 

If there are multiple Nodes then make the Node_ID the number of points 
(sensors) for which Zellweger units are configured. 

Infra:#4 Err. Test file <%s> not 
found. 

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:#11 Err. Illegal MD 
Function for Md <%s>

 

Set Map Descriptor’s function to Passive_Client if driver is configured as a 
Client or Wrbc if configured as a Server. 

INFRA:#12 Err. Illegal MD length 
<%s>

 

The Map Descriptor length parameter is either not defined or set to 0.  Set 
the Map Descriptor length to 100. 

INFRA:#13 Err. Illegal Infra_func 
for Md <%s>

 

This error will be generated if you are using the Infra_func parameter with 
an incorrect value.  See section 0 for legal values.  

INFRA:#21 Err. Da <%s> length 
Reqd/exist <%d/%d> Md <%s> 
where md offset <%d>

 

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:#22 Err. Diagnostic line 
<%d> ignored.

 

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. 

                                                      

 Edit CSV file, download the modified file and reset the FieldServer to have the changes take effect. 

Summary of Contents for Honeywell Zellweger IR-148

Page 1: ...ent Revision 3 A Sierra Monitor Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after September 2009 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 102 Honeywell Zellweger IR 148 ...

Page 2: ... 3 1 FieldServer Related Map Descriptor Parameters 7 5 3 2 Driver Related Map Descriptor Parameters 7 5 3 3 Map Descriptor Example 8 6 Configuring the FieldServer as a Honeywell Zellweger IR 148 Server 9 6 1 Server Side Connection Descriptors 9 6 2 Server Side Node Descriptors 10 6 3 Server Side Map Descriptors 11 6 3 1 FieldServer Specific Map Descriptor Parameters 11 6 3 2 Driver Specific Map De...

Page 3: ...en 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 up to three Honeywell Zellweger units IR 148 on one RS 485 network provided that one unit is configured as a single point unit...

Page 4: ...ccording to manufacturer s instructions FS 8917 16 FS X40 OR FS X30 GND GND FG R1 R2 Connect to R1 or R2 Port G OTHER DEVICES INFRATOX UNIT G OTHER DEVICES INFRATOX UNIT ORANGE WHITE BROWN BLUE WHITE FS X20 Serial 3 1 CONNECTION NOTES Other devices must not transmit Honeywell Zellweger IR 148 49 byte messages If connecting to the X 20 the serial port must be configured for RS 485 connection It is ...

Page 5: ...litate correct storage of the relevant data Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format Float Bit UInt16 SInt16 Packed_Bit Byte Packed_Byte Swapped_Byte Data_Array_Length Number of Data Objects Must be larger than the data s...

Page 6: ...lweger 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 par...

Page 7: ...Ports P1 P8 require a 232 485 converter P1 P8 2 R1 R2 Example Client Side Nodes Nodes Node_Name Node_ID Protocol Port DEV1 1 InfraTox R1 5 3 CLIENT SIDE MAP DESCRIPTORS 5 3 1 FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Data_Array_Name Name of Data Array where data is to be stored i...

Page 8: ...ame Data_Array_Name Data_Array_Offset Function Node_Name Length CMD1 DA_R1 0 Passive Client DEV1 100 One of the Data Arrays declared in Section 4 The Data from the Node Dev1 will be stored in this Data Array The Driver stores Data from device DEV1 with this memory location as the starting point and onward in Data Array DA_R1 This means that the FieldServer cannot poll the target device but monitor...

Page 9: ...ting 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...

Page 10: ...ers Node_ID Irrelevant for this driver when only one Node is connected Otherwise the Node ID should be the number of points sensors for which the Zellweger unit is configured A unique Node_ID is recommended for each Zellweger Unit as it may be useful in exposing Node status information 0 255 Protocol Specify protocol used InfraTox Infra Tox Port Specify at which port the device is connected to the...

Page 11: ... Descriptor 1 to maximum specified in Section 4 Da_Byte_Array_Name Name of Data Array used to lock the sensor The driver will report data for the locked sensor only One of the Data Array names specified in Section 4 Data_Byte_Offset Specifies offset into the Da_Byte_Array_Name Data Array This memory location will be checked when the user has locked a sensor 0 to Data_Array_Length 1 Data_Array_Offs...

Page 12: ...Data Array DA_CTL_R1 the driver will only send data for that particular sensor To disable the lock insert an invalid 0 or 8 number Server Side Map Descriptors Map Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Length Da_Byte_Name Da_Byte_Oset SMD1 DA_R1 0 Wrbc DEV1 100 DA_CTL_R1 0 Driver will look into this data array to send Zellweger message to Zellweger 8 C...

Page 13: ...e Node DEV1 irrespective of the contents The line may contain up to 2000 characters Server Side Map Descriptors Map Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Length Infra_Func SMD1 ini Dummy 2 wrbc DEV1 1 INFRA_SIMULATION Data Array Offset indicates the line number to send to Node DEV1 Wrbc function makes this Server an Active Server This Server continuou...

Page 14: ...t updated 9 1 Gas Value Age In seconds since last update Initial and max value 0xffff 10 1 Sensor Data Age Time since last message containing data about this sensor In seconds since last update Initial and max value 0xffff 11 21 2 22 32 3 33 43 4 44 54 5 55 65 6 66 76 7 77 87 8 Appendix A 1 2 Extended storage Offset Sensor Contents Description 0 1 Alarm or Trouble Non zero if alarm or a trouble ha...

Page 15: ... 0 No 1 Yes 13 1 Audio On Status 0 No 1 Yes 14 1 Alarm Latching Preference On Caution 0 No 1 Yes 15 1 Alarm Latching Preference On Warning 0 No 1 Yes 16 1 Alarm Latching Preference On Alarm 0 No 1 Yes 17 1 Audio On Preference On Caution 0 No 1 Yes 18 1 Audio On Preference On Warning 0 No 1 Yes 19 1 Audio On Preference On Alarm 0 No 1 Yes 20 1 Audio On Preference On Trouble 0 No 1 Yes 21 1 Audio On...

Page 16: ...ming data is being abandoned on port R P d 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 3 ERR Invalid Node_id d Valid 1 8 If there are multiple Node...

Page 17: ..._Length Infra stats UINT32 200 Stat Stats Description 0 INFRA_TROUBLE_MSG_RECV Number of trouble messages received 1 INFRA_TROUBLE_WITH_ALARM_MSG_RECV Number of Alarm as well as Trouble messages reported 2 INFRA_ALARM_MSG_RECV Number of Alarm messages reported 3 INFRA_GAS_VALUE_MSG_RECV Number of Gas Value messages reported 4 INFRA_GAS_VALUE_WITH_ALARM_MSG_RECV Number of Gas value as well as Alarm...

Reviews: