AI Copilot
Placement and Routing Assistant
On this page
- Before placement
- Place functional blocks on a schematic
- Run schematic auto-routing
- Update the schematic to a PCB
- Lay the PCB out with /layout
- Choose the copper layer count first
- Ways to use /layout
- Review an applied layout
- One board or a tower: /topology
- Manual override is expected
- Removed legacy content
- See also
Use WireFrame's placement and routing assistance after component identities, footprints, pin counts, and connections have been reviewed. Automatic output is a proposed starting point, not a finished board.
Before placement#
- resolve every missing physical component;
- confirm symbol pins match footprint pads;
- review functional blocks;
- run Netlist Check and ERC;
- confirm the target schematic or PCB is active;
- save the project.
Place functional blocks on a schematic#
When Copilot presents a block card that can be placed:
- Review its components and connections.
- Add or drag the block to the schematic.
- Inspect the placement and wire proposal.
- Apply it only when it targets the intended sheet.
- Move crowded items and re-run ERC.
Run schematic auto-routing#
With the schematic active, use Tools → Auto Wire only after library and netlist checks pass. It draws the wires of the planned netlist with a local orthogonal router — no AI request — and the whole run is one undo step. Inspect:
- whether wires terminate on the correct pins;
- whether labels and junctions remain readable;
- whether power and ground nets are clear;
- whether generated paths cross symbols or hide annotations.
Use Undo or Revise Design when the result is not acceptable.
Update the schematic to a PCB#
After the schematic is approved, use Tools → Update Schematic to PCB. Then give the board its shape — File → Import → CAD Outline, /board, or the Board Fit tab (see Board Shape and Outline). The layout refuses a board with no outline.
Lay the PCB out with /layout#
With the PCB open, type /layout in AI Copilot. The layout runs on a copy of the board in five stages, shown on a live card in the chat as they happen:
| Stage | What it does |
|---|---|
| Place | Puts parts on the board: connectors to the edge facing out, each functional block around its busiest part, decoupling capacitors against the pins they serve |
| Planes | Adds the copper pours the design rules ask for; a split plane gives each rail the region over its own loads |
| Vias | A fanout via for every surface pad of a plane net, into its own rail's region; thermal via arrays in exposed pads |
| Route | Tracks for every net no plane or pour carries. Nothing is forced: a net that cannot be routed cleanly is named, never shipped with a violation |
| Stitch | Ground stitching and the edge via fence, after the tracks |
Nothing changes on the board until you apply. The card has Stop while it runs, then Apply to the board (or Apply this option) and Discard. After applying, Ctrl+Z takes it back one stage at a time.
Choose the copper layer count first#
The number of copper layers sets the board's price and what the layout can do — 2 layers is cheapest (rails routed, ground poured), 4 layers adds inner ground and power planes. It is your decision: Copilot asks for it before the first layout and records the answer for the project; it does not lay a board out until you have answered.
Ways to use /layout#
| You type | What happens |
|---|---|
/layout |
All stages, no model call |
/layout place,route |
Only the stages you list (place, planes, vias, route, stitch) — no model call |
/layout fresh |
Takes the board's existing tracks up first, then runs the stages |
/layout reseed |
Places every part again instead of keeping the current placement |
/layout fix |
Runs the layout, reads every failure — unrouted connections and the circuit's own rules — changes what it calls for, and runs again, without a model call. /layout fix rules also allows net class changes within the fabricator's limits |
/layout apply |
Commits the proposed layout; /layout apply option <name> commits one compared option |
/layout discard |
Throws the proposal away; the board stays as it was |
/layout rules |
Prints the layout rules in force (net classes, widths, clearances) |
/layout check |
Checks the board as it stands; /layout check full lists every item |
/layout <what you want> |
Copilot plans the layout from your request — for example "keep the keypad together and route on two layers" |
With a free-text request, Copilot can lay the board out several ways and compare them (parts placed, connections routed, vias, copper, overlaps, parts off the board, decoupling distance, blockers), show the table, say which the numbers favour, and ask which to apply. When you ask for the board to be finished rather than for options, it can keep improving a layout round by round — each round listed with its reason — until everything is placed and routed or no change helps.
Copilot changes a net class (a narrower track or a smaller clearance) only if you allowed rule changes, never below the fabricator's minimum, and never below 0.10 mm track/space on 1- and 2-layer boards. It tells you which classes it changed and asks you to accept them.
Review an applied layout#
- Inspect every via, layer transition, clearance, and connection the router named as unrouted.
- Manually repair critical power, high-speed, RF, differential, and sensitive analog paths.
- Run DFM & DRC Check.
One board or a tower: /topology#
/topology asks whether the product should be one board or a stack of boards, and if a stack, which part goes on which board. The options are measured side by side from the design and any 3D files on the Board Fit tab; without a design, only the available room is measured. See Enclosure Fit and Multi-Board Products.
Manual override is expected#
Automatic placement and routing cannot decide product-specific mechanical, thermal, EMC, creepage, or signal-integrity requirements. Lock or manually position critical components and route critical nets deliberately.
Removed legacy content#
The previous page documented clustering algorithms, A* internals, route-order implementation, and experimental GNN training. Those details were removed because this site is a user guideline, not developer architecture documentation.