TinyOS Simulator projects

Tiny OS is designed for embedded sensor network which is an open source operating system and network simulator. It composed of component based programming model to design nesC which evolve Tiny OS programming. We try to re implement TinyOS in new programming language. We develop many event driven applications in Tiny OS and it not only described as an operating system, it also a framework. It acts as framework for embedded systems and group of components are enable to build application into other application.

TinyOs-Network-simulator-Projects

TinyOS Features:

We adopt the features of TinyOS in final year project are:

  • Event driven OS.
  • Completely non blocking.
  • Tasks are non preemptive and run in FIFO order.
  • Specially designed for WSN.
  • Tiny OS code is statically linked.
  • Programs are built of software components.

TinyOS Simulator Requirement:

In M.E projects, we require following parameters to simulate TinyOS. They are given as:

  • Scalability:

We handle large network with various nodes in a wide range of configuration. We can deploy these network approximately about 850 nodes.

  • Completeness:

We ensure an interaction among all systems as possible and capture accurate behavior at wide range level.

  • Fidelity:

We capture the network behavior at fine grain.

  • Bridging:

In ensures the bridge gap among algorithm and implementation which permit developer to test, verify code that run on real hardware.

Components of TinyOS simulator in NesC:

TinyOS simulator is coded by C language which is a component based applications. We provide components for TinyOS are modules and configuration which deployed in students project are:-

  • Modules:

Module provides application code and ensures several interfaces.

  • Configurations:

We use configuration to assemble various components and link the interfaces which is provided by others.

Architecture of TinyOS simulator in WSN:

Based on Springer papers, we implement TinyOS architecture in WSN by component based model and event based model.

  • Component based model:
  • By clean interface we integrate simple function into components.
  • Using complex components we implement composing components.
  • Event based model:

We can interact with outside using an event. They are:

  • External Events: message event and clock event.
  • Internet Events: Triggered by external events.

Models for TinyOS Simulator:

We provide various models for TinyOS simulator and described as follows;

Data model:

We use parameters are:

  • Static memory allocation.
  • Local variables.
  • Global variables.

Thread model:

We consider the processes are:

  • Tasks.
  • Events.
  • Power aware two level scheduling.

Programming Model:

We use

  • Separate construction.
  • Modules construction.
  • Composition configuration.

Component model:

We deploy

  • Use and provide bidirectional interfaces.
  • Call and implement signal handle events and commands.

Network model:

  • TinyOS network stack handle media
  • Access control and single hop packet transmission.

Application of TinyOS Simulator:

We have depolyed 70+ TinyOS Simulator projects and we listed the applications are:

  • Transparent Base (apps/Transparent Base)
  • Generic Base (apps / generic Base).
  • To Base ( apps / To base)