Structural Health Monitoring Using Smart Sensors - ideals ...
Structural Health Monitoring Using Smart Sensors - ideals ...
Structural Health Monitoring Using Smart Sensors - ideals ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Table 7.6. Normalized Accumulated Stress Estimation<br />
Element ID<br />
Normalized Accumulated<br />
Stress Difference ( )<br />
3 0.6377 -2.1416<br />
4 0.6662 0.3378<br />
5 0.9751 4.9952<br />
6 0.4506 -2.5601<br />
7 0.3470 1.9430<br />
8 0.6078 -5.3461<br />
9 0.1368 0.2829<br />
10 1.0000 0<br />
11 0.6226 0.2349<br />
configuration. However, cluster heads do not need to physically line up; rather they need<br />
to line up logically. In Figure 7.22, the manager sensor, CH1, notifies the cluster head to<br />
the right, CH2. The receiver cluster head also initializes itself and notifies the next cluster<br />
head. The initialization and notification are repeated until no cluster head to the right is<br />
found.<br />
The right-most cluster head then starts the procedure of finding inconsistent damage<br />
detection results. This cluster head first checks whether damage is detected in its sensor<br />
community. If not detected, the operation moves to the left cluster head. If detected, the<br />
cluster head inquires with the neighboring cluster heads whether the damage detection<br />
results are consistent. If inconsistent, a flag on the cluster heads involved in the transaction<br />
are marked as “RETAKE”. The search for inconsistency then moves to the left cluster<br />
head, where the procedure is repeated. This inconsistency search and transition to the left<br />
node are repeated until the process reaches the left-most cluster head.<br />
When the left-most cluster head finishes the inconsistency search, the process of<br />
reporting to the base station begins. The left-most cluster head reports damage detection<br />
results, i.e. damaged element ID and any inconsistencies, to the base station. After this<br />
cluster head finishes reporting, the operation moves to the right cluster head. This<br />
procedure is repeated until all of the cluster heads report their results. Then, the operation<br />
moves back to the manager sensor. While all of the nodes are designed to report DCS<br />
logic results to the base station for debugging purpose, the code can be easily changed so<br />
that only cluster heads with damaged elements report to the base station.<br />
The manager sensor then inquires of the other cluster heads whether local sensor<br />
communities organized by these cluster heads need to retake data. Only local sensor<br />
communities with inconsistent damage detection results participate in the next round of<br />
DCS. If the manager sensor in the previous round of DCS does not participate in the next<br />
round, one of the cluster heads takes over the manager sensor’s role.<br />
125