A gas detector on its own only measures. It senses a gas, shows a number, and maybe sounds a local alarm.
A fire and gas system (F&G) is what turns that measurement into action: warning operators, shutting down equipment, isolating fuel, stopping ignition sources, and starting ventilation or suppression.
Integration is the link between the two, and it’s where many installations succeed or fail. A perfectly good detector wired, scaled, or voted incorrectly can fail silently, or trip the plant at 3 a.m. for no reason.
In this guide you’ll learn how gas detectors connect to F&G systems, which signals and protocols are used, how voting logic and cause-and-effect matrices work, how SIL fits in, and the integration mistakes I see most often in the field.
What Is a Fire and Gas (F&G) System?
A fire and gas system is a dedicated safety system that detects hazardous events (flammable gas leaks, toxic gas releases, oxygen deficiency, fire, smoke, heat) and automatically executes protective actions.
You’ll find F&G systems in oil and gas facilities, refineries, petrochemical plants, LNG terminals, power generation, battery storage, semiconductor fabs, wastewater plants, and other sites where a gas release or fire can escalate quickly.
Key characteristics
Independent from process control
An F&G system is normally separate from the basic process control system (BPCS/DCS), so a control failure doesn’t disable safety detection.
Safety-rated logic
The logic solver is typically a certified safety PLC designed to IEC 61508 and applied under IEC 61511 (or ISA-84 in North America).
Defined actions
Every detection event maps to a documented response through a cause-and-effect matrix.
Fail-safe thinking
The design assumes components will eventually fail and decides in advance how the system should behave when they do.
F&G System vs. a Standalone Gas Monitor
| Feature | Standalone gas monitor | Integrated F&G system |
|---|---|---|
| Main function | Measure and alarm locally | Detect, decide, and execute protective actions |
| Logic | None or simple relay | Safety logic solver with voting and C&E matrix |
| Outputs | Local horn/strobe | Alarms, ESD, HVAC control, deluge, door/damper control, notifications |
| Fault handling | Local fault indication | Fault annunciation, inhibit logic, degraded voting |
| Typical standards | Product certification | IEC 61511 / ISA-84, IEC 61508, EN 50402, ISA-TR84.00.07 |
| Operator interface | Display on unit | Central HMI/operator station, event log, alarm management |
F&G System Architecture: From Detector to Final Elemen
Think of the F&G system as three layers that mirror a safety instrumented function.
Sensing layer (inputs)
Gas detectors, flame detectors, smoke/heat detectors, manual call points.
Logic layer (decision)
The F&G logic solver and its input/output modules.
Action layer (outputs/final elements)
Alarms, shutdown valves, fans and dampers, suppression systems, and the link to the plant ESD.
Typical signal path
Gas detector → junction box / marshalling → F&G input card → logic solver (voting, C&E) → output card → alarm / ESD / HVAC / suppression
In parallel, the logic solver sends status data to the operator HMI and, usually through a controlled one-way or gateway connection, to the DCS or SCADA for visibility.
Which detectors connect to an F&G system?
| Detector type | What it detects | Common F&G use |
|---|---|---|
| Catalytic bead (pellistor) | Flammable gas (% LEL) | Point detection in process areas |
| Infrared (NDIR) point | Hydrocarbon gases (% LEL or % vol.) | Preferred in many outdoor and harsh environments |
| Open-path infrared | Gas along a beam path (LEL·m) | Perimeter and large-area coverage |
| Electrochemical | Toxic gases (H₂S, CO, Cl₂, etc.) and O₂ | Toxic and oxygen monitoring |
| Ultrasonic gas leak detector | Acoustic signature of pressurized leaks | High-pressure outdoor areas where gas cloud detection is difficult |
| Flame detector (UV, IR, UV/IR, multi-spectrum IR) | Flame radiation | Fire detection around fuel sources |
| Smoke/heat detector | Smoke or temperature rise | Buildings, control rooms, enclosures |
Each technology has strengths and weaknesses, so the right selection depends on the gas, the environment, and the risk assessment. (See our guides on sensor technologies and how environmental conditions affect gas detectors.)
How Gas Detectors Communicate with the F&G System
This is the heart of integration. There are several common signal methods, and many facilities use more than one.
Analog 4–20 mA (the industry workhorse)
The detector transmits a current proportional to the gas concentration:
- 4 mA = zero gas
- 20 mA = full-scale range (for example 100% LEL, or 100 ppm H₂S)
Why it’s popular:
- Simple, robust, and well understood
- Allows continuous monitoring, trending, and wire-break detection (a loop current of 0 mA is clearly abnormal)
- Works with almost every F&G input card
Important
Fault and inhibit signaling on the current loop is manufacturer-specific. Many devices drop below 4 mA to indicate a fault, often in line with NAMUR NE43 (under about 3.6 mA for failure, over about 21 mA for over-range), and some use set values such as ~1–2 mA for calibration or inhibit.
The F&G input card must be configured to recognize these ranges as faults, not as “zero gas.” Always check the detector manual.
HART over 4–20 mA
HART superimposes a digital signal on the analog loop. The analog value still drives the safety function, while HART gives maintenance teams diagnostics, calibration data, and configuration without extra wiring. It’s a cost-effective upgrade path for existing 4–20 mA installations.
Relay (dry contact) outputs
Many detectors provide alarm relays (low alarm, high alarm, fault). These are simple and independent of the analog signal, but they carry less information, and relay outputs should be supervised (for example with end-of-line resistors) where wire faults would otherwise go unnoticed.
Digital serial and fieldbus (Modbus RTU, PROFIBUS, Foundation Fieldbus)
Digital communication reduces wiring and provides rich diagnostic data. Modbus RTU over RS-485 is very common for gas detectors.
These links are typically used for monitoring and diagnostics, and many sites keep the primary safety trip on a hard-wired or certified path.
Ethernet-based protocols (Modbus TCP, OPC UA)
Increasingly used between the F&G controller and higher-level systems such as SCADA, historians, and asset management tools.
Cybersecurity must be considered carefully, since the safety system should not be exposed to uncontrolled network traffic. (Our article on gas detection in the IIoT era goes deeper.)
Wireless (WirelessHART, ISA100.11a)
Useful for hard-to-wire locations and temporary monitoring. Latency, battery life, and signal reliability must be assessed before using wireless for any safety-critical trip function.
Signal Method Comparison
| Method | Information | Wiring effort | Typical role |
|---|---|---|---|
| 4–20 mA | Concentration, basic fault | Low | Primary safety input |
| 4–20 mA + HART | Concentration + diagnostics | Low | Primary input with maintenance data |
| Relay contacts | Alarm states only | Medium (per alarm) | Backup or simple systems |
| Modbus RTU / fieldbus | Rich digital data | Low (multi-drop) | Monitoring, diagnostics |
| Ethernet (Modbus TCP/OPC UA) | System-level data | Low | SCADA, historian, remote access |
| Wireless | Concentration + status | Very low | Non-critical or hard-to-wire points |
Alarm Levels and Setpoints
F&G systems use staged alarms so operators get early warning before automatic action. Typical examples (always defined by your site risk assessment and regulations, not by this table):
| Gas | Low alarm (alert) | High alarm (action) | Notes |
|---|---|---|---|
| Combustible gas | ~20% LEL | ~40–60% LEL | Always well below the LEL |
| Hydrogen sulfide (H₂S) | ~5–10 ppm | ~15–20 ppm | Depends on exposure limits and local rules |
| Oxygen (O₂) | 19.5% (deficiency) | 23.5% (enrichment) | Both directions matter |
| Carbon monoxide (CO) | ~25–35 ppm | ~100+ ppm | Depends on application and exposure limits |
A good rule
Low alarm means “investigate,” high alarm means “act,” and the F&G system should make that distinction clear in both the HMI and the field alarms.
Voting Logic: Reducing False Trips Without Losing Safety
Voting logic is one of the most important concepts in F&G integration. Instead of tripping on a single detector, the logic solver requires a combination of detectors to confirm an event.
| Voting | Meaning | Benefit | Trade-off |
|---|---|---|---|
| 1oo1 | 1 out of 1 | Fastest response | Any false alarm causes a trip |
| 1oo2 | 1 out of 2 | High safety availability | More spurious trips |
| 2oo2 | 2 out of 2 | Fewer false trips | A single failed detector can block detection |
| 2oo3 | 2 out of 3 | Balances safety and availability | More detectors and cost |
Practical points
Voting applies to detection, not to every alarm
It’s common to alarm on a single detector but trip only on a voted condition.
Detector faults must be handled in the logic
In a 2oo3 arrangement, a faulted detector usually degrades the vote to 1oo2 or 2oo2 depending on the philosophy. This must be defined in the design.
Coverage matters more than count
Voting does not help if detectors are placed where gas will never reach them. Detector placement should come from gas dispersion considerations, release scenarios, and mapping studies (see ISA-TR84.00.07 for performance-based F&G design).
The Cause-and-Effect Matrix: Where Detection Becomes Action
The cause-and-effect (C&E) matrix is the document that defines what happens when each detector or group of detectors activates.
It links causes (detector alarms, voted conditions, faults, manual pushbuttons) to effects (outputs).
Common effects triggered by gas detection:
- Audible and visual alarms (horns, beacons, voice alarms)
- Shutdown of ignition sources and non-essential electrical loads in hazardous areas
- Process shutdown or isolation (ESD valves)
- Closing of HVAC dampers and starting of purge or extraction fans
- Activation of deluge or suppression systems (more typical for fire than gas)
- Door and access control actions
- Notifications to the control room, SCADA, or emergency response
Tip from the field
A C&E matrix that nobody tests is a document, not a safety function. Treat full C&E testing as part of commissioning and periodic proof testing.
Functional Safety: SIL, Standards, and Certified Detectors
Gas detection used for a protective function often falls within functional safety requirements.
Key standards you’ll encounter:
IEC 61508
Functional safety of electrical/electronic/programmable electronic safety-related systems (product level).
IEC 61511 / ISA-84
Functional safety for the process industry (application level).
ISA-TR84.00.07
Guidance on evaluating the effectiveness of fire and gas systems.
IEC 60079-29-1
Performance requirements for flammable gas detectors.
IEC 60079-29-2
Selection, installation, use, and maintenance of flammable gas and oxygen detectors.
EN 50402
Functional safety requirements for fixed gas detection systems.
Typical integration implications
- Use detectors with relevant certifications (hazardous area approval such as ATEX/IECEx or Class I Div. 1/2, and functional safety certification where required).
- Verify the whole loop, not just the detector. SIL is achieved by the complete safety function: sensor, input module, logic solver, output module, and final element.
- Plan proof testing. The PFDavg calculation assumes the proof test interval and coverage you actually perform in service.
- Don’t confuse “SIL-capable” with “SIL-achieved.” A SIL-rated device is only one part of the loop calculation.
For a deeper dive, read our guide on SIL 2 and SIL 3 requirements in gas detection.
Wiring and Installation Considerations
Good integration starts with good installation. Pay attention to:
Wiring topology
2-wire loop-powered, 3-wire, or 4-wire transmitters each have different power and signal requirements. Make sure the input card matches ( sink vs. source).
Hazardous area protection
Use the correct protection method (intrinsic safety with barriers, flameproof enclosures, or increased safety) and follow certification conditions.
Cabling
Shielded twisted pair, correct grounding of shields at one end only (per design), and segregation from power cables to reduce noise.
Cable glands and sealing
Moisture ingress is a leading cause of unexplained signal drift and false alarms.
Power supply integrity
Low voltage at the far end of a long cable can cause erratic readings or resets. Calculate voltage drop.
Mounting position
Lighter-than-air gases (methane, hydrogen) are typically detected high, heavier-than-air gases (propane, H₂S in many cases, chlorine) low, but real placement should follow release studies and ventilation patterns.
Accessibility
Detectors must be reachable for calibration and testing, or the program will quietly slip.
Commissioning and Testing the Integration
Before a detector is considered integrated, verify:
Loop check
Confirm tag, range, units, and scaling from the field device to the HMI.
Signal range check
Simulate 4 mA, 20 mA, below-range, and over-range. Confirm the F&G system shows the correct state, including fault at fault current levels.
Gas test (bump test and calibration)
Apply known test gas and confirm alarm setpoints and responses. (See our guides on calibration and zeroing and span troubleshooting.)
Voting logic test
Trigger combinations and confirm the expected vote results, including degraded voting with a faulted or bypassed detector.
Cause-and-effect test
Confirm every effect (horns, dampers, valves, shutdowns) operates as documented.
Inhibit and bypass test
Confirm that calibration or maintenance mode is clearly annunciated, time-limited, and managed by procedure.
Fail-safe test
Break the loop wire and remove power to confirm the system fails to a safe, annunciated state.
Documentation
Update drawings, I/O lists, C&E, and test records so the as-built matches reality.
Common Integration Mistakes (and How to Avoid Them)
Treating a fault as zero gas
If the input card doesn’t recognize sub-4 mA values as a fault, a failed detector looks “healthy” at zero. Configure fault ranges and alarm on them.
Wrong range or scaling
A detector scaled 0–100% LEL but configured as 0–50% LEL in the logic solver will misreport every reading.
Forgetting inhibit/calibration status
A detector left inhibited after calibration may leave an area unprotected. Alarm on prolonged inhibit.
Overly aggressive voting
2oo2 voting with poor coverage can produce a system that never trips when it should.
Under-voting with unreliable detectors
1oo1 trips from a drifting sensor lead to spurious shutdowns and eventual operator distrust. (See false alarms in gas detection.)
Mixing safety and control without separation
Sharing detectors or logic between BPCS and F&G without clear independence undermines the safety case.
Ignoring environmental effects
Humidity, temperature, condensation, and contaminants cause drift and sensor poisoning that show up as integration problems. (See catalytic sensor poisoning and condensation and infrared detection.)
Poor alarm management
Too many unprioritized alarms bury important events during a real incident.
No periodic C&E testing
Logic changes, I/O reassignments, and software updates can silently break a function that passed at commissioning.
Weak cybersecurity
Opening safety system data to broader networks without proper segmentation introduces risk. Follow IEC 62443 principles.
Best Practices Checklist
- Start from a documented hazard and risk assessment, not from a detector catalog.
- Choose detector technology based on gas, environment, and failure modes.
- Use 4–20 mA (with HART where useful) for primary safety signals.
- Configure the F&G system to recognize fault, inhibit, and over-range states.
- Define voting and degraded-voting behavior in writing.
- Keep the C&E matrix current and test it.
- Make calibration and bump-test access part of the design.
- Track detector health, calibration history, and alarms with a maintenance system.
- Control access to bypasses and inhibits, and log every use.
- Review and test after any change to logic, I/O, or detector hardware.
Fixed Detectors and the Wider Safety Ecosystem
Fixed gas detectors connected to the F&G system protect permanent locations. They work best alongside:
- Portable gas detectors for personal protection, confined space entry, and maintenance work (a different safety layer, not a replacement).
- Fleet or asset management software to track calibration, bump tests, and alarms.
- Procedures and training so operators know exactly what each alarm level means.
If you’re comparing options, see our guide on fixed vs. portable gas detectors and point detectors vs. multipoint sampling systems.
Frequently Asked Questions
What is the difference between an F&G system and a SIS?
A safety instrumented system (SIS) is a broad term for systems that perform safety instrumented functions to reduce process risk, such as an emergency shutdown.
An F&G system is a specialized safety system focused on detecting fire and gas hazards and initiating mitigation.
In many plants, the F&G system is a separate system that interfaces with the ESD, though the two can be combined in some architectures.
Do all gas detectors in an F&G system need to be SIL-rated?
Not necessarily. Whether a detector needs a SIL rating depends on the risk assessment and the safety integrity level assigned to the specific safety function it supports.
Where a SIL is required, use equipment with suitable functional safety certification and verify the entire loop.
What is the best signal type for connecting gas detectors to an F&G system?
For primary safety inputs, 4–20 mA (often with HART) remains the most common because it is simple, reliable, and supports fault detection.
Digital protocols such as Modbus are valuable for diagnostics and monitoring, but many sites keep the main safety trip on the analog or hard-wired path.
How many gas detectors are needed for voting logic?
It depends on the voting scheme: 1oo2 and 2oo2 need at least two detectors, and 2oo3 needs at least three covering the same hazard zone.
The number and location of detectors should be based on a detector mapping or performance-based study, not a fixed rule of thumb.
Can portable gas detectors connect to an F&G system?
Generally no for safety trips. Portable detectors protect individual workers and are not designed to be permanent safety inputs.
Some portable and area-monitoring devices can share data through wireless or software platforms, but they should not replace fixed detection in an F&G design.
How often should the gas detection portion of an F&G system be tested?
Frequencies depend on the manufacturer’s recommendations, regulations, the SIL calculation assumptions, and site experience.
Bump tests, calibrations, and full functional (C&E) tests are normally scheduled at different intervals, and the intervals should be documented in the safety requirements specification and maintenance plan.
What happens if a detector fails in an F&G system?
The system should annunciate a fault, and the logic should respond according to the design: for example, degrading a 2oo3 vote to 1oo2, or applying a defined fail-safe action. Fault handling should be defined in the C&E and tested.
Conclusion
Integrating gas detectors with a fire and gas system is more than connecting wires. It means choosing the right detection technology, sending reliable signals to a properly configured logic solver, defining voting and fault behavior, linking detection to meaningful actions in the C&E matrix, and proving the whole chain works through commissioning and ongoing testing.
When integration is done well, operators trust the system, false trips drop, and when a real leak occurs the plant responds the way it was designed to. When it’s done poorly, a good detector can be completely wasted.
Key takeaways:
- An F&G system turns gas measurements into protective actions.
- 4–20 mA (with HART) remains the standard for primary safety signals, with digital protocols for diagnostics.
- Configure fault, inhibit, and over-range states, not just alarm setpoints.
- Voting logic balances safety and availability, but only works with good detector coverage.
- Test the full chain, including the C&E matrix, and keep testing it over the life of the plant.
Want more practical guidance on gas detection and safety systems? Explore the related guides on safeguardsense.com and subscribe for new articles.
About the author
Written by Seki Hudson, an industrial automation engineer specializing in gas detection and industrial safety systems, with hands-on field experience in fixed and portable gas detection.
Disclaimer
This article is for general educational purposes. Alarm setpoints, detector selection, voting, SIL targets, and testing intervals must be determined by a qualified engineer based on a site-specific risk assessment, applicable regulations, and manufacturer documentation.
