All posts

Bring your own board, Altium included

Drop an Altium .PcbDoc or a KiCad project into Koppar: route it and order it as it is, change it while keeping its copper, or start a new board from it. Attach a datasheet for a part we do not carry. Plus four free tools that open Altium files without a licence.

A Koppar board in 3D beside the words: bring your own board; route it, change it, order it. Under it, board.PcbDoc becomes board.kicad_pcb.

Koppar started as a sentence-to-board tool: describe a circuit, get a routed, checked board. Most boards are not started from nothing, though. They start from last year’s revision, a reference design, a board a contractor sent over in Altium, or a part only a datasheet describes. Over the past weeks Koppar learned to start from those files. This post is what it does with each, and what it does not do yet.

Altium boards come in with their rules

Drop a .PcbDoc, or a ZIP of the whole Altium project, into a Koppar project. The board is converted to KiCad by KiCad’s own Altium importer, and then Koppar does the part that importer leaves out: it reads the board’s design rules from the file and writes them into the KiCad project.

That part matters more than it sounds. Without its rules, a converted board is judged against KiCad’s defaults: 0.2 mm tracks, 0.3 mm drills, default clearances. On a public 8-layer i.MX 8M Mini system-on-module, KiCad’s import alone reported 1,992 design-rule violations, and every clearance, track width, via and drill one among them was false. With the rules carried across, none of those false ones remain.

What comes across:

  • clearance, track width, via size and drill, per net class, per differential-pair class and per single net, with Altium’s rule priority deciding which rule a net gets;
  • differential-pair width and gap;
  • the board minimums: clearance, track, via, drill, hole to hole, copper to board edge;
  • the layer stack, under the names the designer gave it (L2_GND, L5_PWR).

What does not, and is listed for you after the import: rules scoped to a room, a layer or a custom query; per-layer widths; length, matching and timing rules. Set those again if the board needs them.

The schematic is not converted. The board holds every part and every net, so it can be checked, changed and routed without one. Add the .SchDoc sheets too (or the whole Altium project as a ZIP): Koppar reads each part’s manufacturer and part number from them, and the bill of materials looks parts up by that number.

Work on the board as it is

Ask for something about the board itself, “route it”, “fix the design-rule errors”, “get it ready to order”, and it opens as it is, with no generation used. The project chat works on your copper directly: route all or some nets while keeping what is already connected, run the design-rule check, change the rules, place and pour, and step back through every revision. A route shows up as a live run. Once the board passes the design-rule check with nothing left unconnected, its Order tab gives you Gerbers, the assembly files and a price, as for a board Koppar designed. Its parts are priced against live seller stock only when you ask.

The same board workspace opens from the KiCad plugin, from your own agent over MCP, or from the command line.

Change a design you already have

Attach a KiCad project, or an Altium board, and say what should change: add a connector, swap a regulator, rename a net, move a signal to another pin. Koppar reads the design, makes the change, and handles the board the way you would by hand:

  • the copper that is still right stays where it is;
  • only what the change broke is torn up;
  • new parts are placed in free room, and the board grows on one side only if there is none;
  • only the new and changed connections are routed, around the copper you kept.

The result tells you how many of the board’s tracks and vias were kept and how many were added. The checks judge what the edit changed, so the design-rule findings that were already on your board stay yours and do not hold the new one. On six boards of up to 264 parts, five came back released; the sixth was held with one connection open.

Some things an edit does not do yet: reshape the outline or cut a slot, or add a part that exists only in a datasheet. Those go in a new design.

Or use it as a starting point

If the files are background rather than the board to change (a reference design, a previous product, a board you are replacing), say so. Koppar reads them as references and designs a new board, with what it found in them in the brief.

Parts we do not carry: attach the datasheet

When a part is not in the catalogue, attach its datasheet as a PDF. Koppar reads its pin table, and its pinout drawing where it needs to, and draws the part’s symbol from them. A pinout read from the document is marked as such; one that could not be is marked for you to check. The footprint comes from KiCad’s libraries, or from your own .kicad_mod if the package is unusual: attach it too.

The chat also takes images (a photo or drawing of an enclosure can set the board outline and holes), STEP models, ZIPs and links to public GitHub repositories.

Four free tools for Altium files

Not everyone with a .PcbDoc has an Altium licence: the hardware engineer who inherited a board, the manufacturer who was sent one, the KiCad user handed a design by a colleague. These four run in the browser, with no sign-up, at tools.koppar.ai:

  • Altium to KiCad: the .PcbDoc as a .kicad_pcb and a .kicad_pro with the rules above, and the list of the rules that did not come across.
  • Altium PCB viewer: the board and each copper layer as SVGs, with its size, layer stack, parts and nets.
  • Altium to Gerber: Gerber and Excellon drill files, with the copper pours as Altium filled them. Check them in the Gerber viewer before you order; solder-mask and paste expansions set by Altium rules can differ.
  • Altium BOM: drop the .SchDoc sheets and get bom.csv, parts grouped with their comment, footprint, manufacturer and part number.

Each is also an API endpoint, documented at docs.koppar.ai/tools.

Not yet

  • Eagle, EasyEDA and OrCAD files are not imported. KiCad and Altium are.
  • Altium schematics are read for their parts list, not drawn.
  • A footprint is not drawn from a datasheet’s package drawing: it comes from KiCad’s libraries or your own .kicad_mod.

If a file of yours does not come in the way you expected, send it our way from the feedback button in the studio.

Describe the circuit. Get the board.

See what Koppar does