— Blogs —
—Products—
Consumer hotline +8618073152920 WhatsApp:+8615367865107
Address:Room 102, District D, Houhu Industrial Park, Yuelu District, Changsha City, Hunan Province, China
Product knowledge
Time:2026-02-20 11:19:12 Popularity:692
Drainage flow event monitoring should preserve both the peak discharge and the volume passing the measurement section over a defined event. They answer different questions. A short high flow can matter to surcharge investigation, while the integrated volume matters to storage or pumping assessment. One maximum value and a daily total cannot describe the full rise and recession of a storm response.

An event can be defined by rainfall, a pumping cycle or a specified discharge condition. Record the start and end rule, including any antecedent or recession period. Otherwise, two reports can disagree simply because they integrated different periods rather than because their instruments disagreed.
Keep rainfall timing distinct from the flow response. Inflow can be delayed, pumped intermittently or influenced by downstream water level. The end of local rainfall does not necessarily mark the end of the drainage event. If several monitoring points are compared, use a common clock and retain the observation time at each point.
The NiuBoL Doppler velocity meter provides velocity and level observations for an appropriate measurement arrangement. Discharge then depends on the wetted section and the relationship between sensed velocity and cross-sectional mean velocity. It does not measure pH, dissolved oxygen or another water-quality quantity without separate instrumentation.
| Event record | Why it matters | Check before use |
|---|---|---|
| Level and velocity | Show the hydraulic response and support discharge calculation | Matching observation times, depth reference and valid sensing conditions |
| Discharge | Shows rate through the defined section | Area relationship and mean-velocity conversion |
| Peak and peak time | Identify the largest recorded rate | Sampling window, averaging and missing intervals |
| Integrated volume | Describes water passing during the event | Event boundaries, integration method and direction convention |
| Validity and configuration history | Show where the record is incomplete or has changed | Faults, servicing, bed changes and parameter revisions |
Set the acquisition schedule around the rate of change that the investigation needs to capture. An upload every few minutes can still contain more frequent local records if the selected logger supports that arrangement. Conversely, a fast dashboard refresh cannot reconstruct a peak that the sensor or logger never recorded.

For a hypothetical twenty-minute event, suppose valid discharge values at zero, ten and twenty minutes are 0.1, 0.5 and 0.1 m3/s. Assuming linear change between those observations, trapezoidal integration gives 360 m3: two ten-minute intervals, each with a mean rate of 0.3 m3/s.
Multiplying the 0.5 m3/s peak by the full 1200 seconds would instead give 600 m3. That calculation incorrectly assumes the peak persisted throughout the event. Neither calculation establishes what occurred between sparse observations; the linear assumption must be appropriate to the available record. These numbers illustrate processing, not a measured NiuBoL project result.
Retain the original time series and method used to produce a total. Where the logger supplies a cumulative counter, compare increments over matching boundaries and check counter resets. Where the server integrates rates, document its time handling so the same volume is not counted once locally and again during historical upload.

For a partly full pipe, area changes with depth and the actual section geometry. Sediment reduces the available area and may also change the velocity distribution. A nominal pipe diameter alone does not describe a partly blocked measurement section.
When the pipe becomes full, its geometric area stops increasing, but the measurement still needs a valid velocity observation and suitable pressure conditions. Do not infer full-pipe performance merely because software can cap an area at the pipe diameter. Verify the offered sensor version, installation and calculation under the expected surcharge conditions.
Likewise, a low reading near an exposed probe is not necessarily a real low flow. A dry acoustic path, sediment covering the probe or insufficient scatter can make the velocity unavailable. Use a validity rule rather than silently treating loss of a usable signal as zero discharge.

The NiuBoL 0.03-5 m/s Doppler configuration is described as unidirectional. For a tidal outlet, downstream backwater or pump-related reversal, specify the required bidirectional version and demonstrate its signed output. Do not purchase the single-direction configuration and assume that software can recover an unmeasured reverse velocity.
If signed discharge is valid, keep outward, inward and net volume definitions separate. As an arithmetic example, 100 m3 outward and 30 m3 inward produce 70 m3 net outward transfer, while the sum of the absolute transfers is 130 m3. Calling both results total volume without a direction definition creates a reporting error.
A rising level with little measured velocity can reflect backwater, a local stagnant zone or a sensing problem. Check the hydraulic setting and instrument status before labeling it a blockage or illegal discharge. Flow observations can support an investigation; they do not establish pollutant identity or legal responsibility.

| NiuBoL Doppler item | Configuration value | Event check |
|---|---|---|
| Unidirectional velocity range | 0.03-5 m/s | Assess low-flow validity and expected peak speed; specify reversal separately |
| Level range | 0.03-5 m | Check installed datum and pressure conditions |
| Temperature range | -10 to 60 C; accuracy +/-1 C | Apply the conditions for the supplied configuration |
| Supply and output | DC 10-30 V; RS485 Modbus RTU | Verify acquisition continuity and the actual register map |
| Protection and housing | IP68; ABS | Inspect cable, vent path where fitted and access for cleaning |
The lower end of a range does not establish the minimum usable depth above a particular installed probe. Confirm submergence, geometry and installation limits for the delivered unit. A grid or protective bracket can also collect debris or alter local flow, so assess it hydraulically rather than adding it without review.

If the peak window is missing, report the observed peak as the largest valid recorded value, not the proven event maximum. If part of the volume period is unavailable, distinguish a measured partial total from an estimated complete total. Preserve the estimate method and interval instead of filling every missing value with zero.
For a project inquiry, send NiuBoL the pipe or channel section, expected level and speed, possible reversal, event definition and required recording schedule. Include access and power constraints. Request sensor and logger arrangements that can retain the event locally during a communications outage, with that recovery behaviour demonstrated rather than assumed.

No. It describes integrated transfer over the day, not the largest rate or its timing. Retain a suitable event time series and the window used for peak reporting.
No. Fixed full-pipe area is only one input. The velocity, pressure conditions, installation and calculation method must remain suitable for that condition.
No. Order and test a version that supports the required flow directions and signed output. The 0.03-5 m/s unidirectional configuration must not be assumed to provide reverse-flow records.
The observed maximum may be lower than the actual event maximum. Identify the gap and avoid certifying an unobserved peak. Any reconstructed result needs a separate stated method.
Compare them over the same boundaries, units and direction convention. Check resets, missing data and processing before judging the instrument. A difference can originate in record handling rather than sensing.
Provide section geometry, flow-direction requirements, expected conditions, event timescale, local storage needs and receiving equipment. A generic flowmeter quotation cannot establish whether a short storm response will be captured.
Drainage flow event monitoring needs a valid time series, defined event boundaries and an explicit direction convention. Preserve peak timing and integrated volume separately, and identify gaps or hydraulic states that limit the result. This makes the records useful for drainage and pumping investigations.
Prev:Wireless Water Quality Monitoring Faults: Sensor, Logger or Network?
Next:Doppler Flowmeter Accuracy: Velocity Error, Depth and Discharge Validation
Related recommendations
Sensors & Weather Stations Catalog
Agriculture Sensors and Weather Stations Catalog-NiuBoL.pdf
Weather Stations Catalog-NiuBoL.pdf
Agriculture Sensors Catalog-NiuBoL.pdf
Water Quality Sensor Catalog-NiuBoL.pdf
Related products
Combined air temperature and relative humidity sensor
TDR Soil Moisture & Temperature Sensor for irrigation| RS485 |4-20mA| NBL-S-THR
Soil pH sensor RS485 soil Testing instrument soil ph meter for agriculture |NBL-S-PH
Wind Speed sensor Output Modbus/RS485/Analog/0-5V/4-20mA
Tipping bucket rain gauge for weather monitoring auto rainfall sensor RS485/Outdoor/stainless steel
Pyranometer Solar Radiation Sensor 4-20mA/RS485
Screenshot, WhatsApp to identify the QR code
WhatsApp number:+8615367865107
(Click on WhatsApp to copy and add friends)