Attachment E_Final.pdf

ATTACHMENT E

80GSFC25Q7005

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

GODDARD SPACE FLIGHT CENTER

WALLOPS FLIGHT FACILITY

WALLOPS ISLAND, VA 23337

36FC1-TECM-000012- WALLOPS RANGE DATA FORMATS

FOR

Small Aperture Mobile Telemetry Antenna System

LOCATED

AT

NASA GSFC/WALLOPS FLIGHT FACILITY

WALLOPS ISLAND, VIRGINIA

36FC1-TECM-000012-_

CHECK THE CENTRALIZED CONFIGURATION MANAGEMENT SYSTEM AT HTTPS://ROMS.WFF.NASA.GOV/ TO VERIFY

THAT THIS IS THE CORRECT VERSION PRIOR TO USE.

SUBORBITAL AND SPECIAL ORBITAL PROJECTS DIRECTORATE

Wallops Flight Facility

Range and Mission Management Office Wallops Range Data Formats

Revision: 1.1 Effective Date: 02/26/2025

Approved by: Bruce Underwood, Office Chief 802/Advanced Projects Office

National Aeronautics and Space Administration

Goddard Space Flight Center Wallops Flight Facility

Wallops Island, Virginia

Wallops Range Data Formats Document/Feb. 2025/36FC1-TECM-000012

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

CHANGE HISTORY LOG

Revision Effective Date Description of Changes

Draft 01 12/01/2022 Initial Draft by D. Parks

Draft 02 11/01/2023 Updates by D. Stanley

v. 1.0 04/01/2024 Initial Release

v. 1.1 02/26/2025

Editorial change in Table 2 to include bits 35-51 and associated description, as well as Table 8 to remove duplicate data. Addition of IIRV and TLE formats, as well as file name format for INPv3. Change of approver from Jeff Reddish to Joseph O’Brien

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

TABLE OF CONTENTS

1. OVERVIEW

1.1 SCOPE

1.2 RANGE SYSTEMS

1.2.1 RADAC

1.2.2 VTARS

1.2.3 Mission Graphics

1.2.4 Tracking Radars

1.2.5 Meteorological Operations (Met Ops) Wind Tower and Radiosonde Balloon Systems

2. ABBREVIATIONS AND ACRONYMNS

3. FORMATS

3.1 LAUNCH TRAJECTORY ACQUISITION SYSTEM (LTAS)

3.2 MINIMUM DELAY DATA FORMAT (MDDF)

3.3 ETHERNET LTAS AND MDDF (ELTAS AND EMDDF) FORMATS

3.4 RADAR MODES

3.5 STARRS INP FORMAT

3.6 INTERNET PREDICT MESSAGE VERSION 3 (INPV3) FILE FORMAT

3.7 IMPROVED INTER-RANGE VECTOR (IIRV) MESSAGE

3.8 NORAD TWO-LINE ELEMENT (TLE) SET FORMAT

3.9 ASCII TIME CODE FORMAT

3.10 NETWORK COUNTDOWN TIME PROTOCOL

3.11 NASA 36 TIME CODE FORMAT

3.12 IRIG-B TIME CODE

3.13 “PSEUDO” IRIG-B

3.14 WIND TOWER FORMAT (LEGACY)

3.16 730 FOOT WIND TOWER FORMAT

3.17 WW7 WIND TABLE FORMAT

3.18 MET BALLOON LEGACY TCP FORMAT

3.19 REAL TIME SERIAL OUTPUT (RTSO) FORMAT

3.20 RANGE AUXILIARY PROCESSOR SYSTEM (RAPS) TRAJECTORY FORMAT

3.21 RAPS II TRAJECTORY FORMAT

3.22 RADAC MISSION GRAPHICS BUFFER

3.23 VTARS MISSION GRAPHICS BUFFER FORMAT

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

List of Tables

TABLE 1 - LTAS FRAME CONTENTS

TABLE 2- MDDF FRAME CONTENTS

TABLE 3 - ELTAS/ EMDDF MESSAGE STRUCTURE

TABLE 4 - WFF ETHERNET FIXED HEADER

TABLE 5 - WFF ETHERNET STANDARD EXTENDED HEADER

TABLE 6 - WFF ETHERNET ADDRESS FIELD

TABLE 7 - WFF ETHERNET ID FIELD

TABLE 8 - WFF ETHERNET TIME STAMP

TABLE 9 - RADAR MODES

TABLE 10 - INP V3 FORMAT

TABLE 11 - INPV3 FILE NAME DEFINITION

TABLE 12 - IIRV ASCII TTY MESSAGE BODY EXPLANATION

TABLE 13 - IIRV FILE NAME FORMAT

TABLE 14 - TLE FORMAT LINE 1

TABLE 15 - TLE FORMAT LINE 2

TABLE 16 - ASCII TIME CODE FORMAT

TABLE 17 - NCTP DATA FRAME FORMAT

TABLE 18 - NCTP SOURCES AND PARAMETERS

TABLE 19 - NASA 36 TIME CODE STRUCTURE

TABLE 20 - NASA 36 TIME CODE BIT DEFINITIONS

TABLE 21 - IRIG - B TIME CODE STRUCTURE

TABLE 22 - IRIG-B BIT DEFINITIONS

TABLE 23 - "PSEUDO" IRIG-B BIT DEFINITIONS

TABLE 24 - WIND TOWER FORMAT

TABLE 25 - 730 FOOT WIND TOWER FORMAT

TABLE 26 - WIND TABLE HEADER AND LINE DESCRIPTION

TABLE 27 - WIND TABLE COLUMN DATA

TABLE 28 - MET BALLOON LEGACY TCP FORMAT

TABLE 29 - RTSO HEADER AND LINE DESCRIPTION

TABLE 30 - REAL TIME SERIAL OUTPUT (RTSO) SERIAL RECORD FORMAT

TABLE 31 - RAPS TRAJECTORY FORMAT

TABLE 32 - RAPS II TRAJECTORY FORMAT

TABLE 33 - RADAC MISSION GRAPHICS BUFFER FORMAT

TABLE 34 - VTARS MISSION GRAPHICS BUFFER FORMAT

List of Figures

FIGURE 1 – LTAS FORMAT CHART

FIGURE 2 - MDDF FRAME FORMAT

FIGURE 3 - IRIG-B MODULATION METHODS

FIGURE 4 - IRIG-B FRAME FORMAT

FIGURE 5 – “PSEUDO” IRIG-B FRAME FORMAT

FIGURE 6 - WIND TABLE EXAMPLE

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

This page intentionally kept blank.

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

1. OVERVIEW

1.1 Scope

The Wallops Range Data Formats document details data formats used by Wallops Range systems for receiving and sending data. These systems include tracking radars, and range data systems such as RADAC and VTARS. This data is used to provide both situational awareness and to make safety critical decisions.

1.2 Range Systems

The following descriptions provide a summary of the primary systems utilizing the formats in this document.

1.2.1 RADAC

The Range Data Acquisition Computer (RADAC) provides real-time processing of flight vehicle metric data for the Goddard Space Flight Center/Wallops Flight Facility (WFF) Range Control Center (RCC). Data quality personnel use the RADAC system to judge the quality of time, radar, and telemetry data. Range safety personnel base real-time flight termination decisions on RADAC vehicle state information and impact predictions. Additional WFF personnel and range customers use RADAC processed data to judge vehicle performance, identify recovery locations, test antenna instrumentation, and make real-time vehicle command decisions. The RADAC processes vehicle state information for aircraft, rockets, balloons, and satellites.

1.2.2 VTARS

The Vehicle Telemetry and Range Safety (VTARS) Data Processor is a NetAcquire F20 or H30 telemetry data processor. It ingests downlinked vehicle telemetry and decommutates selected range safety parameters as well as vehicle trajectory data. Additionally, it scales or translates these values as necessary, and places the scaled values into data packets/frames for output.

1.2.3 Mission Graphics

The Range Safety Mission Graphics computers provide real-time situational awareness of a vehicle's position and status to assess vehicle health and potential danger to the public. The Mission Graphics computers ingest vehicle tracking data from RADAC and display to Safety personnel overlayed with pre-determined hazard areas. The computers also ingest vehicle health information such as motor pressures and FTS status from VTARS which are displayed in alphanumeric and graphical form. The displayed information and calculations inform Range Safety personnel in making real-time flight termination decisions and any other relevant actions which need to be taken.

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

1.2.4 Tracking Radars

Wallops tracking radars have the capability to output 2 different types of data. Minimum Delay Data Format (MDDF) references data to the location of the radar system. Launch Trajectory Acquisition System (LTAS) data is referenced to the center of the earth. Radars can output either of these data types in 2400 baud synchronous serial or 10 PPS ethernet packets. A header (described in Section 3.3) is added to the ethernet packets.

1.2.5 Meteorological Operations (Met Ops) Wind Tower and Radiosonde Balloon Systems Wind speed and direction are needed to calculate launcher settings for sounding rockets accounting for wind-weighted trajectories. They are also used in ELVs for risk assessment by the Risk Assessment Center (RAC). Launch vehicle providers also use wind profile data to ensure their GNC solution will close out the trajectory given the current winds in the atmosphere. The two primary methods for acquiring a wind profile by altitude are wind towers and radiosonde balloons.

Wind towers provide a wind profile with speed and direction from the ground to the height of the tower. Radiosonde balloons use GPS to measure position and in turn calculate the wind direction and speed at specific altitudes. Where Wind towers provide a wind profile up to a few hundred feet above the ground, radiosonde balloons can provide a wind profile as high as 75,000 feet and higher.

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

2. ABBREVIATIONS AND ACRONYMNS

ASCII American Standard Code for Information Interchange CRC Cyclic Redundancy Code DQ Data Quality ECEF Earth Centered Earth Fixed ELTAS Ethernet Launch Trajectory Acquisition System EMDDF Ethernet Minimum Data Delay Format ETX End of Transmission GMT Greenwich Mean Time Hz Hertz ID Identification IIRV Improved Inter-Range Vector Message IRV Inter-Range Vector Message INP Internet Predict Message LTAS Launch Trajectory Acquisition System Met Ops Meteorological Operations MOCC Mission Operations Control Center MOVE Mission Operation Voice Enhancement NASA National Aeronautics and Space Administration NASCOM NASA (Ground) Communications System NCTP Network Countdown Time Protocol MDDF Minimum Data Delay Format PCDQS Personal Computer Data Quality System PCGDS Personal Computer Graphical Display System RAC Risk Assessment Center RAE Range, Azimuth, Elevation (position information) RAPS Radar Auxiliary Processor System RADAC Range Data Acquisition Computer RCC Range Control Center RTSO Real-Time Serial Output STARRS Space Vehicle Target Acquisition and

Transmission System TLE Two Line Element VTARS Vehicle Telemetry and Range Safety VTDS Video Timing Display System WFF Wallops Flight Facility WGS84 World Geodetic System 1984 (model)

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3. FORMATS

3.1 Launch Trajectory Acquisition System (LTAS)

The LTAS format provides an acquisition source originally for the Spaceflight Tracking and Data Network (STDN).

LTAS is composed of 240-bit blocks containing smoothed E, F, and G data. This data is transmitted Least Significant Bit (LSB) first at 2.4-kb/sec. In addition, 16 of the 240 bits contain a pattern which allows the on-station processors at LTAS-equipped stations to synchronize on the incoming LTAS data and use it as an acquisition source. This EFG coordinate system is Earth Centered Earth Fixed (ECEF), with the E component aligned with the Equator and zero longitude (prime meridian), F aligned with the Equator and +90° longitude and G aligned with Earth spin axis (north pole). This ECEF orientation is defined by the World Geodetic System (WGS) 1984 model, or WGS84.

Table 1 - LTAS Frame Contents Field Type Bits Description Units Values (LSB First)

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

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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

89 90

0 0 = 1

0 1 = 10

1 0 = 10^3

1 1 = 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 velocity components should be multiplied if the field length is exceeded

N/A

119 120

0 0 = 1

0 1 = 10

All other values = invalid

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}

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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

183 184

0 0 = 1.0 usec.

0 1 = 2.4 usec,.

1 0 = 5.0 usec.

1 1 = 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}

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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

193 194 195

0 0 0 = manual

1 0 0 = autotrack

0 1 0 = computer drive

1 1 0 = on-axis orbital

0 0 1 = on-axis powered flight

1 0 1 = on-axis coast

0 1 1 = 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}

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Checksum binary value 7

Bits 211-217; Checksum algorithm:

a. The first 210 data bits are treated 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.

N/A

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

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Figure 1 – LTAS Format Chart

30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0 0 0

60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31

90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61

Sign PSC: 00 - x1, 01 - x10, 10 - x10^3, 11 - x10^10

120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91

Sign VSC: 00 - x1, 01 - x

150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121

PTF OTB Sign OTB = Optical Track Bit (always 0) PTF = Plus Time Flag ("1" is plus time)

180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 sign sign

210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181

Sign Qual Track Beacon LO RO PO DI RI plunge Lift Bit Bit Skin mode Off

240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211

Satellite ID Code (binary)Vehicle ID Code (binary)Day of Year (binary)Format Type = LTAS

Pulse Width

Scale Code

Velocity F-position Component (meters) Scale Code

Time of Day Seconds (binary)Site ID (binary) (ref: STDN 724 Table C-2)

E-position Component (meters)Position

Time of Day 1/10 Seconds

G-position Component (meters)

F-velocity component (meters/second)E-velocity component (meters/second)

SYNC Bits toggle on alternate frames: 0101 1000 0101 1000 (5858H) then 1010 0000 0101 1000 (A058H) Spare Bits Checksum

G-velocity component (meters/second) Track Mode

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.2 Minimum Delay Data Format (MDDF)

The MDDF format provides a method for tracking radars to transmit tracking data.

MDDF is composed of 240-bit blocks containing raw (unsmoothed) range, azimuth, and elevation (RAE) data. Additional radar flags are incorporated including quality and tracking bits. This data is transmitted Least Significant Bit (LSB) first at 2.4-kb/sec. The frame ends with both a CRC and 16-bit sync pattern for receiving systems to synchronize with incoming data. RAE coordinates are referenced to the location of the tracking antenna indicated by the Site Identification.

Table 2- MDDF Frame Contents Bit Description (Values given LSB First) 1-13 Satellite ID Code (binary) 14-17 VID (binary) 18-26 Day of year (binary) 27-30 Format type (binary) 27 28 29 30

0 1 1 1

31-34 Time of day, tenths of second (binary) Bit

31 32 33 34

Value 0.1 0.2 0.4 0.8

35-51 Time of day, seconds (binary) Bit

35 36 51

Value 1 2 65536 52-60 Site Identification 61-79 Angle 1 (X or azimuth) (LSB = 0.0006866455) (binary) 80-98 Angle 2 (Y or elevation) (LSB = 0.0006866455) (binary) 99-123 Range (LSB = 1.7859375 m) (binary) 124-171 Doppler (counts of 240 MHz + 1000 fd) (LSB = 1 cycle)

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

172-173 One-, two-, or three-way data: 172 173 0 0 1-way

1 0 2-way

1 1 3-way 174 R/T (real/test) 1 = real data 175-176 Geo (antenna geometry): 175 176 0 0 az-el

1 0 X-Y (+X south)

1 1 X-Y (+X east) 177-180 Toggle bits: 177 178 179 180 On one frame: 1 0 1 1

On next frame: 0 1 0 0 181 Liftoff; 1 = liftoff has occurred 182 Plunge mode; 1 = plunge 183-184 Pulse width 183 184 0 0 1.0 µsec

1 0 2.4 µsec

0 1 5.0 µsec (0.25 sec for WFC radars)

1 1 10.0 µsec (0.5 sec for BDA and WFC radars) 185 RI refraction correction; 0 = out, 1 = in 186 DI droop; 0 = out, 1 = in 187 PO paramp; 0 = off, 1 = on

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

188 RO radiation; 0 = off, 1 = on 189 LO; 0 = single, 1 = dual LO 190 Beacon/Skin 0 = skin, 1 = beacon 191 Track bit 0 = off, 1 = on The track bit is present under the following conditions (or equivalent):

a. All three servos are in auto mode, i.e. have no designation/acquisition source (including manual) selected.

b. Radiation on.

c. ADRAN/DIRAM range verified.

d. Angle control ADRAN/DIRAM (not autotrack).

e. ADRAN/DIRAM not coast.

192 Quality bit; 0 = bad, 1 = good Q-Bit on corresponds to a 6dB or greater signal-to-noise ration plus a valid on-track bit.

193-195 Mode: 193 194 195 0 0 0 Manual

1 0 0 Autotrack 0 1 0 computer drive 1 1 0 on-axis orbital 0 0 1 on-axis powered flight 1 0 1 on-axis coast 0 1 1 autotrack coast

196 Range 1 = range good, 0 = range bad 197 Angles 1 = angles good, 0 = angles bad 198 Doppler 1 = Doppler good, 0 = doppler bad 199 Destruct Doppler 1 = destruct Doppler

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

200 Last frame indicator 1 = last frame 201-224 Cyclic Redundancy Code 225-240 Sync bits will have the following pattern (starting with bit 225): 0-0-0-1-1-0-1-0-0-0-0-1-1-0-1-0

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Figure 2 - MDDF Frame Format

30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 1 1 1

60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31

90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61

120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91

150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121

180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151

R/T (real)

210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 1 1

LFI DD Dop A R Q T B/S LO RO PO DI RI Pulse-Width plunge L/O 1, 2.4, 5, 10 µsec

240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 0 0 0 1 1 0 1 0 0 0 0 1 1 0 1 0

RangeDoppler (counts of 240 MHz + 1000 fd) (LSB = 1 cycle)

Time of Day (binary seconds)Site ID (binary) (ref: STDN 724 Table C-2)

Angle 1 (X or Azimuth) (LSB = .0006866455) (binary)Angle 2 (Y or elevation) (LSB = .0006866455) (binary)

Time of Day (binary .1 sec)

Angle 2Range (LSB = 1.7859375 meters) (binary)

SIC (binary)VID (binary)Day of Year (binary)Format Type

Cyclic Redundancy CodeSync Bits

Doppler (counts of 240 MHz + 1000 fd) (LSB = 1 cycle)1-, 2-, or 3-

ModeCyclic Redundancy Code way data Ant Geom az-el or x-y

Toggle Bits

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.3 Ethernet LTAS and MDDF (eLTAS and eMDDF) Formats

Ethernet LTAS and MDDF transitions the formats from serial line transmission to Ethernet. It consists of wrapping the LTAS or MDDF frame into a packet which includes a WFF Ethernet Fixed header and an optional WFF Ethernet Standard Extended Header. The eLTAS and eMDDF packets can be sent over 10/100/1000BaseT Ethernet, with an interval of one frame every 0.1 seconds. Both headers were developed by WFF and the formats described below.

Table 3 - eLTAS/ eMDDF Message Structure Wallops Flight Facility Ethernet Standard ELTAS or EMDDF Message

The WFF Ethernet Standard LTAS or MDDF Message is generated by radars, telemetry antennas, and other computer systems to transfer frames over the Ethernet network.

Field Type Bytes Description Fixed Header WFF Ethernet Fixed Header 16 Fixed header Standard Header WFF Ethernet Standard Extended Header 256 Standard header Data Frame LTAS or MDDF Frame 30 LTAS data or MDDF data Total 302

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 4 - WFF Ethernet Fixed Header

Wallops Flight Facility Ethernet Fixed Header The Fixed Header is four 32-bit words that provide a minimal amount of information so that a message can be correctly interpreted. The Fixed Header is required on all messages.

Field Type Bytes Description Units Values Example (MSB first) 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}

1 (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 that contain data which may be smaller than the total body size if the last block is not completely filled.

Bytes

25 (00000019h)

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]

32 (00000020h)

Total 16

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 5 - WFF Ethernet Standard Extended Header

Wallops Flight Facility Ethernet Standard Extended Header The Standard Extended Header is optional. If present it immediately follows the Fixed Header. It provides more detailed information about the contents of the message. The format of a message body is also defined by an application and can be designed to be determined based upon the header information.

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 256

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 6 - WFF Ethernet Address Field

Wallops Flight Facility Ethernet Address Field The Address field identifies the sender or recipient of a message. The inclusion of this information within a message allows separate software to handle the transmission and reception of messages independent of the software that composes messages. By identifying the source of a message, the receiving system can reply to messages if necessary. This information can be useful for logging purposes. The address is contained in the Standard Extended Header.

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. Master1, Radar3). Null terminated.

Recorder

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.

WRAM

Task Id unsigned integer 4 Process identifier of the task which created the message or to which the message is destined. N/A

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

Total 96

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 7 - WFF Ethernet ID Field

Wallops Flight Facility Ethernet ID Field The ID field identifies purpose and/or contents of the message. The Group, Category, Type, Unit, and ID fields are generic and may be used by a software system to identify the purpose and/or contents of the message. It is intended that each field narrows the scope of the message.

The Group field is character based allowing it to be interpreted outside of the context of a particular software system. The Category, Type, and Unit fields are enumerated to allow rapid processing using switch statements. An application would only have to use the fields it needed and could leave the others blank.

Field Type Bytes Description Units Values Example Group character 16 Identifies a group to which the message belongs (i.e. AWOTS, RADAR).

Null terminated.

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 44

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 8 - WFF Ethernet Time Stamp

Wallops Flight Facility Ethernet Time Stamp

The timestamp field is used to timestamp a message.

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. μ seconds [0..999999] 0

Total 16

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.4 Radar Modes

The Wallops Tracking Radars operate in several modes, which are defined by the setting of specific Mode Bits and operating in a distinct tracking configuration. The radar modes are defined below with their specific characteristics.

Table 9 - Radar Modes

Radar Mode Operator Action "T" Bit

(on/off)

"Q" Bit

(on/off)

Mode Bit

(on/off)

Mode Bit

(on/off)

Mode Bit 195 (on/off)

Ethernet (eMDDF)

Track Status

(SLV

Mode) Displayed

(loop back)

General Status

(Mode) Displayed

Notes:

Manual Master Manual (Baseline test) TX = off off off off off Same as serial Manual Manual

Transmitter = Ready Servo power = off Range gate = first interval

Autotrack

Master Auto (Transmitter off test) TX = off off off off off Same as serial Auto RF Auto

Mode change = MM to

MA,

transmitter = ready (no

RAD)

Range gate = First interval

Autotrack Master Auto (Transmitter on test) TX = on on on off off Same as serial Auto RF Auto

Transmitter = Radiate on Range gate = First interval

Autotrack

Master Auto (Interval test) Interval = 2nd on on off off Same as serial Auto RF Auto

Moved range to second interval No "Range Verify" needed

Manual Master Auto (Manual AZ Only Test) off off off off Same as serial Manual Blank Kept Range = Auto Kept EL = Auto Changed AZ = Manual

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

"T" Bit

(on/off)

"Q" Bit

(on/off)

Mode Bit

(on/off)

Mode Bit

(on/off)

Mode Bit 195 (on/off)

Ethernet (eMDDF)

Track Status

(SLV

Mode) Displayed

(loop back)

General Status

(Mode) Displayed

Notes:

Manual Master Auto (Manual EL Only Test) off off off off Same as serial Manual Blank Kept Range = Auto Kept AZ = Auto Changed EL = Manual

Computer Drive

Remote Designate (Baseline test) off off on off Same as serial Comp DRV Remote

Range = Designate AZ = Designate EL = Designate

Computer Drive

Remote Designate (INP test) off off off on off Same as serial Comp DRV Remote

Slaved to INP Range = Designate AZ = Designate EL = Designate

On-axis powered flight

On-Axis Track (Baseline test) on on off off on Same as serial OAT TV Vector OAT selected AZ = Designate EL = Designate

On-Axis Track (Coast test)

Coast is not available in

OAT

"on-axis coast" unachievable

Autotrack Coast

Coast (Baseline tset) Must be in MA first off off off on on Same as serial Auto CST Coast

Range, AZ and EL = coast A-scope = Range gate opens Buttons: MA = lit, OAT = lit Angle BWs = forced to

BW5

Computer Drive

TV Track (Baseline test) Must have range locked on on off on off Same as serial Auto TV TV Track

Remains in manual until range is locked

Autotrack Track "T" Forced (baseline test) on off on off off Same as serial Auto RF Manual Mode = Master Manual Track button = on Quality button = off

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

"T" Bit

(on/off)

"Q" Bit

(on/off)

Mode Bit

(on/off)

Mode Bit

(on/off)

Mode Bit 195 (on/off)

Ethernet (eMDDF)

Track Status

(SLV

Mode) Displayed

(loop back)

General Status

(Mode) Displayed

Notes:

Autotrack Quality "Q" Forced (baseline test) Must have T bit on on on on off off Same as serial Auto RF Manual

Mode = Master Manual Track button = on Quality button = on

Autotrack

Master Auto & T & Q (all on test) on on off off Same as serial Auto RF Auto

Range, AZ & EL = Master Auto Track Button = on Quality Button = on

Manual

Manual and T & Q (T & Q disable test) off off off off off Same as serial Manual Manual

Start in Master Auto with T/Q Select Master Manual MM = T/Q turn off No other modes turn off T/Q

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.5 STARRS INP Format

The STARRS Internet Predict (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 (RAE coordinates are referenced to the tracking antenna)

- 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 characters 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 the example on Line 4 below.

Examples:

Line Time Azimuth (Deg.) Elevation (Deg.) Slant Range (Km)

30*32056*4578*125469<cr><lf> T+30 sec. 320.56 45.78 125.469

210*12076*3375*2345497<cr><lf> T+130 sec. 120.76 33.75 2345.497

500*3457*723*5347<cr><lf> T+300 sec. 34.57 7.23 5.347

8*30344*-23*1010878<cr><lf> T+ 8 sec. 303.44 -.23 1010.878

317*30332*4*999106<cr><lf> T+197 sec. 303.32 0.04 999.106

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.6 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. RAE coordinates incorporated are referenced to the tracking antenna.

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

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

Table 10 - INP v3 Format

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

Fixed Variable Explanation $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 (refer to appendix D).

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) 03 = offline (source) 20-79 = launch trajectory variations 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.

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

<<≡ Two carriage returns (OD 16) followed by one line feed

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

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:

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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

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

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

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

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, Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

- (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

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

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. 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) 02 = Real-Time (source)

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

03 = offline (source) STA Station r

Alphabetic character indicating the range for which the message is generated:

A = CSTC

D = DSN

E = ETR

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

The file name is defined as follows:

STAS_SIC_SAT_YYYYDDD_CASE.Extension

Where the fields are as described in the following table:

Table 11 - INPv3 File Name Definition

Field Length Definition Station

(STAS)

4 The Station identifier is 4 characters used to represent the station supporting the mission. This should consist of the NENSS 3-character Station ID (IE:

KS1, PD1, or BD1) plus a static “S” character to fill out the 4-character file identifier (IE: KS1S, PD1S, or BD1S)

(separator) 1 An underscore character separates Station from SIC.

SIC 4 Support Identification Code (SIC) is the 4 numeric digits used to represent the spacecraft.

(separator) 1 An underscore character separates SIC from SAT.

SAT 3 A 3-Character Unique Satellite name (Supplied by NENSO) (separator) 1 An underscore character separates SAT from Date.

Date

(YYYYDDD)

7 Start date of the first station acquisition (UTC), in the form YYYYDDD, where YYYY is the 4-digit year, and DDD is the day of year (001 to 366).

(separator) 1 An underscore character separates Date from CASE.

CASE 3 A 3 digit case number (formerly defined as trajectory identification number and channel number). The initial version is 01, the next is 02, up to 99.

Example of case numbering:

01-19 =ON ORBIT - SOURCE OR DESTINATION OF DATA

Where: 01 = permission nominal (source) 02 = Real-Time (source) 03 = offline (source) 00 = not used 20-79 = launch trajectory variations 80-99 = entry and landing

(separator) 1 A period character separates CASE from Extension.

Extension 3 inp to represent the format of the data product being sent.

Check the website at: https://roms.wff.nasa.gov to verify that this is the most recent version of this document.

3.7 Improved Inter-Range Vector (IIRV) Message

The Improved Inter-Range Vector Message contains state vector information that can be used to generate a spacecraft’s orbit. The files are in ASCII and may be used to compute pointing angle information for a known antenna location.

The message contains six lines, with each line terminated by two (2) carriage returns followed by two (2) line feeds. There are no spaces between fields on a line. All data fields are right justified, with leading zeros added as needed. A positive sign (+) is indicated by an ASCII space, and a negative sign is indicated by a minus (-). Multiple messages may be placed in the same file, the next message starting on the line after the previous message.

Checksums are provided for each of the position and velocity components and epoch time. In computing these checksums, 0 through 9 have face value; the ampersand (&), used to denote a positive sign, has a value of zero; and the minus (-), used to denote a negative sign, has a value of 1.

Although no parity checks are made on individual characters at Goddard Space Flight Center (GSFC), parity may be required for message switching between NASCOM and other communications networks. The IIRV format is also used for inter-center exchange of acquisition data in NASCOM 4800-bit blocks.

The message body format is summarized below, followed by a more detailed description of each line. On the first line the parameters preceding “GIIRV” are optional.