Fixed gas detectors with cloud monitoring

Gas detection normally arrives as a separate vendor, a separate panel and a separate screen nobody logs into. These detectors share one body, one wiring standard and one spares inventory across more than thirty gases, with the sensing cell setting the target and range. The relays trip locally with no network involved, and the same reading goes to a cloud that keeps the record and raises the alert.

Where fixed detection gets specified

The same detector body serves a pumping station, an animal house and a product somebody else puts their name on. What changes is the sensing cell and how deep the integration goes.

Industrial and municipal sites

Wastewater plants, pumping stations, chemical and fuel storage. Continuous toxic and combustible monitoring, local alarm relays that trip without a network, a 4-20 mA loop into the panel that is already installed, and a logged record of every excursion.

Enclosed livestock and process buildings

Ammonia in animal housing, CO2 in enclosed growing and storage, methane around digesters, oxygen in controlled-atmosphere rooms. Detection on the same bus as the climate and process sensors already in the building, with relays that stage fans before a reading becomes a loss.

Product builders and integrators

You are building a safety or environmental product and need detection as a component rather than as a project: one detector body covering dozens of gases, one wiring standard, and a cloud carrying your name rather than ours.

One body, one cell per gas

Every detector shares the same flameproof housing, LCD, relays, and outputs. The cell inside sets the target gas, range, and resolution. Selectable ranges below; the right range for your application is part of the scoping conversation.

Gas Formula Selectable ranges Resolution Response (T90)
Methane CH4 0-10 / 0-50 / 0-100 %VOL·%LEL 0.1 %LEL / 0.01 %VOL ≤25 s
Combustible (general) EX 0-100 %LEL 0.1 %LEL ≤25 s
Carbon monoxide CO 0-500 / 2000 / 5000 / 10000 ppm 0.1 / 1 ppm ≤15 s
Hydrogen sulfide H2S 0-10 / 20 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤15 s
Oxygen O2 0-30 / 0-100 %VOL 0.01 %VOL ≤15 s
Carbon dioxide CO2 0-1000 / 2000 / 5000 ppm / 0-20 %VOL 1 ppm / 0.01 %VOL ≤15 s
TVOC / VOC VOC 0-10 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤20 s
Benzene C6H6 0-1 / 10 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 ppm ≤30 s
Xylene C8H10 0-1 / 10 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 ppm ≤30 s
Styrene C8H8 0-20 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤30 s
Formaldehyde CH2O 0-5 / 10 / 20 / 100 / 200 ppm 0.01 / 0.1 ppm ≤30 s
Ammonia NH3 0-50 / 100 / 200 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤30 s
Nitrogen N2 0-100 %VOL 0.01 / 0.001 %VOL ≤15 s
Ozone O3 0-10 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤20 s
Hydrogen H2 0-1000 / 2000 / 5000 ppm / 0-4 %VOL 1 ppm / 0.01 %VOL ≤20 s
Tetrahydrothiophene THT 0-50 / 100 / 200 ppm·mg/m³ 0.01 ppm ≤30 s
Nitrogen oxides NOx 0-100 / 200 / 500 / 1000 ppm·mg/m³ 0.01 / 0.1 ppm ≤20 s
Nitric oxide NO 0-100 / 200 / 500 / 1000 ppm·mg/m³ 0.01 / 0.1 ppm ≤20 s
Nitrogen dioxide NO2 0-100 / 200 / 500 / 1000 ppm·mg/m³ 0.01 / 0.1 ppm ≤20 s
Sulfur dioxide SO2 0-100 / 200 / 500 / 1000 ppm·mg/m³ 0.01 / 0.1 ppm ≤20 s
Phosphine PH3 0-5 / 10 / 20 / 50 / 100 ppm 0.01 ppm ≤30 s
Ethylene C2H4 0-50 / 100 / 200 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤15 s
Hydrogen chloride HCl 0-20 / 50 / 100 ppm 0.01 / 0.1 ppm ≤25 s
Chlorine Cl2 0-10 / 20 / 50 / 100 / 200 ppm 0.01 / 0.1 ppm ≤20 s
Chlorine dioxide ClO2 0-20 / 50 / 100 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤30 s
Trichloroethylene C2HCl3 0-20 / 50 / 100 ppm 0.01 / 0.1 ppm ≤25 s
Cyanide CN 0-20 / 100 / 200 ppm 0.01 / 0.1 ppm ≤30 s
Hydrogen cyanide HCN 0-20 / 100 / 200 ppm 0.01 / 0.1 ppm ≤30 s
Ethylene oxide C2H4O 0-50 / 100 / 200 / 500 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤30 s
Hydrogen peroxide H2O2 0-20 / 50 / 100 / 200 / 1000 ppm 0.01 / 0.1 / 1 ppm ≤30 s
Arsine AsH3 0-5 / 10 / 20 ppm 0.01 ppm ≤30 s
Hydrogen fluoride HF 0-5 / 10 / 20 ppm 0.01 ppm ≤30 s
Fluorine F2 0-5 / 10 / 20 ppm 0.01 ppm ≤30 s

The alarm does not wait for the network

Gas detection has a hard requirement most sensors do not: the alarm must work even when the network does not. The platform layers cloud on top of local interlocks instead of replacing them.

Local interlock via relays

Two configurable alarm relays per detector, normally open dry contacts. Fans, solenoids, and sirens trip locally with no network dependency.

4-20 mA into existing panels

The analog loop feeds PLCs, DCS, and legacy alarm panels directly. The detector drops into an installed base without replacing it.

RS485 Modbus into our controllers

Digital readings stream over Modbus-RTU into our industrial IoT controllers, joining every other sensor on the site: climate, level, water quality, energy.

Cloud alerts, logs, and API

Concentration curves, threshold alerts to the right person by severity and shift, exportable excursion logs, and REST plus MQTT APIs for your MES or reporting stack.

Gas readings next to the rest of the site data

A gas reading is most useful next to the rest of the site's data: ammonia beside house temperature and ventilation state, methane beside digester process data, oxygen beside cold-room door events. Because the detectors join our controllers over the same Modbus bus as every other sensor, that context comes built in: one dashboard, one alert routing policy, one API, one brand on the app your operators open.

Questions we get about gas detection

How does one detector platform cover this many gases?

The detector body, display, outputs, and enclosure are identical across the family; the sensing cell inside sets the target gas and range. That means one spare-parts inventory, one integration, and one wiring standard across every gas point on a site. Cells are replaceable at end of life without changing the installation.

How do the detectors connect to the OmnIoT platform?

Each detector outputs 4-20 mA, RS485 Modbus-RTU, and two alarm relays in parallel. The Modbus output connects to our industrial IoT controllers alongside any other sensor on the site, streaming to the cloud for dashboards, alerts, and APIs. The analog loop and relays serve existing panels and local interlocks at the same time.

Do the alarm relays depend on the network?

No. The two relays are driven locally by the detector against its configured set points. Ventilation, shutoff, and sirens trip even if connectivity is down; the cloud layer adds logging, remote visibility, and escalation on top.

Can gas detection be part of a white-label product?

Yes. Detection sits on the same multi-tenant cloud as everything else, so the dashboard and the mobile apps carry your name and your customers sit in your tenant rather than in ours.

Are the detectors suitable for hazardous areas?

The detectors are built in flameproof aluminium enclosures designed for hazardous-area installation, with IP65 sealing for washdown and outdoor sites. Certification documentation for your market and installation class is scoped per engagement.

What does a gas detection engagement look like?

It starts with the gas points: which gases, at what ranges, how many, and what they have to report into. Most sites begin with a handful of detectors on the points that already worry someone before extending to the rest.

Send us the gas points

Which gases, at what ranges, how many points, and what panel or controller they have to report into. We come back with the cell and range to specify and how the detectors wire into what is already there.

Talk to us →