Contiki is an open source operating system for the Internet of Things. Contiki connects tiny low-cost, low-power microcontrollers to the Internet.
the presentation explains how to install the simulator, teach the reader some concepts of contiki OS, goes through API used in platform specific examples, and most importantly explains some example(Blinking example, Light and temperature sensor web demo).
Presentation detailed about SDN (Software Defined Network) overview . It covers from basics like different controllers and touches upon some technical details.
Covers Terminologies used, OpenFlow, Controllers, Open Day light, Cisco ONE, Google B4, NFV,etc
TinyOS is a free open source operating system.
Designed for wireless sensor networks.
TinyOS began as a collaboration between University of California, Berkeley and Intel Research.
An embedded operating system written in nesC language.
It features a component based architecture.
This presentation is prepared for workshop session and is not in detail. You can ask your doubts here or you can email me at prakharbansal1@gmail.com. I'll try to answer to my best.
Presentation detailed about SDN (Software Defined Network) overview . It covers from basics like different controllers and touches upon some technical details.
Covers Terminologies used, OpenFlow, Controllers, Open Day light, Cisco ONE, Google B4, NFV,etc
TinyOS is a free open source operating system.
Designed for wireless sensor networks.
TinyOS began as a collaboration between University of California, Berkeley and Intel Research.
An embedded operating system written in nesC language.
It features a component based architecture.
This presentation is prepared for workshop session and is not in detail. You can ask your doubts here or you can email me at prakharbansal1@gmail.com. I'll try to answer to my best.
Embedded system, basic structure, characteristics, advantages, disadvantages of Embedded system, open source Embedded platforms and its benefits, sensors, actuators, DAS.
on successful go through of this complete PPT, the learners can be able to understand the Raspberry PI, Raspberry Pi Interfaces(Serial, SPI,I2C) Programming, Python programming with Raspberry PI with the focus of Interfacing external gadgets
Controlling output Reading input from pins.
15LLP108_Demo4_LedBlinking.pdf1. Introduction In D.docxfelicidaddinwoodie
15LLP108_Demo4_LedBlinking.pdf
1. Introduction
In Demo3, we have learned how to read sensor values of light, temperature and humidity of a node
and output these values to the console. In this demonstration, we will use the code from Demo3 and
learn how to turn on/off the LEDs and make them blinking regularly on the sensor node XM1000,
meanwhile to count how many times the LED has blinked and output the count to the console.
2. Timer
In order to make the blue LED on the XM1000 sensor node to blink in every half second (i.e. On 0.5S
and Off 0.5S), we also need a timer. Follow the instructions in Demo3 for configure and reset a timer.
We aslo need to create an infinite while() loop so that it runs our functions repeatedly, such as
counting the times the LED has blinked, output the counter’s value and actually turn on or off the
LEDs to make it blinking.
Please follow timer and while() loop structure in Demo3.
3. LED Blinking
To get access to the LED functionalities in Contiki, we need to include the LED header file in the
source code:
#include "leds.h" // file is in directory /home/user/contiki/core/dev
After the process begin, we have to initialise the LEDs on the sensor node by calling the following
function:
leds_init(); // Initialise the LEDs
And finally we can turn on, off, or blink the LEDs by the following functions:
void leds_on(unsigned char leds);
void leds_off(unsigned char leds);
void leds_toggle(unsigned char leds);
void leds_invert(unsigned char leds);
For example, if you want to blink the Blue LED, yon need to call the toggle function as:
void leds_toggle(LEDS_BLUE); // Toggle the blue LED
4. Exercise
Modify the program from Demo3 with periodic timer to make the BLUE led blinking in every half
second, also to count the blinking times and output the counted number to the console.
Can your change the code so that the BLUE LED is lighted for 1 second and off for 0.5 second
periodically?
15LLP108 – Internet of Things and Applications
Lab Session 2: Demo 4 – LED Blinking
Prepared by Xiyu Shi
5. Source code
Here is the source code for reference
#include "contiki.h"
#include "leds.h"
#include <stdio.h> /* for printf() */
static struct etimer timer;
/*____________________________________________________*/
PROCESS(led_blinking_process, "LED Blinking Process");
PROCESS(LED_process, "LED process");
AUTOSTART_PROCESSES(&LED_process);
/*____________________________________________________*/
PROCESS_THREAD(LED_process, ev, data)
{
static int count = 0;
PROCESS_BEGIN();
etimer_set(&timer, CLOCK_CONF_SECOND/2); // 0.5S timer
leds_init(); // intialise the LEDs
while(1) {
PROCESS_WAIT_EVENT_UNTIL(ev==PROCESS_EVENT_TIMER); // wait for timer event
count++; // count the blinking times
process_start(&led_blinking_process, NULL); // to blink the BLUE Led
printf("Count: %d\n", count); // output the counte ...
Embedded system, basic structure, characteristics, advantages, disadvantages of Embedded system, open source Embedded platforms and its benefits, sensors, actuators, DAS.
on successful go through of this complete PPT, the learners can be able to understand the Raspberry PI, Raspberry Pi Interfaces(Serial, SPI,I2C) Programming, Python programming with Raspberry PI with the focus of Interfacing external gadgets
Controlling output Reading input from pins.
15LLP108_Demo4_LedBlinking.pdf1. Introduction In D.docxfelicidaddinwoodie
15LLP108_Demo4_LedBlinking.pdf
1. Introduction
In Demo3, we have learned how to read sensor values of light, temperature and humidity of a node
and output these values to the console. In this demonstration, we will use the code from Demo3 and
learn how to turn on/off the LEDs and make them blinking regularly on the sensor node XM1000,
meanwhile to count how many times the LED has blinked and output the count to the console.
2. Timer
In order to make the blue LED on the XM1000 sensor node to blink in every half second (i.e. On 0.5S
and Off 0.5S), we also need a timer. Follow the instructions in Demo3 for configure and reset a timer.
We aslo need to create an infinite while() loop so that it runs our functions repeatedly, such as
counting the times the LED has blinked, output the counter’s value and actually turn on or off the
LEDs to make it blinking.
Please follow timer and while() loop structure in Demo3.
3. LED Blinking
To get access to the LED functionalities in Contiki, we need to include the LED header file in the
source code:
#include "leds.h" // file is in directory /home/user/contiki/core/dev
After the process begin, we have to initialise the LEDs on the sensor node by calling the following
function:
leds_init(); // Initialise the LEDs
And finally we can turn on, off, or blink the LEDs by the following functions:
void leds_on(unsigned char leds);
void leds_off(unsigned char leds);
void leds_toggle(unsigned char leds);
void leds_invert(unsigned char leds);
For example, if you want to blink the Blue LED, yon need to call the toggle function as:
void leds_toggle(LEDS_BLUE); // Toggle the blue LED
4. Exercise
Modify the program from Demo3 with periodic timer to make the BLUE led blinking in every half
second, also to count the blinking times and output the counted number to the console.
Can your change the code so that the BLUE LED is lighted for 1 second and off for 0.5 second
periodically?
15LLP108 – Internet of Things and Applications
Lab Session 2: Demo 4 – LED Blinking
Prepared by Xiyu Shi
5. Source code
Here is the source code for reference
#include "contiki.h"
#include "leds.h"
#include <stdio.h> /* for printf() */
static struct etimer timer;
/*____________________________________________________*/
PROCESS(led_blinking_process, "LED Blinking Process");
PROCESS(LED_process, "LED process");
AUTOSTART_PROCESSES(&LED_process);
/*____________________________________________________*/
PROCESS_THREAD(LED_process, ev, data)
{
static int count = 0;
PROCESS_BEGIN();
etimer_set(&timer, CLOCK_CONF_SECOND/2); // 0.5S timer
leds_init(); // intialise the LEDs
while(1) {
PROCESS_WAIT_EVENT_UNTIL(ev==PROCESS_EVENT_TIMER); // wait for timer event
count++; // count the blinking times
process_start(&led_blinking_process, NULL); // to blink the BLUE Led
printf("Count: %d\n", count); // output the counte ...
GNAT for Lego Mindtorms NXT is a GPL port for the GNAT compilation system to the Lego Mindstorms NXT robotic platform. Originally born as an education-oriented project at MIT Media Lab, the Lego Mindstorms has evolved into a succesful commercial product for education in robotics in a moltitude of Universities and high schools across the globe. The latest revision of the platform includes a 32 bits processor and supports several different sensors able to detect distance, colors and sounds and to communicate via the Bluetooth protocol.
Is Rust Programming ready for embedded development?Knoldus Inc.
The traditional approach to embedded development would be to run an RTOS on a microcontroller and to write the application in C or C++. This gives huge benefits in terms of the resources required compared to a Linux-based system, but now developers are working down in the world of systems programming, where there is nothing between them and a critical memory-safety bug except a keen eye and perhaps some expensive, imperfect and/or tricky-to-use static analysis tools. That bug might just give hackers access to a product and to anything the product is connected to, both locally and remotely.
Of course, there are plenty of things other than memory safety bugs that might give hackers a route straight into a product, but it would be preferable for developers to concentrate on those, instead of worrying about memory leaks, buffer overflows or tracking down the root cause of a random, undefined behaviour.
But after Rust came into existence the programmers are getting memory safety with low-level control.
If you have considered using embedded rust, you may have run into questions such as “What is embedded?”, “What is a driver crate?” “Where does rtfm/rtic and cortex_m fit into the picture?” This webinar will give you answers to these questions and how you can start your embedded rust journey
O Webinar é focado na mais nova plataforma de desenvolvimento para sensores, o SensorTile.box, com a versão de baixo consumo STM32L4.
Convidado: Thiago Reis – Engenheiro de Produto: STMicroelectronics
Link para o Webinar: https://www.embarcados.com.br/webinars/webinar-explorando-novas-aplicacoes-com-sensortile-box/
The PIC Microcontroller is an electronic device that is easy-to-use in both hardware and software. Sensing the environment by receiving inputs from many sensors, PIC Microcontroller affects its surroundings by controlling lights, motors, and a number of other accessories. It's intended for anyone making interactive hardware projects by connecting it with a power source, few leds and resistors.
This course is designed to introduce the PIC Microcontroller hardware and programming environment to get you started on building projects as soon as possible.
Unleash Your Inner Hero With this Course
-PIC Microcontroller Inner structure and Programming Introduction
-Leds, Resistors and Pushbuttons
-LCD Screens and Seven Segment Displays
-Motor and Keypad.
-DIY Projects and Quick Tips
A Tool for Creating Any Device Imaginable become a favorite of electronic Students and anyone interested in Device manufacturing because of their ease of use and extremely low cost.
Example projects include Ardupilot, a UAV platform able to control aerial drones.
Contents and Overview This course is designed for anyone interested in learning electronic design. No experience is required, and all you need is PIC Microcontroller and several low cost components.
With hours of content in many lectures, this course will take you from zero experience in electronics or programming to PIC Microcontroller Master.
Limited time offer
50% off
Join Today:https://goo.gl/WQIFNY
Simulation of Signals with Field Signal SimulatorIOSR Journals
Abstract: In the recent trends the field signal processing is an emerging technology for data acquisition systems, controlling application systems and automation system in real time environment. Versa Modular European (VME) and CRIO based hardware to simulate the field signals for the computer based control and instrumentation panel. Simulator is used to transmit multiple number of signals at a time. FSS software is a generic software to simulate the field signals for a computer based control and instrumentation system. Its general purpose nature easily extends its capabilities to build and perform unit under test(UUT’s) ATP specific test routines. Field signal simulator (FSS)is also an Automatic Testing Equipment (ATE). The main the Scope of this project covers real time computer (RTC) systems used for Signal Processing & Control application and the simulation techniques used to achieve automation by testing these RTC systems. It also includes RTC hardware and the software used for process & control applications. Simulation hardware & software used to test VME system is also included in the scope of this study.
InvenSense Developers Conference 2016 -
SensorStudio development environment will be detailed. You will learn how to add your sensor driver and create your algorithms, while benefiting from a complete sensor development framework.
https://www.invensense.com/sensorstudio/
https://www.invensense.com/products/genericsensorhub-development-kit/
Advanced view of atmega microcontroller projects list at mega32 avrWiseNaeem
Most of the electronics geeks are asking the whole list of Atmega AVR projects PDF here we will share list every month as our projects are being updated on daily basis. PDF is a good source to work offline. We will offer direct PDF file download link with info of its release date , number of projects.
This paper Presentation(ppt) is totally on Industrial Automation for seminar along with project ( PLC based water bottle filling system) which work on the principle of Industrial Automation .
Yemen is one of the countries with least measure in various fields. In this paper i talk about the role of ICT and Yemen unemployment.
here is the presentation slides of the paper.
http://www.slideshare.net/salahecom/ict-culturing-conference-presentation-presented-20131207
Contiki os timer is an essential topic in contiki OS. This presentation describes the different types of timers and their API .
It is following the same explanation as contiki OS wiki.
WSN protocol 802.15.4 together with cc2420 seminars Salah Amean
WSN protocol 802.15.4 together with cc2420 seminars . It is based on the standand of ieee802.15.4 and data sheet of the radio transceiver cc2420.
Note that some slides are borrowed.
ContikiMAC : Radio Duty Cycling ProtocolSalah Amean
Several MAC duty-cycle protocols have been proposed during the last decade to
address specific WSNs requirements and constraints such as a
low energy consumption linked to battery operated nodes
Radio Duty-Cycle (RDC) MAC protocols try to reduce the energy consumption by allowing a node to keep its radio-transceiver off most of the time.
This allow a node to avoid to keep the radio on unnecessarily, i.e when not involved in any transmission
Idle listening is used to solve such problem in which RDC MAC forces node to switch its transceiver between short active(listen) periods and long inactive (sleep) periods
. This presentation introduces a very important concept in wireless sensor network, particularly in handling transmission and reception of packets in very limited resources channel.
Location in ubiquitous computing, LOCATION SYSTEMSSalah Amean
This presentation is a simple effort to survey positioning systems which is part o
Introduction
Location system
Global Positioning System
Active Badge
Active Bat
Cricket
UbiSense
RADAR
Place Lab
PowerLine Positioning
ActiveFloor
Airbus and Tracking with Cameras
Credit:
1-the presentation follows the book of "Ubiquitous computing fundamentals by John Krumm " 2010 .
2- few videos are downloaded and integrated with the presentation. Most of the videos are important to explain about each topics they are placed in
Mobile apps-user interaction measurement & Apps ecosystemSalah Amean
This presentation talks about the user behaviours and the trend of mobile applications. It also talks about the behaviour of users downloading most common application on the market.
This report takes about the possibility of improving the employment rate in Yemen( since the amount of literacy is extremely low in Yemen in term of Internet).
So to solve the problem of unemployment we have to solve the severe problem of literacy in term of ICT or literacy in general.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
3. WhyChoose
Contiki?
Contiki is an open source operating system for the
Internet ofThings.
Contiki connects tiny low-cost, low-power
microcontrollers to the Internet
4. TheContiki
Operating
System
Contiki is an open source operating system that
runs on tiny low-power microcontrollers and makes
it possible to develop applications that make
efficient use of the hardware while providing
standardized low-power wireless communication
for a range of hardware platforms.
Contiki is used in numerous commercial and non-
commercial systems, such as city sound monitoring,
street lights, networked electrical power meters,
industrial monitoring, radiation monitoring,
construction site monitoring, alarm systems,
remote house monitoring, and so on.
6. Firstly
Cooja makes Contiki easy to install and get started
with it.
Download Instant Contiki
http://sourceforge.net/projects/contiki/files/Instant
%20Contiki/
InstallVMWare Player
https://my.vmware.com/web/vmware/free#deskto
p_end_user_computing/vmware_player/6_0
Register and reboot
Start Instant Contiki
Start Instant Contiki by running
InstantContiki2.6.vmx.Wait for the virtual Ubuntu
Linux boot up.
Log into Instant Contiki.The password is user.
10. Cooja is a highly useful tool for Contiki
development as it allows developers to test their
code and systems long before running it on the
target hardware.
Developers regularly set up new simulations both
to debug their software and to verify the behavior
of their systems.
11. Open a
terminal
window
We will now compile and start Cooja, the Contiki
network simulator.
Starting the terminal
12. StartCooja
Start Cooja by
In the terminal window, go to the Cooja directory:
Start Cooja with the command:
18. Simulation
windows
Network window -Top left
-shows all motes in the simulated
area
Timeline window - At the bottom of screen
- Shows all communication
events in the simulation over
time
- very handy for understanding
what goes on in the network
Notes window - On the top right is where we can
put notes for our simulation.
Mote output window - on the right side of the screen
- shows all serial port printouts
from all the motes.
Simulation control -window is where we start, pause,
and reload our simulation
19. Add mote to
the interface
Before we can simulate our network, we must add
one or more motes.
We do this via the Motes menu, where we click on
Add motes....
Since this is the first mote we add, we must first
create a mote type to add.
Click Create new mote type... and select one of
the available mote types.
For this example, we click Sky mote... to create an
emulatedTmote Sky mote type.
Choose the hardware then install the firmware with
any functionality that you desire
23. Platform
porting
we assume you have a Zolertia Z1 mote connected to a
USB port of your PC
Enable the Z1 in Instant Contiki, so that Instant Contiki
is able to talk to it
cd contiki/examples/FOLDER/
Then upload the compiled firmware to the hardware
Then make login
To access the burnt firmware on the device
30. TmoteSky
platform
TheTmote Sky platform is a wireless sensor board
from Moteiv.
It is an MSP430-based board with an 802.15.4-
compatible CC2420 radio chip,
a 1 megabyte external serial flash memory, and two
light sensors.
Contiki was ported to theTmote Sky by Björn
Grönvall as part of the RUNES project.
TheTmote Sky port was integrated into the Contiki
build system in March 2007.
31. TmoteSky
platform
The platform-specific source code for theTmote
Sky port can be found in the directories
platform/sky and cpu/msp430 in the Contiki
source tree.
Code for writing to the on-chip flash ROM is in the
cpu/msp430/flash.c
Code for reading and writing to the external flash is
the file platform/sky/dev/xmem.c
Code for reading the light sensors is in
platform/sky/dev/light.c.
34. Code detail
PROCESS ( name,
strname )
Declare a process.
PROCESS(blink_process, "Blink");
AUTOSTART_PROCESSES(&blink_process); Starting a process automatically
&blink_process
ROCESS_THREAD(name,
ev,data )
-Define the body of a process
-The process is called whenever an event
occurs in the system
-Start with the PROCESS_BEGIN() macro -
Ends with the PROCESS_END() macro.
PROCESS_EXITHANDLER(handler ) -Specify an action when a process exits.
-Comes before declaring PROCESS_BEGIN()
PROCESS_BEGIN( ) ,PROCESS_END()
-specify the beginning and the End of a
process
35. Code detail
etimer et; -This structure is used for declaring a timer.
The timer must be set with etimer_set()
before it can be used.
PROCESS_WAIT_EVENT_UNTIL(c) Wait for an event to be posted to the process,
with an extra condition.
-This macro is similar to
PROCESS_WAIT_EVENT()
in that it blocks the currently running process
until the process receives an event.
PROCESS_WAIT_EVENT_UNTIL(etimer_expir
ed(&et));
-Check if an event timer has expired.
-Parameters:
et :a pointer to the event timer.
-return true if the time expires
leds_on(LEDS_ALL); On the LEDS
leds_off(LEDS_ALL); Off the LEDs
36. LEDAPI
Simple and important to communicate with the
user
The platform startup code initializes the LEDs
library by calling leds_init() initializes the API
ledv: is LED vector platform independent
#define LEDS_GREEN 1
#define LEDS_YELLOW 2
#define LEDS_RED 4
#define LEDS_ALL 7
leds_on() takes a LEDs vector argument, ledv,
and switches on the LEDs set in the vector.
Led_off() takes the LED in ledv and switch it off.
leds_invert() inverts the current status of the
LEDs set in the argument ledv.
40. ESB
platform
sensors
button_battery_sensor - query the battery voltage
level
sensor - query the on-board button
pir_sensor - query the passive IR sensor (motion
detector)
radio_sensor - query the radio signal strength
sound_sensor - query the microphone
temperature_sensor - query the temperature
sensor
vib_sensor - query the vibration senso
41. Sensor
functions
Each sensor has a set of functions for controlling it
and query it for its state. Some sensors also
generate an events when the sensors change. A
sensor must be activated before it generates events
or relevant values.
SENSORS_ACTIVATE(Button_sensor ) ) - activate
the button sensor
SENSORS_DEACTIVATE(sensor)
sensor.value(0) - query the sensor for its last value
(button either pressed or not)
sensors_event - event sent when a sensor has
changed (the data argument will referer to the
actual sensor)
42. process
PROCESS_BEGIN() -Define the beginning of a process
PROCESS_END() -Define the end of a process.
PROCESS_WAIT_EVENT()
-Wait for an event to be posted to the
process.
-blocks the currently running process until
the process receives an event.
PROCESS_WAIT_EVENT_UNTIL(c) Wait for an event to be posted to the
process, with an extra condition.
PROCESS_YIELD() Yield the currently running process.
PROCESS_YIELD_UNTIL(c) Yield the currently running process until a
condition occurs.
PROCESS_WAIT_UNTIL(c) Wait for a condition to occur.
PROCESS_EXIT() Exit the currently running process.
PROCESS_PAUSE() Yield the process for a short while.
43. LED
functions
Basic LED functions
leds_on() - turn LEDs on
leds_off() - turn LEDs off
leds_invert() - invert LEDs
leds_blink() - blink all LEDs
44. Beeper
functions
Implements a beep function to emit a beep sound
Also play polyphonic tune using buzzer
beep()- click the beeper
beep_beep()- beep
beep_down()- pitchbend down beep
beep_quick() - a number of quick beeps
beep_spinup()- pitchbend up beep
45. Timer
functions
EventTimer Callback timer Simple timer
-generates an
event when the
timer expires a
-call a function
when the timer
expires
-have to be actively
queried to check
when they have
expired
•etimer_expired()
•etimer_reset
•etimer_set()
•etimer_restart()
•ctimer_expired()
•ctimer_reset
•ctimer_set()
•ctimer_restart()
•timer_expired()
•timer_reset
•timer_set()
•timer_restart()
The Contiki kernel does not provide support for timed
events. Rather, an application that wants to use timers
needs to explicitly use the timer library.
47. Border
router set-up
Having able to connect to sensors is very significant
step in IOT
This example features a simple webserver running
on top of the IPv6 Contiki stack on Sky motes to
provide sensor values, and with a RPL border router
to bridge the sensor network to Internet.
Server is located in :
[Contiki home]examplesipv6rpl-border-router
Simulation in Cooja is in
examplesipv6sky-websense
48. Steps
1. Start COOJA and load the simulation "example-
sky-websense.csc"
makeTARGET=cooja example-sky-websense.csc
2. Connect to the COOJA simulation using tunslip6:
make connect-router-cooja
3.You should now be able to browse to the nodes
using your web browser:
Router: http://[aaaa::0212:7401:0001:0101]/
Node 2: http://[aaaa::0212:7402:0002:0202]/
49. tunslip6
Before being able to view the sensor readings from
the webserver,
A serial connection to the server through the
command
50. output
The Cooja simulator provides you with important
details about every sensor node in the network
52. Websense
code details
The second process is
It does the sensing through the web in a way
A protothread that handles reading or getting the
parameters of temperature and light from sensors
54. Question
• what is uIPTCP/I P ?
provides Internet communication abilities to
Contiki
What are the applications of it?
Network enabling an embedded
microcontroller makes it possible to
control electronic consumer devices or
appliances such
as smart meters,
heating, air conditioning, lighting systems, grid
connected electric car chargers and even door
locks, radiation systems, ..anything
55. Questions
What is used for?
Contiki is designed for microcontrollers with small
amounts of memory.
Operating system for memory-efficient networked
embedded systems and wireless sensor networks
What is the typical size of Contiki?
A typical Contiki configuration is 2 kilobytes of
RAM and 40 kilobytes of ROM.
56. Question
What is COOJA?
Cooja is a simulator provided by Contiki, which
unlike most simulators also allows real hardware
platforms to be emulated
No addition stack is needed
Basically is used to handle the memory constraint in limited devices.
The function leds_toggle() is an alias for leds_invert(), and is only kept for backward compatibility.
Platform dependent blink
In step 2 , the user need to open the terminal and go to the same folder and connect to the webserver using the command “make connect-router-cooja”
Then
, ping the COOJA nodes to test the connectivity. Type in the terminal the
ping6 aaaa::0212:7402:0002:0202
ping6 aaaa::0212:7403:0003:0303
In the Make file in sky-websense folder configuration of the tunslip6 is handled there,
Here is the configuration of the tunslip6 which is included in the MakeFile
$(CONTIKI)/tools/tunslip6: $(CONTIKI)/tools/tunslip6.c
(cd $(CONTIKI)/tools && $(MAKE) tunslip6)
connect-router: $(CONTIKI)/tools/tunslip6
sudo $(CONTIKI)/tools/tunslip6 aaaa::1/64
connect-router-cooja: $(CONTIKI)/tools/tunslip6
sudo $(CONTIKI)/tools/tunslip6 -a 127.0.0.1 aaaa::1/64
2- more information on the SLIP
http://en.wikipedia.org/wiki/Serial_Line_Internet_Protocol
https://github.com/maniacbug/contiki-avr-zigduino/wiki/Using%3ASLIP#What_is_SLIP
http_appcall() function exists in apps/webserver/httpd.c