You will now be greeted by your SAS Token. Create a device for the MQTT client connection in Kepware. Now we are ready to create the device in Azure followed by sending the data via MQTT or REST.ġ7.
#Kepserverex receive data mqttclient update#
Click update and your device explorer should now be connected to itġ6. Launch the program and key in the connection string in the IoT Hub Connection String, Hostname with the hostname. Scroll down to find SetupDeviceExplorer.msi. Move over to the device explorer’s github ġ3. HostName= SharedAccessKeyName=wordpressKepwareDemo SharedAccessKey=C+juxnrQt5SzyJJFli+TgaiWa+j8hGCO8QIEWdkNdS4=Īt this point, we are ready to connect and create the virtual device in the IoT Hubġ2. Copy the connection string – primary key (Third string). You should now see your security policy listedġ1.
In the interest of demo, I am going to allow all the accessġ0. Click Shared access policies on the left toolbar:ĩ. Note: Upon completed you will likely be shown the summary of the resourceĦ. Wait for the IoT Hub instance to be completed. You might want to check the pin to dashboard so that you can access the IoT hub easily. Create an IoT Hub instance in your Azure platform by clicking the + logo on the leftĤ. To begin, you will need to login to your Azure portalĢ.
Here are some great links to the relevant Azure documentation that helps in the connections: There are mainly 2 options to send data to Azure. The following section will assume you already have machines or assets already connected and are ready to send the data to Azure. Traditionally, we are leveraged and well known as an OPC Server. This guide assumes you are familiar with Kepware (but if you are not, Kepware’s flagship product KEPServer EX allows you to connect data from industrial assets like sensors, PLCs, CNC machines and many more. The aim of this guide is to provide you a step-by-step instructions to send data from your industrial asset to the Azure.
0 kommentar(er)
