When bridging the gap between a device without IP connectivity and the Cloud, you should know where and how to implement a network communication protocol. This is where WolkGatewayModule-SDK steps in.
In the previous post, we introduced the concept of gateways and gateway modules that bridge the communication for devices without IP connectivity and WolkAbout IoT Platform. In this article, we are going to focus on gateway modules.
Modules enable device communication via their network communication protocol and define how data is obtained from devices, as well as how it is processed before being sent to the gateway.
The user is responsible for providing the custom implementation that usually contains the device’s network communication protocol, as well as for providing the business logic and everything related to the used hardware and the specifics of their particular use case.
However, all the communication that is directed towards the gateway through WolkConnect - BUS Handler is already provided with WolkGatewayModule-SDK-Cpp and WolkGatewayModule-SDK-Python open source implementations written in C++ and Python that use the MQTT protocol over TCP/IP. To get more insight, see the documentation for Python SDK.
WolkGatewayModule-SDK-Cpp provides examples that outline how and where the device communication protocol should be implemented.
To see the module examples made from WolkGatewayModule-SDK-Cpp that have an implementation of a network communication protocol ready to be used in an IoT project, see GitHub repositories for Bluetooth and Modbus modules. These modules were used to build some IoT project examples like presence reporting and remote motor control.
If you need more information on this topic, feel free to contact us.