What this category covers
Data acquisition turns a set of sensors into a record. The hardware decides how many channels are captured, at what interval and with what resolution, while the software decides whether that record is still useful six months later when somebody actually needs to read it. Both halves belong in the specification, and treating the second as an afterthought is how sites end up with a large archive nobody consults.
Industrial loggers are distinguished from laboratory acquisition mainly by environment and autonomy. They run unattended, in a cabinet or outdoors, for weeks or months, and they have to keep their data when the power or the network fails. That single requirement reshapes the specification: memory depth, clock accuracy, battery behaviour and the way data is retrieved all matter more than the headline sample rate.
The recurring selection error is to choose the sample rate first. A phenomenon that changes slowly needs no more than an interval short enough to capture it, and buying a fast system for a slow process usually means paying for resolution, storage and complexity that the application never uses - while giving up the ruggedness and the autonomy the site actually needed.
Product types in data acquisition & monitoring
| Product type | What it does | Usually specified for |
| Data logger | Accepts one or more sensor inputs and stores readings against a real-time clock | Unattended recording over weeks or months, where the record has to survive without a network in place |
| Multi-channel data acquisition system | Samples many channels through shared conversion circuitry and passes them to a host | Laboratory and test-bench work where several signals have to be captured together and related to each other |
| Paperless recorder | Displays and stores trends locally, often with alarm outputs and a screen for an operator | Plant cabinets where someone should be able to see what is happening without opening a computer |
| Temperature and humidity logger | Records climate conditions with an internal or remote sensor | Storage, transport, cold chain and room monitoring, where a defensible record over time is the deliverable |
| Wireless data logger | Transmits readings over a radio link to a gateway or receiver | Retrofit work where cabling is impractical, and sites spread across an area rather than inside one cabinet |
| IoT sensor and gateway | Converts a physical measurement into a transmitted data point, with a gateway aggregating the devices | Distributed monitoring where the data has to reach a system rather than a person, subject to power and radio range |
| Remote monitoring system | Collects from several sites and presents them together, frequently with alarm notification | Assets that are unattended, where the value lies in knowing about a condition without visiting |
| Monitoring software | Stores, plots, compares and reports the collected records | Turning a growing set of readings into something a decision can be based on, rather than an archive |
Monitoring systems, industrial IoT devices and the accessories that complete an installation are listed under this category as well.
How to choose a data logger
There is rarely a single correct instrument for a duty, but there is always a
shortlist that can be justified and a set of answers that eliminates the rest. These
are the questions that decide it.
- The signal types to be captured: voltage, current, resistance, thermocouple, RTD, strain or digital, because the input determines the hardware long before the channel count does.
- The interval the phenomenon actually requires, derived from how fast it changes rather than from what the system can achieve.
- The period to be recorded, which together with the interval gives the memory and the power the installation needs.
- Autonomy: whether mains power is available, whether the unit has to survive an outage, and what it does with its data when the power returns.
- Channel count against per-channel rate, since a multiplexed system trades one for the other and the trade has to match the application.
- How the data is retrieved: a physical visit, a direct connection, or transmission to a system, each with a different cost and a different failure mode.
- The environment: ingress protection, operating temperature, cabinet or field mounting, and whether the unit is exposed to weather.
- Clock accuracy and the time base, because a record that cannot be aligned with another record loses much of its value in investigation.
- What consumes the data. A monitoring system with no defined reader, no reporting requirement and no owner is an archive rather than a measurement.
Working through the selection in order
- List the signals to be recorded, with the range and the resolution needed for each.
- Establish how fast the fastest signal actually changes, and set the interval from that rather than from the hardware capability.
- Work out the recording period required, and derive the memory and the power the installation needs from it.
- Decide where the unit sits and whether power and a network are available there.
- Choose between local storage and transmission, based on how often the site can be visited and what has to happen when an alarm occurs.
- Check the environment and the enclosure at the installation point.
- Confirm the time base and whether the record has to be aligned with another system or with a reference clock.
- Decide what reads the data and what report it has to produce, then confirm that the software can actually deliver it.
Comparing the technologies
| Approach | Best suited to | Limits | Record produced |
| Standalone logger with internal memory | Unattended sites where no network exists and the record is collected on a visit | Record length is set by interval against memory, and clock accuracy matters across a long deployment | A local record, retrieved later |
| Multi-channel system with shared conversion | Test benches and laboratories with many channels to be related to each other | Per-channel sample rate falls as channels increase, and wiring and grounding affect the result more than the electronics | A synchronised multi-channel record |
| Paperless recorder with local display | Plant cabinets where an operator should see the trend at a glance | Screen size and storage are sized for a cabinet installation rather than for analysis | A displayed and stored trend |
| Wireless and IoT sensing | Retrofit work, and dispersed points where cabling is not viable | Battery life, radio range and data cost set the limits, and the radio path has to be surveyed rather than assumed | A transmitted record |
| Remote monitoring platform | Several unattended assets that have to be watched from one place | The communication route becomes a single point of failure, and alarm behaviour has to be designed rather than defaulted | A centralised view with notification |
| Monitoring software | Making a long record readable and comparable over time | Needs a defined data model and an owner, or the records accumulate unread and the investment is wasted | Reporting and analysis |
Parameters to confirm before ordering
What is left after the technology is chosen is a list of values that only the
installation can supply. These are the ones that change the model, the price or the
lead time:
- The signals to be recorded, with the range and resolution required for each.
- The interval needed, and the total period the record has to cover.
- The number of channels, and whether they are all the same type.
- Power available at the installation point, and whether the unit has to run through an outage.
- The environment: indoor cabinet, outdoor, temperature range and exposure.
- How the data is retrieved, and whether it has to reach a system or can be collected locally.
- The alarm or notification requirement, and the action that follows it.
- The report or export format required, and any system the data has to feed.
- Whether the record has to be aligned with another system or to a traceable time source.
- Quantity, and whether the installation is a single point or a network of locations.
Figures are quoted, not assumed
Specifications vary by model and application, so no performance figure is stated on
this page. Where a parameter has not been documented for a particular model, the
product page says so rather than filling the gap with a plausible number. Send the
values above and we will return the ones the selected model actually holds.
Where these instruments are used