previous: Home   next: Query Interface

Setup of SwissQM 1.0

The following instructions provide a walk-through for setting up and using SwissQM. They have been tested on Windows and Linux with Xbow mica2 nodes (mica2 platform) and Moteiv tmote sky nodes (telosb platform) on the TinyOS CVS snapshot release 1.1.15.

Prerequisites

TinyOS

A working TinyOS 1.x installation is required to build the SwissQM Virtual Machine. Furthermore, the necessary tools (compiler, binutils, programmer, etc.) for the desired target platform have to be setup correctly. It is recommended to first test the TinyOS installation before continuing by building and running some of the supplied applications, e.g. CntToLedsAndRfm and RfmToLeds.

If you are using Moteiv's tmote sky nodes you can also install TinyOS using Moteiv's boomerang software which includes TinyOS 1.1.15 and the required tools to build for the the telosb platform.

Pointers and hints:

• TinyOS homepage: TinyOS software, documentation, FAQ, mailing lists, etc.
• Tuning the MICA2 Radio Stack for TinyOS: If you have trouble getting the radio running on mica2 nodes (e.g. CntToLedsAndRfm and RfmToLeds not working together), check that you are setting a default frequency when compiling.
• If you encounter errors frequently when programming tmote sky nodes under linux and you are using a USB 2.0 hub to connect the nodes, try without the hub or disable USB 2.0 support. To disable USB 2.0 support, disconnect the hub and the nodes, unload the ehci_hcd kernel module (as root or using sudo: rmmod ehci_hcd), and then reconnect the hub and nodes. If ehci_hcd is not compiled as a module you will have to recompile your kernel.
• Make sure you have all the necessary tools for your platform (avr-* for mica2 and msp430tools-* for telosb) and that you use versions suitable for TinyOS. The nesC compiler generates C code that contains dollar ($) signs in identifiers, which is not accepted by most "plain" compilers and assemblers. Hence, do not use tools which might be provided by your linux distribution unless you are sure that they are compatible with TinyOS. The safe choice is to use the tools provided by TinyOS, which can be downloaded at http://www.tinyos.net/dist-1.2.0/tools/.

Java

If you followed the instructions for setting up TinyOS, you should have a working JDK and JAVACOMM installation, which is required to run the SwissQM gateway software. You will also need Apache Ant to build the gateway.

Pointers and hints:

• Apache Ant
• If you cannot even program the nodes with a simple application (e.g., CntToLeds), you first have to fix these basic problems with the serial port before you start bothering with JAVACOMM.
• Make sure, you configured JAVACOMM correctly so you can access the serial port to which your node is connected. For IBMs JDK on linux, you have to uncomment the last line in jre/lib/javax.comm.properties to allow access to USB-serial devices like the tmote sky nodes.
• It can happen that serial port access suddenly does not work after restarting the application. Often, reinitialising the serial port with stty -F /dev/<port> raw or by running minicom on that port can sort out the problem.

Building and Installing the SwissQM Virtual Machine

Unpack the source distribution (swissqm-wsn-*) to the apps folder of your TinyOS installation. This will create a new folder SwissQM. Change to that folder and build and install SwissQM as you do for other TinyOS applications, e.g.

for mica2:
make mica2 install,0 mib510

for telos:
make telosb install,0 bsl

install,x will flash the SwissQM image for node x. So change it to enumerate your sensor nodes while programming.

Building and Configuring the SwissQM Gateway

Unpack the source distribution (swissqm-gateway-*) to a convenient location. This will create a new folder SwissQM-gateway. Change to that folder and build the SwissQM gateway by running

ant dist

The file swissqm.properties contains the configuration for the gateway. Edit this file to fit your setup. In particular, you have to set ch.ethz.inf.swissqm.motecom to match your TinyOS mote communication link (the same that you have in the MOTECOM environment variable, which is not required for the gateway) and ch.ethz.inf.swissqm.dblogging to enable or disable logging to a database. If you want to use logging to a database, you also have to set the ch.ethz.inf.swissqm.db.* properties to match your database setup.

If you enabled dblogging make sure that the following structures exist in the database specified in ch.ethz.inf.swissqm.db.name: sequence queryidseq and a table queries. If you are using PostgreSQL you can use the initdb.sql script:
psql -f initdb.sql mydatabase For other databases this file should give enough information about the schema used by the gateway.

previous: Home   next: Query Interface