Merge pull request #98940 from MicrosoftDocs/release-iotedge-fall19

Release iotedge fall19

Author: huypub

articles/iot-edge/deploy-modbus-gateway.md

@@ -6,13 +6,13 @@ manager: philmea
 ms.service: iot-edge
 services: iot-edge
 ms.topic: conceptual
-ms.date: 06/28/2019
+ms.date: 11/19/2019
 ms.author: kgremban
 ---
 
 # Connect Modbus TCP devices through an IoT Edge device gateway
 
-If you want to connect IoT devices that use Modbus TCP or RTU protocols to an Azure IoT hub, use an IoT Edge device as a gateway. The gateway device reads data from your Modbus devices, then communicates that data to the cloud using a supported protocol.
+If you want to connect IoT devices that use Modbus TCP or RTU protocols to an Azure IoT hub, you can use an IoT Edge device as a gateway. The gateway device reads data from your Modbus devices, then communicates that data to the cloud using a supported protocol.
 
 ![Modbus devices connect to IoT Hub through IoT Edge gateway](./media/deploy-modbus-gateway/diagram.png)
 
@@ -23,11 +23,11 @@ This article assumes that you're using Modbus TCP protocol. For more information
 ## Prerequisites
 * An Azure IoT Edge device. For a walkthrough on how to set up one, see [Deploy Azure IoT Edge on Windows](quickstart.md) or [Linux](quickstart-linux.md).
 * The primary key connection string for the IoT Edge device.
-* A physical or simulated Modbus device that supports Modbus TCP.
+* A physical or simulated Modbus device that supports Modbus TCP. You will need to know its IPv4 address.
 
 ## Prepare a Modbus container
 
-If you want to test the Modbus gateway functionality, Microsoft has a sample module that you can use. You can access the module from the Azure Marketplace, [Modbus](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoft_iot.edge-modbus?tab=Overview), or with the image URI, **mcr.microsoft.com/azureiotedge/modbus:1.0**.
+If you want to test the Modbus gateway functionality, Microsoft has a sample module that you can use. You can access the module from the Azure Marketplace, [Modbus](https://azuremarketplace.microsoft.com/marketplace/apps/microsoft_iot.edge-modbus?tab=Overview), or with the image URI, `mcr.microsoft.com/azureiotedge/modbus:1.0`.
 
 If you want to create your own module and customize it for your environment, there is an open-source [Azure IoT Edge Modbus module](https://github.com/Azure/iot-edge-modbus) project on GitHub. Follow the guidance in that project to create your own container image. To create a container image, refer to [Develop C# modules in Visual Studio](how-to-visual-studio-develop-csharp-module.md) or [Develop modules in Visual Studio Code](how-to-vs-code-develop-module.md). Those articles provide instructions on creating new modules and publishing container images to a registry.
 
@@ -41,62 +41,27 @@ This section walks through deploying Microsoft's sample Modbus module to your Io
 
 3. Select **Set modules**.
 
-4. Add the Modbus module:
+4. In the **IoT Edge Modules** section, add the Modbus module:
 
-   1. Click **Add** and select **IoT Edge module**.
+   1. Click the **Add** dropdown and select **Marketplace Module**.
+   2. Search for `Modbus` and select the **Modbus TCP Module** by Microsoft.
+   3. The module is automatically configured for your IoT Hub and appears in the list of IoT Edge Modules. The Routes are also automatically configured. Select **Review + create**.
+   4. Review the deployment manifest and select **Create**.
 
-   2. In the **Name** field, enter "modbus".
+5. Select the Modbus module, `ModbusTCPModule`, in the list and select the **Module Twin Settings** tab. The required JSON for the module twin desired properties is auto populated.
 
-   3. In the **Image** field, enter the image URI of the sample container: `mcr.microsoft.com/azureiotedge/modbus:1.0`.
+6. Look for the **SlaveConnection** property in the JSON and set its value to the IPv4 address of your Modbus device.
 
-   4. Check the **Enable** box to update the module twin's desired properties.
+7. Select **Update**.
 
-   5. Copy the following JSON into the text box. Change the value of **SlaveConnection** to the IPv4 address of your Modbus device.
+8. Select **Review + create**, review the deployment, and then select **Create**.
 
-      ```JSON
-      {
-        "properties.desired":{
-          "PublishInterval":"2000",
-          "SlaveConfigs":{
-            "Slave01":{
-              "SlaveConnection":"<IPV4 address>","HwId":"PowerMeter-0a:01:01:01:01:01",
-              "Operations":{
-                "Op01":{
-                  "PollingInterval": "1000",
-                  "UnitId":"1",
-                  "StartAddress":"40001",
-                  "Count":"2",
-                  "DisplayName":"Voltage"
-                }
-              }
-            }
-          }
-        }
-      }
-      ```
+9. Return to the device details page and select **Refresh**. You should see the new `ModbusTCPModule` module running along with the IoT Edge runtime.
 
-   6. Select **Save**.
-
-5. Back in the **Add Modules** step, select **Next**.
-
-7. In the **Specify Routes** step, copy the following JSON into the text box. This route sends all messages collected by the Modbus module to IoT Hub. In this route, **modbusOutput** is the endpoint that Modbus module uses to output data and **$upstream** is a special destination that tells IoT Edge hub to send messages to IoT Hub.
-
-   ```JSON
-   {
-     "routes": {
-       "modbusToIoTHub":"FROM /messages/modules/modbus/outputs/modbusOutput INTO $upstream"
-     }
-   }
-   ```
-
-8. Select **Next**.
-
-9. In the **Review Deployment** step, select **Submit**.
+## View data
 
-10. Return to the device details page and select **Refresh**. You should see the new **modbus** module running along with the IoT Edge runtime.
+View the data coming through the Modbus module:
 
-## View data
-View the data coming through the modbus module:
 ```cmd/sh
 iotedge logs modbus
 ```
@@ -105,5 +70,5 @@ You can also view the telemetry the device is sending by using the [Azure IoT Hu
 
 ## Next steps
 
-- To learn more about how IoT Edge devices can act as gateways, see [Create an IoT Edge device that acts as a transparent gateway](./how-to-create-transparent-gateway.md).
-- For more information about how IoT Edge modules work, see [Understand Azure IoT Edge modules](iot-edge-modules.md).
+* To learn more about how IoT Edge devices can act as gateways, see [Create an IoT Edge device that acts as a transparent gateway](./how-to-create-transparent-gateway.md).
+* For more information about how IoT Edge modules work, see [Understand Azure IoT Edge modules](iot-edge-modules.md).

articles/iot-edge/how-to-access-host-storage-from-module.md

@@ -4,7 +4,7 @@ description: Use environment variables and create options to enable module acces
 author: kgremban
 manager: philmea
 ms.author: kgremban
-ms.date: 10/15/2019
+ms.date: 11/18/2019
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -18,7 +18,7 @@ In addition to storing data using Azure storage services or in your device's con
 
 To enable a link from module storage to the storage on the host system, create an environment variable for your module that points to a storage folder in the container. Then, use the create options to bind that storage folder to a folder on the host machine.
 
-For example, if you wanted to enable the IoT Edge hub to store messages in your device's local storage and retrieve them later, you can configure the environment variables and the create options in the Azure portal in the **Configure advanced Edge Runtime settings** section.
+For example, if you wanted to enable the IoT Edge hub to store messages in your device's local storage and retrieve them later, you can configure the environment variables and the create options in the Azure portal in the **Runtime Settings** section.
 
 1. For both IoT Edge hub and IoT Edge agent, add an environment variable called **storageFolder** that points to a directory in the module.
 1. For both IoT Edge hub and IoT Edge agent, add binds to connect a local directory on the host machine to a directory in the module. For example: