1 / 13

EmStar: A Software Environment for Developing and Deploying Wireless Sensor Networks

EmStar: A Software Environment for Developing and Deploying Wireless Sensor Networks. CENS Research Review October 28, 2005 UCLA CENS EmStar Team. Outline. Why is EmStar useful? Where is EmStar used?. Numerous Software Requirements. Communication (ad-hoc/wireless). Algorithm/Sensing.

gauri
Download Presentation

EmStar: A Software Environment for Developing and Deploying Wireless Sensor Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EmStar:A Software Environment for Developing and Deploying Wireless Sensor Networks CENS Research Review October 28, 2005 UCLA CENS EmStar Team

  2. Outline • Why is EmStar useful? • Where is EmStar used?

  3. Numerous Software Requirements Communication (ad-hoc/wireless) Algorithm/Sensing Heterogeneity Avoid nesC/ C duplication Inter-platform communication Poor/dynamic Hard to estimate links Not all nodes Are 1-hop Task Scheduling Calibration Signal Processing Time Synch Field coverage / Bird Localization Routing Algorithm Bird Detection Remote Management State inspection/ Interactive Debugging Process control Remote actuation/ monitoring Visualization Dynamic topology Logging System Monitoring (development/deployment)

  4. Experimental Systems are… Experimental • Prototypes • Bugs • Unexpected and transient behavior • Things that will cause trouble: • Multiple asynchronous inter-dependent events • Trying to optimize application and make it smart • Unexpected data and environmental conditions • We need things to be (in lab and for deployments): • Robust so everything keeps running • Can not atomically restart the world • Partial failure is normal in large distributed systems • Softstate is crucial to success of distributed systems • Diagnosable so you can figure out what the problem is

  5. How does EmStar help? User Kernel Emulation Array Client Server Emulation Mode HostMote Protocol /dev/servicename /dev/fusd MN MN MN MN Node 001 Node 002 Node 003 Node N … kfusd.o Robust multi-process, microkernel architecture Simulation Framework with real RF channels Visualization Tools Transceiver Transceiver Transceiver Transceiver Mote Mote Mote Mote • EmStar is a layer above Linux designed to enable: • Simulation: Rapid iteration via real-code simulation tools • Robustness: Keep running despite unexpected failures and bugs • Visibility: Easily debug/diagnose running systems • Module Reuse: Leverage existing libraries, tools, and services

  6. What is EmStar? Layer 4: Extra Tools Help run, maintain, and debug application Layer 3: Existing Modules and Services Existing useful components for applications Layer 2: Device Patterns &Libraries IPC mechanism for a variety of interactions Layer 1: Glib Handle events on IPC Layer 0: FUSD Low Level IPC

  7. EmStar Provides … Communication (ad-hoc/wireless) Algorithm/Sensing Heterogeneity Avoid nesC/ C duplication Inter-platform communication Poor/dynamic Hard to estimate links Not all nodes Are 1-hop Calibration Task Scheduling Signal Processing Time Synch ESS / DSE RNPlite EmTOS Acoustic Ranging syncd Statesync, flooding, sinktree Sensor devices, libraries, staged event driven processing Emview / xoscope Device files EmRun In-memory Logrings Web server clustersync State inspection/ Interactive Debugging Process control Remote actuation/ monitoring Visualization Dynamic topology Logging System Monitoring (development/deployment)

  8. Transparent Trade-off of Scale vs. Reality Simulation Deployment Scale Emulation Test Deployment Reality • Deployment • Time consuming • Difficult to monitor and manage • Little/No out-of-band debugging • But by now, it’s bug free..? • Pure Simulation • Initial development • “Smoke test” • Fix major design flaws • “Emulation” • Real radio channels • Real Mote hardware in the loop • Catch bugs, tune algorithms

  9. Enables Mote-Microserver Integration dse/stream dse/query DSE link/mh Multihop Example: ESS ESS network • NesC-based Multihop tree routing protocol • Runs natively on motes • Runs in EmTOS wrapper on microserver • EmTOS run NesC code on the microserver preventing code duplication • EmStar helps with remote management of microserver ESS EssDse Multihop link/mote0 motenic Dse TimerC AM Transceiver (Mica2) ClockC RadioCRCPacket ADC Mote RF Channel

  10. Acoustic Platform • Localize motes • Localize and count woodpeckers • Linux-based wireless platform • 4-channel microphone array • Distributed acoustic sensing • 15-20 nodes surround targets

  11. Sounds fun, but first… Emstar provides… Time Synchonization State Dissemination Sink Tree, Flooding Acoustic Ranging Multilateration Emsim/Emview Ceiling Testbed Emproxy/rbsh Emrun process monitor Status devices Per-process Logrings • Support for time-synchronized sampling? • Network primitives for coordination among groups of nodes? • Automatic calibration of array location and orientation? • Development tools: • Simulation tools, testbeds, visualization • Debugging and Deployment tools: • Control groups/individual nodes • Health monitoring • Diagnostic data • Error logs

  12. Outside CENS Use • Current external users of our prototype system • Ohio State • Deployed 200 Stargates running EmStar for the DARPA NEST program • Implemented routing layer and software update mechanism • Tiered testbed in support of the DARPA NEST program • MIT • Mote software development using EmTOS on an ePRB testbed • Experiences and feedback • Initial experiences have been generally positive

  13. Conclusion Thanks for listening! More information at: http://cvs.cens.ucla.edu/emstar

More Related