Skip to content

Commit 1f974ea

Browse files
authored
Merge pull request #205749 from hrshelar/patch-5
Update Aqua demo pages for Azure Orbital Ground Station
2 parents 18c05d3 + 0024b11 commit 1f974ea

File tree

2 files changed

+5
-56
lines changed

2 files changed

+5
-56
lines changed

articles/orbital/downlink-aqua.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Sign in to the [Azure portal - Orbital Preview](https://aka.ms/orbital/portal).
7979
> 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.
8080
8181

82-
## Prepare a virtual machine (VM) to receive the downlinked AQUA data
82+
## Prepare your virtual machine (VM) and network to receive AQUA data
8383

8484
1. [Create a virtual network](../virtual-network/quick-create-portal.md) to host your data endpoint virtual machine (VM)
8585
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:
@@ -94,13 +94,7 @@ sudo mount -t tmpfs -o size=28G tmpfs /media/aqua
9494
```console
9595
sudo apt install socat
9696
```
97-
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.
10498

10599
## Configure a contact profile for an AQUA downlink mission
106100
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
132126
| Bandwidth MHz | **15.0** |
133127
| Polarization | **RHCP** |
134128
| 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) |
136130
| Port | **56001** |
137131
| Protocol | **TCP** |
138132
| 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.|

articles/orbital/satellite-imagery-with-orbital-ground-station.md

Lines changed: 2 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Optional setup steps for capturing the ground station telemetry are included in
3232
You must first follow the steps listed in [Tutorial: Downlink data from NASA's AQUA public satellite](downlink-aqua.md).
3333

3434
> [!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:
3636
>
3737
> - **Name:** receiver-vm
3838
> - **Operating System:** Linux (CentOS Linux 7 or higher)
@@ -266,52 +266,7 @@ IPOPP will produce output products in the following directories:
266266

267267
### Capture ground station telemetry
268268

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: 
301-
302-
- [Python](../event-hubs/event-hubs-python-get-started-send.md)
303-
304-
- [.NET](../event-hubs/event-hubs-dotnet-standard-getstarted-send.md) 
305-
306-
- [Java](../event-hubs/event-hubs-java-get-started-send.md) 
307-
308-
- [JavaScript](../event-hubs/event-hubs-node-get-started-send.md)  
309-
310-
Other helpful resources: 
311-
312-
- [Event Hubs using Python Getting Started](../event-hubs/event-hubs-python-get-started-send.md) 
313-
314-
- [Azure Event Hubs client library for Python code samples](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/eventhub/azure-eventhub/samples/async_samples) 
269+
Follow steps here to [receive real-time telemetry from the ground stations](receive-real-time-telemetry.md).
315270

316271
## Next steps
317272

0 commit comments

Comments
 (0)