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/digital-twins/quickstart-view-occupancy-dotnet.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ services: digital-twins
9
9
ms.devlang: csharp
10
10
ms.topic: quickstart
11
11
ms.custom: mvc seodec18
12
-
ms.date: 11/12/2019
12
+
ms.date: 01/10/2020
13
13
# As a developer new to Azure Digital Twins, I need to understand how to send motion and carbon dioxide telemetry to a space in Azure Digital Twins and how to find available rooms with fresh air by using a back-end application.
14
14
---
15
15
@@ -19,7 +19,7 @@ The Azure Digital Twins service allows you to re-create a digital image of your
19
19
20
20
This quickstart uses [a pair of .NET samples](https://github.com/Azure-Samples/digital-twins-samples-csharp) to digitize an imaginary office building. It shows you how to find available rooms in that building. With Digital Twins, you can associate many sensors with your environment. You also can find out if the air quality of your available room is optimal with the help of a simulated sensor for carbon dioxide. One of the sample applications generates random sensor data to help you visualize this scenario.
21
21
22
-
The following video summarizes quickstart setup:
22
+
The following video summarizes the quickstart setup:
@@ -80,11 +80,11 @@ The spatial graph is provisioned by using the [provisionSample.yaml](https://git
80
80
81
81
1. The provisioning step might take a few minutes. It also provisions an IoT Hub within your Digital Twins instance. It loops through until the IoT Hub shows Status=`Running`.
82
82
83
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-provision-sample.png#lightbox)
83
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-provision-sample.png#lightbox)
84
84
85
85
1. At the end of the execution, copy the `ConnectionString` of the device for use in the device simulator sample. Copy only the string outlined in this image.
86
86
87
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-connection-string.png#lightbox)
87
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-connection-string.png#lightbox)
88
88
89
89
>[!TIP]
90
90
> You can view and modify your spatial graph using the [Azure Digital Twins Graph Viewer](https://github.com/Azure/azure-digital-twins-graph-viewer).
@@ -101,7 +101,7 @@ Build and run the sensor simulator device application by following these steps.
101
101
1. Edit [appsettings.json](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/device-connectivity/appsettings.json) to update **DeviceConnectionString** with the previous `ConnectionString`. Save the updated file.
102
102
1. Run `dotnet run` to start sending sensor data. It will be sent to Azure Digital Twins as shown in the following image.
1. Let this simulator run so that you can view results side by side with the next step action. This window shows you the simulated sensor data sent to Digital Twins. The next step queries in real time to find available rooms with fresh air.
107
107
@@ -121,7 +121,7 @@ The sensor sample simulates random data values for two sensors. They're motion a
121
121
-`Room is available and air is fresh`
122
122
-`Room is not available or air quality is poor`
123
123
124
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-get-available.png#lightbox)
124
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-get-available.png#lightbox)
125
125
126
126
To understand what happened in this quickstart and what APIs were called, open [Visual Studio Code](https://code.visualstudio.com/Download) with the code workspace project found in `digital-twins-samples-csharp`. Use the following command:
Copy file name to clipboardExpand all lines: articles/digital-twins/tutorial-facilities-setup.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: bertvanhoof
8
8
ms.custom: seodec18
9
9
ms.service: digital-twins
10
10
ms.topic: tutorial
11
-
ms.date: 11/12/2019
11
+
ms.date: 01/10/2020
12
12
#Customer intent: As an Azure IoT developer, I want to walk through a sample application to learn how to use the features of Digital Twins to create a spatially aware intelligent IoT solution.
13
13
---
14
14
@@ -125,7 +125,6 @@ public static async Task<IEnumerable<ProvisionResults.Space>> ProvisionSample(Ht
125
125
126
126
return results;
127
127
}
128
-
129
128
```
130
129
131
130
This function uses [provisionSample.yaml](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/occupancy-quickstart/src/actions/provisionSample.yaml) in the same folder. Open this file, and note the hierarchy of an office building: *Venue*, *Floor*, *Area*, and *Rooms*. Any of these physical spaces can contain *devices* and *sensors*. Each entry has a predefined `type`—for example, Floor, Room.
@@ -146,7 +145,7 @@ The **provisionSample.yaml** file contains the following nodes:
146
145
147
146
-**devices**: Spaces can contain `devices`, which are physical or virtual entities that manage a number of sensors. For example, a device might be a user’s phone, a Raspberry Pi sensor pod, or a gateway. In the imaginary building in your sample, note how the room named **Focus Room** contains a **Raspberry Pi 3 A1** device. Each device node is identified by a unique `hardwareId`, which is hardcoded in the sample. To configure this sample for an actual production, replace these with values from your setup.
148
147
149
-
-**sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. Note that these are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line.
148
+
-**sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. These are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line.
Copy file name to clipboardExpand all lines: includes/digital-twins-create-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,17 +15,17 @@
15
15
16
16
1. Select the home side-bar, then **+ Create a resource**.
17
17
18
-
[](./media/create-digital-twins-portal/create-a-resource.png#lightbox)
18
+
[](./media/create-digital-twins-portal/azure-portal-create-a-resource.png#lightbox)
19
19
20
20
1. Search for **Digital Twins**, and select **Digital Twins**.
21
21
22
-
[](./media/create-digital-twins-portal/create-digital-twins.png#lightbox)
22
+
[](./media/create-digital-twins-portal/azure-portal-create-digital-twins.png#lightbox)
23
23
24
24
Alternatively, select **Internet of Things**, and select **Digital Twins (preview)**.
25
25
26
26
1. Select **Create** to start the deployment process.
27
27
28
-
[](./media/create-digital-twins-portal/create-and-confirm-resource.png#lightbox)
28
+
[](./media/create-digital-twins-portal/azure-create-and-confirm-resource.png#lightbox)
29
29
30
30
1. In the **Digital Twins** pane, enter the following information:
31
31
***Resource Name**: Create a unique name for your Digital Twins instance.
Copy file name to clipboardExpand all lines: includes/digital-twins-permissions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
17
17
1. In the [Azure portal](https://portal.azure.com), open **Azure Active Directory** from the expandable left menu, and then open the **App registrations** pane.
18
18
19
-
[](./media/digital-twins-permissions/select-aad-pane.png#lightbox)
19
+
[](./media/digital-twins-permissions/azure-portal-select-aad-pane.png#lightbox)
20
20
21
21
1. Select the **+ New registration** button.
22
22
@@ -30,7 +30,7 @@
30
30
31
31
Check **Access tokens** to enable the **oauth2AllowImplicitFlow** setting in your Manifest.json.
1. Open the **Overview** pane of your registered app, and copy the values of the following entities to a temporary file. You'll use these values to configure your sample application in the following sections.
0 commit comments