I recall seeing all kinds of hideously overdesigned hardware back in the 80's. Usually this was found in military projects where the contractor was billing outright for development time, but even in commercial work you used to see all manner of bizarre "exploits" used to avoid the dreaded "select in test" designation on a part simply because some particular parameter wasn't typically specified on the data sheet, and the mandate was "commercial spec only". It's almost comical going through these older designs trying to puzzle through which parameter they were trying to avoid having to specify!
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. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.