We've been aggregating data from smart devices in factories for 10 years. Ethernet is the dominate protocol, but only for non-time critical (non-deterministic) uses. The problem is always the protocol for information exchange (not talking about TCP/IP but at the app level), OPC tried to address it in a general way, XML gose a long way too, but none get rid of custom programming. Until there is a generally accepted way of communicating INFORMATION (not just the bits and bytes) this will be a hard thing to get a grip on. Not to mention most plant managers couldn't give a fig about the technology, SHIP PRODUCT!
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.