|
The Samraksh Company |
.png){kind=spacer} |
Could not compile stylesheet for timeless. Using last compiled stylesheet.
By:
Bahri cagliyan
Hello We try to create a radar sensor network with telosb's.
We install the WirelessRadarDataCollect app to three Telosb's.(With make telosb install,1 (2 and 3 for other nodes))
Then we install the BaseStation Application on one mote.
After all the installation completed,we tried to gather datas.After logging the datas into a txt file we get the following datas in each line.
"00 FF FF FF FF 1A 00 EF 1B B3 0A DD 0B 07 0A DF 0B 0D 0A E1 0A FF 0A DF 0A FF 0A DD 0B 01 0A E7 0A F7 "
There are too many I and Q datas. We dont know which data come from which node.
Could you please explain creating network and gathering datas with BumbleBees.
We install the WirelessRadarDataCollect app to three Telosb's.(With make telosb install,1 (2 and 3 for other nodes))
Then we install the BaseStation Application on one mote.
After all the installation completed,we tried to gather datas.After logging the datas into a txt file we get the following datas in each line.
"00 FF FF FF FF 1A 00 EF 1B B3 0A DD 0B 07 0A DF 0B 0D 0A E1 0A FF 0A DF 0A FF 0A DD 0B 01 0A E7 0A F7 "
There are too many I and Q datas. We dont know which data come from which node.
Could you please explain creating network and gathering datas with BumbleBees.
Accepted Answer
By:
Michael
Hello Bahri,
Thank you for including example output to help me assist you.
The BumbleBee-enabled TelosBs transmit 802.15.4 packets with radar data to the BaseStation TelosB that is connected via USB to the PC.
TinyOS publishes designs in in TinyOS Enhancement Proposals, referred to as TEP. TEP111 explains the packet format used by TinyOS 2.x.
I will decipher the BaseStation's output based on the TEP11 and the WirelessCollect radar_radio_msg format.
You would like to decipher which data comes from which node. One solution is to add the node ID into the payload of the message. Luckily, we already have an example in the TinyOS tutorials. The BlinkToRadio application adds the source mote address to the beginning of the payload. In WirelessCollect.h, add the nodeid member to the radar_radio_msg struct. Something like:
Then, in WirelessCollectC.nc::sendData(), add the following to line 101.
Now you should be able to see the sender's node id inside your packet payload and BaseStation output.
Sincerely,
Michael
Thank you for including example output to help me assist you.
The BumbleBee-enabled TelosBs transmit 802.15.4 packets with radar data to the BaseStation TelosB that is connected via USB to the PC.
TinyOS publishes designs in in TinyOS Enhancement Proposals, referred to as TEP. TEP111 explains the packet format used by TinyOS 2.x.
I will decipher the BaseStation's output based on the TEP11 and the WirelessCollect radar_radio_msg format.
00 : ignore the first 00
FF FF : destination address is the broadcast address.
FF FF : link source address
1A : message length
00 : group id
EF : handler id. This is the AM_RADAR_RADIO_MESSAGE id in WirelessCollect.h
1B B3 : counter.
0A DD 0B 07 : first nx_uint16_t I and Q sample, repeated for SAMPLES_PER_PKT.
You would like to decipher which data comes from which node. One solution is to add the node ID into the payload of the message. Luckily, we already have an example in the TinyOS tutorials. The BlinkToRadio application adds the source mote address to the beginning of the payload. In WirelessCollect.h, add the nodeid member to the radar_radio_msg struct. Something like:
typedef nx_struct radar_radio_msg {
ns_uint16_t nodeid;
nx_uint16_t counter;
nx_uint16_t sample[2*SAMPLES_PER_PKT];
} radar_radio_msg_t;
Then, in WirelessCollectC.nc::sendData(), add the following to line 101.
sendmsg->nodeid = TOS_NODE_ID;
Now you should be able to see the sender's node id inside your packet payload and BaseStation output.
Sincerely,
Michael
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »