What are the main applications of dataloggers?

Where a measurement history earns its keep

Data loggers are used in manufacturing, cold-chain monitoring, energy studies, building performance, environmental and water monitoring, agriculture, product testing and structural monitoring. A logger adds time to a measurement, making it possible to investigate when conditions changed and what happened around that change. Its sensor interfaces and inputs determine which applications it can support. One model will not cover every job.

1. Understand production and process behaviour

Record furnace temperatures, line pressure, tank level and machine states to compare batches, shifts and conditions before a fault. Choose Pt100 probes or thermocouples to match the range and installation. Pressure measurements can reveal which operating step coincides with a pressure loss. In temperature control and pressure control, logging the setpoint alongside the measured value makes the response easier to assess.

A PLC can run the machine while a logger provides an independent measurement history. SCADA can display and archive the data centrally. To investigate PID loop behaviour, align timestamps for the setpoint, measurement and control output. Recording and controlling are different functions. Some advanced loggers offer control outputs, but that capability must be checked separately.

2. Document storage and transport conditions

Cold rooms, refrigerators, warehouses and shipments use temperature histories, sometimes with relative humidity, to document conditions. The records help locate excursions outside the specified storage range. Analysis can compare those events with loading or door openings. Air temperature does not directly establish product core temperature or product condition. Probe placement and the product's own acceptance criteria matter when interpreting the record.

3. Compare energy use with useful output

A suitable measurement system can record current, voltage, active power and energy. A Hall-effect current sensor can supply a current channel, but current readings alone do not establish accurate energy consumption in kWh. AC power also depends on voltage, phase relationships and load behaviour. Use appropriate power measurement hardware or data from an energy analyser.

Compare shift consumption, idle operation and energy per unit produced. For example, 120 kWh for 600 units is 0.20 kWh per unit; 150 kWh for 600 units is 0.25 kWh per unit. The second period uses 25% more energy per unit. Operating conditions still need investigation before assigning a cause. These figures illustrate the calculation, rather than setting a performance target.

4. Investigate building comfort and HVAC operation

In building automation, suitable sensors can track room temperature, humidity, CO₂ and equipment states. The history helps identify overheating periods and unnecessary operating hours. Measurements across several locations reveal differences that a single thermostat may miss. Assess comfort alongside energy use. Direct sunlight, a doorway or a supply-air outlet can influence a probe's reading.

Choose records that answer the actual question

The application determines what to record together
Application Useful paired records Question to investigate
Cold roomTemperature and door stateDoes the change coincide with a door opening?
Production linePressure and machine stepDuring which step does pressure fall?
Energy studykWh and production countHas consumption per unit changed?
IrrigationSoil moisture and water deliveredHow does moisture respond after watering?

Two records changing together do not prove causation. They do provide a better starting point when timestamps and operating context are available. Select the measurement and logging intervals for the event of interest: a slow schedule can miss a brief pressure dip or temperature peak.

5. Monitor water, weather and growing conditions

Log water level, rainfall, air and soil temperature, soil moisture and, with suitable instrumentation, water-quality parameters. A flow meter provides flow information that can be used to assess water movement over time. Flow rate and total volume are different quantities. A total requires elapsed time and correct units, or the appropriate conversion for a pulse-output meter.

Field and greenhouse records support investigation of irrigation timing, local climate differences and seasonal change. For unattended sites, plan power, environmental protection and storage capacity together. Wireless communication or remote access can reduce collection visits. An internet link does not replace the need to check local recording capability.

6. Explain renewable-energy performance

Solar monitoring can combine irradiance, module temperature and electrical production from suitable measurement equipment. Compare production with weather conditions before interpreting a fall in output. Low power alone is not a fault diagnosis: cloud cover, temperature and operating state can affect it. An industrial IoT system can bring site records into a central platform. Verify units and scaling for values obtained through interfaces such as Modbus.

7. Test prototypes and investigate failures

Product development uses logging to track heating, battery voltage, temperatures under load and endurance tests. Retain test conditions, channel identity and event timing so repeated runs can be compared. Alongside measurement accuracy, consider channel synchronisation and sampling speed. Not every logger captures fast transients or vibration waveforms. Those tasks may require a high-speed acquisition or recording system with suitable bandwidth.

8. Follow structural and infrastructure changes

Bridges, dams and other structures can be instrumented to record strain, displacement, tilt, crack opening and vibration. Long-term movement and short dynamic events impose different requirements. A general-purpose temperature logger cannot cover all these measurements. Match the sensor interface, synchronisation and recording rate to the monitoring task.

Turn the application into a practical specification

Match industry requirements to channel count, input type, measurement range, recording duration and configuration options. For live monitoring, check update timing and alarm latency. Specify transfer and retention arrangements for a cloud platform or processing at the edge. Include backup power where continuity matters, sensors and software in the total cost, and calibration and connection checks in the maintenance plan.

Technical references: Onset — storage and transport monitoring · Campbell Scientific — environmental and soil measurements · Campbell Scientific — solar monitoring · Campbell Scientific — structural monitoring · HIOKI — testing and data acquisition