Upgrading your Azure IoT Edge device remotely to the latest release

Last week, the Microsoft Ignite event was hosted in Orlando. As with every Microsoft Event, a lot of new stuff is released by the Microsoft product teams.

The same goes for the IoT Edge runtime, the portal and the logic running on IoT Edge.

The IoT Edge runtime bumped up to version 1.0.2 and there are lots of new features introduced like extended offline operation and proxy support.

And there a lot of bugfixes which is always good 🙂

But the documentation considering the update of your gateways is a bit limited.

If I follow the update procedure, I have to update it on the machine itself.

Let’s check out how we update our runtime remotely.

Update: Microsoft released this document with more details after I wrote this blog. Some parts could be out-dated by now.

Advertentie

Writing commands to IoT Edge Modbus Modules

Microsoft provides several out-of-the-box modules for their Azure IoT Edge platform. If we do a quick search at the Public Docker repository, we see modules like

• microsoft/iot-edge-opc-publisher
• microsoft/iot-edge-opc-proxy
• microsoft/azureiotedge-modbus-tcp
• etc,

I already have described in a previous blog, how to consume and read data from that Modbus module. After checking out the documentation and some testing, I found out how to write commands back to the device too.

Let’s check out how we can use this in a Custom C# module. After that, we use it in an Azure Functions Module. So let’s do a deeper dive into Azure Functions on the IoT Edge as well.