— 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-04-08 11:19:57 Popularity:665
Quick Answer: Water environment monitoring architecture connects a defined measurement point to a usable server record. The sensor measures, the data logger polls and timestamps, the telemetry link transports, and the receiving system validates and stores. Specify each interface separately. An RS485 connection alone does not establish correct units, reliable outage recovery or a complete alarm service.

A river network may combine radar level, surface velocity, rainfall and immersed water quality probes at several locations. The first integration task is assigning an identity to each observation. Keep station, instrument, parameter, unit and measurement time together. A database field called "value" without these attributes cannot distinguish a 1.2 m distance from a 1.2 m/s velocity.
Also distinguish the directly measured quantity from a calculation. A radar initially measures surface distance; water-surface elevation needs a reference. Discharge needs hydraulic relationships as well as geometry. The server should not label all three as direct level-sensor outputs. Store the configuration revision used for a derived value so later changes can be interpreted.
For the field geometry and hydraulic checks, use the separate non-contact river flow monitoring guide. The architecture decision here is how those observations retain their meaning as they pass through acquisition, communications and storage.

A hydrological data logger can perform local engineering conversions, or a server can calculate derived channels from transmitted measurements. Both arrangements can work. Problems arise when both apply the same correction, or neither does. Identify the owner of unit scaling, datum subtraction, averaging and flow conversion before configuring the receiver.
| Layer | Defined responsibility | Interface check |
|---|---|---|
| Sensor | Measurement, compensation and instrument status | Exact model, units, valid range and register format |
| Logger or RTU | Polling, timestamping, local calculations and configured storage | Acquisition schedule, calculation ownership and quality flags |
| Telemetry gateway | Transport to the selected destination | Network availability, acknowledgement and supported security configuration |
| Receiving service | Record validation, duplicate handling and durable storage | Station identity, measurement time, units and version handling |
| Operator application | Trends, data-age indication and defined notifications | Current condition distinguished from delayed or invalid data |
Not every project requires a separate physical box for every layer. A logger may include a modem, while another installation uses an external gateway. The allocation of functions still needs to be explicit. A supplied enclosure or integrated antenna is not evidence that every storage, encryption or notification function has been included.

For each RS485 Modbus RTU instrument, record the address, baud rate, parity, function code, register address, data type and scale. Establish whether a documented register number is an address or a one-based reference. A valid reply proves that communication occurred; it does not prove that the PLC interpreted the number correctly.
For example, an unsigned register containing 1234 with a 0.01 scale represents 12.34 engineering units. Applying a 0.1 scale produces 123.4 while the response remains electrically valid. This is an illustrative decoding example, not a register definition for a particular NiuBoL model. Compare the decoded value with the instrument's known test condition before expanding the bus.
Check signed values and multi-register byte order where relevant. Do not assume all water probes share one map because the cable colors or connector look alike. Configure instruments individually before connecting units with potentially identical default addresses. Select termination, shielding and isolation for the actual cable route and receiving hardware rather than claiming one distance for every field network.

Modbus RTU requests on one ordinary master-controlled bus are sequential. If eight probes each require an illustrative 0.25 seconds for a successful request and response, the sweep already takes two seconds before retries and processing. One unresponsive instrument with several long timeouts can stretch that substantially. A one-second server chart does not mean every probe produced a fresh one-second observation.
Set response timeouts using actual instrument behavior. Separate fast stage channels from slow analytical channels when one schedule cannot satisfy both. Store the acquisition time for each channel, rather than assigning a single upload time to every number. If readings are averaged, retain the averaging interval and distinguish the mean from an instantaneous sample.
Test a disconnected instrument while the remaining channels are operating. Verify that the failed channel is flagged and does not prevent necessary observations elsewhere. A displayed last value may be useful for context, but its age must remain visible. Reusing it as a fresh observation creates false continuity even when every transmitted packet arrives successfully.

The NiuBoL integrated radar flow configuration combines surface velocity and level ranging. Its 0.1-65 m distance range applies to ranging, not to the complete flow-monitoring installation height. Water-quality probes connected to the same station have different immersion and temperature conditions. The following values describe components, not a universal station specification.
| Component example | Electrical and measurement limits | Architecture consequence |
|---|---|---|
| Integrated non-contact radar flowmeter | 10-30 VDC; maximum 1.3 W; RS485 Modbus RTU; velocity 0.1-20 m/s, +/-2%; distance 0.1-65 m, +/-1 mm; operating height 0-20 m | Preserve velocity, distance and calculated flow as distinct channels; installed discharge uncertainty is separate |
| Radar environment and cable | -40 to +80 degrees C; 0-95% RH, non-condensing; 5 m plug-in cable | Confirm enclosure protection and cable-jacket requirements for the ordered assembly; do not assign the same rating to the whole station |
| NBL-WQ-COD-408-S | 12-24 VDC; 0.4 W measuring and 2 W cleaning at 12 V; RS485 Modbus RTU, optional 4-20 mA | Allow for cleaning demand and identify whether the analog output is actually ordered |
| COD probe installation | 0-60 degrees C; pressure at or below 0.2 MPa; IP68; 316L housing; standard 5 m cable | Apply the mounting-depth restriction separately; IP68 alone does not establish unlimited depth or chemical compatibility |
The radar's velocity accuracy term does not certify calculated river discharge. Likewise, an optional analog COD output does not create native Ethernet or a cellular connection. These distinctions prevent a component specification from becoming an unsupported system acceptance promise.

A remote river monitoring network needs a clear answer when the mobile link disappears: are observations retained locally, for how long, and how are they recovered? Confirm these functions for the selected logger and firmware. A modem reconnecting is not the same as historical data being recovered.
Use a stable record identity, such as station plus channel plus measurement timestamp and sequence information. The receiving service should tolerate replay without counting the same observation twice. Keep receipt time separately. A record measured at 10:05 and delivered at 10:40 should remain a 10:05 observation, not create a new event at 10:40.
For telemetry outage recovery testing, interrupt the network while acquisition continues, restore it, and compare the recovered interval against local records. Check missing points, duplicates, ordering and the handling of old alarms. If storage fills, define which records are retained and how the resulting gap is reported. Do not describe storage capacity or automatic replay as standard unless the supplied equipment supports them.

A high-water alarm, a failed probe and an overdue upload are different conditions. Assign separate rules and recipients. During a communications outage, a server can detect absent telemetry but may not know the present water level. Displaying a green water-condition indicator from yesterday's reading would misrepresent that uncertainty.
A floating carrier adds its own checks: power state, probe immersion and mooring condition. The buoy photographs illustrate a mounting arrangement; they do not establish flood survivability, a specific number of reserve days or complete river coverage. Confirm the sensor set and transmission equipment actually fitted.
For flood warning duties, establish who evaluates the observations and what happens if the receiving system is unavailable. Notification delivery and any external warning equipment require their own integration tests. Purchasing level and rainfall sensors does not by itself commission an operational public-warning service.

Add continuous loads, scheduled loads and startup peaks separately. As an illustration, a radar operating at its 1.3 W maximum for 24 hours contributes 31.2 Wh/day. Four hypothetical 0.2 W probes add 19.2 Wh/day, giving 50.4 Wh/day before the logger, modem, cleaning, conversion losses or heating. This is a load calculation, not a complete NiuBoL station configuration.
For the COD example, do not add 2 W of cleaning continuously unless it actually operates continuously. Model the additional consumption above its 0.4 W measuring state for the scheduled cleaning duration, while checking that the supply can carry the 2 W cleaning load. Account for voltage drop when multiple devices switch together.
Battery reserve needs usable energy at site temperature, allowed discharge, aging and system losses. Panel sizing needs local seasonal solar availability and recovery after a low-light period. Neither a 20 Ah battery label nor a low-power probe establishes a fixed number of autonomous days for every installation.

Commission one channel from a known input through the logger to the final server unit. Then test sensor disconnection, power restart, network loss and restoration. For a counter or cumulative flow value, verify whether restart resets it and whether the server avoids inventing a negative volume at that boundary.
Include account access and supported transport security in the receiving-system test. Do not expose serial devices directly to the public network as a substitute for a managed gateway. For quotation, send NiuBoL the channel list, polling requirements, destination interface, outage-storage requirement and measured load profile. These define a meaningful integration scope without assuming every station uses the same hardware.

No. A compatible master must acquire and interpret the registers, and a logger or gateway must transport records using the destination's supported interface.
Not when acquisition times differ or historical records are replayed. Retain measurement and receipt times separately, together with any averaging interval.
It may remain available for reference, but should be marked stale or invalid for current decisions. Do not silently present it as a new measurement or replace the failure with zero.
Disconnect the network during acquisition, restore it and reconcile local and server records. Test completeness, duplicates, timestamps and delayed notifications for the supplied logger version.
No. Flow depends on section geometry and the relationship between observed and mean velocity. Those contributions need site validation beyond the distance channel's specification.
Specify acquisition, storage, gateway, destination setup, power, mounting and commissioning responsibilities. Identify optional functions and acceptance tests so competing quotations cover the same deliverable.
Water environment monitoring architecture is successful when a valid observation remains identifiable, correctly scaled and correctly timed at the receiving system. Define those contracts before selecting the NiuBoL sensor, hydrological data logger and telemetry arrangement, then verify them under both normal operation and deliberate faults.
Prev:Hydrological and Water Quality Monitoring: Flow and Load
Next:Agricultural Monitoring Zone Layout: Where to Share Weather, Soil and Crop Observations
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)