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.

Revision 10 C-13 450-<strong>SN</strong>UG<br />

Table C-3. Acquisition Events for TDRSS Services (Normal Forward and Return) (cont’d)<br />

Event Time<br />

TDRSS autotrack<br />

acquisition<br />

complete, high<br />

accuracy tracking<br />

begins; return<br />

service(s)<br />

established; return<br />

service channel<br />

data stream(s)<br />

transferred from the<br />

ground terminal to<br />

NI<strong>SN</strong><br />

Customer MOC<br />

receives return<br />

service data<br />

stream(s), begins<br />

forward service<br />

data transmission<br />

(e.g., preamble<br />

followed by<br />

commands)<br />

Equipment Status<br />

Customer Platform TDRS/Ground Terminal<br />

T8 = R + tauto Continuing as above Autotrack (if enabled)<br />

locked. Return service(s)<br />

established here<br />

Remarks<br />

Signal acquisition will be<br />

completed before TDRSS<br />

autotrack (if enabled)<br />

acquisition is completed tauto<br />

10<br />

T9 = T8 + has Continuing as above Normal operation For has; this acquisition<br />

sequence assumes that<br />

forward service data is sent<br />

by the customer MOC only<br />

after the return service<br />

acquisition is confirmed by<br />

the customer MOC via<br />

return service data (i.e., no<br />

forward return service data<br />

until successful return<br />

service acquisition); typical<br />

preamble consists of 128-bit<br />

alternating sequence<br />

followed by frame<br />

synchronization word to<br />

enable customer platform<br />

command processing

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

Saved successfully!

Ooh no, something went wrong!