Motescope

Overview

Motescope & Omega (retired) are wireless sensor networks deployed in Soda Hall, the Computer Science building at UC Berkeley. They provide permanent testbeds for development and testing of sensor network applications by facilitating research in sensor network programming environments, communication protocols, system design, and applications.
Motescope is the follow-on to the sMote testbed and is constantly evolving. We first replaced the 78 Mica2DOT motes used in the sMote testbed with MICAz motes. The MICAz motes also use a Atmel ATmega128L microcontroller but with a online pokies nz transmitter frequency of 2.4GHz to 2.4835GHz and an indoor range of 20 to 30 meters. EPIC replaced the MICAz, a node equipped with an 802.15-4-compliant radio chip (the TI CC2420), a 2MB external flash chip, and a 16-bit microcontroller (TI MSP430). Additionally, the EPIC node implements an energy monitoring system called iCount (publication) as well as a calibration circuit to allow measurement of node energy consumption. The EPIC board exports a number of signals and ports for monitoring microcontroller and radio state as well as connecting sensors. Among these are 8 ADC channels, 1 I2C port and 4 general I/O ports. These can be used to connect a variety of analog and digital sensors. We have interfaced the EPIC to many sensors incluing accelerometers, gyroscopes, magnetometers, electrical current sensors, temperature and humidity sensors, passive infrared sensors, and light sensors, amoung others.

The retired Omega testbed consisted of 28 Telos motes (rev B) consisting of an 8MHz Texas Instruments MSP430 microcontroller, 48k Flash, 10k RAM, and a 250kbps 2.4GHz IEEE 802.15.4 Chipcon Wireless Transceiver. The Telos motes were connected via USB for power, programming and debugging.

Nodes on both testbeds run the TinyOS operating system and are programmed in the NesC programming language, a component-oriented variant of C. Typically, you will be able to prototype your application either using the TOSSIM simulation environment or with a handful of motes on your desktop. Our group has developed a range of applications and protocols that run on the motes, including an IPv6-compatible low-power networking stack, blip.


Getting Started

Programming A Node/Testbed
  • EPIC Instructions
  • Older EPIC (Quanto) Instructions
  • MicaZ Instructions
  • Omega Instructions (retired)

  • Reference
  • EPIC Genealogy
  • SVN/Trac
  • TinyOS
  • TinyOS Programming Manual
  • blip

  • Deployment (Soda)

  • EPIC Gen 3
  • MicaZ, MicaZ+PWR, EPIC Gen 1 & 2 (2010)
  • MicaZ, MicaZ+PWR, EPIC Gen 1 (2009)
  • Omega (2007)   (pics) (retired)
  • MicaZ+Power (2007)
  • Mica2DOT (2006)

  • Deployment (CITRIS Building)   (pics)

  • 4th Floor   - Current names: 4th Floor   (format: sdh-4-<mote number>)
  • 5th Floor   - Current names: 5th Floor   (format: sdh-<mote number>)
  • 6th Floor   - Current names: 6th Floor   (format: sdh-<mote number>)
  • 7th Floor   - Current names: 7th Floor   (format: sdh-<mote number>)
  • * note: motes will be renamed to match the naming scheme used in Soda.

    Deployment (HydroWatch)

  • Soda 7th Floor Test
  • Angelo Reserve 3rd Deployment (PMS)

  • HydroWatch Project Page

  • Follow-on: ACme (EPIC-based)

  • First Building-Wide Deployment Test (PMS)

  • ACme Project Page

  • Miscellaneous

    PMS
  • PMS - Position Monitoring System
  • Motestat (discontinued)
  • Meraki   (EPIC+Meraki)
  • Accessing the Meraki (manufacturer's OpenWRT)
  • Flashing The Meraki (OpenWRT/Kamikaze)
  • Cross-Compiling (OpenWRT/Kamikaze)
  • Open-Mesh   (EPIC+Open-Mesh)
  • Contact us for further information
  • NSLU2
  • Installing SlugOS/LE (NFS mounted rootfs)
  • Installing OpenWRT/Kamikaze (stand alone)
  • HP5500
  • Installing GPE/Restoring PocketPC


  •   This material is based upon work supported by the National Science Foundation under grants #0435454 and #0454432, and the NSF Graduate Research Fellowship Program. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.