ꝺꜫꞅh̵Ɪꝕꞟ is a user on mastodon.technology. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.
ꝺꜫꞅh̵Ɪꝕꞟ @deshipu

Why are all the PCB CAD programs so damn inflexible?

Whether it's Eagle, KiCad, EasyEDA or Altium, they are all like: NEIN, NEIN, YOU VILL MAKE ZE SCHEMATIC FIRST, AND ONLY AFTER IT IS DONE YOU CAN DESIGN YOUR PCB.

The problem is, the schematic is often trivial, and equally often I simply don't know it before I get to design the PCB — because I don't yet know which pins will be the easiest to route.

Fritzing lets me design the PCB right away, but it has its own set of problems, including bugs.

· Web · 2 · 2

@deshipu I'd like there to be a pcb design program that acts kinda like "Shenzhen IO": PCB-first, with components clearly labeled and designed, with good graphics and intelligent enough to do unit and integration tests.

@deshipu Maybe I'll actually get on that once I finish up my current load of projects (september-ish?)

@deshipu I understand what you're saying, but many times, when you just want to design the PCB, it's convenient to have the schematic. I have sometimes found where I have made PCBs by hand, then regretted not having the best documented schematic. In addition, the schematic generally allows simulations, which in some cases is very useful.
I think what needs to be improved is workflow optimisation.

@deshipu With regard to what is easier to trace, the experience is long overdue, but in any case, if necessary, it takes only two minutes, and work is being done on it.
To me it usually happens the opposite way, I want the schematic but not the PCB, since I am going to prototype it. And it's true that at the very least a component doesn't exist, it makes you very lazy.

@kwendenarmo Sure, I do recognize the need for the schematic. However, I usually make it later, after the PCB design, when I already know which gpio pins go to which components and so on. It's much more convenient that way.

@deshipu I didn't have that problem with KiCAD, though admittedly I had other problems and ended up writing a racket program that output a PCB file in s-expressions. But when I used it (several years ago) it was easy to bypass the schematic.

@technomancy But then you will never have the schematic. There is no way to go back.

@deshipu I see; I guess you're talking about a different problem than it looked like at first. KiCAD certainly encourages you to do the schematic first, and that's something I'm completely uninterested in. But sure, there are cases where you'd want it later.