EAZYLife STEM LAB · MODULE 28

Electronics Product Design

A circuit that works on a breadboard is only one part of a product. Learn to turn a real need into requirements, a system architecture, a reliable prototype and a design that can be tested and improved.

Free open lessonEngineering design workflowPrototype to product
NEED · DESIGN · BUILD · VERIFY
01 · START WITH A REAL NEED

Do not begin by choosing a microcontroller

Product design starts with a problem worth solving. A useful device is not defined by how many sensors or features it contains. It is defined by whether it solves the intended problem for a particular user, in the environment where it will be used, within realistic cost, power, safety and maintenance limits.

Ask before designing

  • Who will use the device, and what are they trying to achieve?
  • What happens today, and what is inconvenient, expensive or unreliable?
  • Where will the device operate: indoors, outdoors, dusty, wet, hot or vibrating?
  • What must it do, and what is deliberately outside the first version?
  • How will a user know it is working or detect a fault?

Separate needs from solutions

“I need to know when a storage tank is nearly empty” is a user need. “Use an ultrasonic sensor and ESP32” is one possible solution. Keeping these separate prevents early attachment to a component before the requirements are understood.

A product can be simple and still be well engineered. Unnecessary features create cost, power use, failure modes and support work.

Design exercise: Write one sentence describing the user, the problem and the outcome. If the sentence is vague, the design brief is not ready.

02 · TURN THE IDEA INTO REQUIREMENTS

Make success measurable

A requirement describes something the product must do or a constraint it must respect. Good requirements are clear enough to test. Avoid words such as “fast”, “accurate”, “low power” or “cheap” unless you define what they mean for this project.

Requirement typeExample for a tank-level alertHow to verify
FunctionIndicate low, medium and high level states.Present known target distances and check each state.
PerformanceUpdate the displayed level at least once every 2 seconds.Time repeated updates.
PowerOperate from a specified protected 5 V supply.Measure voltage and current during operating modes.
EnvironmentElectronics enclosure must be protected from splashes.Inspect enclosure design and use a suitable controlled test; do not expose an unsealed prototype to water.
UsabilityA user can identify an alarm without reading a manual.Observe representative users responding to the indicators.
Cost and serviceCommon replaceable sensor and accessible wiring connector.Review bill of materials and service procedure.

Build a measurable requirement

Requirement preview

The product shall show a low-level warning at or below 20%. Verify by comparing indication at known tank levels.

This helper formats a draft requirement. Engineering review is still needed to decide whether the target is useful, safe and measurable.

03 · SYSTEM ARCHITECTURE

Divide the product into understandable blocks

A block diagram shows how information and energy move through a system before you commit to detailed wiring or a PCB. It helps reveal missing functions and interfaces.

SensorInput signalControllerLogic and decisionsOutput driverPower interfaceActuatorPump / relay*User interfaceDisplay / buzzerPower managementRegulation / protectionPower to each block*Illustrative system only. A real actuator requires a correctly rated driver and independent protection where needed.
Example architecture for a small monitoring and control product. Signal paths and power paths should be considered separately.

Define interfaces

  • Signal type: analogue voltage, digital logic, pulse, I²C, SPI or UART.
  • Voltage levels and common reference.
  • Connector type, pin order and cable length.
  • Current demand and whether a driver is required.
  • Startup, shutdown and fault behaviour.

Design for failure

Ask what happens if a sensor disconnects, a reading becomes implausible, power dips, a motor stalls or communication stops. Decide what the device should do in each fault state. Do not assume that software alone can make a hazardous actuator safe.

04 · COMPONENT SELECTION

Choose parts by their actual specifications

Component selection is a comparison between requirements and datasheet limits, not a popularity contest. A part that works on a demonstration board may be unsuitable for the final environment or load.

CheckQuestions to answer
Electrical limitsSupply range, absolute maximum ratings, input thresholds, output current and power dissipation?
PerformanceAccuracy, resolution, speed, noise, temperature range and repeatability?
CompatibilityLogic voltage, interface, library support, connector and mechanical fit?
AvailabilityCan the part be sourced consistently? Is there a second-source option?
LifecycleIs it obsolete, difficult to replace or dependent on a fragile supply chain?
CostWhat is the total cost including PCB, enclosure, connectors, protection, assembly and testing?

Datasheet habit: Read the recommended operating conditions, absolute maximum ratings, typical application circuit, pin descriptions and thermal information. Absolute maximum ratings are stress limits, not normal operating targets.

05 · POWER BUDGET AND THERMAL CHECK

Will the product have enough power?

List every subsystem and estimate its current in each operating state. Include startup peaks, radio transmission, motors, relays and displays. A supply that can provide the average current may still fail during a peak load.

Power budget estimator

Enter each load's voltage, current and quantity. The model sums nominal power and current per rail; it does not estimate startup peaks or validate a regulator.

LoadVoltage (V)Current (mA)Qty
Nominal total power0.77 W
Estimated power with headroom1.00 W
Sum of load currents*160 mA

Illustrative sum across the entered loads. Currents at different voltages are not directly additive for selecting one supply. Group loads by rail and account for conversion efficiency and peak demand.

Thermal questions

  • How much power is dissipated in a linear regulator or driver?
  • Can heat escape through the PCB and enclosure?
  • Will nearby components or batteries be heated?
  • Does the design need derating at high ambient temperature?

Battery runtime is an estimate

Runtime depends on usable battery energy, conversion efficiency, load profile, temperature, ageing and cutoff voltage. A simple capacity divided by average current calculation is only a first estimate. Validate with a protected, appropriate battery system and its specified charger.

06 · PROTOTYPE IN STAGES

Reduce uncertainty before committing to a PCB

01

Bench proof

Test the critical sensor, driver, power stage or communication link by itself.

02

Functional prototype

Connect the blocks on a breadboard or suitable development boards. Confirm the main behaviour.

03

Integrated prototype

Bring wiring, connectors, power and enclosure constraints together. Identify interference and thermal issues.

04

Engineering revision

Correct faults, document changes and repeat the tests. Only then prepare a production-intent design.

Do not rush to a custom PCB. A PCB makes a design easier to reproduce, but it also makes mistakes more expensive to correct. Prove uncertain interfaces and high-risk functions first.

07 · ENCLOSURE, PCB AND SERVICEABILITY

The product includes more than its circuit

Mechanical design affects heat, water and dust protection, connector access, mounting, vibration, user interaction and repair. A technically correct circuit can still become a poor product if it cannot be installed, understood or serviced.

PCB design review

  • Check footprints against the exact components and package drawings.
  • Review trace width, current paths, clearances and return paths.
  • Place decoupling capacitors close to the relevant supply pins.
  • Separate noisy switching or motor-current paths from sensitive analogue signals.
  • Label connectors, polarity, test points and revision identifiers.
  • Run ERC and DRC, then inspect the generated manufacturing files.

Enclosure design review

  • Allow for connectors, cable bend radius and mounting hardware.
  • Keep ventilation and thermal paths in mind.
  • Prevent accidental access to hazardous or moving parts.
  • Provide strain relief and sensible cable routing.
  • Make service items reachable without damaging the enclosure.
  • Choose materials and protection ratings for the actual environment.
LidPCB and componentsBaseMountingspacers
Conceptual exploded enclosure view. Actual wall thickness, mounting points, clearances and protection features must be designed for the selected components and environment.
08 · TESTING AND VERIFICATION

Prove the requirements, not just that it powers on

Verification asks whether the design meets its written requirements. Validation asks whether the product solves the user's actual problem. Both matter.

Test stageWhat to record
InspectionPolarity, solder quality, connector orientation, mounting and workmanship.
Power-upSupply voltage, current draw, unexpected heating, reset behaviour.
FunctionalInput range, output states, timing, accuracy and edge cases.
Fault injectionSafe response to disconnected sensors, invalid readings and communication loss.
EnvironmentalTemperature, vibration, dust or moisture tests appropriate to the intended rating.
User validationWhether representative users can install, operate and understand the product.

Keep evidence: record test conditions, measured results, pass/fail criteria, faults found and design revision. “It worked once” is not a repeatable test result.

09 · PRACTICAL DESIGN EXERCISE

Design a low-voltage tank-level monitor

Use the design process to plan a useful monitoring product. This is a design exercise, not a finished safety-certified water-control system. Begin with indication only; automatic pump control can introduce overflow, dry-run and electrical hazards and needs independent protection.

Starting brief

  • Show low, medium and high tank-level states.
  • Use an extra-low-voltage controller and sensor.
  • Provide a clear local display or indicators.
  • Detect a missing or implausible sensor reading.
  • Allow the sensor and controller to be replaced independently.

Suggested system blocks

  • Distance sensor suitable for the tank environment.
  • Microcontroller board with compatible input levels.
  • Three indicators or a small display.
  • Protected regulated supply.
  • Enclosure, cable glands and mounting bracket.

Create your first design review checklist

0 of 8 design checks complete

You can adapt this checklist to a smart plant monitor, room energy monitor, access indicator, small automation controller or another extra-low-voltage project.

10 · FROM PROTOTYPE TO A RESPONSIBLE PRODUCT

Document what you built

A good handover lets another person understand, assemble, test and maintain the product without relying on the designer's memory.

Minimum engineering records

  • Problem statement and requirements.
  • System block diagram and circuit schematic.
  • Bill of materials with manufacturer part numbers and alternatives.
  • PCB source, revision and manufacturing outputs where applicable.
  • Firmware source, version and configuration notes.
  • Assembly, calibration and test instructions.
  • Known limitations, service notes and change history.

Before calling it a product

  • Review electrical, mechanical, thermal and user safety.
  • Check applicable regulations and certification requirements for the market.
  • Assess reliability, repairability and end-of-life handling.
  • Confirm supplier continuity and production test repeatability.
  • Do not claim a protection rating or certification that has not been tested and established.

Engineering is iterative. Build, measure, learn, revise and test again. A prototype is evidence that an idea can work under particular conditions, not proof that every production unit will behave identically.

11 · KNOWLEDGE CHECK

Can you think through a product design?

1. Why should requirements be written before selecting components?

2. A sensor output is 5 V but the controller input is not 5 V tolerant. What should happen?

3. Why include startup and peak current in a power budget?

4. What is the difference between verification and validation?

12 · APPLIED PROJECTS

Put the design process into practice

The final module applies the ideas from this series through project briefs that combine electronics, embedded systems, sensing, control and practical testing.

KEEP LEARNING · GO FURTHER

Keep building beyond the lesson

Use the project ideas and open experiments to practise independently. When a project needs a second technical perspective, personalised troubleshooting or structured practical guidance, you can explore support suited to that specific goal.

Discuss a project