@measurementBlues: No doubt about that. With the sensor technology chugging out information as visible data in smartphone, this has come way beyond the concepts of spreadsheets and time complexities involved in delivering such spreadsheets to the governing party for their advice. Since Fluke allows multiple tagging of smart phones, this can be very useful when getting advice from two people in two different parts of the world.
The Fluke Connect is actually implementing the Industrial Internet model. GE recently brought its major factories and assembly lines under sensor and cloud data. If you have sensors and a cloud connection, then getting the data from any plant to your smartphone won't be too tough, and for that an app won't be required.
Seems like the big value will be in capturing many data sources. Hopefully Fluke is working on making small sensors that can be used in large numbers. I want Fluke quality, but for big data measurements...
The problem is the phone screen is so small. Tablets were needed where you actually need to see some detail. Today's oscilloscopes have large screens so you can see waveform details. Or, it could be that large screens are needed because so many engineers are too old to see small screens.
Just look at the scopes in the ads on these pages. If you don;t see a scope, refresh your browser. The ads rotate. I'm looking at one right now.
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.