PCB automation in Embedr turns hardware source and board state into a concrete layout proposal. It is part of the project stack, not a separate design island: the same folder contains firmware, pin assumptions, datasheets, schematic source, board files, and the agent conversation that produced changes.
Automation helps with the mechanical parts of board iteration:
- creating a first placement,
- routing board connections,
- applying the result to KiCad board files,
- previewing progress,
- canceling long-running jobs,
- reviewing remaining open nets.
It does not replace electrical judgment. Treat the result as a board proposal that must be reviewed.
The input
PCB automation needs a valid board state. In practice, that means:
- a project folder with
embedr.yaml, - a
pcb/workspace, - a board source file such as
pcb/boards/main.zen, - a generated KiCad project and board,
- footprints that match the parts you intend to use,
- named nets that make sense.
If those pieces are missing, ask the agent to initialize the PCB workspace, build the board, and inspect the netlist before attempting placement or routing.
Auto placement
Auto placement proposes where footprints should sit on the board.
Use it when:
- the schematic is structurally correct,
- footprints exist,
- the board outline is known or acceptable,
- you want a first physical arrangement.
Placement is easier to review than routing. Before running auto routing, inspect placement for connector orientation, mounting constraints, user-facing parts, antenna areas, heat sources, and mechanical clearance.
Placement comments
Placement comments are layout hints stored near the hardware source. They help keep board intent in text instead of hiding it only in a generated layout file.
Use them for constraints such as:
- keep a connector near an edge,
- group a sensor with its support parts,
- keep a status LED visible,
- lock a known-good footprint position,
- keep noisy parts away from sensitive analog traces.
The agent can manage missing or stale placement comments. This is especially useful after a schematic edit changes components or references.
Auto layout and routing
Auto layout routes the board from the current placement. In user terms, it tries to connect the nets by adding tracks to the board file.
Use it after placement has been reviewed. A practical loop is:
- Build or sync the PCB workspace.
- Inspect the board.
- Run auto placement.
- Review component positions.
- Run auto layout.
- Inspect routed and unrouted nets.
- Open KiCad for manual review.
If routing leaves open nets, do not treat that as a mystery. It usually means the board needs better placement, a wider outline, different layer assumptions, or manual routing for constrained nets.
Netlist inspection
The netlist is the electrical graph: which pins are connected to which named nets. It is one of the most important debugging surfaces in board design.
Use netlist inspection when:
- a connection is missing in the preview,
- a power rail seems wrong,
- firmware pin names changed,
- the schematic builds but the board looks incomplete,
- routing reports open nets.
Ask questions like:
Inspect the PCB netlist and tell me whether VCC, GND, SDA, and SCL connect to the expected parts.
Schematic evaluation and linting
Schematic evaluation checks whether the hardware source is internally coherent. Linting catches source-level problems while you edit .zen.
Typical issues include:
- unknown component references,
- missing footprints,
- invalid pin names,
- disconnected nets,
- syntax mistakes,
- stale placement comments.
Fix source-level errors before asking for layout automation. Bad source produces bad board state.
Canceling automation
Placement and routing can take time on non-trivial boards. If a run is clearly not useful, cancel it from the Board tab or decline the approval request before it starts.
Canceling does not mean the project is broken. It just means the current board state or prompt should be adjusted before another attempt.
Review checklist
Before using a generated board for fabrication, check:
- every connector orientation,
- regulator and power path,
- decoupling capacitors,
- trace width for power nets,
- clearance around mounting holes,
- antenna and RF keepouts,
- high-current or high-speed routes,
- silkscreen readability,
- unrouted nets,
- KiCad DRC results.
Embedr can help produce and revise the board. You still own the electrical sign-off.