dchisholm:
A proper financial evaluation of KiCAD needs to ask, “How much time, effort, and resources are required to create, document, and maintain the libraries?”.
So much this. Anything else is hot air.
Also, even more important questions - what features does your workflow need which the ECAD software should contain.
Someone started a thread on those issues over a year ago:
I just wanted to share some info on why KiCAD was rejected as a potential tool at the large enterprise where I work, in hopes that this might be of interest to developers.
Database integration: Enterprise class schematic and layout needs to be able to take attributes and parts lists from a database connector.
Schematic parts need to be able to be bound (with a set of attributes) to a part number. Assigning footprints to parts when you go to layout allows human error during every design, r…
1 Like