The Measurement Chain (DAQ Components)

By James McNally | Measurements

The Measurement Chain

I like to look at a data acquisition system as a measurement chain.

Each link in the chain is responsible for taking some information and transforming it in some way. Why a chain? Every link has a responsibility to maintain the quality of the stage before as far as possible. One strong link cannot make up for weak links.

For example, if your sensor is only accurate to 1V – the best DAQ card in the world won’t make it good to 100mV so you must consider it as a holistic system.

This article lays out the components of a data acquisition system and how they affect the quality of the measurement chain.

Concerns and Specifications

With that in mind you must make sure that each stage can maintain the desired:

  • accuracy,
  • repeatability,
  • stability,
  • speed,
  • and precision.

I will talk in detail about these in a future article. As with all things though, the better you need, the more you pay! But equally, there is no need in spending money on a DAQ card with 10x the precision of your sensor so we can use this to ensure we don’t overspecify as well as underspecify the system.

The Links
(Data Acquisition Components)


The sensors are where the physical phenomenon is first turned into something electrical. There are too many types to go into detail here but the key concerns tend to be accuracy, stability and repeatability since there is no digitisation yet (normally, I expect this will be more common going forward).

As well as the electrical characteristics, the mechanical solution must also be considered. For example how you mount temperature probes or strain gauges can make a big difference in how effective they are.

Signal Conditioning

Signal conditioning is present in all these systems, but perhaps less obvious in some. Signal conditioning is electronic circuitry whose purpose is to ensure that the signal we get from the sensor is suitable for input to an analogue to digital converter. Typical examples include:

  • Sensor Specific Conditioning: For example providing power to a piezoelectric sensor or completing a Wheatstone bridge for a strain gauge.
  • Protection: What happens if you connect a sensor to the wrong lines? Or if your sensor uses a different ground reference? Protection circuitry can provide isolation to reduce grounding issues and avoid damage to more sensitive components when problems occur.
  • Filtering: Removing noise from the signal that might cause issues. Examples might be power line filters to remove 50/60Hz noise or anti-aliasing filters which remove high-frequencies that can interfere with our signal during the conversion process.
  • Amplification: The conversion process is generally optimised for a signal in the 2-15V range. Small signals need boosting to make full use of the converter’s range (and large signals may need attenuating to avoid damage).

Signal conditioning concerns tend to depend on the sensors. We are still in the analogue domain so generally, the concern is accuracy, repeatability and stability. A concern can also be frequency response at this stage, especially with filters. Does it treat different frequencies in the same way? If not, how will that affect our measurements?

Analogue to Digital Converter (ADC)

The ADC is where we convert from the analogue to digital domain. It will sample the analogue signal at specific intervals so that a computer can use the data further. There are a number of key specifications here:

  • Sample Rate: How fast can we take in samples. This directly correlates to the frequencies we can measure (for a good signal you want to sample 5-10x the frequency of interest).
  • Resolution: How small a change can we detect. Commonly we have 16 or 24-bit converters which give approx. 65k and 16M levels we can capture in the range of the input. We need a good enough resolution to capture the smallest change we want to detect.
  • Noise: This can be expressed in a number of ways but essentially there will always be some background noise captured and different converters have different noise floors which affect the dynamic range it can achieve. This noise also exists at other stages but is normally expressed as a specification at this stage.
  • Accuracy: There is no such thing as a perfect ADC. Really every measurement means the real value is within a certain range. The better the accuracy the smaller the range (again I will write another article on this subject in the future).

A benefit to some of NI’s hardware which integrates the ADC and signal conditioning into a single device is that you have a single specification covering this and the previous stage. This can improve understanding of your system and make sure your components are well matched.


Now we have the data in the digital domain, it needs to be transferred to our computer. Because it is digital things like noise and accuracy are no longer a concern (most communication links have a higher resolution than ADCs).

The key thing here is speed. Can we transfer data fast enough to keep up with our ADC’s sample rate?

Common options are USB, Ethernet, PCI(e) which give different length and speed options. PCIe and highly integrated systems like PXI can provide the highest bandwidth (4GB/s+ in some PXIe systems) but for many applications, USB provides enough bandwidth and additional flexibility since it can be routed up to 10m.


The final step we consider is the software. Whilst this doesn’t inherently suffer from problems with measurement concerns we can make design decisions to make sure we are sensitive to the rest of the chain.

For example, how many decimal places do you save or display? If you have a temperature sensor that is only accurate to 0.5 degrees, then using 3 decimal places may confuse the user about the accuracy.

Equally, if it is a voltmeter accurate to a millivolt then saving to CSV with one decimal place is reducing the accuracy of the information you collect.

There is also an opportunity for software to compensate or enhance other elements. For example, averaging can reduce noise, or we can use software filters to adapt to variable noise levels.


So, when you design your next system, make sure you know which concerns or specifications are most important to you. Then check these across the full measurement chain to ensure that the data you get is reliable and informative.

We will be publishing more articles in the future to look at specific concerns and some of the mitigations we can put in place to improve them. Subscribe below to be informed when they are published.

Of course, if you need some help now, get in touch.


About the Author

I founded Wiresmith Technology to help engineers improve their systems and products with quality measurement systems. I'm a Certified LabVIEW Architect, Certified LabVIEW Embedded Developer and LabVIEW Champion.