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.
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.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.