Automatic Rainfall Monitoring System: Totals, Timing and Data Checks

An automatic rainfall monitoring system must preserve rainfall amount and its timing from the gauge to the final report. A correct daily total is not enough for a project that needs short-duration storm information, while a fast radio connection cannot repair missed tipping-bucket pulses. For agricultural and water-management networks, start by defining which totals and time windows will drive decisions.

Decide what the rainfall record must answer

An irrigation operator may need the rainfall since the previous watering cycle, together with soil moisture and crop conditions. A catchment operator may need synchronized short-interval rainfall from several locations, paired with river or reservoir levels. Both use rainfall data, but their logging intervals, outage handling and maintenance priorities can differ.

Rainfall depth is an accumulated amount in mm. Rainfall intensity is a rate, normally expressed in mm/h or mm/min, calculated over a defined interval. A rain-presence switch only indicates a wet or precipitation event state; it cannot substitute for a quantitative gauge when the application needs water depth. Label these quantities separately in the PLC, RTU and reporting database.

With a 0.2 mm tipping bucket, 25 valid tips represent 5 mm of rainfall. If those tips occur in five minutes, the average intensity over that interval is 60 mm/h. The same 25 tips over an hour represent 5 mm/h. Saving only an hourly total removes information that may be important for a short storm, even though the total itself remains correct.

Match rainfall resolution to the reporting task

The NBL-W-RS stainless steel tipping bucket is an option for liquid rainfall measurement. The NBL-W-DRS provides finer nominal bucket increments, while the NBL-W-PRS estimates rainfall from impacts on a piezoelectric sensing surface. Select the measurement principle for the exposure and record requirement, not simply the smallest displayed decimal.

The two bucket gauges have the same stated percentage accuracy under their specified test condition. Changing from 0.2 mm to 0.1 mm increments therefore does not, by itself, halve measurement error. At light rainfall rates, a smaller increment can improve the granularity of the time series, but funnel exposure, leveling and water losses still affect the result.

Choose between pulse counting and serial acquisition

A pulse-input logger must count each valid switch closure and apply the configured mm-per-tip factor. Check input compatibility, contact filtering and whether pulses are captured while the processor is sleeping. An excessive debounce interval can reject real tips; inadequate filtering can count switch bounce more than once. Test the complete input circuit rather than only watching the bucket move.

An RS485 gauge transfers numerical data through a serial interface. With Modbus RTU, check the address, baud rate, register meaning and scaling. For the NBL-W-RS rainfall example, a raw value of decimal 26 represents 2.6 mm. It is not a count to multiply by the 0.2 mm bucket factor again. Decode the received quantity before performing interval calculations.

The NBL-W-PRS offers cumulative and read-and-clear data modes. In read-and-clear operation, one reader can consume the increment before another reader receives it. Give one logger ownership of that channel and distribute its records upstream, or choose an appropriate cumulative configuration. Do not allow an engineering laptop and the production logger to poll independently without checking the effect.

Design the automatic rainfall monitoring system around time

A practical acquisition path is gauge to pulse input or RS485, then local data logger, then the selected telemetry link and server. The logger should retain the observation time and station identifier. A 4G connection or another radio link transports the record; it does not establish the measurement's time window or automatically supply local storage.

For cumulative readings, calculate each interval from successive totals only when the counter continuity is known. If the counter decreases, investigate restart, reset or rollover before using the difference. Preserve the preceding value and mark the affected interval. Treating a reset as negative rain or silently clipping it to zero creates a misleading record.

Set one time basis across the network and define how daily boundaries are handled. A five-minute total received late must retain its original observation interval. When a link reconnects, de-duplicate replayed records by station and time instead of adding them to the latest interval. Missing data must remain distinguishable from measured zero rainfall.

One daily statistic may be useful for irrigation summaries, while short-interval totals serve storm analysis. Calculate both from an adequate underlying series rather than storing only the coarsest result. Keep event timestamps where the application needs onset or inter-tip intensity, and check how the logger handles an incomplete bucket at a reporting boundary.

Install for rainfall exposure, then test the measuring chain

Choose an open, accessible location where roofs, foliage and brackets do not intercept rainfall or direct splash into the collector. Review the surrounding exposure as vegetation grows. A mounting height used at one project is not automatically appropriate to another; follow the project's observation requirements and account for wind exposure, access and flood level.

For a tipping bucket, level the base with its bubble and recheck it after tightening the fixings. Release transport restraints before the functional test. Keep the funnel and drain path clear, and confirm that the collected water reaches the bucket without leaking past the measuring path. A dual-bucket mechanism still needs inspection and cleaning; it does not make a blocked funnel harmless.

For the PRS, use a stable mount rather than a flexible side arm that moves with the wind. Impact-based measurements can be affected by mechanical disturbance. Avoid splashback and nearby vibration sources, secure the cables and follow the horizontal mounting arrangement. Its low-temperature operating rating does not establish accurate measurement of snow water equivalent.

Acceptance tests that reveal rainfall errors

Start with a dry inspection and an input test, then perform a controlled water test for the bucket instrument. Record the delivered volume, duration, initial counter, final counter and collector size. Pouring an unmeasured bottle rapidly into the funnel can show that something moves, but it is not an accuracy check at a defined rainfall intensity.

For the nominal 200 mm collector diameter, 1 mm of rainfall corresponds to approximately 31.4 ml. A 314 ml test volume therefore represents about 10 mm before allowance for test setup and residual water. Use a suitable controlled delivery method and the required test rate; account for the initial bucket position and retain the individual test results rather than adjusting a calibration screw after one uncontrolled pour.

Next, interrupt telemetry while the gauge remains operational. Confirm that locally recorded increments arrive once, in the correct time intervals, after reconnection. Test a logger restart separately from a sensor restart. This reveals whether pulse counts, cumulative registers and pending transmissions survive each type of interruption.

Inspection frequency should follow local debris, insect activity and access conditions. A zero trace through a nearby storm calls for checking the funnel, mechanism, wiring and recorder. A weather map alone cannot prove a local fault, but it can identify a station that needs inspection. Record maintenance times so cleaning and test water are not mistaken for natural rain.

Use rainfall with the right companion measurements

In irrigation control, measured rain is not identical to water retained in the root zone. Combine rainfall with representative soil moisture and the irrigation plan. A short intense shower on runoff-prone soil may justify a different response from prolonged gentle rainfall with the same total. Test rain-pause and restart behavior before unattended valve operation.

For a reservoir catchment, place gauges to represent the relevant terrain and rainfall differences, and pair the series with water-level or inflow observations. A single station does not measure catchment-average rainfall. Flood forecasts and gate decisions require hydrological analysis and authorized operating procedures, not a universal alarm threshold copied into the rain gauge.

For a remote agricultural network, separate sensor demand from modem and logger consumption. Battery capacity and panel size depend on actual load, winter solar availability, battery temperature and the required reserve period. Specify stored-record capacity in days at the intended interval, not merely as a large memory number without a record-size calculation.

Project Decision FAQ

Q1. Does an RS485 rain gauge connect directly to a cloud dashboard?

No. It needs a compatible logger or gateway to read and forward the measurements. Define who calculates interval totals, stores outage data and publishes the records. Those functions must be configured and tested at the logger or server level.

Q2. Is 0.01 mm resolution necessarily more accurate than a 0.2 mm bucket?

No. Resolution describes numerical increments. The PRS daily-total accuracy and a bucket's accuracy at a defined test rate describe different performance conditions. Compare the required reporting interval and field exposure, then validate candidate instruments against an appropriate reference.

Q3. Can the standard bucket gauge remain operational in freezing weather?

The listed RS and DRS configurations are for liquid precipitation and have operating ranges starting at 0 C. Frozen water can prevent collection and tipping. A project requiring winter precipitation needs a specifically evaluated heated or other suitable precipitation instrument, with its power and measurement limitations included.

Q4. Why do the local total and the server total differ?

Check scaling, daily reset time, duplicate replay, missed pulses and whether the server summed cumulative readings instead of interval increments. For read-and-clear devices, check for a second reader. Compare raw samples and timestamps before assuming that the gauge is miscalibrated.

Q5. What should be included in a rainfall station quotation?

Specify gauge type, required reporting intervals, output, cable route, power availability and communication coverage. Include the required offline recording period, platform interface and field acceptance test. Civil works, recurring network fees and calibration services should be identified separately from the sensor price.

Summary

An automatic rainfall monitoring system is useful when its totals remain traceable through acquisition, outages and reporting. Match the gauge to precipitation conditions and match the logger to the time series needed by the project. NiuBoL can review the station layout and acquisition requirements for a suitable rainfall sensor and monitoring configuration.

Rainfall sensor technical documents

The downloads below cover the named ARS, RS and PRS variants. Match the model and output version to the installed instrument before using wiring or register information.

NBL-W-ARS-Tipping-bucket-rain-gauge-instruction-manual.pdf

NBL-W-RS-Rain-sensors-instruction-manual-V4.0.pdf

NBL-W-PRS-Piezoelectric-Rain-Sensor-Operator's-Manual.pdf