Closed jmwright closed 7 months ago
Its definitely a YMMV scenario. If you set up your design with the goal of substituting footprints, you can ensure a better result by carefully choosing components and using signal/pin name references as much as possible when defining signal nets and corresponding routing. Lastly, I would strongly suggest using SKiDL for defining both the components and netlist of the circuit. SKiDL connects natively with KiCAD for the component libraries and will allow you to easily change footprint references for any part. The resulting SKiDL circuit can then provide pcbflow with a sound data source for part footprint geometries and circuit netlist.
Lastly, to be honest, I pretty much use KiCAD for almost all my circuit/PCB design projects. I have used pcbflow for small PCBs, but for more complex circuits where robust design rule checking and nuanced design geometry is required, KiCAD is the better tool.
Thanks @michaelgale
@michaelgale I noticed your name on this and thought I would take a look at this since you are also a member of the CadQuery community. It seems like this Python-based workflow could be a nice complement to mechanical design in CadQuery. I do have a couple of questions which I do not think were answered in the readme.