Back in the days when there was such a thing as "repair", a friend of mine worked for a TV repair shop. He would often get calls from someone whose TV would not turn on. He knew if he asked the potential custormer "Are you sure the TV is plugged in?" the caller would say "Do you think I'm an idiot? Of course it's plugged in!" and he didn't want to have to make a service call and discover that the TV was in fact not plugged in and then have to charge for a service call -- not good customer relations.
So he'd tell the caller: "Some TVs don't work if the plug is in the socket upside-down. Try unplugging the set and see if it works if you plug it in the other way." The caller would go to do this and discover that the TV wasn't plugged in at all. The caller would come back and say "Yep, that was the problem! Thanks!"
Allowing customers to save face is a good way to build a customer base for when there are real problems.
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.