Non-Contact Level Measurement

Non-Contact Level Measurement

Non-Contact Level Measurement keeps sensors above the liquid surface to deliver accurate, low‑maintenance water‑level readings for tanks, wet wells and open channels. By using radar or ultrasonic time‑of‑flight methods and modern LPWAN or cellular telemetry, utilities avoid fouling, reduce confined‑space entries, and achieve audit‑ready flow and alarm data.

At a Glance

Contactless level measurement for utilities

A water-level-sensor mounted above the medium delivers reliable readings without touching wastewater, sludge, or corrosives — reducing fouling, OPEX and confined‑space entries. High‑performance radar-level-sensor products (nanoradar technology) provide millimetre‑class repeatability in many field conditions; MERATCH radar devices document ±2 mm precision and IP68 / IK10 ruggedness. (meratch.com)

Non‑contact instruments pair naturally with remote telemetry: attach a datanode or IoT gateway for redundant backhaul (NB‑IoT / LoRaWAN / LTE‑Cat‑M) and local buffering with a datanode-iot or iot-data-logger. MERATCH datanode products list multi‑network options (NB‑IoT, LTE Cat‑M, NTN Satellite, LoRaWAN) and 5+ year autonomy profiles when sized with appropriate batteries and send intervals. (meratch.com)

Why Non-Contact Level Measurement Matters in Water Management

Non‑contact level instruments transmit a microwave or acoustic pulse to the liquid surface and measure the return time (or phase shift) to compute height relative to a fixed datum; because the transducer never touches the medium, maintenance and OPEX are reduced while achieving sub‑centimetre repeatability.

For harsh, aerated, or odorous assets, a non‑invasive approach simplifies hygiene, reduces CIP needs, and limits technician exposure. Modern radar instruments excel in vapour, steam, and heavy turbulence; ultrasonic-level-sensor options are cost‑effective where the air path is clear. Pairing above‑surface measurement to SCADA and LPWAN telemetry transforms level readings into event‑driven alarms, pump control logic, and defensible flow computations for compliance and billing. See also remote-monitoring and telemetry.

Standards and Regulatory Context

Non‑Contact Level Measurement intersects enclosure, safety, EMC, radio and hydrometry standards that should be included in procurement and acceptance tests.

• Enclosures and sealing: specify IP68 or NEMA 4X for outdoor pits and wet wells. MERATCH radar and combined RLS+Datanode units are rated IP68 / IK10. (meratch.com)
• Functional safety and EMC: IEC/UL 61010‑1 instrument safety and IEC/EN 61326‑1 EMC are commonly required for process integrations.
• Hazardous areas: ATEX (2014/34/EU) / IECEx markings for Zone 1/2 gases in lift stations — specify Gas Group and T‑class.
• Radio compliance: LoRa/Cellular radios must meet FCC Part 15 or EU RED requirements; MERATCH devices list multi‑network options for redundancy. (meratch.com)
• Open‑channel flow: use ISO methods (e.g., ISO 1438 for thin‑plate weirs) when converting level to discharge so computed flow is defensible in audits. (iso.org)

A concise specification table helps align vendors:

How Non-Contact Level Measurement is Installed / Measured / Calculated / Implemented: Step-by-Step

A robust deployment follows a disciplined workflow that matches physics to hydraulics, verifies geometry and commissions telemetry.

1. Select the sensing method for the asset.

   • Use radar-level-sensor (FMCW or pulse) for steam, strong vapor, foam, narrow manholes or long ranges. See nanoradar-technology. (meratch.com)
   • Choose ultrasonic-level-sensor where the air path is clear and condensation is manageable.

2. Define geometry, datum and blanking zones.

   • Establish a permanent datum (e.g., invert) and configure empty/full distances. Record the stage-discharge-relationship or weir/flume constants before commissioning.

3. Survey the site and prepare mounting.

   • Verify the beam path: keep ladders, cables and inflows out of the beam angle. Mount opposite inflow where possible to reduce streaming.

4. Install brackets and align the sensor.

   • Mount perpendicular to the surface; use adapters or stilling wells only when datasheet and hydraulics justify them. Reference meratch mounting adapters for rapid installs. (meratch.com)

5. Provide power and cable management.

   • For plant sites use 24 VDC or loop‑powered 4–20 mA wiring with surge protection.
   • For remote nodes, pair the instrument with a datanode-iot or iot-data-logger and choose LPWAN/cellular (see LoRaWAN, NB‑IoT or LTE‑Cat‑M). Use low‑power strategies and size battery-life-iot-sensor and optional solar harvesters accordingly. (meratch.com)

6. Configure outputs and data structures.

   • Map primary process variable to Modbus/HART or to a telemetric payload. Document register maps in the commissioning pack.

7. Commission the instrument precisely.

   • Run false‑echo mapping (radar) or echo‑profile tuning (ultrasonic) at mid‑span; enable temperature compensation and echo damping for pump cycles.

8. Validate with independent references.

   • Cross‑check readings against a staff gauge or manual tape at multiple levels; log as‑found/as‑left values for audits.

9. Integrate to SCADA and alarms.

   • Connect with scada-system or to cloud telemetry; configure high/low, rate‑of‑change and stage alarms.

10. Harden and maintain.

• Verify IP rating after installation torque settle, schedule echo‑profile checks, firmware refresh via OTA or Bluetooth, and battery audits if using LPWAN. See ota-firmware-update and remote-monitoring.

Quick commissioning tip (callout)

• Use echo mapping logs to create a baseline. If you keep echo snapshots in the iot-data-logger, you reduce troubleshooting time after mechanical changes.

Field Callouts — real pilots, practical advice

Key Takeaway from FLOPRES / Graz pilots

• Rural pilots (FLOPRES) proved two‑person crews can complete a MERATCH radar + datanode setup in under 20 minutes; field nodes showed uninterrupted operation in subzero conditions and battery life projections aligned with multi‑year targets. See project references in the References section for details.

Installation quick tips

• Avoid placing the transducer where road spray or snow can accumulate; where unavoidable, use a protective hood and plan for seasonal visual checks. Use ik10-impact-rating and ip68-protection-rating as procurement minimums.

Summary

Non‑Contact Level Measurement keeps sensors out of the liquid, delivering dependable accuracy with less cleaning, safer maintenance and easier integration to plant control, edge analytics and LPWAN telemetry. By matching radar or ultrasonic physics to the asset, writing standards‑aware specs and commissioning with echo‑profile validation, utilities achieve higher uptime and confident audits. MERATCH product blocks (radar + datanode) provide a tested, rapid‑deploy combination for flood warning and urban wastewater monitoring. (meratch.com)

Frequently Asked Questions

1. How is Non‑Contact Level Measurement calculated, measured and implemented in water management?

   • By sending an acoustic or microwave pulse and measuring the return time (time‑of‑flight) or phase/beat frequency (FMCW radar) relative to a fixed datum, then converting that height into process values or flow using documented algorithms. Validate with staff gauges and document uncertainty.

2. What are the decision rules for choosing radar vs ultrasonic in foamy or aerated wet wells?

   • Choose radar if foam, vapor, strong turbulence or high temperatures are present; ultrasonic is suitable where the air path is clean and condensation is manageable. If in doubt, pilot both and compare echo profiles.

3. Which output/protocol stack integrates most cleanly with PLC/RTU and LPWAN backhaul?

   • For PLC/RTU use 4–20 mA or Modbus; for cloud/remote monitoring pair a local datanode with NB‑IoT, LoRaWAN or LTE‑M for cellular backhaul. MERATCH datanode supports multi‑network redundancy. (meratch.com)

4. How do we mount a non‑invasive level sensor in narrow manholes with obstructions while preserving beam clearance?

   • Use side‑mounted brackets, target plates, or stilling wells if hydraulics allow; map blanking zones and run echo profiles during commissioning to confirm the sensor ignores mounting echoes.

5. What documentation proves compliance for ATEX/IECEx and EMC when the transmitter includes LTE‑M or NB‑IoT radios?

   • Vendor declarations of conformity, EMC/RED test reports, and ATEX/IECEx certificates for the exact model; include RF module certification and regional compliance evidence in the procurement pack.

6. How do battery life, reporting interval and PSM/eDRX settings translate into 5–10‑year TCO for remote nodes?

   • Battery life depends on send interval, payload size, and cellular power envelopes. Use a conservative estimate from datasheets (MERATCH datanode shows ≥5 years at 1‑hour interval on D‑battery) and include field maintenance and replacement logistics in TCO. (meratch.com)

Optimize Your Water Management with Non‑Contact Level Measurement

Specify the right physics, validate geometry, and integrate with proven protocol stacks (scada-system, edge-computing-iot, telemetry) to turn level data into reliable pump control and defensible compliance. Use datanode-iot + radar sensor bundles for large deployments to reduce visits and predict lifetime costs. (meratch.com)

Learn more

For a deeper dive on sensor physics and MERATCH product options, see radar-level-sensor and datanode-iot.

References

MERATCH datasheets (selected)

• MERATCH Radar Level Sensor — measurement range 0.2–22 m; precision ±2 mm; IP68, IK10; resolution 1 mm; LoRaWAN/NB‑IoT options; lifetime up to 10 years depending on reporting interval. See datasheet. (meratch.com)
• MERATCH Datanode — multi‑network connectivity (NB‑IoT, LTE Cat‑M, NTN Satellite, 2G fallback, LoRaWAN), IP67, autonomy ≥5 years (1‑hour interval on D‑battery), BLE local interface and OTA firmware. (meratch.com)
• MERATCH Radar Level Sensor + Datanode bundle — combined specification on the RLS+Datanode datasheet (same accuracy and protection; multi‑network redundancy). (meratch.com)

Project references (real world deployments)

• FLOPRES – Flash Flood Prediction System: early warning using MERATCH water level sensors, rain gauges and humidity sensors across Eastern Slovakia and Poland. Two‑person installs under 20 minutes; expansion target 60 villages by Feb 2025. (See project blog for install notes.)
• Danube River Floodplain Monitoring: 12 high‑precision IoT water level sensors (NB‑IoT) for automated floodplain management; millimetre‑level accuracy and 5‑year battery life in pilot. (Case study available.)
• Bratislava Wastewater Management & BVS: radar‑based monitoring with CORVUS repeaters to overcome underground signal challenges — transformed operations to data‑driven workflows.
• Residential Septic Tank Monitoring: single radar node with LoRaWAN backhaul delivering capacity monitoring and desktop notifications for maintenance.

(Full project details and links available in MERATCH case studies and blogs.)

---

Author Bio (Do not change or add anything)

Ing. Peter Kovács, Technical Freelance writter

Ing. Peter Kovács is a senior technical writer specialising for smart‑city infrastructure. He writes for municipal water management engineers, city IoT integrators and procurement teams evaluating large tenders. Peter combines field test protocols, procurement best practices and datasheet analysis to produce practical glossary articles and vendor evaluation templates.