Radar Level Sensor

Practical, standards-aligned guide to non-contact radar level sensors for water and wastewater — selection, commissioning, maintenance, and real-world references.

Radar Level Sensor
non-contact radar
FMCW
60 GHz

Radar Level Sensor

Reliable non-contact radar water level sensor

Non-contact radar level sensors are a first-choice instrument when operators need continuous, low-touch water level sensor telemetry with minimal fouling and maintenance. Because they measure distance with electromagnetic waves rather than pressure or floats, they avoid many common failure modes of contact systems and deliver stable readings for process control, flood warning and wastewater compliance.

Radars work through steam, light fog, moderate surface foam and mist far better than many ultrasonic options, which can be affected by vapour layers and temperature gradients. This behaviour is documented in technical manufacturer guidance and white papers comparing radar and ultrasonic performance in wastewater and treatment-plant environments. (us.endress.com)

Early inclusion of non-contact sensors in a telemetry architecture reduces truck rolls, confined-space entries and OPEX while improving operator confidence in alarms and pump-control logic. For city-scale programs these benefits translate directly to lower service costs and improved regulatory reporting.

Why Radar Level Sensor Matters in Water Management

Non-contact non-contact level measurement is especially valuable across the following asset classes:

  • Finished-water reservoirs and clearwells
  • Stormwater detention and retention basins
  • Combined sewer overflow (CSO) chambers and culverts
  • Sludge and biosolids tanks (where fouling is severe)
  • Remote river gauging and flood early-warning stations

Because modern radar modules use narrow-beam mmWave front-ends (often marketed as nanoradar technology), they can be retrofitted into existing nozzles and vaults with fewer false-echo issues than older broad‑beam units.

Operational highlights:

  • Resilient in mist/fog/steam compared to many ultrasonic level sensor installations. (us.endress.com)
  • Lower long-term OPEX from fewer maintenance visits and less manual calibration; supports predictive maintenance workflows.
  • Flexible backhaul options (wired 4–20 mA/HART and modern LPWANs) that let integrators choose the appropriate network sxample (device families): MERATCH offers LoRa and NB‑IoT variants of compact level sensors (MLLO2301 / MLNB2301) described in factory test documentation and radio reports; these documents show the prodtest outcomes.

For gateway-level deployments choose hardened outdoor gateways (example: Kerlink Wirnet iStation) that include LoRa and cellular backhaul options and remote management features for RF diagnostics.

Standards and Regulatory Context

When specifying radar transmitters for municipal or industrial water, require both functional and cybersecurity evidence in procurement. Key standards and checks include:

  • Functional safety (SIL) for safety-instrumented functions (if the sensor is part of an interlock). Link to procurement clauses requiring IEC 61508 evidence.
  • Industrial cybersecurity: ISA/IEC 62443 at the component level — require signed firmware, role-based access, and component hardening. The ISA/IEC 62443 series is the accepted lifecycle and component-level standard for automation cybersecurity. (isa.org)
  • Radio/regulatory: country-specific spectrum and receiver/regulatory tests (e.g., EN 300 220 family for particular SRDs). Certified radio test reports reduce approval delays; see the TSÚ test report example for radio testing procedures.
  • Drinking‑water compatibility (NSF/ANSI 61) where parts are wetted on potable assets.
  • Hazardous-area approvals (ATEX/IECEx) when sensors or process circuits are installed in gas/dust zones.
  • IP / mechanical: require IP68 or equivalent for submerged installs and specify IK rating for harsh access locations; see IP68 protection rating.

For wastewater and city programs also check the EU Urban Wastewater Treatment Directive (UWWTD) and related national transpositions for monitoring and reporting obligations; planned updates and evaluations of the UWWTD have direct bearing on city telemetry requirements. (circular-cities-and-regions.ec.europa.eu)

Tip: Add a cybersecurity annex to tender documents that maps IEC 62443 component requirements to deliverables (signed firmware files, firmware-hash manifest, secure boot evidence, and a vulnerability disclosure contact). (isa.org)

Types of Radar Level Sensor

Radar platforms differ by waveform, frequency, and mechanical coupling. Map the options to your medium and geometry.

  • FMCW-style, mmWave modules (often sold under nanoradar technology or 60 GHz product names) — high resolution, excellent near-field discrimination.
  • Pulse radar — time-of-flight pulsed microwave for longer ranges and deep tanks.
  • Guided-wave radar — a probe/rod conducts the pulse to the surface (excellent where foam or vapour is severe, at the cost of a contact probe).
  • Microwave (general umbrella) — vendor term covering the above; check datasheets for explicit waveform and near‑zone specs.

See also our primer on time‑of‑flight level measurement for range math and uncertainty.

Frequency choice and beam control

Choose frequency to balance beam width, aiming, and interference rejection:

  • 26 GHz — broader beam, cost-effective for large‑aperture tanks.
  • 60 GHz — narrow beam and compact antennas; good compromise for most urban assets and many retrofits. 60 GHz radar sensor
  • Higher‑frequency mmWave (compact lens antennas) — narrowest beams, best at avoiding internal obstructions but sensitive to precise aiming.

If you retrofit into a nozzle or standpipe, confirm the manufacturer’s near‑zone and blocking-distance specs and prefer devices that provide live echo mapping and SNR diagnostics on commissioning.

System Components

A production radar level transmitter integrates:

  • Antenna (horn, lens or flush) — determines beam angle and buildup tolerance.
  • mmWave front-end (oscillator, mixer, LNA, ADC) — sets sensitivity and dynamic range.
  • DSP/MCU for FFT and echo‑tracking (echo-quality indexes improve diagnostics).
  • Firmware with false‑echo suppression and diagnostics; require OTA firmware update support and signed firmware.
  • Power options: loop‑powered 4–20 mA / HART or battery + LPWAN radio (LoRaWAN / NB‑IoT) for remote sites. See 4–20 mA/HART, LoRaWAN and NB‑IoT.
  • Mechanical process connections (flange, NPT, hygienic) and aiming brackets.

Component selection checklist:

  • Antenna beam angle at −3 dB and condensation-shedding features.
  • Near‑zone (blocking) and minimum measurable distance.
  • Power draw at target reporting interval and expected battery life for wireless variants.
  • Native protocol stacks vs gateway-dependence; prefer devices with local HART/Modbus/4–20 capability for critical assets and LPWAN for distributed, low-frequency telemetry.

How Radar Level Sensor is Installed / Measured / Calculated / Implemented: Step-by-Step

This section paraphrases a robust commissioning workflow used in municipal and research deployments.

  1. Define the duty (15–60 minutes): list medium, min/max level, foam/turbulence, temperature range, and any hazard class.
  2. Choose principle & frequency (15–30 minutes): FMCW for short/high-resolution needs; pulse for long range; use 60 GHz where nozzle space is tight.
  3. Engineer the nozzle/standpipe (30–90 minutes design; 1–2 hours onsite): verify clear aperture, wall thickness, and protrusions. Consider a short stilling well for extreme turbulence.
  4. Mount & aim (15–45 minutes onsite): aim the beam away from ladders and agitators; keep beam roughly normal to average surface.
  5. Power & network (15–60 minutes): wire 4–20 mA/HART or install battery + join LoRaWAN / NB‑IoT. For LoRaWAN, verify RF link to gateway and use regional parameters. (lora-alliance.org)
  6. Commission echo profile (15–30 minutes): run echo mapping, set near‑zone, enable false‑echo suppression; validate across partial fill/drain events.
  7. Integrate to SCADA integration (30–120 minutes): map tags, scale readings, map diagnostics to status bits and alarms.
  8. Acceptance proof (30–60 minutes): cross‑check against staff gauge, tape, or hydrostatic reference and attach acceptance evidence to the asset in CMMS.
  9. Document & train (30–120 minutes): as‑left settings, aiming photos, and a one‑page field SOP.

Each step should be recorded in the asset record with firmware hashes and configuration snapshots for future audits. For wireless networks, require a plan for spares and battery stewardship to keep service intervals predictable.

Maintenance and Performance Considerations

  • Visual inspections: schedule lens/horn inspections where scaling or misting is common; avoid hydrophobic treatments that alter beam shape.
  • Firmware and configuration control: lock write access and store signed configurations.
  • Diagnostics-driven maintenance: trend SNR and echo confidence to detect mis-aiming or condensation early.
  • Foam & turbulence: use a short stilling well or guided‑wave solution when persistent foam prevents reliable echoes.
  • Temperature cycling: re‑torque housings after the first freeze‑thaw season and verify seal integrity.
  • Wireless battery stewardship: balance update rate with payload size to meet battery life targets.

Troubleshooting quick reference

Symptom Likely cause First action
Intermittent dropouts Obstruction or gateway congestion Re‑aim, refresh echo map, check LPWAN duty cycle
Flat‑lined readings Near‑zone clipping or blocking distance Increase blocking distance; re‑span 4–20 mA
Noisy signal Heavy turbulencding well or narrower beam (60 GHz)
Shorter battery life Aggressive reporting rate or cold Reduce frequency; use high-capacity cells; insulate enclosure

Summary

When specified and commissioned correctly, a Radar Level Sensor gives reliable, low‑maintenance level telemetry across potable, storm and wastewater assets. For municipal and smart‑city programs, they reduce OPEX and improve data confidence for both operations and regulatory reporting. Vendor evidence (radio test reports, ingress ratings, and field datasheets) should be part of every procurement package; see the MERATCH device families and test documentation for examples.

Key takeaway — utilities & integrators: insist on signed firmware, echo‑mapping evidence, and a clear acceptance test (staff-gauge cross-check). Cybersecurity and radio conformity documentation speed procurement and deployment. (isa.org)

Pilot highlight — Danube River floodplain: in a research deployment of 12 NB‑IoT radar sensors the project achieved millimetre-level measurement accuracy and automated hourly telemetry to a custom flood-alert system, demonstrating how high-resolution radar sensors can form the backbone of a flood warning system. (Project summary in References.)

Frequently Asked Questions

  1. How is Radar Level Sensor installed in water management?

    • Install by defining duty, choosing frequency/principle, mounting and aiming, commissioning echo mapping, and integrating to SCADA; validate with a staff gauge and store signed configuration snapshots in the asset record.

  2. Which protocols ensure lowest TCO for mixed plants with legacy 4–20 mA loops and LPWAN backhauls?

    • Use loop‑powered 4–20 mA/HART for critical in‑plant control and parallel LPWAN (LoRaWAN / NB‑IoT) for remote telemetry and cloud reporting; gateways and protocol translators can bridge both. 4–20 mA/HART LoRaWAN NB‑IoT.

  3. Which nozzle/standpipe geometries most affect echo mapping in narrow shafts?

    • Small apertures, corrugations and protrusions create internal reflections; specify smooth short standpipes or use an 80/60 GHz narrow‑beam antenna to reduce false echoes.

  4. How do 60 GHz and 80 GHz beams compare in clarifiers with scum baffles and rotating scrapers?

    • Narrower beams (higher frequency mmWave) are better at avoiding internals; select 60 GHz whereh and cost is required and higher mmWave frequencies where aiming precision is achievable.

  5. What procurement clauses mandate IEC 62443 features and signed firmware?

    • Add an IEC 62443 component checklist requiring signed firmware images, secure boot, role‑based access, vulnerability response SLA and firmware-hash manifests as tender deliverables. (isa.org)

  6. How to model service intervals for battery‑powered wireless modules vs loop‑powered transmitters over a 10‑year TCO?

    • Model update rate, payload size, temperature derating of battery capacity, replacement labor cost, and gateway amortization. Use vendor battery-life figures and field-tested duty cycles as inputs (see datasheet examples).

References

Below are relevant MERATCH project references and short notes (real-world evidence you can cite in bids and proposals):

FLOPRES – Flash Flood Prediction System

Danube River Floodplain Monitoring

Bratislava Wastewater Management (BVS)

Residential Septic Tank Monitoring

BVS Bratislava – Podunajské Biskupice / Lafranconi Bridge

Practical callouts from pilots and datasheets

Callout — FLOPRES installation efficiency Two-person crews installed sensor + gateway stacks in under 20 minutes per site in hilly rural areas; this operational detail matters when estimating rollout CAPEX and team sizing. (FLOPRES project update in References.)

Callout — Product evidence MERATCH family documents show LoRa and NB‑IoT variants (MLLO2301 / MLNB2301) and EN radio test reports; for gateway decisions, use gateway factsheets (Kerlink iStation) and device datasheets for battery and IP ratings during procurement.

Author Bio

Ing. Peter Kovács — Technical freelance writer

Ing. Peter Kovács is a senior technical writer specialising in smart‑city infrastructure and municipal water management. He produces field‑tested commissioning protocols, procurement annexes, and vendor‑agnostic glossaries for city engineers, IoT integrators and procurement teams. Peter combines laboratory test interpretation, in‑field commissioning experience and standards mapping to produce practical, auditable content for public tenders and operations teams.