Join the challenge!

Peripherals
Lab

Are you looking for a challenge where you will design a real-time game controlled via virtual IoT hardware? It's gonna be wild!

IoT Hardware Circuit
IEEE BPDC Logo
* Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! ** Phase 1 Deadline preponed to the 13th! *

Key Objectives

Bridge Physical & Digital

Integrate IoT hardware simulation (Wokwi/ESP32) with real-time game engines (GDevelop/p5.js) using MQTT/WebSockets.

Beyond Basic Electronics

Move past simple circuit building into high-level Human-Computer Interaction (HCI) and system architecture.

Cloud-Based Innovation

Transmit, process, and visualize sensor data from a virtual microcontroller to trigger complex logic in a game.

Full-Stack IoT Skills

Build a portfolio-ready project covering firmware coding (C++/MicroPython), network latency, and front-end dev.

Event Overview

Who can join?
Hardware Engineering
1

1-4 participants per team. Open to all relevant branches/years.

3

Interdisciplinary and cross-domain teams are highly encouraged!

2

Single submission per team.

4

Develop Full-Stack IoT Skills: Equip yourself with a portfolio-ready project covering firmware coding, network latency management, and front-end game development.

Technical Reqs

  • Virtual IoT ControllerWokwi simulation (ESP32-based)
  • Game EnvironmentGDevelop / p5.js / equivalent
  • CommunicationMQTT or WebSockets
  • InteractionReal-time data transmission, sensor-to-action mapping, low latency

Strict Restrictions

  • No Keyboard/MouseCannot be used as primary control. Must use virtual IoT inputs!
  • No Pre-built TemplatesFully pre-built templates are strictly not allowed. Build it yourself.
  • No External HardwareNot allowed unless approved earlier. Stick to Wokwi simulation.

The Official Rulebook

Everything you need to know to survive the Peripherals Lab challenge. Read it, learn it, sketch it.

Download PDF

Event Structure

The challenge is divided into two main phases. Read the rules carefully!

PHASE 1: ANALYSIS

Problem Statement, Stakeholder Analysis, Constraints, Use-case flow. 7 Days duration.

PHASE 2: PRESENTATION

PPT, Live Demo, Technical Report, Future Scope. 3 Days duration.

TECHNICAL REQS

Wokwi simulation, GDevelop/p5.js, MQTT/WebSockets, Low latency.

RESTRICTIONS

No keyboard/mouse as primary control. No pre-built templates.

Evaluation Parameters

View the breakdown of marks.

Total: 60 Marks
Clarity
Relevance
Analysis
Technical
Demo
Phase 110 M
Phase 110 M
Phase 110 M
Phase 210 M
Phase 210 M
Communication5 M
Q&A5 M

Awards & Glory

Awards will be given at the discretion of the IEEE Judging Panel. No plagiarism allowed!

Winner

Runner-Up

Best Design

Best Debugging

Innovation Award

Join the Lab

Ready to build? Fill out the form below to register your team.