TinyOS Software Engineering.ppt

TinyOS Software Engineering Sensor Networks for the Masses Outline Software engineering in sensor networks Characteristics of TinyOS TOSSIM and TOSSER Systems in development Future Ideas Conclusion Sensor Network Domain Wide range of users Highly distributed algorithms Limited resources Individual motes have minimal I/O Combination of usually separate difficulties Sensor Network Domain Wide range of users Highly distributed algorithms Limited resources Individual motes have minimal I/O Combination of usually separate difficulties Highly Distributed Algorithms Individual motes have limited computational capability Efficient algorithms require distributed processing over a network of motes Inter-mote concurrency Hard to write and debug Unable to inspect mote state Characteristics of TinyOS Abstractions: frames, commands, events, tasks Event-based non-blocking design Intra-mote concurrency Single stack User code handles interrupts (e.g. ADC) TOSSIM TinyOS mote execution simulator Scalable to one thousand motes Compiles directly from TinyOS source Allows use of traditional tools (e.g. gdb) Extensible radio, ADC and spatial models External interface to network (monitor traffic, inject packets) TOSSIM Benefits One can debug implementations, not just algorithms Bit-level radio simulation requires modifications to only one component Complexity of real-world simulation (e.g. radio) configurable by user Debug inter-mote and intra-mote concurrency TOSSIM: Inter-mote Concurrency Implement distributed algorithm Run in TOSSIM, examine algorithm component state as messages propagate Discover and fix bugs Implement noisy radio model, see how algorithm holds up Bug Example: Intra-mote concurrency New Radio Stack Bug Packets sent in PACKET_DONE event handler would usually (95% of the time) not be heard by other motes These packets heard with old radio stack Quick simulator output result: packets sent in handler don’t go through MAC component (no backoff, start symbol, etc.) Bu