4 ms·
KiCAD becomes better and better, but one limitation embedded into its DNA is very annoying: one project - one schematic - one PCB. It is very kludgy and cumber
by blacklion 11mo ago
KiCAD becomes better and better, but one limitation embedded into its DNA is very annoying: one project - one schematic - one PCB.
It is very kludgy and cumbersome to split project into several PCB (for example, stack of PCBs connected by backplane or headers, like Arduino & Shield for it) and/or to have variations of the PCBs for one schematics, like TH and SMD variants of the PCB for exactly same schematics.
Even in my very modest almost-electrical (as opposed to electronic) projects I need one or another from time to time.
As far as I understand it is limitation which is not easy to fix, because all architecture of KiCAD is based on this 1-1-1 principle.
- abrugsch 11mo agoMy workaround for multiple PCB's for one schematic is to have the schematic as a top level sheet which can then be imported into sub-level projects. so each PCB becomes it's own project but use the common schematic sheet