![\"\"](\"https:\/\/web.archive.org\/web\/20150313184205im_\/http:\/\/nislab.bu.edu\/wp-content\/uploads\/2015\/02\/TeaCP_structure.png\")
<\/a><\/p>\nTeaCP operates at the application layer, and consists of the test configuration component, the application layer component for generating and handling packets, and the post-experiment analysis component. The test configuration component and the application layer component run on sensor motes. The post-experiment analysis component runs on a PC.<\/p>\n
The configurable test parameters include the packet generation interval, the radio power and the channel for the network. The radio power and channel settings are applied to the radio component of the hardware. The packet generation interval is applied to a periodic timer. The firing signal of the timer (i) increments the packet counter by one, (ii) invokes the packet generator to generate a data message (encapsulated in a packet) with packet ID equal to the packet counter, (iii) drives the log generator to output a log message, and (iv) transfers the packet to the network layer, which moves it towards the root using a collection protocol. Since the collection protocol may use multihop routing to accomplish the delivery, the packet may be received by intermediate nodes and the root. No matter whether the node is a relay or the root, the network layer will notify the packet reception handler when it receives a packet from other sensors. The packet reception handler prepares the information needed by the log generator, which outputs log message to storage through serial communication. Finally, post-experiment analysis is done based on the data saved in storage (e.g., the SD card datalogger).<\/p>\n
In the following, we show how to use TeaCP to obtain logs from experiments and simulations and analyze the performance of collection protocols using the TeaCP analysis component.<\/p>\n
Using\u00a0TeaCP in experiments<\/h3>\n
\n
TeaCP can be used in experiments to evaluate and analyze the performance of collection protocols. In an experiment, a number of sensor nodes are deployed in the testing environment. TeaCP utilizes an activator to send out a broadcast message, which contains the test parameters and establishes clock synchronization. Once the sensors have received the broadcast message, they apply the test parameters to their system. Then they start to generate data packets and the whole data collection network starts to run. While the data packets are routed around in the network, each node will generate log messages, recording information about events happening in the network, such as when a packet is generated or received. These log messages are stored by the data logging system as log files. Finally, TeaCP analysis component can calculate the test statistics based on the log files.<\/p>\n
1. Configuring\u00a0a test<\/h4>\n
The test parameters are configured in the header file\u00a0<\/span>test_config.h<\/code>\u00a0under the directory\u00a0<\/span>exp\/nesc\/<\/code>:<\/p>\n\n
\n
\n\n\n\n1<\/div>\n 2<\/div>\n 3<\/div>\n 4<\/div>\n 5<\/div>\n 6<\/div>\n 7<\/div>\n 8<\/div>\n 9<\/div>\n 10<\/div>\n 11<\/div>\n 12<\/div>\n<\/td>\n \n\/\/ teacp\/exp\/nesc\/test_config.h<\/code><\/div>\n<\/div>\n \/\/ Options: PERIODIC_TIMER | EXPONENTIAL_TIMER<\/code><\/div>\n#define PERIODIC_TIMER<\/code><\/div>\n<\/div>\n enum<\/code>{<\/code><\/div>\n\u00a0\u00a0<\/code>NODE_ID = ALL_NODES,<\/code><\/div>\n\u00a0\u00a0<\/code>COMMAND = START,<\/code><\/div>\n\u00a0\u00a0<\/code>PACKET_INTERVAL = 512,<\/code><\/div>\n\u00a0\u00a0<\/code>RADIO_POWER = 3,<\/code><\/div>\n\u00a0\u00a0<\/code>RADIO_CHANNEL = 26<\/code><\/div>\n};<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nTeaCP provides the following configurable test parameters:<\/p>\n \n\n- Traffic type — the traffic pattern in which the packets are generated at each source node. The current version of TeaCP has implemented two kinds of traffic types: one is periodic packet generation (
#define PERIODIC_TIEMR<\/code>) and the other is emulating Poisson packet arrival process (#define EXPONENTIAL_TIMER<\/code>).<\/li>\n- Packet generation interval — the time interval between two consecutive packet generations at each source node. If the traffic type is periodic packet generation, then the packet generation interval is a constant with value PACKET_INTERVAL. If the traffic type is Poisson packet generation, then the packet generation interval is an exponential random variable with expectation equal to PACKET_INTERVAL.<\/li>\n
- Radio power —\u00a0the transmission power when a node\u00a0transmits a packet or a beacon message. For the CC2420\u00a0chip, radio power ranges from -25 dBm to 0 dBm.<\/li>\n
- Radio channel —\u00a0the IEEE 802.15.4 radio channel on which the\u00a0collection network operates. The 2.4GHz ISM band is\u00a0divided into 16 non-overlapping ZigBee channels, with\u00a0channel ID from 11 to 26.<\/li>\n<\/ul>\n<\/ul>\n
After we have configured the parameters for a test, compile and install the TinyOS program onto the activator:<\/p>\n \n \n \n\n\n\n\n $ <\/code>cd<\/code> exp<\/code>\/nesc\/activator\/<\/code><\/div>\n$ <\/code>make<\/code> telosb bsl,<\/code>\/dev\/ttyUSB0<\/code> install<\/code>.50<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n2. Installing TeaCP application layer component<\/h4>\nNext we compile the TeaCP application layer component and the collection protocol and install onto the nodes.<\/p>\n \n \n \n\n\n\n\n $ <\/code>cd<\/code> exp<\/code>\/nesc\/ctp<\/code><\/div>\n$ <\/code>make<\/code> telosb<\/code><\/div>\n$ <\/code>make<\/code> telosb bsl,<\/code>\/dev\/ttyUSB0<\/code> reinstall.1<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nThe last command should be repeated to install the code onto the\u00a0sensors with different node IDs (by specifying\u00a0<\/span>reinstall.[TOS_NODE_ID]<\/code>)<\/p>\n3. Attaching\u00a0the data logging system<\/h4>\nWe then attach the data logging system to each node and deploy the nodes in the testing environment. For the data logging system, you can either use our implemented SD card datalogger or connect each node to a PC through USB port for data logging. If you use the USB datalogging system, you need to run the serial listener to receive the serial messages from the sensors:<\/p>\n \n \n \n\n\n\n\n $ java net.tinyos.tools.Listen -<\/code>comm<\/code> serial@<\/code>\/dev\/ttyUSB0<\/code>:telosb > node_1.log<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nHere we save the received serial messages into the file with extension .log. This is intentional because our TeaCP analysis component identifies a file as a log file by looking at the file extension.<\/p>\n 4. Starting and finishing a test<\/h4>\nPress the user button on the activator node to send out a broadcast signal and the experiment starts.<\/p>\n When the experiment finishes, press the user button on the activator node for five more times and the activator will send out a broadcast signal to tell the sensors to reset. Then collect the log files from the dataloggers for post-experiment analysis. If you are using\u00a0the USB logging system, you need to press\u00a0CTRL+C on the keyboard to terminate the serial listener.<\/p>\n A log file consists of a list of received serial messages, which contains a log message recording information with regard to network events:<\/p>\n \n \n \n\n\n\n1<\/div>\n 2<\/div>\n 3<\/div>\n 4<\/div>\n 5<\/div>\n<\/td>\n \n\n 00 ff ff 00 00 10 00 af 01 00 03 00 04 00 08 00 00 0a 79 00 14 76 53 02<\/code><\/div>\n00 ff ff 00 00 10 00 af 01 00 03 00 08 00 08 00 00 0a 79 00 14 76 91 01<\/code><\/div>\n00 ff ff 00 00 10 00 af 01 00 03 00 06 00 08 00 00 0a 79 00 14 76 aa 03<\/code><\/div>\n00 ff ff 00 00 10 00 af 00 00 03 00 03 00 03 00 00 0a 7a 00 14 78 3c 00<\/code><\/div>\n00 ff ff 00 00 10 00 af 01 00 03 00 04 00 08 00 00 0a 7a 00 14 78 8a 02<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nThe format of the received serial message is explained in the figure:<\/p>\n \n ![\"\"](\"https:\/\/web.archive.org\/web\/20150313184205im_\/http:\/\/nislab.bu.edu\/wp-content\/uploads\/2015\/02\/serial_message_format2.png\") <\/a><\/p>\nFormat of received serial messages in log files.<\/p>\n<\/div>\n The first few bytes of the received serial message are the header added by the TinyOS serial communication protocol. The rest of the serial message is the log message generated by a sensor recording information about a network event. For example, the log message in the figure tells us that the packet (with ID 0x00000a79 generated by source node 6) arrives at node 3 in three hops and the last hop is node 8.<\/p>\n Using\u00a0TeaCP in simulations<\/span><\/h3>\n
\nThe procedure of using TeaCP to run TOSSIM simulations is basically the same as in experiments. The only difference is that the activator is not needed in the simulation to send out a broadcast message configuring the network. In simulations, the configured test parameters are applied by compiling them into the code of sensors.<\/p>\n 1. Configuring a test<\/h4>\nThe same as experiments, we configure the packet generation interval in\u00a0<\/span>test_config.h<\/code>\u00a0<\/span>under\u00a0<\/span>sim\/nesc\/<\/code>. However, the configurations of radio power and radio channel in the header file are not applicable any more. Instead, the TOSSIM simulation uses a different way to configure the link conditions between nodes. TeaCP includes the configurations in the simulation script, e.g.,\u00a0<\/span>static.py<\/code>\u00a0<\/span>under the directory\u00a0<\/span>sim\/test_scripts\/<\/code>:<\/p>\n\n \n \n\n\n\n1<\/div>\n 2<\/div>\n 3<\/div>\n 4<\/div>\n 5<\/div>\n 6<\/div>\n 7<\/div>\n 8<\/div>\n<\/td>\n \n\n default_arg <\/code>=<\/code> {<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'protocol'<\/code>: <\/code>'ctp'<\/code>,<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'log_filename'<\/code>: <\/code>'log\/temp\/simulation.log'<\/code>,<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'noise_filename'<\/code>: <\/code>'noise-100dBm.txt'<\/code>,<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'link_filename'<\/code>: <\/code>'static\/perfect-grid-25nodes.txt'<\/code>,<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'finish_time'<\/code>: <\/code>500<\/code>,<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>'link_gain_adjust'<\/code>: <\/code>0<\/code><\/div>\n\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nThe file\u00a0<\/span>link_filename<\/code>\u00a0<\/span>specifies the link gains between nodes in the network. The file\u00a0<\/span>noise_filename<\/code>specifies the noise trace at each node.<\/p>\n2. Compiling TeaCP application layer component<\/h4>\nAfter we finish the configuration, compile the TeaCP\u00a0application layer component:<\/p>\n \n \n \n\n\n\n\n $ <\/code>cd<\/code> sim<\/code>\/nesc\/ctp<\/code><\/div>\n$ <\/code>make<\/code> micaz sim<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\nThis compilation generates the Python code of\u00a0the TOSSIM simulator, | | |
| | | | | | |