Automated PCB Manufacturing Needs Automated Design
Automated PCB assembly has reached low-volume, high-mix work. A robotic line can now build one unit each of 100 different designs with no changeovers. The factory is no longer the slow step. The handoff from the design tool to the factory is.
This post looks at where that handoff loses time and data, and what a design workflow needs to feed an automated line.
What changed on the factory floor
This week a Massachusetts electronics manufacturer showed the factory it has run for five years: one factory-scale robot that builds circuit boards on demand. The post went to the top of Hacker News.
The architecture is different from a conventional SMT line:
- There is no fixed conveyor. Levitating movers carry each board and its parts between stations.
- The stations print solder paste, place parts, reflow, and inspect.
- Software schedules every board on its own route through the cell.
- There are no changeovers and no setup per design.
On a conventional line, setup time sets the economics. Feeders, stencils, and programs change for each job, so small batches cost almost as much to set up as large ones. Remove the setup and a 10-unit job of a new revision runs like any other job. That is the high-mix, low-volume work that resisted automation for decades.
Where the handoff breaks
The comments on the post show where the friction is. It is not in the factory. It is in the files.
“I uploaded a zip of my gerbers and it came up with some error that I could not figure out and halted any further movement.”
Another engineer uploaded an old Gerber export from a desktop EDA tool and got the same result. The manufacturer explained why: its automation wants the original design files, because Gerbers alone do not carry all the design and assembly data that the line needs.
That is a data problem, and it is easy to see why. A typical fabrication and assembly package has:
- Gerber files for copper, solder mask, silkscreen, and outline, plus an Excellon drill file.
- A BOM with manufacturer part numbers.
- A pick-and-place (centroid) file with reference designators, positions, rotations, and sides.
- A fabrication drawing with the stackup, material, finish, and impedance notes.
Each of these files is a separate export of one design. Nothing links them to each other. A Gerber has no part data, no net names, and no design intent. When the BOM and the centroid file disagree, or a rotation convention is different, a person has to find the problem. Formats such as IPC-2581 and ODB++ put more of this data in one file, but the export step and the manual check are still there.
Other engineers in the thread described the same problem from other directions:
- One asked the factory to publish its design rules as a template for desktop EDA tools, to avoid “getting to a finished pcb then discovering that you have a rule about no route through pads.”
- Another wrote that “designs take weeks to get manufacturing feedback on.”
- Another said the BOM step for 50+ line items and 500+ placements is “a heavy human lift.”
The usual sequence is: design in one tool, export, zip, upload, wait for an error or a DFM email, go back to the tool, fix, and export again. Each pass through that sequence costs days.
Design and manufacturing data in one project
The fix is to remove the handoff, not to make it faster. Design data, the fabricator's rules, and the quote must stay in the same project, so that a change to one updates the others.
That means three things in practice:
- The design tool knows the fabricator's rules while you design, not after you upload.
- The manufacturing outputs come from the same design data and are checked against each other.
- The quote follows the design. When the board changes, the quote changes.
It also must cover the whole device, not only the board. A device is a board, an enclosure, mechanical parts, cables, and firmware. A board that is assembled in four days does not help much if the machined housing still waits on a STEP file that nobody exported.
How Flux does it
Flux is an AI hardware engineer. It designs the electronics and the mechanical parts of a complete device in one project, in the browser. The manufacturing work happens in that same project.
- Design rules come from the fabricator. The Flux agent checks the design against each fabricator's rules while it works.
- Outputs are checked against each other. The agent runs DRC on the exported board, checks the Gerbers against the board outline and silkscreen, and cross-checks the BOM against the pick-and-place data.
- Quotes cover the whole device. Flux gets quotes directly from fabricators for circuit boards and assembly, 3D printing in plastic and metal, CNC machining, sheet metal, injection molding, and wire harnesses. The agent compares price and lead time.
- Quotes stay current. Move a connector 5 mm, and the agent checks the change and updates the quote. It places the order when you confirm.
A typical request for a motor controller and its housing:
“Check the motor controller and its aluminum housing against my fabricators' rules. Then get quotes for 50 assembled boards and 50 CNC-machined housings, and show me the fastest option.”
Without Flux, that request is a week of exports, uploads, and DFM emails between two vendors. In Flux, it is one message in the project where the device lives.
The last manual step
The manufacturer in the thread said AI-designed boards are already arriving at its factory. As AI agents design more hardware, the number of designs per week goes up, and every one has to arrive ready to build. A handoff that needs a person to fix the files does not scale with that volume.
The test for an AI hardware agent is whether its boards work when they are built. We cover how to measure that in AI-generated hardware designs that work and how to evaluate AI PCB design. Desktop tools with an agent added on top still end in the same export and the same zip; see our post on MCP and computer use.
The factory is automated. The design side is now automated too, in the same project.
Design your next device with Flux and send it straight to manufacturing.
Frequently asked questions about automated PCB manufacturing
Automated PCB manufacturing uses robots and scheduling software to print solder paste, place parts, reflow, and inspect circuit boards with little manual setup. The newest factories route each board on its own path, so they can build many different low-volume designs on demand without changeovers.
Gerber files describe the copper, mask, and silkscreen layers. They do not carry all the design and assembly data, such as parts, placements, and design intent, that an automated line needs to quote and build a board without manual work. Native design data lets the factory automate more of the job.
The Flux agent checks the design against each fabricator's rules, verifies the manufacturing files, and cross-checks the BOM against the pick-and-place data. It then gets quotes directly from fabricators for the boards, assembly, and mechanical parts, keeps the quotes current as the design changes, and places the order when you confirm.
Related Content
Your AI Agent Can Outgrow Its Editor: Hardware Design Workflows Beyond EDA and CAD Features
AI Is Coming for Your CAD Skills. Let It.
Cloud AI Agents: Your Project, Not Your Whole Laptop
How to Choose Decoupling Capacitors with PDN Simulation, Not Rules of Thumb
Gerber File Check: The Flux Agent Checks Your Files Before Fabrication
Stack Overflow for Hardware Engineering: Ask AI Inside Your Design
Let’s start building.
Let’s build your idea together. All you need to do is describe what you want to make, or what problem you want to solve. Flux will work with you to make it a reality.
