Design tool

Schematic capture

Multi-sheet schematics with live connectivity and an Electrical Rules Check.

WireFrame EDA schematic editor showing a sheet of the h730duino STM32H730 board

Place symbols from your libraries, wire them, name nets and split a design across as many sheets as it needs. Connectivity is built as you draw, and the Electrical Rules Check finds floating inputs, broken nets and duplicate designators before the board exists.

What it does

Wires, labels and power symbols

Wire (W), Net Label (N), power port (P) and GND (G) tools, junctions, and net labels that connect across sheets.

Multi-sheet projects

One project holds many .schxml sheets and the board; the project tree keeps them together.

Electrical Rules Check

Undriven inputs, unconnected pins, output-to-output conflicts, dangling labels and wires, duplicate designators — click a result to go to it.

Annotations and PDF

Lines, boxes, text and a title block; export the schematic as a printable PDF.

Connectivity is built as you draw, not compiled afterwards

Most of what goes wrong on a schematic is connectivity: a wire that looks like it touches a pin and does not, two nets with the same name on different sheets, a bus that lost one member. WireFrame builds the net graph while you draw rather than deriving it when you ask for a netlist, so a wire that is one grid unit short is a separate net immediately and visibly, instead of at export time when you have moved on. Hover any wire and the whole net lights up across every sheet it reaches.

Multi-sheet projects are hierarchical, not just numbered

A sheet can contain a sheet. Power, the MCU, the connectors and each sensor can live in their own file, with named ports on the sheet symbol joined to hierarchical labels inside it. Designators are checked across the whole hierarchy, so a sheet-local R1 colliding with another sheet's R1 is an ERC error rather than a surprise on the BOM.

The ERC is a list of things to fix, not a wall of warnings

An Electrical Rules Check that reports six hundred items teaches people to ignore it. WireFrame's ERC follows KiCad's rule set — inputs nothing drives, outputs driving outputs, pins left unconnected without a no-connect flag, power pins with no source, dangling labels and wires, duplicate designators, labels that reach only one pin — and each result takes you to the item on its sheet. A result you have judged and accepted can be excluded, with your reason kept beside it, so the list stays short enough to read every time.

What a schematic becomes

The sheet is not the deliverable. From here the same connectivity feeds the PCB (where the ratsnest is this net graph), the BOM, the netlist exported for another tool, the PDF for review, and a SPICE simulation of a block you select and the Copilot's own understanding of the design. One graph, several outputs, no re-entry.

The details

Sheet formatsA4, A3, A2 or a custom size, with a title block
HierarchyHierarchical sheets joined by sheet pins and hierarchical labels; KiCad hierarchies import intact
Symbol librariesKiCad (.kicad_sym, .lib), Altium (.SchLib, .IntLib) and WireFrame's own verified library
BusesBus members such as D[0..15] in imported designs are expanded and checked by the ERC; there is no bus drawing tool yet
ERC rulesKiCad's rule set: undriven inputs and power pins, pin-to-pin conflicts, unconnected pins, dangling labels and wires, duplicate or missing designators, sheet pins that do not match — any result can be excluded with a stored reason
ExportSchematic PDF, every sheet in one file; BOM and IPC-D-356A netlist with the fabrication outputs; KiCad, Altium Designer and EasyEDA projects
ShortcutsW wire · N net label · P power port · G ground · Space rotate · Ctrl+E properties

How to start

  1. Create a project with File › New, or open one from the project tree.
  2. Pick symbols in the Library panel and double-click to place them.
  3. Wire with W, label nets with N, then run the ERC before converting to PCB.

Questions

Can I open a KiCad schematic directly?

Yes. File › Import › KiCad Project opens the whole project, schematic and board together, with the hierarchy intact. All 15 of KiCad's own demo projects import with a netlist identical, net for net, to the one kicad-cli exports from the same files.

Do I have to annotate designators by hand?

No. The ERC flags designators that are missing or used twice, and its Annotate fix numbers them for you.

What happens to the board when I change the schematic?

Tools › Update Schematic to PCB carries the difference across: parts added, removed or re-valued, nets joined or split. Your placement and routing are kept; only what actually changed is touched.