Prepare for launch and early operations
Follow these steps to get ready for an upcoming satellite launch and acquire your satellite with Azure Orbital Ground Station.
Prerequisites
- An Azure account with an active subscription. Create an account for free.
- Contributor permissions at the subscription level.
- A Basic Support Plan or higher to submit a spacecraft authorization request.
- Private spacecraft: an active satellite license. In certain countries including the United States, authorization for market access (or a waiver of the United States’ market access rules) is required for satellites not licensed in the country.
- Private spacecraft: added as a point of communication to Microsoft and/or Partner ground stations. For more information, see initiate ground station licensing.
- A contact profile resource
Compatibility testing
Compatibility testing is an important risk reduction process in the launch campaign. Azure Orbital Ground Station provides two options to perform compatibility testing.
Option 1 - Buy your own set of equipment for your lab
This option is preferred if you're standing up a new satellite constellation and plan to periodically launch satellites. By procuring your own lab equipment, you can fully verify all aspects of RF functionality.
We can connect you with our digitizer and software modem partner, Kratos. Relevant equipment could include wideband and narrowband digitizers, a wideband software receiver, and a virtualized narrowband modem.
Option 2 - Use our Free Professional Services
Depending on your scenario, it might be impractical for you to obtain your own lab equipment. We can help through our Free Professional Services program at no additional cost.
This option is evaluated on a case-by-case basis, so reach out to the Azure Orbital Ground Station team to learn more. A typical offering is shown below:
For each channel, we execute a replay of a customer furnished RF test vector in our lab against flight-like equipment.
- The customer provides RF test vectors in raw 32-bit I/Q format or bitstream test vectors in a raw format.
- Our team provides a capture of the system output of the other end of the RF chain. Expect a 21 day turn around time.
- We can repeat Steps 1 and 2 up to two more times to eliminate any bugs.
Acquisition of satellite after launch vehicle separation
Satellites typically don't have accurate TLEs before and shortly after launch, and contact windows can shift as the TLE estimates improve. In order to accommodate this uncertainty, Azure Orbital Ground Station supports a Launch Window Scheduling feature in Preview. This feature allows you to reserve contact windows for this critical mission phase ahead of launch without requiring an accurate satellite TLE. You can provide as many TLE updates as needed until five minutes ahead of the scheduled contact start time.
Our team enables the Launch Window Scheduling feature manually on a per-spacecraft basis, so contact Azure Orbital Ground Station to request this Preview feature for your upcoming launch campaign.
The following outlines a typical contact scheduling flow when using Launch Window Scheduling:
You don't need an accurate TLE to schedule a contact. Update the spacecraft resource with the best estimate TLE.
Specify the time window of interest for your contact by adjusting the Start Time and End Time fields in the List Available Contacts API or Portal contact scheduling flow. To account for the unpredictability of launch and vehicle separation, we recommend your window include additional time before and after the anticipated satellite pass.
The service returns contact options if a whole window or partial window is available in your specified block.
Schedule the contact as normal.
Note
TLE updates for Launch Window Scheduling contacts are performed the same way as regular contacts. The TLE will lock five minutes before the start time of a Launch Window Schedule contact. The ground station antenna will use this TLE and move when it computes the satellite is ascending above the minimum elevation.
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for