Environmental science has long wanted more measurement points than it could afford. The case for networks of many inexpensive stations in place of a few costly ones was made for the earth sciences by Hart and Martinez (2006), and early deployments of wireless motes for habitat monitoring showed both the promise and the fragility of the idea (Mainwaring et al., 2002). Commercial data loggers are dependable and well supported, but a price per unit that is reasonable for a research catchment with a handful of stations becomes prohibitive when the design calls for dozens of stations, or when the network is to be run by a water authority or university in a low-income region.

Open-source hardware has changed the arithmetic. Pearce (2012) argued that research equipment built from open designs and commodity parts could cost a small fraction of proprietary equivalents, and loggers were among the first instruments to which the approach was applied (Fisher and Gould, 2012). Several designs have since been described in enough detail to copy, among them the ALog family for field geoscience (Wickert, 2014; Wickert et al., 2019), the Cave Pearl logger assembled from hobbyist modules (Beddows and Mallon, 2018), and Arduino-based hydrological stations for data-scarce regions (Hund et al., 2016).

These projects have also exposed recurring difficulties, which reviews of low-cost sensing describe frankly (Mao et al., 2019; Chan et al., 2021). This article proposes a design method that takes those difficulties as its starting point. It describes a logger architecture and the reasoning behind each choice, and it is offered as a specification to be built and tested. No prototype results are reported, and none should be inferred.

Four lessons recur in the published accounts. The first concerns energy. A development board that draws tens of milliamperes continuously will exhaust a set of alkaline cells within days, and the long-running designs achieve their endurance by removing or bypassing voltage regulators, indicator lights and serial converters that the hobbyist board carries for convenience, and by cutting power to the memory card, which can otherwise dominate the sleep current (Beddows and Mallon, 2018). The second concerns time. The resonator on a microcontroller board is not a clock, and a network whose stations disagree about the time by minutes cannot resolve the passage of a flood wave or a weather front.

The third lesson concerns the analogue front end. Low-cost boards measure voltage against the supply rail or an internal reference of modest stability, so readings from resistive sensors drift with battery voltage and temperature unless the measurement is arranged to cancel the reference. The fourth concerns what happens after collection. Horsburgh et al. (2019) observe that the hardware is the easier half of a low-cost network, and that data without consistent identifiers, units and site metadata are of limited use. To these may be added the meteorological community's long-standing insistence that a measurement is defined by its siting, exposure and maintenance as much as by its sensor (WMO, 2018).

The method proceeds in six steps: write the energy budget, fix the core architecture, design the sensor interfaces, design the data path, prepare the release package, and plan verification. The resulting architecture is summarised in Figure 1, grouped into the four subsystems that the steps address, and the principal design decisions are collected in Table 1 with the reason for each.

A network multiplies every small weakness. Three practical matters deserve attention beyond the board itself. Enclosures and connectors fail more often than electronics, and a sealed housing with a desiccant, a pressure-equalising vent and gland-sealed cables is worth more than a refinement to the circuit. Each unit should carry a unique identifier in firmware and on its label, tied to a site register that records location, installation date, sensor serial numbers and every visit. And the people who will maintain the network should be able to assemble and repair a unit themselves, which argues for through-hole or large surface-mount parts where the choice exists and for a design that tolerates substitution. These considerations are organisational more than electronic, and they are the ones that reviews of low-cost networks single out as decisive (Mao et al., 2019).

The design described here is a proposal. It has not been fabricated, programmed or deployed in the course of this work, and nothing in the article should be read as a performance claim. The first thing a validation would need to show is whether the paper energy budget survives contact with real components, whose sleep currents vary between production batches and rise with temperature. The second is long-term timekeeping and data completeness over a season in the field, expressed as the fraction of scheduled records actually recovered. The third is the accuracy of the analogue channels against traceable references across the temperature range.

Some limits are inherent. A logger built from commodity parts depends on components that may be withdrawn or counterfeited, and a published bill of materials ages quickly. Low cost per unit does not mean low cost per data point once assembly time, calibration and site visits are counted, a caution raised by Chan et al. (2021). Open designs also carry no warranty or certification, which restricts their use where measurements have regulatory standing. The method is intended for research and operational screening networks, where transparency and repairability weigh heavily, and not as a replacement for certified instruments in compliance monitoring.

The open loggers already in the literature show that a capable instrument can be built from inexpensive parts, and they also show where such instruments usually disappoint. The method proposed here orders the design work so that energy, timing, analogue integrity, data handling and documentation are settled deliberately and in that sequence, with a verification plan written before the first unit goes into the ground. Whether a logger built this way meets its budget and keeps its data through a field season is for a build and trial to establish, and the release package is designed so that any group may carry out that trial and publish the result.

To be declared by the author(s) before publication.

To be declared by the author(s) before publication.