|
||||||||||||||
Restricted Laser Tracking of SatellitesWerner GurtnerOriginal: 02-May-2005 1. Introduction There are satellites that must (or can) only be tracked by laser ranging under certain restrictions or conditions:
With fixed nadir pointing, the satellite can be protected by imposing a maximum allowable elevation for the station to operate. The elevation would be pass dependent and all ranging to the satellite must cease above this level. For off-nadir pointing, operating restrictions at each station will depend upon station position, spacecraft position and orientation, and the field of view of any vulnerable on-board detectors. In general this information will not be available at the stations, and the respective satellite mission control center must provide the tracking constraints to each of the participating stations in advance. In cases where satellites can be repositioned or re-oriented to a non-nominal direction (actively or because of an attitude control system failure) it may be necessary to update these tracking or viewing constraints in a very short timeframe. In some cases it may not be practical or prudent to issue long-term viewing constraints which may inadvertently place the satellite in jeopardy. In order to be able to track the satellites under such restrictions, we need to:
2. Procedures 2.1 Fixed nadir pointing The mission control center for the relevant satellite defines the maximum elevation (including a safety factor) up to which laser ranging can be performed. For the time interval during which the satellite is above this maximum elevation, the tracking system has to shut down / block the laser automatically. An additional level of safety can be added by splitting the pass into two independent segments, so that the system will not track the pass segment above the maximum elevation, at all. The defined maximum elevation can include a maximum off-nadir pointing angle within which the satellite can operate. If this angle is small it may be more effective to decrease the maximum elevation accordingly to avoid having to compute individual pointing-dependent pass segments. Example: ICESsat: Maximum elevation set to 70 degrees 2.2 Off nadir pointing (pass- and station-dependent forbidden zones) In cases where corner cubes or vulnerable detectors are pointing to off-nadir positions satellite passes may have to be divided into more complicated pass segments. The mission control center will generate a station-dependent pass segment list or viewing table and distribute it to the stations in advance. As stations may use different minimum elevations for different satellites or weather conditions or depending on their actual horizon mask, the pass segment lists will be based on a low minimum elevation angle, e.g. 5 degrees. Stations will set their own minimum elevation angle as required. The pass segment list (see below) will contain all pass segments for a time period to be selected by the mission control. The list will include the station code, the satellite name, the start and end dates/times for all pass segments, the maximum elevation for each pass segment, and the segment length. The following example defines the contents and format of the list. Example: Satellite : GP-B Generation Date : 2004-07-23 19:07:00 [UTC] Generated by : GP-B Mission Operations / Stanford University Minimum Elevation : 5 deg ----------------------------------------------------------------------------- Start Date/Time End Date/TimeMaxEl Dur ID SAT COSPAR SIC [UTC] [UTC][deg][min] ---- ---------- ------- ---- ------------------- ------------------- ------- 1824 GP-B 0401401 8603 2004-07-24 00:46:57 2004-07-24 00:53:51 80 6.9 1824 GP-B 0401401 8603 2004-07-24 02:23:59 2004-07-24 02:28:26 10 4.4 1824 GP-B 0401401 8603 2004-07-24 11:51:43 2004-07-24 11:55:45 27 4.0 1824 GP-B 0401401 8603 2004-07-24 13:29:21 2004-07-24 13:33:19 27 4.0 ----------------------------------------------------------------------------- Start Date/Time End Date/TimeMaxEl Dur ID SAT COSPAR SIC [UTC] [UTC][deg][min] ---- ---------- ------- ---- ------------------- ------------------- ------- 7810 GP-B 0401401 8603 2004-07-24 00:47:15 2004-07-24 00:52:53 13 5.6 7810 GP-B 0401401 8603 2004-07-24 02:25:23 2004-07-24 02:32:23 67 7.0 7810 GP-B 0401401 8603 2004-07-24 04:02:14 2004-07-24 04:05:52 7 3.6 7810 GP-B 0401401 8603 2004-07-24 13:28:30 2004-07-24 13:32:27 27 3.9
Descriptive file header: 4 lines, contents start after position
20 This version is a slight modification of the original format, decided by the Format and Procedure Working Group on April 26, 2005, to be used after June 1st 2005. A file may contain pass segments for more than one station, see the example. A station can easily extract its records from the pass segment list (e.g., using the UNIX grep utility). The station will "fold" these pass segments onto the locally computed pass start and end times to generate the valid pass definition.
By following the prescribed schedule, the tracking system will range to the satellite only within the accepted pass segments, switching off the laser beam during the forbidden time intervals. In case of mere geometrical blockage, like e.g., for GP-B, the existence of a pass segment list is not mandatory for tracking. 2.3 Additional safety measures Additional safety measures can be in force:
3. Acceptance procedures The precise acceptance procedures will be defined by the mission sponsor as a subset of the procedures described below. 3.1 Description of the tracking system procedures Each SLR tracking station must prepare a detailed description of its procedure to handle the restricted tracking of vulnerable satellites, e.g.:
3.2 Test campaign For each candidate station, the mission control center will prepare a test campaign with a suitable satellite by sending an appropriate pass segment list under the same restrictions/conditions as the satellite in question. The candidate station will track the test satellite under the restricted rules for at least five successful passes. The station will send a report of the tracked passes to the mission control center, together with a list of the effective pass segment start and end times. Stations capable of pass interleaving should track about half of the test passes without and half with pass interleaving. The mission control center will also verify that the forbidden zones were properly omitted from tracking by e.g., using
3.3 "Dry run" on the vulnerable satellite After successful restricted tracking of the test satellite the station can be asked to successfully track some passes of the vulnerable satellite without laser ranging and submit a report about this "dry run" tracking to the mission control center. Finally the mission control center will send the candidate station a written authorization to include the satellite into its routine tracking with a written waiver of any legal liability. Copies of all reports and authorizations have to be sent to the ILRS Central Bureau. 3.4 Verification of actual passes The mission control center can request full-rate data of the first few actual passes and occasionally later during the mission life time to do a more detailed verification of the proper handling of the restricted pass segments. KHz-Stations will decimate the full-rate test data to 10 Hz before submission. 4. Liability in case of unintentional damage The mission control center will issue a written document relieving the accepted tracking station of any liability or financial consequence in case a component of the satellite is unintentionally damaged by the laser beam.
Responsible Government Official: Carey Noll | ||||||||||||||