IoT & Robotics
Lab Curriculum.

BUG FOUND: learners who can connect a sensor once, but cannot keep a device system working.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Sensors and actuators: types, ranges, and failure modes.
2. Microcontroller / single-board basics and GPIO.
3. IoT communication basics: MQTT / HTTP concepts, topics, and payloads.
4. Data flow: sensor → device → gateway → dashboard.
5. Robotics basics: motors, servos, and control loops.
6. Logging and monitoring a device system.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: sensor kits / simulators, MQTT tools, dashboards, logs.

• BUG #1: Sensor data stops arriving — trace sensor → device → network → dashboard, find the broken link, restore it.
• BUG #2: Unreliable data: spikes and gaps — find the sensor / power / network cause, filter or fix correctly, prove stability.
• BUG #3: Robot movement fault: wrong direction / overshoot — find the control / wiring / calibration cause, fix it, test safely.
• BUG #4: Dashboard shows stale data — find the caching / connection cause, fix freshness, add a stale-data alert.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Navigate a device network and code: map every device, topic, and dashboard field.
• Fix the weak link in a multi-device system without breaking other devices.
• Add monitoring (heartbeat, battery, signal) to an unmonitored device.
• Review a peer's device change for safety, power, and failure handling.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — a working IoT prototype simulation with a fault log, operating note, and demo.

$ ship → PROOF — exact output: prototype simulation, fault log, and an operating note.

$ run --lab iot-robotics → ✓ SHIPPED, job-ready