Measurement performance in data acquisition systems:
How much is enough?

Anyone looking for equipment in the field of data acquisition is likely to encounter a wide and sometimes wild assortment of components and solutions. The possibilities range from PC plug-in cards to data loggers to VXI mainframe systems.

On the upside, you can find an answer for practically every application and every budget. On the downside, your hair could turn gray(er) by the time you sort through the hundreds of solutions out there to find the right one for your needs. Fortunately, you can narrow the decision process down to just five key attributes:

* Transducer types. The right system can not only measure the required transducers easily and accurately, but can also produce useful readings in the appropriate units. With hundreds of transducer types to choose from, this part of the decision can take a bit of work. Be sure to consider signal conditioning as well. In many cases, you need to modify the transducer output before the system inputs can accept it. Universal inputs, such as those offered in the new HP 34970A data acquisition & switching system, accept a wide range of transducer signals directly.
* Number of channels. Your channel-count requirements will help limit the range of solutions; the various categories and products vary widely in both their channel counts and their potential for expansion - often an important consideration.
* Data handling capabilities. This can include everything from displaying numeric readings to transferring data to a PC for 3D graphing and analysis to taking action based on measurement results.
* Application environment. The intended application environment (benchtop, rack mount or remote location) also helps determine the optimum form and feature set.
* Measurement performance. Application requirements dictate the resolution, accuracy, noise performance and speed you need. A temperature experiment that requires 0.1° of overall accuracy puts much tighter constraints on a data acquisition system than an experiment that needs only 2° of accuracy, for instance. Similarly, some datalogging and monitoring applications take measurements only a few times an hour, whereas automated test systems can measure hundreds of channels a second.

This article explores measurement performance, the attribute most likely to cause confusion when it comes to buying and applying a data acquisition system.

In a recent survey of R&D engineers, measurement performance topped the list as the biggest data acquisition concern. This isn't too surprising, since the ultimate outcome is a set of measurements that will be analysed and acted upon. Measurements are only as useful as they are correct, and errors can lead to misguided design decisions, expensive retesting and customer satisfaction problems. Clearly, trust in the results is an important aspect of data acquisition. On the other hand, you don't want to pay for more performance than you really need. Let's take a closer look at the four aspects of measurement performance.

Resolution

Resolution is measured in bits or digits and indicates how well an analogue-to-digital converter (ADC) can look at small changes in signal level (a useful rule of thumb for converting the two: digits x 3.5 = bits). The more bits or digits, the better the resolution. Figure 1 shows how ADC resolution affects the measurement of a sine wave.

If you have a java enabled browser try our Interactive Sampling Application of the screens below.


Figure 1a: Original sine wave

Figure 1b: Sine wave digitised with 2-bit ADC

Figure 1c: Sine wave digitised with 3-bit ADC

Figure 1d: Sine wave digitised with 4-bit ADC


To an extent, you can live with low resolution by shifting the input range to focus the available resolution on a narrower amplitude range. However, higher resolution lets you measure a broader range of amplitudes without changing the input range, which can slow measurements, add settling errors, and in some cases even require hardware modifications or different signal conditioning.

Noise

Noise is reflected in the stability from reading to reading, or the repeatability of a measurement. It is sufficiently large in some systems that it dominates the overall measurement accuracy. Noise enters data acquisition systems a number of ways; one common path is through noisy instrument environments. PC plug-in cards are at a disadvantage here because inside the PC they are exposed to high-frequency processor and bus signals that couple into measurements and can seriously degrade performance. In recent years PC card vendors have addressed this problem with shielding and thoughtful board lay-outs, improving noise performance immensely. However, standalone data acquisition systems, such as VXI, still have an advantage because they are removed from the noisy PC environment and carefully designed to minimise internal noise (Figure 2).

If you have a java enabled browser try our Interactive Noise Application of the screens below.


Figure 2a: HP 34970A, 200 samples integrating over 1 power line cycle (27 samples/second)

Figure 2b: PC plug-card without an integrating ADC; same measurement setup. Reducing the higher noise level would require extensive averaging.

Figure 2c: HP 34970A 200 samples integrating over 200 power line cycles (0.17 samples/ second).

Figure 2d: PC plug-card without integrating ADC; same measurement setup. Again, the higher noise level illustrates the need for more averaging.


Note: The HP 34970A and the PC plug-in card (a popular 16-bit model) were set up as identically as possibly. The HP 34970A was configured with the HP 34902A 16-channel reed multiplexer. Both systems were set to dc volts on the 0-100 mV range. The short was placed directly on the terminal block on the HP 34970A and directly on the PC card connector.

A second noise path is through the cabling you use to connect your transducers. Troublesome 50/60 Hz noise couples into cabling from surrounding power cords and wiring, lights and other electrical equipment. While much of this noise can be avoided with proper cabling (by using shielded twisted pairs, for example), some power-line noise still finds its way into the ADC. Data acquisition systems use a variety of means used to reject this noise:

* Low-pass filtering. This method puts a simple low-pass filter on the input that attenuates power line frequencies and harmonics. Filtering works is common in low-precision systems, giving good noise rejection but at the price of overall accuracy and slower reading speeds.
* Averaging. Another trick, used often with high-speed cards and systems, is to take many noisy samples and average them together, thus reducing noise. This can help compensate for a lack of noise rejection in hardware, but it often means extra work for you in the system software. It also can slow reading speeds down considerably, since you might need to average hundreds or thousands of samples to bring noise down to an acceptable level.
* Integrating ADCs. A third way to lower noise is to use an integrating ADC, a special ADC that integrates the input over exact multiples of one power-line cycle, automatically removing 50/60 Hz noise. This method has been used in high-end systems for years, but has just recently been made available in more affordable systems (such as the HP 34970A).

Accuracy

Accuracy reflects how closely the measured value matches the actual value of a signal. For example, a data acquisition system with 0.1% system accuracy will measure a "perfect" 10 Volt source with up to 0.1% of error; it might display as high as 10.01 V or as low as 9.99 V. Clearly, the better the accuracy, the better the quality of the data, and the more confidence you can place in your results. Figure 3 compares the concepts of accuracy and repeatability, and Figure 4 demonstrates how the three possibilities would affect an actual measurement.


If you have a java enabled browser try our Interactive Accuracy Application of the screen above.

Comparing accuracy specifications of data acquisition systems is not always as easy as reading numbers right off the data sheet. There are many sources of error in a data acquisition system and thus many accuracy figures to consider, including the following:

* ADC accuracy (integral and differential linearity, offset, time and temperature drift, and noise)
* Multiplexer accuracy (thermal offsets, cross talk, settling time and trace resistance)
* Conversion routine accuracy


Some manufacturers simplify the exercise by providing "system" accuracy specifications, which combine all these instrument-generated errors together into a single number. Others list each accuracy component separately, and you must carefully add them to come up with the final performance number. When comparing data acquisition system specifications, make sure you compare overall system performance. Also, you'll need to add the transducer error to determine complete measurement accuracy.

Speed

Data acquisition scanning speeds can range from a few samples an hour to several million samples per second. Consider what you realistically need for your specific applications; faster is not necessarily better. Faster systems tend to be less accurate and have higher price tags and higher noise levels. (In fact, many data acquisition systems run at higher speeds than the application really requires, simply to acquire enough samples to perform the averaging needed to overcome noise problems.)

Low-speed acquisition, up to several hundred channels per second, covers a surprising number of applications. One recent survey showed that 15 scans per second is adequate for 75% of the engineers queried. Most datalogging and monitoring applications fit into the low-speed category because many common physical parameters (temperature and humidity, for example) don't change very quickly and therefore don't need to be sampled often. Automated test applications occupy the top of the low-speed segment. Test throughput is important and the drive to minimise test time by maximising measurement speed can push scan rates to several hundred channels per second.

High-speed data acquisition, starting at a thousand channels per second or so, is needed to capture high-speed transient events. These applications include mechanical phenomena such as vibration, audio, and dynamic-strain. High sample rates are sometimes also required in multiplexed data acquisition applications with high channel counts. For example, a cable-test system with 500 channels that needs to sample each channel 20 times a second requires an ADC capable of 10,000 readings per second, as well as a multiplexer capable of quick scanning.

Speed requirements often determine the type of switch used in the data acquisition system multiplexer. Electromechanical switches, such as reed and armature relays, are common in low-speed applications. A key benefit is their ability to switch high voltage and current levels, but they are limited to switching rates of several hundred channels per second. Plus, since they are mechanical parts, they have finite lives and eventually wear out. Electronic switches, such as FETs and solid-state relays, are typically used in high-speed applications. In addition to fast switching, they have no moving parts and therefore don't wear out. The disadvantage is that they typically can't handle much voltage or current and must be carefully protected from input spikes, transients and other electrical unpleasantness.

Bottom line: analyse your needs before you shop around

By carefully analysing your application requirements before you start searching for a data acquisition solution, you'll have a better idea of how much performance you need to buy. If you'd like more information on HP's data acquisition systems and how they compare to other solutions on the market, please call the engineers at HP DIRECT. They'll make sure you get the performance your application demands, without paying for more than you need.

 


  • Power Supplies: Are you getting the power you think?


  • Power Supplies: Understanding power supply noise.


  • Data Acquisition: Whatever the application, there is a data acquisition solution.