What Is a Carbon Monoxide and Combustible Gas Combination Alarm & How Does It Work? OEM Engineering Guide

For OEM purchasing personnel, “Combination Alarm” is a term that can easily lead to misinterpretations of specifications.

Customer inquiries often simply state:

“We need a CO combo alarm.”

However, this statement doesn’t clearly define the product.

A Smoke + CO Combination Alarm and a CO + Combustible Gas Combination Alarm are two different product architectures.

The former monitors: Smoke + Carbon Monoxide

the latter monitors: Carbon Monoxide + Combustible Gas.

The Combustible Gas can be Natural Gas/Methane (CH₄), LPG, or other combustible gases explicitly specified in the product design.

This distinction not only affects the Sensor BOM but also directly impacts the product’s installation location, intake structure, power supply, alarm algorithm, testing methods, and the final certification path.

Therefore, for OEM projects, we usually don’t start by confirming “what kind of enclosure is needed,” but rather by confirming:

Target Market → Target Gas → Installation Environment → Sensor Architecture → Power Supply → Alarm Logic → Applicable Standards → Certification Scope.

This is a more reliable order for defining the specifications of a CO + Gas combined alarm.

Quick Answer: What Is a Carbon Monoxide and Combustible Gas Combination Alarm?

The Carbon Monoxide and Combustible Gas Combination Alarm (CO + Gas Combination Alarm) simultaneously monitors carbon monoxide and a specified combustible gas.

Typical products may monitor:

CO + CH₄

or:

CO + LPG

However, “Gas” cannot be used as a final engineering specification.

The OEM RFQ must clearly specify which gas is being detected.

A typical architecture can be understood as follows:

CO → CO Sensing Channel → Signal Processing → MCU

Simultaneously:

Combustible Gas → Gas Sensing Channel → Signal Processing → MCU

Then the MCU drives the alarm based on the respective alarm logic of the two detection channels: Buzzer / LED / LCD / Voice / Relay / Wireless Communication

It is important to emphasize that:

CO + Gas vs Smoke + CO Combination Alarm: What Is the Difference?

Do not use “CO combo alarm” as the final RFQ description. Specify whether the project requires Smoke + CO, CO + CH₄, CO + LPG, or another defined sensing combination.

CS12 uses photoelectric light scattering + electrochemical CO sensing and lists EN 14604 and EN 50291-1; this is a typical Smoke + CO architecture.

CO + Gas products are completely different.

They do not have a smoke chamber.

Therefore, they cannot be classified into the same Combo specification simply because both products contain “CO”.

What Gases Can a CO + Combustible Gas Alarm Detect?

The vague term “Gas” must be separated here.

This may involve:

Carbon Monoxide — CO

CO is a toxic gas produced by incomplete combustion.

Its primary hazard mechanism is toxic exposure.

Therefore, CO alarm logic is usually not as simple as: Detected → Immediate Alarm.

It needs to consider: CO Concentration + Exposure Time.

Methane / Natural Gas — CH₄

Methane is the main component of natural gas. The main concern is combustible/explosion Risk. Therefore, the detection logic differs from CO.

LPG

LPG typically involves components such as propane and butane, but what a specific product claims to detect and how it is calibrated should be defined based on product design and target market.

This is why OEM specifications cannot simply state: “Combustible Gas Sensor.” It is necessary to further confirm:

Which gas is the product calibrated and certified to detect?

Why Installation Location Depends on the Target Gas

This is a crucial engineering difference between CO + Gas products and Smoke + CO products.

Different gases have different physical properties.

Therefore, one installation position should not be assumed to be correct for every CO + Gas combination. For example, if a product targets different combustible gases, its installation location needs to be determined based on the target gas, gas source, product manual, and applicable standards.

This directly impacts the OEM project’s: Housing Design → Mounting Method → ​​Manual → Warning Label → Packaging → Certification. Therefore, the engineering department must confirm the following before ID/structure finalization:

What gas are we detecting, and where is the finished alarm intended to be installed?

Do not design a generic enclosure first and then decide at the final stage whether to detect CH₄ or LPG.

How Does a CO + Combustible Gas Combination Alarm Work?

From a hardware perspective, it’s not as simple as “one sensor detecting two hazards.”

A more reasonable understanding is:

Two Detection Channels, One Product Platform

Typical System:

Simultaneously:

The MCU then executes its respective Calibration Parameters + Compensation + Fault Monitoring + Alarm Algorithm, ultimately controlling the Buzzer + LED + LCD + Voice + Communication. Specific sensor configurations must be confirmed for each model.

How Does the CO Detection Channel Work?

For products employing electrochemical CO sensors, CO in the air enters the sensor through the casing.

The sensor generates a weak electrical signal proportional to the CO concentration, which then passes through Amplification/filtering, an ADC, and an MCU. The MCU integrates with:

Therefore:

CO Sensor ≠ Complete CO Alarm.

Ultimately, CO alarm performance depends on the complete signal chain, firmware, gas calibration, and production consistency.

CFS’s existing Standalone CO technology also emphasizes the relationship among the sensor, signal processing, temperature compensation, algorithms, and mass-production control.

How Does the Combustible Gas Detection Channel Work?

A typical combustible gas detection channel requires:

Target Gas → Gas Sensor → Signal Conditioning → MCU → Gas Alarm Decision

However, the specific sensor technology depends on:

Sensor selection should follow the target gas—not the product name.

Why CO and Combustible Gas Need Different Alarm Logic

CO primarily focuses on toxic exposure. Combustible Gas primarily focuses on: Flammability/Explosion Risk. Therefore, the outputs of the two sensors cannot be unified into a simple ppm threshold.

CO Alarm Logic: CO typically uses concentration + Exposure Time for judgment.

The CFS GC01 lists CO response parameters, including 50 ppm, 100 ppm, and 300 ppm, corresponding to different alarm time windows.

Combustible Gas Alarm Logic: Combustible gas alarm logic is typically designed around the flammability risk of the target gas.

The engineering specifications should clearly define: Target Gas + Measurement Basis + Alarm Threshold + Tolerance + Response Time + Recovery Behavior. Specific thresholds should not be generalized across models in blog posts.

They should be based on the Applicable Standard, Certified Model, and Gas Calibration Specification.

CO and combustible gas should not share one generic alarm threshold because they represent different hazards and are evaluated using different detection logic.

Why Gas Calibration Is More Complex in a Combination Alarm

CO + Gas products mean the factory needs to control two detection channels.

For OEM procurement, the question shouldn’t be simply:

“Is the product gas tested?”

but rather:

“Which gas channels are calibrated, at what points, using what reference gas, and what production records are retained?”

Typical manufacturing controls need to consider:

CO Channel: CO Sensor → Signal Reading → Calibration → Alarm Verification

and:

Combustible Gas Channel:

Target Gas → Sensor Response → Calibration / Verification → Alarm Verification

Ultimately, it also requires:

Complete Product Functional Test

That is to say:

Sensor Calibration ≠ Finished Product Verification

Why Power Architecture Matters More in CO + Gas Alarms

CO electrochemical detection itself can achieve low power consumption.

However, the technology used in the combustible gas sensor directly changes the entire power budget.

Therefore, OEM customers ask:

“Can we make it a sealed 10-year battery model?”

The engineering department cannot answer solely based on battery capacity.

It needs to first confirm:

Combustible Gas Sensor Technology → Operating Current → Warm-Up → Sampling Strategy → MCU → Display → Buzzer → Communication → Battery.

CFS GC01 specifications currently list a DC 12 V / 0.5 A adapter. Before publication, the final power-consumption and backup-power specifications should be verified against the approved engineering specification.

CO + Gas Alarm Certification: Why One Certificate Is Not Enough

This part requires extreme caution because CO Compliance ≠ Combustible Gas Compliance, and it is certainly not the same as Smoke Alarm Compliance. Different hazards correspond to different standard systems.

Therefore, the Smoke + CO standards (EN 14604 + EN 50291) cannot be directly copied to CO + Gas products.

The CFS Smoke + CO series public page does indeed use EN 14604 for the Smoke side and EN 50291 for the CO side; this precisely illustrates that combined products need to define compliance scopes separately for different detection functions.

North American products also need to select standards based on the final product classification, target gas, usage scenario, and the scope confirmed by the certification body. For example, the CFS AJ987 current page lists UL 1484:2022 and UL 2034, but formal OEM projects should still confirm whether the specific model and actual configuration fall within the scope of the corresponding certificates and cannot infer this directly from the series pages on the website.

What Product Changes Can Affect Certification Scope?

Private label projects are particularly prone to this issue: The supplier has a certificate, so the buyer assumes the new SKU is automatically covered. However, actual projects require further verification regarding:

If there are any key configuration changes, an engineering and certification impact assessment should be conducted before mass production.

CO + Gas vs Smoke + CO vs Standalone Gas Alarm

Standalone vs RF vs Wi-Fi CO + Gas Alarm

“Combination” describes the detection architecture.

Standalone / RF / Wi-Fi describe the communication architecture.

Do not confuse the two items.

Therefore, a product can be:

CO + CH₄ + Standalone

or:

CO + CH₄ + RF Interlinked

or even:

CO + CH₄ + Wi-Fi Connected

What Should OEM Buyers Put in a CO + Gas Alarm RFQ?

When customers send inquiries, it won’t just be: “Need CO gas alarm. Please quote.”

What Should Buyers Test Before Approving a Sample?

Sample approval recommendations should at least cover:

Complete Product

Buzzer / LED / LCD / Test / Silence / Power / Fault indication。

Ultimately, confirm that both sensing channels function independently and correctly within the complete product architecture.

Prototype Pass ≠ Mass Production Pass

The fact that a single engineering sample can simultaneously detect CO and CH₄ does not guarantee that 10,000 mass-produced units will perform the same way. Mass production control is recommended.

The core question in procurement audits should shift from:

“Does the sample work?”

to: “How do you ensure every production unit performs like the approved sample?”

What Should OEM Buyers Audit at the Factory?

OEM & Private Label CO + Gas Alarm Options

Level 1 — Branding

Level 2 — Product Configuration

Evaluate within the limits permitted by engineering and certification standards:

Level 3 — Platform Development

Suitable for true ODM projects:

The deeper the customization, the earlier the impact of certification should be reviewed. Don’t wait until the sample is complete to ask the lab.

CFS CO + Gas Platform Example

The GC01 Standalone 2-in-1 CO + Gas Detector is listed as a CO + Gas platform device, featuring CO + CH₄ detection, a DC 12 V/0.5 A power supply, and local audible and visual status indication.

The website’s product matrix also lists the GC01R wireless interconnected version and the GC01W Wi-Fi version, allowing users to further select Standalone, Interlinked, or Connected solutions based on their project’s communication architecture.

FAQ