Update: It was a blizz! The airplane in Budapest after a successful flight. landed The recording is available here:
On Monday, November 15th a great team of MVPs will walk you through the simple process of setting up an Azure IoT solution.
What to expect?
We will take you through an end-to-end solution from real flight tracking data like speed, altitude and location from a flight departing London. During the event we’ll track the flight’s progress to its destination and show how to get that data from an IoT device at the edge into Microsoft Azure IoT and the cloud where it can be processed for display on a dashboard or stored for later processing. We won’t be able to teach you how to become an IoT expert in the 2.5 hours we have – but what we can do is show you how to build on your current developer skills to integrate IoT into your business applications (and passion projects!) and set you up on your journey to become certified in IoT with the Microsoft AZ220 qualification.
I myself will show the power of Time Series Insights to capture data, let you understand how that data can support business objectives, and show how to surface that data from an engineer’s perspective.
The interactive, online, event takes place at 10:00-12:45 GMT (UTC±0).
Azure IoT Edge runs on both Windows 10 and Linux, let’s talk about how to set up that Azure IoT Edge runtime.
The current LTS 1.1.* version of Azure IoT Edge still supports Windows containers on Windows devices.
The newest version of Azure IoT Edge, the 1.2.* version supports running only Linux containers on Windows. This is called EFLOW (Edge for Linux on Windows).
So, Microsoft supports both Linux containers on Linux and Windows too. Technically, you have to write only one solution running on both operating systems.
Still, you have to build and push separate container versions of the same logic based on the processor architecture.
Azure IoT Edge runs on most flavors of (Linux) operating systems that can run containers; however, not all of these systems are equally supported. There is documentation available with an up-to-date list of supported operating systems. Check out if your operating system gets either Tier 1 or Tier 2 support.
As an example, Ubuntu 20.04LTS is currently not officially supported in Tier 1.
Update 21-10-2021: During the recent Azure IoT Edge Summit – Technical Track it is announced Ubuntu 20.04 is on the product team near term roadmap and coming soon.
Still, the Azure IoT Edge runtime can be installed and is considered compatible.
That runtime is built up in a few parts:
A daemon (process) that secures the runtime and start the local part of an Azure IoT Edge solution
The open-source Moby container runtime where the modules will be hosted in
A local directory structure for configuration
Regarding the installation of the runtime, you can follow the original documentation.
This guide does not point you to a simple installation. You need to have technical skills to roll out the runtime. And the rollout is done by hand.
Now, a script is provided and maintained by the Microsoft product team that can be used to automate the roll out of the runtime, including support for DPS.
IoT Plug and Play enables solution builders to integrate IoT devices with their solutions without any manual configuration.
It introduces a model as a public description of a device. This device model advertises the capabilities of the logic on your IoT device like telemetry, properties, and commands. These elements are bundled as an interface. These interfaces are described using the Digital Twins Definition Language (DTDL).
Implementing IPnP in your solution is not that hard. The Azure IoT Device SDKs have you covered. Just interact with the cloud as usual. Only, when setting up the connection, the device exposes a ModelId. This id is compared with public models available in a repository so the actual model can be restored.
Next to direct-internet-connected devices, Azure IoT also support this concept of edge compute:
The way Azure IoT Edge devices are connected to the cloud differs quite a lot.
Azure IoT Edge devices lack the support for a ModelId. So there is no direct reference to any model is a model repository. But each type of edge device comes with a Deployment Manifest, describing the logic to be rolled out on the edge device and related settings.
These differences have an impact on how to implement IoT Plug and Play device templates.
Let’s see how to get started with IPnP for edge devices in IoT Central.