How shadow-leaked/bca-6th-sem works
Project Type and Purpose
• This is an educational IoT hardware-software lab series built around Arduino UNO-compatible boards.
• Each folder (01_led_blinking through 08_bluetooth_relay) is a standalone “module” combining firmware, sensors, actuators, and (in later labs) wireless interfaces.
• Purpose: teach students sensor interfacing, actuators, displays, communication (Bluetooth), and home-automation concepts.
File Structure
• Top-level: README.md, LICENSE, plus a directory “iot_practical.”
• Inside iot_practical: eight numbered subfolders, each containing one .ino sketch file and a readme.md.
• No backend or frontend code—firmware only. No CI/CD or deployment scripts beyond uploading sketches.
• Common configuration: pin assignments, library includes.
Main Components
a. Hardware Layer
– Microcontroller Unit (MCU): Arduino UNO / Nano / Mega / UNO R4.
– Power Supply: USB or external 5 V.
– Sensors & Inputs: LED (output), Push Button, LDR, LM35/DHT22, MQ135, HC-05 Bluetooth RX/TX, Relay.
– Actuators & Displays: LED, 16×2 LCD, Relay contacts.
b. Firmware Layer
– Sketch (.ino) running in Arduino loop().
– PinMode configuration, digitalRead/digitalWrite, analogRead, library calls (LiquidCrystal, DHT, SoftwareSerial).
c. Communication & UI Layer
– Bluetooth HC-05 ↔ Smartphone App (“Serial Bluetooth Terminal”).
– LCD display for local feedback.
d. Optional External System
– Mobile App (Android) as remote control/UI.
Relationships & Data Flows
• Sensor → MCU: analogRead/digitalRead → firmware logic.
• MCU → Actuator/Display: digitalWrite or library APIs → LED blink or LCD text or relay ON/OFF.
• MCU ↔ Bluetooth module: UART (TX/RX) ↔ mobile app.
• Power bus feeding all hardware modules.
Architectural Patterns & Principles
• Layered separation: Hardware vs Firmware vs User Interface.
• Common firmware loop handling events in each practical.
• Reusable pin-configuration block; modular code per sensor/actuator.
• For Bluetooth modules: decouple serial comm logic from display/actuator logic.
Final Checklist
• All major components (MCU, power, sensors, actuators, communication).
• Annotations for pin assignments or library names if more detail is required.