http://energy.eecs.umich.edu/wiki

This used to be the wiki home of research using TinyOS and epic motes. The code is in the SensorsResearch folder of the SVN repository on whereabouts.eecs.umich.edu. These pages walk through various parts of the code.

• General Overview - This is a starting point to the epic based motes. It walks through setting up the TinyOS environment on Linux and gets you started with TinyOS applications.
  • Checkout SVN Repository
    • SVN Repository Structure
  • Setting up TinyOS
  • Setup Blip - Configure Blip and install IPBasestation on a mote.
  • Install a TinyOS App - How to install a TinyOS app on a mote.
  • Create IPv6 Address
    • Configure IPv6
  • Use print - How to use the print function in a tinyos app.
  • Blip 2.0 - How to setup and use Blip 2.0
  • Creating a TinyOS Target - Something like make hemera
• Using the Epic Testbed - One way to set up the Epic or Quanto testbed.

• PRR 1 Hop
• Experiments

• My Experience With Blip

• UDPAccel Application Overview - TinyOS application that detects movement.
• Printers - These just print the data from the mote to the screen.
  • UDPAccelRecevier
• Forwarders
  • UDPAccelForwarder

• UDPAccelData Application Overview - This goes over a slightly more complicated TinyOS application.
• Connecting to the UDPAccelData application - This explains code that handles the packets from the UDPAccelData application in various ways.

• UDPMotion Application Overview - This goes over some of the interesting points of the UDPMotion application.
• Forwarders - These receive data from the BLIP driver and forward it on to Whereabouts
  • MotionSensorForwarder
• Clients - These use the UDPMotion data in various ways
  • motionDetector - Simple app prints motion sensor data from Whereabouts.
  • officeChecker - Notifies you when a person returns to their office.
  • computerSleeper - This goes over how the computerSleeper app works and how to build and use it.
  • gtalkUpdater - Sets your Google Talk status when you leave the office.
  • officeWatcher - Simple client for the Presence aggregator.
• Tools - These run on a server and assist a client app
  • computerWaker Tool - This wakes a computer that used computerSleeper back up.
• Supporters - These are apps that do not use the data from UDPMotion but collect and submit other data to Whereabouts that can be used in conjunction with UDPMotion.
  • keyboardWatcher - Sends a message to Whereabouts saying there is keyboard activity.
  • Bluetooth XML wrt Motion Sensing - There may be a bluetooth sensor someday.
• Aggregators - These collect data from UDPMotion and its supporters and synthesize it into an easier to use and more helpful message that it sends back to Whereabouts.
  • Presence - A simple message that contains whether or not there is someone in an office and sometimes even who.

Low power listening (LPL) turns the radio off when it is not in use in order to save battery life.

• UDPMotionLPL Application Overview

• HemeraBasic Application Overview
• HemeraBasic2 Application Overview
  • Rohm BH17 Light Sensor Driver
• Whereabouts Server for Hemera - Special configuration settings needed to make the hemera applications work as they should.
• Forwarders
  • HemeraForwarder - Forwards the packets received from the Hemera motes on to Whereabouts.
• Servers
  • thlServer - A simple Java server that services HTTP requests for THL data.
• Supporters
  • moteIDRoomSupporter - Allows you to send a packet that connects a mote ID to a building, floor, and room.
• Collectors - These are threads that are meant to be run from another application and collect data from Whery.
  • officeCollector
  • thlCollector
  • moteIDRoomCollector
• Miners - These process the data stored in the mysql database.
  • motionMiner

These tests will work on irene/hemera motes.

• BatteryChecker - Create a battery charge checking mote.
• DigitalPinOscillator - Sets a pin high for 5 seconds, and then low for 5 seconds.
• DigitalPinSampler - Displays value of digital pins on led0.
• SHT11Tester - Polls the SHT11.
• SimplePacket - Simple radio test app.
• BH17Tester - Polls the BH17 light sensor.

Schematics for some hardware can be found in the SVN repository:

$ svn co svn+ssh://<uniqname>@whereabouts.eecs.umich.edu/home/cvs/svnroot/trunk/SensorsProject/BoardDesigns

Use EAGLE to view the schematic and board files. Always open the schematic and board files together! (Eagle should ask you about this)

• Hemera

Sparkfun.com has three very helpful tutorials for getting started with Eagle. Keep in mind that they used an earlier version of Eagle and the shortcuts don’t quite line up correctly.

• Eagle: Schematics
• Eagle: PCB Layout
• Eagle: Creating a new part

• Sending Packets to Motes

• Change older clients over to the Presence aggregator.
• test for a disconnect in connection to whereabouts and fix it
  • updater
  • client
• add mac to computerSleeper
• different usernames based on mote id with hashmap
• computer energy use monitoring
• low power tinyos
• finish hemera board
• ability to send packet that associates a room and mote
  • check over data before submitting
• dont do automatic 1 min refresh request when no activity
• error handling mote2room
• make clean and recompile
• move collectors to own folder
• update tinyos to svn
• add the time of the last update from the motes to the website map information box
• check to see if reading the sht11 still toggles the motion sensor
• try using the new version of blip
• measure power with new version of blip
• get music school map setup
• figure out why node 31’s light sensor doesn’t work
• try using the epic id chip to set the id of the mote
• document the server sent streaming api
• script to do a lot of graphs and intervals
• heatmap on website
• update wiki with blip 2 stuff
• get wiki from atul
• create send packet on motion app again for irene
• finish rohm bh17 tinyos driver
• problems:
  • can’t ppp to the test bed
  • i2c bug with msp430-gcc 4.4.5
• python abstract base class for generic listener sender (could be to send to mysql database, other db, whatever)
• wireshark plugin
• track # of retransmissions

• Proxies - a username that would submit data for an actual user
• Services - a way to register services with the server and allow users to customize their privacy policies to allow/disallow certain services.

//get privacy policy
try {
  System.out.println("privacy policy:::");
  String command = "GetPrivacyPolicy";
  XMLDoc = new XMLDoc("<args/>");
  EncapsulatedDoc response = client.sendCommand(command, argDoc);
  if (response == null || response.getHeader("Status") == null || !response.getHeader("Status").equalsIgnoreCase("OK")) {
    throw new Exception("Error getting privacy policy: " + response.getBody());
  }
  XMLDoc privpol = new XMLDoc(response.getBody());
  System.out.println(privpol);
} catch (Exception e) {
  System.out.println("error getting privacy policy: " + e.getMessage());
}