Why do IoT projects fail on demo day?
The most common reasons are not exotic. A loose jumper wire, a sensor powered from the wrong rail, a Wi-Fi network at the college that blocks the cloud service, or a relay that resets the microcontroller when it switches a motor. Each is avoidable with a little planning and testing, which is what mentoring adds.
Examiners also probe understanding: why an ESP32 instead of an Arduino Uno, what protocol the sensor uses, how the readings reach the dashboard, and what happens if the network drops. A model that works but cannot be explained scores far lower than a simpler one the group understands.
How should components be chosen?
| Need | Common choice | Why |
|---|---|---|
| Wi-Fi and enough GPIO | ESP32 | Built-in Wi-Fi and Bluetooth, low cost, Arduino IDE support |
| Simple sensing without network | Arduino Uno or Nano | Easy to learn, very stable |
| Camera, Linux tools or local ML | Raspberry Pi 4 or 5 | Full operating system, Python, OpenCV |
| Long-range low-power links | LoRa modules | Kilometres of range at low data rates |
| Mains switching | Relay module with opto-isolation | Separates high voltage from the controller |
| Dashboard | ThingSpeak, Blynk, Firebase or a small web app | Free tiers suit student projects |
Most student IoT projects need ₹1,500 to ₹4,000 of components. Camera and Raspberry Pi projects cost more. Components are bought at actual cost or by you directly.
What does a good IoT build process look like?
- Draw the block diagram: sensors, controller, actuators, power supply, network and dashboard.
- Write a power budget so every module gets the voltage and current it needs.
- Prototype each sensor and actuator on its own, with a short test sketch and logged readings.
- Integrate one module at a time, testing after each step.
- Move from breadboard to a soldered board or simple PCB once the circuit is stable.
- Connect the dashboard and log real data for several days to use in your results chapter.
- Prepare demo-day spares and an offline fallback in case the college network blocks the cloud.
Which IoT topics work well?
- Smart energy meter with theft detection and a monthly usage dashboard
- Soil moisture and weather-based irrigation controller for a real plot
- Cold-chain temperature logger with SMS alerts for a pharmacy or dairy
- Gas leakage detection with automatic exhaust and buzzer
- Parking slot occupancy display for a campus lot
- Patient vital signs monitor with threshold alerts for caregivers
How does mentoring work?
- Share the topic, branch, deadline and the components you already have.
- Free scope call to fix the block diagram, the bill of materials and the demo plan.
- Pay 50% to book; the balance is due after you see the build reach the agreed stage.
- Guided build with reviews of circuits, wiring photos and firmware every 2 to 3 days.
- Debugging sessions over video when something will not work.
- Report guidance: circuit diagram, BOM table, flowchart, readings and results.
- Mock viva on sensors, protocols, power and failure modes.
What do you get?
- Reviewed block diagram, power budget and bill of materials
- Firmware reviews with explanations of each part of the code
- Debugging help for wiring, power and connectivity
- Report guidance with real readings and graphs
- A demo-day checklist
- Mock viva with embedded and IoT questions
Which plan fits?
| Plan | Best when | Price |
|---|---|---|
| Core Branch Mini Project | Simulation or small hardware mini project | ₹2,999 |
| Hardware / IoT Final Year | Final year working model with report and viva | from ₹9,999 |
| Diploma ITR | MSBTE fifth-semester industrial training project | ₹1,999 |
How should an IoT project report be organised?
| Chapter | What to include |
|---|---|
| Introduction | Problem, users, objectives and why an IoT approach fits |
| Literature survey | Similar systems, the sensors and protocols they used, their limits |
| System design | Block diagram, circuit diagram, power budget, flowchart |
| Hardware | Components with specifications and the bill of materials with costs |
| Software | Firmware structure, communication protocol, dashboard or app |
| Testing and results | Sensor calibration, logged readings, graphs, response times |
| Conclusion | What worked, limitations, cost, future improvements |
Which power and safety checks matter?
- Never power motors, pumps or solenoids from the microcontroller's own regulator
- Use a common ground between modules, and check it first when readings are erratic
- Add flyback diodes across relay coils and inductive loads
- Keep any mains wiring enclosed, insulated and switched through an isolated relay module
- Fuse the supply and label voltages on the board for the demo
- Test the full system for at least an hour before the review to catch heating and resets
How do you log data for the results chapter?
Log readings with timestamps from the first stable prototype, not only on the last day. A few days of real data lets you plot trends, show how the system reacted to events such as a gas leak test or a dry soil spell, and calculate response times. Export the logs as CSV from the dashboard or an SD card, and keep the raw files: examiners sometimes ask how a graph was produced.
Which communication protocol should you use?
Match the protocol to the job. Sensors on the same board usually talk over I2C or SPI, and your viva will include a question on the difference. For sending readings to a dashboard, HTTP requests are simplest to explain, while MQTT is better when many devices publish frequently or the network is unreliable. Bluetooth Low Energy suits short-range phone apps, and LoRa suits farms or campuses where Wi-Fi does not reach. Whichever you pick, be ready to draw the message flow from sensor to screen.
Frequently asked questions
Do you supply the components?
You can buy them yourself from our bill of materials, or we can arrange them at actual cost. Either way, you assemble and test the model with guidance.
ESP32 or Arduino for my project?
Choose ESP32 if you need Wi-Fi, Bluetooth or more pins; Arduino Uno if the project is standalone and you want the simplest setup. We help you decide on the scope call.
What if the college Wi-Fi blocks my cloud dashboard?
Plan an offline fallback: a local web page served by the ESP32, a mobile hotspot, or an LCD display. We include this in the demo-day checklist.
Do you help with PCB design?
Yes, at a student level: moving a stable breadboard circuit to a simple PCB or perfboard layout, with a clear schematic for the report.
Which IoT viva questions should I prepare?
Expect questions on the sensor working principle, communication protocols such as I2C, SPI and MQTT, power supply design, why you chose the controller and how you handle network loss.
How much does it cost?
Mini projects from ₹2,999; final year IoT models from ₹9,999 plus components at actual cost.