Schematic with clean ERC
Deliverable: A complete schematic for a supplied circuit, hierarchically organised, passing electrical rule check with every remaining warning explained.
Course
Board design taken to manufacture — schematic, footprints, layout, planes and Gerbers — with the checks that decide whether a fab house builds it or sends it back.
6 modules · 3 months
Deliverable: A complete schematic for a supplied circuit, hierarchically organised, passing electrical rule check with every remaining warning explained.
Deliverable: A footprint created from a datasheet package drawing, printed at 1:1 and physically checked against the real component before use.
Deliverable: A routed two-layer board with a continuous ground plane, correct track widths for the currents involved, passing DRC against a stated fab capability.
Deliverable: Gerbers, drill files, fabrication drawing, assembly drawing and BOM, checked in a Gerber viewer and reviewed as a fab house would review them.
Every student gets placement assistance — that is what 100% placement assistance means. It is support for all, not a job for all. We do not promise a specific salary, a specific number of interviews, or placement at any named company, and you should be wary of anyone who does.
Unlike almost everything else taught here, a PCB mistake costs money and weeks.
Fabrication takes a fortnight. A wrong footprint means the part will not fit and the whole run is scrap. A missing DRC check means the fab house rejects the files and you start the queue again. There is no undo.
So the course is organised around the checks — ERC, DRC, a printed footprint held against the real component, and a Gerber review before anything is sent.
Two minutes, a sheet of paper at 1:1, and the actual component.
It is the least sophisticated technique in the entire course and it catches the single most expensive error. Every experienced hardware engineer does it, and almost every beginner learns to only after paying for a board they cannot populate.
A schematic shows current going out. The layout decides how it gets back.
Most noise, coupling and EMC problems are a return path forced to take a long way round by a split or a gap in the ground plane. Planes get their own module because this is invisible on screen and obvious on an oscilloscope, and it is where layout stops being a drawing exercise.
A layout engineer who works from the netlist alone will produce a board that passes every check and misbehaves.
Which nets are sensitive, where decoupling has to physically sit, what runs hot, what must not run beside what — none of that is in the netlist. Understanding the circuit is part of laying it out, and this course treats it that way.
Questions
The course uses both. KiCad is free and increasingly used in startups and small firms, so you can practise at home. Altium is common in established Indian hardware companies and is what many advertisements name. The design skills — placement, planes, DRC — are the same in either, and only the interface differs.
Because a wrong footprint is the most expensive mistake in board design. The board comes back from fabrication, the part does not fit, and the whole run is scrap. Printing at 1:1 and physically placing the component on it takes two minutes and catches the error while it is free.
For signals, rarely. For power, very much — an undersized track carrying two amps heats, and in the worst case lifts off the board. The routing module gives you the actual relationship between width, copper weight and current, so it is a calculation rather than a guess.
You need to understand it. Where decoupling goes, which nets are sensitive, where return current flows — none of these are visible from a netlist. A layout engineer who does not read the circuit produces boards that pass DRC and behave badly, which is worse than one that fails outright.
Three details is all we need. A course advisor will call you back.
Firmware written close to the metal — registers, interrupts, timers and buses — debugged on real hardware, because embedded bugs live where a simulator cannot show them.
The fastest way to make electronics actually do something — sensors, motors, displays and code — taught by building prototypes you design rather than diagrams you copy.
Hardware description taught as hardware, not as programming — RTL that synthesises, testbenches that prove it, and designs that meet timing on a real FPGA.
Electrical drafting for panels and installations — schematics, layouts, cable schedules and wire numbering — built so the person commissioning the panel can trace every circuit.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.