Workshops: Hands-on Labs, Tutorials & MasterClasses

IoT WorkshopsHere are some of our tentative workshop topics — both embedded systems and IoT workshops. More will be added in the months leading up to the event. Since workshops have limited seats available, delegates need to reserve their seats in advance. Pricing and other details can be found at this helpful page.

There will be more workshops added over the coming weeks! Get a Pro pass to make sure you will be the first to reserve seats for your favourite workshops.


By Deepak Gupta and Aneesha Pillari, co-founders, Future Foundry

Attendees will build a glove that can be used to by the blind to navigate using sonar sensors. It also lets you send SOS alerts to a preferred contact at the press of a button the glove.

The workshop will be hands-on and conducted in groups of 3-4 participants. Each group will build the hardware, write code and test their prototypes. The session will conclude with a discussion on additions that can be made to the prototype.


By Amey Inamdar, Staff Engineering Manager, Marvell Semiconductors


  • What is Weave
  • Architecture
  • Build Weave enabled light bulb using Marvell MW302 Dev Board
  • What’s required to convert this prototype to product

With strong penetration of Android phones, Google has a strong user base. With introduction of Google Home, the reach increases and newer possibilities emerge. Google Weave defines a protocol which can be used from Android (and iOS) devices as well as Google Home to control the smart home devices.

This tutorial not only provides an insight into Google Weave protocol, but goes to an extent to show how to create a new product compatible with Google Weave based on Marvell’s MW302 Wi-Fi microcontroller and then describes what does it take to convert the prototype into product.

Key takeaways:

  • Details of Google Weave Protocol
  • Building a product with Google Weave 


By Anuj Deshpande, founder, Makerville

Voice has emerged as the next interface for the smart home. Google, Apple and Amazon are in a race to capture this market with their services and hardware. In these times, it’s necessary to understand how one can make their own hardware which works with these services as well as dd voice as a form of user control for their connected devices.

Amazon is leading the pack in terms of first-to-market as well as developer engagement. With AVS and the Skills API, Amazon is ensuring that it has covered the full spectrum for anything related to voice interfaces. It’s Echo range of devices have sold millions of units and are becoming the central hub in the smart home ecosystem. Amazon’s AWS and it’s IoT offerings, which are offered independent from Alexa, perfectly complement it and are gaining a lot of adoption and traction.

Key takeaways:

  • How to integrate voice in your next product
  • How to build voice apps (also known as skills) for your connected appliances 


By Pranav Pai Vernekar, Founder, Inventrom

  1. Introduction to IoT and the Bolt IoT Platform: 15 mins
  2. Interfacing electronics • Interfacing a simple actuator(LED) and writing a code for control: 30 mins • Interfacing a digital sensor and writing code for data pull: 15 mins
  3. Setting up Bolt cloud platform and linking to Bolt Card: 20 mins
  4. Visualising sensor data in the form of graphs and charts: 15 mins

Project: 1. Appliance Control • Interfacing bolt hardware to Relay and appliance: 10 mins • Building Smartphone app UI for controlling appliance: 20 mins • Linking App to Bolt Cloud: 10 mins • Internet control and monitoring of appliance: 20 mins 2. Internet Controlled robot • Assembling hardware of Robot and interfacing with Bolt Platform: 30 mins • Building Smartphone Remote for robot control: 20 mins • Linking physical pins to smartphone remote: 10 mins • Writing a code for various controls of Robot: 15 mins 


By Srinivasa MoorthyCEOAndhra Pradesh Electronics IT Agency (APEITA)

With the advent of Internet of Things electronics systems are proliferating into every nook and corner. Conventional Electronics design involved multiple capabilities (Electrical, mechanical, Software, Compliance etc.) and needed a big team to design a single product. With the IoT the volume of products designed are exploding pressure on reduced time to market and lack qualified experts is putting pressure on companies to find ways of efficient development. “DEFINE” (stands for Design, Environment, Functionality, Implementation, Necessities, Enablers) framework which enables the designers to develop the architecture of an y embedded systems . This framework enables the designers to develop the contours of the product quickly and takes the system design to the next phase quickly. This chapter will explain the framework in details by detailing every element involved in the framework. This chapter will also give a checklist and guideline to help the designer to develop the overall product quickly and efficiently. Idea of the  workshop  is to give a simple checklist and guideline based approach to design the over all product architecture (today there is no literature which is available as it is mostly comes out of experience). With startups and entrepreneurs access to experienced consultants is a challenge and this framework allows them to develop the high level product architecture easily. The session will have about 50 mins of lecture and 20 mins case study and 10 mins of Q&A.  


By Anirban Chowdhury, Co-founder and Director, Technology, Frugal Labs Tech Solutions Pvt Ltd

The workshop will focus on data handling in a IoT device under different application domains and how its different from the normal data. Adjustments to be done due to the amount of data produce and its real time nature. And finally how to analyse it depending on the requirements.

1. Sending the data:

  • Data acquisition from sensor
  • Protocol implementation for data transfer from the device to the server 

2. Storing the data

  • Setting up Brokers and acquiring the data to be store with time-stamp
  • Time series database(InfluxDB)
  • Read/ Write/ Edit/ Delete data from the DB
  • Simple queries 

3. Analysing the data

  • Basic logic scripts
  • Getting Started with Pandas
  • Data Loading
  • Plotting and Visualisation 

Key take aways:

  • Understanding of IoT data flow
  • Basic DB understanding
  • Analytical tool : Pandas 


By Nihal Kashinath, founder, IoTBLR

Ways to evaluate if IoT is a requirement or not for a particular business Exposure to different revenue models for IoT Hands-on experience in choosing the right model for a given IoT use case. Understanding of Lean Business Canvas framework Hands-on experience in constructing a business model for a given IoT usecase”. This workshop teaches participants to evaluate the need for IoT in their businesses and also introduces them to some of the effective revenue models being used to extract value from IoT implementations. Following that, participants working in teams will take up specific IoT usecases (utilities in a smart city, industry automation, health tech for hospitals, smart agriculture, etc) prepare a business model for it, diving deep into concepts of value proposition, customers, revenue generation, profitability, etc.


By Pranav Pai Vernekar, Founder, Inventrom

  1. Introduction to IoT and the Bolt IoT Platform: 15 mins
  2. Interfacing electronics
    1. • Interfacing a simple actuator(LED) and writing a code for control: 10 mins
    2. • Interfacing a digital sensor and writing code for data pull: 15 mins
  3. Building a smartphone remote for control of actuator: 10 mins
  4. Building a UI for presentation of sensor data : 15 mins
  5. Setting up Bolt cloud platform and linking to Bolt Card: 10 mins
  6. Visualising sensor data in the form of graphs and charts: 15 mins
  7. Internet control of actuators using Bolt Cloud: 10 mins

Project: 1. Temperature Monitor • Interfacing Bolt with temperature sensor and writing script for data collection: 20 mins • Building a cloud UI for monitoring the temperature: 20 mins • Setting up trigger based mechanisms based on temperature: 10 mins • Script for tracking device status: 10 mins Q&A and Brainstorm session : 20 mins