A flame detector that keeps dropping into fault is more than a nuisance. Every fault means that zone is partly or fully blind to a hydrocarbon fire, and every repeated fault teaches operators to ignore the alarm panel.
If your flame detector fault keeps coming back after you clear it, something is wrong that a reset will not fix.
This guide walks through the nine most common causes of recurring flame detector faults, how to tell them apart, and a step-by-step diagnostic sequence you can follow in the field.
It applies to UV, IR, UV/IR and multi-spectrum IR (IR3) detectors, with notes where the technologies differ.
Safety first
Flame detectors are usually part of a safety instrumented function. Before you touch one, follow your site’s permit-to-work, bypass/override, and management-of-change procedures, and tell the control room. Always confirm details against the manufacturer’s manual for your exact model.
Why Does a Flame Detector Keep Going Into Fault?
The most common reasons a flame detector repeatedly faults are
- Dirty, wet, or damaged optical window (optical integrity fault)
- Low supply voltage or voltage drop on long cable runs
- Wiring faults: loose terminals, corrosion, open or shorted loop
- Water or condensation inside the housing or conduit
- Electromagnetic interference (EMI/RFI) or poor grounding
- High ambient temperature or direct sunlight exposure
- Ageing sensor (especially UV tubes) or failed internal electronics
- Wrong configuration or incompatible controller input settings
- Faults in the controller or input card, not the detector at all
The rest of this article shows you how to confirm which one you have.
Fault vs. Alarm vs. Warning: Know What You Are Chasing
Before troubleshooting, be clear about what the detector is actually telling you.
| Condition | What it means | Typical 4-20 mA behavior* | Typical response |
|---|---|---|---|
| Normal / healthy | Detector operating, no flame | ~4 mA | None |
| Flame alarm | Flame signature detected | ~16-20 mA (model dependent) | Execute fire response |
| Warning / maintenance | Degradation, e.g. dirty window | Specific mA level or relay | Schedule cleaning/inspection |
| Fault | Detector cannot guarantee detection | Often 0 mA or <2 mA | Troubleshoot, treat zone as unprotected |
*Current levels are manufacturer-specific. Some detectors also use HART, Modbus, or relay outputs for fault. Always check your model’s output table.
A key point
on many detectors, a loss of signal at the controller (open loop, 0 mA) looks identical to a detector-reported fault.
That is why you need to find out whether the detector, the wiring, or the controller is the true source.
Cause 1: Dirty, Wet, or Damaged Optical Window
This is the number one cause of recurring faults. Most modern flame detectors run an automatic optical integrity (oi) test.
They send a reference signal through the window to the sensor, and if the signal drops below a threshold, the detector raises an oi fault.
Common contaminants
- Oil mist, grease, and process residue
- Dust, salt spray, and sand
- Paint overspray or sealant residue
- Condensation, rain film, and ice
- Scratched or crazed sapphire/glass from abrasive cleaning
How to confirm
Check the diagnostic output or LED code for an oi-type fault. Inspect the window visually with a torch.
If the fault clears after cleaning and returns days later, contamination is building quickly and you have a location or maintenance interval problem.
Fix
Clean with the manufacturer-approved method, typically a soft lint-free cloth and a suitable cleaner such as isopropyl alcohol or glass cleaner.
Avoid abrasive pads, which scratch the window and make the problem permanent. If the environment is dirty, consider an air shroud, a different mounting position, or a shorter cleaning interval.
Cause 2: Low Supply Voltage and Voltage Drop
Flame detectors, especially those with window heaters and oi circuits, draw significant current. If the voltage at the detector falls below its minimum, usually shown in the datasheet, it will fault or reset intermittently.
Typical culprits
- Undersized cable over long distances
- Power supply near its capacity limit
- Degraded batteries or a failing UPS
- High resistance connections that add voltage drop only when current rises (heater on in cold weather)
How to confirm
Measure the voltage at the detector terminals, not at the supply, while the detector is powered and operating. Compare it to the minimum operating voltage in the manual.
Take a second reading when the heater is active if the unit has one. Intermittent faults that correlate with cold mornings or rain often point here.
Fix
Increase cable size, shorten the run, add a local power supply, or repair high-resistance joints.
Cause 3: Wiring Faults and Loose Terminations
Wiring problems cause a large share of “mystery” faults, especially in plants with vibration, heat cycling, and corrosive atmospheres.
Look for:
- Loose or back-out terminals
- Corroded conductors or green copper at the gland
- Damaged insulation, pinched cable at the bracket
- Open circuit or short in the 4-20 mA loop
- Incorrect polarity after maintenance
- Unterminated or incorrectly terminated shields
How to confirm
With the loop isolated and safe, perform a continuity and insulation resistance test per your site standard.
Wiggle-test the cable at accessible points while watching the controller. Check the junction box, not only the detector.
Fix
Re-terminate, replace damaged cable sections, and use proper ferrules and gland sealing. Where corrosion is severe, replace the whole run rather than patching it.
Cause 4: Water Ingress and Condensation
An enclosure that was sealed at commissioning may not be sealed now. Damaged O-rings, over-tightened or cross-threaded covers, missing gland seals, and unsealed conduits all let moisture in.
Temperature cycling then pumps humid air into the housing (the “breathing” effect), and the water condenses on cold electronics.
Symptoms include faults after rain or washdown, faults in the early morning, and corrosion on the board or terminals.
How to confirm
Open the unit (only when permitted and de-energized as required) and inspect for moisture, rust, white residue, or a dirty O-ring. Check conduit for water at the low points.
Fix
Replace O-rings and glands, dry the enclosure, fit conduit seals at the correct locations, and use drain/breather devices that suit the certification of the detector. Water-damaged boards are rarely reliable afterwards and are usually better replaced.
Cause 5: EMI/RFI and Grounding Problems
Variable frequency drives, radios, welding equipment, and high-voltage cables can induce noise in signal wiring.
Poor grounding can create ground loops and ground faults, which cause erratic readings or spurious faults.
Clues that it is electrical noise
- Faults that appear only when a certain motor, VFD, or radio is active
- Random, short-lived faults that clear on their own
- Faults that vary when you touch or move cables
How to confirm
Compare the fault log timestamps with plant activity. Check shield grounding at one end only (typically the controller or safe area end), unless the manufacturer specifies otherwise. Measure for stray voltage on the shield.
Fix
Separate signal cables from power cables, use shielded twisted pair, ground shields correctly, and install the detector away from major noise sources where possible.
Cause 6: Temperature Extremes and Solar Radiation
Detectors have rated operating temperature ranges. In hot climates, a detector on a sun-exposed bracket can exceed its internal limit even when ambient air is within spec. In cold climates, window icing and a failed heater cause oi faults.
How to confirm
Compare the fault time to the time of day and weather. Measure the housing temperature in the afternoon sun. Check that the window heater is working if fitted.
Fix
Install a sunshade (if approved for the model), reposition the detector, or choose a detector rated for the temperature extremes.
Cause 7: Ageing Sensors and Failed Electronics
Flame detector sensors do not last forever.
UV detectors
The UV tube degrades with age and exposure, and sensitivity drops.
IR and multi-spectrum IR detectors
The pyroelectric or thermopile sensors are more stable but can drift or fail, and electronics can fail after years of heat and vibration.
All types
Electrolytic capacitors, relays, and heaters wear out.
How to confirm
If you have eliminated the window, power, wiring, moisture, and noise, and the detector still faults on a bench or on a known-good loop, the unit itself is failing.
Check the detector’s install date and service life in the manual, and look at any internal diagnostic counters or logs.
Fix
Replace the detector or sensor module. Keep a record of the replacement date to inform your lifecycle plan.
Cause 8: Configuration and Compatibility Problems
Faults can also come from setup errors:
- Detector configured for a different output mode (for example, 4-20 mA vs relay/HART)
- Controller input range does not match the detector’s fault signaling levels
- Wrong sensitivity or time delay setting that conflicts with the oi routine
- Firmware mismatch after replacement with a different revision
A replacement detector that “should be identical” can behave differently if the DIP switches, software settings, or firmware version are different.
Fix
Compare the configuration to the original commissioning records and the manufacturer’s manual. Make sure that the controller interprets the fault current level correctly.
Cause 9: The Problem Is Not the Detector
Sometimes the detector is healthy and the fault is generated elsewhere:
- A failing analog input card or channel
- Incorrect scaling or fault thresholds in the PLC/DCS or fire & gas panel
- A damaged barrier or isolator in the loop
- A loose connection in the marshalling cabinet
How to confirm
Inject a known 4-20 mA signal at the field terminals or the panel, or swap the input channel and see whether the fault follows the channel or stays with the detector.
Step-by-Step Diagnostic Sequence
When you are in front of a faulting detector, this order saves the most time:
- Notify the control room and follow your bypass and permit procedures.
- Read the fault code. Use LEDs, HART, Modbus, or the manufacturer’s tool. Many faults identify themselves (oi, low voltage, internal fault).
- Check the fault history. When does it fault: time of day, weather, plant events?
- Inspect the window. Clean it if dirty and see if the fault clears.
- Measure voltage at the detector terminals under load.
- Inspect the enclosure and glands for moisture and corrosion.
- Test the wiring: continuity, insulation, shields, terminations, junction boxes.
- Check the controller side: input channel, scaling, fault thresholds.
- Look for interference sources and check grounding.
- Swap with a known-good detector (matching model and configuration) to determine whether the problem follows the detector or stays with the location.
- Document everything and update your maintenance plan.
Fault Symptom Cheat Sheet
| Symptom | Most likely cause | First check |
|---|---|---|
| oi / optical fault after rain or dust | Dirty or wet window | Inspect and clean window |
| Fault in cold mornings | Icing, failed heater, voltage drop | Window heater, voltage under load |
| Fault only in the afternoon | Overheating, sun exposure | Housing temperature, shade |
| Random short faults | EMI, loose terminal | Shield grounding, wiggle test |
| Fault after washdown | Water ingress | O-ring, glands, conduit |
| Constant 0 mA at panel | Open loop or no power | Terminals, fuse, supply |
| Fault follows a particular detector when swapped | Failing detector | Replace or repair unit |
| Fault stays on the channel when detector swapped | Controller/input card | Test the input with a signal injector |
How to Prevent Repeat Flame Detector Faults
Fixing the fault is half the job. Prevent it from returning:
- Set a cleaning schedule based on the actual environment, not a generic interval.
- Perform functional tests with an approved test lamp at the intervals your safety plan requires.
- Trend your faults. Repeated faults on the same detector or area show a systemic cause.
- Keep spares of the exact model, with the right configuration.
- Inspect seals and glands during every planned visit.
- Record installation dates and plan sensor replacement before end of life.
- Review mounting positions for exposure to dirt, spray, sun, vibration, and EMI.
Why You Should Not Ignore Recurring Faults
A fault is the detector telling you it cannot be trusted to detect a fire. Resetting without finding the cause leaves a hidden gap in your fire and gas protection layer, and it can violate your safety management system and the integrity of your safety function. Treat every recurring fault as a reliability issue, not an operator inconvenience.
Frequently Asked Questions
What does a fault on a flame detector mean?
A fault means the detector has detected a condition that prevents it from reliably detecting flame, such as a dirty window, low voltage, internal failure, or loss of the signal loop. Treat the area as unprotected until it is fixed.
Why does my flame detector show an optical integrity (oi) fault?
It usually means the window is dirty, wet, scratched, or obstructed, or the internal optical path is degraded.
Cleaning the window clears most oi faults. If it persists after cleaning, the optics or sensor may be failing.
Can a flame detector fault because of weather?
Yes. Rain, fog, condensation, ice, and extreme temperatures can all trigger faults, either by affecting the window and heater or by exposing weak seals and connections.
Can a flame detector fault because of power supply problems?
Yes. Low voltage, voltage drop on long cable runs, ripple, and unstable power supplies are common causes of intermittent faults.
How do I know whether the detector or the wiring is faulty?
Swap in a known-good detector, or inject a 4-20 mA signal at the field terminals. If the fault follows the detector, replace or repair it. If the fault stays at the location or channel, check the wiring and controller.
How often should flame detectors be cleaned and tested?
It depends on the environment, the manufacturer’s recommendations, and your site’s safety plan. Dirty or coastal locations may need monthly or even more frequent window cleaning, while clean indoor areas may need much less.
Can I just reset a flame detector fault?
You can reset it, but doing that without finding the cause is risky. A fault that returns is a sign of an underlying problem, and the detector may not be protecting the area.
How long do flame detectors last?
Service life varies by technology and environment. Many industrial detectors are designed for years of operation, but UV tubes and electronics degrade over time. Check the manufacturer’s specified life and your own failure data.
Final Thoughts
Recurring flame detector faults rarely come from random bad luck. They come from dirty optics, weak power, bad wiring, moisture, noise, heat, or an ageing unit, and each leaves a pattern you can learn to read.
Work through the diagnostic sequence in order, confirm the cause with measurements rather than guesses, and fix the root cause so the same fault does not return next week.
If you manage a fire and gas system, make fault trending part of your routine. The goal is not just to clear faults, but to keep every detector ready for the day it is needed.