developing an iot system fiware based from the scratch

8
Developing an IoT System FIWARE based from the scratch

Upload: fiware

Post on 12-Jan-2017

17 views

Category:

Internet


1 download

TRANSCRIPT

Page 1: Developing an IoT System FIWARE Based from the Scratch

Developing an IoT System FIWARE based from the scratch

Page 2: Developing an IoT System FIWARE Based from the Scratch

About me: Jose BenitezCofounder and CEO at SecmoticProject manager, FIWARE developer, IoT LoverTelecommunication Engineer (electronic & computer)

Page 3: Developing an IoT System FIWARE Based from the Scratch

Objective

Connect 2 devices using different IoT Protocols to a cloud

Intel EdisonUltra lightwieght 2.0 (UL2.0)

Raspberry PiLightweight Machine to Machine (LWM2M)

Page 4: Developing an IoT System FIWARE Based from the Scratch

Tools• A Cloud. In our case: FIWARE LAB• FIWARE Generic Enblers• Orion Context Broker• IDAS (LWM2M & UL2.0) iot Agents

• Dashboard for represent data• Freeboard

Page 5: Developing an IoT System FIWARE Based from the Scratch

Architecture

Instance in FIWARE LAB

IDAS

Page 6: Developing an IoT System FIWARE Based from the Scratch

Theory: What is this again..?

Intel EdisonUltra lightwieght 2.0 (UL2.0)

Raspberry PiLightweight Machine to Machine (LWM2M)

Page 7: Developing an IoT System FIWARE Based from the Scratch

Steps1. Instance in FIWARE LAB: Creation of an instance, configuration of security groups, static IP

allocation2. Instance configuration: access via ssh, docker installation3. Configuring the architecture with docker-compose

1. The docker-compose.yml2. Configuring the containers (orion, mongo, iotagent#1, iotagent#2)

4. Configuring the devices1. Configuring the intel edison to use UL2.0 and its sensors2. Configuring the raspberry to use LWM2M with waakama

5. Connecting the devices to the cloud and see the real time changes6. Data visualization via Freeboard.io

DONT GET LOST!IF YOU HAVE DOUBTS, STOP ME!

Page 8: Developing an IoT System FIWARE Based from the Scratch

Creative Technological

[email protected]