4 ms·
The blog post isn’t clear: Did the LLM actually do the routing? The only screenshot showing connected traces comes after the author says they added ground fills
by Aurornis 1y ago
The blog post isn’t clear: Did the LLM actually do the routing? The only screenshot showing connected traces comes after the author says they added ground fills and “tidied up the layout”
It’s amazing that this worked at all, but to be clear this layout is actually very bad. Just look at that minimum width trace used to carry power across the entire board and into the ESP32. Using min width traces and wrapping them and min clearance to components is a classic mistake of people (or LLMs?) that have zero understanding of PCB layout techniques beyond “draw lines until everything is connected”
It would be interesting to see if you could feed the file into an LLM and get it to produce the feedback.
- Animats 1y ago> Did the LLM actually do the routing? Good question. KiCAD once had a router, built in, or sort of built in, but it was taken out for licensing reasons. So who's doing that?
- dilawar 1y agofreerouting plugin is available as a standalone program. It's pretty good. You export DSN from kicad and use freerouting. Not as simple as button click though.
- stavros 1y agoWhy would anyone want a router? Routing is by far the most fun and relaxing part of PCB design! I'd pay for a game that just had me route PCBs.
- tripletao 1y agoThe video seems more clear. The LLM generated the BOM and netlist using atopile, a tool for specifying the equivalent of a schematic in code. He did the placement and routing in KiCad in the usual way, presumably by hand. ETA: Other commenters suspect a traditional autorouter based on the poor layout quality. I agree that's also possible, and nothing in the video excludes that. It definitely wasn't the LLM, though.
- Aurornis 1y agoThat makes more sense. Going from a highly detailed set of common parts and instructions to an incomplete net list seems within the realm of LLM tasks. I assumed the author was more experienced, I suppose this is more of an entry level hobbyist blog. There are some very fundamental problems with routing PCBs like this that are covered in introductory materials.
- owenversteeg 1y agoI could be wrong, but that looks like autoroute to me just based on the aesthetics of it, autoroute has a bit of a "smell" that you can recognize if you pay attention. For example see the via and traces to the left of SW2. No human I know, even a total noob designing their first ever PCB, would do that. Also, it certainly wasn't the LLM; atopile doesn't allow you to specify routing as far as I'm aware, their docs seem to tell you to route in KiCad.
- owenversteeg 1y agoFew other thoughts: - impressive that this worked so well with LLM-generated atopile, given that atopile is about a year old! - the hardest part of a PCB is still the routing and nonstandard parts of the design; what this did is basically "find a reference design, pick components that match the reference design, and put them on the correct nets" which is the easiest part of the process for people designing PCBs today - much like with code, 99% of PCBs designed are fairly basic boards implementing the reference design with some small tweaks, and then there is a tiny amount of envelope-pushing designs/crazy complex stuff. Obviously you can't design some fancy PCB with complex RF with this, but give it some time and I'd bet you can probably make a lot of the basic stuff...
- grues-dinner 1y ago> 99% of PCBs designed are fairly basic boards implementing the reference design with some small tweaks This may be true of hobbyists, but is very much not true in industry. Maybe all those millions of IoT devices skew the number of PCBs made that look a bit like an ESP32 plus a button and an LED, but most unique designs probably aren't those. Endless march of things like new super-dense PC/mobile motherboards and all the weird hyper-specific industrial electronics takes far more effort, say. And no one is sweating the few days to design and lay them out to meet the constraints for a simple ESP32 + a button. Primarily the size and shape and power usage. That's not the hard bit of slinging mass-market IoT trinkets, the software side is.
- torginus 1y ago
- ai-christianson 1y ago> It’s amazing that this worked at all, but to be clear this layout is actually very bad. Just look at that minimum width trace used to carry power across the entire board and into the ESP32. Using min width traces and wrapping them and min clearance to components is a classic mistake of people (or LLMs?) that have zero understanding of PCB layout techniques beyond “draw lines until everything is connected” Is it really so implausible that these constraints could be built into the process/algorithm/agentic workflow?
- z3c0 1y agoNo, but at that point, why even leverage a stochastic text generator? Placing hard constraints on a generative algorithm is just regular programming with more steps and greater instability. Edit: Also, one could just look to the world of decision tree and route-finding algorithms that could probably do this task better than a language model.
- ai-christianson 1y agoIDK, modeling, constraints, simulations and stochastic processes seem like a match made in heaven. It's like how pairing a coding agent that can run unit tests and iterate is way more powerful than code gen alone.
- Szpadel 1y ago> It would be interesting to see if you could feed the file into an LLM and get it to produce the feedback. I did something like that already and It works ok. I'm just electonic amateur and it happened to me to incorrectly wire up MOSFET or using ptype incorrectly. I basically send screenshot of schematic and ask for feedback or suggestions. it actually provide nice feedback and for someone not very experienced it's very reassuring to get green light from LLM.