3 ms·
I should try that lib! (Same one mentioned in the article?) I should also give layout/routing a try. My thought was, schematic design, from the perspective of
by the__alchemist 9d ago
I should try that lib! (Same one mentioned in the article?)
I should also give layout/routing a try. My thought was, schematic design, from the perspective of what LLMs are good at, seems like the much more appropriate/easy tasks, so if it's failing at the basics there... I think I also experienced some consternation at patterns I've seen in real PCBs like a section dedicated to bypass caps that have no context of what pins they go to. (e.g. power connected to ground).
And I gave it a board that had a mixed of components/routing that I have used successfully one or many times, and parts that I am unsure about/don't know how to use and wire. Me seeing it make substantial changes to the known-working parts (My stake-in-the-ground), I got very nervous!
- tonyarkles 9d agoYeah it's the one mentioned in the article. I've tried FreeRouting or whatever it's called before and had... ok results... but it's a pain in the ass to set up. This KiCadRoutingTools code was super easy to set up in comparison. Edit: actually, one interesting thing to consider about routing vs. schematic design: my general experience with LLMs is that things work best when there's a feedback loop. On the schematic side, there isn't really much of a feedback loop; nothing will tell you that you've e.g. flipped the + and - terminals of your Opamp. On the layout side, you've got the ratsnest and DRC to tell you whether you're winning or not. That might be the key to making LLM-based routing work. Opus refused to hand-route my whole board yesterday but is currently using the KCRT tools to do the routing and things seem to be progressing well.