21.01.2014 Views

Structural Health Monitoring Using Smart Sensors - ideals ...

Structural Health Monitoring Using Smart Sensors - ideals ...

Structural Health Monitoring Using Smart Sensors - ideals ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

anges from 10 to 20. If 50 percent overlap is employed in the spectral density estimation<br />

with 2,048 FFT data points, 20 time number of averages needs 21,504 data points.<br />

There are other factors to be considered when the number of data points is<br />

determined. One of them is the sampling frequency. The sampling frequency typically<br />

ranges from 100 to 256 Hz for civil infrastructure. These sampling frequencies are high<br />

enough considering the dominant modes of bridges, buildings, and towers. The<br />

frequencies of dominants modes are usually lower than 10 Hz. The reasons why the<br />

sampling frequency is much higher than the minimum frequency to capture vibrations<br />

below 10 Hz include that higher modes may also be influential to the response, that a<br />

periodic wave consists of multiple frequency components, that transient signal may have<br />

high frequency components, and that ground motion, whose peak values are often utilized<br />

in earthquake engineering, usually has higher-frequency components. A sampling<br />

frequency of 256 Hz is a reasonable assumption for SHM system with smart sensors.<br />

When a 0.1 Hz component of a signal sampled at 256 Hz is analyzed with an FFT of<br />

length 1,024, only less than a half of the natural period fits in one window; the resolution<br />

of FFT is too coarse. In such cases, the sampling frequency is lowered or the number of<br />

FFT points is increased. Increasing the number of FFT points results in an increase in the<br />

total number of data points.<br />

The data type also affects the amount of memory required to store a measured signal.<br />

The most often utilized are 16- and 32-bit integers, and double precision data. The sizes of<br />

these data types are 2, 4, and 8 bytes, respectively. The effective number of bits of<br />

resolution in the measured data determines the requirements on the data type. For<br />

example, an acceleration signal with a resolution of 20 effective bits needs to use either a<br />

32-bit integer or double precision data. Considering that many ADCs on smart sensors has<br />

resolution poorer than 16-bit, 16-bit integers are most likely able to represent measured<br />

sensor data.<br />

The combination of 21,504 data points and 16-bit integer yields 43 kB of data per<br />

sensing channel. Though this number will vary with changes in the number of data points<br />

or the data type, 43 kB is used from here on as a typical amount of data generated per<br />

sensing channel.<br />

The number of sensing channels also depends on the applications. For example, one<br />

of the bridges in Hong Kong famous for its densely instrumented sensors, Ting Kau<br />

Bridge, has 67 channels to measure acceleration and 132 channels to measure strain.<br />

These channels are normally sampled at 25.6 Hz. As such, hundreds of sensor nodes are<br />

considered herein. One sensor node may have multiple sensing channels; for example,<br />

acceleration measurement in three directions needs three channels. In total, this research<br />

has a target of approximately a thousand channels.<br />

A thousand sensing channels, each of which generates 43 kB of data, produce 43 MB<br />

of data per measurement. Centrally collecting such a large amount of data is not practical.<br />

Mechitov et al. (2004) reported that communication at the sink node is the bottle neck and<br />

that collection of 480 kB of data from 16 Mica2s required more than 6,000 seconds. If<br />

smart sensors with limited hardware resources, especially battery and RF components, are<br />

52

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!