— 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:2025-06-15 22:18:09 Popularity:1609
A professional rain gauge should be specified by the rainfall record the project needs, not by resolution alone. State the accumulated depth, reporting interval, intensity calculation and missing-data rules. For NiuBoL tipping-bucket gauges, the NBL-W-RS records 0.2 mm increments and the NBL-W-DRS records 0.1 mm increments; neither increment is a complete statement of measurement accuracy.

A reservoir operator may need an hourly catchment input, an irrigation contractor a daily rainfall total, and an urban drainage engineer a short-interval storm record. These are different deliverables even when the same rain gauge supplies the observations. A quotation that says only "rainfall, RS485" leaves the receiving system's most important behavior undefined.
Write down which records must remain available after the display updates. A daily total alone cannot reconstruct the distribution of rain within a storm. A short-interval stream can support later aggregation only if the timestamps, interval boundaries and missing periods remain identifiable. Choose the recording arrangement together with the gauge rather than treating the logger as an interchangeable accessory.
| Specification | NBL-W-RS | NBL-W-DRS |
|---|---|---|
| Liquid-rainfall mechanism | Tipping bucket | Double tipping-bucket arrangement |
| Collector diameter | 200 +/-0.6 mm | 200 +/-0.6 mm |
| Rainfall increment | 0.2 mm; 6.28 mL | 0.1 mm; 3.14 mL |
| Intensity range | 0-4 mm/min | 0-4 mm/min |
| Accuracy condition | +/-4%, indoor static test at 2 mm/min | +/-4%, indoor static test at 2 mm/min |
| Output choices | Reed-contact switching, voltage or RS485 version | Reed-contact switching, voltage or RS485 version |
| Supply choices | 5 V DC or 12-24 V DC, according to configuration | 5 V DC or 12-24 V DC, according to configuration |
| Operating temperature | 0-50 degree C | 0-60 degree C |
| Standard cable | 5 m | 5 m |
The smaller DRS increment gives finer depth steps. It does not establish half the field error, and the quoted test condition does not describe every rainfall intensity or installation. Confirm the selected output and electrical requirements; the listed alternatives are not a promise that every interface is supplied simultaneously.

For a pulse-counting version, accumulated depth equals the accepted tip count multiplied by the configured increment. As an illustrative calculation, 25 tips at 0.2 mm per tip represent 5 mm. Entering 0.1 mm for that same gauge would report only 2.5 mm. This is a configuration error, not a calibration finding.
The same quantization matters when calculating intensity. One 0.2 mm tip assigned to a one-minute interval represents an interval-average rate of 12 mm/h. One 0.1 mm tip represents 6 mm/h over that interval. Neither calculation establishes the instantaneous rate at the moment of the tip. Specify whether the application uses fixed intervals or a time-between-tips calculation.

The first tip occurs after enough water has reached the mechanism. It is not necessarily the instant the first drop lands on the site. Light rain can begin before a tipping event, and water retained in the collector can affect event timing. A system that needs immediate wet/dry detection should state that requirement separately from accumulated depth.
Likewise, "rain has stopped" needs a defined rule. A receiving application might classify an event as finished after a specified period without additional observations, but that period is a project setting, not an inherent property of the bucket. Record the rule beside the rainfall series so users do not mistake processing decisions for direct measurements.

Specify the station time zone, day boundary and timestamp meaning. A timestamp may identify an interval's beginning or end; mixing those conventions shifts a storm between records. For cross-site comparisons, use one documented convention and retain enough timing information to reconcile the records.
Ask whether an RS485 rainfall value is cumulative, interval-based or resettable, and how a reset or power interruption appears. Use the register definition for the supplied version. Do not subtract successive cumulative values without first checking reset behavior. A negative difference after a reset is not negative rainfall, and a missing response is not a dry interval.

A reed-contact version needs a suitable counting input and verified contact handling. A voltage version needs the correct analog input and scaling. An RS485 version needs its communication settings, register map, units and update behavior established before integration with a PLC, RTU or data logger. Confirm Modbus RTU for the ordered digital version rather than inferring a protocol from the RS485 label alone.
The gauge measures rainfall; a communication gateway moves the records. Cellular coverage, server storage and alarm logic belong to the complete station design. Test the saved series at the intended receiving system, not just a live number on a local screen.

For irrigation, combine rainfall with root-zone observations and the irrigation plan. Gauge depth is not automatically effective rainfall retained by the crop. For drainage, choose intervals that support the analysis and retain the storm sequence; a daily sum can hide a short burst. For reservoir work, review spatial coverage rather than assuming one point represents an entire catchment.
Research projects should document instrument changes, recording rules and interruptions because they can affect comparisons over time. These applications justify different recording arrangements, not unsupported claims that one gauge predicts flooding, measures soil moisture or identifies rainwater chemistry. The precipitation sensor types comparison explains when a different measurement method is needed.

Check a known sequence of input events through the complete acquisition path. Verify the increment, count, timestamps and exported interval totals. Test a day-boundary transition and an intentional communication gap. For a cumulative interface, include the specified reset behavior. Keep these data-handling checks separate from a controlled water-delivery calibration test.
For the latter, use the appropriate documented procedure and controlled delivery conditions; an arbitrary pour does not establish the published accuracy. Collector cleanliness, leveling and drainage still matter in service. The rain-gauge maintenance checklist covers those inspections without replacing the project recording test.

Request the exact gauge model, increment, output version, cable, acquisition channel and required records. State whether the price includes a logger, remote communication, mounting, configuration and acceptance work. A sensor-only quotation cannot be compared directly with a complete recording station. No fixed system price can be inferred from the rainfall increment.
Send NiuBoL the intended use, expected rainfall conditions and an example of the desired exported record. Include the receiving PLC or logger and any required reporting intervals. This gives the supplier enough information to separate the sensor selection from the recording and communication work.

No. Resolution describes the rainfall increment. Accuracy is a separate specification with test conditions, while field performance also depends on exposure, collection and maintenance.
Not on their own. A daily total does not preserve when rain fell within that day. Retain an appropriate short-interval or event record if the analysis needs storm timing.
No. Mark the gap as unavailable until the acquisition and recording behavior is resolved. A confirmed valid zero and a missing observation have different meanings.
Not by virtue of that interface. Remote reporting requires compatible acquisition and communication equipment, its power supply and a receiving system.
Demonstrate both the chosen measurement configuration and the final saved record. Check depth scaling, interval boundaries, reset behavior and missing-data handling before approving repeat orders.
NBL-W-ARS-Tipping-bucket-rain-gauge-instruction-manual.pdf
NBL-W-RS-Rain-sensors-instruction-manual-V4.0.pdf
NBL-W-DRS-Double-Tipping-Bucket-Rain-Sensor-Instruction-Manual.pdf
Specify a professional rain gauge together with the record it must deliver. Keep depth resolution, accuracy and timing rules distinct. A verified acquisition path and usable rainfall series make the RS or DRS selection meaningful for irrigation, drainage and hydrological projects.
Prev:Multifunction Weather Station: Choose the Channels Your Project Uses
Next:Compact Weather Sensor: When to Separate Measurement Positions
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)