Attachment A - Statement of Work.pdf

NASA WFF S & C Band Telemetry Antenna System SOW-001107

STATEMENT OF WORK

NASA Wallops Flight Facility S & C Band Telemetry Antenna System

Background

The National Aeronautics and Space Administration (NASA) Wallops Flight Facility (WFF) in Wallops Island, VA has a requirement for a dual S & C band precision auto tracking telemetry antenna system. This antenna system will provide telemetry data reception for range missions such as sounding rockets, expendable launch vehicles, unmanned aerial vehicles, missile targets, and aircraft. A minimum 21 dB/K G/T figure of merit at S-Band, and 24 dB/K at C-band is required to support future sounding rocket missions that will reach higher altitude and range, and downlink higher data rates by a factor of ten. The required antenna will support the sounding rocket capabilities and shall be comprised of maintainable, state of the art hardware and software.

Scope

The contractor shall deliver and install an autotrack antenna system that fully meets the attached requirements. The complete system (hereafter referred to as the “Antenna System”) shall include the outdoor antenna hardware (hereafter referred to as the “Antenna Subsystem”, and indoor tracking and control hardware (hereafter referred to as the “Control Subsystem”). All radio frequency (RF) and control signaling between the two subsystems shall utilize fiber optics. NASA will provide the fiber optic cable, but the contractor shall provide all optical interface hardware. The contractor shall integrate the Control Subsystem hardware that includes tracking receivers, multicouplers, camera monitoring system, antenna control unit, and associated components and cabling into an EIA 19-inch rack. The Antenna and Control Subsystems shall be installed at WFF. The contractor shall conduct factory acceptance testing at the contractor’s facility, conduct site acceptance testing, and provide operations and maintenance training at WFF. The contractor shall provide the required specifications for a concrete pad and an electric power connection for NASA.

Requirements

1. The Contractor shall conduct the following meetings:

Meeting Type Schedule Location

Kick-off Meeting Within 21 days after contract start

Remote

Preliminary Design Review (PDR) 3 months WFF Critical Design Review (CDR) 6 months WFF Test Readiness Review (TRR) for FAT and SAT

At least 2 weeks prior to start of test

Remote

Factory Acceptance Testing (FAT) Contractor scheduled Vendor facility Pre-ship Review After Disposition of FAT

RFAs Remote

Site Acceptance Testing (SAT) Contractor scheduled WFF Project Closeout Review After Disposition of SAT

RFAs Remote

NOTE: The Contractor shall complete any Request for Actions (RFA) for each review prior to the next lifecycle review or test. RFAs shall be generated for each lifecycle review and test.

2. The Contractor shall provide an Electrical Power interface control document (ICD) for the NASA power connection no later than 8 weeks after contract start.

3. The Contractor shall provide concrete pad specifications (see requirement #205 of

RQMT-001107) no later than 8 weeks after contract start.

The Contractor shall review and provide comment as necessary on the design drawings of the concrete pad and electrical power interface. The vendor shall provide concurrence on the concrete pad and electrical power interface prior to installation of the antenna system.

4. The Contractor shall provide an equipment rack (H-87” x W-24” x D-30”) for the Control Subsystem equipment to be installed at the WFF (see requirement #5 of RQMT-001107). The rack configuration, elevation, power consumption, and interfaces shall be presented at PDR. The final rack ICD shall be provided at CDR.

5. The Contractor shall conduct FAT of the Antenna System at the vendor facility (see requirement #206 of RQMT-001107). The Government shall witness FAT and shall be notified at least 30 calendar days prior to start of testing.

The FAT shall include checkout of Antenna System. The FAT procedures shall cover testing of the overall Antenna System functionality. NASA will provide a test section of fiber optic cable similar to that being used for the final installation at WFF. The test section shall be used to connect the Antenna and Control Subsystems for FAT.

The Contractor shall conduct a FAT dry run and provide results to NASA at the FAT Test Readiness Review prior to formal FAT witnessed by NASA.

6. The Contractor shall provide crane and forklift services necessary to support the installation of the Antenna System.

7. The Contractor shall provide on-site installation (as per NASA and/or OSHA requirements) and Antenna System SAT at WFF (see requirement #206 of RQMT- 001107). The Contractor shall notify the Government at least 60 calendar days prior to planned on-site installation start date and shall coordinate specific dates with the Government.

8. The Contractor shall provide training for antenna operation and maintenance within 30 days after the completion of the SAT to be conducted at WFF for a minimum of 10 personnel (see requirement #215 of RQMT-001107).

Note: All documents developed under this contract shall belong to the Government.

Deliverables

Deliverables Frequency Delivery Method FAT Test Procedures 60 calendar days prior to start of test

(see requirement #207 of RQMT- 001107).

Electronic PDF

SAT Test Procedures 60 calendar days prior to start of test (see requirement #207 of RQMT- 001107).

Electronic PDF

Status Reports Monthly Electronic PDF Technical Data including specifications, interface data, system and interconnect drawings, technical and vendor manuals, user guides, training materials, and maintenance procedures (see requirements #209 & #231 of

RQMT-001107).

With Delivery of Antenna Hard and digital copies

Antenna System Test Data 15 days after test completion Two (2) printed copies and one (1) electronic copy. Electronic copy shall be on DVD, Blue-Ray disc, or as digital download.

Training Materials for 10 personnel Prior to start of training One (1) electronic copy of the training materials shall be provided. Electronic copy shall be on DVD, Blue-Ray disc, or as digital download.

Government-Furnished Equipment and Government-Furnished Information

1. The Government shall provide the concrete pad for the Antenna Subsystem.

2. The Government shall provide the electrical service for the Antenna Subsystem.

3. The Government shall provide required floor space and electrical power for the

Control Subsystem equipment.

4. The Government shall be responsible for connectivity to the Control Subsystem rack in building N-162 (see requirements #41-44 of RQMT-001107).

5. The Government shall provide IRIG-B and NTP timecode interface cabling to the

Control Subsystem rack.

6. The Government shall provide the fiber optic cable interfacing the Antenna and

Control Subsystems, with the appropriate number of optical fibers (see requirements #41-44 of RQMT-001107).

7. The Government shall be using GFE standard fiber connectivity (a patch panel at each end, 9/125 micron single mode fiber cabling, and LC UPC coupler plates) (see requirements #41-44 of RQMT-001107).

8. The Government shall provide an indoor working space with access to internet and phone service for on-site testing (SAT) as well as the maintenance and operations training.

9. The Government shall provide a bore site system for SAT at WFF.

Attachments:

The attached appendices define required slaving and predict data formats to be supported by the antenna control unit referenced in requirements #101 - 114 of RQMT-001107

Appendix A. Ethernet Launch Trajectory Acquisition System (eLTAS) Format eLTAS network data packets are used to transport target position information and velocity as a slaving source to the range tracking systems. eLTAS packets are transmitted as UDP datagrams from source systems every 100 ms on the even tenth of a second. The message consists of a fixed header, optional standard header, and data packet as shown in Table A.1. The message is 302 bytes long when the optional standard header is included, otherwise the message is 46 bytes long. The header and packet format definitions are shown in Table A.2 – A.4.

eLTAS Message The Ethernet Standard LTAS Message is generated by RADARs, telemetry antennas, and other computer systems to transfer slaving data at a rate of 10 packets/sec over an Ethernet network.

Type Bytes Description

WFF Ethernet Fixed Header 16 Fixed header.

WFF Ethernet Standard Extended Header (Optional) 256 Standard header.

LTAS Frame 30f LTAS data Total Bytes 46 or 302

Table A.1. eLTAS Packet

WFF Ethernet Fixed Header The 16 byte Fixed Header consists of four 32-bit words containing information to correctly interpret the message. The Fixed header is required for all messages.

Field Type Bytes Description Units Values Example

Word Byte Ordering bytes; flag 4

Indicates the byte ordering of the computer on which the message originates. Used by the receiving system to correctly interpret the remaining message fields. N/A

{FFFFFFFFh = Least Significant Byte (LSB) first/Little Endian, 00000000h = Most Significant Byte (MSB) first/Big Endian} FFFFFFFFh

Extended Header Type unsigned integer;

enumeration 4

Indicates the presence and type of extended header that follows the fixed header. At a minimum a message will always contain the fixed header. An extended header may follow immediately after the fixed header. This field will indicate the type of the extended header so that it can be correctly interpreted. N/A

{0 = No extended header follows fixed header, 1 = Standard WFF Extended Header follows fixed header, 2 = Donna's Extended Header follows fixed header, 3 = SIPS Extended Header follows fixed header}

(00000001h)

Body Size unsigned integer; count 4

Contains a count of the number of bytes used in the message body. If the body is not blocked then this will be the total size of the body. If the body is blocked then this will be the total number of Bytes

(00000019h) bytes that contain data which may be smaller than the total body size if the last block is not completely filled.

Body Blocking Size unsigned integer; count 4

Indicates the size of blocks, in bytes, to be used for the message body. A block size should be a power of 2 for efficient processing. The size should be set such that one block will usually contain the type of data being placed within the body. The message body size must be a multiple of the block size. Bytes

[0 = No blocking ..

4294967295]

(00000020h)

Total Bytes 16

Table A.2. eLTAS 16 Byte Ethernet Header

WFF Ethernet Standard Extended Header The 256 byte Standard Extended Header is optional. If present it immediately follows the Fixed Header, and provides more detailed information regarding the message contents. The formats for the WFF Ethernet Address Field, WFF Ethernet ID Field, and WFF Ethernet Timestamp follow the Standard Extended Header Definition below.

Field Type Bytes Description Units Values Example

Source Address WFF Ethernet Address 96 Identifies the message sender. N/A

WFF,

AWOTS,

Master, 1, High, 0, 0

Destination Address WFF Ethernet Address 96

Identifies the message recipient. N/A

WFF,

AWOTS,

Recorder, 1, WrmDc, 0, 0

ID WFF Ethernet ID 44

Identifies the purpose and/or content of the message. N/A

AWOTS, 0,

4, 0, 65536, 0, 2, 0

Timestamp WFF Ethernet Timestamp 16 Identifies the time the message was created. N/A

1996, 320, 50400, 0

Spare byte 4 Reserved for future use. N/A 0 Total Bytes 256

Wallops Flight Facility Ethernet Address Field

The Address field identifies the sender or recipient of a message..

Field Type Bytes Description Units Values Example

Site Id character 16

Indicates the physical/geographical location of the sender/recipient (i.e.

WFF, PFRR). Null terminated. N/A WFF

System Name character 16

Indicates the name of the software system that produced the message (source) or the name of the software system that is to receive the message (destination) (i.e. AWOTS, RIR778).

Null terminated. N/A AWOTS

Logical Unit Name character 16

Indicates the name of the computer on which the above mentioned software system in running (i.e. N/A Recorder

Master1, Radar3). Null terminated.

Address Type unsigned integer;

enumeration 4

Indicates the type of address being specified in the next field (Box ID). N/A

{0 = Socket, 1 = Windows pipe} 1

Box Id character 32

Specifies the unique ‘port’ identifier on the computer system identified above (Logical Unit Name). The interpretation of the characters is determined by Address Type field.

Null terminated. N/A WRAM

Task Id unsigned integer 4

Process identifier of the task which created the message or to which the message is destined. N/A 0

Spares byte 8 Reserved for future use. N/A 0 Total Bytes 96

Wallops Flight Facility Ethernet ID Field

The ID field identifies purpose and/or contents of the message..

Field Type Bytes Description Units Values Example

Group character 16

Identifies a group to which the message belongs (i.e. AWOTS, RADAR). Null terminated. N/A AWOTS

Category unsigned integer;

enumeration 4

Identifies a category to which the message belongs (i.e. Command, Data, Status) N/A

{0 = Command, 1 = Data, 2 = Status}

0 (= Command)

Type unsigned integer;

enumeration 4 Application defined. N/A

{0 = Query, 1 = MDDF, 2 = LTAS, 3 = TIME, 4 = Execute}

4 (= Execute)

Unit unsigned integer;

enumeration 4 Application defined. N/A

0 (= not used)

Id integer 4 Application defined. N/A 65536

Is Certified Boolean 4 Indicates if an acknowledgement of receipt message is requested. N/A

{0 = No,1 = Yes} 0

Priority integer 4 Application defined number to define priority of message handling. N/A 2 (= normal)

Security Key bytes 4 N/A 0 (= not set) Total Bytes 44

Wallops Flight Facility Ethernet Time Stamp

The timestamp contains the time when the message was generated.

Field Type Bytes Description Units Values Example

Time Stamp Year unsigned integer 4

Year that the message was created; 4 digits. Years 1996

Time Stamp Day of Year unsigned integer 4

Day of the year that the message was created; 1 = January 1st. Days [1..366] 320

Time Stamp Total Seconds

GMT

unsigned integer 4

Time of day that the message was created;

seconds elapsed since midnight GMT. Seconds

[0..86399

50400 (= 2:00 pm)

Time Stamp Fractional Seconds unsigned integer 4

Fractional seconds in microseconds. Microseconds

[0..99999 9] 0

Time Stamp Total Seconds

GMT

unsigned integer 4

Time of day that the message was created;

seconds elapsed since midnight GMT. Seconds [0..86399]

50400 (= 2:00 pm)

Time Stamp Fractional Seconds unsigned integer 4

Fractional seconds in microseconds. Microseconds [0..999999] 0

Total Bytes 8

Table A.3. eLTAS 256 Byte WFF Ethernet Standard Extended Header

Launch Trajectory Acquisition System (LTAS)

The 30 Byte eLTAS data frame is transmitted Least Significant Bit (LSB) first *STDN 724 (now 450-TAH-STDN), Tracking and Acquisition Handbook for the Spaceflight Tracking and Data Network, October Field Type Bits Description Units Values Satellite ID Code binary value 13 Bits 1-13 N/A Vehicle ID Code binary value 4 Bits 14-17 N/A Day of Year binary count 9 Bits 18-26 Days Format Type binary value 4 Bits 27-30 N/A {0000 = LTAS} Time of Day - Tenths of Seconds binary count 4 Bits 31-34; LSB = 0.1 sec Tenths of seconds Time of Day – Seconds binary count 17 Bits 35-51; LSB = 1.0 sec Seconds Site ID binary value 9 Bits 52-60 N/A E-Position Component binary count 27 Bits 61-87 Meters

Sign for E- Position Component bit flag 1

Bit 88; indicates if E-position should be a positive or negative number; if negative then E-position will be 2's complement N/A

{0 = positive, 1= negative}

Position Scale Code (PSC) binary value 2

Bits 89-90; a scale code used to determine a value by which all position components should be multiplied if the field length is exceeded N/A

{00 = 1, 01 = 10, 10 = 10^3, 11 = 10^10}

F-Position Component binary count 27 Bits 91-117 Meters

Sign for F- Position Component bit flag 1

Bit 118; indicates if F-position should be a positive or negative number; if negative then F-position will be 2's complement N/A

{0 = positive, 1 = negative}

Velocity Scale Code (VSC) binary value 2

Bits 119-120; a scale code used to determine a value by which all N/A

{00 = 1, 01 = 10, 10 = invalid, 11 = invalid} velocity components should be multiplied if the field length is exceeded

G-Position Component binary count 27 Bits 121-147 Meters

Sign for G- Position Component bit flag 1

Bit 148; indicates if G-position should be a positive or negative number; if negative then G-position will be 2's complement N/A

{0 = positive, 1 = negative}

Optical Track Bit (OTB) bit flag 1 Bit 149; always 0 N/A {0} Plus Time Flag (PTF) bit flag 1 Bit 150 N/A {1 = using plus time} F-Velocity Component binary count 14 Bits 151-164 Meters/ second

Sign for F- Velocity Component bit flag 1

Bit 165; indicates if F-velocity should be a positive or negative number; if negative then F-velocity will be 2's complement N/A

{0 = positive, 1 = negative}

E-Velocity Component binary count 14 Bits 166-179 Meters/second

Sign for E- Velocity Component bit flag 1

Bit 180; indicates if E-velocity should be a positive or negative number; if negative then E-velocity will be 2's complement N/A

{0 = positive, 1 = negative}

Liftoff (L) bit flag 1 Bit 181 N/A {1 = liftoff has occurred} Plunge Mode

(P) bit flag 1 Bit 182 N/A {1 = plunge}

Pulse Width (P/W) binary value 2 Bit 183-184 N/A

{00 = 1.0 usec, 01 = 2.4 usec, 10 = 5.0 usec, 11 = 10.0 usec}

Refraction Correction (RFI) bit flag 1 Bit 185 N/A {0 = out, 1 = in} Droop (DI) bit flag 1 Bit 186 N/A {0 = out, 1 = in} Paramp (PO) bit flag 1 Bit 187 N/A {0 = off, 1 = on} Radiation (RO) bit flag 1 Bit 188 N/A {0 = off, 1 = on}

LO bit flag 1 Bit 189 N/A {0 = single LO, 1 = dual

LO}

Beacon/Skin (B/S) bit flag 1 Bit 190 N/A {0 = skin,1 = beacon} Track Bit (T) bit flag 1 Bit 191 N/A {0 = off, 1 = on} Quality Bit (Q) bit flag 1 Bit 192 N/A {0 = bad, 1 = good}

Mode binary value 3 Bits 193-195 N/A

Bits 193-194-195 0 00 = manual 100 = autotrack 010 = computer drive 110 = on-axis orbital 001= on-axis powered flight 101 = on-axis coast 011 = autotrack coast

G-Velocity Component binary count 14 Bits 196-209 Meters/ second

Sign for G- Velocity Component bit flag 1

Bit 210; indicates if G-velocity should be a positive or negative number; if negative then G-velocity will be 2's complement N/A

{0 = positive, 1 = negative}

Checksum binary value 7 Bits 211-217; Checksum algorithm:

a. The first 210 data bits are treated N/A as fourteen words of 15 bits each.

These words are summed, treating them as positive integers, in an accumulator capable of handling a 19-bit positive integer sum.

b. This sum is split up into three parts: the most significant 7 bits, the next most significant 6 bits, and the least significant 6 bits, and these three words are summed, treating them as positive integers, in an accumulator capable of handling an 8-bit positive integer sum.

c. The least significant 7 bits of these sums become the checksum.

Spares bits 7 Bits 218-224 N/A

Sync Bits binary value 16 Bits 225-240 N/A

Alternating hex 1A1A on one message, hex 1A05 on the next

Total Bytes 240

Table A.4. eLTAS 30 Byte LTAS Frame

Appendix B. NORAD Two Line Element (TLE) Set Format

Data for each satellite consists of three lines in the following format:

AAAAAAAAAAAAAAAAAAAAAAAA

1 NNNNNU NNNNNAAA NNNNN.NNNNNNNN +.NNNNNNNN +NNNNN‐N +NNNNN‐N N NNNNN

2 NNNNN NNN.NNNN NNN.NNNN NNNNNNN NNN.NNNN NNN.NNNN NN.NNNNNNNNNNNNNN

The first line is a twenty-four character name (to be consistent with the name length in the NORAD SATCAT).

The second and third lines are the standard Two-Line Orbital Element Set Format identical to that used by NORAD and NASA. Characters are designated as ‘A’, and numerals are designated as ‘N’. The format description is:

Line 1 Column Description

01 Line Number of Element Data

03-07 Satellite Number

08 Classification (U=Unclassified)

10-11 International Designator (Last two digits of launch year)

12-14 International Designator (Launch number of the year)

15-17 International Designator (Piece of the launch)

19-20 Epoch Year (Last two digits of year)

21-32 Epoch (Day of the year and fractional portion of the day)

34-43 First Time Derivative of the Mean Motion

45-52 Second Time Derivative of Mean Motion (Leading decimal point assumed)

54-61 BSTAR drag term (Leading decimal point assumed)

63 Ephemeris type

65-68 Element number

69 Checksum (Modulo 10) (Letters, blanks, periods, plus signs = 0; minus signs = 1)

Line 2

Column Description

01 Line Number of Element Data

03-07 Satellite Number

09-16 Inclination [Degrees]

18-25 Right Ascension of the Ascending Node [Degrees]

27-33 Eccentricity (Leading decimal point assumed)

35-42 Argument of Perigee [Degrees]

44-51 Mean Anomaly [Degrees]

53-63 Mean Motion [Revs per day]

64-68 Revolution number at epoch [Revs]

69 Checksum (Modulo 10)

All other columns are blank or fixed.

Example:

NOAA 14

1 23455U 94089A 97320.90946019 .00000140 00000‐0 10191‐3 0 2 23455 99.0090 272.6745 0008546 223.1686 136.8816 14.11711747148495

*Information from https://www.celestrak.com/NORAD/documentation/tle-fmt.php

Appendix C. Improved Inter-Range Vector Message Format

The Improved Inter-Range Vector (IIRV) contains state vector information that can be used to generate a spacecraft’s orbit.

Files can contain one or more IIRV messages consisting of 6 lines each. The format of IIRV messages are identical within a file with the exception that Items 1-4 (twelve bytes) appear only once in Line 1 of the first IIRV message.

Fields are contiguous and there are no spaces between fields on a line. All lines are terminated by two (2) carriage returns and two (2) line feeds. All values are in ASCII.

Table C.1 defines the format and description of the Improved Inter-Range Vector message.

Line Item Numbe r

Numbe r of bytes

Data Item Range of Values

1 1 2 Message Type 03 = Operations Data Message 2 7 Message

Identification A unique 7-character number used to reference this message

3 1 Message Source 0 = FDF 4 2 Message Class 10 = IIRV (nominal)

15 = IIRV (inflight update) 5 5 Message Start GIIRV (fixed) 6 1 Originator

Identification Alphabetic character that identifies the originator of message: ASCII Space =

GSFC

7 4 Routing Indicator NASCOM routing indicator, identifying the site from which the message was generated.

8-9 2 Carriage Returns Two carriage returns (ASCII) 10-11 2 Line Feeds Two Line feeds (ASCII)

2 12 1 Vector Type 1 = Routine on-orbit (free flight) 2 = Forced (special orbit update) 3 = Spare 4 = Maneuver ignition 5 = Maneuver cutoff 6 = Reentry 7 = Powered flight 8 = Stationary

13 1 Data Source 1 = Nominal/planning 2 = Real-time 3 = Off-line

14 1 Transfer Type 1 = Interrange 15 1 Coordinate System 1 = Geocentric true-of-date rotating 16 4 Support

Identification Code Mission specific

17 2 Vehicle Identification Code

18 3 Sequence Number Counter incremented for each vector in a r

Numbe r of bytes

Data Item Range of Values set of vector data 19 3 Day of year Day of year (001 = January 1) 20 9 Vector Epoch HHMMSSSSS in UTC with resolution to nearest millisecond (the implied decimal point is three places from the right)

21 3 Check Sum Sum of the decimal equivalent of the preceding characters for items 12-20 (right- justified), where:

0-9 = face value Minus = 1 ASCII Space = 0

22-23 2 Carriage Returns Two carriage returns (ASCII) 24-25 2 Line Feeds Two Line feeds (ASCII)

3 26 1 Sign Character ASCII space = Positive Minus sign = Negative

27 12 X Position X component of position* 28 1 Sign Character Same as Item 26 29 12 Y Position Y component of position* 30 1 Sign Character Same as Item 26 31 12 Z Position Z component of position* 32 3 Check Sum Sum of the decimal equivalent of the preceding characters for items 26-31 (right- justified), where:

0-9 = face value Minus = 1 ASCII Space = 0

33-34 2 Carriage Returns Two carriage returns (ASCII) 35-36 2 Line Feeds Two Line feeds (ASCII)

4 37 1 Sign Character Same as item 26 38 12 X Velocity X component of velocity** 39 1 Sign Character Same as item 26 40 12 Y Velocity Y component of velocity** 41 1 Sign Character Same as item 26 42 12 Z Velocity Z component of velocity** 43 3 Check Sum Sum of the decimal equivalent of the preceding characters for items 37-42 (right-justified) where:

0-9 = face value Minus = 1 ASCII Space = 0

44-45 2 Carriage Returns Two carriage returns (ASCII) 46-47 2 Line Feeds Two Line feeds (ASCII)

5 48 8 Mass Mass of spacecraft in kilograms with a resolution to the nearest tenth of a kilogram. The implied decimal point is one place from the right. Contains all zeros when not used.

r

Numbe r of bytes

Data Item Range of Values

49 5 Cross-sectional Area Average satellite cross-sectional area in square meters with a resolution to the nearest hundredth of a square meter.

The implied decimal point is two places from the right. Contains all zeros when not used.

50 4 Drag Dimensionless Drag coefficient. The implied decimal point is two places from the right. Contains all zeros when not used.

51 1 Sign Character Same as item 26 52 7 Coefficient of Solar

Reflectivity Dimensionless Solar Reflectivity coefficient. The implied decimal point is six places from the right. Contains all zeros when not used.

53 3 Check Sum Sum of the decimal equivalent of the preceding characters for items 48-52 (right- justified) where:

0-9 = face value Minus = 1 ASCII Space = 0

54-55 2 Carriage Returns Same as items 8-9 56-57 2 Line Feeds Same as items 10-11

6 58 5 End of Message Set to ITERM 59 1 Spare ASCII space 60 4 Originator Routing

Indicator Set to GCQU or GAQD

61-62 2 Carriage Returns Two carriage returns (ASCII) 63-64 2 Line Feeds Two Line feeds (ASCII)

7-12 5-64 184 Second IIRV if provided

Same as items 5-64 when the data block contains a second vector.

13-

5-64 184 Third IIRV if provided

Same as items 5-64 when the data block contains a third vector.

Etc. 5-64 184 nth IIRV if provided

Table C.1. Improved Inter-Range Vector Message Format

Appendix D. STARRS INP File Format

A Space Vehicle Radar Target Acquisition and Transmission Replacement System (STARRS) Internet Protocol (INP) message text file contains lines of time stamped (relative to T-0) vehicle azimuth, elevation, and range data samples. Lines are delimited by a <cr><lf>, and consist of ASCII characters formatted as follows:

MMSS*AAAAA*EEEE*RRRRRRRcrlf

The formatting rules for a sample line are as follows:

‐ M = minutes, S = seconds, A = azimuth, E = elevation, R = range ‐ Decimal points and colons are implied. The example line above is interpreted as

MM:SS*AAA.AA*EE.EE*RRRRR.RRR

‐ Numbers are referenced from the right with no leading zeroes. The format shown above indicates the maximum number of character that will be in a line sample.

For example, if elevation is .02 degrees, only one elevation character is present in the line. See examples below.

‐ Decimal point for azimuth and elevation is assumed to be two characters from the right

‐ Decimal point for range is assumed to be three characters from the right ‐ Negative sign for elevation is placed to the left of the numerical characters being used. See example 4 below.

Examples:

1. 30*32056*4578*125469crlf -> Time T+30sec AZ=320.56 EL=45.78 Slant Range 125.469 KM

2. 210*12076*3375*2345497crlf -> Time T+130sec AZ=120.76 EL=33.75 Slant Range 2345.497 KM

3. 500*3457*723*5347crlf -> Time T+300sec AZ=34.57 EL=7.23 Slant Range

5.347 KM

4. 8*30344*-23*1010878 -> Time T+ 8sec AZ = 303.44 EL = -.23 Slant Range

1010.878 km

5. 317*30332*4*999106 -> Time T+197 sec AZ = 303.32 EL = 0.04 Slant Range

999.106 km.

Appendix D. Internet Predict Message version 3 (INPv3) File Format

The INPv3 file is an ASCII text file containing predicted pointing data for a specific mission event at a specific antenna. The INPv3 always contains angle information, range information, range rate information, and additional range rate and delta range rate parameters with respect to the speed of light. The INP must contain at least 6 data points but has no upper limit to the number of points that can be contained in the file. All data points must have the correct checksum calculations. In computing the checksums, 0 through 9 have face value, the ampersand (&), denoting a positive sign, has a value of 10;

the minus (-), denoting a negative sign, has a value of 11. INPv3 files are issued as Ground Elapsed Time (GET) or Greenwich Mean Time (GMT). An INPv3 generated for GET has points for time elapsed since liftoff with the time for liftoff being considered 000 days, 00 hours, 00 minutes, 00 seconds. INPs generated with elapsed time are GET INPv3 files and an INPv3 generated with Real-Time are GMT. The complete format is shown in Table D.1.

Example:

XY1 AtlasV

$INP$ SET G0001, MIS 3332, SC 02, CH 01, STA KS1

SC XMT 0000.000000,SC RCV 0000.000000,STA XMT 00.000000,RG MOD

000000

SOP 18,290,041500 RTLT 00:00:00.0

LOS 18,290,042247 RTLT 00:00:00.0

GET AZI ELE CK R.KMS RR

RR.C DRR.C

000000 05200 &0007 24 0000074 &00.000000 &0.0000000000000 &0.000000000000000

000001 05200 &0007 24 0000074 &00.000000 &0.0000000000000 &0.000000000000000

000002 05200 &0009 26 0000074 -00.000807 -0.0000000026915 - 0.000000002691525

000003 05200 &0015 23 0000074 -00.000690 -0.0000000023028 &0.000000000388720

000745 09178 &0011 37 0017051 &61.085013 &0.0002037576712 &0.000000092523115

000746 09178 &0005 40 0017113 &61.116807 &0.0002038637243 &0.000000106053135

000747 09178 &0000 35 0017185 &72.649279 &0.0002423319102 &0.000038468185822

$END$ SET G0001, MIS 3332, SC 02, CH 01, STA KS1

INPv3 Line Formats

NOTE: All lines should end with <CR><CR><LF>.

< = Carriage Return <CR>

≡ = Line Feed <LF>

∆ = Space

Line1: sss∆vvvvv<<≡

Line2: $INP$∆SET∆annnn,∆MIS∆ssss,∆SC∆vv,∆CH∆cc,∆STA∆rii<<≡

Line3:

SC∆XMT∆ffff.ffffff,SC∆RCV∆gggg.gggggg,STA∆XMT∆hh.hhhhhh,RG∆MOD∆rrrrrr<<≡≡

Line4: eee∆yy,ddd,hhmmss∆∆∆RTLT∆rr:tt:vv.v<<≡

Line5: fff∆yy,ddd,hhmmss∆∆∆RTLT∆rr:tt:vv.v <<≡≡

Line6: ∆∆ttt∆∆∆aaaaa∆∆∆bbbbb∆∆CK∆∆R.rrrr∆∆∆RR∆∆∆RR.C∆∆∆DRR.C<<≡

Line7 to Line n-1:

hhmmss∆aaaaa∆bbbbb∆kk∆rrrrrrr∆&ttt.tttttt∆cc.ccccccccccccc∆dd.ddddddddddddddd<<≡

Line n: hhmmss∆aaaaa∆bbbbb∆kk∆rrrrrrr∆&ttt.tttttt∆cc.ccccccccccccc∆dd.ddddddddddddddd<<≡≡

Line n+1: $END$∆SET∆annnn,∆MIS∆ssss,∆SC∆vv,∆CH∆cc,∆STA∆rii<<≡

Important Notes:

There has to be a space after the satellite name even if no vehicle is specified

Points must be consistent within the file with no gaps (required for Doppler shifting)

$INP$ and $END$ Line Information must match

SOP is acceptable in place of AOS

There is no limitation on how many points can be specified

Line 1 Definition

Fixed Variable Explanation sss 3-Character Unique Satellite Name (Supplied by the NENSO) vvvvv Launch Vehicle Name

<<≡ Two carriage returns (OD16) followed by one line feed (OA16)

Line 2 Definition

$INP$ Start of message

SET

a Alphabetic character specifying generator of data:

G = FDF/RLT L = JPL E = ETR

S = FDF/NON-RLT P = PMR W = WTR

J = JSC K = KMR Z = WLP

nnnn Predict set number (message sequence number), consisting of four alphanumeric characters and necessary upper and lower case teletype shift characters

MIS Mission ssss SIC, consisting of four numeric characters, cannot be all zeros

SC Spacecraft vv VID, consisting of two numeric characters (refer to appendix D).

Cannot be 00

CH Channel cc Channel identification number 01-99 is defined as: Trajectory Identification Number 01-19 =ON ORBIT - SOURCE OR DESTINATION OF DATA where:

01 = pre-mission nominal (source) 00 = not used

02 = Real-Time (source) 20-79 = launch trajectory variations

03 = offline (source) 80-99 = entry and landing

STA Station r Alphabetic character indicating the range for which the message is generated:

A = CSTC K = KMR W = WTR

D = DSN P = PMR Z = WLP

E = ETR S = STDN

ii Tracker ID, 2 digit number, FDF’s NASA Directory of Station Locations (NDOSL) contains the Stations Tracker IDs.

Line 3 Definition

SC XMT Spacecraft transmit ffff.ffffff Spacecraft transmit frequency in MHz

SC RCV Spacecraft receive gggg.gggggg Spacecraft receive frequency in MHz

STA XMT Station transmission hh.hhhhhh Station transmission frequency in MHz

RG.MOD Range modules (ambiguities) rrrrrr Number of range modules subtracted from the range value

<<≡≡ Two carriage returns (OD16) followed by two line feeds (OA16)

Line 4 Definition eee Three alphabetic characters identifying the event used as the start of the message. Valid entries are:

AOS: Usually indicates horizon break.

SOP: (Start of Predicts); Indicates that the start of the INP does not correspond to a particular event.

EMG: (Emergence); Time of spacecraft coming out of occultation with a celestial body

CON: (Continuation); Used when message follows another INP which contains data points previous to these Used by DOD radars only yy,ddd,hhmmss UTC of the event described in eee field in 2 digit year, 3 digit day of year, 2 digit hours, 2 digit minutes, and 2 digit seconds.

RTLT Round Trip Light Time rr:tt:vv.v Round trip light time at time specified by yy,ddd,hhmmss field in 2 digit hours, 2 digit minutes, 2 digit seconds, and 1 digit tenths of seconds

Line 5 Definition fff Three alphabetic characters identifying the event used as the end of message. Valid entries are:

LOS: Loss of signal due to spacecraft going below station horizon

EOP: End of predicts indicates that the end of INP does not correspond to a particular event

OCC: Occultation predicts end due to spacecraft going behind a celestial body

TBC: Indicates that predicts to be continued in another INP Used by DOD radars only yy,ddd,hhmmss UTC of the event described in fff field in 2 digit year, 3 digit day of year, 2 digit hours, 2 digit minutes, and 2 digit seconds.

RTLT Round Trip Light Time rr:tt:vv.v Round trip light time at time specified by yy,ddd,hhmmss field in 2 digit hours, 2 digit minutes, 2 digit seconds, and 1 digit tenths of seconds

Line 6 Definition ttt Indicates: GET = Ground Elapsed Time

GMT = Greenwich Mean Time aaaaa Up to five alphanumeric characters indicating the coordinate system for angle 1. Valid entries are:

AZI

X30

X85 bbbbb Up to five alphanumeric characters indicating the coordinate system for angle 2. Valid entries are:

ELE

Y30

Y85

CK Checksum

R Range (optional) rrrr Up to four alphabetic characters with appropriate upper and lower case shift indicating the units for range field. Valid entries are:

KMS = kilometers

KYD = kiloyards

NMI = nautical miles

MCS = microseconds

RR Range Rate in Kilometers/Second (- is negative, & is positive), displayed as ttt.tttttt

RR.C Range Rate WRT Speed of Light in Kilometers/Second, displayed as cc.ccccccccccccc

DRR.C Delta Range Rate WRT Speed of Light in Kilometers/Second, displayed as dd.ddddddddddddddd

Line 7 to n-1 Definition hhmmss Six numeric characters specifying the UTC hours, minutes, and seconds of the point.

aaaaa Angle 1 value in 1/100 degree. Elevation (Interpreted as XX.XX, - is negative elevation, & is positive elevation). For X85 and X30, the first character is the sign of the angle where & (ampersand) indicates positive,

- (minus) indicates negative. For azimuth, signs are not required, zeros are used to fill unused character positions; e.g., 8.46 deg az = 00846, +

7.31 deg x = &0731 bbbbb Angle 2 value in 1/100 degree. Azimuth (Interpreted as XXX.XX). For ELE, Y85, and Y30, the first character is the sign of the angle where & (ampersand) indicates positive, - (minus) indicates negative. Zeros are used to fill unused character positions; e.g., 7.31 deg Y or EL = &0731

CK Checksum computed on digits in the aaaaa and bbbbb fields. 0 through 9 carry face value, (&) = 10 and (-) = 11 rrrrrrr Range (Interpreted as XXXXXX.X, in Kilometers ttt.tttttt Range Rate (In Kilometers/Second, - is negative, & is positive) cc.ccccccccccccc Range Rate WRT Speed of Light in Kilometers/Second dd.ddddddddddddd dd

Delta Range Rate WRT Speed of Light in Kilometers/Second

Line n Definition hhmmss Six numeric characters specifying the UTC hours, minutes, and seconds of the point.

aaaaa Angle 1 value in 1/100 degree. Elevation (Interpreted as XX.XX, - is negative elevation, & is positive elevation). For X85 and X30, the first character is the sign of the angle where & (ampersand) indicates positive,

- (minus) indicates negative. For azimuth, signs are not required, zeros are used to fill unused character positions; e.g., 8.46 deg az = 00846,

7.31 deg x = &0731 bbbbb Angle 2 value in 1/100 degree. Azimuth (Interpreted as XXX.XX). For ELE, Y85, and Y30, the first character is the sign of the angle where & (ampersand) indicates positive, - (minus) indicates negative. Zeros are used to fill unused character positions; e.g., 7.31 deg Y or EL = &0731

CK Checksum computed on digits in the aaaaa and bbbbb fields. 0 through 9 carry face value, (&) = 10 and (-) = 11 rrrrrrr Range (Interpreted as XXXXXX.X, in Kilometers ttt.tttttt Range Rate (In Kilometers/Second, - is negative, & is positive) cc.ccccccccccccc Range Rate WRT Speed of Light in Kilometers/Second dd.dddddddddddd ddd

Delta Range Rate WRT Speed of Light in Kilometers/Second

Line n+1 Definition

$ END $ Start of message

SET

a Alphabetic of data character specifying generator:

G = FDF/RLT L = JPL E = ETR

S = FDF/NON-RLT P = PMR W = WTR

J = JSC K = KMR Z = WLP

nnnn Predict set number (message sequence number), consisting of four alphanumeric characters and necessary upper and lower case teletype shift characters

MIS Mission ssss SIC, consisting of four numeric characters, cannot be all zeros

SC Spacecraft vv VID, consisting of two numeric characters (refer to appendix D). Cannot be 00

CH Channel cc Channel identification number 01-99 is defined as: Trajectory Identification Number 01-19 =ON ORBIT - SOURCE OR DESTINATION OF DATA where:

01 = pre-mission nominal (source) 01 = pre-mission nominal

(source) 02 = Real-Time (source) 02 = Real-Time (source)

03 = offline (source) 03 = offline (source)

STA Station r Alphabetic character indicating the range for which the message is generated:

A = CSTC A = CSTC A = CSTC

D = DSN D = DSN D = DSN

E = ETR E = ETR E = ETR

ii Tracker ID, 2 digit number, FDF’s NASA Directory of Station Locations (NDOSL) contains the Stations Tracker IDs.

Table D.1. INPv3 Message Format