Contiki - User contributions [en]

RSS measurement

2014-11-30T03:13:14Z

Nitin: /* Introduction */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the firmware later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of motes. You can select any number of motes, but for simplicity we are considering only 2 motes.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, see page 49 on this link http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Sensor acquisition

2014-11-23T06:44:20Z

Nitin: /* Generic Template for Creating Application on Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This article helps you learn how to create the Sensor Acquisition Program, which can be used to show the Temperature, Humidity and Light Intensity in the vicinity of Tmote Sky.

== How to start an application in Contiki ==

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application in Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Sensor acquisition

2014-11-23T06:43:48Z

Nitin: /* How to start an application on Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This article helps you learn how to create the Sensor Acquisition Program, which can be used to show the Temperature, Humidity and Light Intensity in the vicinity of Tmote Sky.

== How to start an application in Contiki ==

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:47:26Z

Nitin: /* Step 3 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 '''How to start an application in Contiki''' walk you through the complete process of writing you own application in Contiki. Section#3 '''Generic structure of Application in Contiki''' gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n",i);

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder (contiki/exmples/my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:43:45Z

Nitin: /* Step 4 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 '''How to start an application in Contiki''' walk you through the complete process of writing you own application in Contiki. Section#3 '''Generic structure of Application in Contiki''' gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder (contiki/exmples/my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:42:59Z

Nitin:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 '''How to start an application in Contiki''' walk you through the complete process of writing you own application in Contiki. Section#3 '''Generic structure of Application in Contiki''' gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:41:11Z

Nitin: /* Introduction */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 '''How to start an application in Contiki''' walk you through the complete process of writing you own application in Contiki. Section#3 '''Code''' contains the C code for a very simple application that prints "EE-652 is an awesome course at USC" on the terminal. Section#3 '''Generic structure of Application in Contiki''' gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:40:32Z

Nitin: /* Introduction */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 '''How to start an application in Contiki''' walk you through the complete process of writing you own application in Contiki. Section#3 '''Code''' contains the C code for a very simple application that prints "EE-652 is an awesome course at USC". Section#3 '''Generic structure of Application in Contiki''' gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:39:42Z

Nitin:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 How to start an application in Contiki walk you through the complete process of writing you own application in Contiki. Section#3 Code contains the C code for a very simple application that prints "EE-652 is an awesome course at USC". Section#3 Generic structure of Application in Contiki gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:38:32Z

Nitin: /* Introduction */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki. Section#2 [[How to start an application in Contiki]] walk you through the complete process of writing you own application in Contiki. Section#3 [[Code]] contains the C code for a very simple application that prints "EE-652 is an awesome course at USC". Section#3 [[Generic structure of Application in Contiki]] gives a generic skeleton of any application in contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:34:25Z

Nitin:

Build your own application in Contiki

2014-11-23T05:33:20Z

Nitin: /* Step 6 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit.

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:33:01Z

Nitin: /* Step 6 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

Then Press CTRL-C to quit

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:32:01Z

Nitin: /* How to start an application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:30:22Z

Nitin: /* Step 6 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>EE-652 is an awesome course at USC</code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:28:48Z

Nitin: /* How to start an application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

=== Step 6 ===

'''Upload the firmware on Tmote Sky''' - Plug the Tmote Sky in your computer. Then use the terminal window to go to contiki/examples/my_first_app and then write the following commands to upload your program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make my_first_app.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:24:20Z

Nitin: /* Step 3 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
'''Write my_first_app.c'''

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:23:49Z

Nitin: /* Step 4 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write my_first_app.c

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
'''Makefile''' - Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:23:22Z

Nitin: /* Step 5 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write my_first_app.c

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
'''Compilation''' - Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:22:23Z

Nitin:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write my_first_app.c

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

=== Step 4 ===
Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

=== Step 5 ===
Use terminal to go to "contiki/examples/my_first_app" directory. Once you are in this directory type "make". This will compile your code and generates all the supporting files like .csc file, symbols.c, symbols.h etc.

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:15:48Z

Nitin: /* Step 3 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write my_first_app.c

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

=== Step 4 ===
Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:14:59Z

Nitin: /* Step 3 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write C code.

<code><nowiki>
<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}
</nowiki></code>

Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

=== Step 4 ===
Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:12:37Z

Nitin: /* Step 4 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write C code. Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

=== Step 4 ===
Create makefile in the same folder(my_first_app)

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:11:45Z

Nitin: /* Generic C code for Application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write C code. Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic structure of Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

=== Step 4 ===
Create the makefile.

<code><nowiki>
CONTIKI_PROJECT = my_first_app
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:08:28Z

Nitin: /* How to start an application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

=== Step 1 ===
Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

=== Step 2 ===
Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

=== Step 3 ===
Write C code. Every process in Contiki should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:06:21Z

Nitin: /* Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

<Header Files>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:05:52Z

Nitin: /* Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
/* Declare variables required */
static int i=652;

/* Begin Process */
PROCESS_BEGIN();

/* Set of C statement(s) */
printf("EE-%d is an awesome course at USC\n");

/* Process End */
PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:04:52Z

Nitin: /* Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
static int i=652; /* Declare variables required */

PROCESS_BEGIN(); /* Begin Process */

printf("EE-%d is an awesome course at USC\n"); /* Set of C statement(s) */

PROCESS_END(); /* Process End */
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T05:03:05Z

Nitin: /* Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(my_first_app_process,"My_First_App");
AUTOSTART_PROCESSES(&my_first_app_process);

PROCESS_THREAD(my_first_app_process,ev,data)
{
static int i=652;

PROCESS_BEGIN();

printf("EE-%d is an awesome course at USC\n");

PROCESS_END();
}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T04:59:07Z

Nitin: /* Generic C code for Application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

<Header Files>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T04:58:11Z

Nitin: /* Generic Template for Creating Application on Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic C code for Application in Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T04:55:57Z

Nitin: /* How to start an application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

'''Content of my_first_app.c'''
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro called PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

File:Byaic 2.png

2014-11-23T04:53:20Z

Nitin: Nitin uploaded a new version of "File:Byaic 2.png"

File:Byaic 2.png

2014-11-23T04:51:20Z

Nitin:

Build your own application in Contiki

2014-11-23T04:51:00Z

Nitin: /* How to start an application in Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]

Now create a new C file named my_first_app.c

[[File:byaic_2.png|center|800px]]

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

File:Byaic 1.png

2014-11-23T04:46:36Z

Nitin: Nitin uploaded a new version of "File:Byaic 1.png"

File:Byaic 1.png

2014-11-23T04:44:26Z

Nitin:

Build your own application in Contiki

2014-11-23T04:43:49Z

Nitin: /* How to start an application on Contiki */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application in Contiki ==

Go to the directory contiki/examples and make new sub directory named my_first_app

[[File:byaic_1.png|center|800px]]
Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T04:33:38Z

Nitin: /* Introduction */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial help you understand how to build you own application in Contiki.

== How to start an application on Contiki ==

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Build your own application in Contiki

2014-11-23T04:31:37Z

Nitin: Created page with " Back to Contiki Tutorials __TOC__ == Introduction == This article helps you learn how to create the Sensor Acquisition Program, which can be used to..."

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This article helps you learn how to create the Sensor Acquisition Program, which can be used to show the Temperature, Humidity and Light Intensity in the vicinity of Tmote Sky.

== How to start an application on Contiki ==

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Contiki tutorials

2014-11-23T04:31:09Z

Nitin:

[[Main_Page | Back to Main Page]]

== List of Tutorials ==

Completed
# [[Installation]]
# [[Hello World]]
# [[Broadcast Example]]
# [[Collect View]]
# [[Contiki build system]]
# [[Interfacing with Python]]
# [[Sensor acquisition]] (light, temperature, humidity)

Need review
# [[Timers]] Tim, Leo
# [[CFS-Coffee]] Kevin

Starting
# [[Tutornet]] Pedro, Kwame
# [[Cooja Simulator]] (Getting started, debugging) Pedro
# [[Network Stack]] Yash
# [[CSMA]] Tim, Leo
# [[RSS measurement]] Nitin
# [[RPL objective function & simulation using DGRM model in cooja ]] Ashwini Telang
# [[RPL UDP]] Jiahao Liang
# [[MAC protocols in ContikiOS]] Pedro
# [[RPL Border Router]] Chhavi
# [[REST example running on Cooja and Sky motes]] Mrunal Muni
# [[Trickle library]] Subhashini Sundaresan
# [[Packetbuffer Basics]] Pradipta
# [[Antelope(Database Management System) - Contiki]] Gopi Krishna
# [[Mobility of Nodes in Cooja]] Pratyush Deshpande
# [[Contiki Shell]] Abhilash Nagaraj Hegde
# [[Contiki Coffee File System]] Zhikun Liu
# [[Contiki Programming Guide]] Haimo Bai
# [[Analyse of a real 6LoWPAN network using a Contiki-based sniffer module]] Yash Goyal
# [[Build your own application in Contiki]] Nitin





<pre style="color: red">Be sure to include references in your tutorials, especially if you quote material from other sites!</pre>

Build your own application on Contiki

2014-11-23T04:30:41Z

Nitin: Created page with " Back to Contiki Tutorials __TOC__ == Introduction == This tutorial helps you to understand how to build your own application in Contiki. == How to ..."

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to build your own application in Contiki.

== How to start an application on Contiki ==

Every process should start with the PROCESS macro. It takes two arguments
*name: The variable name of the process structure.
*strname: The string representation of the process name.
<code><nowiki> PROCESS(name,strname) </nowiki></code>

Then comes another macro AUTOSTART_PROCESS(struct process &). AUTOSTART_PROCESSES automatically starts the process(es) given in the argument(s) when the module boots.
*&name: Reference to the process name.
<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

Then we call the PROCESS_THREAD function. This function is used to define the protothread of a process. The process is called whenever an event occurs in the system.Each process in the module requires an event handler under the PROCESS_THREAD macro.
*name: The variable name of the process structure.
*process_event_t: The variable of type character.If this variable is same as PROCESS_EVENT_EXIT then PROCESS_EXITHANDLER is invoked.
<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

Then comes the PROCESS_BEGIN macro. This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.
<code><nowiki>PROCESS_BEGIN() </nowiki></code>

Then we write the set of C statements as per the requirement of the application.

At the end we use another macro PROCESS_END. This macro defines the end of a process. It must appear in a PROCESS_THREAD() definition and must always be included. The process exits when the PROCESS_END() macro is reached.
<code><nowiki> PROCESS_END() </nowiki></code>

== Generic Template for Creating Application on Contiki ==

<code><nowiki>

PROCESS(name,strname);
AUTOSTART_PROCESSES(struct process &);

PROCESS_THREAD(name, process_event_t, process_data_t)
{

----Initialization of required variables----

PROCESS_BEGIN();

---Set of C statements---

PROCESS_END();

}

</nowiki></code>

== Sensor Acquisition Program on the Tmote Sky! ==

=== Step 1 ===

Using the opened terminal window compile and upload the Sensor Acquisition program on the Tmote Sky.

:: <code>make TARGET=sky savetarget</code> (This save the target for any future compilations)
:: <code>make sensor-acq.upload</code> (This will upload the code on the Tmote Sky)
:: <code>make login</code> (This will enable us to view the output. If permission error occurs, use sudo command at the beginning)
See the following link for troubleshooting - http://anrg.usc.edu/contiki/index.php/Troubleshooting

=== Step 2 ===

Press the reset button on the Tmote Sky. The following message will appear on the terminal window

:: <code>Temperature=28.04 C (6764)</code>
:: <code>Humidity=73.20% (2259)</code>
:: <code>Light=38.26 lux (94)</code>

Values inside the round brackets (ex 6764, 2259 and 94) are the actual sensor values and the calibrated values can be obtained by performing calculations on these sensor values. You can find the calculations at
http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

=== Step 3 ===

Press Ctrl-C to quit.

== Code ==

<code><nowiki>

PROCESS(sensor_acq_process,"Sensor Acquisition");
AUTOSTART_PROCESSES(&sensor_acq_process);

PROCESS_THREAD(sensor_acq_process,ev,data)
{
static struct etimer et;
static int val;
static struct sensors_sensor *sensor;
static float s = 0;
static int dec;
static float frac;

PROCESS_BEGIN();

printf("Starting Sensor Example.\n");

while(1)
{
etimer_set(&et, CLOCK_SECOND * 2);
SENSORS_ACTIVATE(light_sensor);
SENSORS_ACTIVATE(sht11_sensor);

PROCESS_WAIT_EVENT_UNTIL(etimer_expired(&et));

val = sht11_sensor.value(SHT11_SENSOR_TEMP);
if(val != -1)
{
s= ((0.01*val) - 39.60);
dec = s;
frac = s - dec;
printf("\nTemperature=%d.%02u C (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val=sht11_sensor.value(SHT11_SENSOR_HUMIDITY);
if(val != -1)
{
s= (((0.0405*val) - 4) + ((-2.8 * 0.000001)*(pow(val,2))));
dec = s;
frac = s - dec;
printf("Humidity=%d.%02u % (%d)\n", dec, (unsigned int)(frac * 100),val);
}

val = light_sensor.value(LIGHT_SENSOR_TOTAL_SOLAR);
if(val != -1)
{
s = (float)(val * 0.4071);
dec = s;
frac = s - dec;
printf("Light=%d.%02u lux (%d)\n", dec, (unsigned int)(frac * 100),val);
}

etimer_reset(&et);
SENSORS_DEACTIVATE(light_sensor);
SENSORS_DEACTIVATE(sht11_sensor);

} //end of while

PROCESS_END();

}

</nowiki></code>

== Understanding the Code ==

::<code>etimer_set(&et, CLOCK_SECOND * 2);</code>
This will set the timer to repeat the iterations every 2 seconds.

::<code>SENSORS_ACTIVATE(light_sensor);</code>
::<code>SENSORS_ACTIVATE(sht11_sensor);</code>
We need to activate light_sensor for measuring the light intensity and sht11_sensor for the measurement of temperature and humidity.

::<code>val = sht11_sensor.value(SHT11_SENSOR_TEMP);</code>
Here we are capturing the actual sensor value.

::<code>s = ((0.01*val) - 39.60);</code>
We need to calibrate the sensor values by doing some calculations. You can find the calculations here: http://tinyos.stanford.edu/tinyos-wiki/index.php/Boomerang_ADC_Example

::<code>SENSORS_DEACTIVATE(light_sensor);</code>
::<code>SENSORS_DEACTIVATE(sht11_sensor);</code>
After we are done with the calculations, we need to deactivate the sensors.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

Contiki tutorials

2014-11-23T04:27:59Z

Nitin:

[[Main_Page | Back to Main Page]]

== List of Tutorials ==

Completed
# [[Installation]]
# [[Hello World]]
# [[Broadcast Example]]
# [[Collect View]]
# [[Contiki build system]]
# [[Interfacing with Python]]
# [[Sensor acquisition]] (light, temperature, humidity)

Need review
# [[Timers]] Tim, Leo
# [[CFS-Coffee]] Kevin

Starting
# [[Tutornet]] Pedro, Kwame
# [[Cooja Simulator]] (Getting started, debugging) Pedro
# [[Network Stack]] Yash
# [[CSMA]] Tim, Leo
# [[RSS measurement]] Nitin
# [[RPL objective function & simulation using DGRM model in cooja ]] Ashwini Telang
# [[RPL UDP]] Jiahao Liang
# [[MAC protocols in ContikiOS]] Pedro
# [[RPL Border Router]] Chhavi
# [[REST example running on Cooja and Sky motes]] Mrunal Muni
# [[Trickle library]] Subhashini Sundaresan
# [[Packetbuffer Basics]] Pradipta
# [[Antelope(Database Management System) - Contiki]] Gopi Krishna
# [[Mobility of Nodes in Cooja]] Pratyush Deshpande
# [[Contiki Shell]] Abhilash Nagaraj Hegde
# [[Contiki Coffee File System]] Zhikun Liu
# [[Contiki Programming Guide]] Haimo Bai
# [[Analyse of a real 6LoWPAN network using a Contiki-based sniffer module]] Yash Goyal
# [[Build your own application on Contiki]] Nitin





<pre style="color: red">Be sure to include references in your tutorials, especially if you quote material from other sites!</pre>

RSS measurement

2014-11-23T02:58:52Z

Nitin: /* Understanding the Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the firmware later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of motes. You can select any number of motes, but for simplicity we are considering only 2 motes.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, see page 49 on this link http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin

RSS measurement

2014-11-23T02:57:58Z

Nitin: /* Step 5 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the firmware later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of motes. You can select any number of motes, but for simplicity we are considering only 2 motes.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, see page 49 on this link http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

RSS measurement

2014-11-23T02:56:34Z

Nitin: /* Step 3 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the firmware later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of new motes=2.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, see page 49 on this link http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

RSS measurement

2014-11-23T02:54:45Z

Nitin: /* Understanding the Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the code later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of new motes=2.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, see page 49 on this link http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

RSS measurement

2014-11-23T02:53:04Z

Nitin: /* Understanding the Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the code later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of new motes=2.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, follow [http://web.stanford.edu/class/cs244e/papers/cc2420.pdf]

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

RSS measurement

2014-11-23T02:52:15Z

Nitin: /* Understanding the Code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the code later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of new motes=2.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

To understand the calculations performed in recv() function, follow [[Media:http://web.stanford.edu/class/cs244e/papers/cc2420.pdf]]

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf

RSS measurement

2014-11-23T02:48:14Z

Nitin: /* Step 7 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial helps you to understand how to measure Radio Signal Strength (RSS) received by a Tmote Sky. In this tutorial we have one sender and one receiver. Receiver receives the packet and display the RSS value of the packet received.

You can find the step by step simulation in the next section "RSS Measurement Program on Cooja" and you can find the C code in the subsequent section.

== RSS Measurement Program on Cooja ==

=== Step 1 ===
Create New Simulation on Cooja. Let's say we call our simulation as "RSS".

[[File:RSS_1.png|center|800px]]

=== Step 2 ===
Create Motes.

[[File:RSS_2.png|center|800px]]

=== Step 3 ===
Browse the firmware.
Note: You can find the code later in this tutorial.

[[File:RSS_3.png|center|800px]]

=== Step 4 ===
Compile the firmware.

[[File:RSS_4.png|center|800px]]

=== Step 5 ===
Select number of new motes=2.
Note: We are uploading same firmware on both the motes. One will act as Sender and another will act as Receiver.

[[File:RSS_5.png|center|800px]]

=== Step 6 ===
Start the simulation.

[[File:RSS_6.png|center|800px]]

=== Step 7 ===
You can see the RSSI value in the mote output window. These RSSI values are in '''dBm'''.

[[File:RSS_7.png|center|800px]]

== Code ==

<code><nowiki>
<HEADER FILES>

static struct collect_conn tc;

PROCESS(example_collect_process, "RSS Measurement");
AUTOSTART_PROCESSES(&example_collect_process);

static void recv(const rimeaddr_t *originator, uint8_t seqno, uint8_t hops)
{
static signed char rss;
static signed char rss_val;
static signed char rss_offset;
printf("Sink got message from %d.%d, seqno %d, hops %d: len %d '%s'\n",originator->u8[0], originator->u8[1],seqno, hops,packetbuf_datalen(),
(char *)packetbuf_dataptr());
rss_val = cc2420_last_rssi;
rss_offset=-45;
rss=rss_val + rss_offset;
printf("RSSI of Last Packet Received is %d\n",rss);
}

static const struct collect_callbacks callbacks = { recv };

PROCESS_THREAD(example_collect_process, ev, data)
{
static struct etimer periodic;
static struct etimer et;

PROCESS_BEGIN();

collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);

if(rimeaddr_node_addr.u8[0] == 1 && rimeaddr_node_addr.u8[1] == 0)
{
printf("I am sink\n");
collect_set_sink(&tc, 1);
}

/* Allow some time for the network to settle. */
etimer_set(&et, 120 * CLOCK_SECOND);
PROCESS_WAIT_UNTIL(etimer_expired(&et));

while(1)
{

/* Send a packet every 1 seconds. */
if(etimer_expired(&periodic))
{
etimer_set(&periodic, CLOCK_SECOND * 1 );
etimer_set(&et, random_rand() % (CLOCK_SECOND * 1));
}

PROCESS_WAIT_EVENT();

if(etimer_expired(&et))
{
static rimeaddr_t oldparent;
const rimeaddr_t *parent;
if(rimeaddr_node_addr.u8[0] != 1 )
{
printf("Sending\n");
packetbuf_clear();
packetbuf_set_datalen(sprintf(packetbuf_dataptr(),"%s", "Fight On") + 1);
collect_send(&tc, 15);

parent = collect_parent(&tc);
if(!rimeaddr_cmp(parent, &oldparent))
{
if(!rimeaddr_cmp(&oldparent, &rimeaddr_null))
{
printf("#L %d 0\n", oldparent.u8[0]);
}
if(!rimeaddr_cmp(parent, &rimeaddr_null))
{
printf("#L %d 1\n", parent->u8[0]);
}

rimeaddr_copy(&oldparent, parent);
}
}
}

} //end of while

PROCESS_END();
} //end of process thread
</nowiki></code>

== Understanding the Code ==

::<code>1-static const struct collect_callbacks callbacks = { recv };</code>
callbacks = { recv } calls the recv() function when a packet is received.

::<code>2-collect_open(&tc, 130, COLLECT_ROUTER, &callbacks);</code>
Opens a connection.

::<code>3-collect_set_sink(&tc, 1);</code>
Sets the node as sink. Note that we are setting node 1.0 as the sink here.

::<code>4-collect_send(&tc, 15);</code>
Sends data through the link.

::<code>5-etimer_set(&et, CLOCK_SECOND * 1);</code>
This will set the timer to repeat the iterations every 1 seconds.

::<code>6-if(rimeaddr_node_addr.u8[0] != 1 )</code>
This if condition will work only for the source nodes i.e. node id != 1.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by : Nitin
http://web.stanford.edu/class/cs244e/papers/cc2420.pdf