Define
Describe the user, need, operating environment and measurable outcome.
Bring the ideas together. Choose a useful problem, plan a build, integrate the electronics and firmware, then test what you have made. These project briefs turn the concepts from earlier modules into practical engineering work.
A project is more than connecting components until something moves or lights up. It is an opportunity to demonstrate that you can define a problem, select suitable parts, make the system behave as intended and collect evidence that it works under stated conditions.
Describe the user, need, operating environment and measurable outcome.
Draw the block diagram, choose interfaces and check component ratings.
Prove risky subsystems first, then integrate wiring, firmware and enclosure.
Test normal operation, edge cases and faults. Record results and revisions.
Start smaller than your ambition. A reliable first version with clear test evidence is more valuable than a complicated prototype whose behaviour you cannot explain.
Choose according to the skills you want to practise and the tools available. The briefs are starting points, not fixed recipes. Adapt the requirements to your own context.
Build a device that measures room temperature, light level and humidity, then presents clear local readings.
Extension challenge: Add min/max logging and a simple trend indicator without making the display difficult to read.
Combine light, temperature and humidity readings into a useful local instrument. Focus on sensor calibration, readable presentation and handling invalid data.
Measure tank level and show low, medium and high states. Design mounting, sensor range, fault indication and service access. Begin with indication only.
Integrate reflectance sensors, a distance sensor, motor driver and state-based behaviour on a differential-drive chassis.
Measure shaft speed with an encoder, compare it with a target and use controlled PWM to reduce speed error under changing load.
Send sensor telemetry from a microcontroller to a local web interface, with timestamps, stale-data handling and clear connection status.
Create a protected test fixture that measures a selected low-voltage input, displays readings and guides repeatable component checks.
| Stage | Work to complete | Evidence before moving on |
|---|---|---|
| Problem and requirements | Define who needs it, what it must do, operating limits, cost and safety boundaries. | A short design brief with measurable acceptance criteria. |
| Architecture | Draw sensor, controller, power, driver, communication and user-interface blocks. | Block diagram and interface list with voltage/current assumptions. |
| Parts and calculations | Check datasheets, pinouts, supply needs, resistor values, thermal limits and mechanical fit. | Bill of materials with exact part variants and alternatives. |
| Subsystem tests | Test sensors, drivers, displays, power and communication separately. | Measurements and notes for each subsystem. |
| Integration | Combine proven blocks, organise wiring and implement clear firmware states. | Repeatable end-to-end demonstration. |
| Verification | Test expected values, boundary conditions, startup, reset and safe fault behaviour. | Results against pass/fail criteria, including failures and corrections. |
| Revision and handover | Improve the design, document versions and explain how to operate and maintain it. | Schematic, code, photos, test log and known limitations. |
Safety boundary: These project directions are for appropriately designed extra-low-voltage learning prototypes. Do not turn a lesson into an exposed mains, high-energy battery, high-voltage or safety-critical build. Use current-limited supplies, rated drivers and independent protection where a physical hazard exists. A hobby sensor or prototype is not a certified life-safety device.
Use this checklist before presenting a project as complete. Completion means more than a successful demonstration: it means you can explain the design and support your claims with evidence.
For each project, keep a short problem statement, block diagram, schematic, source code, photographs, measured results and a note about what you changed after testing. A few well-documented projects show more than many unexplained demonstrations.
Be ready to answer: Why this sensor? Why this driver? What happens when a reading is wrong? How did you choose the power supply? What did your measurements reveal? What would you change in a second revision?
Return to the relevant lessons when a project exposes a knowledge gap. Use the interactive experiments to explore a principle, the project playground to try ideas, and the calculators to check component values. Then take suitable low-voltage work to the bench and compare the real result with your prediction.
If you reach a point where you need a second technical perspective, structured practical sessions or project-specific troubleshooting, EazyLife can discuss guidance suited to that particular project. The open lessons and project briefs remain available to explore independently.
Use the product-design process from the previous module to turn one of these project briefs into a structured, testable design.
For learners who want personalised feedback, guided bench sessions or help developing a specific project, EazyLife can discuss a suitable support arrangement. Independent learning and experimentation remain open.
This is the final module in the EazyLife STEM Lab learning series. The published lessons end here, but the engineering work does not. Keep asking questions, building carefully, testing honestly and improving what you make.