Presentation is loading. Please wait.

Presentation is loading. Please wait.

TinyOS Applications Advanced Computer Networks. TinyOS Applications Outline  AntiTheft Example –LEDs, timer, booting  Sensing Example –Light Sensor.

Published byCharleen Barrett Modified over 9 years ago

Similar presentations

Presentation on theme: "TinyOS Applications Advanced Computer Networks. TinyOS Applications Outline  AntiTheft Example –LEDs, timer, booting  Sensing Example –Light Sensor."— Presentation transcript:

1 TinyOS Applications Advanced Computer Networks

2 TinyOS Applications Outline  AntiTheft Example –LEDs, timer, booting  Sensing Example –Light Sensor –Wiring to AntiTheft  Single Hop Networks –Active Messages interface –Sending packets –Receiving packets Advanced Computer Networks TinyOS Applications 2

3 AntiTheft Example [List 6.1] module AntiTheftC { uses { uses { interface Boot; interface Boot; interface Timer as WarningTimer; interface Timer as WarningTimer; interface Leds; interface Leds; }} implementation { enum { WARN_INTERVAL = 4096, WARN_DURATION = 64 }; enum { WARN_INTERVAL = 4096, WARN_DURATION = 64 }; Advanced Computer Networks TinyOS Applications 3 can only declare integer constants

4 AntiTheft Example [List 6.1] event void WarningTimer.fired ( ) { if (call Leds.get ( ) & LEDS_LED0) if (call Leds.get ( ) & LEDS_LED0) { /* Red LED is on. Turn it off, will switch on again in 4096 – 64 ms. */ { /* Red LED is on. Turn it off, will switch on again in 4096 – 64 ms. */ call Leds.led0Off ( ); call Leds.led0Off ( ); call WarningTimer.startOneShot ( WARN_INTERVAL – call WarningTimer.startOneShot ( WARN_INTERVAL – WARN_DURATION); WARN_DURATION); } else else { // Red LED is off. Turn it on for 64 ms. { // Red LED is off. Turn it on for 64 ms. call Leds.led0On ( ); call Leds.led0On ( ); call WarningTimer.startOneShot (WARN_DURATION); call WarningTimer.startOneShot (WARN_DURATION); }} Advanced Computer Networks TinyOS Applications 4

5 event void Boot.booted ( ) { /* We just booted. Perform first /* We just booted. Perform first LED transition */ LED transition */ signal WarningTimer.fired ( ); signal WarningTimer.fired ( ); }} interface Leds { [List 6.2] … async command void led0On ( ); async command void led0On ( ); async command void led0Off ( ); async command void led0Off ( ); async command uint8_t get ( ); async command uint8_t get ( );} Advanced Computer Networks TinyOS Applications 5 AntiTheft Example [List 6.1] software signal

6 AntiTheft configuration [List 6.6] configuration AntiTheftAppC { } implementation { components AntiTheftC, MainC, LedsC; components AntiTheftC, MainC, LedsC; components new TimerMilliC ( ) as WTimer; components new TimerMilliC ( ) as WTimer; AntiTheftC.Boot -> MainC; AntiTheftC.Boot -> MainC; AntiTheftC.Leds -> LedsC; AntiTheftC.Leds -> LedsC; AntiTheftC.WarningTimer -> WTimer; AntiTheftC.WarningTimer -> WTimer;} Advanced Computer Networks TinyOS Applications 6

7 Sensing Example  TinyOS provides two standard interfaces for reading sensor samples –Read :: acquire a single sample –ReadStream :: sample at a fixed rate. interface Read { command error_t read ( ); command error_t read ( ); event void readDone (error_t, val_t val ); event void readDone (error_t, val_t val );} Advanced Computer Networks TinyOS Applications 7

8 Sensing Example [List 6.8] module DarkC { uses { uses { interface Boot; interface Boot; interface Leds; interface Leds; interface Timer as TheftTimer; interface Timer as TheftTimer; interface Read as Light; interface Read as Light; }} Advanced Computer Networks TinyOS Applications 8

9 Sensing Example [List 6.8] implementation { enum { DARK_INTERVAL = 256, DARK_THRESHOLD = 200}; enum { DARK_INTERVAL = 256, DARK_THRESHOLD = 200}; event void Boot.booted ( ) { event void Boot.booted ( ) { call TheftTimer.startPeriodic ( DARK_INTERVAL); call TheftTimer.startPeriodic ( DARK_INTERVAL); } event void TheftTimer.fired ( ) { event void TheftTimer.fired ( ) { call Light.read ( ); //Initiate split-phase light sampling call Light.read ( ); //Initiate split-phase light sampling } Advanced Computer Networks TinyOS Applications 9

10 Sensing Example [List 6.8] /* Light sample completed. Check if it is a theft. */ event void Light.readDone (error_t ok,uint16_t val) { event void Light.readDone (error_t ok,uint16_t val) { if (ok == SUCCESS && val < DARK_THRESHOLD) if (ok == SUCCESS && val < DARK_THRESHOLD) call Leds.led2On ( ); /* Alert! Alert! */ call Leds.led2On ( ); /* Alert! Alert! */ else else call Leds.led2Off( ); /* Don’t leave LED on */ call Leds.led2Off( ); /* Don’t leave LED on */ }} Advanced Computer Networks TinyOS Applications 10

11 Sensor Components  Sensors are represented in TinyOS by generic components, e.g., PhotoC for the light sensor on the mts310 board. generic configuration PhotoC ( ) { provides interface Read ; provides interface Read ;} Advanced Computer Networks TinyOS Applications 11

12 AntiTheft Light Sensor Wiring [List 6.9] configuration AntiTheftAppC { } implementation { … /* the wiring for the blinking Red LED */ components DarkC; components DarkC; components new TimerMilliC ( ) as TTimer; components new TimerMilliC ( ) as TTimer; components new PhotoC ( ); components new PhotoC ( ); DarkC.Boot -> MainC; DarkC.Boot -> MainC; DarkC.Leds -> LedsC; DarkC.Leds -> LedsC; DarkC.TheftTimer -> Ttimer; DarkC.TheftTimer -> Ttimer; DarkC.Light -> PhotoC; DarkC.Light -> PhotoC;} Advanced Computer Networks TinyOS Applications 12

13 Single Hop Networks  TinyOS uses a layered network structure where each layer defines a header and footer layout.  The lowest exposed network layer in TinyOS is called active messages (AM).  AM is typically implemented directly over a mote’s radio providing unreliable, single hop packet transmission and reception. Advanced Computer Networks TinyOS Applications 13

14 Single Hop Networks  Packets are identified by an 8-bit packet type.  ‘Active Messages’ indicates the type is used automatically to dispatch received packets to an appropriate handler.  Each packet holds a user-specified payload of up to TOSH_DATA_LENGTH bytes (normally 28 bytes)**.  A variable of type message_t holds a single AM packet. ** changeable at compile time. Advanced Computer Networks TinyOS Applications 14

15 Platform-Independent Types  TinyOS has traditionally used structs to define message formats and directly access messages.  Platform-independent structs are declared with nx_struct and every field of a platform-independent struct must be a platform-independent type. nx_uint16_t val ; // A big-endian 16-bit value nxle_uint32_t otherval; // A litte-endian 32-bit value Advanced Computer Networks TinyOS Applications 15

16 TinyOS 2.0 CC2420 Header [List 3.32] typedef nx_struct cc2420_header_t ** { typedef nx_struct cc2420_header_t ** { nxle_uint8_t length; nxle_uint8_t length; nxle_uint16_t fcf; nxle_uint16_t fcf; nxle_uint8_t dsn; nxle_uint8_t dsn; nxle_uint16_t destpan; nxle_uint16_t destpan; nxle_uint16_t dest; nxle_uint16_t dest; nxle_uint16_t src; nxle_uint16_t src; nxle_uint8_t type; nxle_uint8_t type; } cc2420_header_t; } cc2420_header_t; The CC2420 expects all fields to be little-endian. Advanced Computer Networks TinyOS Applications 16

17 Theft Report Payload Platform-independent struct in the antitheft.h header file: #ifndef ANTITHEFT_H #define ANTITHEFT_H typedef nx_struct theft { nx_uint16_t who; nx_uint16_t who; } theft_t; …#endif Advanced Computer Networks TinyOS Applications 17 struct to define payload

18 AMSend Interface [List 6.12]  Contains all the commands needed to fill in and send packets: interface AMSend { command error_t send (am_addr_t addr, message_t* msg, uint8_t len); command error_t send (am_addr_t addr, message_t* msg, uint8_t len); event void sendDone (message_t* msg, error_t error); event void sendDone (message_t* msg, error_t error); command error_t cancel (message_t* msg); command error_t cancel (message_t* msg); command uint8_t maxPayLoadLength ( ); command uint8_t maxPayLoadLength ( ); command void* getPayLoad (message_t* msg, uint8_t len); command void* getPayLoad (message_t* msg, uint8_t len);} Advanced Computer Networks TinyOS Applications 18

19 Sending Report-Theft Packets [List 6.13] uses interface AMSend as Theft; … message_t reportMsg; bool sending; void reportTheft ( ) { theft_t* payload = call Theft.getPayload (&reportMsg, theft_t* payload = call Theft.getPayload (&reportMsg, sizeof (theft_t) ); sizeof (theft_t) ); if (payload && !sending) if (payload && !sending) { //Payload fits and we are idle – Send packet { //Payload fits and we are idle – Send packet payload->who = TOS_NODE_ID; //Report being stolen! payload->who = TOS_NODE_ID; //Report being stolen! //Broadcast the report packet to everyone //Broadcast the report packet to everyone if (call Theft.send(TOS_BCAST_ADDR, &reportMsg, if (call Theft.send(TOS_BCAST_ADDR, &reportMsg, sizeof (theft_t) ) == SUCCESS) sizeof (theft_t) ) == SUCCESS) }} Advanced Computer Networks TinyOS Applications 19

20 event void Theft.sendDone (message_t *msg, error_t error) { error_t error) { sending = FALSE; //Our send completed sending = FALSE; //Our send completed} Advanced Computer Networks TinyOS Applications 20 Sending Report-Theft Packets [List 6.13]

21 Generic AMSenderC configuration generic configuration AMSenderC (am_id_t AMId) { provides { provides { interface AMSend; interface AMSend; interface Packet; interface Packet; interface AMPacket; interface AMPacket; interface PacketAcknowledgements as Acks; interface PacketAcknowledgements as Acks; }} Advanced Computer Networks TinyOS Applications 21

22 Communication Stack Cannot switch itself on and off on- demand, and needs the SplitControl interface to start and stop the radio: interface SplitControl { [List 6.14] command error_t start ( ); command error_t start ( ); event void startDone (error_t error); event void startDone (error_t error); command error_t stop ( ); command error_t stop ( ); event void stopDone (error_t error); event void stopDone (error_t error);} Advanced Computer Networks TinyOS Applications 22

23 MovingC using SplitControl uses interface SplitControl as CommControl; … event void Boot.booted ( ) { call CommControl.start ( ) ; call CommControl.start ( ) ;} event void CommControl.startDone (error_t ok) { //Start checks once communication stack is ready //Start checks once communication stack is ready call TheftTimer.startPeriodic ( ACCEL_INTERVAL ); call TheftTimer.startPeriodic ( ACCEL_INTERVAL );} event void CommControl.stopDone (error_t ok) { } Advanced Computer Networks TinyOS Applications 23

24 Moving C Receiving Packet  MovingC receives a packet payload (defined as a struct contained in a header file) that contains acceleration settings for detecting movement of the mote: typedef nx_struct settings { nx_uint16_t accerVariance; nx_uint16_t accerVariance; nx_uint16_t accelInterval; nx_uint16_t accelInterval; } settings_t; Advanced Computer Networks TinyOS Applications 24 struct to define payload

25 AM Packet Reception  Provided by the TinyOS Receive interface: interface Receive { event message_t* receive(message_t* msg, event message_t* receive(message_t* msg, void* payload, uint8_t len); void* payload, uint8_t len);} Receive.receive, as a receive “handler”, receives a packet buffer which it can simply return or return as a different buffer if the handler wants to hold onto buffer. Advanced Computer Networks TinyOS Applications 25

26 MovingC Receiving Packet [List 6.16] uses interface Receive as Setting; … uint16_t accelVariance = ACCEL_VARIANCE ; event message_t *Settings.receive (message_t *msg, void *payload, uint8_t len) { void *payload, uint8_t len) { if (len >= sizeof (settings_t)) //Check for valid packet if (len >= sizeof (settings_t)) //Check for valid packet { /* Read settings by casting payload to settings_t, { /* Read settings by casting payload to settings_t, reset check interval */ reset check interval */ settings_t *settings = payload; settings_t *settings = payload; accelVariance = setting->accelVariance; accelVariance = setting->accelVariance; call TheftTimer.startPeriodic (setting->accelInterval); call TheftTimer.startPeriodic (setting->accelInterval); } return msg: return msg:} Advanced Computer Networks TinyOS Applications 26

27 TinyOS Applications Summary  AntiTheft Example –LEDs, Timer, Boot –get, enum  Sensing Example –Light Sensor –Read (split-phase) –Wiring to AntiTheft –Two Timer instances Advanced Computer Networks TinyOS Applications 27

28 TinyOS Applications Summary  Single Hop Networks –Active Messages, typed messages –Platform-independent types  Sending packets –AMSenderC generic configuration –SplitControl of Radio Stack –Structs for packet payloads  Receiving packets –Implemented as a receive event handler. Advanced Computer Networks TinyOS Applications 28

Download ppt "TinyOS Applications Advanced Computer Networks. TinyOS Applications Outline  AntiTheft Example –LEDs, timer, booting  Sensing Example –Light Sensor."

Similar presentations

David Culler, Jason Hill, Robert Szewczyk, Alec Woo U.C. Berkeley 2/9/2001 TinyOS Programming Boot Camp Part IV – Tiny OS 4.3 Component Overview.

David Culler, Jason Hill, Robert Szewczyk, Alec Woo U.C. Berkeley 2/9/2001 TinyOS Programming Boot Camp Part IV – Tiny OS 4.3 Component Overview.
How to use TinyOS Jason Hill Rob Szewczyk Alec Woo David Culler An event based execution environment for Networked Sensors.

How to use TinyOS Jason Hill Rob Szewczyk Alec Woo David Culler An event based execution environment for Networked Sensors.
TinyOS 2.0 Network Stack Enhancements Joseph PolastrePhil Levis UC Berkeley UC Berkeley Moteiv Corporation.

TinyOS 2.0 Network Stack Enhancements Joseph PolastrePhil Levis UC Berkeley UC Berkeley Moteiv Corporation.
David Gay, Intel Research Berkeley with Phil Levis, Vlado Handziski, Jonathan Hui, Jan-Hinrich Hauer, Ben Greenstein, Martin Turon, Kevin Klues, Cory Sharp,

David Gay, Intel Research Berkeley with Phil Levis, Vlado Handziski, Jonathan Hui, Jan-Hinrich Hauer, Ben Greenstein, Martin Turon, Kevin Klues, Cory Sharp,
1 Tomás Sánchez López July 9, 2004 Real-time & Embedded Systems Laboratory TinyOS … in deep.

1 Tomás Sánchez López July 9, 2004 Real-time & Embedded Systems Laboratory TinyOS … in deep.
R4 Dynamically loading processes. Overview R4 is closely related to R3, much of what you have written for R3 applies to R4 In R3, we executed procedures.

R4 Dynamically loading processes. Overview R4 is closely related to R3, much of what you have written for R3 applies to R4 In R3, we executed procedures.
NesC Prepared for the Multimedia Networks Group University of Virginia.

NesC Prepared for the Multimedia Networks Group University of Virginia.
NesC: A Programming Language for Motes David Gay, Phil Levis, Eric Brewer, Rob von Behren, Nikita Borisov, Mike Chen, David Culler Intel Research, UC Berkeley.

NesC: A Programming Language for Motes David Gay, Phil Levis, Eric Brewer, Rob von Behren, Nikita Borisov, Mike Chen, David Culler Intel Research, UC Berkeley.
Feb 2007WSN Training: First Steps in nesC Programming1 First Steps in TinyOS and nesC Programming Topics  Timer Application: MyApp  Application directory.

Feb 2007WSN Training: First Steps in nesC Programming1 First Steps in TinyOS and nesC Programming Topics  Timer Application: MyApp  Application directory.
1 Lab 3 Objectives  Case study: “Hello world” program on motes  Write you first program on mote.

1 Lab 3 Objectives  Case study: “Hello world” program on motes  Write you first program on mote.
Peek into TinyOS Programs Vinod Kulathumani. 2 Basics Application consists of one or more components assembled, or wired A component provides and uses.

Peek into TinyOS Programs Vinod Kulathumani. 2 Basics Application consists of one or more components assembled, or wired A component provides and uses.
1 Lab4 Objectives  Learn to read light sensor data from sensor board  Learn to transmit a message containing the sensed data  through Mote serial port.

1 Lab4 Objectives  Learn to read light sensor data from sensor board  Learn to transmit a message containing the sensed data  through Mote serial port.
INTRODUCTION TO TINYOS 2.X AND NESC. Anatomy of TelosB Mote  Limited computational and communication resources  MSP430 16-bit microcontroller 10kB RAM.

INTRODUCTION TO TINYOS 2.X AND NESC. Anatomy of TelosB Mote  Limited computational and communication resources  MSP bit microcontroller 10kB RAM.
TinyOS Introduction Advanced Computer Networks. TinyOS Outline  Introduction to the Architecture of TinyOS and nesC  Component Model –Components, interfaces,

TinyOS Introduction Advanced Computer Networks. TinyOS Outline  Introduction to the Architecture of TinyOS and nesC  Component Model –Components, interfaces,
7/13/2007AIIT Summer Course - D#1 Wireless Embedded Systems and Networking Lab Day 5: Part 1: TinyOS Programming on Open Source Distribution Jaein Jeong.

7/13/2007AIIT Summer Course - D#1 Wireless Embedded Systems and Networking Lab Day 5: Part 1: TinyOS Programming on Open Source Distribution Jaein Jeong.
1 TinyOS Network Communication Computer Network Programming Wenyuan Xu Fall 2007.

1 TinyOS Network Communication Computer Network Programming Wenyuan Xu Fall 2007.
Radio Stack Iteration How to improve the CC1000 Joe Polastre January 15, 2004 NEST Retreat.

Radio Stack Iteration How to improve the CC1000 Joe Polastre January 15, 2004 NEST Retreat.
Development of a Mica2 Mote Sensor Network Cliff Macklin Bill Ehrbar December 8, 2004 University of Colorado, Colorado Springs.

Development of a Mica2 Mote Sensor Network Cliff Macklin Bill Ehrbar December 8, 2004 University of Colorado, Colorado Springs.
TinyOS Software Engineering Sensor Networks for the Masses.

TinyOS Software Engineering Sensor Networks for the Masses.
2008EECS194-51 Embedded Network Programming nesC, TinyOS, Networking, Microcontrollers Jonathan Hui University of California, Berkeley.

2008EECS Embedded Network Programming nesC, TinyOS, Networking, Microcontrollers Jonathan Hui University of California, Berkeley.

Similar presentations

Ads by Google