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/how-to-use-3d-scenes-studio.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,7 +244,7 @@ Once you've defined your property expression, select **Add condition** to define
244
244
245
245
In the **Add condition** options, enter a **Label** for the condition in the visualization.
246
246
247
-
Then, set the **Values** to identify value boundaries for the condition (the exact selection will change depending on the property type). For numerical properties, vhe min of each value range is inclusive, and the max is exclusive.
247
+
Then, set the **Values** to identify value boundaries for the condition (the exact selection will change depending on the property type). For numerical properties, the min of each value range is inclusive, and the max is exclusive.
248
248
249
249
Under **Actions**, define what happens in the scene visualization when the condition is met. You can use **Mesh coloring** to control the color of the property expression in the viewer, or **Badge** to display a badge of a certain color and icon when the condition for the property expression is met.
Copy file name to clipboardExpand all lines: articles/digital-twins/quickstart-3d-scenes-studio.md
+35-31Lines changed: 35 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,42 +202,46 @@ Next, you'll create a *behavior* for the element. These behaviors allow you to c
202
202
203
203
1. Skip the **Twins** tab, which isn't used in this quickstart.
204
204
205
-
1. Switch to the **Visual rules** tab. *Visual rules* are data-driven overlays on your elements that you can configure to indicate the health or status of the element. Here, you'll set some conditions to indicate the efficiency of the packing line.
205
+
1. Switch to the **Visual rules** tab. *Visual rules* are data-driven overlays on your elements that you can configure to indicate the health or status of the element.
206
206
207
-
1. Select **Add Rule**.
207
+
1. First, you'll set some conditions to indicate the efficiency of the packing line.
208
208
209
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules.png" alt-text="Screenshot of the New behavior options in 3D Scenes Studio, showing the Visual rules options." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules.png":::
210
-
211
-
1. Enter a **Display name** of *Hourly pickups*. Leave the **Property expression** on **Single property** and open the property dropdown list. It contains names of all the properties on the primary twin for the *Arm1* element. Select *PrimaryTwin.FailedPickupsLastHr*. Then, select **Add condition**.
212
-
213
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-2.png" alt-text="Screenshot of the New behavior options in 3D Scenes Studio, showing the New visual rule options." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-2.png":::
214
-
215
-
1. Next, you'll define some boundaries to indicate when the hourly pickups are missing too many packages. For this scenario, let's say an arm needs attention if it misses three or more pickups in an hour. **Label** the condition *>3 missed pickups*, and define a value range between *3* and *Infinity* (the min range value is inclusive, and the max value is exclusive). Assign an **Element coloring** of red. Select **Save**.
216
-
217
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-3.png" alt-text="Screenshot of the Add condition options in 3D Scenes Studio creating the coloring condition." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-3.png":::
218
-
219
-
Select **Add condition** again, and create a condition labeled *1-3 missed pickups*. Define a value range between *1* and *3*, and assign an **Element coloring** of orange. Save the condition.
220
-
221
-
Select **Add condition** one more time, and create a condition labeled *0 missed pickups*. Define a value range between *0* and *1*, and assign an **Element coloring** of green. Save the condition.
222
-
223
-
After creating all three conditions, **Save** the new visual rule.
224
-
225
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-4.png" alt-text="Screenshot of saving the finished conditions in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-4.png":::
226
-
227
-
1. Next, create one more visual rule to display alerts for missed packages. Select **Add Rule** again.
228
-
229
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge.png" alt-text="Screenshot of adding a second rule in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge.png":::
230
-
231
-
1. Enter a **Display name** of *PickupFailedAlert*. Change the **Property expression** to **Custom (advanced)**, enter a property of *PrimaryTwin.PickupFailedAlert*, and set the **Type** to *boolean*. This is a boolean property on the arm twin that is set to True when a package pickup fails. Select **Add condition**.
232
-
233
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-2.png" alt-text="Screenshot of adding a condition for the second visual rule in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-2.png":::
234
-
235
-
1. Enter a **Label** of *${PrimaryTwin.PickupFailedBoxID} failed*. This will dynamically display the value of the arm twin's string property *PickupFailedBoxID*, which holds an ID representing the box that the arm most recently failed to pick up. Set the **Value** to **True** and choose a **Visual type** of **Badge**. Set the **Color** to red and choose an **Icon**. Select **Save**.
209
+
1. Select **Add Rule**.
210
+
211
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules.png" alt-text="Screenshot of the New behavior options in 3D Scenes Studio, showing the Visual rules options." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules.png":::
212
+
213
+
1. Enter a **Display name** of *Hourly pickups*. Leave the **Property expression** on **Single property** and open the property dropdown list. It contains names of all the properties on the primary twin for the *Arm1* element. Select *PrimaryTwin.FailedPickupsLastHr*. Then, select **Add condition**.
214
+
215
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-2.png" alt-text="Screenshot of the New behavior options in 3D Scenes Studio, showing the New visual rule options." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-2.png":::
216
+
217
+
1. Next, you'll define some boundaries to indicate when the hourly pickups are missing too many packages. For this scenario, let's say an arm needs attention if it misses more than three pickups in an hour. **Label** the condition *>3 missed pickups*, and define a value range between *4* and *Infinity* (the min range value is inclusive, and the max value is exclusive). Assign an **Element coloring** of red. Select **Save**.
218
+
219
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-3.png" alt-text="Screenshot of the Add condition options in 3D Scenes Studio creating the coloring condition." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-3.png":::
220
+
221
+
1. Select **Add condition** again, and create a condition labeled *1-3 missed pickups*. Define a value range between *1* and *4*, and assign an **Element coloring** of orange. Save the condition.
222
+
223
+
Select **Add condition** one more time, and create a condition labeled *0 missed pickups*. Define a value range between *0* and *1*, and assign an **Element coloring** of green. Save the condition.
224
+
225
+
After creating all three conditions, **Save** the new visual rule.
226
+
227
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-4.png" alt-text="Screenshot of saving the finished conditions in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-4.png":::
236
228
237
-
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-3.png" alt-text="Screenshot of the Add condition options in 3D Scenes Studio creating the badge condition." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-3.png":::
229
+
1. Next, create one more visual rule to display alerts for missed packages.
238
230
239
-
1. You should now see both of your rules listed in the **Visual rules** tab.
231
+
1. From the **Visual rules** tab, select **Add Rule** again.
240
232
233
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge.png" alt-text="Screenshot of adding a second rule in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge.png":::
234
+
235
+
1. Enter a **Display name** of *PickupFailedAlert*. Change the **Property expression** to **Custom (advanced)**, enter a property of *PrimaryTwin.PickupFailedAlert*, and set the **Type** to *boolean*. This is a boolean property on the arm twin that is set to *True* when a package pickup fails. Select **Add condition**.
236
+
237
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-2.png" alt-text="Screenshot of adding a condition for the second visual rule in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-2.png":::
238
+
239
+
1. Enter a **Label** of *${PrimaryTwin.PickupFailedBoxID} failed*. Later, in the scene view, this will dynamically display the value of the arm twin's string property *PickupFailedBoxID*, which holds an ID representing the box that the arm most recently failed to pick up. Set the **Value** to *True* and choose a **Visual type** of *Badge*. Set the **Color** to red and choose an **Icon**. Select **Save**.
240
+
241
+
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-3.png" alt-text="Screenshot of the Add condition options in 3D Scenes Studio creating the badge condition." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-badge-3.png":::
242
+
243
+
You should now see both of your rules listed in the **Visual rules** tab.
244
+
241
245
:::image type="content" source="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-complete.png" alt-text="Screenshot of the finished visual rules in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/new-behavior-visual-rules-complete.png":::
242
246
243
247
1. Switch to the **Widgets** tab. Widgets are data-driven visuals that provide additional context and data, to help you understand the scenario that the behavior represents. Here, you'll add two visual widgets to display property information for the arm element.
0 commit comments