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-operations/discover-manage-assets/concept-assets-asset-endpoints.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
@@ -28,7 +28,7 @@ You can create, edit, and delete asset endpoints and assets by using the Azure I
28
28
29
29
Before you can create an asset, you need to define an asset endpoint profile. An *asset endpoint* is a profile that describes southbound edge connectivity information for one or more assets.
30
30
31
-
Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), and the connector for ONVIF (preview). Asset endpoints are configurations for a connector that enable it to connect to an assets. For example:
31
+
Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), and the connector for ONVIF (preview). Asset endpoints are configurations for a connector that enable it to connect to an asset. For example:
32
32
33
33
- An asset endpoint for OPC UA stores the information you need to connect to an OPC UA server.
34
34
- An asset endpoint for the media connector stores the information you need to connect to a media source.
Copy file name to clipboardExpand all lines: articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.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
@@ -27,7 +27,7 @@ An ONVIF compliant camera connected to your Azure IoT Operations cluster. If you
27
27
28
28
The connector for ONVIF (preview) uses [asset endpoint and asset](concept-assets-asset-endpoints.md) custom resources to represent the connection and the camera.
29
29
30
-
For example, use the following Bicep and parameters to to create an asset endpoint that enables discovery of an ONVIF compliant camera at `http://onvif-rtsp-simulator:8000`:
30
+
For example, use the following Bicep and parameters to create an asset endpoint that enables discovery of an ONVIF compliant camera at `http://onvif-rtsp-simulator:8000`:
31
31
32
32
```bicep
33
33
metadata description = 'Asset endpoint profile for ONVIF discovery'
@@ -100,7 +100,7 @@ Each **DiscoveredAsset** custom resource represents one of the [ONVIF services](
100
100
101
101
Each **DiscoveredAssetEndpointProfile** custom resource represents a video stream format that the camera exposes.
102
102
103
-
Currently, during public preview, you must manually create the **Asset** and **AssetEndpointProfile** custom resources that represent the capabilities of the camera and it's video streams.
103
+
Currently, during public preview, you must manually create the **Asset** and **AssetEndpointProfile** custom resources that represent the capabilities of the camera and its video streams.
104
104
105
105
To create an asset that represents the PTZ capabilities of the camera discovered above, use the following Bicep and parameters:
106
106
@@ -156,7 +156,7 @@ The following JSON snippet shows a set of parameter values to use:
156
156
157
157
These parameters configure:
158
158
159
-
- The name of the asset to create. The `-ptz` suffix is a reuired convention to indicate that the asset represents the PTZ capabilities of the camera.
159
+
- The name of the asset to create. The `-ptz` suffix is a required convention to indicate that the asset represents the PTZ capabilities of the camera.
160
160
- The associated asset endpoint you created previously.
161
161
162
162
To apply the previous configuration, save the examples above as files, and run the following command:
0 commit comments