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.

Table 5-11. TDRSS MA Return Service Customer Platform Signal Constraints<br />

(cont’d)<br />

Maximum Prec<br />

Parameters (Notes 1, 2, and 13) Description (Notes 1, 2, and 13)<br />

For support through F3-F7 and K, L, M -161.2 dBW<br />

For support through F8-F10 -149 dBW<br />

Notes:<br />

1. The definitions and descriptions of the customer constraints are provided in Appendix E.<br />

2. When a constraint value is listed for a baud rate range and data is transmitted on both channels,<br />

the maximum baud rate of the 2 channels should be used to determine the constraint value<br />

applicable.<br />

3. It is recommended that customers use G2 inversion to increase symbol transition density.<br />

Additionally, biphase symbol formatting increases symbol transition density. CCSDS<br />

randomization is recommended to aid in compliance with the data randomness requirements.<br />

4. The frequency stability requirements are valid at any constant temperature (0.5 C) in the range<br />

expected during the mission. At a minimum, a temperature range of -10 C to +55 C shall be<br />

considered.<br />

5. Noncoherent configurations (DG1 mode 2 and DG2 noncoherent) require a customer transmit<br />

frequency uncertainty of + 700 Hz. If a customer cannot accurately define their transmit frequency<br />

to within + 700 Hz, a customer can request a reconfiguration which would expand the oscillator<br />

frequency search to + 3 kHz for DG1 and SQPSK DG2 configurations and + 35 kHz for BPSK and<br />

QPSK DG2 configurations after the start of service.<br />

6. Derivation of the phase noise requirements involved making assumptions about the distribution of<br />

the phase noise power in each frequency region. Since no phase noise PSD will exactly match<br />

the phase noise power distribution assumed for this derivation, phase noise PSDs which are close<br />

to violating the phase noise limits or phase noise PSDs which violate the phase noise limits<br />

should be evaluated on a case-by-case basis to determine their acceptability.<br />

7. For customers receiving Doppler tracking services, more stringent phase noise constraints should<br />

be considered by the customer. It is the responsibility of the customer to ensure customer<br />

transponder / transmitter phase noise performance enables achievement of the desired total<br />

Doppler tracking error performance. Appendix U provides recommended customer phase noise<br />

performance constraints which ensure a total Doppler tracking error (system + customer) ≤ 0.2<br />

rad/sec (1, channel data rate > 1 kbps) or ≤ 0.4 rad/sec (1, channel data rate ≤ 1 kbps)<br />

assuming an averaging time of 1 second.<br />

8. The minimum SHO EIRP should reflect the minimum Prec expected over the service period, where<br />

the Prec can exceed this minimum by no more than 12 dB. An actual customer Prec value that is<br />

12 dB greater than the minimum may cause false PN lock or nonacquisition.<br />

9. Deleted.<br />

10. Deleted.<br />

11. Bandwidth limitation for gain flatness, phase nonlinearity and gain slope while maintaining<br />

consistency with NTIA spectral emission mask (Appendix D):70% of the signal main lobe width or<br />

70 % of the necessary bandwidth whichever is smaller.<br />

12. Coherent return link phase noise user constraint assumes a forward service signal with no phase<br />

noise on it. Phase noise created in the user receiver carrier tracking loop by thermal noise on the<br />

forward link is a component which must be considered as a contributor to the user coherent<br />

return service phase noise.<br />

13. Customers are recommended to provide to the <strong>SN</strong> a transmitter EVM measurement for each of<br />

their service modes.<br />

Revision 10 5-42 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!