Fugitive gas detection system
AssigneeGas Activated Systems
InventorsMichael A. Bryan, Jerry W. Noles
Life of this patent
Estimating the term…
Abstract
A fugitive gas detection system is provided. The system includes a cloud service, a plurality of reach-based components, a plurality of wireless gas sensors. The reach-based components comprise backhauls and gateways. The wireless gas sensors are acted as nodes to acquire sensor data in a local mesh network and the nodes are connected to the cloud service through the reach-based components, one node can transmit the sensor data to other sensor nodes of the local mesh network. The system measures flammable gas levels with speed, economy and accuracy.
Claims19
A fugitive gas detection system, comprising,
- a cloud service;
- a plurality of reach-based components;
- a plurality of wireless gas sensors operating as nodes to acquire sensor data, wherein at least one of the gas sensors is a MEMS based multigas sensor, the MEMS based multigas sensor includes a plurality of probes to detect special qualities of a gas and the special qualities of the measured gas are recorded by a radar chart, the MEMS based multigas sensor detects the species and concentration of the gas using the radar chart;
- and
- wherein the nodes are connected to the cloud service through the reach-based components.
A fugitive gas detection system, comprising,
- a cloud service;
- a plurality of reach-based components;
- a plurality of wireless gas sensors operating as nodes to acquire sensor data, wherein each node includes an on-board GPS;
- and
- wherein the nodes are connected to the cloud service through the reach-based components.
A fugitive gas detection system, comprising,
- a cloud service;
- a plurality of reach-based components;
- a plurality of wireless gas sensors operating as nodes to acquire sensor data, wherein a gas detected by each of the plurality of wireless gas sensors is selected from the group consisting of methane, ethane, propane, butane, acetone, and methanol;
- and
- wherein the nodes are connected to the cloud service through the reach-based components.
Dependencies are inferred from the claim text.