Aus Doc-Wiki

Wechseln zu: Navigation, Suche
Sensor Lab logo
Fields of research



The Sensor Lab is located on the Telematics Group floor, room 1.101 at the IfI. The door is locked by a card reader (Ci-port with profile 0418). Please contact the supervisor of your course to get access to the lab.


The sensor nodes we have ordered are from Crossbow technology ( Basically, the sensors operate in 2.4GHz ISM band. The range of the radio module is about up to 50 m indoor and up to 300 m outdoor.

For more details see the data sheet.

MIB520 USB Gateway boards are available for programming sensor motes, using them with USB power, and debugging or base station uses.

Sensor boards

A number of sensor boards are available.


A number of MDA100CB sensor boards are available. The include the following features:


The MDA300CA is a sensor board and general measurement platform. It allows for low-power wireless instrumentation and can be used and extended to be used in various areas.


The MTS310CB sensor board includes the following components:

In addition to the sensors, it also has a sounder, which can be used as an alert, or possibly for audio communication between motes.


The MTS400CC board, which includes the following sensors:

Additionally, a few MTS420CC boards are available, which are basically the same, but include an additional ublox LEA-4A GPS module. Getting this to work with IRIS motes is still a work in progress, however.

A full list of available hardware is also available on the Sensor Lab website. More detailed information is also available.

New motes

A new set of motes and sensors are also available: SL:CM motes

Hardware inventory

The Sensorlab currently has the following motes:

The following attachments are available for IRIS motes:

The following attachments are available for the telosb compatible motes:

Also available are two SG1000 WSN sinks/bridges.


We have a Libelium Waspmote Evaluator Kit. For more information, see: SL:Waspmote

Sensor nodes:

Sensor boards:

Communication interfaces:




Raspberry Pi / Arduino

Additionally, two Raspberry Pi are available, with a working TinyOS setup on both:

Username and password can be found in ~sensorlab/documents/RaspberryPi/info.txt

In addition, we have 2 more two Raspberry Pi without an operation system.

We also have two CookingHacks Wifi Sets including Raspberry Pi 2:

There are four additional of the same kits with Arduino instead of Raspberry Pi.

Each of the CookingHacks kits includes four Sugus. These appear to be edible (as yet unconfirmed). Please don't eat all of them and leave some for other people if they are tasty.

Apart from that, the kits each include:


Furthermore, we have an SL:Identive NFC SDK:


We have a number of non-rechargeable batteries, as well as rechargeable AccuCell batteries. Please avoid deep discharges on the AccuCell batteries, as well as unnecessary recharges, as it can significantly lower their lifespan.

Android Phones

We have two Google Nexus 5 phones for use in projects involving smart phone app development (i.e. for visualization or making use of phone sensors).

AVR Dragon

An AVR Dragon with jumper cables for connecting pins is available. This should allow debugging IRIS nodes (via JTAG) and Arduino based platforms. More information: SL:AVRDragon



General documents can be found on:

TinyOS Iris API:

How To

How To Disassemble a Sensor Node to Reprogram it (.pdf) (.doc)


There is a printer in the Sensor Lab, in case you require printed documentation. To use it, please start the ws1 PC, which acts as a print server for the lab. It should be reachable from ws1-6 and pc01.

Modifications for IRIS motes

PacketParrot application

The PacketParrot application which is provided with TinyOS does not work on directly on the Iris motes. Thus, the following modified version can be used instead. The modifications are basically replacing the special radio component, which is used for sending and receiving, by the generic AMSenderC and AMReceiverC components.


To make the motelist command work with IRIS motes, a change has to be made to the motelist script. The following patch has to be applied:

--- motelist	2012-11-12 15:23:43.405203257 +0100
+++ motelist.fixed	2012-11-12 15:24:13.326732983 +0100
@@ -62,6 +62,7 @@
   #  Scan /sys/bus/usb/drivers/usb for FTDI or CP210X devices 
   my @ftdidevs =
     grep { (($_->{UsbVendor}||"") eq "0403" && ($_->{UsbProduct}||"") eq "6001") 
+       || (($_->{UsbVendor}||"") eq "0403" && ($_->{UsbProduct}||"") eq "6010")
        || (($_->{UsbVendor}||"") eq "10c4" && ($_->{UsbProduct}||"") eq "ea60")}
     map { {
       SysPath => $_,


Sometimes the java utilities can throw an exception in a thread, which does not terminate the whole application. This means that it will simply hang, stuck. Attempted mitigation:

--- /opt/tinyos-2.1.2/support/sdk/java/net/tinyos/comm/ 2016-07-01 10:25:13.333736932 +0200
+++ /opt/tinyos-2.1.2/support/sdk/java/net/tinyos/comm/      2016-07-01 10:24:48.794370923 +0200
@@ -124,6 +124,10 @@
         synchronized (m_listeners) {
           Iterator i = m_listeners.iterator();
-          while (i.hasNext())
-            ((SerialPortListener);
+          try {
+            while (i.hasNext())
+              ((SerialPortListener);
+          } catch (Exception e) {
+            System.exit(1);
+          }



SL:Install TinyOS 2.1 in Debian (lenny)


The PCs in the sensor lab room are currently running Ubuntu 10.04.


TOSSIM version in Tinyos 2.1.1 requires Python 2.5.5, which is not available in Ubuntu 10.04 (only newer versions are available). The following has been used successfully to install a compatible Python version:

sudo apt-get install build-essential gcc
cd Downloads
tar -xvzf Python-2.5.5.tgz
cd Python-2.5.5
./configure --prefix=/usr/local/python2.5
make test
sudo make install
sudo ln -s /usr/local/python2.5/bin/python /usr/bin/python2.5
sudo ln -s /usr/local/python2.5/bin/python-config /usr/bin/python2.5-config


login to the set up computer

 user: wsn
 password: tinyos

start Xubuntos in VMWare-Player

 user: xubuntos
 password: tinyos


Note: the motelist command does not show any connected motes (I think it is because of that the hardware is very new and therefore cannot be recognised)

To find out which usb device to use, just connect the node and use the dmesg command.

Transfer test application Blink to the node attached via USB

 cd /opt/tinyos-2.1.0/apps/Blink
 make iris install.1 mib520,/dev/ttyUSB0

Tinyos first test.JPG

Manuals (CD KIT)

Sensor Kit

CD Documents and Manuals











See also

Meine Werkzeuge