Call Phone +8618073152920 Hotline: +8618073152920
Call Phone +8618073152920
English
CONTACT US/ CONTACT US
Consumer hotline +8618073152920
Changsha Zoko Link Technology Co., Ltd.

Email:Arvin@niubol.com

WhatsApp:+8615367865107

Address:Room 102, District D, Houhu Industrial Park, Yuelu District, Changsha City, Hunan Province, China

Position:Home >> Blogs >> Product knowledge

Product knowledge

Water and Rainfall Telemetry: Recover Records After a Network Outage

Time:2026-02-23 09:43:49 Popularity:727

Water and rainfall telemetry must distinguish a failed connection from failed observation. If a remote station continues measuring during a network outage, those records should retain their original acquisition times when transferred later. If acquisition also stops, the missing interval must remain visible. A reconnecting modem alone cannot reconstruct water levels or rainfall timing that were never recorded.

Radar level sensor with bracket and mounting dimension drawing

Specify three intervals, not one reporting frequency

Define how often the station acquires a measurement, how often it saves a record and how often it attempts transmission. These intervals can differ. A radar polled frequently but saved only as an hourly final value will not preserve the level changes between those saves, even if the modem uploads successfully every hour.

For rainfall, establish whether the logger records individual tips, interval totals or only a cumulative counter. These formats retain different information. A counter difference may recover total rainfall across a communications gap, but it cannot recover the distribution within that gap unless more detailed local records also exist.

Interval or eventWhat to defineWhy it matters after an outage
AcquisitionSensor polling or pulse countingDetermines what was observed locally
RecordingSaved values, summaries and quality statesDetermines what can be recovered later
TransmissionNormal uploads, retries and event messagesDetermines when the receiving system can use a record
Clock correctionTime reference and treatment of adjustmentsPrevents an apparent gap or duplicate caused by a time change

A station specification should state all four behaviours explicitly. Storage size and modem generation are insufficient descriptions of a water and rainfall telemetry system because neither establishes which observations survive an interruption.

Radar level sensor cable connections and housing dimensions

Keep the water-level record independent of upload time

A NiuBoL radar water level sensor provides a distance measurement for a compatible RTU or data logger. Retain the distinction between the measured distance and the calculated water elevation. If an offset or reference height changes, record its effective time so delayed records are not converted using an unrelated new setting.

Use an acquisition timestamp or a clearly defined interval timestamp at the destination. Also retain arrival time where useful for operations. A level measured at 10:05 and uploaded at 14:00 belongs in the 10:05 observation history; it should not appear as a sudden live level change at 14:00.

When showing the latest condition, check its age. Historical backfill should not replace a newer valid observation on the live display. Conversely, the receiving system must not discard a delayed valid record merely because a more recent one has already arrived.

NiuBoL rain gauge and outdoor monitoring equipment

Protect rainfall counting through communications interruptions

With the NiuBoL NBL-W-RS rain gauge, select the actual pulse, voltage or RS485 configuration and the corresponding logger input. For a reed-switch version, confirm that counting continues while the communications process reconnects. The modem's workload must not prevent legitimate tips from being captured.

In an illustrative 0.2 mm-per-tip installation, a cumulative counter rising from 100 to 118 tips represents 3.6 mm. If only those two endpoints are available, the total is known under the stated counting assumptions, but the times of the 18 tips are not. Do not distribute the amount evenly across missing minutes and label that distribution observed rainfall.

A counter reset changes the problem. If the counter starts again during the gap and its previous total was not retained, ordinary subtraction is invalid. Test restart behaviour and record the reset event. Avoid treating a negative difference as negative rain or silently replacing it with zero.

Rain gauge funnel and tipping mechanism details

Match the hardware to the record that must survive

Field itemConfiguration parameterAcquisition requirement
Radar level configuration77-79 GHz; distance 0.15-65 m; RS485; DC 10-30 VConfirm the offered protocol, output definition and suitable range at high and low water
Radar sensor demandUp to 0.6 WAdd logger and modem loads; sensor demand does not size the station battery
NBL-W-RS rainfall configuration0.2 mm resolution; intensity range 0-4 mm/minVerify pulse factor and counting performance for the ordered version
Rain gauge temperature0-50 C operationDo not assume an unheated configuration measures frozen precipitation
Local historyCapacity depends on the selected RTU, record size and scheduleSpecify a required recoverable duration and demonstrate it

For devices offering RS485 Modbus RTU, verify the register map, data type, units and invalid-value handling at the logger. The physical interface does not define storage retention or backfill. A local sensor bus can function normally while the remote server receives nothing.

As a sizing example, one record per minute produces 2,880 records over 48 hours. The required bytes depend on the complete record format, indexing and implementation overhead. Multiply by the intended channels or packet structure as appropriate, then allow for the required retention and overwrite policy. A nominal memory-card size is not a tested retention guarantee.

Outdoor water level monitoring instrument beside a water body

Recover the backlog without counting it twice

Agree how the receiver identifies a record, such as a station identifier with a sequence number or an agreed timestamp-and-channel key. An interrupted acknowledgement can cause retransmission of a record that the server already stored. The receiving process must recognize that retry instead of adding the same rainfall increment twice.

Test recovery with live traffic still arriving. A long backlog should not prevent current station health and level information from reaching operators. Specify the priority and transfer method in the gateway configuration; do not assume every modem or server implements the same queue behaviour.

If the monitoring point also includes a flow sensor, preserve which values are instantaneous discharge and which are cumulative volume. Adding repeated cumulative totals is not a volume calculation. Backfilled records need the same quantity definitions as ordinary live records.

Solar-powered overhead monitoring installation beside a canal

Distinguish network loss from station power loss

A network-only test establishes recovery while acquisition remains powered. It says nothing about a depleted battery or a disconnected logger. Run a separate controlled restart test and verify the clock, rainfall counter, pending records and water-level settings afterwards.

Specify the response to a full history buffer. Whether the station overwrites old records, stops logging or raises an alarm affects recoverability. Demonstrate the configured behaviour with a suitable test arrangement rather than waiting for a prolonged field outage to discover it.

For remote installations, include the reconnecting modem in the power assessment. Repeated connection attempts can differ from steady transmission. Any strategy that switches equipment off must be checked against the need to keep counting rain and recording water levels.

Examples of outdoor rainfall monitoring installations

Run a recoverability test before accepting the station

  1. Establish a known sequence of water-level observations and rain-gauge test pulses.
  2. Interrupt the remote connection while local acquisition continues.
  3. Restore the link and compare local history with the receiver's recovered records.
  4. Repeat a transmission or interrupt an acknowledgement to check duplicate handling.
  5. Restart the station separately and inspect time, counters, settings and any unrecoverable gap.

Use the project's required duration, load and equipment configuration. A short bench test cannot prove an unlimited outage capability, but it can reveal timestamp, counting and retry errors before installation. Include the actual receiving endpoint rather than stopping at a modem connection indicator.

For a NiuBoL station review, provide the acquisition schedule, required recoverable outage duration, sensor interfaces and destination data format. Ask for the RTU and gateway configuration that meets those requirements, with storage and restart behaviour demonstrated as part of commissioning.

Solar-powered monitoring mast beside a water channel

Project Decision FAQ

Q1. Does a reconnected station prove that all records were recovered?

No. Compare the expected local records with the received history, including gaps and duplicate identifiers. A live connection only establishes that communication is currently available.

Q2. Can a cumulative rain counter recover a complete storm profile?

It may recover total tips between valid endpoints if no reset or counting loss occurred. It cannot recover their timing without tip times or interval records. Keep inferred distribution separate from observations.

Q3. Should old measurements trigger a live warning after backfill?

The receiver should distinguish historical events from the current condition. Define how delayed events are reviewed and whether notifications are retrospective. Do not silently present old data as a fresh live alarm.

Q4. How much local memory is enough?

Calculate it from the record format, recording interval and required recoverable duration, then test the implementation. Include overwrite behaviour and power-loss persistence; card capacity alone does not establish either.

Q5. Can any RS485 sensor be added later?

Only after checking electrical and protocol compatibility, logger support, power and the resulting record format. Adding channels can reduce retention or change transfer demand even when the bus connection is available.

Q6. What should the integration quotation identify?

List sensor versions, acquisition equipment, recoverable history duration, remote transport and endpoint work. Include the outage and restart tests so the quoted system is evaluated on recoverable observations, not just an upload demonstration.

Summary

Water and rainfall telemetry is useful during outages only when local observation, storage and later transfer are designed together. Preserve acquisition times, distinguish missing records from zero rainfall, and test both retries and station restarts. This gives operators a recoverable hydrological history rather than a connection that merely resumes displaying numbers.

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

Tell us your requirements, Let's discuss more about your project.we can do more.

Name*

Tel*

Email*

Company*

Country*

Message


online
Contacts
Email
Top
XWater and Rainfall Telemetry: Recover Records After a Network Outage-Product knowledge-Automatic Weather Stations_Industrial, Agricultural, Water & Environmental IoT Monitoring Solutions—NiuBoL

Screenshot, WhatsApp to identify the QR code

WhatsApp number:+8615367865107

(Click on WhatsApp to copy and add friends)

Open WhatsApp

The WhatsApp ID has been copied, please open WhatsApp to add consultation details!
WhatsApp