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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Sender<br />

Send a packet<br />

• Sender sends a packet to the receiver.<br />

• Sender keeps sending the packet until<br />

acknowledgement packet is received.<br />

Receiver<br />

Acknowledge<br />

• Receiver saves received parameters and<br />

return acknowledgement packet<br />

Figure 5.16. Simple block diagram of the reliable unicast protocol for short messages.<br />

Sender<br />

SendSMsg.send()<br />

Pack parameters and data<br />

(e.g., Destination, message<br />

ID, data, etc. )<br />

SendShortSubTask()<br />

SendShortMsg.sendDone()<br />

call TimerNotice.start()<br />

Receiver<br />

ReceiveShortMsg.receive()<br />

Receiver stores received<br />

parameters and data.<br />

Acknowledge the sender<br />

Signal received()<br />

TimerShort.fired()<br />

if acknowledged,<br />

signal SendDone()<br />

else<br />

post SendShortSubTask()<br />

ReceiveNoticeMsg.receive()<br />

set flag as acknowledged<br />

SendAckMsg()<br />

SendShortSubTask()<br />

Figure 5.17. Detailed block diagram of the reliable unicast protocol for short messages.<br />

Sender<br />

Inquiry<br />

• Inquire of receivers whether they are ready<br />

Send a packet<br />

• Sender sends a packet to the receiver.<br />

• Sender keeps sending the packet until<br />

acknowledgement packet is received.<br />

Receiver<br />

Acknowledge<br />

• Receiver saves received parameters and<br />

return acknowledgement packet<br />

Acknowledge<br />

• Receiver saves received parameters and<br />

return acknowledgement packet<br />

Figure 5.18. Simple block diagram of the reliable multicast protocol for short messages.<br />

Unicast<br />

The sender transmits a packet, including the destination ID, source ID, message ID,<br />

parameter, and commands. Until this packet is acknowledged, the sender continues to<br />

transmit this packet. The receiver extracts information from the packet and sends an<br />

acknowledgment back to the sender (see Figures 5.16 and 5.17)<br />

The end of one round is difficult to judge, as explained in the reliable unicast protocol<br />

for long data records. The same solution applies to short messages. The source and<br />

message IDs for the last 15 rounds of communication are stored so that acknowledgment<br />

can be sent even after the receiver is disengaged from this round of communication.<br />

Multicast<br />

The sender first transmits a packet including the receivers’ node IDs, as was the case<br />

for the multicast communication protocol for long data records. Once all of the receivers<br />

return an acknowledgment to the sender, the sender transmits a packet containing<br />

parameters and commands. The receivers also acknowledge this packet. To judge the end<br />

72

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

Saved successfully!

Ooh no, something went wrong!