Session-1 Theory [Getting started with basics]

  • v1.1 Introduction to IoT

Ø 1.1.1 What is IoT?

Ø 1.1.2 Why do we need IoT?

Ø 1.1.3 Definition of IoT

Ø 1.1.4 History of IoT

Ø 1.1.5 Applications

Ø 1.1.6 Market Study

Basic IOT Architecture

Ø 1.2.1 How to fetch The real world Data Or Unique Identity Data

Ø 1.2.2 How to store these In a Gateway Buffer or How to hold Data

Ø 1.2.3 How to Pass the Data on to the network for controlling via App or any remote Device

v How to Decide IoT gateway? (Raspberry-Pi / Arduino)

Ø 1.3.1 What is Gateway ? why its needed ? Difference between IoT gateway and WSN Device?

Ø 1.3.2 Difference between IoT gateway protocols and WSN protocols.

Ø 1.3.3 Design consideration of IoT Hardware/SoC in terms of Power consumption,Data memory, Range/connectivity, Protocols constraints on Soc, Run-time etc.

Session -2 Practical (Let’s start with fetching the data and store it On to the gateway)

Ø 2.1.1 The Arduino Open-Microcontroller Platform

Ø 2.1.2 Arduino Basics

Ø 2.1.3 Arduino Board Layout &Architecture

Ø 2.3.1 Interfacing sensors with Arduino

Ø 2.3.2 Programming Arduino

Ø 2.3.3 Reading from Sensors (real world data)




Session-3 Theory & Cloud Practical Demo1 [Why MQTT or COAP not HTTP]


  • v Upload Data on IoT Cloud Running on HTTP & SMTP Protocol and Monitor Graphically
  • v Access Devices Through IoT Cloud Platform
  • v MQTT Functions and working
  • v In the Project session, which can be controlled via Android App From any remote location will be taught. These are the list of the Ideas in which this key concept can be implemented.


Ø 3.1 Network & connectivity


Ø 3.2 Broker Theory and comparison


Ø 3.3 Run-times


Ø 3.4 Power & complexity


Ø 3.5 Security


Ø 3.6 Upgrades & maintenance


v Theory & Cloud Practical Demo 2




Ø 4.1 Data Latency


Ø 4.2 Scalability


Ø 4.3 Security


Ø 4.4 Bandwidth efficiency


Ø 4.5 Power efficiency


Ø 4.6QualityOfService




Ø 5.1 Send data on to server through ehternet (W5100) and IoT protocols:




Ø 5.2 Why MQTT protocol for IOT (why companies like amazon, Tata Motors, 2elemetry etc have selected


Ø 5.3 MQTT protocol for their web service for IOT.


Ø 5.4 IPV4 addressing problem for IOT and introduction to IPv6 is required to address more devices.


Session-6 Practical [Two way communication code]


Ø 6.1.1 Learn How to publish or subscribe Topics through Mosquito Broker


Ø 6.1.2 Why broker needed and Comparison between different Brokers for MQTT


v MQTT complete Two Way Communication code build & explanation


v End to end IoT device two way communication @ Hi-Tron platform


v Create Local IoT server platform using MQTT broker


Ø 7.1 Comparison Between Different IoT Message Brokers.


Ø 7.2 Complete Broker Setup on Amazon Web services cloud.


Ø 7.3 Running an IoT Broker on AWS Demo using MQTTfx and MQTT lens Clients.


Ø 7.4 Create Alarm,Alert or Notification based on specific threshold values




Ø Smart Home


Ø Smart Grid


Ø Smart Watches


Ø Smart Lightening


Ø Tank Level


Ø Water Flow


Ø Gas Flow Energy and Water


Ø Indoor Air Quality


Ø Temperature Monitoring


Ø Ozone Presence


Ø Forest Fire Detection


Ø Air Pollution


Ø Snow Level Monitoring Landslide and Avalanche Prevention


Ø Smart Water level Indicator


Ø Smart A.C.


Ø Smart Gas Flow Indicator


Ø Earth Quake early Detection


live Chat

this watch was built by serious watch enthusiasts for serious watch enthusiasts. You receive a large amount of that within the watch industry, replica watches as a sportier and bolder evolution of the 1972-born Royal Oak). In 2015 replica Tag Heuer Autavia price , on the movement. The hours and minutes are shown via two skeletonized hands fit under the flying tourbillon. Replicas De relojes The handwork requires expert craftsmanship and is really impressive. The result after many hours of work is of exceptional beauty. The paillonne enamel surrounds the typical Jaquet Droz time indication.