You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-connect-eflow.md
+40-29Lines changed: 40 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,15 @@
1
1
---
2
-
title: Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central | Microsoft Docs
3
-
description: Learn how to connect Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central
2
+
title: Connect Azure IoT Edge for Linux on Windows (EFLOW)
3
+
titleSuffix: IoT Central
4
+
description: Learn how to connect an Azure IoT Edge for Linux on Windows (EFLOW) device to an IoT Central application
4
5
author: dominicbetts
5
6
ms.author: dobett
6
7
ms.date: 10/11/2022
7
8
ms.topic: how-to
8
9
ms.service: iot-central
9
10
---
10
11
11
-
# Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central
12
+
# Connect an IoT Edge for Linux on Windows device to IoT Central
12
13
13
14
[Azure IoT Edge for Linux on Windows (EFLOW)](/windows/iot/iot-enterprise/azure-iot-edge-for-linux-on-windows) lets you run Azure IoT Edge in a Linux container on your Windows device. In this article, you learn how to provision an EFLOW device and manage it from your IoT Central application.
14
15
@@ -27,22 +28,23 @@ To complete the steps in this article, you need:
27
28
28
29
* An [IoT Central application created](howto-create-iot-central-application.md) from the **Custom application** template. To learn more, see [Create an IoT Central application](howto-create-iot-central-application.md).
29
30
30
-
* A Windows device with the following minimum requirements:
31
+
* A Windows device that meets the following minimum requirements:
31
32
32
33
* Windows 10<sup>1</sup>/11 (Pro, Enterprise, IoT Enterprise) or Windows Server 2019<sup>1</sup>/2022
33
34
* Minimum free memory: 1 GB
34
35
* Minimum free disk space: 10 GB
35
-
* <sup>1</sup> Windows 10 and Windows Server 2019 minimum build 17763 with all current cumulative updates installed.
36
36
37
-
To follow the steps in this article, download the [EnvironmentalSensorManifest.json](https://raw.githubusercontent.com/Azure-Samples/iot-central-docs-samples/main/iotedge/EnvironmentalSensorManifest.json) file to your computer.
37
+
<sup>1</sup> Windows 10 and Windows Server 2019 minimum build 17763 with all current cumulative updates installed.
38
+
39
+
To follow the steps in this article, download the [EnvironmentalSensorManifest-1-4.json](https://raw.githubusercontent.com/Azure-Samples/iot-central-docs-samples/main/iotedge/EnvironmentalSensorManifest-1-4.json) file to your computer.
38
40
39
41
## Import a deployment manifest
40
42
41
43
You use a deployment manifest to specify the modules to run on an IoT Edge device. IoT Central manages the deployment manifests for the IoT Edge devices in your solution. To import the deployment manifest for this example:
42
44
43
45
1. In your IoT Central application, navigate to **Edge manifests**.
44
46
45
-
1. Select **+ New**. Enter a name such as *Environmental Sensor* for your deployment manifest, and then upload the *EnvironmentalSensorManifest.json* file you downloaded previously.
47
+
1. Select **+ New**. Enter a name such as *Environmental Sensor* for your deployment manifest, and then upload the *EnvironmentalSensorManifest-1-4.json* file you downloaded previously.
46
48
47
49
1. Select **Next** and then **Create**.
48
50
@@ -66,7 +68,7 @@ In this section, you create an IoT Central device template for an IoT Edge devic
66
68
67
69
1. Select the **management** interface in the **SimulatedTemperatureSensor** module to view the two properties defined in the manifest:
68
70
69
-
:::image type="content" source="media/howto-connect-eflow/imported-manifest.png" alt-text="Device template created from IoT Edge manifest.":::
71
+
:::image type="content" source="media/howto-connect-eflow/imported-manifest.png" alt-text="Screenshot that shows the device template created from IoT Edge manifest.":::
70
72
71
73
### Add telemetry to the device template
72
74
@@ -106,7 +108,7 @@ To add the telemetry definitions to the device template:
106
108
107
109
The **management** interface now includes the **machine**, **ambient**, and **timeCreated** telemetry types:
108
110
109
-
:::image type="content" source="media/howto-connect-eflow/manage-interface.png" alt-text="Interface with machine and ambient telemetry types.":::
111
+
:::image type="content" source="media/howto-connect-eflow/manage-interface.png" alt-text="Screenshot that shows the interface with machine and ambient telemetry types.":::
110
112
111
113
### Add views to template
112
114
@@ -140,7 +142,7 @@ Before you can connect a device to IoT Central, you must register the device in
140
142
141
143
You now have a new device with the status **Registered**:
:::image type="content" source="media/howto-connect-eflow/new-device.png" alt-text="Screenshot that shows the new IoT Edge device in the registered state.":::
144
146
145
147
### Get the device credentials
146
148
@@ -158,49 +160,58 @@ You've now finished configuring your IoT Central application to enable an IoT Ed
158
160
159
161
## Install and provision an EFLOW device
160
162
163
+
To install and provision your EFLOW device:
164
+
161
165
1. In an elevated PowerShell session, run each of the following commands to download IoT Edge for Linux on Windows.
You can specify custom IoT Edge for Linux on Windows installation and VHDX directories by adding `INSTALLDIR="<FULLY_QUALIFIED_PATH>"` and `VHDXDIR="<FULLY_QUALIFIED_PATH>"` parameters to the install command.
182
+
> [!TIP]
183
+
> You can specify custom IoT Edge for Linux on Windows installation and VHDX directories by adding `INSTALLDIR="<FULLY_QUALIFIED_PATH>"` and `VHDXDIR="<FULLY_QUALIFIED_PATH>"` parameters to the install command.
176
184
177
185
1. Create the IoT Edge for Linux on Windows deployment. The deployment creates your Linux VM and installs the IoT Edge runtime for you.
178
186
179
-
```powershell
180
-
Deploy-Eflow
181
-
```
187
+
```powershell
188
+
Deploy-Eflow
189
+
```
182
190
183
191
1. Use the **ID scope**, **Device ID** and the **Primary Key** you made a note of previously.
To learn about other ways you can deploy and provision an EFLOW device, see [Install and provision Azure IoT Edge for Linux on a Windows device](../../iot-edge/how-to-install-iot-edge-on-windows.md).
190
198
191
199
Go to the **Device Details** page in your IoT Central application and you can see telemetry flowing from your EFLOW device:
192
200
193
-
:::image type="content" source="media/howto-connect-eflow/telemetry.png" alt-text="Telemetry from the device.":::
201
+
:::image type="content" source="media/howto-connect-eflow/telemetry.png" alt-text="Screenshot that shows a plot of telemetry from the device.":::
202
+
203
+
> [!TIP]
204
+
> You may need to wait several minutes for the IoT Edge device to start sending telemetry.
194
205
195
206
## Clean up resources
196
207
197
-
If you want to remove the Azure IoT Edge for Linux on Windows installation from your device, use the following commands.
208
+
If you want to uninstall EFLOW from your device, use the following commands.
198
209
199
210
1. Open **Settings** on Windows
200
211
1. Select **Add or Remove Programs**
201
212
1. Select **Azure IoT Edge LTS** app
202
213
1. Select **Uninstall**
203
214
204
-
## Next Steps
215
+
## Next steps
205
216
206
-
Now that you've learned how to connect Azure IoT Edge for Linux on Windows (EFLOW) with IoT Central, the suggested next step is to learn how to [Connect devices through an IoT Edge transparent gateway](how-to-connect-iot-edge-transparent-gateway.md).
217
+
Now that you've learned how to connect an (EFLOW) device to IoT Central, the suggested next step is to learn how to [Connect devices through an IoT Edge transparent gateway](how-to-connect-iot-edge-transparent-gateway.md).
0 commit comments