IPES IR3 Flame Detector
Operating Manual
Page 14 of 37
Analog Signal
Self-Test-Every 35 minutes
Informational digital signals are standard RS‐485 communication with Modbus:
● Hardware self‐test Fault
● Optical interference Fault
● Fire detected
(The digital channel protocol Modbus RTU is described in Appendix B.)
Relay dry contact signal:
• Operation of the normally open Fire relay dry contacts*
o FIRE relay – two‐directional single‐pole contact, which allows the state to be changed at the output to normally
closed or normally open. Relay state is set at the factory. Default setting is Normally Open (Closes when in Fire
Alarm mode). The contact relay is rated for currents ranging from 10 mA to 5 A at DC voltage of 30 V.
The output signal “Fire” can be cleared after eliminating the source of the alarm signal.
* A normally closed condition of the Fire relay contacts does not comply with the requirements of NFPA 72 or
ULC/ORD – C386 and is not approved by FM approvals.
• Operation of the normally open Fault relay dry contacts
o FAULT relay – single‐direction pole contact which is normally open. The relay is designed to handle currents of
10 mA to 5 A at DC voltage of 30 V.
Refer to Table 5‐1: Determining LED Conditions above.
Possible detector configurations using ESP Commander
The IPES–IR3 has the following detector operating modes:
• “Near/far” and “slow/fast” modes – To provide maximum sensitivity.
• “Latching/non‐latching mode”– To select either latching or non‐latching functionality of the fire relay, which
provides latching alarm state for the fire‐alarm relay in compliance with NFPA 72 and ULC/ORD – C386.
The manufacturer’s default settings correspond to far and fast. To change the manufacturer’s settings, connect the
flame detector to the computer and use the ESP Commander program.
HART Protocol
Communication
The HART communication is used to monitor status of the flame detectors and provides the flexibility to make
configuration changes in the field. The important status monitored are the process value (value to determine fault, or
alarm conditions). In addition, the user can test the built-in test, which occurs automatically every 35 mins. For more
details, HART menu tree and connection diagram, please refer to the Appendix C.