Chinese
Spanish
French
Russian
German
Portuguese
Indonesian
Thai
Vietnamese
Arabic
Direct Answer: What Does an Open Channel Radar Flow Meter Need?
An open channel radar flow meter needs more than a non-contact sensor: it needs a representative surface, a surveyed channel section, a stable level datum, documented velocity conversion, rigid mounting and a verified data path. Without those inputs, the station may display a flow number that cannot be defended during commissioning or later channel changes.
Use radar where floodwater, debris, sediment, corrosion or unsafe access make submerged measurement difficult. Confirm that low-flow and high-flow surfaces provide a usable return and that the mounting structure remains clear of the maximum water level and radar footprint.
Buyer Risk: Buying the Sensor Without the Hydraulic Scope
The largest error can come from channel geometry, datum, coefficient or mounting rather than the electronics. The RFQ should assign responsibility for survey, section configuration, bracket design, reference comparison, telemetry, maintenance access and re-verification after scour, deposition or civil work.
Project Background: Why Non-Contact Flow Monitoring Is Specified
River authorities, municipal drainage teams, irrigation operators and industrial utilities often need flow data at locations where conventional contact sensors create maintenance or safety problems. Flood debris can strike a submerged probe, sediment can bury it, corrosive effluent can shorten cable and housing life, and field personnel may not be able to enter the channel safely. Radar moves the velocity and level measurement above the water, reducing these particular exposure risks.
Non-contact does not mean installation-independent. Radar velocity is derived from the Doppler shift of microwave energy reflected by the moving surface. If the surface is mirror-smooth, covered with vegetation or foam, hidden by a bridge member, or dominated by standing waves unrelated to mean flow, the signal may not represent the section. The level channel measures distance to the surface, so an incorrect mounting datum directly changes wetted-area calculation.
The buyer is therefore purchasing a measurement station and a hydraulic model, not a standalone sensor. A complete scope includes the radar head, rigid bracket, surge protection, power system, RTU or gateway, cross-section survey, configuration, communication map, site acceptance and a process for updating geometry after civil or sediment changes.
How a Radar Flow Meter Sits in the Monitoring Architecture
The YEX-HY-RFMS-01 combines a 24 GHz velocity radar with a 76-81 GHz level radar. The velocity channel observes surface motion; the level channel supplies distance data. The controller uses the configured channel section and velocity relationship to calculate instantaneous discharge. RS485 Modbus RTU then exposes measured and calculated values to a PLC, RTU, SCADA system or IoT gateway.
For flood monitoring, the gateway can increase sampling or transmission frequency as level rises. For irrigation, the system can aggregate flow volume by operating period. For an industrial outfall, the flow value can be time-aligned with pH, conductivity, turbidity or COD data to calculate event loads. These functions belong in the data architecture and should not be assumed from the sensor alone.
Radar Flow Meter for Open Channels: Verified Technical Parameters
| Parameter | YEX-HY-RFMS-01 specification | Procurement check |
|---|---|---|
| Power supply | DC 10-30 V | Confirm cabinet voltage, cable drop, solar autonomy and modem peak load. |
| Maximum power | 1.3 W | Include controller, heater if any, RTU and communications in the station budget. |
| Velocity frequency | 24.00 GHz | Review aiming, surface return and interference at the proposed structure. |
| Velocity range | 0.1-20 m/s | Provide dry-weather, normal, warning and flood velocities. |
| Velocity accuracy / resolution | ±2% / 0.01 m/s | Define total flow uncertainty separately from the velocity channel. |
| Level frequency | 76-81 GHz | Check beam clearance, datum survey and lowest target condition. |
| Level range | 0.1-65 m | Confirm mounting height, maximum flood level and structural freeboard. |
| Distance accuracy / resolution | ±1 mm / 1 mm | Acceptance must include datum and still-water verification, not only display resolution. |
| Output | RS485 Modbus RTU | Request register map, units, data types, byte order and default settings. |
| Operating environment | -40 to +80 °C; 0-95% RH non-condensing | Specify enclosure condensation, lightning, wind, ice and cable protection. |
Cross-Section and Velocity Coefficient Decisions
The radar does not directly measure every point in the section. It observes a surface area and uses a configured relationship to mean velocity. For a simple stable channel, a surveyed trapezoidal or rectangular section may be adequate. For natural rivers, the section may need multiple surveyed points and periodic review. If sediment deposition, scour, vegetation or gate operation changes the section, an old configuration can produce a plausible but biased discharge.
Define who supplies the survey, which coordinate system and datum are used, how the section is entered, and which hydraulic levels are included. The velocity coefficient should be documented rather than hidden as an installer default. Commissioning should compare the online result with an agreed velocity-area survey at several flow conditions. A single comparison cannot demonstrate performance across the full range.
Store raw surface velocity and measured level with calculated flow. If only final discharge is archived, engineers cannot determine later whether a disagreement came from the radar return, level datum, section geometry or coefficient.
Mounting Design and Radar Footprint
A rigid bridge, pole or cantilever bracket is required. The structure must resist wind and vibration without changing sensor angle. The velocity head should point at a representative moving surface, not directly at a bank eddy, standing wave, gate jet or local obstruction. The level beam needs an unobstructed path to the water across the complete operating range.
Integrators should prepare a mounting drawing showing sensor coordinates, height, angle, beam footprint, channel banks, maximum water level and access platform. Consider cable drip loops, glands, surge protection and a safe method to reach the unit. If a road bridge is used, traffic permits and vibration should be part of the site review.
Commission the aiming under actual hydraulic conditions. A mechanically neat installation can still observe the wrong part of the surface. Record photographs and angle settings in the handover package so later maintenance does not change the geometry without authorization.
RS485 Modbus, RTU and SCADA Integration
Connect the RFMS-01 to the RTU using the ordered communication settings and protocol document. Confirm address, baud rate, parity, stop bits, function codes, register length, data type and byte order. Map velocity, level, instantaneous flow and cumulative flow as separate tags with engineering units. If configuration registers are writable, restrict access and log changes.
Use a communication-loss timer that marks data invalid rather than holding the last number indefinitely. The RTU should buffer data during network outages and preserve timestamps. For solar stations, sample and transmission rates can be different: the device may sample frequently while the modem uploads summarized and event data according to the power budget.
Alarm design should use persistence and rate-of-change logic appropriate to the application. A short reflection disturbance should not create a false flood alarm, but excessive filtering can hide a real rapid rise. Keep raw data available for tuning after the first wet season.
Systematic Application Scenarios
Flood-warning river crossing
Challenge: high velocity, debris and unsafe access during storms. System solution: mount RFMS-01 above the channel, connect to a solar RTU, and transmit level, surface velocity, discharge and station health. User value: continuous event data supports threshold warnings while maintenance stays out of the water.
Urban stormwater outfall
Challenge: intermittent flow, rapid level change and multiple reflections from concrete structures. System solution: select a straight unobstructed section, document the culvert geometry and use event-triggered high-frequency logging. User value: the utility can quantify event volume and compare capacity across storms.
Irrigation main canal
Challenge: gate changes and seasonal weed growth alter the rating relationship. System solution: position the radar away from gate turbulence, perform comparison surveys at several gate positions and schedule geometry inspections. User value: water allocation records become traceable to a documented section and coefficient.
Industrial wastewater channel
Challenge: corrosive liquid and solids increase contact-sensor maintenance. System solution: use non-contact radar and align flow data with online quality sensors in SCADA. User value: the plant can calculate discharge loads and investigate events without routinely retrieving a submerged flow probe.
Reservoir release channel
Challenge: a wide operating range produces different surface patterns. System solution: review the footprint at low and high release, preserve the raw variables and validate against gate or survey records. User value: operators gain an independent continuous trend and a documented method for reconciling differences.
Selection and RFQ Checklist
- Channel type, coordinates, photographs and access conditions
- Surveyed cross-section and datum
- Minimum, normal, warning and maximum levels
- Expected surface velocity and discharge range
- Foam, vegetation, ice, sediment, debris and wind conditions
- Mounting structure, height, angle and maximum flood clearance
- DC supply, solar design, cable length, grounding and surge protection
- PLC, RTU, SCADA or IoT gateway and required Modbus settings
- Sampling, buffering, transmission, alarm and time-synchronization requirements
- Reference survey, FAT, SAT, documentation, spares and training
Commissioning and Acceptance Boundaries
Factory acceptance should confirm the ordered model, supply range, communication, displayed units and supplied documentation. Site acceptance should verify structural alignment, level datum, surface return, section configuration, raw velocity, calculated flow, time stamps, alarms, communications and power-cycle recovery.
Define the comparison method and tolerance before installation. The acceptance document should state whether the criterion applies to velocity, level or final flow and under which hydraulic conditions. If the station is commissioned during only low flow, schedule a high-flow verification rather than claiming full-range validation.
Request a YexSensor Radar Flow Meter Review
Send the channel cross-section, mounting drawing, level and velocity range, surface conditions, power, telemetry and acceptance method. YexSensor can review whether RFMS-01 fits the measurement duty and identify missing engineering inputs.
- Cross-section file and level datum
- Low, normal and flood conditions
- Mounting height, angle and access
- RS485 Modbus and RTU requirements
- Quantity, destination, schedule and support scope
Send Your Project Requirements | Review YEX-HY-RFMS-01 specifications
FAQ
Q1. How does radar calculate open-channel discharge?
It measures surface velocity and water level, then applies the configured channel section and a validated surface-to-mean velocity relationship. Store raw level and velocity with calculated flow.
Q2. Can a radar flow meter work without a channel survey?
It can report raw variables, but defensible discharge normally needs reliable section geometry. Natural or sediment-prone channels require a survey and a recheck trigger.
Q3. What surface conditions can weaken the result?
Very smooth water, dense foam, ice, vegetation, standing waves, bank eddies and obstructions can reduce or bias the return. Provide photographs across expected conditions.
Q4. Where should the radar be mounted?
Use a rigid structure above a straight representative reach with unobstructed velocity and level views. Check maximum flood clearance, beam footprint and safe maintenance access.
Q5. Is Modbus RS485 automatically compatible with any RTU?
No. Confirm address, baud rate, parity, function code, registers, data type, byte order, units and fault behavior for the ordered revision.
Q6. How is radar different from a submerged Doppler meter?
Radar observes the moving surface without water contact; a submerged Doppler instrument measures acoustic returns in the water. Select from surface condition, depth, sediment, access and required range.
Q7. What should be included in the purchase scope?
Include the radar head, bracket, cable, surge protection, power, RTU or gateway, section configuration, protocol documents, reference comparison, commissioning and training.
Q8. When should channel geometry be rechecked?
Recheck after floods, dredging, sediment deposition, vegetation growth or civil changes and at an interval based on channel stability and consequence of error.
Q9. Can one station support flood alarms and volume reporting?
Yes, when sampling, buffering, alarm logic, time continuity and flow integration are designed for both. Define behavior during communication and power loss.
Q10. What should site acceptance prove?
Prove alignment, datum, raw velocity, level, configured section, calculated flow, units, timestamps, alarms, communication, power recovery and the agreed comparison method.
Summary
An open channel radar flow meter reduces submerged maintenance only when the hydraulic model and installation are engineered with the sensor. Confirm the surface, section, datum, mounting and velocity relationship, verify raw and calculated data through Modbus RS485 or the RTU, and include survey, telemetry, acceptance and re-verification responsibilities in the RFQ.
