How to build a simple IoT Edge Version 2 Heartbeat Module
Recently, the Microsoft Azure IoT Edge platform was updated with more features, better documentation and lots of goodies. Yes, the learning curve of this new version is steep, especially if you are new (like me) to Docker. But once you just have started building your own Edge solution, things seem to fall into place. A logical flow seems to be described in the Microsoft documentation: Simulate an IoT Edge device in Windows Simulate an IoT Edge device in Linux Develop and deploy a C# module Deploy Azure Stream Analytics as a module Deploy Azure Machine Learning as a module Deploy Azure Functions as a module Looks easy, doesn't it? But reading the comments, people are still confused. First of all: DO NOT MIX VERSION ONE AND VERSION TWO DOCUMENTATION. Version one is based on one executable (gw.exe) which injects classes from DLL's (a configuration file has to be supplied). Modules are just classes in the DLL's. Version two is based on Docker Containers, each module is a separate container and therefore each module is a separate executable. These modules share the same logic to connect to a message bus which provides the routing. This 'runtime' has to be installed on the Edge machine, next to/outside the Docker containers. Note: the good thing is that the architecture still stands, multiple modules on top of a messagebus and messages are routed. The better thing is that the routing is now far more intelligent. And Microsoft has provided some guidance for migration After that, work your way through the documentation provided above, and check out my recent blogs: Deploy an Azure StreamAnalytics Job on the IotEdge Introduction to the Microsoft Azure IoTEdge Modbus-tcp-iotedge module Better property roundtrip for Azure IoIEdge Module Twin OK, I know, the learning curve is still steep. How about a full example of a simple module? The full article can be found here The source code of this module is available on Github The module is available for download as a Docker imageDeploying a NodeJS server with SocketIO to Docker using Azure IoT Edge
The current Azure IoT Edge public preview uses Docker to deploy logic from the cloud into local gateways. It's currently featuring: C# modules written in .Net standard Python modules Azure Function built on your machine Azure Stream Analytics jobs built and deployed in the cloud Azure Machine Learning We can expect Microsoft will support other types of modules soon as they have proven with other recent projects. An Azure Cognitive Services module is a good example, it's put in every IoT Edge presentation. The IoT Edge portal makes it possible to deploy modules which are available in private or public image repositories. Could it be possible to build and deploy images to the gateway which are not specifically designed for IoT Edge? It turns out, it is possible. Let's deploy a NodeJS server which serves SocketIO. Read the full article here Accessing NodeJS SockerIO server Configuring the port forwarding Passing through messages using SocketIOQualcomm AI Vision Devkit = IoT + AI + IoT Edge with hardware capabilities and stylish design
Hi, If when you see "IoT", "AI" and "Edge" you see a lot of possibilities and your mind is full of ideas.....and you need a device that combines hardware possibilities, packaging, and price, take a look at the https://azure.github.io/Vision-AI-DevKit-Pages/ stylish design hardware acceleration for AI camera mic speakers different connectors (HDMI, audio, etc) wifi memory card slot battery AND running IoT Edge !!! Get started with this great webcast: https://channel9.msdn.com/Shows/Internet-of-Things-Show/Unboxing-the-Vision-AI-DevKit The official documentation provides a lot of resources. https://azure.github.io/Vision-AI-DevKit-Pages/docs/Get_Started/ The DevKit includes two modules (besides those included by default with IoT Edge, $edge***): The included modules are quite simple but they are a good start to make you interact with the device. The documentation provides links to https://azure.github.io/Vision-AI-DevKit-Pages/docs/projects/ and complete https://azure.github.io/Vision-AI-DevKit-Pages/docs/Tutorial-HOL_Using_the_VisionSample/. Time to create your own module ;). Note: if you are lucky enough to get a devkit, start updating the firmware :).
All Around Azure Virtual Learning Event - Learn, Ask Questions, Get Certified - January 19th, 2021
Interested in becoming a certified Azure IoT developer? Attend our All Around Azure event full of expert-led sessions on how to use IoT on January 19. Sign up to learn from local experts, get your questions answered, and prepare for the certification exam.
Need help with updating disconnected devices
hey, I am new to azure and IOT and I need help with knowing how to do this. The scenario is that: I have a set of Linux devices that can't be connected to the internet ever, these devices should be connected to another device (will have internet) which will act as parent to all these disconnected devices. The challenge is to update these child devices using Azure IOT, the updates will be deployed in the hub, and it has to passed to child devices via parent device and automatically needs to be installed in the child devices. The parent might not require this update or might. How will I do this? also I can't use any scripting mechanisms. Now when I surfed a bit through azure documentation, I found out that I can use device update for this, What I found was: 1) setup every device in IOT hub 2)set the device with internet as parent and others a child 3)set up MCC module in parent 4)Connect the devices physically (Lan or Wi-Fi) 5)Roll out updates Now I don't know whether this is true or not, it's just my understanding. I am having few doubts: 1)do we also add the child devices (disconnected devices in IOT hub), if yes what if we have 1000 devices? (I'm asking about scalability) 2)How do I actually physically connect the parent and child devices, do I just plug in Lan/Wi-Fi, or do I have to do anything else? 3)How to add MCC Module? 4)how does this actually works? is it feasible?
