An open path gas detector (OPGD) integrates infrared absorbance over the full transmitter-to-receiver distance, so a 0.5–1 m dense plume that crosses the beam only attenuates a small slice of it, dropping the integrated signal well below the LEL-m equivalent alarm threshold [S2][S3].
For this reason, an OPGD is specified for fence-line and area coverage where a broad, migrating cloud is expected, and it is paired with point detectors when a small but locally concentrated leak is the dominant risk [S2][S6].
How an open path detector turns a beam into a gas reading
An OPGD is a line-of-sight IR link: a transmitter projects a focused infrared beam across the monitored volume, and a receiver measures the energy that arrives. Hydrocarbon vapour in the beam absorbs IR at characteristic wavelengths, and the receiver converts the loss of energy into a gas concentration [S2]. The reading is therefore an integrated absorbance, not a localised concentration.
Because the integration happens over the full path length, the same reported value can come from a thin highly-concentrated plume or a thick dilute cloud. The detector cannot tell the two cases apart, and that ambiguity is the root cause of the small-cloud miss [S2]. For general context on how a gas detector family is split into point, open-path, and ultrasonic variants, the same physical logic (local vs integrated sensing) governs the trade-off.
Field-of-influence and the spherical cloud rule
Mapping tools such as Detect3D place detectors against a spherical 100% LEL gas cloud whose diameter is scaled to the local confinement: 5 m in enclosed modules, 8 m in semi-enclosed areas, and 10 m in open modules [S3]. A point detector's field-of-influence is a sphere of that diameter, so any gas cloud whose centre is within the sphere alarms the device.
An OPGD's field-of-influence is a rounded cylinder along the beam axis, and the cloud only registers if the sphere's centre intersects the cylinder [S3]. A 0.5–2 m concentrated jet that drifts past the beam outside that intersection zone produces no alarm, even when the local concentration is well above 100% LEL. This geometry is why pairing an OPGD with a fixed gas detector at known leak sources is the standard mitigation in performance-based designs [S3][S4].
Why a small, dense release is the worst case for OPGD
At a pressurised leak, the release forms a high-velocity jet that is narrowest at the orifice; air entrainment then dilutes the jet and widens it as distance grows, until dilution begins to dominate and the cloud thins again [S4]. A detector placed right at the release point sees the narrowest, fastest part of the jet, and if it is offset from the centreline, the venturi effect of the jet pulls fresh air across the sensor head, further lowering local concentration [S4].
A small concentrated cloud is therefore both geometrically too short to dominate the beam integral and kinematically hard to keep inside the beam. Empirical trials reported by an OPGD manufacturer showed only a slight rise in alarm probability when a small or low-concentration cloud was released, because the integrated absorbance stayed near the noise floor of the path-length-weighted reading [S6]. The same logic drives the use of a combustible gas detector at the point of release to catch exactly this small-cloud case.
Comparison: open path vs point vs ultrasonic
Selection pivots on cloud size, cloud location, and required coverage area. An OPGD covers 5–120 m paths in one device and is the lowest-cost option per square metre for large open facilities, but it cannot localise along the path and is blind to a small concentrated jet that misses the beam [S2][S7]. A point portable gas detector or fixed catalytic/IR point sensor localises a leak within 1–5 m and triggers on a small cloud whose centre sits inside the spherical FOI, at the cost of covering far less area per device [S3][S4].
For personnel safety in a confined space or for a multi-hazard response, a multi-gas detector is the standard wearable, but it does not substitute for area coverage. Ultrasonic gas leak detectors, which listen for the acoustic emission of a pressurised release rather than waiting for a cloud to form, complement both OPGD and point detectors where the small, fast jet is the dominant scenario [S4][S7].
Design rules that close the small-cloud gap
Performance-based guidance (ISA TR84.00.07, BS 60080:2020, and the HSE OTO-93-002 dataset that anchors the 5 m / 8 m / 10 m spherical cloud sizes) all converge on three mitigations for the OPGD blind spot: place point detectors where the jet has widened to its maximum footprint, add ultrasonic detectors at high-pressure sources for the small-fast-jet case, and size the OPGD beam so it crosses the predicted cloud centre rather than the release point [S3][S4].
Two other engineering rules are non-negotiable: keep the transmitter and receiver on stable, vibration-free mounts because beam misalignment kills sensitivity and eventually faults the unit, and add rain/sun hoods to cut thermal drift across the optical window [S2]. A summary slide deck from an OPGD vendor concludes that the path-integrated reading inherently under-represents small, concentrated releases, and recommends layering OPGD with point and ultrasonic technologies rather than relying on a single line-of-sight device [S6][S7].
Failure modes and field symptoms
The dominant false-negative failure is exactly the small concentrated cloud: beam alignment is good, fog and rain are not at fault, and the unit still does not alarm because the path-integrated absorbance has not crossed the trip level [S2][S6]. The dominant false-positive is beam blockage, from a forklift crossing the path, heavy snow, or a bird sitting on the receiver window, which the unit reads as a high, broad absorbance and trips as a full-scale gas event [S2].
These two failure modes frame the maintenance regime: walk the beam with a gas test sheet monthly to confirm sensitivity along the path, log alignment checks after any nearby construction, and verify that a point detector at each credible leak source is in healthy state, because that point detector is the one device in the array that is physically capable of catching a 0.5–2 m concentrated plume [S3][S4][S6].
Trackable signals for specifiers: a refresh of Detect3D and similar F&G mapping tools to keep the 5 m / 8 m / 10 m cloud-size assumption aligned with the latest CFD-derived release footprints, and the next round of OPGD firmware that exposes raw path-integrated absorbance so small-cloud events can be trended against the alarm threshold [S3][S6].
See also our earlier report, Cloud vs Edge for Manufacturing Analytics: Latency Budget and Cost Verdict.