Sensor network have now evolved and reached to the corporate house. This is why I am placed here. TinyOS is widely used. No other operating systems have such popularity. All effort has been made to have sensor network a better lifetime in the terms of battery. The structure of tinyOS is based on event, task and component. The code is divided in multiple components and all the components are wired together in proper order to let it work properly. An event is created using timing. For example starting a timer for counter application is an event. Stopping the same timer will be another event. However, counting a sequence will be termed as a task. All this arrangement has been done to save power. The idea is use only those components in your system which you need instantaneously. Once you have used that component abandon it. In this process power will be given to those processes only when you need it. So this idea of hurry up and sleep left with us so many problems.

Firstly, if the sensing system doesn’t not respond promptly, you will end up assuming that a particular task is completed and when you allow other task to access the same component conflict of interests will occur and your mote program will get crashed. Once it happens, you know! you have no other option, but to reprogram the motes again. We have observed this problem several times.

This has been done just to minimize the power consumption. This particular arrangement is not recommended in industrial scenario where abundance of power is available. It is also not recommended in the home automation where there is no dearth of power. So from critic’s point of view is it recommended only for wild life monitoring system where power is scarce? 

Mera nam kya hai