In this guide
Why You Should Not Submit Every Project on a Breadboard
A breadboard is excellent during experimentation. You can quickly change sensor connections, replace resistors, move GPIO pins, test different modules, troubleshoot your circuit, and add or remove components without soldering.
But this flexibility comes with a disadvantage: connections are temporary. Jumper wires can loosen. A wire can move while transporting the project. Two similar-coloured wires can be accidentally swapped. Long breadboard connections can also make the finished prototype difficult to understand.
That is why a breadboard should usually be treated as a development stage, not automatically as the final construction method.
A typical student workflow is:
Idea
↓
Breadboard prototype
↓
Test circuit and firmware
↓
Freeze the working design
↓
Draw final schematic
↓
Perfboard / Stripboard / Custom PCB
↓
Solder
↓
Electrical testing
↓
Final assembly
Viva point: Moving from a breadboard to a soldered board is not mainly about appearance. You are replacing temporary contacts with mechanically stronger, more repeatable electrical connections.
When Should You Leave the Breadboard Behind?
Do not solder the project immediately after the LED turns on once. Your breadboard prototype should first be stable enough that you are no longer changing the basic circuit every few hours.
A good time to move forward is when:
- all important sensors work,
- the microcontroller pin assignments are decided,
- the required power rails are confirmed,
- communication interfaces work reliably,
- the firmware has been tested,
- you know which connectors you need,
- the circuit survives repeated power cycles,
- the major design is unlikely to change.
For example, if you are still deciding whether your ESP32 should use GPIO 18 or GPIO 19 for a sensor, keep using the breadboard. If your complete system has worked correctly for several test sessions and you mainly need a sturdy final build, you are ready for the next stage.
Do Not Rush Because Submission Is Near
One of the worst student workflows is:
Circuit works once on breadboard
↓
Immediately solder everything
↓
Project stops working
↓
No idea which connection failed
Freeze and document the working circuit first. Take photos of the breadboard. Save your final pin mapping. Draw a schematic. Record supply voltages. That information becomes your reference when troubleshooting the soldered version.
Perfboard, Stripboard or Custom PCB?
You do not automatically need a custom PCB for every final-year project. The right construction method depends on complexity, available time, how many copies you need and how polished the prototype needs to be.
| Method | Best suited for | Main advantage | Main limitation |
|---|---|---|---|
| Breadboard | Development and experimentation | Very easy to modify | Temporary connections |
| Perfboard | One-off final prototypes | Flexible placement and soldered connections | Manual wiring can become messy |
| Stripboard | Small circuits with repeated connections | Copper strips reduce some point-to-point wiring | Tracks must be planned and sometimes cut |
| Custom PCB | Stable, repeatable final designs | Clean routing and professional layout | Requires PCB design and fabrication |
Perfboard
Perfboard contains a grid of holes with individual copper pads or similar solderable points depending on board type. You insert components through the holes and manually create electrical connections using component leads, insulated wire, solder bridges where appropriate, and jumper wires.
Perfboard is useful when your project has an ESP32 development board, two or three sensors, a buzzer, LEDs, a few resistors, connectors, and a small power section. It is especially practical for a single college prototype because you can still modify the circuit relatively easily.
Stripboard
Stripboard has parallel copper strips running across the board. Components are connected where their leads share a copper strip. You may need to cut tracks to electrically separate sections. For example:
Copper strip:
=================================
After track cut:
============== ==============
Stripboard can reduce manual wiring, but you need to plan carefully. An unintentional continuous strip can short signals that should be separate.
Custom PCB
A custom PCB is the better choice when the circuit is final, wiring is becoming dense, you need several identical boards, connector positions matter, board size matters, the prototype must withstand frequent handling, or you want the design to be reproducible.
A PCB design normally starts from the schematic, assigns physical footprints to components, places them on the board, and routes copper connections between them. Tools such as KiCad support this schematic-to-PCB workflow.
Important: A PCB does not automatically fix a bad circuit. If the schematic, pin mapping or power design is wrong, the PCB can reproduce the same mistake very neatly.
Quick Decision Framework
Use this simple rule:
Is the circuit still changing?
|
Yes
|
Breadboard
↓ No
Need dense wiring, repeatability or a polished board?
|
Yes
|
Custom PCB
For many final-year projects, a good perfboard build inside a proper enclosure is completely reasonable. A custom PCB becomes more valuable as wiring complexity and repeatability increase.
Step 1: Convert the Working Breadboard Into a Schematic
Do not copy the physical breadboard arrangement directly. A breadboard shows where wires happen to be placed. A schematic shows how the circuit is electrically connected.
For example, instead of documenting "Blue wire from row 18 to row 31", document:
ESP32 GPIO 21 → OLED SDA
ESP32 GPIO 22 → OLED SCL
3.3 V → OLED VCC
GND → OLED GND
Then draw the actual schematic. Your schematic should include: microcontroller, sensors, resistors, LEDs, transistors, connectors, power inputs, voltage regulators if used, ground connections, communication lines, and protection components where required.
Label important signals. For example:
SDA
SCL
TRIG
ECHO
BUZZER
3V3
5V
GND
A clean schematic also helps during your viva because you can explain the system logically rather than tracing jumper wires.
Step 2: Plan the Physical Layout Before Soldering
Do not begin soldering components randomly onto an empty board. First place the components without soldering them. Think about: where power enters, where the ESP32 will sit, connector accessibility, USB port access, sensor cable direction, space for mounting screws, display position, heat-producing components, wire length, and enclosure dimensions.
Keep Related Components Together
If a sensor interface uses a pull-up resistor, keep that resistor reasonably close to the relevant circuit instead of placing it on the opposite side of the board. Keep power components grouped together. Try to keep signal paths understandable.
Make Replaceable Modules Replaceable
Suppose your project uses an ESP32 development board. Instead of permanently soldering the entire development board directly to the perfboard, use suitable female headers:
Perfboard
|
Female headers
|
ESP32 development board
If the ESP32 fails, you can remove it without desoldering dozens of pins. Sockets can similarly be useful for some removable ICs or modules.
Practical tip: Before soldering headers, insert the module temporarily so the two header rows remain aligned. Remove the module before performing any soldering that could unnecessarily heat it.
Step 3: Understand Basic Soldering Technique
Good soldering is mainly about transferring enough heat to the surfaces that need to join and then allowing solder to wet those surfaces properly.
Tin the Iron Tip
A clean soldering tip should have a thin coating of solder — this is called tinning. Tinning helps transfer heat from the tip to the joint. If the tip is dry, heavily oxidised or covered in burnt residue, heat transfer becomes much worse. Clean it using the cleaning method recommended for your station, then apply a small amount of fresh solder.
Heat the Joint, Not Just the Solder
This is the most important beginner rule. Bad technique: iron → solder wire → giant melted blob → cold component lead.
Better technique — touch the iron so it heats both the component lead and the copper pad, then feed solder into the heated joint:
solder wire
↓
Component lead + copper pad
↑
iron tip
The solder should melt because the joint is hot enough, not only because you pressed solder directly onto the iron tip. Official soldering guidance from Adafruit similarly recommends heating both the pad and component lead before applying solder: https://learn.adafruit.com/adafruit-guide-excellent-soldering/making-a-good-solder-joint
Use Enough Solder, Not Maximum Solder
More solder does not make a stronger electrical connection. Too much can hide the actual joint, create bridges, make inspection difficult, and connect neighbouring pads accidentally. For a typical through-hole connection, you want solder to flow around both the pad and the lead rather than forming a loose ball.
Let the Joint Cool Without Movement
After removing the iron, do not move the component immediately. Movement while the solder is solidifying can produce a disturbed or unreliable joint. Hold the component steady for the short cooling period.
What Soldering-Iron Temperature Should You Use?
There is no universal perfect temperature. The correct setting depends on: solder alloy, lead-free versus leaded solder, tip size, copper area, component size, thermal mass, and soldering station performance. Lead-free solder usually requires somewhat more heat than common tin-lead solder formulations.
As one practical reference, Adafruit's soldering guide suggests about 400°C for lead-free solder and about 370°C for 60/40 tin-lead solder on a temperature-controlled station: https://learn.adafruit.com/adafruit-guide-excellent-soldering/preparation
Treat these as starting guidance, not mandatory settings. Use the temperature recommended for your solder and equipment, and aim to make the joint efficiently without keeping the iron on the component longer than necessary.
Warning: Excessive heat or excessive contact time can damage pads, connectors, insulation and temperature-sensitive components. Increasing temperature is not a substitute for using the correct tip, clean surfaces and adequate flux.
Soldering Safety for Student Projects
A soldering iron can cause serious burns, and soldering fumes should not be ignored.
Work in a Ventilated Area
Soldering creates fumes mainly associated with heated flux. Use appropriate ventilation or fume extraction. Do not intentionally breathe the smoke above the joint. A small desk with your face directly over the soldering point is poor practice.
Prefer Lead-Free Solder Where Appropriate
Lead-free solder avoids the lead exposure associated with lead-containing solder, although lead-free soldering still requires proper ventilation because flux fumes remain. If your college laboratory specifies a particular solder alloy, follow the lab's safety procedure. If you handle lead-containing solder: wash your hands afterwards, avoid touching your face, do not eat while soldering, keep solder away from food areas.
Wear Eye Protection
Eye protection is useful when cutting component leads, desoldering, working with spring-loaded tools, when solder accidentally spits, or trimming wires. A clipped component lead can travel much farther than you expect.
Always Use an Iron Stand
Never put a hot iron directly on the desk, cardboard, wires, or your project enclosure. Return it to a proper stand whenever it is not in your hand.
Power Down Before Modifying the Circuit
Do not solder a normal prototype while it is powered. Disconnect USB, batteries, bench supplies, and external adapters. Then verify power is removed before working.
Common Bad Solder Joints and How to Fix Them
Cold or Disturbed Joint
A cold or disturbed joint may look rough, irregular, cracked, or poorly flowed. Possible causes include insufficient heating or movement while the solder was cooling.
Fix: Reheat the joint properly, allow the solder to flow across the pad and lead, then let it cool without movement.
Solder Bridge
A bridge occurs when solder unintentionally connects neighbouring pads or pins. For example:
Correct:
O O O
| | |
Bridge:
O===O O
A bridge between power and ground can stop the entire project and may damage components.
Fix: Remove excess solder using an appropriate desoldering method, clean the area and inspect again under good lighting.
Insufficient Wetting
Sometimes solder forms a blob but does not properly bond to the pad or component lead. Causes can include dirty surfaces, oxidised leads, insufficient heating, poor tip condition, or inadequate flux.
Fix: Clean the joint if necessary, use suitable flux, ensure the tip is clean and tinned, and heat both surfaces properly.
Too Much Solder
A huge solder dome may hide whether the joint underneath is actually good.
Fix: Remove excess solder and remake the joint if necessary.
Too Little Solder
If barely any solder connects the lead and pad, the connection may be mechanically weak or intermittent.
Fix: Reheat the complete joint and feed a small additional amount of solder.
| Problem | Typical sign | Likely cause | Basic fix |
|---|---|---|---|
| Cold/disturbed joint | Rough or poorly flowed surface | Low heat or movement | Reheat and cool undisturbed |
| Solder bridge | Adjacent pads connected | Excess solder | Remove excess and inspect |
| Poor wetting | Solder beads instead of flowing | Dirty/cold surface | Clean, flux and reflow |
| Too much solder | Large blob | Excess feed | Remove excess |
| Too little solder | Incomplete pad coverage | Insufficient solder | Reheat and add a small amount |
Adafruit also documents examples of these common joint problems: https://learn.adafruit.com/adafruit-guide-excellent-soldering/common-problems
Worked Example: ESP32 Water-Tank Monitoring Prototype
Suppose your final-year project contains an ESP32 development board, ultrasonic distance sensor, buzzer, status LEDs, OLED display, and a low-voltage power input. You first prove everything on a breadboard.
Your working pin map might be:
ESP32 GPIO 5 → Ultrasonic TRIG
ESP32 GPIO 18 → Ultrasonic ECHO interface
ESP32 GPIO 21 → OLED SDA
ESP32 GPIO 22 → OLED SCL
ESP32 GPIO 23 → Buzzer control
ESP32 GPIO 2 → Status LED
3.3V / 5V → As required by each module
GND → Common ground
Do not blindly copy this example into another circuit; voltage compatibility and valid GPIO choices depend on your actual modules and design.
Stage 1: Freeze the Breadboard
Test sensor readings, display, buzzer, Wi-Fi if used, and repeated restart behaviour.
Stage 2: Draw the Schematic
Document every connection. If any sensor output exceeds a microcontroller input's allowed voltage, include the required interface circuitry in the schematic rather than relying on an undocumented breadboard trick.
Stage 3: Choose Construction Method
Because this is one college prototype with a modest number of modules, perfboard may be enough. A custom PCB would become more attractive if you wanted several identical units or a much more compact assembly.
Stage 4: Arrange the Board
Place the ESP32 on headers, a connector for the ultrasonic sensor cable, the OLED connector, buzzer, LED and resistor, and the power connector. Keep the ESP32 USB port accessible.
Stage 5: Solder Power First
Solder power input → required supply rails → ground connections, then stop. Do not insert the ESP32 yet. Use a multimeter to check:
VCC ↔ GND short? NO
3.3 V rail correct? YES
5 V rail correct? YES, if used
Ground continuity? YES
Only after the power section is correct should you move on.
Stage 6: Add Signal Connections
Connect sensor, display and output signals one subsystem at a time. Test each stage rather than soldering the entire board and testing only at the end — this makes faults much easier to locate. (A systematic test-each-stage approach is covered in How to Test and Debug Your Final-Year Project Before Submission.)
Schematic → Layout → Solder → Test
This four-stage process should become your default workflow.
1. Schematic
Confirm electrically: what connects to what? What voltage does each part require? Where are power and ground? Which GPIO performs each function?
2. Layout
Decide physically: where will each component sit? Where will wires or copper tracks run? Can connectors be accessed? Can modules be removed?
For custom PCBs, tools such as KiCad follow this schematic-to-board workflow, where schematic connections are transferred into a physical PCB layout.
3. Solder
Work gradually: power → microcontroller headers → one subsystem → test → next subsystem.
4. Test
Use a multimeter before applying power. Check continuity, unintended shorts, supply voltage, polarity, and connector orientation.
For custom PCB design, KiCad's official documentation explains its schematic, footprint, board-layout and design-rule workflow: https://docs.kicad.org/9.0/en/getting_started_in_kicad/getting_started_in_kicad.html
Custom PCB Checks Before Manufacturing
If you decide to make a PCB, do not send the board for fabrication immediately after routing the last track. Check: component footprints, connector orientation, pin numbering, board dimensions, mounting holes, power and ground nets, trace routing, clearances, silkscreen labels, and polarity markings. Run the PCB software's electrical and design-rule checks where applicable.
Print the PCB at 1:1 Scale
A useful practical check is to print the board layout at actual size and place physical components on the printout. This can expose mistakes such as wrong header spacing, a connector too close to the enclosure wall, mounting holes in the wrong position, or a module overlapping another component. A schematic can be electrically perfect while the physical footprint is wrong.
Common Mistakes Students Make During Final Assembly
Soldering Before the Circuit Is Stable
You end up repeatedly desoldering parts because the design is still changing.
Better: Freeze the breadboard design first.
No Schematic
The only documentation is a photo of jumper wires.
Better: Create the schematic before permanent assembly.
Soldering Every Module Permanently
When one board fails, half the prototype must be desoldered.
Better: Use headers or connectors where replacement is reasonably expected.
Ignoring Connector Orientation
A reversed power connector can cause immediate problems.
Better: Mark polarity clearly on the board and enclosure.
Testing Only After Everything Is Finished
When it fails, there may be 50 possible causes.
Better: Test each subsystem as it is added.
Forgetting Strain Relief
A sensor cable directly soldered to a tiny pad may eventually break when repeatedly pulled.
Better: Use connectors, cable ties, mounting points or other suitable strain relief.
Leaving Exposed Loose Wires
Your project works on the table but fails during transport.
Better: Secure wiring mechanically instead of depending on solder joints to carry cable stress.
Trying to Fix Every Problem by Adding More Solder
A bad joint is not automatically a joint with too little solder.
Better: Identify whether the actual issue is heat transfer, oxidation, contamination, bridging or mechanical movement.
What You Should Be Able to Explain in Your Viva
Be prepared for questions such as:
Why did you move from a breadboard to perfboard?
Because the design had become stable and the final prototype required more mechanically reliable permanent connections.
Why did you use perfboard instead of a custom PCB?
Because only one prototype was required and the circuit complexity could still be managed cleanly using point-to-point soldered wiring.
Why might a PCB be better?
A PCB can provide controlled physical placement, repeatable interconnections and easier reproduction when the design is final.
Why do you heat the pad and component lead before feeding solder?
Because both surfaces need sufficient heat for solder to wet and bond to them properly.
What is a cold solder joint?
It is an unreliable joint associated with improper solder flow or cooling conditions and may produce intermittent electrical contact.
How did you test the board before connecting the ESP32?
By checking for shorts, verifying continuity and confirming the required supply voltages before inserting sensitive modules. That last answer is particularly useful because it demonstrates that you followed a deliberate engineering process rather than simply connecting power and hoping the circuit worked.
Final Breadboard-to-PCB Checklist
Before final assembly, confirm:
- The complete breadboard circuit has been tested.
- GPIO assignments are final.
- Power requirements are documented.
- A clean schematic exists.
- Perfboard, stripboard or PCB was chosen deliberately.
- Component placement was planned before soldering.
- Replaceable modules use suitable headers or connectors where practical.
- The soldering tip is clean and tinned.
- Both pad and lead are heated when making a joint.
- The work area has suitable ventilation.
- Eye protection is used where appropriate.
- Every solder joint has been visually inspected.
- There are no accidental solder bridges.
- Power and ground have been checked for shorts.
- Supply voltages were verified before inserting expensive modules.
- Each subsystem was tested separately.
- Cables and connectors have adequate mechanical support.
- You can explain your construction method during the viva.
Conclusion
Moving from breadboard to a reliable final prototype is less about making the project look professional and more about converting an experimental circuit into a documented, mechanically stable and testable system.
The safest workflow is simple:
Working breadboard
↓
Final schematic
↓
Physical layout
↓
Solder one section
↓
Test
↓
Add next section
↓
Final inspection
For a small one-off project, perfboard or stripboard may be entirely sufficient. For a denser, repeatable or more polished design, a custom PCB may be worth the additional design work.
Whichever method you choose, concentrate on clean connections, sensible layout, safe soldering practices and staged testing. If you can explain not only what you soldered but also why you selected that construction method and how you verified it, you will be much better prepared for project demonstration and viva questions.
Sources: