I have been using (or rather learning to use) KiCad on a processor board project. For most of the design work that I'm involved in KiCad appears to be a capable tool. The library and module (footprint) editors are a little clumsy to use, but once I got used to their quirks they are relatively easy to use. The schematic libraries are somewhat limited so I have been adding new parts as I needed them. I have completed a preliminary schematic and just started on the layout. KiCad is not as polished as some of the commercial software I have used before, but I think it shows a lot of promise as a useful PCB design and layout tool.
MKolb: "The library and module (footprint) editors are a little clumsy to use"
Good point. CERN's H&T group is working in improving this as it's included in some WorkPackages included in CERN's roadmap for KiCad.
MKolb: "The schematic libraries are somewhat limited so I have been adding new parts as I needed them"
Very good point!! I think I'm going to pass CERN guys a note about this issue. It would be fine to have a central repository with lots of parts collections and their associated footprints, spice model, 3D... I don't know if anybody at CERN or at KiCad core developers group has thought in doing this, but I agree with you: they should do that!!
Overall, thanks for your very valuable oppinion!! I'll give feedback to CERN's hardware guys about your experience using standard KiCad.
Javier Serrano from CERN has just told me that Dick Hollenbeck --KiCad main developer-- is giving the final touches to a Github plug-in for KiCad.
This will allow a KiCad user to enter a line in his component library table with a github URL, and automatically all KiCad symbols and footprints in any directory of that Github repository will be available for use.
By this way, the existence of personal online component libraries is going to be enabled in the coming KiCad versions.
@MKolb: Thank you very much for this resource!! I've given a quick look to some of the libraries in Kicadlib and these seem quite complete.
Now, I just wonder if there is some way of applying Quality Assurance techniques to free/open component libraries -- a little error on schematic/footprint could potentially lead to PCB respin and a lot of money losses.
I have experienced footprint problems before and they are a royal pain to clean up. Especially after we shipped several hundred units (military market where a hundred units is a lot). Getting management to approve a clean layout took a long time and at least one wrong turn.
I am not to the point where I completely trust any of KiCad footprint modules, so I check each one that I plan on using. I usually compare them to manufacturer recommended footprints, but not all of those agree on the same pad dimensions for the same land pattern.