Those looking to leverage Azure IoT Hub for MQTT integration to ThingWorx would likely also find this recorded session and shared utilities quite helpful. See Multiple clients subscribe to MQTT broker on Monnit Gateway for setup details. Users can then integrate this data with data collected from traditional industrial automation assetssuch as PLCs, sensors, and databasesto create a single source of consolidated plant floor data. It securely accesses otherwise siloed data and transmits it to KEPServerEX.
KEPWARE MQTT DRIVER
Monnit Gateway is set up and multiple Kepware Servers are configured. The MQTT Client driver is a user-friendly out-of-the-box MQTT to OPC UA translator. This approach can be quite good for a simple demo if you have a Kepware Integrator or Kepware Enterprise license, but the use of IoT Gateway for many servers and tags can be quite costly. The objective of the test is to subscribe multiple Kepware Servers to MQTT broker on Monnit Gateway and then pull data from this configuration. ThingWorx entities for import (ThingWorx 9.0) Enjoy!Įnd to end Integration of Kepware to ThingWorx using MQTT over Azure IoT (YoutTube 45 minute deep-dive) Today, I took the time to build, test, validate, and share an approach and utilities to do this in cases where the Azure Industrial IoT OPC UA integration is overkill or simply a step later in the project plan. Recently the topic has come up again as more and more of the ThingWorx expert community start to work with Azure IoT. People ask me many things about Azure (in a ThingWorx context), and one of the common ones has been about MQTT communications from Kepware to ThingWorx using IoT Hub. I was always grateful when someone took the time to help me understand, and now it is time to repay the favour. If all goes well, your data should appear as you desire.I've had a lot of questions over the years working with Azure IoT, Kepware, and ThingWorx that I really struggled getting answers to.Add in your tags by right clicking and following the window.For Example, this is how I want to model my data to look like:
KEPWARE MQTT SOFTWARE
Its design allows users to connect, manage, monitor, and control diverse automation devices and software applications from plant control systems to enterprise information systems. In advanced template, Kepware allows your to dictate how your payload format should look. ThingWorx Kepware Server is a single solution collecting, aggregating, and providing secure access to industrial operations data.
![kepware mqtt kepware mqtt](https://content.instructables.com/ORIG/FJD/31ZD/JU8N8JKZ/FJD31ZDJU8N8JKZ.png)
![kepware mqtt kepware mqtt](http://www.talosengineering.com/wp-content/uploads/2018/05/Azure-IOT-Hub.png)
![kepware mqtt kepware mqtt](https://miro.medium.com/max/2000/1*LHKiPcZXldMgM5IDt0ZQnQ.png)
Begin by right clicking on the IoT Gatway > Add REST client. A driver for devices that support the MQTT protocol.However, for those who prefer greater modelling of the data, this is it. This may or may not be useful in doing your data modelling since most of the data can be usually managed within Splunk. By correctly formatting your data, using the IoT Gateway allows greater flexibility of how you want the data to appear in Splunk. The rest client is part of the IoT Gateway plug-in in Kepware.
![kepware mqtt kepware mqtt](https://cdn.eshop.foxon.cz/71075-large_default/mqtt-client-driver-kepserverex-opc-server.jpg)
Please ensure that your Splunk HEC Collector is properly set up About the REST Client: