I’m sorry for the slow reply, but wordpress doesn’t alert me about comments :-(.Ģ) The .cert.pem does need to be stored on the IoT Edge box, on the file system, because as you note, you definitely need it for config.yaml. S Author msstevebus Posted on OctoOctoCategories Azure IoT Edge, Azure IoT Hub, Kepware, MQTT Tags azure iot edge, azure iot hub, kepware, mqtt So, based on the same principals as my “ Connect MQTT client to Azure IoT Edge” post, I’ve put together step-by-step instruction on how to leverage Kepware’s IoT Gateway as an MQTT-based “leaf IoT device” for IoT Edge. However, customers are interested in how to have the data flow through Azure IoT Edge to take advantage of the many nice edge-processing capabilities available. However, in cases where customers either can’t, or don’t want to leverage OPC-UA, Kepware already published a nice technical note showing how to connect Kepware via MQTT directly to Azure IoT Hub via Kepware’s IoT Gateway and MQTT. OPC-UA is both a nice industrial protocol, but more importantly, offers a robust data format that plugs in nicely into other Azure services. Microsoft’s recommended solution is to leverage OPC-UA and our IoT Edge OPC-UA publisher. I’ve gotten the request a few times from customers who leverage, or want to leverage Kepware for connectivity to their manufacturing equipment and then send that data to IoT Hub through Azure IoT Edge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |