1. Define the measurement
Write the parameter, engineering unit, and duty cycle before you open a catalog. Turbidity for an outfall, volumetric water content at root depth, and wind for a mast boom are different instruments—even when they share a brand.
Capture environment constraints: immersion, fouling, temperature, power availability, and whether operators can visit for calibration.
2. Select the sensing element
Browse the sensing technologies catalog by domain: water & hydrology, weather & radiation, or soil & crop. Prefer parameter-specific probes with published status (Available, Configurable, In development) and OEM price bands.
Confirm the interface your platform already supports—Modbus RTU, SDI-12, RS-485, or 4–20 mA—before inventing a new radio path.
3. Choose integration
Your logger or RTU: cable the probe to an existing master and keep radio out of the critical path.
Unified probe bus: keep multiple elements on one field interface for maintenance simplicity.
Optional LoRaWAN kit: use a decoder-ready PS kit when coverage and battery life beat copper, and when named payload fields matter more than raw hex.
4. Commission and document
Record model, serial/lot, calibration date, install location, and the first verified reading against a reference. For LoRaWAN kits, add DevEUI, JoinEUI custody, and decoder version.
Sensors report process and environmental data; they do not replace regulatory compliance procedures.
FAQ
Should I start with LoRaWAN or with the probe?
Start with the measurement. Select the probe or sonde that matches the parameter and environment, then decide whether your logger, Modbus master, or a LoRaWAN kit carries the data.
When is a LoRaWAN kit the right choice?
When you want a turnkey wireless edge node with a documented decoder and do not already have a field logger or RTU for that measurement.
Can I mix probes and LoRaWAN kits on one site?
Yes. Many sites use Modbus sondes on a logger for water quality while using LoRaWAN kits for leak or weather nodes that need sparse coverage.