02.04.2013 Views

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7.1.3 Customer Acquisition Requirements<br />

Acquisition and reacquisition by the customer platform of the TDRS transmitted signal<br />

requires prediction by the customer MOC of the customer platform receive frequency<br />

over various projected time periods. Similarly, acquisition and reacquisition by the <strong>SN</strong><br />

ground terminal of the customer platform signal requires prediction by the customer<br />

MOC of the customer platform transmitter frequency over various projected time<br />

periods. The frequency predictions are ultimately incorporated in the SHO as customer<br />

platform frequencies for the specific service support periods. Refer to Section 9 for<br />

additional information on TDRSS tracking services that can assist customers in<br />

predicting their local oscillator frequencies.<br />

7.1.4 TDRSS Acquisition Support to Customers<br />

For each scheduled TDRSS service support period, the customer requirements for<br />

signal acquisition/reacquisition, and the TDRSS capabilities to aid acquisition/<br />

reacquisition, are as follows:<br />

a. Customer Epoch Uncertainty<br />

1. Autotrack. The maximum epoch time uncertainty of the applicable<br />

customer platform ephemeris supplied to the TDRSS shall be +4.5<br />

seconds and +3.2 seconds for customer platform operations requiring the<br />

TDRSS KuSA return service autotrack process within the TDRSS Primary<br />

FOV and EEFOV, respectively. Similarly, the maximum epoch time<br />

uncertainty of the customer platform ephemeris shall be 4.5 seconds for<br />

the TDRSS KuSA return service autotrack process within the TDRSS<br />

LEOFOV.<br />

NOTE:<br />

KuSAF EEFOV autotrack support and KuSAR EEFOV<br />

autotrack support shall be coordinated through GSFC Code<br />

450. Autotrack service is not available through the Ku-band<br />

return IF service.<br />

2. Program track. The maximum epoch time uncertainty of the applicable<br />

customer platform ephemeris supplied to the TDRSS shall be +4.5<br />

seconds and +3.2 seconds for customer platform operations using TDRSS<br />

KuSA open-loop pointing within the TDRSS Primary FOV and EEFOV,<br />

respectively.<br />

3. LEO Program track. The maximum epoch time uncertainty of the<br />

applicable customer platform ephemeris supplied to the TDRSS shall be<br />

+1.5 seconds for customer platform operations requiring the TDRSS KuSA<br />

open-loop pointing for customers within the TDRSS LEOFOV.<br />

b. Customer Frequency Uncertainty. The customer MOC must know the<br />

operating frequency of the customer platform to within +5 kHz.<br />

Revision 10 7-2 450-<strong>SN</strong>UG

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!