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/orbital/downlink-aqua.md
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
79
79
> You can confirm that your spacecraft resource for AQUA is authorized by checking that the **Authorization status** shows **Allowed** in the spacecraft's overiew page.
80
80
81
81
82
-
## Prepare a virtual machine (VM) to receive the downlinked AQUA data
82
+
## Prepare your virtual machine (VM) and network to receive AQUA data
83
83
84
84
1.[Create a virtual network](../virtual-network/quick-create-portal.md) to host your data endpoint virtual machine (VM)
85
85
2.[Create a virtual machine (VM)](../virtual-network/quick-create-portal.md#create-virtual-machines) within the virtual network above. Ensure that this VM has the following specifications:
5. Edit the [Network Security Group](../virtual-network/network-security-groups-overview.md) for the subnet that your virtual machine is using to allow inbound connections from the following IPs over TCP port 56001:
98
-
- 20.47.120.4
99
-
- 20.47.120.38
100
-
- 20.72.252.246
101
-
- 20.94.235.188
102
-
- 20.69.186.50
103
-
- 20.47.120.177
97
+
5.[Prepare the network for Azure Orbital Ground Station integration](prepare-network.md) to configure your network.
104
98
105
99
## Configure a contact profile for an AQUA downlink mission
106
100
1. In the Azure portal search box, enter **Contact profile**. Select **Contact profile** in the search results.
@@ -132,7 +126,7 @@ sudo apt install socat
132
126
| Bandwidth MHz |**15.0**|
133
127
| Polarization |**RHCP**|
134
128
| Endpoint name | Enter the name of the virtual machine (VM) you created above |
135
-
| IP Address | Enter the Public IP address of the virtual machine you created above (VM) |
129
+
| IP Address | Enter the Private IP address of the virtual machine you created above (VM) |
136
130
| Port |**56001**|
137
131
| Protocol |**TCP**|
138
132
| Demodulation Configuration | Leave this field **blank** or request a demodulation configuration from the [Azure Orbital team](mailto:[email protected]) to use a software modem. Include your Subscription ID, Spacecraft resource ID, and Contact Profile resource ID in your email request.|
Copy file name to clipboardExpand all lines: articles/orbital/satellite-imagery-with-orbital-ground-station.md
+2-47Lines changed: 2 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Optional setup steps for capturing the ground station telemetry are included in
32
32
You must first follow the steps listed in [Tutorial: Downlink data from NASA's AQUA public satellite](downlink-aqua.md).
33
33
34
34
> [!NOTE]
35
-
> In the section [Prepare a virtual machine (VM) to receive the downlinked AQUA data](downlink-aqua.md#prepare-a-virtual-machine-vm-to-receive-the-downlinked-aqua-data), use the following values:
35
+
> In the section [Prepare a virtual machine (VM) to receive the downlinked AQUA data](downlink-aqua.md#prepare-your-virtual-machine-vm-and-network-to-receive-aqua-data), use the following values:
36
36
>
37
37
> -**Name:** receiver-vm
38
38
> -**Operating System:** Linux (CentOS Linux 7 or higher)
@@ -266,52 +266,7 @@ IPOPP will produce output products in the following directories:
266
266
267
267
### Capture ground station telemetry
268
268
269
-
An Azure Orbital Ground station emits telemetry events that can be used to analyze the ground station operation during the contact. You can configure your contact profile to send such telemetry events to Azure Event Hubs. The steps below describe how to create Event Hubs and grant Azure Orbital access to send events to it.
270
-
271
-
1. In your subscription, go to **Resource Provider** settings and register Microsoft.Orbital as a provider.
272
-
2.[Create Azure Event Hubs](../event-hubs/event-hubs-create.md) in your subscription.
273
-
3. From the left menu, select **Access Control (IAM)**. Under **Grant Access to this Resource**, select **Add Role Assignment**.
274
-
4. Select **Azure Event Hubs Data Sender**.
275
-
5. Assign access to '**User, group, or service principal**'.
276
-
6. Click '**+ Select members**'.
277
-
7. Search for '**Azure Orbital Resource Provider**' and press **Select**.
278
-
8. Press **Review + Assign** to grant Azure Orbital the rights to send telemetry into your event hub.
279
-
9. To confirm the newly added role assignment, go back to the Access Control (IAM) page and select **View access to this resource**.
280
-
281
-
Congrats! Orbital can now communicate with your hub.
282
-
283
-
### Enable telemetry for a contact profile in the Azure portal
284
-
285
-
1. Go to **Contact Profile** resource, and click **Create**.
286
-
2. Choose a namespace using the **Event Hubs Namespace** dropdown.
287
-
3. Choose an instance using the **Event Hubs Instance** dropdown that appears after namespace selection.
288
-
289
-
### Test telemetry on a contact
290
-
291
-
1. Schedule a contact using the Contact Profile that you previously configured for Telemetry.
292
-
2. Once the contact begins, you should begin to see data in your Event Hubs soon after.
293
-
294
-
To verify that events are being received in your Event Hubs, you can check the graphs present on the Event Hubs namespace **Overview** page. The graphs show data across all Event Hubs instances within a namespace. You can navigate to the Overview page of a specific instance to see the graphs for that instance.
295
-
296
-
You can enable an Event Hubs [Capture feature](../event-hubs/event-hubs-capture-enable-through-portal.md) that will automatically deliver the telemetry data to an Azure Blob storage account of your choosing.
297
-
298
-
Once enabled, you can check your container and view or download the data.
299
-
300
-
The Event Hubs documentation provides a great deal of guidance on how to write simple consumer apps to receive events from Event Hubs:
0 commit comments