1 / 21

Tiny OS

Tiny OS. Vinay Kumar Singh Dongseo University. Outline. Introduction. TinyOS nesC My Aim. Problems. Timing consideration. My next plan. References. Introduction. TinyOS Very small “operating system” for sensor networks. (core OS 396 bytes).

Sharon_Dale
Download Presentation

Tiny OS

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. Tiny OS Vinay Kumar Singh Dongseo University

  2. Outline • Introduction. • TinyOS • nesC • My Aim. • Problems. • Timing consideration. • My next plan. • References

  3. Introduction • TinyOS Very small “operating system” for sensor networks. (core OS 396 bytes). • Follows Component-oriented architecture. • It follows Concurrency based model on tasks and events. • nesC is an extension to C. • nesC follows the concurrency model so all the data races are avoided. • The cricket software constrains various issues like timing, accuracy etc.

  4. Tiny OS • An “Operating system” for wireless embedded sensor networks. • Actually a set of software components that can be “wired” together into a single binary which is run on the motes. • Minimal OS functions • 2 threads of execution: tasks and hardware event handlers • No memory management • Main Ideology • HURRY UP AND SLEEP!! • Sleep as often as possible to save power • High concurrency, interrupt driven (no polling)

  5. Component Hierarchy in TinyOS

  6. nesC

  7. nesC Interfaces

  8. nesC components

  9. Visualizing configurations C1 C2 C2 C3 C3 • Connect configurations: configuration app { } implementation { uses c1, c2, c3; c1 -> c2; // implicit interface set. c2.out -> c3.triangle; c3 <- c2.side; } • Partial configurations: component c2c3 { provides interface triangle t1; } implementation { uses c2, c3; t1 -> c2.in; c2.out -> c3.triangle; c3 <- c2.side; }

  10. My Aim • As in the cricket system all the processing done in the PDA attached to the cricket mote, I wanted to do processing at the base station. • For using the cricket RF for dual system I have to make the changes in the cricket program. • The base station contains the cricket mote attached with base station. • Check the different application running on the cricket mote.

  11. Indoor Tracking System (Previous) Target Expansion Board RF Base Station

  12. Indoor Tracking System Target Base Station

  13. Cricket software • Work done • Add storage in flash. • Temp adjustment. • Add units to all outputs but report. • Add setting of units. • Disable RS-232 depending of the test switch position on beacons . • Error codes. • Add coord.. to msg beacon. • Temp to msg beacon. • Work remaining. • Time consideration. • Data transmission using cricket RF.

  14. Times consideration • In cricket • TIMER_OFFSET 550us • MAX_ALLOWED_TIMER_VAL 45000us • AVG_BEACON_INTERVAL_TIME 1000us • DESYNC_DELAY 500us • MAX_US_TRAVEL_TIME 53000 us • MIN_BEACON_INTERVAL_TIME 668us Total time taken in Total calculation = 47ms. • Time factors to be added. • PROPGATION TIME • DESYNC_DELAY • UPDATE TIME.

  15. Cricket program Problems • The program that I download from the MIT project is not working well. (Actually there is no simulator tools like TinyViz for running this cricket program on PC) • Some components in the program are missing. • It is not generating the documents. • Because we have to use only the cricket unit for transmission of message we have to make arrange the time that is taken in different operation. • We have to also test the application provided by the cricket.

  16. Application development Fig 1: Software Archicture

  17. References • Nissanka B. Priyantha, Anit Chakraborty, Hari Balakrishnan, The Cricket Location-Support system, Proc. 6th ACM MOBICOM, Boston, MA, August 2000. • Hari Balakrishnan, Roshan Baliga, Dorothy Curtis, Michel Goraczko, Allen Miu, Nissanka B. Priyantha, Adam Smith, Ken Steele, Seth Teller, Kevin Wang, Lessons from Developing and Deploying the Cricket Indoor Location System, November 2003. (Preprint. • Cricket V2 user manual. • Cricket software by MIT Cricket project.

  18. Thank You

More Related