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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

customer platform transmitted signal characteristics within the constraints<br />

specified in Table 8-9. Customer platform parameters exceeding these<br />

constraints can also degrade TDRSS KaSA return service performance. Refer<br />

to Section 3, paragraph 3.5 for guidelines if the constraints in this paragraph<br />

cannot be met. Definitions of user customer platform constraints are given in<br />

Appendix E.<br />

d. Multipath. The <strong>SN</strong> ground terminal will provide lockup and interference<br />

protection from multipath signals reflected from the Earth.<br />

8.3.3.3 Signal Tracking<br />

TDRSS provides KaSA 225 MHz return signal tracking (carrier, symbol synchronization,<br />

Viterbi decoder synchronization) for non-powered flight dynamics. During a customer<br />

KaSA return service support period, loss-of-lock (carrier, symbol synchronization, and<br />

Viterbi decoder) indications appear in the periodically updated UPD (every 5 seconds).<br />

The KaSA return service shall maintain signal tracking for the following conditions:<br />

a. Cycle Slips. The mean time-between-cycle slip in the <strong>SN</strong> ground terminal<br />

carrier tracking loop for each TDRSS KaSA return service will be 90 minutes<br />

minimum. This value applies at carrier tracking threshold, which is 3 dB less<br />

than the minimum Prec for BER listed in Table 8-7, and increases exponentially<br />

as a function of linear dB increases in Prec. Cycle slips may result in channel<br />

and/or data polarity reversal. The <strong>SN</strong> ground terminal can correct for these<br />

reversals under the same conditions as the <strong>SN</strong> ground terminal can resolve<br />

channel and/or data polarity ambiguity as discussed in Appendix B. The time<br />

for the <strong>SN</strong> ground terminal to recover from a cycle slip will be consistent with<br />

the time required for the <strong>SN</strong> ground terminal receiver to detect and<br />

automatically reacquire the signal.<br />

b. Bit Slippage. For each TDRSS KaSA return service operating with a minimum<br />

Prec required consistent with the Prec for BER of Table 8-7 and data transition<br />

densities greater than 40% for NRZ symbols, the minimum mean time between<br />

slips caused by a cycle slip in the <strong>SN</strong> ground terminal symbol clock recovery<br />

loop is either 90 minutes or 10 10 symbol periods, whichever is greater. For a<br />

KaSA return service operating with 1 dB more than the minimum Prec required<br />

for the BER, and NRZ symbol transition densities between 25% and 40%, the<br />

minimum mean time between slips is either 90 minutes or 10 10 symbol periods,<br />

whichever is greater.<br />

c. Loss of Symbol Synchronization. For each TDRSS KaSA return service with<br />

data transition densities greater than 40% for NRZ symbols, the <strong>SN</strong> ground<br />

terminal symbol synchronization loop will not unlock for a Prec that is 3 dB less<br />

than the minimum Prec required for BER in Table 8-7 (refer also to note 3 of<br />

Table 8-7). For NRZ symbol transition densities between 25% and 40%, the<br />

<strong>SN</strong> ground terminal symbol synchronizer loop will not unlock for a Prec that is 2<br />

dB less than the minimum Prec required for the BER. In both cases, the BER<br />

performance will be degraded when the Prec is less than the minimum required<br />

for BER.<br />

Revision 10 8-26 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!