Contiki - User contributions [en]

Troubleshooting

2014-05-12T05:07:29Z

Lgadde: /* Problem with compling */

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. You will then have to re-login to or reboot your computer for the changes to take effect. You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Problem with compling in Cooja =====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

LD example-netflood.sky
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3):
relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
collect2: ld returned 1 exit status
make: *** [example-netflood.sky] Error 1

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the Makefile of the currently compling program and remove the line which looks similar to the following.

CFLAGS += -g

Troubleshooting

2014-04-25T23:57:35Z

Lgadde: /* Problem with compling */

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. You will then have to re-login to or reboot your computer for the changes to take effect. You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Problem with compling =====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

LD example-netflood.sky
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3):
relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
collect2: ld returned 1 exit status
make: *** [example-netflood.sky] Error 1

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the make file of the currently compling program and remove the line which looks similar to the following.

CFLAGS += -g

Troubleshooting

2014-04-25T23:55:39Z

Lgadde: /* = Problem with compling */

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. You will then have to re-login to or reboot your computer for the changes to take effect. You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Problem with compling =====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

LD example-netflood.sky
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
collect2: ld returned 1 exit status
make: *** [example-netflood.sky] Error 1

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the make file of the currently compling program and remove the line which looks similar to the following.

CFLAGS += -g

Troubleshooting

2014-04-25T23:54:08Z

Lgadde:

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. You will then have to re-login to or reboot your computer for the changes to take effect. You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Problem with compling ====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

<code><nowiki>LD example-netflood.sky</nowiki></code>
<code><nowiki>/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</nowiki></code>
<code><nowiki>collect2: ld returned 1 exit status</nowiki></code>
<code><nowiki>make: *** [example-netflood.sky] Error 1</nowiki></code>

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the make file of the currently compling program and remove the line which looks similar to the following.

CFLAGS += -g

Troubleshooting

2014-03-06T05:27:23Z

Lgadde:

Troubleshooting

2014-03-06T05:26:54Z

Lgadde:

Troubleshooting

2014-03-06T05:23:40Z

Lgadde:

Troubleshooting

2014-03-06T05:22:13Z

Lgadde:

Troubleshooting

2014-03-06T05:21:30Z

Lgadde:

Troubleshooting

2014-03-06T05:20:30Z

Lgadde:

Troubleshooting

2014-03-06T05:19:58Z

Lgadde:

Troubleshooting

2014-03-06T05:18:20Z

Lgadde:

Troubleshooting

2014-03-06T05:17:27Z

Lgadde: /* Issue with make login */

Troubleshooting

2014-03-06T05:15:04Z

Lgadde: /* Issue with make login */

Troubleshooting

2014-03-06T05:13:08Z

Lgadde:

Troubleshooting

2014-03-06T05:12:10Z

Lgadde: /* Permission denied */

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

To resolve the issue, simply use the following command:
sudo adduser <username> dialout

If that doesnot work
If you are getting an error
/dev/ttyUSB0 Can't open port
Error 1
followed by errors in the make file

Trying the following command which should give the desired output
make TARGET=sky sky-motelist
(sky can be replaced by the mote which is being used e.g z1)

The desired output
../../tools/sky/motelist-linux
Reference Device Description
---------- ---------------- ---------------------------------------------
M4A7J5HF /dev/ttyUSB0 Moteiv tmote sky

This means it is a common serial port connection problem with Ubuntu 12.04 LTS.

sudo apt-get remove modemmanager

sudo adduser $USER dialout (or)
sudo usermod -a -G dialout $USER // adds the user to the dialout
// replace $USER by the username
sudo reboot
id -Gn
And check now if the device is attached to the dialout user group.

ls -l /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Mar 5 19:58 /dev/ttyUSB0

There is no need to mess with dev rules or u permissions

-----------------------------------------------------------------------------------------------------------
If you get a error saying

make: ../../tools/sky/serialdump-linux: Command not found
make: *** [login] Error 127

Try the following question if the answers are true then this procedure for troubleshooting
Are you using a 64bit version of Ubuntu?
Are you using a Ubuntu 12.04 LTS or newer versions of it?

Now, try few commands like
ldd serialdump-linux

The output look similar to the following
ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

Broadcast Example

2014-02-08T00:05:28Z

Lgadde: /* Understanding the code */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. A glance at core/net/rime/broadcast.h and core/net/rime/broadcast.c helps in the understanding underlying concepts of this example.
In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

'''PROCESS_EXITHANDLER(handler)'''

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is declared at the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

'''broadcast_close(struct broadcast_conn *)'''

This function closes a broadcast connection that has previously been opened with broadcast_open().This function typically is called as an exit handler.
*broadcast_conn *: This is same as the variable from boradcast_recv().

'''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. This macro initiates PT_END().It must always be used together with a matching PT_BEGIN() macro.

'''broadcast_open(struct broadcast_conn *, uint16_t ,const struct broadcast_callbacks *)'''

Sets up an identified best-effort broadcast connection. The caller will allocate the memory for the struct broadcast_conn, usually by declaring it as a static variable. The struct broadcast_callbacks pointer points to a structure containing a pointer to a function that will be called when a packet arrives on the channel. This function opens a connection of type abc_conn and sets the callbacks to structure passed. Also, this points to channel_set_attributes() function.

*broadcast_conn *: A pointer to a struct broadcast_conn
*uint16_t: The channel on which the connection will operate
*broadcast_callbacks *: A struct broadcast_callbacks with function pointers to functions that will be called when a packet has been received

'''etimer_set(struct etimer *, clock_time_t)'''

This function is used to set an event timer for a time sometime in the future. When the event timer expires, the event PROCESS_EVENT_TIMER will be posted to the process that called the etimer_set() function.

*etimer *: A pointer to the event timer
*clock_time_t *: The interval before the timer expires.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T23:27:17Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

'''PROCESS_EXITHANDLER(handler)'''

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is declared at the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

'''broadcast_close(struct broadcast_conn *)'''

This function closes a broadcast connection that has previously been opened with broadcast_open().This function typically is called as an exit handler.
*broadcast_conn *: This is same as the variable from boradcast_recv().

'''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. This macro initiates PT_END().It must always be used together with a matching PT_BEGIN() macro.

'''broadcast_open(struct broadcast_conn *, uint16_t ,const struct broadcast_callbacks *)'''

Sets up an identified best-effort broadcast connection. The caller will allocate the memory for the struct broadcast_conn, usually by declaring it as a static variable. The struct broadcast_callbacks pointer points to a structure containing a pointer to a function that will be called when a packet arrives on the channel. This function opens a connection of type abc_conn and sets the callbacks to structure passed. Also, this points to channel_set_attributes() function.

*broadcast_conn *: A pointer to a struct broadcast_conn
*uint16_t: The channel on which the connection will operate
*broadcast_callbacks *: A struct broadcast_callbacks with function pointers to functions that will be called when a packet has been received

'''etimer_set(struct etimer *, clock_time_t)'''

This function is used to set an event timer for a time sometime in the future. When the event timer expires, the event PROCESS_EVENT_TIMER will be posted to the process that called the etimer_set() function.

*etimer *: A pointer to the event timer
*clock_time_t *: The interval before the timer expires.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T23:25:02Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

'''PROCESS_EXITHANDLER(handler)'''

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is declared at the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

'''broadcast_close(struct broadcast_conn *)'''

This function closes a broadcast connection that has previously been opened with broadcast_open().This function typically is called as an exit handler.
*broadcast_conn *: This is same as the variable from boradcast_recv().

'''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. This macro initiates PT_END().It must always be used together with a matching PT_BEGIN() macro.

'''broadcast_open(struct broadcast_conn *, uint16_t ,const struct broadcast_callbacks *)'''

Sets up an identified best-effort broadcast connection. The caller will allocate the memory for the struct broadcast_conn, usually by declaring it as a static variable. The struct broadcast_callbacks pointer points to a structure containing a pointer to a function that will be called when a packet arrives on the channel. This function opens a connection of type abc_conn and sets the callbacks to structure passed. Also, this points to channel_set_attributes() function.

*broadcast_conn *: A pointer to a struct broadcast_conn
* uint16_t: The channel on which the connection will operate
*broadcast_callbacks *: A struct broadcast_callbacks with function pointers to functions that will be called when a packet has been received

'''etimer_set(struct etimer *, clock_time_t)'''

This function is used to set an event timer for a time sometime in the future. When the event timer expires, the event PROCESS_EVENT_TIMER will be posted to the process that called the etimer_set() function.

*etimer *: A pointer to the event timer
*clock_time_t *: The interval before the timer expires.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T22:48:21Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

'''PROCESS_EXITHANDLER(handler)'''

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is declared at the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

'''broadcast_close(struct broadcast_conn *)'''

This function closes a broadcast connection that has previously been opened with broadcast_open().This function typically is called as an exit handler.
*broadcast_conn *: This is same as the variable from boradcast_recv().

'''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.
This macro initiates PT_END().It must always be used together with a matching PT_BEGIN() macro.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T22:38:10Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

PROCESS_EXITHANDLER(handler)

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is declared at the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

'''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.
This macro initiates PT_END().It must always be used together with a matching PT_BEGIN() macro.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T22:33:16Z

Lgadde:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

PROCESS_EXITHANDLER(handler)

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler: The action to be performed.

'''PROCESS_BEGIN()'''

This macro defines the beginning of a process, and must always appear in a PROCESS_THREAD() definition.This macros initiates PT_BEGIN(), which is used to declare the starting point of a protothread. All C statements above the PT_BEGIN() invokation will be executed each time the protothread is scheduled.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T22:24:57Z

Lgadde:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

PROCESS_EXITHANDLER(handler)

Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler The action to be performed.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T22:13:11Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.

==== Macros and Structures ====

<code><nowiki> PROCESS(name,strname) </nowiki></code>

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

<code><nowiki> AUTOSTART_PROCESS(struct process &) </nowiki></code>

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

<code><nowiki> broadcast_recv(struct broadcast_conn *, const rimeaddr_t *) </nowiki></code>

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

<code><nowiki> PROCESS_THREAD(name, process_event_t, process_data_t) </nowiki></code>

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

PROCESS_EXITHANDLER(handler)
Specify an action when a process exits.
NOTE This declaration must come immediately before the PROCESS_BEGIN() macro.
*handler The action to be performed.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T09:57:10Z

Lgadde: /* Macros and Structures */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

=== Introduction ===

This exercise is an introduction into programming the [http://www.capsil.org/capsilwiki/index.php/TELOSB/TMote_Sky Tmote Sky]. It uses the Rime stack to communicate with other Contiki nodes over the radio. You will run the broadcast example already found in the Contiki core folders to send your name from a base station via broadcast packets. The exercise sends broadcast packets at random intervals between 20 and 40 seconds such that all Tmote Sky boards nearby will receive the packet.

=== You will learn: ===

* How to program the Broadcast communication found within the Rime stack
* How to encapsulate data in packets

=== Connect the Tmote Sky: ===
Before continuing with the tutorial, plug a Tmote Sky into the computer’s USB port. The LEDs on the skymote will start blinking to indicate that the mote is connected.

=== Step 1: ===

The first step is to change directories. At this point you should be familiar with the Contiki 2.7 core folders. The Rime stack is located within the examples folder, so type

<code><nowiki> cd contiki-2.7/examples/rime </nowiki></code>

directly into terminal. Once inside the rime folder, use the ls command to view all the files within it. We will be working specifically with example-broadcast.c.

=== Step 2: ===

Next, we will edit the data in the example-broadcast.c packet. In order to do this, you will need to open the packet within your text editor. In this exercise, we use gedit, but feel free to use whichever text editor you are most comfortable with. Type:

<code><nowiki> gedit example-broadcast.c </nowiki></code>

into terminal. This will open your text editor, allowing you to edit the code inside the broadcast packet.

=== Step 3: ===

To edit the actual data that your Tmote Sky will broadcast, scroll down to the line that contains

<code><nowiki> packetbuf_copyfrom(“Hello”, 6) </nowiki></code>

Change the character string to your name. Then change the number of characters accordingly. Remember to account for the null zero associated with character strings in C when changing the number of characters. The line should now read

<code><nowiki> packetbuf_copyfrom(“yourName”, 9) </nowiki></code>

Save and exit the text editor.

=== Step 4: ===

In the next step we configure Tmote Sky. Connect your mote to your computer via USB. If you are using VirtualBox or Parallels, assure that the mote actually connects to your virtual machine (the LEDs on the mote will blink when connected to the laptop).

Then in terminal, type

<code><nowiki> sudo chown:user /dev/ttyUSB0 </nowiki></code>

You will be prompted to enter the password for your user account. If you are running Instant Contiki, the password is user. The sudo [http://en.wikipedia.org/wiki/Chown chown] command is used to change the owner of the file in Unix-systems.

Note: If you manually installed Contiki, you must type in your username instead of user. Then, when prompted to do so, enter your password.

=== Step 5: ===

In this step, we will compile and upload the Broadcast packet to your Tmote Sky. In the terminal window, type

<code><nowiki> make TARGET=sky example-broadcast.upload login </nowiki></code>

You will notice that instead of typing example-broadcast.sky, we use example-broadcast.upload. The .upload tells Contiki to install the binary onto the attached mote. Additionally, we add login to use the terminal to communicate with the mote over the serial interface referred to by /dev/ttyUSB0. Note that login can be specified later in another call to make, i.e. make login.

This should compile and upload the example-broadcast.c packet such that your mote will be able to broadcast your name. After the compilation is complete, the text broadcast message sent... should appear in terminal every 2 to 4 seconds, indicating that your name (which we added within the text editor) is being broadcast to all other motes in the area.

'''Congratulations! You have successfully programmed the Tmote Sky! '''

'''Note:''' If at any point, you would like to exit the compilation/broadcast stage, press CTRL-C

'''Tip:''' You can save the TARGET by typing make TARGET=sky savetarget into terminal to avoid compiling the target repeatedly.

=== Understanding the code ===
The purpose of this example is to test the broadcast layer in Rime. In the code, a process called example_braodcast_process is kicked off by AUTOSTART_PROCESSES.
(Best effort)

=== Macros and Structures ===
'''PROCESS(name,strname)'''

The process has two names: the variable of the process structure, which is used by the C program, and a human readable string name, which is used when debugging.

*name: The variable name of the process structure.
*strname: The string representation of the process name.

'''AUTOSTART_PROCESS(struct process &)'''

The AUTOSTART_PROCESSES definition specifices what processes to start when the module is loaded. We can pass more than one process.

*&name: Refernce to process name

'''broadcast_recv(struct broadcast_conn *, const rimeaddr_t *)'''

This function is called whenever a broadcast message is received. Reads the message, address of the sender and displays them.

*broadcast_conn *: This structure which has 2 structures : abc_conn, broadcast_callbacks *. The abc_conn is basic type of connection over which the broadcast connection is developed. And, the broadcast_callbacks point to functions recv and sent functions.

*rimeaddr_t *: This is union which has a array u8[RIMEADDR_SIZE] of type character.

'''PROCESS_THREAD(name, process_event_t, process_data_t)'''

A process in Contiki consists of a single reference to "protothread".This function is used to define the protothread of a process. The process is called whenever an event occurs in the system. A process always start with the PROCESS_BEGIN() and end with the PROCESS_END() function.

*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.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Broadcast Example

2014-02-07T09:40:38Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:32:35Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:24:33Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:21:39Z

Lgadde: /* Understanding the code */

Broadcast Example

2014-02-07T09:09:15Z

Lgadde: /* Understanding the code */

Broadcast Example

2014-02-07T09:07:18Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:06:04Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:05:24Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:04:15Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T09:00:52Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T06:50:28Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T06:48:55Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T06:35:37Z

Lgadde:

Broadcast Example

2014-02-07T06:34:22Z

Lgadde: /* Macros and Structures */

Broadcast Example

2014-02-07T06:33:15Z

Lgadde:

Broadcast Example

2014-02-07T06:17:42Z

Lgadde:

Broadcast Example

2014-02-07T06:15:54Z

Lgadde:

Broadcast Example

2014-02-07T06:09:56Z

Lgadde:

Broadcast Example

2014-02-07T06:06:13Z

Lgadde:

Broadcast Example

2014-02-07T06:03:08Z

Lgadde:

Broadcast Example

2014-02-07T04:32:47Z

Lgadde: