[{"data":1,"prerenderedAt":22},["ShallowReactive",2],{"article-ai-pcb-design-in-altium-and-kicad":3},{"slug":4,"date":5,"read_time":6,"image":7,"cta":8,"zh":10,"en":16},"ai-pcb-design-in-altium-and-kicad","2026-09-16",6,"/og.png?v=8",{"link":9},"https://ai-3.trio-prc.com/",{"title":11,"tag":12,"excerpt":13,"keywords":14,"content":15},"AI 在 Altium 和 KiCad 里画 PCB，到底是怎么动手的","AI 设计 PCB","让 AI 画 PCB 有两条路：一条是模拟你点鼠标，一条是通过接口驱动 EDA。前者演示很顺、换台电脑就废；后者麻烦一点，但能一直用下去。","AI设计PCB,Altium AI,KiCad AI,自动布线,DRC,原理图生成","\u003Ch2>两条技术路线，差别在换一台电脑之后\u003C/h2>\u003Cp>把 AI 接到 EDA 软件上，最快的做法是让程序去操作界面：找到窗口、点菜单、发按键。演示视频里它看起来完全可行。问题出现在第二台电脑上——Altium 换个版本菜单文字变了、屏幕分辨率不同控件坐标偏了、用户手里恰好开着一个模态对话框，流程就断在半路。更糟的情况是它点错地方：把主窗口关掉，或者让脚本引擎弹出层叠的模态框卡死，只能手动重启软件。\u003C/p>\u003Cp>另一条路是让 EDA 自己提供接口：AI 发出的每个动作都是一次调用，由运行在你机器上的连接器交给 EDA 执行。这条路前期要把每个动作一个一个实现出来，但它可测试、可重放、行为确定，出了问题能复现也能回退。ONEPASSPCB 走的是这一条，而且把\"不做任何系统层面的模拟点击\"写成了硬规则。\u003C/p>\u003Ch2>AI 实际能做完的部分\u003C/h2>\u003Cp>从需求到可评审的工程，AI 能接手的大致是这些：按功能建元件与符号、连网络、标位号与参数、摆器件与设板框、跑自动布线、执行设计规则检查并逐条解释违规。这些动作都直接落在你打开着的那个工程文件里，你随时可以停下来接手手工调整——不需要在\"AI 的版本\"和\"我的版本\"之间做合并。\u003C/p>\u003Ch2>自动布线那一步最容易\"跑了但没结果\"\u003C/h2>\u003Cp>自动布线器通常分两段：先走线，再优化。实际用下来，崩溃多半发生在优化阶段，而这时输出文件可能已经建立、只是内容是空的。如果判断标准写成\"文件存在就算成功\"，失败就会被推迟到导回 EDA 那一步才暴露，用户看到的是一句读不懂的报错。\u003C/p>\u003Cp>正确的判据是看文件里有没有真正的布线结果；发现是空的就说清楚下一步：要么关掉优化再跑一次，要么先跑 DRC 把封装占位区的重叠清理掉——重叠焊盘正是优化阶段崩溃最常见的诱因。\u003C/p>\u003Ch2>怎么开始\u003C/h2>\u003Cp>注册账号、下载对应你 EDA 的连接器（Altium Designer 或 KiCad 各一套，互相独立）、双击启动、在网页上拿配对码配上，然后打开工程开始提需求。工程文件始终在你自己的机器上。\u003C/p>\u003Cp>备料那半边的工作流见另一篇：\u003Ca href=\"/blog/why-bom-prices-differ-across-distributors\">同一颗料，为什么各家报的价差这么多\u003C/a>。\u003C/p>",{"title":17,"tag":18,"excerpt":19,"keywords":20,"content":21},"How an AI actually draws a PCB inside Altium and KiCad","AI PCB Design","There are two ways to connect an AI to an EDA tool: simulate your mouse, or drive the tool through an API. The first demos beautifully and dies on the second machine.","AI PCB design,Altium AI,KiCad AI,autorouting,DRC,schematic generation","\u003Ch2>Two approaches, and the difference shows on the second machine\u003C/h2>\u003Cp>The fastest way to wire an AI into an EDA tool is to drive the interface: find the window, click the menu, send the keystrokes. In a demo video it looks perfectly workable. It falls apart on the next machine — a new Altium version renamed the menu, a different screen resolution moved the control, or the user happens to have a modal dialog open. Worse, it can click the wrong thing: close the main window, or leave the scripting engine stuck behind stacked modal dialogs until someone restarts the tool by hand.\u003C/p>\u003Cp>The other approach is to let the EDA tool expose an interface: every AI action is a call, executed by a connector running on your machine. It costs more up front, because each action has to be implemented, but it is testable, replayable and deterministic. ONEPASSPCB took that route and made never simulating input at the OS level a hard rule.\u003C/p>\u003Ch2>What the AI can finish on its own\u003C/h2>\u003Cp>From a requirement to a reviewable project, the AI can create parts and symbols, wire nets, assign designators and values, place components, define the board outline, run the autorouter, and run design rule checks while explaining each violation. All of it lands in the project file you have open, so you can stop and take over by hand at any point — there is no merging between the AI version and your version.\u003C/p>\u003Ch2>Autorouting is where a run finishes with nothing to show\u003C/h2>\u003Cp>Autorouters usually work in two stages: route, then optimize. In practice the crash tends to happen during optimization, by which time the output file may exist but contain nothing. If success is judged by does the file exist, the failure is deferred until the import step and surfaces as an error message nobody can read.\u003C/p>\u003Cp>The right check is whether the file contains an actual routing result. If it does not, say what to do next: disable the optimizer and run again, or run DRC first to clear overlapping courtyards — overlapping pads are the most common trigger for an optimizer crash.\u003C/p>\u003Ch2>Getting started\u003C/h2>\u003Cp>Create an account, download the connector for your tool (Altium Designer and KiCad have separate, independent ones), double-click to start it, pair it with the code shown in the browser, then open your project and start describing what you need. Your project files never leave your machine.\u003C/p>\u003Cp>For the sourcing half of the job, see \u003Ca href=\"/en/blog/why-bom-prices-differ-across-distributors\">why the same part gets such different prices from different distributors\u003C/a>.\u003C/p>",1789615679540]