It is interesting to reflect upon the evolution of instruments. With SmartPhones, "instruments" may become peripherals and sensors with the SmartPhone serving as the control panel, display, and (perhaps) processor. This poses an interesting marketing problem for the instrument vendors. Historically it was the control panel, display, and packaging that impressed the buyer and drove sales. The rest of the instrument was pretty much out of sight and out of mind. Now any processing done by the "instrument" may be hidden in a small electronics module which is little more than a thickened section of the sensor wire and the purchased instrument may be a SmartPhone accessory.
@MFOSS582, I did get a live demo of hte Mooshimeter. Also an interesting concept in that it's wireless, but the Fluke system goes far beyond, with it's ability to connect to a second phone and display data. OTOH, Fluke is a large company with far more resources.
I haven't taken an in-depth look, but Opto 22's Groov look pretty sweet for remote equipment access - it's a somewhat similar concept to Fluke, but for mobile access to industrial equipment. The groov system has a box (~$2K or so IIRC) in the middle between remote access and the equipment.
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.