When we talk about IoT, the first tasks that come along are sensing and data fetching. You can read about all the involved steps for IoT implementation in our previous blog (http://www.ushva.com/blog/2018/08/22/enabling-energy-with-iot/). Data sensing has been there for quite some time as that is also used for on-site monitoring and alarming as well as automation. There are standard sensor fittings & solutions available when we talk about the sensing task. But when it comes to data fetching and transmitting, a lot must be thought upon as there are no standard solutions/products available in the market.
The market is flooded with highly affordable Chinese devices which seem attractive in the first go. Then there are expensive devices by DELL, Microsoft and software-based solutions which require the installation of a computer (PC) on-site.
Two broad types: a) Embedded Device b) Driver based data fetching on a PC
Choosing from the vast list of devices, it is immensely important for the implementer to choose the right set of devices/solutions for an optimal implementation.
Following factors must be considered while finalizing a fix for data fetching and transmitting:
· Type of data logging on-site (sensors, PLCs, utility meters, actuators, etc.)
· On-device connector requirement based on local data logging
· Type of data to be fetched (binary, integer, float, etc.)
· Local machine to device communication protocol (MODBUS, ETHERNET IP, PROFIBUS, etc.)
· Amount of data points (tags) to be fetched at a given instant
· Edge processing (on-site processing) requirement
· Local data storage
· Device to Server communication (Wi-Fi, GSM, LoRaWAN, etc.)
· On-site environment and space constraints
Keeping in mind all the above factors, the data fetching method must be finalized along with the considerations for the future implications. Startups are comings up with new edge devices which might suit some very specific requirements as well as be affordable for the buyers/implementers. As a word of caution, one should always focus on the overall picture rather than just the initial cost.
P.S.: In the next blog, we will share information about the specific data fetching options for the users to be fairly aware. Stay tuned!