DOI: 10.5281/zenodo.3405737
title: Wireless Link Quality Estimation on FlockLab - and Beyond

description: This repository contains wireless link quality estimation data for the FlockLab testbed [1,2]. The rationale and description of this dataset is described in a the following abstract (pdf is included in this repository -- see below). <strong>Dataset: Wireless Link Quality Estimationon FlockLab – and Beyond</strong><br> Romain Jacob, Reto Da Forno, Roman Trüb, Andreas Biri, Lothar Thiele<br> DATA '19 Proceedings of the 2nd Workshop on Data Acquisition To Analysis, 2019 <strong>Data collection scenario</strong> The data collection scenario is simple. Each FlockLab node is assigned one dedicated time slot. In this slot, a node sends 100 packets, called strobes. All strobes have the same payload size and use a given radio frequency channel and transmit power. All other nodes listen for the strobes and log packet reception events (i.e., success or failed). The test scenario is ran every two hours on two different platforms: the TelosB [3] and DPP-cc430 [4] platforms. We used all 27 nodes currently available. <em>Current dataset status</em> 2 months of data about 500 tests per platform <strong>Data collection firmware</strong> We are happy to share the link quality data we collected for the FlockLab testbed, but we also wanted to make it easier for others to collect similar datasets for other wireless networks. To achieve this, we include in this repository the data collection firmware we design. The entire data collection scheduling and control is done entirely in software, in order to make the firmware usable in a large variety on wireless networks. We implemented our data collection software using Baloo [5], a flexible network stack design framework based on Synchronous Transmission. Baloo efficiently handles network time synchronization and offers a flexible interface to schedule communication rounds. The firmware source code is available in the Baloo repository [6]. A set of experiment parameters can be patched directly in the firmware, which let the user tune the data collection without having to recompile the source code. This improves usability and facilitates automation. An example patching script is included in this repository. Currently, the following parameters can be patched: rf_channel, payload, host_id, and rand_seed <em>Current supported platforms</em> TelosB [3] DPP-cc430 [4] <strong>Repository versions</strong> <strong>v1.1.0</strong><br> Initial version.<br> Add the data collected in August 2019.<br> Data collected was disturbed at the beginning of the month and resumed normally on the August 13. Data from previous days are incomplete. <strong>v1.0.0</strong><br> Initial version.<br> Contain collected data in July 2019, from the 10th to 30th of July.<br> No data were collected on the 31st of July (technical issue). <strong>List of files</strong> <strong>yyyy-mm_raw_platform.zip</strong><br> Archive containing all FlockLab test result files (one .zip file per month and per platform). <strong>yyyy-mm_preprocessed_all.zip</strong><br> Archive containing preprocessed csv files, one per month and per platform. <strong>firmware.zip</strong><br> Archive containing the firmware for all supported platform. <strong>firmware_patch.sh</strong><br> Example bash script illustrating the firmware patching. <strong>parse_flocklab_results.ipynb </strong>[open in nbviewer]<br> Jupyter notebook used to create the pre-process data files. Also includes some example of data visualization. <strong>parse_flocklab_results.html</strong><br> HTML rendering of the notebook (static). <strong>plots.zip</strong><br> Archive containing high resolution visualization of the dataset, generated by the <strong>parse_flocklab_results </strong>notebook, and presented in the <strong>abstract</strong>. <strong>abstract.pdf</strong><br> A 3 page abstract presenting the dataset. <strong>CRediT.pdf</strong><br> The list of contributions from the authors. <strong>Dataset updates</strong> We plan to carry-on collecting this data in the long-run (However, we will likely decrease the time resolution to free testing time up). The newly collected data will be added to this;repository periodically; we envision monthly updates. <strong>References</strong> [1] R. Lim, F. Ferrari, M. Zimmerling, C. Walser, P. Sommer, and J. Beutel, “FlockLab: A Testbed for Distributed, Synchronized Tracing and Profiling of Wireless Embedded Systems,” in <em>Proceedings of the 12th International Conference on Information Processing in Sensor Networks</em>, New York, NY, USA, 2013, pp. 153–166. [2] “FlockLab,” <em>GitLab</em>. [Online]. Available: https://gitlab.ethz.ch/tec/public/flocklab/wikis/home. [Accessed: 24-Jul-2019]. [3] Advanticsys, “MTM-CM5000-MSP 802.15.4 TelosB mote Module.” [Online]. Available: https://www.advanticsys.com/shop/mtmcm5000msp-p-14.html. [Accessed: 21-Sep-2018]. [4] Texas Instruments, “CC430F6137 16-Bit Ultra-Low-Power MCU.” [Online]. Available: http://www.ti.com/product/CC430F6137. [Accessed: 21-Sep-2018]. [5] R. Jacob, J. Bächli, R. Da Forno, and L. Thiele, “Synchronous Transmissions Made Easy: Design Your Network Stack with Baloo,” in <em>Proceedings of the 2019 International Conference on Embedded Wireless Systems and Networks</em>, 2019. [6] “Baloo,” Dec-2018. [Online]. Available: http://www.romainjacob.net/research/baloo/.