|
1 | 1 | ---
|
2 | 2 | # Mandatory fields. See more on aka.ms/skyeye/meta.
|
3 |
| -title: Tutorial develop C module for Linux - Azure IoT Edge | Microsoft Docs |
| 3 | +title: Tutorial - develop C module for Linux - Azure IoT Edge | Microsoft Docs |
4 | 4 | description: This tutorial shows you how to create an IoT Edge module with C code and deploy it to a Linux device running IoT Edge
|
5 | 5 | services: iot-edge
|
6 | 6 | author: PatAltimore
|
@@ -53,11 +53,11 @@ Before beginning this tutorial, you should have gone through the previous tutori
|
53 | 53 | * [Visual Studio Code](https://code.visualstudio.com/) configured with the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools).
|
54 | 54 | * [Docker CE](https://docs.docker.com/install/) configured to run Linux containers.
|
55 | 55 |
|
56 |
| -To develop an IoT Edge module in C, install the following additional prerequisites on your development machine: |
| 56 | +To develop an IoT Edge module in C, install the following prerequisites on your development machine: |
57 | 57 |
|
58 | 58 | * [C/C++ extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) for Visual Studio Code.
|
59 | 59 |
|
60 |
| -Installing the Azure IoT C SDK is not required for this tutorial, but can provide helpful functionality like intellisense and reading program definitions. For installation information, see [Azure IoT C SDKs and Libraries](https://github.com/Azure/azure-iot-sdk-c). |
| 60 | +Installing the Azure IoT C SDK isn't required for this tutorial, but can provide helpful functionality like intellisense and reading program definitions. For installation information, see [Azure IoT C SDKs and Libraries](https://github.com/Azure/azure-iot-sdk-c). |
61 | 61 |
|
62 | 62 | ## Create a module project
|
63 | 63 |
|
@@ -106,7 +106,7 @@ Currently, Visual Studio Code can develop C modules for Linux AMD64 and Linux AR
|
106 | 106 |
|
107 | 107 | ### Update the module with custom code
|
108 | 108 |
|
109 |
| -The default module code receives messages on an input queue and passes them along through an output queue. Let's add some additional code so that the module processes the messages at the edge before forwarding them to IoT Hub. Update the module so that it analyzes the temperature data in each message, and only sends the message to IoT Hub if the temperature exceeds a certain threshold. |
| 109 | +The default module code receives messages on an input queue and passes them along through an output queue. Let's add more code so the module processes messages at the edge before forwarding them to IoT Hub. Update the module so that it analyzes the temperature data in each message, and only sends the message to IoT Hub if the temperature exceeds a certain threshold. |
110 | 110 |
|
111 | 111 | 1. The data from the sensor in this scenario comes in JSON format. To filter messages in JSON format, import a JSON library for C. This tutorial uses Parson.
|
112 | 112 |
|
@@ -324,7 +324,7 @@ Make sure that your IoT Edge device is up and running.
|
324 | 324 |
|
325 | 325 | 2. Right-click the name of your IoT Edge device, then select **Create Deployment for Single Device**.
|
326 | 326 |
|
327 |
| -3. Select the **deployment.amd64.json** file in the **config** folder and then click **Select Edge Deployment Manifest**. Do not use the deployment.template.json file. |
| 327 | +3. Select the **deployment.amd64.json** file in the **config** folder and then click **Select Edge Deployment Manifest**. Don't use the deployment.template.json file, as that file is only a template. |
328 | 328 |
|
329 | 329 | 4. Under your device, expand **Modules** to see a list of deployed and running modules. Click the refresh button. You should see the new **CModule** running along with the **SimulatedTemperatureSensor** module and the **$edgeAgent** and **$edgeHub**.
|
330 | 330 |
|
@@ -358,7 +358,7 @@ We used the CModule module twin in the deployment manifest to set the temperatur
|
358 | 358 |
|
359 | 359 | ## Clean up resources
|
360 | 360 |
|
361 |
| -If you plan to continue to the next recommended article, you can keep the resources and configurations that you created and reuse them. You can also keep using the same IoT Edge device as a test device. |
| 361 | +If you continue to the next recommended article, you can keep your resources and configurations and reuse them. You can also keep using the same IoT Edge device as a test device. |
362 | 362 |
|
363 | 363 | Otherwise, you can delete the local configurations and the Azure resources that you used in this article to avoid charges.
|
364 | 364 |
|
|
0 commit comments