

It has connectivity libraries for a vast array of equipment and is a popular choice for unlocking the data from both new and legacy industrial devices.

PTC/Kepware's KEPServerEX is an industry leader in industrial and manufacturing device connectivity. Note: inline images in this sample are not currently showing on the Azure Samples site - to see images and screenshots in this article, visit the github repository by clicking the "Browse on Github" button above Overview So hope to see your help or some reference from you again.These instructions provide the necessary steps to connect PTC/Kepware's KEPServerEX to Azure IoT Hub through Azure IoT Edge.

I think there's a lot of instructions in the internet, but my English is not really good so it's quite hard for me to scan all those document for the answer. And in project 2, Client connects to PLC, then send data to Server.Īnd if so, is there any difference in the configuration? For example, in project 1, I connect the PLC to Client, are there any changes I need to make it work?

So as I understand, the roles of Server and Client in those 2 projects are reversed, right? I mean in project 1, Server connects directly to PLC, why Client access data through Server.
