snebulos.mit.edu...431-ICD-000049 Revision -– A Effective Date: TBD Expiration Date: TBD CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRI

431-ICD-000049Revision -– A

Effective Date: TBDExpiration Date: TBD

CHECK WITH RLEP DATABASE AT:https://lunarngin.gsfc.nasa.gov

TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.

Lunar Precursor and Robotic Program (LPRP)Lunar Reconnaissance Orbiter Project

External Systems Interface Control Document for theLunar Reconnaissance Ground System

December 20, 2006February 20, 2007

Goddard Space Flight CenterGreenbelt, Maryland

National Aeronautics andSpace Administration

pgf

Note

CRaTER ISOC REVIEW ----------------- Reviewed by Robert Goeke (RFG) 3/28/07 Reviewed by Peter Ford (PGF) 3/29/07 Bookmark color code: black - major document sections blue-green - CRaTER-specific sections red - comments, notes and edits

LRO (LPRP) Ext. Sys. ICD for (LRGS) 431-ICD-000049Revision -– A



CM FOREWORD

This document is a Lunar Reconnaissance Orbiter (LRO) Project Configuration Management(CM)-controlled document. Changes to this document require prior approval of the applicableConfiguration Control Board (CCB) Chairperson or designee. Proposed changes shall besubmitted to the LRO CM Office (CMO), along with supportive material justifying the proposedchange. Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

LRO Configuration Management OfficeMail Stop 451Goddard Space Flight CenterGreenbelt, Maryland 20771




Signature Page

Prepared by: Reviewed by:

_________Ralph Casasanta DateLRO Ground System EngineerCode 444

________Jim Clapsadle. DateLRO Ground System EngineerCode 444

Reviewed by:

________Jack Murphy. DateLRO Mission Operations LeadCode 444

________Ron Zellar DateLR System EngineerGSFC/NASA, Code 556

________Mark BeckmanRivers Lamb. DateLRO Flight Dynamics LeadCode 595

________Sue Hoge. DateFlight Dynamics Facility Operations DirectorCode 595

________Stefan Waldherr. DateJPL, Telecommunications and MissionServices Manager, Office 911

________Cathy Barclay DateHTSI, Code 452NENS – White Sands Station

________Michael Kohout DateHTSI, Code 452NENS – Space Network

________Donald Gittle DateUniversal Space Network

Approved by:

________Richard S Saylor, Jr. DateLRO Ground System LeadCode 444







Signature Page (Continued)

Reviewed by:

________Dr. Peter G. Ford DateCRaTER Science ManagerMassachusetts Institute of Technology

________Charles Avis DateDLRE Science ManagerJet Propulsion Laboratory

________Joel Parker DateDepartment of Space StudiesSouthwest Research Institute

________Dr Karl Harshman DateLEND Co-InvestigatorGSFC, Code 691

________Dr. Gregory Neumann DateLOLA Co-InvestigatorGSFC, Code 698

________Ernest Bowman-Cisneros DateLROC SOC ManagerArizona State University

________Helene Winters DateMini-RF Science ManagerJohns Hopkins – Applied Research LaboratoryApproved by:

________Richard S Saylor, Jr. DateLRO Ground System and Operations LeadCode 444

pgf

Highlight

CRaTER signature




LUNAR RECONNAISSANCE ORBITER PROJECT

DOCUMENT CHANGE RECORD Sheet: 1 of 1REV

LEVEL DESCRIPTION OF CHANGE APPROVEDBY

DATEAPPROVED

Rev - Initial Release, Released per 431-CCR-000210 R. Saylor 19 Jan 2007

Rev – A 451-CCR-000383:(Provides these updates, at a minimum):

Updates to consolidate MOC-generated SOC products, such as Real-time HK data, Instrument Measurement Files, etc

Added newly identified WS1-MOC Products for Meta Summary Reports for science instrument files

Moved several MOC-ADS Products to Internal ICDIdentified other MOC-ADS products as MOC productsUpdates not originally included in initial releaseMinor style changes (grammer and spell checks)Identified changes as documented in file ICD-000049 Rev A

Updates (an Excel spreadsheet)

R. Saylor




List of TBDs/TBRs

ItemNo.

Location Type Summary Ind./Org. Due Date

1 Section 1.4 TBDIdentify relevant document titleand CM number (if any) for theDSN SPS

Ralph Casasanta/444 GSSDRMOR

2 Table 3-1 TBRProvide correct DMR referencesand trace concepts for all externalproducts identified in the table


3 Table 4-1 TBR Provide product information forfile sizes Ralph Casasanta/444 GS

SDRMOR

4 Section 4 TBR

Provide product accuracyinformation, as noted for each ofthe approximately 135 productslistedThis is referenced by Sections4.x.y.4 and 4.x.y.z.4


5 Section 4 TBSProvide correct file name conceptsfor each of the external productslisted in this section


6 Section 4 TBRIdentify File Formats for productsthat have not yet been totallydefined

Ralph Casasanta/444Other Groups, asidentified

GSSDRMOR

7Section4.1.2.11 TBD

Identify LRO Thruster maneuvermodeling tool, which will factorinto the creation of the sampleProduct

Mark Beckman/FDF GSSDRMOR

8 Section 4.2 TBS

Provide telemetry headerstructures for SLE Interface withDSN and for Space Networktelemetry interfaces

Ralph Casasanta/444SN and DSN reps

GSSDRMOR

9 Section 4.4.3 TBS Provide Command structure andformation for interface with SN

Ralph Casasanta/444and SN (BobGonzales)

GSSDRMOR

10 Section 4.4.3 TBS Supply SLE F-CLTU Format andfield definitions for this interface Ralph Casasanta/444 GS

SDRMOR

11 Appendix B TBS

Provide Sample products, as listedin AppendixAdditionally, remove productcallouts for those binary products(R/T telemetry streams, files orstation status, which are definedby APIDs in T&C Handbook



ii



TABLE OF CONTENTS

Page1.0 INTRODUCTION......................................................................................................................................... 1-1

1.1 PURPOSE AND SCOPE ................................................................................................................................. 1-11.2 DOCUMENT ORGANIZATION..................................................................................................................... 1-11.3 REQUIREMENTS TRACEABILITY METHODOLOGY ................................................................................ 1-11.4 APPLICABLE DOCUMENTS......................................................................................................................... 1-11.5 REFERENCED DOCUMENTS ....................................................................................................................... 1-21.6 OTHER DOCUMENTED REFERENCES ....................................................................................................... 1-2

2.0 GROUND SYSTEM OVERVIEW........................................................................................................... 2-1

2.1 GROUND SYSTEM ARCHITECTURE .......................................................................................................... 2-22.1.1 The LRO Space Communications Network....................................................................................... 2-32.1.2 LRO Mission Operations Center ........................................................................................................ 2-42.1.3 The Science Operations Centers......................................................................................................... 2-42.1.4 Flight Dynamics Facility...................................................................................................................... 2-52.1.5 Ground System Communications........................................................................................................ 2-5

2.2 LRO OPERATIONAL GROUND SYSTEM .................................................................................................. 2-72.2.1 ITOS-Supported Real-time Telemetry and Commanding............................................................... 2-72.2.2 Data Processing System ....................................................................................................................... 2-82.2.3 Data Management System.................................................................................................................... 2-82.2.4 Mission Planning System...................................................................................................................... 2-82.2.5 Mission Operations Center – Attitude Determination System ...................................................... 2-92.2.6 Trending and Analysis System............................................................................................................. 2-92.2.7 Monitoring and Alert System............................................................................................................... 2-9

2.3 FLIGHT DYNAMICS FACILITY ................................................................................................................... 2-92.4 MISSION OPERATIONS TEAM.................................................................................................................. 2-102.5 FLIGHT SOFTWARE MAINTENANCE FACILITY .................................................................................... 2-102.6 LRO SPACE COMMUNICATIONS NETWORK ........................................................................................ 2-10

3.0 LRO GS EXTERNAL INTERFACE PRODUCT SYNOPSIS........................................................ 3-1

4.0 LRO GROUND SYSTEM EXTERNAL INTERFACES AND PRODUCT................................ 4-1

4.1 FLIGHT DYNAMICS FACILITY PRODUCTS ............................................................................................ 4-254.1.1 FDF Products for Network Support................................................................................................. 4-26

4.1.1.1 (FDF-6) SCN Station Acquisition Data .......................................................................................... 4-264.1.1.2 (FDF-5) DSN Site Acquisition Data ................................................................................................ 4-284.1.1.3 (FDF-7) Laser Ranging Site Prediction Data................................................................................ 4-294.1.1.4 (FDF-8) Space Network Acquisition Data..................................................................................... 4-31

4.1.2 FDF Products to support MOC Functions ..................................................................................... 4-344.1.2.1 (FDF-9, FDF-10) Ground Station View Period Predicts File (HGA and Omni ViewPeriods) 4-354.1.2.2 (FDF-3) LRO Beta Angle Predict File ............................................................................................ 4-374.1.2.3 (FDF-4) LRO Definitive Ephemeris File........................................................................................ 4-384.1.2.4 (FDF-29) LRO Definitive SPICE SPK File .................................................................................. 4-39


iii



4.1.2.5 (FDF-30) LRO Predictive SPICE SPK File .................................................................................. 4-404.1.2.6 (FDF-13) Lunar Orbit Ascending and Descending Node Predicts ....................................... 4-404.1.2.7 (FDF-14) Lunar Orbit Terminator Crossing Predicts ................................................................ 4-414.1.2.8 (FDF-15) Mission Eclipse Predicts................................................................................................... 4-424.1.2.9 (FDF-16) Lunar Ephemeris.................................................................................................................. 4-434.1.2.10 (FDF-23) LRO State Vector Table ................................................................................................... 4-454.1.2.11 (FDF-17) Orbiter Thruster Maneuver Plans.................................................................................. 4-464.1.2.12 (FDF-19) Orbiter Post Maneuver Report........................................................................................ 4-474.1.2.13 (FDF-18) Post Separation Report ...................................................................................................... 4-494.1.2.14 (FDF-20) Predicted LRO Ephemeris File ...................................................................................... 4-524.1.2.15 (FDF-21) Predicted Lunar Ground Track File.............................................................................. 4-534.1.2.16 (FDF-22) Definitive Lunar Ground Track File ............................................................................ 4-544.1.2.17 (FDF-32) SPICE Generic PCK (Planetary Constants) .............................................................. 4-554.1.2.18 (FDF-33) SPICE Binary PCK (High-Precision Lunar Orientation)..................................... 4-55

4.1.3 FDF MOC/ADS Products .................................................................................................................. 4-564.1.3.1 (FDF-1) Attitude Determination Verification Report................................................................ 4-564.1.3.2 (FDF-2) Attitude Slew Plans ............................................................................................................... 4-564.1.3.3 (FDF-11) Gyro Calibration Data........................................................................................................ 4-574.1.3.4 (FDF-12) HGA Calibration Data....................................................................................................... 4-584.1.3.5 (FDF-24) Star Tracker Calibration Data......................................................................................... 4-584.1.3.6 (FDF-25) Thruster Calibration Data................................................................................................. 4-594.1.3.7 (FDF-26) LRO Momentum Management Unload Plan ............................................................ 4-594.1.3.8 (FDF-27) Star Tracker Occultation Report.................................................................................... 4-604.1.3.9 (FDF-34) SPICE Predicted CK (Predicted S/C Orientation) .................................................. 4-614.1.3.10 (FDF-35) SPICE Definitive CK (Definitive S/C, HGA, SA Orientation) ......................... 4-614.1.3.11 (FDF-31) HGA/SA Fixed offset SPK.............................................................................................. 4-62

4.2 STATION PRODUCTS AND DESCRIPTIONS ....................................................................................... 4-634.2.1 Space Communication Network (WS1) Product Descriptions.................................................... 4-66

4.2.1.1 SCN Support Schedules ........................................................................................................................ 4-664.2.1.2 SCN Support Schedule Report ........................................................................................................... 4-684.2.1.3 WS1 Raw Tracking Data ...................................................................................................................... 4-704.2.1.4 Archived VC0 Telemetry Data........................................................................................................... 4-734.2.1.5 Archived VC1 Telemetry Data........................................................................................................... 4-744.2.1.6 Archived VC2 Telemetry Data........................................................................................................... 4-754.2.1.7 Archived VC3 Telemetry Data........................................................................................................... 4-764.2.1.8 Real-time VC0 Telemetry Data.......................................................................................................... 4-764.2.1.9 Real-time VC1 Telemetry Data.......................................................................................................... 4-774.2.1.10 WS1 Station Status Packets ................................................................................................................. 4-784.2.1.11 WS1 Weather Data.................................................................................................................................. 4-784.2.1.12 Ka-Band VC3 Telemetry ...................................................................................................................... 4-804.2.1.13 Ka-Band VC2 Telemetry ...................................................................................................................... 4-814.2.1.14 Ka-Band RF Receiver Data.................................................................................................................. 4-814.2.1.15 SDPS CFDP Status Packets................................................................................................................. 4-824.2.1.16 VC2 Housekeeping Telemetry Files................................................................................................. 4-834.2.1.17 VC2 FSW Telemetry Files................................................................................................................... 4-834.2.1.18 VC3 Measurement Telemetry Files.................................................................................................. 4-844.2.1.19 Event Logs.................................................................................................................................................. 4-84


iv



4.2.1.20 System Logs............................................................................................................................................... 4-854.2.2 Universal Space Network Product Descriptions ........................................................................... 4-85

4.2.2.1 USN Raw Tracking Data ...................................................................................................................... 4-854.2.2.2 USN Station Status Packets ................................................................................................................. 4-864.2.2.3 USN Weather Data.................................................................................................................................. 4-874.2.2.4 Real-time VC0 Telemetry Data.......................................................................................................... 4-894.2.2.5 Real-time VC1 Telemetry Data.......................................................................................................... 4-894.2.2.6 Archived VC0 Telemetry Data........................................................................................................... 4-904.2.2.7 Archived VC1 Telemetry Data........................................................................................................... 4-91

4.2.3 Deep Space Network Product Descriptions.................................................................................... 4-924.2.3.1 DSN Tracking Data................................................................................................................................. 4-924.2.3.2 Real-time VC0 Telemetry Data.......................................................................................................... 4-924.2.3.3 Archived VC0 Telemetry Data........................................................................................................... 4-934.2.3.4 Archived VC1 Telemetry Data........................................................................................................... 4-944.2.3.5 Real-Time VC1 Telemetry Data ........................................................................................................ 4-944.2.3.6 DSN Station Status Packets ................................................................................................................. 4-95

4.2.4 Laser Ranging Product Description ................................................................................................ 4-964.2.4.1 Weekly Laser Ranging Schedule....................................................................................................... 4-96

4.2.5 Space Network (SN) Product Description....................................................................................... 4-964.2.5.1 Real-time VC0 Orbiter Telemetry..................................................................................................... 4-964.2.5.2 Archived VC0 Orbiter Telemetry...................................................................................................... 4-97

4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONS.................................. 4-974.3.1 CRaTER SOC Products ...................................................................................................................... 4-98

4.3.1.1 CRaTER Activity Request ................................................................................................................... 4-984.3.1.2 CRaTER Instrument Reset Timeline................................................................................................ 4-99

4.3.2 DLRE SOC Products......................................................................................................................... 4-1004.3.2.1 DLRE Activity Request....................................................................................................................... 4-1004.3.2.2 DLRE FSW Load................................................................................................................................... 4-101

4.3.3 LAMP SOC Products ........................................................................................................................ 4-1034.3.3.1 LAMP Activity Request...................................................................................................................... 4-1034.3.3.2 LAMP HV Command Sequence...................................................................................................... 4-1044.3.3.3 LAMP Instrument FSW Load........................................................................................................... 4-105

4.3.4 LEND SOC Products......................................................................................................................... 4-1064.3.4.1 LEND Activity Request ...................................................................................................................... 4-106

4.3.5 LOLA SOC Products ......................................................................................................................... 4-1084.3.5.1 LOLA Activity Request ...................................................................................................................... 4-1084.3.5.2 LOLA Improved Lunar Gravity Model......................................................................................... 4-1094.3.5.3 LOLA Instrument FSW Load ........................................................................................................... 4-1104.3.5.4 LOLA Processed OD Information .................................................................................................. 4-1114.3.5.5 LOLA Target Requests........................................................................................................................ 4-112

4.3.6 LROC SOC Products......................................................................................................................... 4-1134.3.6.1 LROC Instrument Initialization Command Sequence ............................................................. 4-1134.3.6.2 LROC Daily Command Sequence .................................................................................................. 4-1154.3.6.3 LROC Target Request.......................................................................................................................... 4-116

4.3.7 Mini-RF SOC Products..................................................................................................................... 4-1174.3.7.1 Mini-RF Load Files............................................................................................................................... 4-1174.3.7.2 Mini-RF Command Timeline............................................................................................................ 4-119


v



4.4 LRO FSWM FACILITY TO LRO MISSION MOC INTERFACE PRODUCTS......................... 4-1204.4.1.1 Orbiter FSW Load Files ...................................................................................................................... 4-120

4.5 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONS ................... 4-1204.5.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS ................................................. 4-120

4.5.1.1 Daily Command Load Report ........................................................................................................... 4-1214.5.1.2 SPICE SLCK Clock Correlation File............................................................................................. 4-1224.5.1.3 SPICE Event Kernel ............................................................................................................................. 4-1224.5.1.4 SPICE FK – Frame Kernels............................................................................................................... 4-1234.5.1.5 MOC PRODUCTS FOR CRaTER ................................................................................................. 4-1234.5.1.6 MOC PRODUCTS FOR DLRE....................................................................................................... 4-1274.5.1.7 MOC PRODUCTS FOR LAMP...................................................................................................... 4-1304.5.1.8 MOC PRODUCTS FOR LEND ...................................................................................................... 4-1344.5.1.9 MOC PRODUCTS FOR LOLA ...................................................................................................... 4-1384.5.1.10 MOC PRODUCTS FOR LROC ...................................................................................................... 4-1424.5.1.11 MOC PRODUCTS FOR Mini-RF .................................................................................................. 4-146

4.5.2 PLANETARY DATA SYSTEM (PDS) Interface and Products .................................................. 4-1504.5.2.1 Products Delivered to PDS................................................................................................................. 4-150

4.5.3 MOC PRODUCTS TO STATIONS................................................................................................. 4-1524.5.3.1 SCN Real-time Orbiter Commands (WS1 and USN).............................................................. 4-1544.5.3.2 DSN Real-time Orbiter Commands................................................................................................ 4-1544.5.3.3 SN Real-time Orbiter Commands.................................................................................................... 4-1554.5.3.4 SCN Orbiter Commands – CFDP Structure ................................................................................ 4-1554.5.3.5 DSN Orbiter Commands – CFDP Structure................................................................................ 4-1554.5.3.6 SDPS CFDP Control ............................................................................................................................ 4-156

4.5.4 MOC PRODUCTS to the CDDIS (for Laser Ranging Support)............................................... 4-1564.5.4.1 SCN Support Schedules ...................................................................................................................... 4-156

4.5.5 NAVIGATION AND ANCILLARY INFORMATION FACILITY (NAIF) Interface andProducts.............................................................................................................................................................. 4-156

4.5.5.1 SPICE Planetary SPK .......................................................................................................................... 4-1574.5.5.2 SPICE LSK – Leap Second ............................................................................................................... 4-157

4.6 LAUNCH SITE (KSC) PRODUCT AND DESCRIPTIONS .......................................................................... 4-1574.6.1 Launch Site Product Interface with the LRO MOC .................................................................... 4-157

4.6.1.1 Real-time VC0 Orbiter Telemetry................................................................................................... 4-1574.6.1.2 Archived VC0 Orbiter Telemetry.................................................................................................... 4-1584.6.1.3 Archived VC1 Telemetry Data......................................................................................................... 4-1584.6.1.4 Archived VC2 Telemetry Data......................................................................................................... 4-1594.6.1.5 Archived VC3 telemetry Data........................................................................................................... 4-1594.6.1.6 Launch Vehicle Post Separation Vector........................................................................................ 4-160

4.6.2 LRO MOC Product Interface with the Launch Site .................................................................... 4-1604.6.2.1 Telemetry to KSC.................................................................................................................................. 4-1604.6.2.2 Commands to KSC................................................................................................................................ 4-161

A APPENDIX – ABBREVIATIONS AND ACRONYMS......................................................................... A-1

B APPENDIX B – SAMPLE PRODUCT FORMATS ................................................................................B-1

B.1 SAMPLE FDF PRODUCTS...........................................................................................................................B-1B.1.1 SCN Acquisition Data Sample.............................................................................................................B-1B.1.2 LR Prediction Data Sample .................................................................................................................B-2


vi



B.1.3 Space Network Acquisition Data Sample..........................................................................................B-3B.1.4 Ground Station View Period Predicts Data Sample .......................................................................B-4B.1.5 LRO Beta Angle Predict File Sample ................................................................................................B-5B.1.6 LRO Definitive Ephemeris File Sample.............................................................................................B-6B.1.7 Lunar Orbit Ascending and Descending Node Predicts Sample..................................................B-7B.1.8 Lunar Orbit Terminator Crossing Predicts Sample........................................................................B-8B.1.9 Mission Eclipse Predicts Data Sample..............................................................................................B-9B.1.10 Lunar Ephemeris Data Sample ....................................................................................................B-10B.1.11 Orbiter Thruster Maneuver Plans Data Sample.......................................................................B-11B.1.12 Orbiter Post Maneuver Report Data Sample ............................................................................B-12B.1.13 Post Separation Report Data Sample .........................................................................................B-13B.1.14 Predicted LRO Ephemeris File Sample......................................................................................B-14B.1.15 Predicted Lunar Ground Track File Sample.............................................................................B-15B.1.16 Definitive Lunar Ground Track File Sample.............................................................................B-16B.1.17 Attitude Determination Verification Report Sample ................................................................B-17B.1.18 Attitude Slew Plan Sample ............................................................................................................B-18B.1.19 Gyro Calibration Data Sample ....................................................................................................B-19B.1.20 HGA Calibration Data Sample ....................................................................................................B-20B.1.21 LRO State Vector Table Sample...................................................................................................B-21B.1.22 Star Tracker Calibration Data Sample.......................................................................................B-22B.1.23 Thruster Calibration Data Sample..............................................................................................B-23B.1.24 LRO Momentum Management Unload Plan Sample...............................................................B-24B.1.25 Star Tracker Occultation Report Sample ...................................................................................B-25

B.2 SPACE COMMUNICATIONS DATA PRODUCTS......................................................................................B-26B.2.1 Station Support Schedules Sample ...................................................................................................B-26B.2.2 Station Support Schedules Report Sample ......................................................................................B-27B.2.3 Station Tracking Data Sample ..........................................................................................................B-28B.2.4 SCN Station Status Packets Sample .................................................................................................B-29B.2.5 WS1/USN Weather Data Sample ......................................................................................................B-30B.2.6 Ka-Band RF Receiver Data File Sample ........................................................................................B-31B.2.7 CFDP Status Messages Sample ........................................................................................................B-32B.2.8 Weekly Laser Ranging Schedule Sample.........................................................................................B-33B.2.9 DSN Tracking Data File Sample ......................................................................................................B-34

B.3 SCIENCE OPERATIONS CENTER PRODUCTS .........................................................................................B-35B.3.1 CRaTER Activity Request Sample ....................................................................................................B-35B.3.2 CRaTER Instrument Reset Timeline Sample ..................................................................................B-36B.3.3 DLRE Activity Request Sample .........................................................................................................B-37B.3.4 DLRE FSW Load Sample ...................................................................................................................B-38B.3.5 LAMP Activity Request Sample.........................................................................................................B-39B.3.6 LAMP HV Command Sequence Sample ..........................................................................................B-40B.3.7 LAMP Instrument FSW Load Sample ..............................................................................................B-41B.3.8 LEND Activity Request Sample.........................................................................................................B-42B.3.9 LOLA Activity Request Sample .........................................................................................................B-43B.3.10 LOLA Gravity Model Sample .......................................................................................................B-44B.3.11 LOLA Instrument FSW Load Sample..........................................................................................B-45B.3.12 LOLA Processed OD Information Sample.................................................................................B-46B.3.13 LOLA Target Requests Sample ....................................................................................................B-47


vii



B.3.14 LROC Instrument Initialization Command Sequence Sample ...............................................B-48B.3.15 LROC Instrument Initialization Command Sequence Sample ...............................................B-49B.3.16 LROC Daily Command Sequence Sample .................................................................................B-50B.3.17 LROC Target Requests ..................................................................................................................B-51B.3.18 Mini-RF Load Files ........................................................................................................................B-52B.3.19 Mini-RF Command Timeline Files..............................................................................................B-53

B.4 MISSION OPERATIONS CENTER PRODUCTS .........................................................................................B-54B.4.1 Daily Command Load Report Sample .............................................................................................B-54B.4.2 SCLK SPICE Clock Correlation File Sample ................................................................................B-55B.4.3 SPICE Event Kernel Sample..............................................................................................................B-56B.4.4 SPICE FK – Frame Kernel Sample..................................................................................................B-57B.4.5 CRaTER – Spacecraft Housekeeping Data File Sample..............................................................B-58B.4.6 CRaTER Housekeeping Data File Sample......................................................................................B-59B.4.7 CRaTER Raw Measurement Data Files Sample............................................................................B-60B.4.8 CRaTER Realtime VC0 Housekeeping Data Sample....................................................................B-61B.4.9 DLRE – Spacecraft Housekeeping Data File Sample...................................................................B-62B.4.10 DLRE Housekeeping Data Files Sample....................................................................................B-63B.4.11 DLRE Raw Measurement Data File Sample .............................................................................B-64B.4.12 DLRE Real-time VC0 Housekeeping Data Sample..................................................................B-65B.4.13 LAMP – Spacecraft Housekeeping Data File Sample .............................................................B-66B.4.14 LAMP Housekeeping Data Files Sample ...................................................................................B-67B.4.15 LAMP Raw Measurement Data Files Sample...........................................................................B-68B.4.16 LAMP Real-time VC0 Housekeeping Data Sample .................................................................B-69B.4.17 LEND – Spacecraft Housekeeping Data Files Sample............................................................B-70B.4.18 LEND Housekeeping Data Files Sample ...................................................................................B-71B.4.19 LEND Raw Measurement Data Files Sample ...........................................................................B-72B.4.20 LEND Real-time VC0 Housekeeping Data Sample..................................................................B-73B.4.21 LOLA – Spacecraft Housekeeping Data Files Sample ............................................................B-74B.4.22 LOLA Housekeeping Data Files Sample....................................................................................B-75B.4.23 LOLA Raw Measurement Data Files Sample............................................................................B-76B.4.24 LROC – Spacecraft Housekeeping Data Files Sample............................................................B-77B.4.25 LROC Housekeeping Data Files Sample ...................................................................................B-78B.4.26 LROC Raw Measurement Data Files Sample ...........................................................................B-79B.4.27 Mini-RF – Spacecraft Housekeeping Data Files Sample........................................................B-80B.4.28 Mini-RF Housekeeping Data Files Sample ...............................................................................B-81B.4.29 Mini-RF Operations Opportunity Sample..................................................................................B-82B.4.30 Mini-RF Raw Measurement Data Files Sample .......................................................................B-83B.4.31 Post Maneuver Spacecraft Mass Sample ...................................................................................B-84B.4.32 SCN Realtime Orbiter Commands Sample ................................................................................B-85B.4.33 SCN Realtime Orbiter Commands – CFDP Sample ................................................................B-86B.4.34 DSN Realtime Orbiter Commands Sample ................................................................................B-87B.4.35 DSN Realtime Orbiter Commands – CFDP Sample................................................................B-88

B.5 SAMPLE LAUNCH SITE PRODUCTS ........................................................................................................B-89B.5.1 Realtime Telemetry to KSC Sample..................................................................................................B-89B.5.2 Launch Vehicle Post Separation Vector Sample ...........................................................................B-90

B.6 SAMPLE PRODUCTS TO OTHER FACILITIES .........................................................................................B-91B.6.1 CFDP Control Messages....................................................................................................................B-91


viii



B.6.2 Weekly LRO Schedule Sample...........................................................................................................B-92B.6.3 Processed OD File Sample ................................................................................................................B-93B.6.4 Improved Lunar Gravity Model Sample..........................................................................................B-94

1.0 INTRODUCTION....................................................................................................................................1-11-1

1.1 PURPOSE AND SCOPE ............................................................................................................................1-11-11.2 DOCUMENT ORGANIZATION................................................................................................................1-11-11.3 REQUIREMENTS TRACEABILITY METHODOLOGY ...........................................................................1-11-11.4 APPLICABLE DOCUMENTS....................................................................................................................1-11-11.5 REFERENCED DOCUMENTS ..................................................................................................................1-21-21.6 OTHER DOCUMENTED REFERENCES ..................................................................................................1-21-2

2.0 GROUND SYSTEM OVERVIEW......................................................................................................2-12-1

2.1 GROUND SYSTEM ARCHITECTURE .....................................................................................................2-22-22.1.1 The LRO Space Communications Network..................................................................................2-32-32.1.2 LRO Mission Operations Center ...................................................................................................2-42-42.1.3 The Science Operations Centers....................................................................................................2-42-42.1.4 Flight Dynamics Facility.................................................................................................................2-52-52.1.5 Ground System Communications...................................................................................................2-52-5

2.2 LRO OPERATIONAL GROUND SYSTEM .............................................................................................2-72-72.2.1 ITOS-Supported Real-time Telemetry and Commanding..........................................................2-72-72.2.2 Data Processing System ..................................................................................................................2-82-82.2.3 Data Management System...............................................................................................................2-82-82.2.4 Mission Planning System.................................................................................................................2-92-92.2.5 Attitude Ground System...................................................................................................................2-92-92.2.6 Trending and Analysis System........................................................................................................2-92-92.2.7 Monitoring and Alert System..........................................................................................................2-92-9

2.3 FLIGHT DYNAMICS FACILITY ..........................................................................................................2-102-102.4 MISSION OPERATIONS TEAM...........................................................................................................2-102-102.5 FLIGHT SOFTWARE MAINTENANCE FACILITY .............................................................................2-102-102.6 LRO SPACE COMMUNICATIONS NETWORK .................................................................................2-102-10

3.0 LRO GS EXTERNAL INTERFACE PRODUCT SYNOPSIS...................................................3-13-1

4.0 LRO GROUND SYSTEM EXTERNAL INTERFACES AND PRODUCT...........................4-14-1

4.1 FLIGHT DYNAMICS FACILITY PRODUCTS .....................................................................................4-344-314.1.1 FDF Products for Network Support..........................................................................................4-354-32

4.1.1.1 (FDF-6) SCN Station Acquisition Data ...................................................................................4-354-324.1.1.2 (FDF-5) DSN Site Acquisition Data .........................................................................................4-384-354.1.1.3 (FDF-7) Laser Ranging Site Prediction Data.........................................................................4-404-374.1.1.4 (FDF-8) Space Network Acquisition Data..............................................................................4-414-38

4.1.2 FDF Products to support MOC Functions ..............................................................................4-454-414.1.2.1 (FDF-9, FDF-10) Ground Station View Period Predicts File (HGA and Omni ViewPeriods) 4-454-414.1.2.2 (FDF-3) LRO Beta Angle Predict File .....................................................................................4-474-434.1.2.3 (FDF-4) LRO Definitive Ephemeris File.................................................................................4-484-444.1.2.4 (FDF-29) LRO Definitive SPICE SPK File ...........................................................................4-494-464.1.2.5 (FDF-30) LRO Predictive SPICE SPK File ...........................................................................4-504-46


ix



4.1.2.6 (FDF-13) Lunar Orbit Ascending and Descending Node Predicts ................................4-514-474.1.2.7 (FDF-14) Lunar Orbit Terminator Crossing Predicts .........................................................4-524-484.1.2.8 (FDF-15) Mission Eclipse Predicts............................................................................................4-534-494.1.2.9 (FDF-16) Lunar Ephemeris...........................................................................................................4-544-504.1.2.10 (FDF-23) LRO State Vector Table.............................................................................................4-554-524.1.2.11 (FDF-17) Orbiter Thruster Maneuver Plans...........................................................................4-574-534.1.2.12 (FDF-19) Orbiter Post Maneuver Report.................................................................................4-584-544.1.2.13 (FDF-18) Post Separation Report ...............................................................................................4-594-564.1.2.14 (FDF-20) Predicted LRO Ephemeris File ...............................................................................4-624-594.1.2.15 (FDF-21) Predicted Lunar Ground Track File.......................................................................4-644-604.1.2.16 (FDF-22) Definitive Lunar Ground Track File .....................................................................4-654-614.1.2.17 (FDF-33) SPICE Binary PCK (High-Precision Lunar Orientation)..............................4-664-634.1.2.18 (FDF-36) FDF Reprocessed SPICE Definitive SPK Ephemeris (High-Precision OrbitEphemeris).................................................................................................................................................................4-674-634.1.2.19 (FDF-37) FDF Solar Conjunction File .....................................................................................4-674-644.1.2.20 (FDF-25) Thruster Calibration Data..........................................................................................4-694-654.1.2.21 (FDF-26) LRO Momentum Management Unload Plan .....................................................4-694-66

4.2 STATION PRODUCTS AND DESCRIPTIONS ................................................................................4-774-664.2.1 Space Communication Network (WS1) Product Descriptions.............................................4-804-69

4.2.1.1 (GNSO-1) SCN Support Schedules...........................................................................................4-804-694.2.1.2 (GNSO-2) SCN Support Schedule Report ..............................................................................4-834-724.2.1.3 (WS1-5) WS1 Raw Tracking Data.............................................................................................4-854-744.2.1.4 (WS1-10) Archived VC0 Telemetry Data...............................................................................4-894-774.2.1.5 (WS1-11) Archived VC1 Telemetry Data...............................................................................4-904-794.2.1.6 (WS1-12) Archived VC2 Telemetry Data...............................................................................4-924-814.2.1.7 (WS1-13) Archived VC3 Telemetry Data...............................................................................4-944-824.2.1.8 (WS1-6) Real-time VC0 Telemetry Data................................................................................4-954-844.2.1.9 (WS1-7) Real-time VC1 Telemetry Data................................................................................4-964-844.2.1.10 (WS-1) WS1 Station Status Packets ..........................................................................................4-974-854.2.1.11 (WS1-2) WS1 Weather Data ........................................................................................................4-974-864.2.1.12 (WS1-3) Ka-Band VC3 Telemetry ............................................................................................4-994-884.2.1.13 (WS1-4) Ka-Band VC2 Telemetry ..........................................................................................4-1004-884.2.1.14 (WS1-8) Ka-Band RF Receiver Data......................................................................................4-1004-894.2.1.15 (WS1-9) SDPS CFDP Status Packets .....................................................................................4-1014-894.2.1.16 (WS1-14) VC2 Housekeeping Telemetry Files ..................................................................4-1024-904.2.1.17 (WS1-15) Post-Pass Summary Report....................................................................................4-1024-914.2.1.18 (WS1-16) VC3 Measurement Telemetry Files....................................................................4-1044-924.2.1.19 (WS1-17) SPDP Event Logs ......................................................................................................4-1054-934.2.1.20 (WS1-18) SDPS System Logs ...................................................................................................4-1054-934.2.1.21 (WS1-19) SDPS CFDP PDU .....................................................................................................4-1064-94

4.2.2 Universal Space Network Product Descriptions ..................................................................4-1064-944.2.2.1 (USN-3) USN Raw Tracking Data...........................................................................................4-1064-944.2.2.2 (USN-1) USN Station Status Packets......................................................................................4-1074-954.2.2.3 (USN-2) USN Weather Data ......................................................................................................4-1084-964.2.2.4 (USN-4) Real-time VC0 Telemetry Data..............................................................................4-1104-974.2.2.5 (USN-5) Real-time VC1 Telemetry Data..............................................................................4-1104-984.2.2.6 (USN-6) Archived VC0 Telemetry Data ...............................................................................4-1114-99


x



4.2.2.7 (USN-7) Archived VC1 Telemetry Data .............................................................................4-1124-1004.2.3 Deep Space Network Product Descriptions.........................................................................4-1144-101

4.2.3.1 (DSN-1) DSN Tracking Data...................................................................................................4-1144-1024.2.3.2 (DSN-2) Real-time VC0 Telemetry Data............................................................................4-1154-1024.2.3.3 (DSN-5) Archived VC0 Telemetry Data .............................................................................4-1154-1034.2.3.4 (DSN-6) Archived VC1 Telemetry Data .............................................................................4-1164-1044.2.3.5 (DSN-3) Real-Time VC1 Telemetry Data ..........................................................................4-1174-1054.2.3.6 (DSN-4) DSN Station Monitor Packets ...............................................................................4-1184-105

4.2.4 Space Network (SN) Product Description............................................................................4-1194-1064.2.4.1 (SN-1) Real-time VC0 Orbiter Telemetry...........................................................................4-1194-1064.2.4.2 (SN-2) Archived VC0 Orbiter Telemetry............................................................................4-1204-106

4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONS.......................4-1214-1074.3.1 CRaTER SOC Products ...........................................................................................................4-1214-107

4.3.1.1 (CRaTER-1) LRO Operations Activity Request ..............................................................4-1214-1074.3.1.2 (CRaTER-2) CRaTER Instrument Reset Timeline..........................................................4-1234-109

4.3.2 DLRE SOC Products................................................................................................................4-1234-1104.3.2.1 (DLRE-1) LRO Operations Activity Request....................................................................4-1234-1104.3.2.2 (DLRE-2) DLRE FSW Load....................................................................................................4-1254-111

4.3.3 LAMP SOC Products ...............................................................................................................4-1274-1134.3.3.1 (LAMP-1) LRO Operations Activity Request...................................................................4-1274-1134.3.3.2 (LAMP-3) LAMP Instrument FSW Load ...........................................................................4-1294-115

4.3.4 LEND SOC Products................................................................................................................4-1314-1164.3.4.1 (LEND-1) LRO Operations Activity Request ...................................................................4-1314-116

4.3.5 LOLA SOC Products ................................................................................................................4-1334-1184.3.5.1 (LOLA-1) LRO Operations Activity Request ...................................................................4-1334-1184.3.5.2 (LOLA-2) LOLA Improved Lunar Gravity Model..........................................................4-1344-1194.3.5.3 (LOLA-3) LOLA Instrument FSW Load ............................................................................4-1354-1204.3.5.4 (LOLA-4) LOLA Processed OD Information ...................................................................4-1374-1224.3.5.5 (LOLA-5) LOLA Target Requests.........................................................................................4-1384-123

4.3.6 LROC SOC Products................................................................................................................4-1404-1244.3.6.1 (LROC-1) LRO Operations Activity Request for LROC..............................................4-1404-1254.3.6.2 (LROC-2) LROC Instrument Initialization Command Sequence..............................4-1424-1264.3.6.3 (LROC-3) LROC Daily Command Sequence ...................................................................4-1444-1274.3.6.4 (LROC-4) LROC Target Request...........................................................................................4-1464-129

4.3.7 Mini-RF SOC Products............................................................................................................4-1484-1304.3.7.1 (Mini-RF-1) LRO Operations Activity Request for Mini-RF .....................................4-1484-1314.3.7.2 (Mini-RF-2) Mini-RF Load Files ...........................................................................................4-1504-1324.3.7.3 (Mini-RF-3) Mini-RF Command Timeline.........................................................................4-1514-1344.3.7.4 (Mini-RF-4) Mini-RF Target Request ..................................................................................4-1524-135

4.4 LRO FSWM FACILITY TO LRO MISSION MOC INTERFACE PRODUCTS................4-1544-1364.4.1.1 (FSWM-1) Orbiter FSW Load Files......................................................................................4-1544-136

4.5 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONS ..........4-1544-1364.5.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS ........................................4-1544-137

4.5.1.1 (MOC-7) Daily Command Load Report..............................................................................4-1554-1374.5.1.2 (MOC-2) SPICE SLCK Clock Correlation File................................................................4-1574-1384.5.1.3 (MOC-33) SPICE Event Kernel..............................................................................................4-1584-1394.5.1.4 (MOC-39) SPICE FK – Frame Kernels ...............................................................................4-1594-140


xi



4.5.1.5 (MOC-41) SPICE Predicted CK (Predicted S/C Orientation).....................................4-1604-1414.5.1.6 (MOC-42) SPICE Definitive CK (Definitive S/C Orientation) ..................................4-1614-1414.5.1.7 (MOC-43) SPICE Definitive HGA Orientation CK........................................................4-1614-1424.5.1.8 (MOC-44) SPICE Definitive SA Orientation CK............................................................4-1624-1424.5.1.9 (MOC-45) HGA/SA Fixed Offset Frames Kernel ...........................................................4-1624-1434.5.1.10 Instrument – Spacecraft Housekeeping Data File ............................................................4-1634-1434.5.1.11 Instrument Housekeeping Data Files ....................................................................................4-1644-1454.5.1.12 Instrument Raw Measurement Data Files ...........................................................................4-1654-1464.5.1.13 Meta Summary Reports..............................................................................................................4-1674-1474.5.1.14 Real-time VC0 housekeeping data.........................................................................................4-1684-1494.5.1.15 (MOC-30) Mini-RF Operations Opportunity.....................................................................4-1714-1524.5.1.16 (MOC-61) PDS NAIF Dataset Archive ...............................................................................4-1724-1534.5.1.17 (MOC-62) RTS Command Load Report .............................................................................4-1734-154

4.5.2 PLANETARY DATA SYSTEM (PDS) Interface and Products .........................................4-1754-1554.5.2.1 Products Delivered to PDS........................................................................................................4-1754-155

4.5.3 MOC PRODUCTS TO STATIONS........................................................................................4-1774-1564.5.3.1 (MOC-34) SCN Real-time Orbiter Commands (WS1 and USN) ..............................4-1794-1594.5.3.2 (MOC-35) DSN Real-time Orbiter Commands ................................................................4-1804-1594.5.3.3 (MOC-36) SN Real-time Orbiter Commands....................................................................4-1804-1604.5.3.4 (MOC-1) SDPS CFDP Control ...............................................................................................4-1814-160

4.5.4 NAVIGATION AND ANCILLARY INFORMATION FACILITY (NAIF) Interface andProducts.....................................................................................................................................................4-1824-161

4.5.4.1 (NAIF-1) SPICE Planetary SPK.............................................................................................4-1824-1614.5.4.2 (NAIF-2) SPICE LSK – Leap Second..................................................................................4-1834-1614.5.4.3 (NAIF-3) SPICE Generic PCK (Planetary Constants) ...................................................4-1834-1614.5.4.4 (NAIF-4) SPICE Binary (High Precision Lunar Orientation) PCK ..........................4-1834-162

4.6 LAUNCH SITE (KSC) PRODUCT AND DESCRIPTIONS .................................................................4-1844-1624.6.1 Launch Site Product Interface with the LRO MOC ...........................................................4-1844-162

4.6.1.1 (KSC-1) Real-time VC0 Orbiter Telemetry .......................................................................4-1844-1624.6.1.2 (KSC-2) Real-time VC1 Orbiter Telemetry .......................................................................4-1854-1634.6.1.3 (KSC-3) Archived VC0 Orbiter Telemetry ........................................................................4-1854-1634.6.1.4 (KSC-4) Archived VC1 Telemetry Data .............................................................................4-1854-1644.6.1.5 (KSC-5)Archived VC2 Telemetry Data...............................................................................4-1864-1644.6.1.6 (KSC-6) Archived VC3 telemetry Data ...............................................................................4-1864-1654.6.1.7 (LV-1) Launch Vehicle Post Separation Vector ...............................................................4-1874-165

4.6.2 LRO MOC Product Interface with the Launch Site ...........................................................4-1874-1654.6.2.1 (MOC-38) Telemetry to KSC ..................................................................................................4-1874-1654.6.2.2 (MOC-37) Commands to KSC ................................................................................................4-1884-166

A APPENDIX – ABBREVIATIONS AND ACRONYMS...................................................................A-1A-1

B APPENDIX B – SAMPLE PRODUCT FORMATS ......................................................................... B-1B-1

B.1 SAMPLE FDF PRODUCTS.................................................................................................................... B-1B-1B.1.1 (FDF-6) SCN INP-2 Acquisition Data Sample..........................................................................B-1B-1B.1.2 (FDF-6) SCN OEM Acquisition Data Sample ...........................................................................B-1B-1B.1.3 (FDF-7) LR Prediction Data Sample...........................................................................................B-2B-2B.1.4 (FDF-8) Space Network Acquisition Data Sample ...................................................................B-3B-3B.1.5 (FDF-9) and (FDF-10) Ground Station View Period Predicts Data Sample......................B-4B-4


xii



B.1.6 (FDF-3) LRO Beta Angle Predict File Sample..........................................................................B-5B-5B.1.7 (FDF-4) LRO Definitive Ephemeris File Sample......................................................................B-6B-6B.1.8 (FDF-13) Lunar Orbit Ascending and Descending Node Predicts Sample .........................B-7B-7B.1.9 (FDF-14) Lunar Orbit Terminator Crossing Predicts Sample...............................................B-8B-8B.1.10 (FDF-15) Mission Eclipse Predicts Data Sample................................................................B-9B-9B.1.11 (FDF-16) Lunar Ephemeris Data Sample .........................................................................B-10B-10B.1.12 (FDF-17) Orbiter Thruster Maneuver Plans Data Sample............................................B-11B-11B.1.13 (FDF-19) Orbiter Post Maneuver Report Data Sample .................................................B-12B-12B.1.14 (FDF-18) Post Separation Report Data Sample ..............................................................B-13B-13B.1.15 (FDF-20) Predicted LRO Ephemeris File Sample...........................................................B-14B-14B.1.16 (FDF-21) Predicted Lunar Ground Track File Sample ..................................................B-15B-15B.1.17 (FDF-22) Definitive Lunar Ground Track File Sample..................................................B-16B-16B.1.18 (FDF-23) LRO State Vector Table Sample........................................................................B-17B-17B.1.19 (FDF-26) LRO Momentum Management Unload Plan Sample ....................................B-18B-18B.1.20 (FDF-37) Solar Conjunction File Sample .........................................................................B-19B-19

B.2 SPACE COMMUNICATIONS DATA PRODUCTS............................................................................. B-31B-20B.2.1 (GNSO-1) Station Support Schedules Sample........................................................................B-31B-20B.2.2 (GNSO-2) Station Support Schedules Report Sample ..........................................................B-32B-21B.2.3 (WS1-5) Station Tracking Data Sample ..................................................................................B-33B-22B.2.4 (WS1-2) and (USN-2) WS1/USN Weather Data Sample......................................................B-35B-23B.2.5 (WS1- 8) Ka-Band RF Receiver Data File Sample ...............................................................B-36B-24B.2.6 (WS1-15) Post-Pass Summary Report Sample.......................................................................B-37B-25B.2.7 (WS1-17) SDPS Event Log Sample ..........................................................................................B-39B-27B.2.8 (WS1-18) SDPS System Log Sample ........................................................................................B-40B-28B.2.9 (DSN-1) DSN Tracking Data File Sample..............................................................................B-41B-29

B.3 SCIENCE OPERATIONS CENTER PRODUCTS ................................................................................ B-42B-30B.3.1 LRO Operations Activity Request Sample...............................................................................B-42B-30B.3.2 (CRaTER-2) CRaTER Instrument Reset Timeline Sample ..................................................B-43B-31B.3.3 (DLRE-2) DLRE FSW Load Sample ........................................................................................B-45B-32B.3.4 (LAMP-3) LAMP Instrument FSW Load Sample ..................................................................B-48B-33B.3.5 (LOLA-2) LOLA Improved Lunar Gravity Model Sample...................................................B-51B-34B.3.6 (LOLA-3) LOLA Instrument FSW Load Sample....................................................................B-52B-35B.3.7 (LOLA-5) LOLA Target Requests Sample...............................................................................B-54B-36B.3.8 (LROC-2) LROC Instrument Initialization Command Sequence Sample .........................B-56B-37B.3.9 (LROC-3) LROC Daily Command Sequence Sample...........................................................B-57B-38B.3.10 (LROC-4) LROC Target Requests.......................................................................................B-58B-39B.3.11 (Mini-RF-2) Mini-RF Load Files.........................................................................................B-59B-40B.3.12 (Mini-RF-3) Mini-RF Command Timeline Files...............................................................B-60B-41B.3.13 (Mini-RF-4) Mini-RF Target Requests...............................................................................B-61B-42

B.4 MISSION OPERATIONS CENTER PRODUCTS ................................................................................ B-63B-43B.4.1 (MOC-7) Daily Command Load Report Sample ...................................................................B-63B-43B.4.2 (MOC-62) RTS Command Load Report Sample....................................................................B-64B-44B.4.3 MOC-2) SCLK SPICE Clock Correlation File Sample........................................................B-65B-45B.4.4 (MOC-33) SPICE Event Kernel Sample..................................................................................B-68B-48B.4.5 (MOC-39) SPICE FK – Frame Kernel Sample......................................................................B-69B-49B.4.6 (MOC-30) Mini-RF Operations Opportunity Sample...........................................................B-94B-50B.4.7 (MOC-nn) Meta-Summary Report Sample .............................................................................B-96B-51


xiii



B.4.8 (MOC-34) SCN Realtime Orbiter Commands Sample .........................................................B-97B-52B.4.9 (MOC-35) DSN Realtime Orbiter Commands Sample.........................................................B-99B-53

B.5 SAMPLE LAUNCH SITE PRODUCTS ............................................................................................. B-101B-54B.5.1 (LV-1) Launch Vehicle Post Separation Vector Sample ....................................................B-102B-54


xiv



LIST OF FIGURES

Figure PageFigure 2-1 LRO Ground System Overview Diagram.................................................................. 2-32-3

Figure 2-2 LRO Communications Architecture ......................................................................... 2-62-6

Figure 4-1 SMEX/LEOT Telemetry Header ..........................................................................4-784-67

Figure 4-2 SLE Telemetry Header Structure ......................................................................4-1144-102

Figure 4-3 ITOS Annotation Header Layout ......................................................................4-1694-150

Figure 4-4 EOS Ground Message Header ..........................................................................4-1774-157

Figure 4-5 SLE F-CLTU Command Structure....................................................................4-1794-158

Figure 4-6 Space Network Command Structure..................................................................4-1794-158

Figure B.1-7 Sample SCN INP-2 Acquisition Data File............................................................. B-1B-1

Figure B.1-8 Sample SCN OEM Acquisition Data File ............................................................. B-1B-1

Figure B.1-9 Sample Laser Ranging Prediction Data File .......................................................... B-2B-2

Figure B.1-10 Sample Space Network Acquisition Data File...................................................... B-3B-3

Figure B.1-11 Sample Ground Station View Period Predicts Data File......................................... B-4B-4

Figure B.1-12 Sample LRO Beta Angle Predict File ................................................................. B-5B-5

Figure B.1-13 Sample LRO Definitive Ephemeris File .............................................................. B-6B-6

Figure B.1-14 Sample Lunar Orbit Ascending and Descending Node Predicts File ........................ B-7B-7

Figure B.1-15 Sample Lunar Orbit Terminator Crossing Predicts Data File .................................. B-8B-8

Figure B.1-16 Sample Mission Eclipse Predicts Data File.......................................................... B-9B-9

Figure B.1-17 Sample Lunar Ephemeris Data File ................................................................ B-10B-10

Figure B.1-18 Sample Orbiter Thruster Maneuver Plans Data File .......................................... B-11B-11

Figure B.1-19 Sample Orbiter Post Maneuver Report Data File .............................................. B-12B-12

Figure B.1-20 Sample Post Separation Report Data File ........................................................ B-13B-13

Figure B.1-21 Sample Predicted LRO Ephemeris File ........................................................... B-14B-14


xv



Figure B.1-22 Sample Predicted Lunar Ground Track File..................................................... B-15B-15

Figure B.1-23 Sample Definitive Lunar Ground Track File .................................................... B-16B-16

Figure B.1-24 Sample LRO State Vector Table Data File ...................................................... B-17B-17

Figure B.1-25 Sample LRO Momentum Management Unload Plan File .................................. B-18B-18

Figure B.1-26 Sample Solar Conjunction File ...................................................................... B-19B-19

Figure B.2-1 Sample Station Support Schedules File............................................................. B-31B-20

Figure B.2-2 Sample Station Support Schedule Report File.................................................... B-32B-21

Figure B.2-3 Sample Station Tracking Data File................................................................... B-33B-22

Figure B.2-4 Sample WS1/USN Weather Data File .............................................................. B-35B-23

Figure B.2-5 Sample Ka-Band RF Receiver Data File ........................................................... B-36B-24

Figure B.2-6 Sample Post-Pass Summary Report File ........................................................... B-37B-25

Figure B.2-7 Sample SDPS Event Log File.......................................................................... B-39B-27

Figure B.2-8 Sample SDPS System Log File ....................................................................... B-40B-28

Figure B.2-9 Sample DSN Tracking Data File ..................................................................... B-41B-29

Figure B.3-1 Sample LRO Operations Activity Request File .................................................. B-42B-30

Figure B.3-2 CRaTER Instrument Reset Timeline ................................................................ B-43B-31

Figure B.3-3 Sample DLRE FSW Load File ........................................................................ B-45B-32

Figure B.3-4 Sample LAMP Instrument FSW Load File........................................................ B-48B-33

Figure B.3-5 Sample LOLA Improved Lunar Gravity Model ................................................. B-51B-34

Figure B.3-6 Sample LOLA Instrument FSW Load File ........................................................ B-52B-35

Figure B.3-7 Sample LOLA Target Requests File................................................................. B-54B-36

Figure B.3-8 Sample LROC Instrument Initialization Command Sequence .............................. B-56B-37

Figure B.3-9 LROC Daily Command Sequence File ............................................................. B-57B-38

Figure B.3-10 Sample LROC Target Requests File ............................................................... B-58B-39

Figure B.3-11 Sample Mini-RF Load File ........................................................................... B-59B-40


xvi



Figure B.3-12 Sample Mini-RF Command Timeline File....................................................... B-60B-41

Figure B.3-13 Sample Mini-RF Target Requests File ............................................................ B-61B-42

Figure B.4-1 Sample Daily Command Load Report File ........................................................ B-63B-43

Figure B.4-1 Sample RTS Command Load Report File ......................................................... B-64B-44

Figure B.4-2 Sample SCLK SPICE Clock Correlation File .................................................... B-67B-47

Figure B.4-3 Sample SPICE Event Kernel........................................................................... B-68B-48

Figure B.4-4 Sample SPICE FK – Frame Kernel .................................................................. B-69B-49

Figure B.4-5 Sample Mini- Operations Opportunity File ....................................................... B-94B-50

Figure B.4-6 Sample Meta-summary Report ........................................................................ B-96B-51

Figure B.4-7 Sample SCN Realtime Orbiter Commands........................................................ B-97B-52

Figure B.4-8 Sample DSN Realtime Orbiter Commands........................................................ B-99B-53

Figure B.5-9 Sample Launch Vehicle Post Separation Vector File ........................................ B-102B-54

LIST OF TABLESTable PageTable 2-1 MOC Functional Component Information ........................................................................2-7

Table 3-1 LRO External Interface Products Cross Reference.............................................................3-1

Table 4-1 LRO Product Summary Information................................................................................4-2

Table 4-2 FDF File Naming Convention ......................................................................................4-25


xvii



Table 4-3 FDF – SCN Acquisition Data Description ......................................................................4-27

Table 4-4 FDF – Laser Ranging Prediction Data Description ..........................................................4-30

Table 4-5 FDF – SN Acquisition Data Description ........................................................................4-31

Table 4-6 FDF – Ground Station View Period Data Description ......................................................4-35

Table 4-7 FDF – LRO Beta Angle Data Description ......................................................................4-37

Table 4-8 FDF – LRO Definitive Ephemeris Data Description ........................................................4-38

Table 4-9 FDF – LRO Ascending Descending Node Data Description..............................................4-41

Table 4-10 FDF – LRO Lunar Orbit Terminator Crossing Predicts Data Description ..........................4-42

Table 4-11 FDF – LRO Mission Eclipse Data Description ..............................................................4-43

Table 4-12 FDF – Lunar Ephemeris Data Description ....................................................................4-44

Table 4-13 FDF – LRO State Vector Table Data Description ..........................................................4-45

Table 4-14 FDF – LRO Orbiter Post Maneuver Report Data Description Information.........................4-48

Table 4-15 FDF – LRO Post Separation Report Data Description Information ...................................4-49

Table 4-16 FDF – LRO Predictive Ephemeris Data Description Information .....................................4-52

Table 4-17 FDF – LRO Predicted Ephemeris Data Description Information ......................................4-53

Table 4-18 FDF – LRO Definitive Lunar Ground Track Description Information...............................4-54

Table 4-19 FDF – Attitude Slew Plan Data Description Information ................................................4-57

Table 4-20 FDF – Tracker Occultation Report Data Description Information.....................................4-60

Table 4-21 SMEX/LEOT Field Definitions and Expected Values ....................................................4-64

Table 4-22 SLE Telemetry Header Structure Definitions ................................................................4-66

Table 4-23 Space Network Telemetry Header Structure Definitions ......Error! Bookmark not defined.

Table 4-24 SCN Station Support Schedule Field Definitions ...........................................................4-67

Table 4-25 LRO TR Code Assignments .......................................................................................4-67

Table 4-26 SCN Station Support Schedule Field Definitions ...........................................................4-69

Table 4-27 WS1 Raw Tracking Data File Field Definitions.............................................................4-70


xviii



Table 4-28 WS1 Station Weather Data Field Definitions ................................................................4-79

Table 4-29 WS1 Ka-Band Receiver Data Field Definitions .............................................................4-81

Table 4-30 USN Station Weather Data Field Definitions ................................................................4-88

Table 4-31 EOS Ground Message Header Definitions ..................................................................4-152

Table 4-32 SLE Command Structure Definitions.........................................................................4-153

Table 4-33 Space Network Command Structure Definitions..........................................................4-154

Table 2-1 MOC Functional Component Information .................................................................. 2-72-7

Table 3-1 LRO External Interface Products Cross Reference....................................................... 3-13-1

Table 4-1 LRO Product Summary Information.......................................................................... 4-24-2

Table 4-2 FDF File Naming Convention ...............................................................................4-344-31

Table 4-3 FDF – SCN Acquisition Data Description ...............................................................4-364-33

Table 4-4 FDF – Laser Ranging Prediction Data Description ...................................................4-404-37

Table 4-5 FDF – IIRV TTY SN Acquisition Data Description..................................................4-424-39

Table 4-6 FDF – Ground Station View Period Data Description ...............................................4-464-42

Table 4-7 FDF – LRO Beta Angle Data Description ...............................................................4-474-43

Table 4-8 FDF – LRO Definitive Ephemeris Data Description .................................................4-484-44

Table 4-9 FDF – LRO Ascending Descending Node Data Description.......................................4-514-47

Table 4-10 FDF – LRO Lunar Orbit Terminator Crossing Predicts Data Description ...................4-524-48

Table 4-11 FDF – LRO Mission Eclipse Data Description .......................................................4-534-49

Table 4-12 FDF – Lunar Ephemeris Data Description .............................................................4-544-50

Table 4-13 FDF – LRO State Vector Table Data Description ...................................................4-564-52

Table 4-14 FDF – LRO Orbiter Post Maneuver Report Data Description Information..................4-584-54

Table 4-15 FDF – LRO Post Separation Report Data Description Information ............................4-604-56

Table 4-16 FDF – LRO Predictive Ephemeris Data Description Information ..............................4-634-59

Table 4-17 FDF – LRO Predicted Ephemeris Data Description Information ...............................4-644-60


xix



Table 4-18 FDF – LRO Definitive Lunar Ground Track Description Information........................4-654-62

Table 4-19 Solar Conjunction Data Description......................................................................4-684-64

Table 4-20 SMEX/LEOT Field Definitions and Expected Values .............................................4-784-67

Table 4-21 SCN Station Support Schedule Field Definitions ....................................................4-814-69

Table 4-22 LRO TR Code Assignments ................................................................................4-814-70

Table 4-23 SCN Support Schedule Report Field Definitions ....................................................4-834-72

Table 4-24 WS1 Raw Tracking Data File Field Definitions......................................................4-864-75

Table 4-25 WS1 Station Weather Data Field Definitions .........................................................4-984-86

Table 4-26 WS1 Ka-Band Receiver Data Field Definitions ....................................................4-1014-89

Table 4-27 Post-Pass Summary Field Definitions .................................................................4-1034-91

Table 4-28 USN Station Weather Data Field Definitions .......................................................4-1094-96

Table 4-29 SLE Telemetry Header Structure Definitions .....................................................4-1144-102

Table 4-30 SOC File Naming Conventions and Descriptions................................................4-1634-144

Table 4-31 Meta-Summary Report Description ..................................................................4-1674-148

Table 4-32 ITOS Annotation Header Field Definitions........................................................4-1694-150

Table 4-33 EOS Ground Message Header Definitions .........................................................4-1784-157

Table 4-34 SLE Command Structure Definitions................................................................4-1794-158

Table 4-35 Space Network Command Structure Definitions.................................................4-1794-159


xx




1-1



1.0 INTRODUCTIONThe Interface Control Document for the Lunar Reconnaissance Orbiter Ground System (431-ICD-000049) is one of three documents produced by the Lunar Reconnaissance Orbiter (LRO)ground system team that provides the foundation for the development and operations of theground system for all mission phases. The other documents are the Lunar ReconnaissanceOrbiter Detailed Mission Requirements Document (431-RQMT-000049) and the LunarReconnaissance Orbiter Mission Design Handbook (431-HDBK-000486).This document provides the Level-3 mission interface requirements and identifies the products,which are noted in that document and provided within the scope of this document.1.1 PURPOSE AND SCOPEThe ICD specifies the interface that the LRO ground system (GS) has with the SpaceCommunications Network (SCN) and the various science centers, as well as the externalinterfaces with other LRO mission operations center (MOC) elements.1.2 DOCUMENT ORGANIZATIONThe document organization provides details regarding the various ground system elements andthe interfaces and products between the external LRO elements and the LRO ground system.

Section 2.0 contains a brief description of the mission, ground system architecture, and identifiesthe various ground system elements. More detailed and specific information on the orbiter,launch vehicle, schedules, and mission phases is provided by the LRO Mission Concept ofOperations (MCO).

Section 3.0 provides the cross reference of the external products to/from the LRO MOC; itprovides a mapping of DMR requirements and the cross reference to other document sections,which is linked to provide more specific details.Section 4 provides the call out of each external interface and the associated products that aretransferred between LRO external elements and the LRO ground system elements.Outstanding open items within the ICD are identified as “To Be Determined” (TBD), “To BeSupplied” (TBS), or “To Be Resolved” (TBR). Open items are documented in the List ofTBDs/TBRs section in the front of the document.

1.3 REQUIREMENTS TRACEABILITY METHODOLOGYThe ground system interfaces specified in this document are derived from the LunarReconnaissance Orbiter Detailed Mission Requirements DocumentLunar ReconnaissanceOrbiter Detailed Mission Requirements DocumentLunar Reconnaissance Orbiter DetailedMission Requirements Document (431-RQMT-0000049), which identified the specific instanceassociated with the interface description.

1.4 APPLICABLE DOCUMENTSThe following LRO project documents apply only to the extent they are cited in this document.431-RQMT-000174 Lunar Reconnaissance Orbiter Mission Assurance Requirements


1-2



431-RQMT-000049 Lunar Reconnaissance Orbiter Detailed Mission RequirementsDocument

431-HDBK-000052 Lunar Reconnaissance Orbiter Telemetry and Command FormatsHandbook

431-HDBK-000053 Lunar Reconnaissance Orbiter Telemetry and Command DatabaseHandbook

431-SPEC-000078 Lunar Reconnaissance Orbiter CCSDS File Delivery ProtocolSpecification

431-ICD-0000NN ICD between the LRO Project and the NASA Ground Network(NGN) (Scheduling and Monitoring Interface)

431-HDBK-000486 Lunar Reconnaissance Orbiter Mission Design Handbook431-RQMT-000113 LRO Pointing and Alignment Requirements

1.5 REFERENCED DOCUMENTSThe following NASA and GFSC documents are used as supporting and reference documentsonly.

NASA NPR 2810.1a NASA Security of Information Technology; Revalidated 12August 2004

STDN-724 STDN Tracking and Acquisition Handbook; 1990Lunar Reconnaissance Orbiter (LRO) Flight Software (CF) CCSDS File Data Protocol Task

User's Guide, Version 1.0, September 14, 2006820-013 0163-Telecomm DSN Space Link Extension Forward Link Service and Return Link

Service; Revision A – February 15, 2004820-13 TRK 2-33 DSN document to define external interface for SPICE SPK, Type

13DSN-xxx-xxxx (TBD) Deep Space Network Service Preparation Sub-system (SPS)820-

13, 0168 Service Management Interface document887-117 SPS Portal Operation ManualCCSDS 502.0-B-1 Orbit Data Messages, September 2004

1.6 OTHER DOCUMENTED REFERENCESFormat data concepts specifically needed to support the laser ranging sites

http://ilrs.gsfc.nasa.gov/products_formats_procedures/fullrate/fr_format_v3.htmlhttp://ilrs.gsfc.nasa.gov/products_formats_procedures/predicitons/index.htmlhttp://naif.jpl.nasa.gov/naif/about.htmlhttps://spsweb.fltops.jpl.nasa.gov


1-3




2-1



2.0 GROUND SYSTEM OVERVIEWThe Lunar Reconnaissance Orbiter (LRO) is the first robotic mission of the Lunar Precursor andRobotic Program (LPRP). The primary objective of the LRO mission is to conductinvestigations that support future human exploration of the Moon. The launch readiness date forLRO is October 2008.LRO specific objectives are:

• Characterize the lunar radiation environment, biological impacts, and potential mitigation• Determine a high resolution global, geodetic grid of the Moon in three dimensions• Assess in detail the resources and environments of the Moon’s polar cap regions• Perform high spatial resolution measurement of the Moon’s surfaceThe LRO instrument complement includes six instruments. Together, all six instruments allowLRO to meet the mission objectives. The following text provides an overview description of thesix instruments:

• Lunar Orbiter Laser Altimeter (LOLA): LOLA will determine the global topographyof the lunar surface at high resolution, measuring landing site slopes and search for polarice in shadow regions.

• Lunar Reconnaissance Orbiter Camera (LROC): LROC will acquire targeted imagesof the lunar surface capable of resolving small-scale features that could be landing sitehazards. LROC will also produce wide-angle images at multiple wavelengths of the lunarpoles to document the changing illumination conditions and potential resources.

• Lunar Exploration Neutron Detector (LEND): LEND will map the flux of neutronsfrom the lunar surface to search for evidence of water ice and provide measurements ofspace radiation environment which can be useful for future human exploration.

• Diviner Lunar Radiometer Experiment (DLRE): DLRE will map the temperature ofthe entire lunar surface at 300-meter horizontal scales to identify cold-traps and potentialice deposits.

• Lyman-Alpha Mapping Project (LAMP): LAMP will observe the entire lunar surfacein the far ultraviolet (UV). LAMP will search for surface ice and frost in the PolarRegions and provide images of permanently shadowed regions illuminated only bystarlight.

• Cosmic Ray Telescope for Effects of Radiation (CRaTER): CRaTER will investigatethe effect of galactic cosmic rays on tissue-equivalent plastics as a constraint on modelsof biological response to background space radiation.

LRO will also fly a technology demonstration instrument called the Mini-Radio Frequency (RF).The purpose of the Mini-RF is to demonstrate new radar technology for future use in planetaryresource mapping. The mini-RF payload will operate on a non-interference basis throughout themission.

pgf

Highlight

CRaTER definition


2-2



The LRO spacecraft bus will be built at Goddard Space Flight Center (GSFC). Integration of themeasurement instruments to the orbiter system as well as orbiter environmental testing will beperformed at GSFC.LRO is scheduled to launch in October 2008. The orbiter will be launched aboard an evolvedexpendable launch vehicle (EELV) from the Eastern Range at the Kennedy Space Center (KSC).The Launch Vehicle (LV) will inject LRO into a cis-lunar transfer orbit. LRO will be required toperform a series of Lunar Orbit Insertion (LOI) maneuvers to enter into the orbitercommissioning orbit of 30x216 kilometers (km). After orbiter commissioning is complete, LROwill be maneuvered into a 50 km circular orbit.Once LRO is in the final mission orbit, the six instruments will start to collect measurement datafor the mission. Measurement data along with housekeeping (HK) data will be dumped to theLRO Ground System (GS). Once the data is are received onat the ground MOC, the GS MOC isresponsible for distribution of the data to the individual science operations centers (SOCs). TheSOCs will receive and process the data to create level 1 data products. The LRO GS and SOCsalso have the responsibility to transfer the processed data products to the Planetary Data System(PDS) for long term archival.

The details of the mission with the identification of the mission phases and the activities witheach phase are provided in the Lunar Reconnaissance Orbiter Mission Design Handbook (431-HDBK-000486)2.1 GROUND SYSTEM ARCHITECTUREThe LRO GS is comprised of several main elements as shown in Figure 2-1 LRO GroundSystem Overview DiagramFigure 2-1 LRO Ground System Overview Diagram:

• The LRO Space Communications Network, which consists of an S/Ka Band ground stationat White Sands and various S-Band only ground stations located throughout the world. Itincludes the Deep Space Network for use as a contingency/emergency network and a laserranging facility, which is used to provide improved orbit knowledge for the orbiter. TheLRO mission uses the Space Network (SN) asset for the first several hours post-launch toprovide any necessary support until the first ground station coverage.

• Mission Operations Center (MOC)• Flight Dynamics (FD), which supports maneuver planning, orbit determination, and attitude

determination and sensor calibration processing• SOC for each instrument• Communications network which provides voice and data connectivity between each of these

elementsBecause of the high data volume that LRO will produce and the use of Ka-Band frequency, LROelected to use a dedicated S/Ka ground station for primary measurement data downlink. Themeasurement data is are collected at the ground station and rate buffered to the MOC post-passfor data processing/accountability. The MOC at GSFC will distribute the measurement filesalong with other mission products that are needed for processing to each of the instrument SOCs.


2-3



The MOC is the focal point for all orbiter operations including health and safety monitoring. Allcommands to the orbiter are generated at the MOC. The SOCs support instrument operationsincluding instrument command sequence inputs, measurement data processing, transferringmeasurement products to the PDS, and instrument housekeeping and performance trending.

Figure 2-1 LRO Ground System Overview DiagramEach LRO Ground System element, as listed in Figure 2-1, is briefly described in the followingsubsections.2.1.1 The LRO Space Communications NetworkThe LRO Space Communications Network (SCN) consists of a dedicated ground station atWhite Sands Complex, which is identified as White Sands One (WS1) and commercial S-Bandground stations; it uses the Jet Propulsion Laboratory (JPL)/DSN ground stations forbackup/emergency support. The SN supports any post-launch contacts within the first several


2-4



hours after launch that are required before either the WS1 station or the USN or DSN stationshave a contact with the LRO Orbiter.

The SCN supports the laser ranging site, which is located in Greenbelt, Maryland. The laserranging site provides one-way laser time of flight data and supports, through the LOLA SOC, thedevelopment of an improved lunar gravity model.The WS1 ground station is capable of receiving 100 megabits per second (Mbps) downlink onKa-Band frequency of measurement data files produced by the instruments and supporting real-time commands and telemetry on S-Band frequency. Due to susceptibility to Ka from weather,White Sands provides the optimal location due to its minimal precipitation levels. Because LROrequires near continuous tracking data for orbit determination, additional S-Band sites areneeded. The S-Band only sites will provide real-time telemetry and commands capabilities alongwith tracking data. The S-Band stations could be used to dump low rate measurement files in acontingency mode. LRO plans to use the Deep Space Network for emergency/backup support.The emergency/backup support will utilize only the S-Band frequency.

2.1.2 LRO Mission Operations CenterThe MOC will be located at GSFC. It is the main telemetry and command interface to theorbiter. The MOC will process housekeeping data to monitor health and safety of the orbiter.The MOC will also distribute measurement data to the individual SOCs along with otherrequired mission products. The MOC provides temporary measurement data storage untilverification is received from the SOC on file delivery. The MOC will receive any requiredinstrument command sequences from the SOCs and process them before uplink. The MOC willalso distribute real-time telemetry to the SOCs.

The LRO MOC provides the following types of control functions as listed below; thesefunctional components will be further described and identified in later sections.

• Telemetry& Command System (includes functionality to support Integration and Test (I&T)Ground Support Equipment (GSE))

• Mission Planning System• Trending System• MOC – Attitude Determination Ground System (MOC-ADSAGS)• Data Processing System• Data Management System• Monitoring and Alert System

2.1.3 The Science Operations CentersThe six SOCs and the Mini-RF technology demonstration operations center provide the hardwareand software to support the following functions:

• Instrument health and safety monitoring• Instrument command sequence generation/request


2-5



• Support orbiter calibration planning/coordination• Measurement data processing (level 0 and high)• Measurement data product archiving and transfer to the PDS• Maintain instrument flight software/tablesThe SOCs themselves are not controlled and developed by the LRO ground system. The groundsystem responsibility ends with the interfaces to/from each of the SOCs2.1.4 Flight Dynamics FacilityFlight Dynamics (FD) performs orbit determination, attitude processing and maneuver/trajectory planning. For orbit determination, FD will receive the tracking data from the groundnetwork and generate mission products. FD will also provide attitude verification and planningsupport for slews. Besides pre-mission trajectory and orbit planning, FD will also monitor andplan for trajectory maneuvers during the cruise, Lunar Orbit Insertion burns, and station-keepingmaneuvers. The maneuver plans will be supplied to the MOC for execution.

2.1.5 Ground System CommunicationsThe ground system communication network provides voice and data connectivity between eachof the ground system elements. It will provide the necessary communication lines between theground networks, MOC and SOCs.

Figure 2–2 depicts the communication architecture among the various LRO elements. It includesthe space communications networks, the Kennedy Space Center (KSC), the GSFC MOC, and theseven science centers, which are located at various sites within the continental US. Thecommunication links consist of dedicated communications lines, circuits, and routers.


2-6



Figure 2-22 LRO Communications ArchitectureCommunication among the I&T GSE, GS elements, the various science centers, and dedicatedground station at the White Sands Complex (WSC), the JPL/DSN backup/emergency groundstations, and the commercial S-Band network is accomplished through the Nascom Division andthe NASA Integrated Services Network (NISN). NISN maintains both a secure or “closed”Internet Protocol (IP) Operational Network (IONet), an unsecured or “open” IONet, and a hybridRestricted IONet (RIONet).All LRO MOC GS elements are on the restricted IONet; the FDF component, located at GSFC inBuilding 28, resides on the closed IONet. NISN supplies the IP access connection from theclosed, restricted, and open IONets and to the Center Network Environment (CNE) Wide AreaNetwork (WAN).If the MOC needs to send any real-time data from the restricted IONet to the open IONet, theMOC will provide this data using a socket connection through a secure applications gateway, asdepicted in Figure 2-2Figure 2-2.

LRO SE personnel conducted a trade study and selected the secure copy (scp) mechanism fornon real-time data transfers. All files into and out of the MOC will use this identified protocol.The LRO MOC will scp “push” files from the MOC to an agreed upon directory locations thatthe external elements have identified. Conversely, the external elements will scp “push” their


2-7



files to a standard input directory structure within the LRO MOC. The MOC and externalelements will negotiate these details as part of future Operations Agreements.

2.2 LRO OPERATIONAL GROUND SYSTEM The LRO orbiter monitoring and control functions of the GS are performed within the LROMOC by the Mission Operations Team (MOT). The ITOS GS element typically performs itsfunctions in real time during an LRO spacecraft ground contact and is located within the real-time portion of the MOC. The LRO GS architecture is depicted in Figure 2–4. LRO mission planning, command load generation, trend analysis, and attitude determinationfunctions of the GS also are performed within the LRO MOC by the LRO MOT. These elementsperform their functions using data from prior spacecraft passes and other sources. The productsof these elements may be used during a LRO spacecraft ground contact and are located withinthe offline portion of the MOC. This set of GS elements that support both real-time and offline functionality are defined andidentified in the following table:

Table 2-1 MOC Functional Component Information

Functional Element Component Provider Section Reference

Telemetry and Command ITOS GOTS – GSFC 584 Section 2.2.1

Mission Planning FlexPlan COTS – GMV Section 2.2.4

Trending and Analysis ITPS GOTS – GSFC 583 Section 2.2.6

Data Processing System ITOS/DPS GOTS – GSFC 584 Section 2.2.2

Data Management System DMS GOTS – GSFC 584 Section 2.2.3

Monitoring and Alert System ATTENTION COTS – Attention SW, Inc Section 2.2.7

AttitudeDeterminationGroundSystem

MOC-ADSAGS GOTS – Code 595 Section 2.2.5

2.2.1 ITOS-Supported Real-time Telemetry and Commanding The real-time telemetry and command portion of ITOS receives virtual channel (VC) telemetryidentified as VC0 and VC1. ITOS processes the engineering data and displays it to the MOT formonitoring the health and safety of the LRO spacecraft. ITOS processes the VC0 data andgenerates attitude data files for use by the MOC-ADS. ITOS archives engineering data files forlater trending analysis by ITPS. ITOS performs the following real-time functions in support ofthe spacecraft health and safety:• Receive command files from FlexPlan


2-8



• Performs real-time commanding using the received files from the FlexPlan• Transmits real-time data packets to instrument ground support equipment (IGSE) during

L&EO• Transmits real-time packet data to the various science centers• Performs real-time commanding• Generates log files for spacecraft health and safety monitoring by Attention• Subsets the data packets into usable files for ingest by the ITPS• Provides attitude data packets to the M OC-ADSAGS component or use in the single

onboard computer (SOBC) attitude verification determination and to generate new gyrocalibration tables

2.2.2 Data Processing SystemITOS provides the functionality of the Data Processing System (DPS); this is the primaryinterface to the station front end units for receiving and processing files transmitted using theCCSDS File Delivery Protocol (CFDP). The DPS is responsible for ensuring a reliable transferof data and that the data received on the ground is in the same format in which it was stored onthe spacecraft.There will be two active units, one at the station for high data rate capture and one at the MOCfor low data rate capture and uplink of table and memory files. The system located within theLRO MOC is identified as the MOC Data Processing System (MDPS); the system resident at theWhite Sands station is referenced as the station DPS (SDPS) or the WS1-DPS system. Thestation and MOC DPS are both setup and controlled by the ITOS system at the MOC and allcommanding is coordinated and funneled through the ITOS for uplink to the spacecraft.The WS1 DPS will provide temporary data storage and deliver data products to the DataManagement System after processing is complete for a file. The WS1 DPS can receive thescience data in any virtual channel (nominally it is commanded to be downlinked in either VC2or VC3, but the spacecraft could be commanded to downlink the data in any VC), and performsdata accountability. The MOC DPS nominally receives spacecraft housekeeping files on VC1;however, the spacecraft can be commanded to downlink science data in VC1 also. ITOS/DPSthen distributes the data to the ITOS/DMS component for eventual transmission to theappropriate science team for further data analysis.2.2.3 Data Management SystemITOS also provides the functionality for the Data Management System (DMS). This componentprovides the data file archiving, data file dissemination, and provides a mechanism that can beused to track the delivery of data file products, which the LRO MOC transfers to the other LROground segment elements, such as the Ground Networks, the SOCs and the PDS. ITOS/DMSreceives the corresponding files from another source, such as FDF or the ITOS/DPS components(for VC1, VC2, and VC3 data files) and performs data transfer and accountability to ensure thatthe files are delivered to the correct recipient and delivered error free.


2-9



2.2.4 Mission Planning SystemFlexPlan was chosen as the mission planning system; it provides the short term daily planningand the long term projected planning for mission operations. FlexPlan receives science planninginformation from the science centers, maneuver planning data from FDF, and spacecraft healthand safety commands from the operations team. The LRO mission planner uses the FlexPlan togenerate and maintain daily planning activities as well as spacecraft command files that areforwarded to the ITOS for uplink to the spacecraft.2.2.5 Mission Operations Center – Attitude Determination Ground SystemThe MOC-ADSAGS provides the attitude determination validation and attitude sensorcalibration; it is a COTS/GOTS system developed by the Flight Dynamics Branch at GSFC. Itreceives the on-board attitude quaternion data from the LRO spacecraft via ITOS/DMS,performs sensor calibration, applies biases and misalignment information to the data, andvalidates the on-board calculated attitude solutions from the spacecraft.The MOC-ADSAGS creates the command data for any orbiter off-nadir slews. One suchexample is to support the LROC instrument slews for LOLA, LROC, or Mini-RF or for slews tosupport spacecraft maneuvers. LROC sends a file to the MOC. The MOC-ADSAGS elementreceives the data file and generates a slew plan; this slew is eventually sent to MPS for ingestionand the creation of the daily command load. Also, itThe AGS handles more than just LROCslew requests from the various science centerss; it also provides slew inputs for station-keepingmaneuvers and momentum management requests.

2.2.6 Trending and Analysis SystemThe LRO Ground System and Operations team choose the Integrated Trending and PlottingSystem (ITPS) was chosen as the trending system; it provides the capability to ingest, store,analyze and display spacecraft health and safety data. ITPS will ingest and archive all missionhousekeeping and engineering data to perform full data analysis and will also process the data toprovide a reduced resolution data containing min/max/mean & standard deviation.

2.2.7 Monitoring and Alert SystemThe LRO Ground System and Operations team choose the Attention COTS product was chosenas the Monitoring and Alert System. This system is resident in the LRO MOC and it provides acomprehensive solution for spacecraft and ground system monitoring. The system interfaceswith all MOC ground components, monitoring system events and software tasks. Uponrecognizing anomalous events, the MAS initiates the pre-defined notification and reportingprocedures are in place to ensure that a proper response is received. and The MAS ensures thatdata is are accumulated to support the MOT in their research activities and to assists the MOT tocorrect the anomalous behavior. For spacecraft supports the monitoring system creates passsummaries to keep a record of all supports including commands sent; procedures executed, andspecified event messages. The monitoring system compares entries in these pass log files againsta predefined set of limits and checks. If an event or data value is flagged as a problem, themonitoring system issues a notification to one of a selected group of operations personnel of a


2-10



spacecraft anomaly and providing an informative, textual message identifying the anomalysituation.

2.3 FLIGHT DYNAMICS FACILITY The FDF provides the prime support for all orbit determination and generation of acquisitiondata. The FDF is located in Building 28 at GSFC. During all phases of the LRO mission, the FDF receives the station-tracking data, which includestwo-way Doppler tracking, laser ranging data, and ranging data. FDF determines the spacecraftorbit and generates predicted and definitive spacecraft ephemeredes. The predicted ephemeris isused to provide acquisition data to all ground stations. FDF will supply the operations team withall mission planning aids.The FDF provides processing and control for all maneuvers and generates the trajectorymaneuver commands for all mission phases.

2.4 MISSION OPERATIONS TEAMThe MOT personnel are responsible for managing the health and safety of the spacecraftfollowing initial acquisition. They are the focal point of LRO GS operations during the life ofthe mission. In this capacity, they• Coordinate the various operational entities• Conduct operational tests with the spacecraft during the prelaunch phase• Conduct operational testing of the LRO MOC facility systems• Lead the GS operations efforts for the life of the mission2.5 FLIGHT SOFTWARE MAINTENANCE FACILITY The Flight Software and Maintenance Facility (FSMF) interfaces with the LRO program’s I&TGSE system. It is responsible for maintaining the onboard flight software (FSW) startingapproximately 60 days after launch until the end of the mission.2.6 LRO SPACE COMMUNICATIONS NETWORK The LRO mission requires support from a variety of networks identified as the SpaceCommunications Network (SCN):

1. The Ka and S-Band antennas located at WS1 will provide the prime station support forthe LRO mission.

2. A second network will provide commercial S-band support for the LRO mission. TheLRO mission contracted this support to the Universal Space Network (USN). The USNNetwork Management Center (NMC) is located in Horsham, Pennsylvania. For theLRO mission, USN uses two prime remote ground stations (RGSs) located at Dongara,Australia and Weilham, Germany. USN maintains two backup stations to support theLRO mission; and these stations are located at South Point, Hawaii, and ; Kiruna,Sweden.

3. The DSN, operated by the JPL located in Pasadena, California, maintains three stationsat Goldstone, California; Madrid, Spain; and Canberra, Australia. DSN is designated for


2-11



emergency/backup support for telemetry, tracking, and command interface during theinitial acquisition, during any orbit maneuvers, or at any other times when a spacecraftemergency is identified.

4. Laser Ranging facility, which is located in Greenbelt, Maryland, provides one-way lasertime of flight data and supports, through the LOLA SOC, the development of animproved lunar gravity model.

The Space Network (SN) will be used for launch support and for post separation coverage. TheSN shall provide S-band (DG1 mode 1 or 2) telemetry and command services post separationthrough the first two hours of the mission.


3-1



3.0 LRO GS EXTERNAL INTERFACE PRODUCT SYNOPSIS

This section provides a listing of all external products used by, generated by, or stored by the LRO MOC. Table 3-1 provides a comprehensivelisting of all LRO external interfaces defined to date. This table reflects the product name, identifies who created the product and who uses theproduct, and provides a cross-reference to a DMR identifier to track where this interface product originates and who uses this interface productwithin their processing flow. It also provides a mapping to another document section in which a user can lookup more details regarding a product.

Table 3-1 LRO External Interface Products Cross Reference

Destination(s)

No. ID Product Name Source

CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN

SectionReference DMR Reference

1 CRaTER-1CRaTER LROOperations ActivityRequest

CRaTER _ Section4.3.1.1

DMR-51, DMR-218,DMR-77, DMR-573

2 CRaTER-2 CRaTER InstrumentReset Timeline CRaTER _ Section

4.3.1.2DMR-51, DMR-218,DMR-77, DMR-573

3 DLRE-1DLRE LROOperations ActivityRequest

DLRE _ Section4.3.2.1

4 DLRE-2 DLRE FSW Loads DLRE _ Section4.3.2.2

pgf

Highlight

CRaTER SOC to MOC deliverables


3-2



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


5 DSN-1 DSN Tracking Data DSN _ Section4.2.3.1

6 DSN-2 Real-Time VC0telemetry data DSN _ Section

4.2.3.2

7 DSN-3 Real-Time VC1telemetry DSN _ Section

4.2.3.5

8 DSN-4 DSN Station StatusPackets DSN _ Section

4.2.3.6

9 DSN-5 Archived VC0Telemetry Data DSN _ Section

4.2.3.3

10 DSN-6 Archived VC1Telemetry Data DSN _ Section

4.2.3.4

11 FDF-1AttitudeDeterminationVerification Report

MOC/ADS _ Section4.1.3.1 DMR-591

12 FDF-2 Attitude Slew Plans MOC/ADS _ Section4.1.3.2 DMR-592


3-3



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


FDF/OD _1311 FDF-3 LRO Beta Angle

Predict File MOC/DMS _ _ _ _ _ _ _Section4.1.2.2 DMR-594

1412 FDF-4 LRO Definitive

Ephemeris File FDF/OD _ Section4.1.2.3 DMR-595

1513 FDF-5 DSN Site Acquisition

Data FDF/OD _ Section4.1.1.2 DMR-596

1614 FDF-6 SCN Station

Acquisition Data FDF/OD _ _ Section4.1.1.1 DMR-571, DMR-604

1715 FDF-7 Laser Ranging Site

Prediction Data FDF/OD _ Section4.1.1.3 DMR-597

1816 FDF-8 Space Network

Acquisition Data FDF/OD _ Section4.1.1.4

1917 FDF-9 Ground Station HGA

View Period Predicts FDF/OD _ _ Section4.1.2.1 DMR-598

2018 FDF-10 Ground Station Omni

View Period Predicts FDF/OD _ _ Section4.1.2.1


3-4



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


21 FDF-11 Gyro Calibration Data MOC/ADS _ Section4.1.3.3 DMR-609

22 FDF-12 HGA CalibrationData MOC/ADS _ Section

4.1.3.4 DMR-564

FDF/OD _231

9 FDF-13

Lunar OrbitAscending andDescending NodePredicts MOC/DMS _ _ _ _ _ _ _

Section4.1.2.6 DMR-599

FDF/OD _2420 FDF-14

Lunar OrbitTerminator CrossingPredicts MOC/DMS _ _ _ _ _ _ _


FDF/OD _252

1 FDF-15 Mission EclipsePredicts

MOC/DMS _ _ _ _ _ _


2622 FDF-16 Lunar Ephemeris FDF/OD _ Section

4.1.2.9 DMR-602


3-5



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


2723 FDF-17 Orbiter Thruster

Maneuver Plans FDF/Man _ Section4.1.2.11 DMR-603

2824 FDF-18 Post-Separation

Report FDF/OD _ Section4.1.2.13

DMR-606

FDF/Man _2925 FDF-19 Orbiter Post

Maneuver Report MOC/DMS _Section4.1.2.12 DMR-605

3026 FDF-20 Predicted LRO

Ephemeris File FDF/OD _ Section4.1.2.14 DMR-607

FDF/OD _3127 FDF-21 Predicted Lunar

Ground Track File MOC/DMS _ _ _ _ _ _ _Section4.1.2.15 DMR-608

FDF/OD _3228 FDF-22 Definitive Lunar

Ground Track File MOC/DMS _ _ _ _ _ _ _Section4.1.2.16

3329 FDF-23 LRO State Vector

Table FDF/OD _ Section4.1.2.10 DMR-613


3-6



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


34 FDF-24 Star TrackerCalibration data MOC/ADS _ Section

4.1.3.5 DMR-611

3530 FDF-25 Thruster Calibration

DataMOC/ADSFDF/Man _ Section

4.1.2.201.1 DMR-610

3631 FDF-26

LRO MomentumManagement UnloadPlan

FDF/ADSMan _ Section

4.1.2.211.1 DMR-593

37 FDF-27 Star TrackerOccultation Report FDF/ADS _ Section

4.1.3.8DMR-612

FDF/OD _383

2 FDF-29 LRO DefinitiveSPICE SPK File MOC/DMS _ _ _ _ _ _ _

Section4.1.2.4

FDF/OD _393

3 FDF-30 LRO PredictiveSPICE SPK File MOC/DMS _ _ _ _ _ _ _

Section4.1.2.5


3-7



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


34 FDF-31 HGA/SA Fixed offsetSPK

FDF/OD

MOC/DMS _ _ _ _ _ _ _ _Section 1.1

MOC/DMS _ _ _ _ _ _ _

37 FDF-34SPICE Predicted CK(Predicted S/COrientation)

FDF _Section 1.1

FDF _ _423438 FDF-36

FDF ReprocessedSPICE DefinitiveSPK Ephemeris Data MOC/DMS _ _ _ _ _ _ _

Section4.1.2.18

FDF _433539 FDF-37 Solar Conjunction

File MOC/DMS _Section4.1.2.19

443640 WS1-1 WS1 Station Status

Packets WS1 _ Section4.2.1.10

453741 GNSO-1 SCN Support

Schedules WOTIS _ Section4.2.1.1


3-8



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN



Schedule Report WOTIS _ _ _ Section4.2.1.2

WS1 _473943 WS1-2 WS1 Weather Data

MOC/DMS _ _Section4.2.1.11

484044 WS1-3 Ka-Band VC3

telemetry WS1 _ Section4.2.1.12



WS1 _ _504246 WS1-5 WS1 Raw Tracking

Data MOC/DMS _Section4.2.1.3

514347 WS1-6 Real-time VC0




534549 WS1-8 Ka-Band RF Receiver

Data WS1 _ Section4.2.1.14


3-9



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


544650 WS1-9 SDPS CFDP Status

Packets WS1/SDPS _ Section4.2.1.15

554751 WS1-10 Archived VC0

telemetry data WS1 _ Section4.2.1.4







595155 WS1-14 VC2 Housekeeping

telemetry files WS1/SDPS _ Section4.2.1.16

605256 WS1-15

VC2 FSW telemetryfilesPost PassSummary Report

WS1/SDPS _ Section4.2.1.17

615357 WS1-16 VC3 Measurement

telemetry files WS1/SDPS _ Section4.2.1.18


3-10



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


625458 WS1-17 Event Logs WS1/SDPS _ Section

4.2.1.19

635559 WS1-18 System Logs WS1/SDPS _ Section

4.2.1.20

6456 WS1-19 SDPS CFDP PDU WS1/SDPS _ Section

4.2.1.21

655760 USN-1 USN Station Status

Packets USN _ Section4.2.2.2

USN _665861 USN-2 USN Weather Data

MOC/DMS _ _Section4.2.2.3

USN _ _675962 USN-3 Raw Tracking Data

Files MOC/DMS _Section4.2.2.1

686063 USN-4 Real-time VC0 orbiter

telemetry USN _ Section4.2.2.4


3-11



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


696164 USN-5 Real-time VC1 orbiter

telemetry USN _ Section4.2.2.5

706265 USN-6 Archived VC0

telemetry data USN _ Section4.2.2.6


telemetry data USN _ Section4.2.2.7

726467 KSC-1 Real-time VC0 orbiter

telemetry KSC _ Section4.6.1.1

736568 KSC-2 Real-time VC1 orbiter

telemetry KSC _Section4.6.1.24.6.1.1

746669 KSC-3 Archived VC0

telemetry data KSC _ Section4.6.1.3






3-12



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN




787073 SN-1 Real-time VC0

Orbiter Telemetry SN _Section4.2.4.14.2.4.14.2.5.1

79717483

SN-2 Archived VC0 OrbiterTelemetry SN _

Section4.2.4.24.2.4.24.2.5.2

817275 LAMP-1

LRO OperationsLAMP ActivityRequest

LAMP _ Section4.3.3.1

85 LAMP-2 LAMP HV commandsequence LAMP _ Section

4.3.3.2

837376 LAMP-3 LAMP Instrument

FSW Loads LAMP _ Section4.3.3.2

847477 LV-1 Launch Vehicle Post-

Sep Vector

LV, via KSCLaunchSupportTeam

_ Section4.6.1.7


3-13



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


857578 LEND-1

LRO OperationsLEND ActivityRequest

LEND _ Section4.3.4.1

867679 LOLA-1

LRO OperationsLOLA ActivityRequest

LOLA _ Section4.3.5.1

LOLA _ _877780 LOLA-2 LOLA Gravity Model

DMS _Section4.3.5.2

887881 LOLA-3 LOLA Instrument

FSW Loads LOLA _ Section4.3.5.3

LOLA _ _897982 LOLA-4 LOLA Processed OD

information DMS _Section4.3.5.4

908083 LOLA-5 LOLA Target Request LOLA _ Section

4.3.5.5

918184 LROC-1 LRO Operations

Activity Request LROC _ Section4.3.6.1


3-14



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


928285 LROC-21

LROC InstrumentInitializationCommand Sequence

LROC _ Section4.3.6.2

938386 LROC-32 LROC Command

Timeline LROC _ Section4.3.6.3

948487 LROC-43 LROC Target Request LROC _ Section

4.3.6.4

958588 Mini-RF-1 LRO Operations

Activity Request Mini-RF _ Section4.3.7.1

968689

Mini-RF-21 Mini-RF Load Files Mini-RF _ Section

4.3.7.2

978790

Mini-RF-32

Mini-RF CommandTimeline Mini-RF _ Section

4.3.7.3

988891 Mini-RF-4 Mini-RF Target

Requests Mini-RF _ Section4.3.7.4

998992 MOC-1 SDPS CFDP Control MOC/ITOS _

Section4.5.3.44.5.3.44.5.3.6


3-15



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


100909

3MOC-2 SPICE SCK – Clock

Correlation File MOC _ _ _ _ _ _ _ _ Section4.5.1.2

101919

4MOC-3 CRaTER - Spacecraft

HK Data File MOC/DMS _Section4.5.1.104.5.1.11.3

102929

5MOC-4 CRaTER HK Data

Files MOC/DMS _Section4.5.1.114.5.1.11.4

103939

6MOC-5

CRaTER RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.11.5

104949

7MOC-6 CRaTER Real-time

VC0 HK data MOC/ITOS _Section4.5.1.144.5.1.11.6

105959

8MOC-7 Daily Command Load

Report MOC/DMS _ _ _ _ _ _ _ Section4.5.1.1

10696 MOC-62 RTS Command Load

Report MOC/DMS _ _ _ _ _ _ _ Section4.5.1.17

pgf

Highlight

CRaTER instrument data


3-16



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


107979

9MOC-8 DLRE - Spacecraft

HK Data File MOC/DMS _Section4.5.1.104.5.1.12.4

10898100

MOC-9 DLRE HK Data Files MOC/DMS _Section4.5.1.114.5.1.12.5

10999101

MOC-10DLRE RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.12.6

110100102

MOC-11 DLRE Real-time VC0HK data MOC/ITOS _

Section4.5.1.144.5.1.12.7

111101103

MOC-12 LAMP - SpacecraftHK Data File MOC/DMS _

Section4.5.1.104.5.1.13.4

112102104

MOC-13 LAMP HK Data Files MOC/DMS _Section4.5.1.114.5.1.13.5


3-17



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


113103105

MOC-14LAMP RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.13.6

114104106

MOC-15 LAMP Real-timeVC0 HK data MOC/ITOS _

Section4.5.1.144.5.1.13.7

115105107

MOC-16 LEND - SpacecraftHK Data File MOC/DMS _

Section4.5.1.104.5.1.14.5

116106108

MOC-17 LEND HK Data Files MOC/DMS _Section4.5.1.114.5.1.14.6

117107109

MOC-18LEND RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.14.7

118108110

MOC-19 LEND Real-time VC0HK data MOC/DMS _

Section4.5.1.144.5.1.14.8


3-18



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


119109111

MOC-20 LOLA - SpacecraftHK Data File MOC/DMS _

Section4.5.1.104.5.1.15.5

120110112

MOC-21 LOLA HK Data Files MOC/DMS _Section4.5.1.114.5.1.15.6

121111113

MOC-22LOLA RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.15.7

122112114

MOC-23 LOLA Real-time VC0HK data MOC/ITOS _

Section4.5.1.144.5.1.15.8

123113115

MOC-24 LROC Real-time VC0HK data MOC/ITOS _

Section4.5.1.144.5.1.16.9

124114116

MOC-25 LROC - SpacecraftHK Data File MOC/DMS _

Section4.5.1.104.5.1.16.6


3-19



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


125115117

MOC-26 LROC HK Data Files MOC/DMS _Section4.5.1.114.5.1.16.7

126116118

MOC-27LROC NAC RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.16.8

127117 MOC-39

LROC WAC RawMeasurement DataFiles

MOC/DMS _ Section4.5.1.12

128118119

MOC-28 Mini-RF - SpacecraftHK Data File MOC/DMS _

Section4.5.1.104.5.1.17.8

129119120

MOC-29 Mini-RF HK DataFiles MOC/DMS _

Section4.5.1.114.5.1.17.9

130120121

MOC-30 Mini-RF OperationsOpportunity MOC _

Section4.5.1.154.5.1.17.10


3-20



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


131121122

MOC-31Mini-RF RawMeasurement DataFiles

MOC/DMS _Section4.5.1.124.5.1.17.11

132122123

MOC-32 Mini-RF Real-timeVC0 HK data MOC/ITOS _

Section4.5.1.144.5.1.17.12

133123124

MOC-33 SPICE Event kernel MOC/DMS _ _ Section4.5.1.3

134124125

MOC-34SCN Real-timeOrbiter Commands(WS1 and USN)

MOC/ITOS _ _ Section4.5.3.1

135125126

MOC-35 DSN Real-Timeorbiter commands MOC/ITOS _ Section

4.5.3.2

136126127

MOC-36 SN Real-Time orbitercommands MOC/ITOS _ Section

4.5.3.3


3-21



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


137127128

MOC-37 Commands to KSC MOC/ITOS _ Section4.6.2.2

138128129

MOC-38 Telemetry to KSC MOC/ITOS _ Section4.6.2.1

_139129130

MOC-3940 SPICE FK – FrameKernels

MultipleLRO Groups _ _ _ _ _ _ _ _

Section4.5.1.4

AGS _ _140141141130131

MOC-41SPICE Predicted CK(Predicted S/COrientation) MOC/DMS _ _ _ _ _ _ _

Section4.5.1.5

AGS _142131132

MOC-42SPICE Definitive CK(Definitive S/COrientation) MOC/DMS _ _ _ _ _ _ _

Section4.5.1.6

AGS _143132133

MOC-43 SPICE DefinitiveHGA Orientation CK MOC/DMS _ _ _ _ _ _ _

Section4.5.1.7


3-22



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


AGS _144133134

MOC-44 SPICE Definitive SAOrientation CK MOC/DMS _ _ _ _ _ _ _

Section4.5.1.8

TBR _145134 MOC-45 HGA/SA Fixed Offset

Frames MOC/DMS _ _ _ _ _ _ _

Section4.5.1.9

146135137

MOC-46 CRaTER HK MetaSummary Report DMS _ Section

4.5.1.13

147136138

MOC-47CRaTERMeasurement MetaSummary Report

DMS _ Section4.5.1.13

148137139

MOC-48 DLRE HK MetaSummary Report DMS _ Section

4.5.1.13

149138140

MOC-49DLRE MeasurementMeta SummaryReport


pgf

Highlight

CRaTER-specific reports


3-23



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


150139141

MOC-50 LAMP HK MetaSummary Report DMS _ Section

4.5.1.13

151140142

MOC-51LAMP MeasurementMeta SummaryReport


152141143

MOC-52 LEND HK MetaSummary Report DMS _ Section

4.5.1.13

153142144

MOC-53LEND MeasurementMeta SummaryReport


154143145

M)C-54 LOLA HK MetaSummary Report DMS _ Section

4.5.1.13

155144146

MOC-55LOLA MeasurementMeta SummaryReport



3-24



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


156145147

MOC-56 LROC HK MetaSummary Report DMS _ Section

4.5.1.13

157146148

MOC-57 LROC NAC MetaSummary Report DMS _ Section

4.5.1.13

158147149

MOC-58 LROC W+AC MetaSummary Report DMS _ Section

4.5.1.13

159148150

MOC-59 Mini-RF HK MetaSummary Report DMS _ Section

4.5.1.13

160149151

MOC-60Mini-RFMeasurement MetaSummary Report


161150 MOC-61 PDS NAIF Dataset

Archive DMS _ Section4.5.1.16

162151152

FSWM-1 Orbiter FSW LoadFiles FSWM _ Section

4.4.1.1


3-25



Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

CDDIS

MDPS

MOC/DMS

MOC/ITOS

NAIF/PDS

FDF

DSN

SCN

SDPS

SCN/GNSO

USN

SN


JPL/NAIF _163152153

NAIF-1 SPICE Planetary SPKMOC/DMS _ _ _ _ _ _ _

Section4.5.4.1

JPL/NAIF _164153154

NAIF-2 SPICE LSK (LeapSecond Kernel) MOC/DMS _ _ _ _ _ _ _

Section4.5.4.2

JPL/NAIF _165154 NAIF-3

SPICE Binary PCK(High Precision LunarOrientation) MOC/DMS _ _ _ _ _ _ _

Section4.5.4.3

JPL/NAIF _166155156

NAIF-4 SPICE Binary PCKMOC/DMS _ _ _ _ _ _ _

Section4.5.4.4


4-1



4.0 LRO GROUND SYSTEM EXTERNAL INTERFACES AND PRODUCTFor the products defined within this section, Table 4-1 provides the high-level details regardingproduct information; specifically for the file duration or file time span, volume estimates of thedata file and the file delivery protocols and mechanisms.

This table also provides the quick section reference so that users can easily reference the specificsection to review for more informational details. The LRO MOC supports 2 standard deliveryprotocols to support data delivery to/from the MOC.The LRO MOC uses a standard TCP/IP socket connection to support the transfer of real-timetelemetry or commands or other real-time status information; the LRO MOC issues the socketconnection and will retry these connections a configurable number of times in the event of anydropped sockets.The LRO MOC uses a secure copy (scp) protocol support the secure and reliable transfer of filedata products. For the scp option the LRO MOC will provide the Hostname, Pathname, andUSERID and Shared Keys to the external entities that are required to transfer files into the MOC.The MOC normally would prefer to initiate the file transfer (either scp pull or scp push), but thisoption might not always be the best option. In instances where the SOCs are transferring files tothe MOC, they would perform the SCP push option

pgf

Note

External sites receiving data from the MOC via SCP must also provide the MOC with hostname, pathname, userid, and shared keys.

pgf

Note

The origin of each product is defined, but its destination isn't always so clear. I recommend adding one table for each recipient, e.g., MOC, NAIF, each SOC, DSN, etc., listing the complete set of products coming from, and going to that entity.


4-2



Table 4-1 LRO Product Summary Information

No. ID Product Name SectionReference Time span Volume Delivery Mechanism and File

Conventions

1 CRaTER-1CRaTER LROOperationsActivity Request

Section4.3.1.1

Valid until the next load isuplinked to the spacecraft.

Variable size based on typesof commands

The file is electronically delivered to the MOCuser via the secure copy protocol. See above forscp options and detailsDelivery date/time is TBR based on when theCRaTER SOC needs to submit the LROOperations Activity Request; to support uplinkon the same day, the SOC should deliver the fileNo later than noon time (local) Eastern time.

2 CRaTER-2CRaTERInstrument ResetTimeline

Section4.3.1.2

Valid until the next load that isuplinked to the spacecraft.


The file is electronically delivered to the MOCvia the secure copy protocol. See above for scpoptions and detailsDelivery date/time is based on when theCRaTER SOC needs to submit the InstrumentReset Timeline; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern time.TBR

3 DLRE-1LRO OperationsDLRE ActivityRequest

Section4.3.2.1

Valid until the next ActivityRequest is uplinked to thespacecraft.


The file is electronically delivered to the MOCvia the secure copy protocol. See above for scpoptions and detailsDelivery date/time is based on when the DLRESOC needs to submit the LRO OperationsActivity Request; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern time.TBR.

pgf

Highlight

CRaTER SOC to MOC deliverables


4-3




Conventions

4 DLRE-2 DLRE FSWLoads

Section4.3.2.2

The DLRE Instrument FSWLoad is active until the next loadis uplinked to the spacecraft.

TBR Variable – based onFSW Image being uploaded

The file is electronically delivered to the MOCvia the secure copy protocol. See above for scpoptions and detailsDelivery date/time is based on when the DLRESOC needs to submit the LRO OperationsActivity Request; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern time.TBR

5 DSN-1 DSN TrackingData

Section4.2.3.1

Five minutes intervals during astation contact

Variable size based onlength of passTBR

The file is electronically delivered to the MOCvia the secure copy protocol. Delivery date/timeis TBR. The DSN Tracking Data File isdelivered at the completion of the five minuteduration for each tracking file

6 DSN-2 Real-Time VC0telemetry data

Section4.2.3.2

Contains all spacecraft datadownlinked during the last real-time station contact.

TBR – Variable based onstation contact time anddownlinked data rate

This is the real-time data sent from the DSNstation to the LRO MOC facility via a standardreal-time TCP/IP socket connection

7 DSN-3 Real-Time VC1telemetry

Section4.2.3.5

Near real-time support(approximately 30 secondslatency).

TBR – Variable based onVCs being transmitted, datarate, and station contacttime

The file is electronically delivered to the MOCvia a TBR real-time TCP/IP socket connectionDelivery time is near real-time as the data arereceived at the DSN stationAs noted previously, the stations will performthe Reed-Solomon decoding of the data prior todelivery to the LRO MOC (VC0 – VC3)

8 DSN-4 DSN StationStatus Packets

Section4.2.3.6

Packet sent every second duringstation contact

The DSN Station StatusPackets is TBS bytes ofinformation for everypacket sent.

The station status packets are electronicallydelivered to the MOC via a real-time socketconnection.


4-4




Conventions

9 DSN-5 Archived VC0Telemetry Data

Section4.2.3.3

Contains archived real-timeOrbiter telemetry data

TBR –Variable, Bbased onreal-time Orbiter Datapreviously downlinkedduring station contact andbased on time duration thatthe LRO MOT requests forretransmissionFiles can be bounded basedon time limits, size limits,or command

The file is electronically delivered to the MOCvia the secure copy protocol, within 30 minutesof the completion of the DSN stationcontactDSN provides an off-line SLE socketconnect for the delivery of the Archived VC0telemetry data. The MOC issues a ReturnChannel Frames and specifies VC0 and astart/stop time period.

10 DSN-6 Archived VC1Telemetry Data

Section4.2.3.4

Contains archived VC1 Orbiterhousekeeping data

TBR –Variable, Bbased onindividual scienceinstrument and scienceHousekeeping filesVC1data previous downlinkedduring a station contact andbased on time duration thatthe LRO MOT requests forretransmissionFiles can be bounded basedon time limits, size limits,or command

The DSN provides an off-line SLE socketconnect for the delivery of the Archived VC1telemetry data. The MOC issues a ReturnChannel Frames and specifies VC0 and astart/stop time period.file is electronicallydelivered to the MOC via the secure copyprotocol, within 30 minutes of the completion ofthe DSN station contact

11 FDF-1

AttitudeDeterminationVerificationReport

Section 1.1

The MOC-ADS element createsthis file on a weekly basis usingall received data from that timespan.

TBRThe report is transferred electronically to theMOC’s Data Management System via TBRdelivery mechanism

12 FDF-2 Attitude SlewPlans Section 1.1 Valid for the upcoming slews TBR – based on number

and types of slews.The file is electronically delivered via the securecopy protocol Delivery date/time is TBR


4-5




Conventions

131113 FDF-3 LRO Beta Angle

PredictsSection4.1.2.2

The time span for this product isfor the next six (6) months. Itstarts at 0000 UTC of the nextday and contains predicted betaangles for the six (6) months.

TBR24 Kbytes for 180 daysof data

The file is posted to the FDF Product Center on amonthly basis (first day of the month), no laterthan noon (12:00 pm), local time (based on theEastern Time zone). The MOC uses the securecopy protocol to “get” the file.


Ephemeris FileSection4.1.2.3

The time span for this product isfor the previous seven (7) daysfrom 0000 UTC seven daysprior to 0000 UTC of the currentday.

TBR1143 Kbytes for 7 days

The file is posted to the FDF Product Center on aweekly basis (Wednesday of the week), no laterthan noon (12:00 pm), local time (based on theEastern Time zone). The MOC uses the securecopy protocol to “get” the file.

151315 FDF-5 DSN Site

Acquisition DataSection4.1.1.2

The time span for this product is28 days TBR

The FDF-generated file is electronicallydelivered to the DSN via the secure copyprotocol. Delivery date/time is TBR. FDFgenerates the file on a daily basis

161416 FDF-6 SCN Station


10 days of station contactsstarts at 0000Z for thesubsequent Monday

TBRINP2 product isapproximately 579 KbytesOEM product is TBR

The FDF-generated file is electronicallydelivered to the SCN user via a TBRmechanism. The file is generated on a weeklyschedule, nominally on the Wednesday of theweek, unless agreed upon by FDF. It will beready for delivery by 1400 Hours local time,EST.

171517 FDF-7

Laser RangingSite PredictionData

Section4.1.1.3

The time span for this product is10 days from 0000 Hours of thefirst day within the file to 0000Hours 10 days later.

TBR

The FDF-generated file is electronicallydelivered to the Crustal Dynamics DataInformation System (CDDIS) via the securecopy protocol.FDF delivers this file on a weekly basis(Wednesday of the week prior to the week inquestion)


4-6




Conventions

181618 FDF-8 Space Network


Time span is approximatelyL+24 Hours TBR

The FDF-generated file is electronicallydelivered to the WSC TDRSS SchedulingOffice

191719 FDF-9

Ground StationHGA ViewPeriod Predicts

Section4.1.2.1

30 28 days from starting at 0000Hours of the first day within thefile to 0000 Hours thirty dayslater

TBR96 Kbytes

The file is generated on a daily basis and postedto the FDF Product Center, no later than noonlocal time (based on the Eastern Time zone).The users electronically pull (TBR mechanism)to receive the file

201820 FDF-10

Ground StationOmni ViewPeriod Predicts

Section4.1.2.1

30 28 days from starting at 0000Hours of the first day within thefile to 0000 Hours thirty dayslater

TBR96 Kbytes

The file is generated on a daily basis and postedto the FDF Product Center, no later than noonlocal time (based on the Eastern Time zone).The users electronically pull (TBR mechanism)to receive the file

21 FDF-11 Gyro CalibrationData Section 1.1 Valid until the next gyro cal

function TBR

The file is generated on an as-needed basis anddelivered to the DMS System via a TBR deliverymechanismDelivery date/time is TBR

22 FDF-12 HGACalibration Data Section 1.1 Valid until the next HGA cal

function TBR

The file is generated on an as-needed basiswhenever the LRO High Gain Antennae iscalibrated and delivered to the DMS System viaa TBR delivery mechanismDelivery date/time is TBR

231923 FDF-13

Lunar OrbitAscending andDescendingNode Predicts

Section4.1.2.6

Contain seven (7) days of nodecrossing data for LROspacecraft scheduled beginningat 0000Z on the next subsequentday and stopping at 0000Zseven days later.

TBRData records every 1 minute

The file is posted to the FDF Product Center on adaily basis, no later than noon (12:00 pm), localtime (based on the Eastern Time zone).The MOC uses the secure copy protocol to “get”the file.


4-7




Conventions

242024 FDF-14

Lunar OrbitTerminatorCrossingPredicts

Section4.1.2.7

Contain seven (7) days ofterminator crossing data forLRO spacecraft scheduledbeginning at 0000Z on the nextsubsequent day and stopping at0000Z seven days later.



252125 FDF-15 Mission Eclipse

PredictsSection4.1.2.8

Contain ninety (90) days ofeclipse prediction data for LROspacecraft scheduled beginningat 0000Z on the next subsequentday and stopping at 0000Zninety (90) days later.

TBR – 90 days of missioneclipse predictsData records every 1 minute


262226 FDF-16 Lunar

EphemerisSection4.1.2.9

Contain seven (7) days of lunarposition and velocityinformation scheduledbeginning at 0000Z on the nextsubsequent day and stopping at0000Z seven days later.

TBR – 7 days lunarephemeris predictsdata records every 1 minute


272327 FDF-17 Orbiter Thruster

Maneuver PlansSection4.1.2.11

Thruster Maneuver Plan onlyvalid for the stated period withinthe plan

TBR

The file is posted to the FDF Product CenterTBR days before the planned maneuver, no laterthan noon (12:00 pm), local time (based on theEastern Time zone).The MOC uses the secure copy protocol to “get”the file.

282428 FDF-18 Post-Separation

ReportSection4.1.2.13

This report is generated within 2hours after the LRO separationfrom the launch vehicle.

TBR – 1Several (2-3) pageof ASCII text information

The file is posted to the FDF Product Center nolater than 2 hours after the LRO separation fromthe EELV.The MOC uses the secure copy protocol to “get”the file.


4-8




Conventions

292529 FDF-19

Orbiter PostManeuverReport

Section4.1.2.12

Report valid until the next LROthruster maneuver.

TBR – 1 page of ASCII textinformation detailing theinformation on the justcompleted Maneuver

The file is posted to the FDF Product Center nolater than 12 hours after the completion of thecurrent thruster maneuver.The MOC uses the secure copy protocol to “get”the file.

302630 FDF-20 Predicted LRO

Ephemeris FileSection4.1.2.14

Contains the next thirty seven(307) days of predictiveephemeris data from 0000Z ofthe next subsequent day outthrough an additional 30 days.

TBR

The file is posted to the FDF Product Center on aweekly daily basis (Wednesday of the week), nolater than noon (12:00 pm), local time (based onthe Eastern Time zone).The MOC uses the secure copy protocol to “get”the file.

312731 FDF-21

Predicted LunarGround TrackFile

Section4.1.2.15

Contains the next thirty seven(307) days of lunar ground trackdata from 0000Z of the nextsubsequent day out through anadditional 30 days.

TBR

The file is posted to the FDF Product Center on aweekly daily basis (Wednesday of the week), nolater than noon (12:00 pm), local time (based onthe Eastern Time zone).The MOC uses the secure copy protocol to “get”the file.

322832 FDF-22

Definitive LunarGround TrackFile

Section4.1.2.16

The time span for this product isfor the previous 24 hours from0000Z of the previous day to0000Z of the current day.

TBR


332933 FDF-23 LRO State

Vector TableSection4.1.2.10

Contains the next seven (TBR7)days of LRO State Vectors(centered at TBR 10 minuteincrements)

TBR



4-9




Conventions

34 FDF-24 Star TrackerCalibration data Section 1.1 Valid until the next Star Tracker

cal function TBR

The MOC-ADS-generated file is electronicallydelivered to the DMS element via the securecopy protocol.Delivery date/time is TBR.

353035 FDF-25 Thruster

Calibration DataSection4.1.2.201.1

Valid until the next Thruster calfunction

TBRThe MOC-ADS-generated file is electronicallydelivered to the DMS element via the securecopy protocol.Delivery date/time is TBR.

363136 FDF-26

LROMomentumManagementUnload Plan

Section4.1.2.211.1

LRO momentum managementUnload Plan only valid for theidentified time period

TBR

The MOC-ADS-generated file is electronicallydelivered to the DMS element via the securecopy protocol.Delivery date/time is TBR.

37 FDF-27Star TrackerOccultationReport

Section 1.1

Contains the next (TBR) days ofdata that identifies when the startracker is occulted by either themoon, earth or sun

TBR


38 FDF-28 Attitude SlewReport

Section4.1.3.2

Valid for the upcoming slews TBR – based on numberand types of slews.

The file is electronically delivered via the securecopy protocol Delivery date/time is TBR


SPICE SPK FileSection4.1.2.4

The time span for this product isfor the previous seven (7) daydaysperiod from 0000 UTC ofthe previous day to 0000 UTCof the current day.


The file is posted to the FDF Product Center on adaily weekly basis (on Wednesday of the week),no later than noon (12:00 pm), local time (basedon the Eastern Time zone).The MOC uses the secure copy protocol to “get”the file.


4-10




Conventions

403339 FDF-30 LRO Predictive

SPICE SPK FileSection4.1.2.5

The time span for this product isfor the next 28 days from 0000UTC of the current day to 0000UTC 28 days in the future.


The file is posted to the FDF Product Center on adaily weekly basis (On Wednesday), no laterthan noon (12:00 pm), local time (based on theEastern Time zone).The MOC uses the secure copy protocol to “get”the file.

40 FDF-31 HGA/SA Fixedoffset SPK Section 1.1

TBR TBR The FDF-generated file is electronicallydelivered to the user via the secure copyprotocol. Delivery date/time is TBR.

41 FDF-32SPICE GenericPCK (PlanetaryConstants)

Section4.1.2.17

TBR TBR The FDF-generated file is electronicallydelivered to the user via the secure copyprotocol. Delivery date/time is TBR.

42 FDF-33

SPICE BinaryPCK (High-Precision LunarOrientation)

Section4.1.2.17 TBR TBR

The FDF-generated file is electronicallydelivered to the user via the secure copyprotocol. Delivery date/time is TBR.

43 FDF-34SPICE PredictedCK (PredictedS/C Orientation)

Section 1.1TBR TBR The FDF-generated file is electronically

delivered to the user via the secure copyprotocol. Delivery date/time is TBR.

44 FDF-35

SPICEDefinitive CK(Definitive S/C,HGA, SAOrientation)

Section 1.1

TBR TBRThe FDF-generated file is electronicallydelivered to the user via the secure copyprotocol. Delivery date/time is TBR.


4-11




Conventions

463445 FDF-36

FDFReprocessedSPICEDefinitive SPKEphemeris Data

Section4.1.2.18

This file contains weekly filesfor the previous 3 months andprevious 12 months ofreprocessed FDF definitiveephemeris data;Weekly files are defined from aMonday (0000Z) through thenext Monday (0000Z)

TBR – each file contains 1-week of reprocesseddefinitive ephemerisdata records at 1 minute

FDF generates the file and places the file ontothe FDF Product Server; the MOC electronicallyreceives the set of files using the secure copyget; Delivery date and time are predicated on 3months after nominal mission begins and 12months after nominal mission begins

473546 FDF-37 Solar

Conjunction FileSection4.1.2.19

28 days starting at 0000 Hoursof the first day < 1 Kbytes

The file is generated on a weekly basis(Wednesday of the week) and posted to the FDFProduct Center, no later than noon local time(based on the Eastern Time zone). The userselectronically pull (TBR mechanism) to receivethe file

483649 WS1-1 WS1 Station

Status PacketsSection4.2.1.10

Contains a current station statusdata for the last 1 (TBR)seconds during the stationcontact

TBRStation Status Packets are delivered to the MOCevery 1 (TBR) seconds in real-time via a socketconnection to MOC – ITOS element


4-12




Conventions


SchedulesSection4.2.1.1

Covers the weekly stationcontacts from Monday, 00:00:00Z for the specified start date upthrough 23:59:59Z of the nextsubsequent Sunday date.The file may actually containone week plus one day to ensureconsistency from one schedulingperiod to the next.

TBR

GNSO electronically delivers schedule files is tothe MOC on a weekly basis via the secure copyprotocol.Delivery date is Thursday for the Strawman,Forecast, and Operations Schedule; /the deliverytime is TBR.

Operational schedule delivered on the Thursdaybefore the start of the week in question

The forecast schedule represents the time period14 days in advance and the Strawman schedulerepresents a time period 28 days in advance;each schedule covers a 7 day duration


Schedule ReportSection4.2.1.2

Covers the weekly stationcontacts from Monday, 00:00:00Z for the specified start date upthrough 23:59:59Z of the nextsubsequent Sunday date.

TBR

GNSO electronically delivers schedule files is tothe MOC on a weekly basis via email to theLRO MOC/MPS account.Delivery date is Thursday for the Strawman,Forecast, and Operations Schedule; the delivery/time is TBR.

Operational schedule delivered on the Thursdaybefore the start of the week in question

The forecast schedule represents the time period14 days in advance and the Strawman schedulerepresents a time period 28 days in advance

513952 WS1-2 WS1 Weather

DataSection4.2.1.11

Contains the weatherinformation that corresponds tothe time period of the stationcontactthe data are sampled andprovided at 1 minute intervals.

TBR

The file is electronically delivered to the MOCvia the secure copy protocol.Delivery is scheduled to occur within 20 minutesof the conclusion of the station contact.


4-13




Conventions


telemetrySection4.2.1.12

Contains science measurementdata files as defined within thecorresponding Data InstrumentICD.

TBR – Based on individualscience instrument filesFiles can be bounded basedon time limits, size limits,or command

The file is electronically delivered to the MOCvia the secure copy protocol, within 30 minutesof the completion of the WS1 station contact



Contains instrumenthousekeeping data files asdefined within thecorresponding Data InstrumentICD.

TBR – Based on individualscience Housekeeping filesFiles can be bounded basedon time limits, size limits,or command


544255 WS1-5 WS1 Raw

Tracking DataSection4.2.1.3

Tracking data correspond toreceived UTDF data from thelast 5 minutes (nominal case) orover the last hour (when data isare forwarded via real-timeconnection))

TBR – max time limit for afile is 5 minutes (nominalcase) or Hourly files asbackup when data is aretransmitted in R/T to FDF.

Data delivered either1) Real-time to FDF. (backup also has filescreated at hourly intervals) Real-time support isfor mission critical activities.

2) Files to both FDF and MOC every 5 minutes.The files are electronically delivered to the FDFand the MOC via the secure copy protocol,



The data is are delivered in nearreal-time to the LRO MOC as itis received by the station.

TBR – based on downlinkdata rate

The data are delivered electronically to the MOCvia a real-time socket connection; data aredelivered with near real-time of receipt at thestation (within TBD seconds)Stations perform the Reed-Solomon decoding ofthe VC0 data prior to delivery to the LRO MOC.


4-14




Conventions



The data is are delivered in nearreal-time to the LRO MOC as itis received by the station.



574558 WS1-8 Ka-Band RF

Receiver DataSection4.2.1.14

Corresponds to the last WS1station contact (AOS to LOS) TBR

The file is electronically delivered to the MOCand FDF via the secure copy protocol; , within30 minutes of the completion of the WS1 stationcontact

584659 WS1-9 SDPS CFDP


Contains a running summationof requested status data for thelast 60 second during the stationcontact

TBRStation Status Packets are delivered to the MOCevery 60 seconds in real-time via a socketconnection to MOC – ITOS element


telemetry dataSection4.2.1.4

Contains archived real-timeOrbiter

TBR – Based on Real-timeOrbiter Data downlinkedduring station contactFiles can be bounded basedon time limits, size limits,or command





TBR – Based on individualscience instrument andscience Housekeeping filesFiles can be bounded basedon time limits, size limits,or command



4-15




Conventions



Contains stored/archived scienceinstrument housekeeping datafiles as defined within thecorresponding Data InstrumentICD.





Contains stored/archived sciencemeasurement data files asdefined within thecorresponding Data InstrumentICD.



635164 WS1-14

VC2Housekeepingtelemetry files

Section4.2.1.16

Provides LRO Housekeepingdata files created and stored onboard since last station contact



645265 WS1-15

Post PassSummaryReportVC2FSW telemetryfiles

Section4.2.1.17

Provides FSW Telemetry filescreated and stored on-boardsince last station contactStationDPS status information fordownlinked files over the laststation contact

TBR – Based on individualscience instrument andscience Housekeeping filesFiles can be bounded basedon time limits, size limits,or commandVariable basedon number of files that theOrbiter downlinked duringthe last WS1 station contact



4-16




Conventions

655366 WS1-16

VC3Measurementtelemetry files

Section4.2.1.18

Provides LRO ScienceMeasurement data files createdand stored on board since laststation contact



665467 WS1-17 Event Logs Section

4.2.1.19 TBR TBR TBR

675568 WS1-18 System Logs Section

4.2.1.20 TBR TBR TBR

6856 WS1-19 SDPS CFDP-

PDUSection4.2.1.21

Only valid for current WS1station contact < 1 Kbyte UDP Socket connection to MOC – ITOS

element every 30 seconds

695769 USN-1 USN Station


Contains a current station statusdata for the last 5 (TBR)seconds during the stationcontact

TBRStation Status Packets are delivered to the MOCevery 5 (TBR) seconds in real-time via a socketconnection to MOC – ITOS element

705870 USN-2 USN Weather

DataSection4.2.2.3

Contains the weatherinformation that corresponds tothe time period of the stationcontactWeather data will be collected at5-minute intervals and deliveredin one file post pass.

TBR

The file is delivered electronically to the MOC,post-pass, via the secure copy (push) protocolover the Open IONetDelivery is scheduled to occur within 30 minutesof the conclusion of the station contact.

715971 USN-3 Raw Tracking

Data FilesSection4.2.2.1

Tracking data correspond toreceived UTDF data from thelast 5 minutes

TBR – max time limit for afile is 5 minutes (nominalcase)

Data Files delivered via the secure copy protocolto both FDF and MOC every 5 minutes. Via theOpen IONet


4-17




Conventions

726072 USN-4 Real-time VC0

orbiter telemetrySection4.2.2.4

The data is delivered in nearreal-time to the LRO MOC as itis received by the station.



736173 USN-5 Real-time VC1


The data is delivered in nearreal-time to the LRO MOC as itis received by the station.





Contains archived real-timeOrbiter telemetry data

TBR – Based on Real-timeOrbiter Data downlinkedduring station contactFiles can be bounded basedon time limits, size limits,or command

The file is electronically delivered to the MOCvia the secure copy protocolThe Archived VC0 Telemetry is provided viaSecure copy (pull by MOC) over the RestrictedIONET





The file is electronically delivered to the MOCvia the secure copy protocolThe Archived VC1 Telemetry is provided viaSecure copy (pull by MOC) over the RestrictedIONET

766476 KSC-1 Real-time VC0


Launch/Real-time or simulatedOrbiter VC0 telemetry

TBR – based on Real-timerates or simulated rates

Real-time data are electronically delivered to theMOC via a socket connection.

776577 KSC-2 Real-time VC1

orbiter telemetrySection4.6.1.24.6.1.1

Simulated Orbiter VC1telemetry

TBR – based on rates usedto support simulations



4-18




Conventions



Archived VC0 telemetry Orbiterdata corresponding to arehearsal or launch support

TBR – based file sizes The file is electronically delivered to the MOCvia the secure copy protocol.



Archived VC1 telemetry Orbiterdata corresponding to arehearsal or launch support




Archived VC2 telemetry forInstrument H/K datacorresponding to a rehearsal




Archived VC3 telemetry forInstrument measurement datacorresponding to a rehearsal


827082 SN-1

Real-time VC0OrbiterTelemetry

Section4.2.4.14.2.4.14.2.5.1

Real-time VC0 Orbitertelemetry during post-launchTDRSS contact

Based on 2Kbps Real-timerate


837183 SN-2

Archived VC0OrbiterTelemetry

Section4.2.4.24.2.4.24.2.5.2

Archived Orbiter VC0 datacorresponds to the length of theTDRSS contact

TBR – based on 2KbpsReal-time rates and lengthof TDRSS contact

The file is electronically delivered to the MOCvia the secure copy protocol.

847284 LAMP-1

LRO OperationsLAMP ActivityRequest

Section4.3.3.1

Activity Request active until thenext load is uplinked to thespacecraft; nominally daily orweekly instrument loads.

TBR – based on number ofcommands

The file is electronically delivered to the MOCvia the secure copy protocol,delivery date/time is based on when the LAMPSOC needs to submit the LRO OperationsActivity Request; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern timeTBR


4-19




Conventions

85 LAMP-2LAMP HVcommandsequence

Section4.3.3.2

HV Command Sequence activeuntil the next load is uplinked tothe spacecraft; nominally dailyor weekly instrument loads.


The file is electronically delivered to the MOCvia the secure copy protocol., delivery date/timeis TBR

867385 LAMP-3

LAMPInstrument FSWLoads

Section4.3.3.2

The LAMP Instrument FSWLoad is active until the next loadis uplinked to the spacecraft.

TBR – based on FSWImage being uploaded64Kbytes for a complete FSWTable Load

The file is electronically delivered to the MOCvia the secure copy protocol.,delivery date/time is based on when the LAMPSOC needs to submit the LAMP InstrumentFSW Load; to support uplink on the same day,the SOC should deliver the file No later thannoon time (local) Eastern timeTBR

877486 LV-1 Launch Vehicle

Post-Sep VectorSection4.6.1.7

File is delivered approximately30 minutes after spacecraftseparation

1 page text information

Via fax to FDF, at GSFC in Building 28, roomTBD.The fax telephone number is 301-286-xxxx).Backup mechanism is to directly phone the flightdynamic’s facility at 301-286-yyyy).

887587 LEND-1

LRO OperationsLEND ActivityRequest

Section4.3.4.1



The file is electronically delivered to the MOCvia the secure copy protocol,delivery date/time is TBR

897688 LOLA-1

LRO OperationsLOLA ActivityRequest

Section4.3.5.1



The file is electronically delivered to the MOCvia the secure copy protocol,delivery date/time is based on when the LOLASOC needs to submit the LRO OperationsActivity Request; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern timeTBR


4-20




Conventions

907789 LOLA-2 LOLA Gravity

ModelSection4.3.5.2

LOLA Gravity Model valid onlyupon delivery; only expectingone deliveryThe updated gravity modelgenerated every six months andis based on the previous sixmonths of Laser Rangingtransmit data and other trackingdata.

TBR – based on size andparameters for the newGravityModelApproximately 1Mbytes file size

The file is electronically delivered to the FDFand MOC via the secure copy protocol;delivery date/time is TBRdependent on whenLOLA SOC generates the file during the 3-4month window.

917890 LOLA-3

LOLAInstrument FSWLoads

Section4.3.5.3

The LOLA Instrument FSWLoad is active until the next loadis uplinked to the spacecraft.

TBR – based on FSWImage being uploaded

The file is electronically delivered to the MOCvia the secure copy protocol;delivery date/time is based on when the LOLASOC needs to submit the LOLA InstrumentFSW Load; to support uplink on the same day,the SOC should deliver the file No later thannoon time (local) Eastern timeTBR.

927991 LOLA-4

LOLAProcessed ODinformation

Section4.3.5.4

TBR SPK files in weekly arcsTBR –Variable based onsize and parameters for thesampling rate for the LOLAProcess OD data

The file is electronically delivered to the FDFand MOC via the secure copy protocol,delivery date/time is TBRweekly for thepreceding 7-days of Processed OD data.

938092 LOLA-5 LOLA Target

RequestSection4.3.5.5

LOLA Target Requests activeand valid only for the associatedtime period identified in thecommands

9 commands, which span a3 day interval since LOLArequests are similar toLROC concepts270 bytes per fileTBR –based on number ofcommands

The file is electronically delivered to the MOCvia the secure copy protocol;delivery date/time is based on when the LOLASOC needs to submit the LOLA TargetRequests; to support uplink on the same day, theSOC should deliver the file No later than noontime (local) Eastern timeTBR.


4-21




Conventions

948193 LROC-1 LRO Operations

Activity RequestSection4.3.6.1


Variable based on numberof commands

The file is electronically delivered to the MOCvia the secure copy protocol,delivery date/time is based on when the LROCSOC needs to submit the LRO OperationsActivity Request; to support uplink on the sameday, the SOC should deliver the file No laterthan noon time (local) Eastern time

958294 LROC-21

LROCInstrumentInitializationCommandSequence

Section4.3.6.2

LROC Instrument InitializationCommand Sequences arepreloaded before launch. Thereare 8 files that can be used toinitialize the LROC instrument.Each of the 8 load files could beused and remain on-board untilthey are replaced by a newinitialization file. ActivityRequest active until the nextload is uplinked to thespacecraft; nominally daily orweekly instrument loads.

Each LROC CommandInitialization File can be upto 256 Kbytes – based onthe LROC FSW DataICDTBR – based onnumber of commands

The file is electronically delivered to the MOCvia the secure copy protocol,once, prelaunch (required 2 months prior tolaunch, preferred 4 months prior to launch)Thefile is electronically delivered to theMOC via the secure copy protocol,delivery date/time is TBR

968395 LROC-32

LROC DailyCommandSequence

Section4.3.6.3

Daily Command Sequenceactive for 24 hours until the nextload is uplinked to thespacecraft.

TBR Variable – based onnumber of imagecommands and commandmnemonics

The file is electronically delivered to the MOCvia the secure copy protocol; delivery date/timeis TBR.LROC delivers this command sequencedaily, no later than noon time Eastern

978496 LROC-43 LROC Target

RequestSection4.3.6.4

LROC Target Requests activeand valid only for the timeassociated in the command load

9 commands, which span a3 day interval; consistentwith LROC, which can slewup to 3 times per day ~ 270bytes per file TBR – basedon number of commands

The file is electronically delivered to the MOCvia the secure copy protocol; LROC delivers thiscommand sequence daily, no later than noontime Eastern delivery date/time is TBR.


4-22




Conventions

988597 Mini-RF-1 LRO Operations

Activity RequestSection4.3.7.1


Variable – based on numberof commands

The file is electronically delivered to the MOCvia the secure copy protocol,delivery date/time is based on when the Mini-RFSOC needs to submit the Activity Request; tosupport uplink on the same day, the SOC shoulddeliver the file No later than noon time (local)Eastern time

998698

Mini-RF-12

Mini-RF LoadFiles

Section4.3.7.2

The Mini-RF Load File is activeuntil the next load is uplinked tothe spacecraft.


The file is electronically delivered to the MOCvia the secure copy protocol;delivery date/time is based on when the Mini-RFSOC needs to submit the Load File; to supportuplink on the same day, the SOC should deliverthe file No later than noon time (local) EasterntimeTBR.

100879

9

Mini-RF-23

Mini-RFCommandTimeline

Section4.3.7.3

Command Timeline active untilthe next load is uplinked to thespacecraft.

1-2 Kbytes TBR – based onnumber of commandsrequired to support timelineactivities

The file is electronically delivered to the MOCvia the secure copy protocol;delivery date/time is based on when the Mini-RFSOC needs to submit the Command Timeline; tosupport uplink on the same day, the SOC shoulddeliver the file No later than noon time (local)Eastern timeTBR.

10188100

Mini-RF-4 Mini-RF TargetRequests

Section4.3.7.4

Mini-RF Target Requests activeand valid only for the timeassociated in the command load

3 commands, which spanthe Mini-RF monthlyoperations~ 100 bytes per file

The file is electronically delivered to the MOCvia the secure copy protocol; Mini-RF deliversthis command sequence daily, no later than noontime Eastern

10289101

MOC-1 SDPS CFDPControl

Section4.5.3.44.5.3.44.5.3.6

CFDP Control messages are senton a regular scheduled timeperiod (similar to a heartbeattimer); one every TBD seconds

TBR Bytes

The CFDP Control delivered via a Real-timesocket connection to the MUE located at WS1stationCFDP Controls issued every TBR seconds


4-23




Conventions

10390102

MOC-2SPICE SCK –ClockCorrelation File

Section4.5.1.2

Valid for previous day’s clockupdates from 0000Z of theprevious day to 0000Z of thecurrent day. .

TBR< 50 Kbytes for primemission phase

The Clock Correlation file is electronicallydelivered to each SOC on a daily basis via thesecure copy protocoldelivery time is TBR.Clock Correlation file sent to each SOC

10491103

MOC-3CRaTER -Spacecraft HKData File

Section4.5.1.104.5.1.5.2

Data corresponds to the storeds/c housekeeping data, whichwas downlinked during the lastreal-time station contact

TBR – file size can bebased on time limits, filesize, or via commanddownlink

The file is electronically delivered to theCRaTER SOC via the secure copy protocoldelivery time is TBR.

10592104

MOC-4 CRaTER HKData Files

Section4.5.1.114.5.1.11.4

Data corresponds to the storedCRaTER s/c housekeeping data,which was downlinked duringthe last real-time station contact


The file is electronically delivered via the securecopy protocoldelivery date/time is TBR.

10693105

MOC-5CRaTER RawMeasurementData Files

Section4.5.1.124.5.1.11.5

Data corresponds to the storedCRaTER instrumentmeasurement data, which wasdownlinked during the last real-time station contact



10794106

MOC-6CRaTER Real-time VC0 HKdata

Section4.5.1.144.5.1.11.6

Data correspond to the near real-time at which the data werecollected during the currentstation contact.

Data volume is TBR; basedon data downlink rate andfilter table rates

The data are delivered electronically to theCRaTER SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

10895107

MOC-7 Daily CommandLoad Report

Section4.5.1.1

Contents of this file correspondto the current command loadfrom 0000Z of the previous dayto 0000Z of the current day.

Data volume is TBRvariable – based on thenumber of s/c andinstrument commands forthat daily activity set

The MOC electronically delivers this file to eachSOC via the secure copy protocol on a dailybasisDelivery date/time is TBR.

pgf

Highlight

CRaTER instrument data


4-24




Conventions

10996 MOC-62 RTS Command

Load ReportSection4.5.1.17

Contents of this file correspondto the current RTS commandloadLoad for a specific RTSsequence is valid until reloaded

Data volume is variable –based on the number ofRelative commands for thesequence

The MOC electronically delivers this file to eachSOC via the secure copy protocol on an as-needed basisDelivery date/time is noon local (Eastern), afterthe RTS load is approved and signed byoperations personnel

11097108

MOC-8DLRE -Spacecraft HKData File

Section4.5.1.104.5.1.12.4



The file is electronically delivered to the DLRESOC via the secure copy protocoldelivery time is TBR.

11198109

MOC-9 DLRE HK DataFiles

Section4.5.1.114.5.1.12.5

Data corresponds to the storedDLRE s/c housekeeping data,which was downlinked duringthe last real-time station contact



11299110

MOC-10DLRE RawMeasurementData Files

Section4.5.1.124.5.1.12.6

Data corresponds to the storedDLRE instrument measurementdata, which was downlinkedduring the last real-time stationcontact



113100111

MOC-11 DLRE Real-timeVC0 HK data

Section4.5.1.144.5.1.12.7



The data are delivered electronically to theDLRE SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

114101112

MOC-12LAMP -Spacecraft HKData File

Section4.5.1.104.5.1.7.1



The file is electronically delivered to the LAMPSOC via the secure copy protocoldelivery time is TBR.


4-25




Conventions

115102113

MOC-13 LAMP HK DataFiles

Section4.5.1.114.5.1.13.5

Data corresponds to the storedLAMP s/c housekeeping data,which was downlinked duringthe last real-time station contact



116103114

MOC-14LAMP RawMeasurementData Files

Section4.5.1.124.5.1.13.6

Data corresponds to the storedLAMP instrument measurementdata, which was downlinkedduring the last real-time stationcontact



117104115

MOC-15LAMP Real-time VC0 HKdata

Section4.5.1.144.5.1.13.7



The data are delivered electronically to theLAMP SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

118105116

MOC-16LEND -Spacecraft HKData File

Section4.5.1.104.5.1.14.5



The file is electronically delivered to the LAMPSOC via the secure copy protocoldelivery time is TBR.The MOC delivers the file data to both GSFCLEND SOC and to the University of ArizonaLEND SOC.

119106117

MOC-17 LEND HK DataFiles

Section4.5.1.114.5.1.14.6

Data corresponds to the storedLEND s/c housekeeping data,which was downlinked duringthe last real-time station contact


The file is electronically delivered via the securecopy protocolThe MOC delivers file data to both GSFC LENDSOC and to the University of Arizona LENDSOC.


4-26




Conventions

120107118

MOC-18LEND RawMeasurementData Files

Section4.5.1.124.5.1.14.7

Data corresponds to the storedLEND instrument measurementdata, which was downlinkedduring the last real-time stationcontact


The file is electronically delivered via the securecopy protocolThe MOC delivers file data to both GSFC LENDSOC and to the University of Arizona LENDSOC

121108119

MOC-19 LEND Real-timeVC0 HK data

Section4.5.1.144.5.1.14.8



The data are delivered electronically to theLEND SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connectionThe MOC delivers real-time data to both GSFCLEND SOC and to the University of ArizonaLEND SOC

122109120

MOC-20LOLA -Spacecraft HKData File

Section4.5.1.104.5.1.15.5




123110121

MOC-21 LOLA HK DataFiles

Section4.5.1.114.5.1.15.6

Data corresponds to the storedLOLA s/c housekeeping data,which was downlinked duringthe last real-time station contact



124111122

MOC-22LOLA RawMeasurementData Files

Section4.5.1.124.5.1.15.7

Data corresponds to the storedLOLA instrument measurementdata, which was downlinkedduring the last real-time stationcontact




4-27




Conventions

125112123

MOC-23 LOLA Real-timeVC0 HK data

Section4.5.1.144.5.1.15.8



The data are delivered electronically to theLOLA SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

126113124

MOC-24 LROC Real-timeVC0 HK data

Section4.5.1.144.5.1.16.9



The data are delivered electronically to theLROC SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

127114125

MOC-25LROC -Spacecraft HKData File

Section4.5.1.104.5.1.16.6




128115126

MOC-26 LROC HK DataFiles

Section4.5.1.114.5.1.16.7

Data corresponds to the storedLROC s/c housekeeping data,which was downlinked duringthe last real-time station contact


The file is electronically delivered via the securecopy protocoldelivery date/time is TBR

129116127

MOC-27

LROC NACRawMeasurementData Files

Section4.5.1.124.5.1.16.8

Data corresponds to the storedLROC instrument NACmeasurement data, which wasdownlinked during the last real-time station contact

TBR Variable – file sizecan be based on time limits,file size, or via commanddownlink


130117 MOC-39

LROC WACRawMeasurementData Files

Section4.5.1.12

Data corresponds to the storedLROC WAC measurement data,which was downlinked duringthe last real-time station contact

Variable – file size can bebased on time limits, filesize, or via commanddownlink



4-28




Conventions

131118128

MOC-28Mini-RF -Spacecraft HKData File

Section4.5.1.104.5.1.17.8




132119129

MOC-29 Mini-RF HKData Files

Section4.5.1.114.5.1.17.9

Data corresponds to the storedMini-RF housekeeping data,which was downlinked duringthe last real-time station contact



133120130

MOC-30Mini-RFOperationsOpportunity

Section4.5.1.154.5.1.17.10

TBRValid for the upcomingweek TBR


134121131

MOC-31Mini-RF RawMeasurementData Files

Section4.5.1.124.5.1.17.11

Data corresponds to the storedMini-RF instrument sciencedata, which was downlinkedduring the last real-time stationcontact



135122132

MOC-32Mini-RF Real-time VC0 HKdata

Section4.5.1.144.5.1.17.12



The data are delivered electronically to theLROC SOC via a real-time socket connection.The telemetry and command component in theLRO MOC (e.g., ITOS) initiates the transfer viaa socket connection

136123133

MOC-33 SPICE EventKernel

Section4.5.1.3

TBRData valid for upcomingmonth

TBRVariable based onnumber of Orbitermaneuvers during themonth

The file is electronically delivered via the scpdelivery date/time is first Wednesday of themonth, noon local Eastern . TBR

137124134

MOC-34

SCN Real-timeOrbiterCommands(WS1 and USN)

Section4.5.3.1

Real-time commands are validonly for specified time periodswhen commands are uplinked

Variable – based on numberof commands to uplinkduring station contactTBR

The commands are sent via real-time socketconnects to the USN/WS1 station


4-29




Conventions

138125135

MOC-35DSN Real-Timeorbitercommands

Section4.5.3.2


TBRVariable – based onnumber of commands touplink during stationcontact

The commands are sent via real-time socketconnects to the DSN station

139126136

MOC-36SN Real-Timeorbitercommands

Section4.5.3.3


Variable – based on numberof commands to uplinkduring station contactTBR

The commands are sent via real-time socketconnects to the SN

140127137

MOC-37 Commands toKSC

Section4.6.2.2

The command load is valid forthe specified time period only

TBR Variable based onnumber of commands (real-time commands of ATSLoads, etc)

The commands are sent electronically via a real-time socket connectiondelivery date/time is TBR.

141128138

MOC-38 Telemetry toKSC

Section4.6.2.1

Telemetry to KSC is sent in nearreal-time after spacecraftseparation from the EELV

TBR Variable – based onlow downlink data rate

The telemetry data are electronically delivered tothe KSC launch site via a socket connection

142129139

MOC-40 SPICE FK –Frame Kernels

Section4.5.1.4

File does not contain time-stamped dataFile valid until next release

< 1 KbytesMOC electronically distributes the file once pre-launch and possibly once post-launchMOC uses scp “push” to deliver file

143130140

MOC-41SPICE PredictedCK (PredictedS/C Orientation)

Section4.5.1.5

Provides the next 24 hours ofpredicted s/c orientation

< 100 KbytesData records at 1 minute

MOC electronically distributes the file every dayat noon time (local Eastern time)MOC uses scp “push” to deliver file

144131141

MOC-42

SPICEDefinitive CK(Definitive S/COrientation)

Section4.5.1.6

Provides the previous 24 hoursof definitive s/c attitude data



145132 MOC-43

SPICEDefinitive HGAOrientation CK

Section4.5.1.7

Provides the previous 24 hoursof definitive HGA Orientationattitude data




4-30




Conventions

146133 MOC-44

SPICEDefinitive SAOrientation CK

Section4.5.1.8

Provides the previous 24 hoursof definitive SA orientationattitude data



147134 MOC-45 HGA/SA Fixed

Offset FramesSection4.5.1.9

File does not contain time-stamped dataFile valid until next release

< 1 KbytesMOC electronically distributes the file once pre-launch and possibly once post-launchMOC uses scp “push” to deliver file

148135 MOC-46

CRaTER HKMeta SummaryReport

Section4.5.1.13

File provides summaryinformation for the last set ofdownlinked instrument HKproducts

< 100 Kbytes, but variablebased on number ofinstrument HK filesdownlinked in last WS1contact

MOC electronically distributes the file within 24hours of receipt from the stationMOC uses scp “push” to deliver file

149136 MOC-47

CRaTERMeasurementMeta SummaryReport

Section4.5.1.13

File provides summaryinformation for the last set ofdownlinked instrumentMeasurement products

< 100 Kbytes, but variablebased on number ofinstrument measurementfiles downlinked in lastWS1 contact


150137 MOC-48

DLRE HK MetaSummaryReport

Section4.5.1.13




151138 MOC-49

DLREMeasurementMeta SummaryReport

Section4.5.1.13




152139 MOC-50

LAMP HK MetaSummaryReport

Section4.5.1.13




pgf

Highlight



4-31




Conventions

153140 MOC-51

LAMPMeasurementMeta SummaryReport

Section4.5.1.13




154141 MOC-52

LEND HK MetaSummaryReport

Section4.5.1.13




155142 MOC-53

LENDMeasurementMeta SummaryReport

Section4.5.1.13




156143 MOC-54

LOLA HK MetaSummaryReport

Section4.5.1.13




157144 MOC-55

LOLAMeasurementMeta SummaryReport

Section4.5.1.13




158145 MOC-56

LROC HK MetaSummaryReport

Section4.5.1.13





4-32




Conventions

159146 MOC-57

LROC NACMeta SummaryReport

Section4.5.1.13




160147 MOC-58

LROC WACMeta SummaryReport

Section4.5.1.13




161148 MOC-59

Mini-RF HKMeta SummaryReport

Section4.5.1.13




162149 MOC-60

Mini-RFMeasurementMeta SummaryReport

Section4.5.1.13




163150 MOC-61 PDS NAIF

Dataset ArchiveSection4.5.1.16

Provides the complete archive ofMOC products to the NAIFArchive Facility

Variable – based on numberof files, archive frequencyand file archivecompression techniques

MOC electronically transfers the archive setMOC uses scp “push” mechanism

142 LROProject

SPICE FK(Frame Kernels)

Section4.5.1.4

Frame Kernels, definition of andspecification of relationshipbetween reference frames(coordinate systems). Includesinstrument mounting alignmentsCreate once pre-launch andpossible once post-launch toprovide any new alignmentinformation.

TBR – base on number ofalignments and pointmatrices for eachinstrument and Orbiter HWthat are included in theoverall reference frame

Input comes form multiple LRO groups viaemails or other document references.F


4-33




Conventions165151143

FSWM-1 Orbiter FSWLoad Files

Section4.4.1.1

N/A – File contains latest FSWTable/Memory Load file

TBR Variable – based onFSW image to be modified File is transferred via TBR secure mechanism

166152144

NAIF-1 SPICE PlanetarySPK

Section4.5.4.1

Contains next seven days ofplanetary ephemeris in SPICESPK format

TBR Variable – based onPlanetary information andduration image to bemodified

When announced, file is pulled from NAIF website

167153145

NAIF-2SPICE LSK(Leap SecondKernel)

Section4.5.4.2

Historical reference containingall of the Leap Secondmodifications since the Epoch

TBR Variable – based onamount of data required toindicate Leap SecondUpdates

When announced, file is pulled from NAIF website

168154 NAIF-3 Planetary

ConstantsSection4.5.4.3

File does not contain time-stamped dataFile valid until next NAIFrelease

< 1 MByteThe NAIF generates this file on an as-neededbasis: the MOC pulls the file electronically viathe secure copy protocol

169155 NAIF-4

SPICE BinaryPCK (HighPrecision LunarOrientation)

Section4.5.4.4

File does not contain time-stamped dataFile valid until next NAIFrelease

< 1 KbytesNAIF announces when new file is available andMOC electronically pulls the file


4-34



4.1 FLIGHT DYNAMICS FACILITY PRODUCTSThis section provides the details of the products that the Flight Dynamics Facility creates tosupport the LRO mission. FDF creates these products on a regular basis to provide data for:• station acquisition data,• science operations center planning purposes,• attitude and maneuver planning• general reports to the Mission Operations Team useFor products destined to the MOC, FDF generates these products using a standard namingconvention as defined by the following concepts of a file name and a file extension separated bythe standard period (.):

<file name>.<file extension>; where<file name> FDFnn_YYYYDDD_YYYYDDD_fvn; where

Table 4-2 FDF File Naming Convention

FDFnn => 5 ASCII characters in which the nn refers to the identifier listed as the LRO GroundSystem Product Matrix; for example

FDF03 = LRO Beta Angle Predict FileFDF14 = Lunar Orbit Terminator Crossing Predicts

Start Date ofproductYYYYDDD

=> 7 ASCII charactersYYYY => 4 ASCII characters for the year (2008 – 2013)DDD => 3 ASCII characters for day of year designator (001 – 366); followed by theunderscore (_) character

Stop Date ofproductYYYYDDD

=> 7 ASCII charactersYYYY => 4 ASCII characters for the year (2008 – 2013)DDD => 3 ASCII characters for day of year designator (001 – 366); followed by theunderscore (_) character

f => Flag to indicate if maneuvers are modeled or included within the productb => Maneuvers are modeled. For definitive products, all maneuvers are modeled.For predictive products, at least one future maneuver is modeled.n => No maneuvers are modeled. For predictive products, the propagation includes nospacecraft perturbations and represents the product if no spacecraft maneuversare performed with the time span of the product

vn => 2 ASCII characters to represent the version number for the file.

The initial creation of a file will be represented by version number 01; a subsequent version is02, 03, etc. The YYYYDDD designation identifies the start date and the end date for which datais are contained within the file. FDF generates the products to start at 0000Z on the start dateand end at 0000Z on the end date so that there is always an overlap between products in theevent that FDF was down and could not generate a new product until the previous hadcompletely expired. FDF generates a product that has a start time of 0000Z for the start date and


4-35



actually ends at 0000Z. In the example of a 10 day product (e.g., SCN Station Acquisition Data– FDF-6), the duration is 10 complete days, but the product includes 0000Z for the eleventh day.

For example, the name for the LRO Beta Angle Predict File, based on these concepts, isidentified as FDF03_2009015_20091948289_n01.txt. This assumes that the first data pointrepresents a starting time after of 0000Z on October January 15, 20089 and an end date of July13, 2009 at 2359Z and it was the first generation of the file and that no maneuvers were modeled.

<file extension> 3-4 ASCII characters representing the type of file; e.g.,txt, for a text fileinp2 for the FDF generated SCN acquisition data product (version 2 of INP)bsp, for a binary SPICE (SPK) filexsp, for a transfer format SPICE SPK filetf, for a text reference frame designationtls, for leap second filestpc, for PCK constants file

This naming convention is the standard, except where noted that a different naming conventionis required based upon other mission concepts. These special cases will be explicitly called outin the corresponding sections.

FDF generates all products to support the LRO launch window. FDF delivers these products toall LRO elements at launch minus 3 days (L – 3D). The products contain information thatprovides accurate prediction information up through the Lunar Orbit Insertion (LOI) maneuver.FDF provides product updates in the event of a launch slip of greater than 1 day. In the event ofa non-nominal launch, FDF regenerates the products within 2 hours of recalculating the Orbiter’strajectory

4.1.1 FDF Products for Network SupportThis section provides the details on the acquisitions data products that FDF generates; theseproducts are used by the various networks that provide tracking, telemetry and commandinterfaces to support the LRO mission.

4.1.1.1 (FDF-6) SCN Station Acquisition Data4.1.1.1.1 Product DescriptionThis product file contains acquisition information for each Space Communications Networkground station supporting the LRO telemetry and measurement data downlink or commanduplink. FDF creates a separate file for each station supporting the LRO mission. FDF generatesan acquisition data product with an INP2 format (as defined below) for use at WS1 and the USN-owned stations. For the USN collaborative sites, FDF generates an acquisition data productusing a standard CCSDS format identified as an Orbital Ephemeris Message (OEM) DataProduct.4.1.1.1.2 Support Duration


4-36



The FDF will provide the Station Acquisition Data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.1.1.1.3 FormatThe station acquisition data is formatted as an INP-like data file; this data file consists of ASCIItextual data fields that are tab delimited. FDF generates the INP product as a tab-delimitedASCII text fields; FDF generates the OEM product as defined by the CCSDS Standards for thatproduct.This product is generated weekly, on Wednesday, and updated after each LRO maneuver. Theproduct contains 10 days of acquisition data for each station. This product is generated such thatthe time tag information is centered at 1 minute increments.

The file contains the acquisition data for each contact for the station; FDF generates a separatefile for each station. Each file will have 1:N lines of header information that identifies the filename and file creation information. This is followed by 1:N lines of station acquisitioninformation. The standard fields and field description (for the 1:N lines of acquisition data) arelisted in the following table. Data will be provided down to an elevation angle equal to zero (nostation masking will be used)

Table 4-3 FDF – SCN Acquisition Data Description

Field name Field CharacteristicsStrand name 31 ASCII text characters representing the facility/station name to satellite/0059

(LRO). The station name is represented by the 4 ASCII text charactersrepresenting the unique station identifier (add table of station identifiers for eachSCN and DSN station). The field appears as follows:

Facility/NNNN to Satellite/0059

Where NNNN represents the 4 character ASCII station name and 0059 is the 4-digit NASA SIC code for LRO.NNNN = LR1S for LRO White Sands S-band Station

LR1K for White Sands Ka-Band StationSDSK for White Sands Ka-Band Backup StationSDSS for SDO/LRO STGT S-Band backup StationUSPS for USN Dongara, AustraliaUSHS for USN South Point, HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, GermanyDS24 (or DS15 or DS27) for the DSN 34m at Goldstone, CaDS34 (or DS45) for the DSN-34m at Canberra, AustraliaDS54 (or DS65) for the DSN 34-m at Madrid, Spain


4-37



Field name Field CharacteristicsTimetag information:yearday of year andtime of day

YYYYDDD.HHMMSS (GMT) ; 14 ASCII digits with a period between the first 7and last 6; where

YYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS => 6 ASCII digits representing the hours, minutes, and seconds of day

Range RRRRRR.ddddd (Km)RRRRRR => 6 ASCII digits for whole range (0 – 999999)Note 1

ddddd => 5 ASCII digits for decimal portion of range (00 – 99999)

Range rate RR.dddddd (Km/s)RR => 2 ASCII digits for whole range rate (0 – 99) Note 1

dddddd => 6 ASCII digits for decimal portion of range (00 – 999999)

Azimuth angle AAA.ddd (Degree)AAA => 3 ASCII digits for whole angle measurement (0 – 360)ddd => 3 ASCII digits for decimal portion of range (00 – 999)

Elevation angle EEE.ddd (Degree)EEE => 3 ASCII digits for whole angle measurement (0 – 90)ddd =>3 ASCII digits for decimal portion of range (00 – 999)

Note 1 : Field is actually floating point and the value will vary in magnitude

A sample file name for the first generation of this data file has the following convention:

<File name>_<Maneuver Model Flag><version number>.<file extension>

where File Name = [17 26 Characters], which includes the filed field delimiters ofeither an underscore character (_) or the period (.); the followingfield definitions are used to define the fields

Station Identifier =>5 total ASCII Characters4 ASCII Characters used to represent the stations supportingthe LRO mission; followed by a 1 character underscore

Project Identifier => 5 total ASCII Characters4 ASCII Characters used to represent the LRO mission identifier (0059), followed by an underscore

Start Date/Time => 8 total ASCII Characters8 ASCII Characters used to represent the start date associated with the first station acquisition; YYYYDDD. followed by a 1 character underscore

Stop Date/Time => 8 total ASCII Characters8 ASCII Characters used to represent the start date associated with the first station acquisition; YYYYDDD. followed by a 1 character underscore


4-38



ManeuverModel Flag

= [1 characters] One ASCII character that indicates whethermaneuvers were modeled for this product

b => Maneuvers are modeledn => No maneuvers are modeled

version number = [2 characters] Two ASCII character version number. The initialversion is 01, next is 02 … up to 99.

file extension = [4characters] inp2 to represent the second format version of an INPdata product

For example, a sample file name for the acquisition data (INP2 product version) correspondingto the LRO STGT station (for the 10 day duration of Thursday, January 15, 2009 at 0000Zthrough SaturdaySunday, January 254, 2009 at 0000Z) would have the following file nameconvention:LR1S_0059_2009015_2009025_n01.inp2

A sample file name for the acquisition data (OEM product version) corresponding to the USNKiruna (KU1S) station (for the 10 day duration of Thursday, January 15, 2009 at 0000Z throughSaturdaySunday, January 254, 2009 at 0000Z) would have the following file name convention:KU1S_0059_2009015_2009025_n01.oem

An INP-2 sample station acquisition data product is provided as a reference in Appendix B,Figure B.1-8Figure B.1-7Figure B.1-7.

An OEM sample station acquisition data product is provided as a reference in Appendix B,Figure B.1-9Figure B.1-8.4.1.1.1.4 Accuracy and CompletenessThe data file will consist of all station contacts for the upcoming ten days and will contain theacquisition information centered at one minute increments. The accuracy of this stationacquisition data is are consistent with the predicted ephemeris data based upon the most recenttracking information. The file data contents will be accurate to 0.01 deg.

4.1.1.2 (FDF-5) DSN Site Acquisition Data4.1.1.2.1 Product DescriptionThe DSN site acquisition data describes the FDF-generated information necessary to allow theDSN 34-meter subnet to acquire the LRO spacecraft.4.1.1.2.2 Support DurationFDF provides the DSN acquisition data through LOI plus 10 days and for any DSN supportedproficiency or mission emergency modes. FDF will provide this data during pre-launch for usein testing interfaces and to support any pre-launch mission rehearsals and tests.4.1.1.2.3 FormatThe format is the predicted SPICE SPK Transfer Format file; this format is consistent with theinformation listed at the following URL:


4-39



https://spsweb.fltops.jpl.nasa.govThe DSN site acquisition data will be sent directly from the FDF to the Deep Space MissionSystem (DSMS) Service Preparation Subsystem (SPS) website. DSN requires userauthentication to access this web site.

The file name will conform to the standards FDF-generated file name specifications(TBR—FDF05??) of the SPS.

<File name>_<Maneuver Model Flag><version number>.<file extension>

where File Name = [26 Characters], which includes the field delimiters of either anunderscore character (_) or the period (.); the following fielddefinitions are used to define the fields

Station Identifier =>5 total ASCII Characters4 ASCII Characters used to represent the stations supportingthe LRO mission; followed by a 1 character underscore

Project Identifier => 5 total ASCII Characters4 ASCII Characters used to represent the LRO mission identifier (0059), followed by an underscore

Start Date/Time => 8 total ASCII Characters8 ASCII Characters used to represent the start date associated with the first station acquisition; YYYYDDD. followed by a 1 character underscore

Stop Date/Time => 8 total ASCII Characters8 ASCII Characters used to represent the start date associated with the first station acquisition; YYYYDDD. followed by a 1 character underscore

ManeuverModel Flag

= [1 characters] One ASCII character that indicates whethermaneuvers were modeled for this product

b => Maneuvers are modeledn => No maneuvers are modeled

version number = [2 characters] Two ASCII character version number. The initialversion is 01, next is 02 … up to 99.

file extension = [4characters] inp2 to represent the second format version of an INPdata product

For example, a sample file name for the SPICE file corresponding to DSN’s Goldstone 34-meterstation (for the 28 day duration of Thursday, January 15, 2009 at 0000Z through Thursday,February 12, 2009 at 0000Z) would have the following file name convention:DS24_0059_2009015_2009043_n01.bsp

Another reference for SPICE SPK data formats is:http://naif.jpl.nasa.gov/naif


4-40



The SPICE ID for LRO is 125 (octal) or -85 (decimal).This product will be generated weekly, on Wednesdays, and updated after each LRO maneuver.Product will include 10 28 days of data. SPK file will be type 13 with order of interpolationequal to 11. Since this product is a binary file, no sample product is listed in Appendix B.4.1.1.2.4 Accuracy and CompletenessThe accuracy of this file is consistent with the tracking data used to create all predicted products.The file data contents will be accurate to TBD.

4.1.1.3 (FDF-7) Laser Ranging Site Prediction Data4.1.1.3.1 Product DescriptionThe laser ranging site prediction data describes the FDF-generated information used by the laserranging site; it provides detailed information to point the laser accurately to the spacecraft and toput the laser pulses in the LOLA earth range window. This information provides times, angles,and other necessary information to allow the laser ranging site to locate the LRO spacecraft andbegin the laser ranging functions. FDF will deliver the file to a CDDIS controlled (TBR)directory location.4.1.1.3.2 Support DurationFDF provides the laser ranging site acquisition data for all post-LOI mission phases. FDF willprovide this data during pre-launch for use in testing interfaces and to support any pre-launchmission rehearsals and tests. FDF continues to provide this data for all post-launch missionphases.4.1.1.3.3 FormatThe laser ranging site acquisition data format provides the required information for a laserranging site to be able to perform laser ranging activities to the LRO spacecraft. The LRO LaserRanging Prediction information is the LRO state vector in an earth-centric, inertial referenceframe. It consists of the following data fields:Time, X-Position, Y-Position, Z-Position, X-Velocity, Y-Velocity, Z-Velocity. The formats ofthese fields are defined in the follow table:

Table 4-4 FDF – Laser Ranging Prediction Data Description

Field name Field Characteristicstimetag information:yearday of year andtime of day

YYYYDDD HHMMSS.mmm whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3

first 6 are the hours, minutes, and seconds of daylast 3 are the milliseconds of day


4-41



Field name Field CharacteristicsX-Position (Km) RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and

last 3first 6 are the whole portions of the X-component of LRO’s positionlast 3 are the decimal portion of the X-component position

Y-Position (Km) RRRRRR.rrr => 10 ASCII characters including the period between the first 6 andlast 3

first 6 are the whole portions of the Y-component of the LRO’s positionlast 3 are the decimal portion of the Y-component position

Z-Position (Km) RRRRRR.rrr => 10 ASCII characters including the period between the first 6 andlast 3

first 6 are the whole portions of the Z-component of the LRO’s positionlast 3 are the decimal portion of the Z-component position

X-Velocity (Km/s) RR.rrrrrr => 9 ASCII characters including the period between the first 2 and last 6first 2 are the whole portions of the X-component of the LRO’s velocitylast 6 are the decimal portion of the X-component velocity

Y-Velocity (Km/s) RR.rrrrrr => 9 ASCII characters including the period between the first 2 and last 6first 2 are the whole portions of the Y-component of the LRO’s velocitylast 6 are the decimal portion of the Y-component velocity

Z-Velocity (Km/s) RR.rrrrrr => 9 ASCII characters including the period between the first 2 and last 6first 2 are the whole portions of the Z-component of the LRO’s velocitylast 6 are the decimal portion of the Z-component velocity

The product is generated weekly, on Wednesdays, and updated after each LRO maneuver; theproduct will include 10 days of data at a 1 minute intervals.

A sample file name (for the 10 day duration of Thursday, January 15, 2009 at 0000Z throughSunday, January 25, 2009 at 0000Z) and corresponding for the first generation of this data file isgiven as FDF07_2009015_2009025_n01.txtA sample Laser Ranging Site Prediction Data file is provided as a reference in Appendix B,Figure B.1-10Figure B.1-9Figure B.1-8.4.1.1.3.4 Accuracy and CompletenessFDF will create this file, such that the file is consistent with other prediction data files (e.g.,SPICE Prediction or the LRO Predicted Ephemeris File). The file contents should have anaccuracyaccuracy over the 84-hours prediction, of less than 800 m in along-track error. Thispredictive compares are not applicable across spacecraft maneuvers4.1.1.4 (FDF-8) Space Network Acquisition Data4.1.1.4.1 Product DescriptionThis product file contains the LRO spacecraft acquisition data for the Space Network’s TDRSSsupport during the launch and early orbit phase prior to ground station contacts.4.1.1.4.2 Support Duration


4-42



The FDF will provide the SN Acquisition Data for the L&EO mission phase or for pre-launchtests with the Space Network.4.1.1.4.3 FormatThe SN acquisition data is are formatted as an Improved InterRange Vector (IIRV) file inaccordance with the STDN 724.

This product is generated on an as-needed basis to support either the mission tests/rehearsals orfor the L&EO mission phase. The product contains approximately 2 hour of acquisition data forthe TDRSS contact to support the L&EO mission phase (though it is likely that 24 hours ofacquisition data will be sent).

The IIRV character layout is shown for reference in the following table.

Table 4-5 FDF – IIRV TTY SN Acquisition Data Description

Line Character Explanation1 ---- Optional text message.

2 GIIRV

A

rrrr

Start of message (fixed).

A Alphabetic character indicating originator of message:ASCII space = GSFC Z = WLPE = ETR L = JPL, W = WTR J = JSC, P = PMR A = CSTC, K = KMR C= CNESrrrr Destination routing indicator. Specifies the site for which the messagewas generated. If for more than one station, this field should contain"MANY."


4-43



Line Character Explanation3 V

S

1

C

Sic (4 chars)

bbnnn

doy

Hhmmsssss

ccc

Vector type: 1 = Free flight (routine on-orbit), 2 = Forced (special orbit update) 3 = Spare, 4 = Maneuver ignition, 5 = Maneuver cutoff 6 = Reentry, 7 = Powered flight, 8 = Stationary, 9 = SpareS = Source of data: 1 = Nominal/planning, 2 = Real-time, 3 = Off-line, 4 = Off-line/meanNOTE: Nominal/planning sets cannot be sent to White Sands GroundTerminal (WSGT) from the NCC.1 Fixed one (1)

C = Coordinate system: 1 = Geocentric True-of-Date Rotating 2 = Geocentric mean of 1950.0 (B1950.0). 3 = Heliocentric B1950.0. 4 = Reserved for JPL use (non-GSFC). 5 = Reserved for JPL use (non-GSFC). 6 = Geocentric mean of 2000.0 (J2000.0). 7 = Heliocentric J2000.0.

sic (4 chars) SIC

bb Body number/VID (01-99).nnn Counter incremented for each vector in a set of vector data on a per-station per-transmission basis.doy Day of year (001 = January 1).

hhmmsssss Vector epoch in UTC with resolution to nearest millisecond.(The implied decimal point is three places from the right).

ccc Checksum of the decimal equivalent of the preceding characters onLine 3:

0 through 9 = face value.; Minus (-) = 1; ASCII Space = 0.

4 Sxxxxxxxxxxyyyyyyyyyyzzzzzzzzzz

ccc

s Sign character: ASCII Space = positive or Minus sign = negativexxxxxxxxxxxx = X component of position (meters)yyyyyyyyyyyy = Y component of position (meters)zzzzzzzzzzzz = Z component of position (meters)

ccc Checksum of the decimal equivalent of the preceding characters onLine 4: 0 through 9 = face value.; Minus (-) = 1; ASCII Space = 0.


4-44



Line Character Explanation5 S

xxxxxxxxxxyyyyyyyyyyzzzzzzzzzz

ccc

s Sign character (same as above)xxxxxxxxxxxx · = X-component of velocityyyyyyyyyyyyy ·= Y-component of velocityzzzzzzzzzzzz ·= Z-component of velocityNOTE:All velocity components are in meters/second with resolution to thenearest millimeter/second. The implied decimal point is three places fromthe right.

ccc Checksum of the decimal equivalent of the preceding characters onLine 5: 0 through 9 = face value.; Minus (-) = 1; ASCII Space = 0.

6 mmmmmmmmmm

aaaaa

kkkk

S

rrrrrr

ccc

Mass of spacecraft in kilograms with resolution to 1/10 of a kilogram.The implied decimal point is one place from the right. Contains all zeroswhen not used.

Average spacecraft cross-sectional area in square meters with resolutionto the nearest hundredth of a square meter. The implied decimal point istwo places from the right. Contains all zeros when not used.

Dimensionless drag coefficient. The implied decimal point is two placesfrom the right. Contains all zeros when not used.

Sign character for coefficient of solar reflectivity ASCII Space = positive or Minus Sign = negative

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

Checksum of the decimal equivalent of the preceding characters on Line6: 0 through 9 = face value.; Minus (-) = 1; ASCII Space = 0.

7 oooo ITERM End of message (fixed)Originator routing indicator

The file will be transmitted from FDF to DSMC at White Sands using conventional FDFtransmission protocols. As an example, a sample file name for the IIRV file for the launch dayof Tuesday, October 28, 2009 would have the following file name convention:FDF0_0059_2008289_2008289_n01.txt.4.1.1.4.4 Accuracy and CompletenessThe data file will contain predict information for the first day of the mission although thesupported period is after launch for approximately 1 hour. The accuracy of this SN acquisitiondata will be best available based on the latest acquisition source at this time which is likely the


4-45



pre-mission nominal or time-slipped nominal, or the separation vector. The file data contentswill be accurate to 0.01 deg.

4.1.2 FDF Products to support MOC FunctionsFDF generates this following set of products for use by the MOC to perform most of its dailyfunctions. Some of these data products are electronically transferred to the various ScienceOperations Centers while other are used internally within the MOC by the LRO operations teamto support command generation or as reports that are generated on a daily or as-needed basis.4.1.2.1 (FDF-9, FDF-10) Ground Station View Period Predicts File (HGA and Omni View

Periods)4.1.2.1.1 Product DescriptionThe Ground Station View Period Predict file is two separate files, one contains specific dataassociated with the High Gain antenna and the other file contains the data associated with theomni antenna. These files contain information that identifies when the specified antenna isviewable from the LRO ground station.For the White Sands Antennas, FDF uses the different station mask information to identifydifferent station views for the Ka-Band antenna as compared for the S-Band antenna. FDF usesa 20 degree station mask for the Ka-Band and a 5 degree mask for the S-band antenna.4.1.2.1.2 Support DurationFDF provides the Ground Station View Period Predicts file for all mission phases. FDF willprovide this data during pre-launch for use in testing interfaces and to support any pre-launchmission rehearsals and tests. FDF continues to provide this data for all post-launch missionphases.4.1.2.1.3 FormatThis file contains the data associated with view periods for all supporting ground stations used toprovide LRO with Tracking, Telemetry, & Command (TT&C) support during the variousmission phases. It consists of the station identifier and the view period information for thatstation based on a fixed minimum elevation angle of 5 degrees.

The product will be generated weekly, on Wednesday, and updated after each LRO maneuver.The product will include 28 days worth of station view periods.

The general format of this file consists of the following information:1:N Header lines that provide the Station Name and date that FDF generated the file, and headerlines that provide the field description; the file then contains N lines of data for each station viewperiod

Station Name is the 31 ASCII Character qualifiers previous discussed. The N lines of datacontain the following fields

Start Time Stop Time Duration Orbit # Time Max Elev. Maximum Elevation Angle;where these fields are defined in the following table:


4-46



Table 4-6 FDF – Ground Station View Period Data Description

Field name Field CharacteristicsStation name 31 ASCII text characters representing the unique station identifier, with the

following format:Satellite-0059-to-Facility-NNNN; whereNNNN = LR1S for LRO White Sands S-band Station

LR1K for White Sands Ka-Band StationSDSS for SDO/LRO STGT backupUSPS for USN DongaraUSHS for USN South Point, HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, GermanyDS24 for the DSN 34-m at Goldstone, CaDS34 for the DSN-34m at Canberra, AustraliaDS54 for the DSN 34-m at Madrid, Spain

Start time information:yearday of year andtime of day

YYYYDDD.HHMMSS, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366), followed by a period (.)HHMMSS => 6 ASCII digits for the hours, minutes, and seconds of day

Stop time information:yearday of year andtime of day

YYYYDDD.HHMMSS, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366), followed by a period (.)HHMMSS => 6 ASCII digits for the hours, minutes, and seconds of day

Station View Duration (inseconds)

SSSS.mmm (8 ASCII digits), whereSSSS => 4 ASCII characters representing the whole seconds; followed by aperiod(.)mmm => 3 ASCII characters for the milliseconds of station contact

Orbit Number 7 ASCII characters representing a monotonically increasing Orbit Number(1 to 9999999)NOTE: This field is only valid after lunar insertion

Time of Maximum Elevation YYYYDDD.HHMMSS, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366), followed by a period (.)HHMMSS => 6 ASCII digits for the hours, minutes, and seconds of day

Max elevation angle EE.dddEE => 2 ASCII digits for whole angle measurement (0 – 90)dd => 3 ASCII digits for decimal portion of range (00 – 999)

A sample file name for the first generation of the HGA data file is given as FDF09_20090152009015_2009043_n01.txtFDF09_HGA_2008289_n01.txt; for the omni antenna file,the file name would conform to the following conventions:FDF10_2009015_2009043_n01.txtFDF10_OMNI_2008289_n01.txt


4-47



A sample Ground Station View Period Predict Data file is provided as a reference in AppendixB, Figure B.1-12Figure B.1-11Figure B.1-10.4.1.2.1.4 Accuracy and CompletenessThe file data contents will be accurate to the best predictions from the tracking data, whichthemselves should be accurate to 5 seconds.

4.1.2.2 (FDF-3) LRO Beta Angle Predict File4.1.2.2.1 Product DescriptionThe LRO Beta Angle Predict File provides the angle information between the LRO lunar orbitplane and the sun with the following definition. When the sun is in the orbit plane, this results ina zero degree (0°) angle. If the sun and orbit plane are perpendicular to each other; then thisresults in a beta angle of ninety degrees (90°). In this specific instance, the LRO spacecraft is incontinuous full sun.4.1.2.2.2 Support DurationFDF will generate this file for all post-LOI mission phases.4.1.2.2.3 FormatThe LRO Beta Angle Predict file is an ASCII-formatted file in which the fields are tab delimited.The file contains the time of the sample, the Beta angle information (given in degrees andhundredths of degree) and the sun quadrant information that provides information as to whetherthe angle is increasing or decreasing. A positive Beta Angle correlates to the spacecraft orientedto a positive orbit normal reference frame. The file entries are generated at six hour increments.The file contains the time, beta angle, and quadrant information; the following table provides abrief description of each field:

Table 4-7 FDF – LRO Beta Angle Data Description

Field name Field CharacteristicsTime information:yearday of year andtime of day

YYYYDDD.HHMMSS. (GMT) 14 total ASCII Characters with a period betweenthe first 7 and last six; where

YYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS => 6 ASCII digits (hours, minutes, and seconds of day)

Beta Angle SBB.bb => (degrees) 6 total ASCII characters with a period between the first 3and last 2

the first character is a sign value (positive or negative angles) a Blank = Positive angle Orbit Normal reference - = Negative angle Orbit Normal reference

the next 2 are the whole decimal degrees of the beta anglelast 2 are the decimal portion of the Beta angle

Quadrant N => 1 ASCII character that identifies the quadrant information related to the BetaAngle definition. Allowable values are: 1 – 4 inclusive


4-48



A sample file name for the first generation of this data file is given asFDF03_2009015_2009195_n01.txt

Product will be generated monthly, on the first Wednesday of each month. Product will include180 days of data at a six-hour intervals.

A sample LRO Beta Angle File data file is provided as a reference in Appendix B, Figure B.1-13Figure B.1-12Figure B.1-11.4.1.2.2.4 Accuracy and CompletenessThe file data contents will be accurate to one degree.4.1.2.3 (FDF-4) LRO Definitive Ephemeris File4.1.2.3.1 Product DescriptionThe LRO Definitive Ephemeris file contains the LRO spacecraft’s position and velocityinformation in an inertial, mean J2000 coordinate reference frame. The coordinate frame will beEarth-centered for pre-LOI mission phases and moon-centered for post-LOI mission phases. Thedata is are centered at one minute increments.4.1.2.3.2 Support DurationFDF will generate this file for all mission phases.4.1.2.3.3 FormatThe Definitive Ephemeris file is an ASCII-formatted file in which the fields are tab delimited.The file contains the time of the sample, the X,Y, Z position information (given in Kilometers, orKm) and the X, Y, and Z velocity components (given in Kilometers per second, or Km/sec). Thefile entries are generated at one minute increments. The following table provides a briefdescription of each field:

Table 4-8 FDF – LRO Definitive Ephemeris Data Description


YYYYDDD.HHMMSS (GMT), 14 total ASCII Characters with a period betweenthe first 7 and last six; where


X-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between thefirst 6 and last 6

first signed 6 are the whole portions of the X-component of LRO’s position*last 6 are the decimal portion of the X-component position

Y-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between thefirst 6 and last 6

first signed 6 are the whole portions of the Y-component of LRO’s position*last 6 are the decimal portion of the Y-component position


4-49



Field name Field CharacteristicsZ-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between the

first 6 and last 6first signed 6 are the whole portions of the Z-component of LRO’s position*last 6 are the decimal portion of the Z-component position

X-Velocity SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6

first signed 6 are the whole portions of the X-component of the LRO’svelocity*

last 6 are the decimal portion of the X-component velocity

Y-Velocity SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6

first signed 2 are the whole portions of the Y-component of the LRO’svelocity*

last 6 are the decimal portion of the Y-component velocity

Z-Velocity (Km/s) SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6

first signed 2 are the whole portions of the Z-component of the LRO’svelocity*

last 6 are the decimal portion of the Z-component velocity

* - Field is actually a floating value so the value will vary significantly over the course of the mission.


The product is generated weekly, on Wednesdays; the product includes 7 days of data. The dataare provided at a one minute intervals.

A sample LRO Definitive Ephemeris File data file is provided as a reference in Appendix B,Figure B.1-14Figure B.1-13Figure B.1-12.4.1.2.3.4 Accuracy and CompletenessThe file data contents will be accurate to 500 meters.4.1.2.4 (FDF-29) LRO Definitive SPICE SPK File4.1.2.4.1 Product DescriptionThis file contains the SPICE “kernel” information for the definitive LRO spacecraft ephemerisdata. This kernel file contains the previous week’s definitive LRO spacecraft position andvelocity information for the previous dayweek based upon only on the received S-Band trackingdata recently received over the last seven days.This product will be Earth-centered J2000 and Moon-centered J2000 following LOI (or asneeded)..4.1.2.4.2 Support DurationFDF will generate this file for all post-LOI mission phases.4.1.2.4.3 Format


4-50



The Definitive Spice file is a UNIX-based binary SPICE file and will require the use of theSPICE Toolkit, which can be accessed from the Navigation and Ancillary Information Facility(NAIF) web site. This web site is located at the following URL:http://naif.jpl.nasa.gov/naif/index.html

A sample file name for the first generation of this data file isFDF29_200900814_2009015_n01.bsp (binary SPICE format (little Endian) (or .xsp – SPICESPK Transfer Format?).The SPICE ID for LRO will be -85, as assigned by JPL).

The product will be generated weekly, on Wednesdays, by noontime, Eastern Standard time.Product will include 7 days worth of data. SPK file will be type 13 and interpolation order 11;since this is a binary file, no sample product will be shown in the Appendix B.4.1.2.4.4 Accuracy and CompletenessThe file data position information will be accurate to within 500 meters.

4.1.2.5 (FDF-30) LRO Predictive SPICE SPK File4.1.2.5.1 Product DescriptionThis file contains the SPICE “kernel” information for the predictive LRO spacecraft ephemerisdata. This kernel file contains the next twenty-eight (28) day’s worth of LRO spacecraftpositions and velocity information based upon the just processed day’s tracking data. This filewill contain the LRO Predictive ephemeris data; this file could provide ephemeris datainformation related to the LRO station keeping maneuvers that are to occur in within this 28 daytime period.4.1.2.5.2 Support DurationFDF will generate this file for all post-LOI mission phases.4.1.2.5.3 FormatThis product will be Earth-centered J2000 and Moon-centered J2000 following LOI (or asneeded). The Predictive Spice file is a UNIX-based binary SPICE file and will require the use ofthe SPICE Toolkit, which can be accessed from the Navigation and Ancillary InformationFacility (NAIF) web site. This web site is located at the following URL:http://naif.jpl.nasa.gov/naif/index.htmlA sample file name for the first generation of this data file is given asFDF30_2009015_2009043_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format. {Sample sent in .xsp format}.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated daily. Product will include 28 days worth of data. SPK file will betype 13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in the Appendix B.4.1.2.5.4 Accuracy and Completeness


4-51



In nominal lunar mission orbit, the FDF-generated LRO Predictive SPICE SPK File shall havean accuracy over the 84-hours prediction, of less than 800 m in along-track error. This predictivecompares are not applicable across spacecraft maneuvers.4.1.2.6 (FDF-13) Lunar Orbit Ascending and Descending Node Predicts4.1.2.6.1 Product DescriptionThis file contains the lunar-nodal crossing predicts associated when the LRO orbit either crossesthe ascending node or the descending node.4.1.2.6.2 Support DurationFDF will generate this file only during post-LOI during all mission phases and immediately aftera lunar orbit maneuver (such as a station keeping maneuver).4.1.2.6.3 FormatThis is a file that contains 1-week’s worth of nodal crossing predicts. The file is an ASCII textfile in which the fields are tab delimited. The file contains 1:n lines of file header informationfollowed by the nodal crossing time, the nodal crossing type, and the corresponding lunarlongitude, and the orbit number; these fields are separated by tabs. The following table providesa brief description of each field:

Table 4-9 FDF – LRO Ascending Descending Node Data Description

Field name Field Characteristicstimetag information:yearday of year andtime of day

YYYYDDD.HHMMSS (GMT), whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366) preceding a periodHHMMSS => 6 ASCII digits representing hours, minutes and seconds of day

Node Crossing Type 1 Character ASCII flag to indicate if the type of nodal crossingA => Ascending Node Crossing TypeD => Descending Node Crossing Type

Lunar Longitude AAA.dd (degrees, East Longitude)AAA => 3 ASCII digits for whole angle measurement (0 – 360)dd => 2 ASCII digits for decimal portion of range (00 – 99)The lunar longitude is consistent with the DE416 coordinate system

Lunar Orbit 5 ASCII Characters to represent a monotonically increasing orbit number from 1 ..99999. Orbit number increments at ascending node crossing beginning at lunarinsertion

NOTE1: The orbit number is only provided at the Ascending Node Crossing time


FDF will generate this product on a daily basis or after a maneuver has occurred. The productwill contain 7 days of data.


4-52



A sample LRO Ascending Descending Node data product is provided as a reference in AppendixB, Figure B.1-15Figure B.1-14Figure B.1-13.4.1.2.6.4 Accuracy and CompletenessThe data file will consist of every ascending and descending node crossing predictions for theupcoming seven days and will contain the data centered at one minute intervals. The accuracy ofthis node crossing times data is 1 2 seconds by the end of the predicted time span.4.1.2.7 (FDF-14) Lunar Orbit Terminator Crossing Predicts4.1.2.7.1 Product DescriptionThis is a file that contains lunar terminator crossing predicts associated when the LRO spacecraftcrosses the lunar terminator line.4.1.2.7.2 Support DurationFDF will generate this file only during all post-LOI mission phases.4.1.2.7.3 FormatThis is a file that contains 1-week’s worth of lunar terminator crossing predicts. The file is anASCII text file in which the fields are tab delimited. The file contains the actual terminatorcrossing time and the corresponding terminator type; the following table provides a briefdescription of each data field:

Table 4-10 FDF – LRO Lunar Orbit Terminator Crossing Predicts Data Description

Field name Field Characteristicstime information:yearday of year andtime of day

YYYYDDD.HHMMSS (GMT), whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366) preceding a periodHHMMSS => 6 ASCII digits representing hours, minutes and seconds of day

Lunar Terminator Type 1 Character ASCII flag to indicate if the type of terminator crossingN => Into Lunar night (going from Lunar day into night)D => Into Lunar day (going from Lunar night into day )

A sample file name for the first generation of this data file is given asFDF14_2009015_2009022_n01.txt.

FDF will generate this product on a daily basis or after a maneuver has occurred. The productwill contain 7 days of data.

A sample LRO Lunar Terminator Crossing data product is provided as a reference in AppendixB, Figure B.1-16Figure B.1-15Figure B.1-14.4.1.2.7.4 Accuracy and CompletenessThe data file will consist of every lunar terminator crossing predictions for the upcoming sevendays; the accuracy of the node crossing data is 1 second.


4-53



4.1.2.8 (FDF-15) Mission Eclipse Predicts4.1.2.8.1 Product DescriptionThis file contains the predictive information associated when the LRO spacecraft is put into ashadow resulting from either a lunar or earth caused eclipse.4.1.2.8.2 Support DurationFDF will generate this file during all mission phases and immediately after a maneuver.4.1.2.8.3 FormatFDF generates this file as an ASCII-formatted file in which the fields are tab delimited. Theformat for this file can consist of 1 lines that identify the mission eclipses that result in both apartial eclipse (LRO is flying in the penumbra shadow) and a full eclipse (LRO is flying in theumbra shadow). The umbra is always a subset of the penumbra phase and as such the start/stoptimes and durations will be contained within the penumbra. The usual configuration is that apenumbra is followed immediately by an umbra then a penumbra as LRO enters, transits, andexits the eclipse. The file has the following field information: Start Time, Stop Time, ShadowFlag, Duration, and Occultation Flag, and Total Duration; these fields are defined in thefollowing table:

Table 4-11 FDF – LRO Mission Eclipse Data Description

Field name Field CharacteristicsStart time information:yearday of year andtime of day

YYYYDDD.HHMMSS (GMT) whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366) preceding period.HHMMSS => 6 ASCII digits representing hours, minutes, and seconds of day

Stop time information:yearday of year andtime of day


Current Condition Entering Penumbra or Umbra

Duration of Current Condition MMM.dd (minutes)MMM => 3 ASCII digits for whole portion of minutes (0 – 160)dd => 2 ASCII digits for decimal portion of minutes (00 – 99)

Occultation Occulting BodyEarth or Moon

Total Duration Total duration of penumbra and umbra on current orbit (minutes)MMM.ddMMM => 3 ASCII digits for whole portion of minutes (0 – 160)dd => 2 ASCII digits for decimal portion of minutes (00 – 99)

This file contains 90-days worth of mission eclipse information for either lunar or earth eclipses.


4-54




FDF will generate this product on a weekly basis, on Wednesday. The product will contain 90days of data.

A sample LRO Mission Eclipse data product is provided as a reference in Appendix B, FigureB.1-17Figure B.1-16Figure B.1-15.4.1.2.8.4 Accuracy and CompletenessThe data file will consist of every LRO eclipse predictions for the upcoming ninety (90) days.The accuracy of this eclipse data time is 5 seconds.

4.1.2.9 (FDF-16) Lunar Ephemeris4.1.2.9.1 Product DescriptionThis file contains the Lunar Ephemeris, which is used to update the on-board attitude/orbit flightsoftware tables used by the ACS FSW.4.1.2.9.2 Support DurationFDF will generate this file during all mission phases.4.1.2.9.3 FormatThe format for this file is an ASCII Formatted file in which the fields are tab delimited. The filecontains multiple lines that provide the ephemeris information for the moon’s position andvelocity, centered at 1-minute increments. The file consists of the following field: Time, X-Position, Y- Position, Z- Position, X-Velocity, Y- Velocity, and Z- Velocity; where the fields aredefined in the following table

Table 4-12 FDF – Lunar Ephemeris Data Description




X-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between thefirst 6 and last 6

Sign plus the first 6 are the whole portions of the X-component of moon’sposition*

last 6 are the decimal portion of the X-component position

Y-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between thefirst 6 and last 6

Sign plus the first 6 are the whole portions of the X-component of moon’sposition*

last 6 are the decimal portion of the Y-component position


4-55



Field name Field CharacteristicsZ-Position SRRRRRR.rrrrrr (Km) => 14 ASCII characters including the period between the

first 6 and last 6Sign plus the first 6 are the whole portions of the X-component of moon’s

position*last 6 are the decimal portion of the Z-component position

X-Velocity SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6



Y-Velocity SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6



Z-Velocity (Km/s) SRR.rrrrrr (km/sec) => 10 ASCII characters including the period between the first3 and last 6



* - Field is actually a floating value so the value will vary significantly over the course of the mission.

This file contains ten seven days of moon ephemeris information; the lunar ephemerisinformation is provided in the ECI reference frame.


FDF will generate this product on a weekly daily basis by noon time Eastern, on Wednesday ofeach week. The product will contain 10 seven days of data and is centered at 10 minuteintervals.A sample of the Lunar Ephemeris data product is provided as a reference in Appendix B, FigureB.1-18Figure B.1-17Figure B.1-16.4.1.2.9.4 Accuracy and CompletenessThe data file will consist of the lunar position and velocity predictions and is accurate to 100meters.4.1.2.10 (FDF-23) LRO State Vector Table4.1.2.10.1 Product DescriptionThe LRO State Vector Table provides the predicted set of OD state information for the LROspacecraft for the upcoming referenced time period, nominally 1-weeks of predicted OD stateinformation. This These data is are used by the on-board computer to update its attitude flightSW system.


4-56



4.1.2.10.2 Support DurationThe MOC-ADSFDF provides this State Vector Table throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.1.2.10.3 FormatThe file is an ASCII formatted file that provides the State Vector data file in which the fields aretab delimited. The table is a multi-line file that contains both meta-data and state vector data.The meta-data corresponds to when the report was generated, the start and stop times and otherinformation related to the state vector generation. The file contains a reference time, and x-, y-,and z-position data and the corresponding x-, y-, and z-velocity data. The LRO positioninformation is given in Kilometers (or Km), the LRO velocity components given in Kilometersper second, or Km/sec). The file entries are time centered every 10 minutes. The following tableprovides a brief description of each field:

Table 4-13 FDF – LRO State Vector Table Data Description



X-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodfirst signed 6 are the whole number of X-position vector information (0-

999999) *last 6 are the degree decimal of the X-position (000000- 999999)

Y-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodfirst signed 6 are the whole degrees of Y-position vector information (0-

999999)*last 6 are the degree decimal of the Y-position (000000- 999999)

Z-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodfirst signed 6 are the whole degrees of Z-position vector information (0-

999999)*last 6 are the degree decimal of the Z-Position (000000- 999999)

X-Velocity SRRRRRR.rrrrrr (km/sec) => 10 ASCII characters including the period betweenthe first 6 and last 6



Y-Velocity SRRRRRR.rrrrrr (km/sec) => 10 ASCII characters including the period betweenthe first 6 and last 3




4-57



Z-Velocity SRRRRRR.rrrrrr (km/sec) => 10 ASCII characters including the period betweenthe first 6 and last 3



* - Value is actually floating point and will vary in length due to mission phase


Product will be generated daily and updated after each LRO maneuver. Product will include 7days worth of data. Data will be provided at a 10 min step size. The product must be EarthCentered Inertial for all mission phases.A sample LRO State Vector Table is provided as a reference in Appendix B, Figure B.1-25Figure B.1-24.4.1.2.10.4 Accuracy and CompletenessProduct will be accurate to TBD.

4.1.2.11 (FDF-17) Orbiter Thruster Maneuver Plans4.1.2.11.1 Product DescriptionThis file contains the data information for the upcoming LRO maneuver related to the requiredstart thruster firing time, the thruster sequence, initial attitude, stop thruster firing time.4.1.2.11.2 Support DurationFDF will generate this file during all mission phases in preparation for the next scheduledmaneuver.4.1.2.11.3 FormatThis product consists of one file detailing the parameters required to characterize an LROthruster maneuver as modeled in the FreeFlyer LRO bipropellant propulsion model (TBD).

The file is a multi-line ASCII file that provides the maneuver metadata (and the actual maneuverdata, which can include the pre-burn attitude; the thruster to use; the maneuver start time, themaneuver stop time and duration of the burn; the post-burn lunar orbital elements; the post-burnpredicted attitude; the predicted fuel used; the predicted delta-V; the fuel used to date; theremaining LRO fuel; the predicted tank pressure and pressure at the completion of the thrusterburn.


A sample of the Orbiter Thruster Maneuver Plan product is provided as a reference in AppendixB, Figure B.1-19Figure B.1-18Figure B.1-17.4.1.2.11.4 Accuracy and Completeness


4-58



The data file will contain all thruster information related to this upcoming LRO maneuver; it willbe accurate to TBR criteria.

4.1.2.12 (FDF-19) Orbiter Post Maneuver Report4.1.2.12.1 Product DescriptionThis file contains the data generated to show a comparison of the predicted and actualperformance and provides a calculation of the fuel used and an estimate of the remaining fuelavailable. FDF generates this report after each the completion of each thruster maneuver.4.1.2.12.2 Support DurationThis report is generated at the completion of each LRO maneuver for any mission phase in whichFDF profiles the results of a thruster maneuver.4.1.2.12.3 FormatThe report is an ASCII formatted file in which the fields are tab delimited. The report providesthe thruster profile and compares the planned versus actual thruster information, the fuel usedand the remaining on-board fuel, and the estimated and actual spacecraft mass following thethruster maneuver.

Thruster Used, Maneuver Start Time, Maneuver Stop Time, Expected Fuel Used, ExpectedRemaining Fuel, Actual Fuel Used, Actual Remaining Fuel, Propellant Tank Pressure andTemperature; Estimated Spacecraft Mass, and Actual Spacecraft Mass, Projected maneuver andactual maneuver (e.g., expected 50m meters/sec and achieved 49.5 meters/sec) as defined in thefollowing table:

Table 4-14 FDF – LRO Orbiter Post Maneuver Report Data Description Information

Field name Field CharacteristicsThruster Used 2 ASCII Characters that identified the LRO thruster used in the maneuver

01 – 08

Maneuver Start Time:yearday of year andtime of day

YYYY DDD HHMMSS.sss, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3


Maneuver Stop Time:yearday of year andtime of day



Expected Fuel Used RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the fuel usedlast 3 are the decimal portion of the fuel used


4-59



Field name Field CharacteristicsExpected Remaining Fuel RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3

first 4 are the whole portions of the remaining fuellast 3 are the decimal portion of the remaining fuel

Actual Fuel Used RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the fuel usedlast 3 are the decimal portion of the fuel used

Actual Remaining Fuel RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the remaining fuellast 3 are the decimal portion of the remaining fuel

Propellant Tank Pressure RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the current tank pressurelast 3 are the decimal portion of the current tank pressure

Propellant Tank Temperature RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the current tank temperaturelast 3 are the decimal portion of the current tank temperature

Expected Spacecraft Mass RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the expected orbiter masslast 3 are the decimal portion of the expected orbiter mass

Actual Spacecraft Mass RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3first 4 are the whole portions of the actual orbiter masslast 3 are the decimal portion of the actual orbiter mass

Targeted Maneuver VVV.vvv => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole portions of the targeted maneuver velocitylast 3 are the decimal portion of the targeted maneuver velocity

Targeted Maneuver VVV.vvv => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole portions of the actual maneuver velocitylast 3 are the decimal portion of the actual maneuver velocity

A sample file name for the first generation of this data file is given asFDF19_2009015_2009015_n01.txtA sample of the Orbiter Post Maneuver Report product is provided as a reference in Appendix B,Appendix B, Figure B.1-20Figure B.1-19Figure B.1-18.4.1.2.12.4 Accuracy and CompletenessTBR

4.1.2.13 (FDF-18) Post Separation Report4.1.2.13.1 Product DescriptionThis report provides a comparison of the launch separation vector that the launch vehicle supportteam reports against the launch separation vector that FDF calculates based on the updatedlaunch information.


4-60



The report compares the time-slipped nominal separation vector (or if available the FDF-determined separation vector from inertial guidance telemetry or radar data) versus the ELV-vendor supplied actual separation vector.4.1.2.13.2 Support DurationFDF generates this report only once during the launch and early orbit mission phase, nominallywithin the first hour of the mission. FDF will also generate this report in support of pre-missionrehearsals that are configured to provide test and training of the launch day support for the LROmission team.4.1.2.13.3 FormatThe report is an ASCII formatted file in which the fields are tab delimited. The report fieldsprovide the comparison between the reported launch vehicle separation vector and the FDF-calculated launch vehicle separation vector (updated to reflect the actual launch epoch). Thereport is a multi-line file, which contains the two original vectors (and their magnitudes) and thenthe position and velocity magnitudes of the differences. This information is identified in thefollowing table:

Table 4-15 FDF – LRO Post Separation Report Data Description Information

Field name Field CharacteristicsLine 1 – from EELV Launch Support Team

LV Separation Time:yearday of year andtime of day



X-Position (Km) RRRRRR.rrr => 10 ASCII characters including the period between the first 6 andlast 3

first 6 are the whole value X-component of the LV separation positionlast 3 are the decimal portion of the X-component position


first 6 are the whole value Y-component of the LV separation positionlast 3 are the decimal portion of the X-component position


first 6 are the whole value Z-component of the LV separation positionlast 3 are the decimal portion of the Z-component position



4-61



Field name Field CharacteristicsY-Velocity (Km/s) RR.rrrrrr => 9 ASCII characters including the period between the first 2 and last 6

first 2 are the whole portions of the Y-component of the LRO’s velocitylast 6 are the decimal portion of the Y-component velocity


LV Position VectorMagnitude

RRRRRR.rrr => 10 ASCII characters including the period between the first 6 andlast 3

first 6 are the whole portions of the Magnitude of the position vectorlast 3 are the decimal portion of the Magnitude of the position vector

LV Velocity VectorMagnitude


first 6 are the whole portions of the Magnitude of the velocity vectorlast 3 are the decimal portion of the Magnitude of the velocity vector

Line 2 – FDF Calculated Data

FDF Calculated SeparationTime:yearday of year andtime of day



X-Position (Km) RRRRRR.rrr => 10 ASCII characters including the period between the first 6 andlast 3

first 6 are the whole value X-component of the FDF separation positionlast 3 are the decimal portion of the X-component position


first 6 are the whole value Y-component of the FDF separation positionlast 3 are the decimal portion of the X-component position


first 6 are the whole value Z-component of the FDF separation positionlast 3 are the decimal portion of the Z-component position


Y-Velocity (Km/s) RR.rrrrrr => 9 ASCII characters including the period between the first 2 and last 6first 2 are the whole portions of the Y-component of the LRO’s velocitylast 6 are the decimal portion of the Y-component velocity



4-62



Field name Field CharacteristicsFDF Position VectorMagnitude


first 6 are the whole portions of the Magnitude of the position vectorlast 3 are the decimal portion of the Magnitude of the position vector

FDF Velocity VectorMagnitude


first 6 are the whole portions of the Magnitude of the velocity vectorlast 3 are the decimal portion of the Magnitude of the velocity vector

Line 3 – Launch Vehicle Separation Comparison

Magnitude of the PositionDifference


first 6 are the whole portions of the position Delta Magnitudelast 3 are the decimal portion of the position Delta Magnitude

Magnitude of the VelocityDifference


first 6 are the whole portions of velocity Delta Magnitudelast 3 are the decimal portion of the Delta Magnitude

A sample file name for the first generation of this data file (for a launch date of 28 October 2008)is given as FDF18_20090152008302_2008302_n01.txtA sample of the Post Separation Report product is provided as a reference in Appendix B, FigureB.1-21Figure B.1-20Figure B.1-19.4.1.2.13.4 Accuracy and CompletenessThe product represents estimated positions from either inertial guidance data or a pre-launchestimate of the position of LRO. The accuracy will be to the best available from the data.4.1.2.14 (FDF-20) Predicted LRO Ephemeris File4.1.2.14.1 Product DescriptionThis file contains predictive LRO ephemeris data for the spacecraft position and velocityinformation centered at one minute increments. The file is generated in an inertial, mean J2000coordinate reference frame. The coordinate frame will be Earth-centered for pre-LOI missionphases and moon-centered for post-LOI mission phases

This product will transition from being Earth-Centered J2000 to Moon-centered J2000 followingLOI (or as needed).4.1.2.14.2 Support DurationFDF will generate this file for all mission phases.4.1.2.14.3 FormatThe Predictive LRO Ephemeris file is an ASCII-formatted file in which the fields are tabdelimited. The file contains the time of the sample, the X,Y, Z position information (given inKilometers, or Km) and the X, Y, and Z velocity components (given in Kilometers per second, or


4-63



Km/sec). The file entries are generated at five minute increments. The following table providesa brief description of each field:

Table 4-16 FDF – LRO Predictive Ephemeris Data Description Information



X-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodSigned first 6 whole portions of the X-component of LRO’s position*last 6 are the decimal portion of the X-component position

Y-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodSigned first 6 are the whole portions of the Y-component of the LRO’s

position*last 6 are the decimal portion of the Y-component position

Z-Position SRRRRRR.rrrrrr (km) => 14 ASCII characters including the periodSigned first 6 are the whole portions of the Z-component of the LRO’s

position*last 6 are the decimal portion of the Z-component position

X-Velocity SRRRRRR.rrrrrr (km/sec) => 14 ASCII characters including the periodSigned first 6 are the whole portions of the X-component of the LRO’s

velocity*last 6 are the decimal portion of the X-component velocity

Y-Velocity SRRRRRR.rrrrrr (km/sec) => 14 ASCII characters including the periodSigned first 6 are the whole portions of the Y-component of the LRO’s

velocity *last 3 are the decimal portion of the Y-component velocity

Z-Velocity SRRRRRR.rrrrrr (km/sec) => 14 ASCII characters including the periodSigned first 6 are the whole portions of the Z-component of the LRO’s

velocity*last 6 are the decimal portion of the Z-component velocity

* - Signed whole number is floating point and could be from 1 to 7 characters for LRO

A sample file name for the first generation of this data file is given asFDF20_2009015_2009022_n01.txtFDF will generate this product on a daily basis or update the file after each LRO maneuver; theproduct will include 7 days worth of data. The file contains data at a one minute step size.A sample Predictive LRO Ephemeris File data file is provided as a reference in Appendix B,Figure B.1-22Figure B.1-21Figure B.1-20.4.1.2.14.4 Accuracy and Completeness


4-64



In nominal lunar mission orbit, the FDF-generated Predicted LRO Ephemeris File shall have anaccuracy over the 84-hours prediction, of less than 800 m in along-track error. This predictivecompares are not applicable across spacecraft maneuvers..4.1.2.15 (FDF-21) Predicted Lunar Ground Track File4.1.2.15.1 Product DescriptionThis file contains the predictive LRO ground track against the lunar surface. The Predicted LunarGround Track provided this information in the principal axis (PA) reference frame.4.1.2.15.2 Support DurationFDF will generate this file for all only post-LOI mission phases.4.1.2.15.3 FormatThe Predictive Lunar Ground Track file is an ASCII-formatted file in which the fields are tabdelimited. The file contains the time of the sample, the lunar Longitude and Latitude position,the LRO altitude, and ground track velocity every 60 seconds. The longitude and latitudeinformation is based on the DE416 reference frame. The LRO altitude is given in Kilometers (orKm), the LRO ground track velocity magnitude given in Kilometers per second, or Km/sec).The file entries are generated at one minute increments. The following table provides a briefdescription of each field:

Table 4-17 FDF – LRO Predicted Ephemeris Data Description Information



Lunar Longitude RRR.rrr (degrees) => 7 ASCII characters including the period between the first 3and last 3

first 3 are the whole degrees of Longitude East (0- 360)last 3 are the degree decimal of Longitude (000- 999)

Lunar Latitude SRR.rrr (degrees) => 6 ASCII characters including the period between the first 3and last 3

first character is the sign (blank = Northern Lats; - = Southern Lats)next 2 are the whole degrees of Latitude (0- 90)last 3 are the degree decimal of Latitude (000- 999)

LRO Altitude RRR.rrr (km) => 7 ASCII characters including the period between the first 3 andlast 3

first 3 are the whole portions of the LRO’s altitude in floating point (expectedvalues for LRO are 000 – 999 km)

last 3 are the decimal portion of the LRO’s altitude (in hundredths of Km, 000 – 999)


4-65



Ground Track-VelocityMagnitude

SRRRRRR.rrr (km/sec) => 10 ASCII characters including the period between thefirst 6 and last 3

first 6 are the whole portions of the X-component of the LRO’s velocity(floating point value, expected value for LRO is single digit)


A sample file name for the first generation of this data file is given asFDF21_2009015_2009022_n01.txtProduct will be generated daily and updated after each LRO maneuver. Product will include 7days worth of data. Data will be provided at a one minute step size.A sample LRO Predictive Lunar Ground Track File is provided as a reference in Appendix B,Figure B.1-23Figure B.1-22Figure B.1-21.4.1.2.15.4 Accuracy and CompletenessThe file data contents will be accurate to 0.02 deg.

4.1.2.16 (FDF-22) Definitive Lunar Ground Track File4.1.2.16.1 Product DescriptionThis file contains the definitive LRO ground track against the lunar surface based on the mostrecent definitive ephemeris. The Definitive Lunar Ground Track file provides this information inthe PA reference frame.4.1.2.16.2 Support DurationFDF will generate this file for all only post-LOI mission phases.4.1.2.16.3 FormatThe Definitive Lunar Ground Track file is an ASCII-formatted file in which the fields are tabdelimited. The file contains the time of the sample, the lunar Longitude and Latitude position,the LRO altitude, and ground track velocity every 60 seconds. The longitude and latitudeinformation is based on the DE416 reference frame. The LRO altitude is given in Kilometers (orKm), the LRO ground track velocity magnitude given in Kilometers per second, or Km/sec).The file entries are generated at one minute increments. The following table provides a briefdescription of each field:

Table 4-18 FDF – LRO Definitive Lunar Ground Track Description Information



Lunar Longitude RRR.rrr (degrees) => 7 ASCII characters including the period between the first 3and last 3

first 3 are the whole degrees of Longitude East (0- 360)last 3 are the degree decimal of Longitude (000- 999)


4-66



Lunar Latitude SRR.rrr (degrees) => 7 ASCII characters including the period between the first 3and last 3

first character is the sign (blank = Northern Lats; - = Southern Lats)next 2 are the whole degrees of Latitude (0- 90)last 3 are the degree decimal of Latitude (000- 999)

LRO Altitude RRR.rrr (km) => 7 ASCII characters including the period between the first 3 andlast 3

first 3 are the whole portions of the LRO’s altitude in floating point (in Km,000 – 999)

last 3 are the decimal portion of the LRO’s altitude (in hundredths of Km, 000 – 999)

Ground Track VelocityMagnitude

SRRRRRR.rrr (km/sec) => 11 ASCII characters including the period between thefirst 6 and last 3

first signed 6 are the whole portions of the X-component of the LRO’svelocity in floating point (value will typically be 1.6)


A sample file name for the first generation of this data file is given asFDF22_2009014_2009015_n01.txtProduct will be generated weeklydaily, on Wednesdays. Product will include 7 the previous daysworth of data. Data will be provided at a one minute step size.A sample Definitive Lunar Ground Track File is provided as a reference in Appendix B, FigureB.1-24Figure B.1-23Figure B.1-22.4.1.2.16.4 Accuracy and CompletenessThe file data contents will be accurate to 0.01 deg.

4.1.2.17 (FDF-33) SPICE Binary PCK (High-Precision Lunar Orientation)4.1.2.17.1 Product DescriptionThe SPICE Binary PCK (High-Precision Lunar Orientation) file is based upon informationsupplied by FDF; the NAIF creates the final product based on the FDF inputs.4.1.2.17.2 Support DurationThis file is generated for post-LOI mission phases.4.1.2.17.3 FormatA sample file name for the first generation of this data file is given as FDF33_2009015_n01.bspfor a binary file (little Endian format) or .xsp for a SPICE SPK Transfer Format. {Sample sentin .xsp format}.The SPICE ID for LRO is -85, as assigned by JPL.

The product will be generated daily. Product will include 28 days worth of data. SPK file will betype 13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in the Appendix B.4.1.2.17.4 Accuracy and Completeness


4-67



TBR4.1.2.18 (FDF-36) FDF Reprocessed SPICE Definitive SPK Ephemeris (High-Precision

Orbit Ephemeris)Data1.1.1.1.14.1.2.18.1 Product DescriptionThe FDF Reprocessed SPICE Definitive SPK ephemeris file provides the LRO ephemeris basedupon a DE416 reference frame. FDF creates this product using the LRO OD reprocessing resultswhich will include laser tracking measurements and LOLA OD and Improved gravity modelproducts.This reprocessed SPICE Binary SPK file is based upon both S-band and laser tracking. SinceFDF generates a 55-hour solution arcs for the LRO orbit determination (with 7-hr overlapperiods), ephemeris data will be generated in 48-hr non-continguouscontiguous segments. Thisproduct will only be generated in post-processing using the laser data, not for day-to-daynavigation support of the mission. This product will be sent to the NAIF/PDS for permanentarchival from the MOC.1.1.1.1.24.1.2.18.2 Support DurationFDF generates this product twice during the nominal mission. The FDF Reprocessed SPICEDefinitive SPK file is to be provided to the NAIF/PDS at launch + 3 months, and at launch + 1year.1.1.1.1.34.1.2.18.3 FormatThe FDF Reprocessed SPICE Definitive SPK file is a binary formatted file generated by theSPICE Toolset. The SPICE ID for LRO is -85, as assigned by JPL.

A sample file name for the first generation of this data file is given asFDF36_2009015__2009022_n01.xsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format. {Sample sent in .xsp format}. The format will be SPICE .xsp which is aTransfer Format.

The product will include all definitive portions of the mission since LOI. SPK file will be type13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in Appendix B.1.1.1.1.44.1.2.18.4 Accuracy and CompletenessTBR

4.1.2.19 (FDF-37) FDF Solar Conjunction File1.1.1.2.14.1.2.19.1 Product DescriptionThe Solar conjunction File contains the periods whenever the sun, Orbiter and earth align suchthat the sun is either within 3-5 degrees of the Orbiter and earth. In these instances, there will besolar Radio Frequency interference (RFI) that affects the scheduled station contact. This fileidentifies these periods of solar RFI and identifies the sun position as either a Type 1 (in-linewith the earth to Orbiter vector) or Type 2 (in-line with the Orbiter to earth vector).


4-68



The solar conjunction predictions will contain all upcoming conjunctions on both the uplink andthe downlink within the product span. For many of the deliveries, no solar conjunctions may bepresent during the product span. If there are no times of solar conjunction, the file will onlycontain the base header information for each station). The uplink conjunction limit is set at 3degrees, whereas the downlink conjunction limit is set currently at 5 degrees.4.1.2.19.2 Support DurationFDF generates this product on a weekly basis during the nominal mission and after post lunarinsertion. This product contains the next 28 days of potential solar RFI; is there are no periods ofsolar RFI, the file only contains the base header information for each station.4.1.2.19.3 FormatThe solar Conjunction File is an ASCII text formatted file. The solar conjunction file willcontain the start time, stop time and a flag to indicate what type of solar conjunction (e.g., Type 1or Type 2 as an example). The following table provides a description of the fields within the file.

Table 4-19 Solar Conjunction Data Description

Field name Field CharacteristicsStation name 31 ASCII text characters representing the unique station identifier, with the

following format:Satellite-0059-to-Facility-NNNN; whereNNNN = LR1S for LRO White Sands S-band Station

LR1K for White Sands Ka-Band StationSDSS for SDO/LRO STGT backupUSPS for USN DongaraUSHS for USN South Point, HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, GermanyDS24 for the DSN 34-m at Goldstone, CaDS34 for the DSN-34m at Canberra, AustraliaDS54 for the DSN 34-m at Madrid, Spain

Start Time information:yearday of year andtime of day



Stop Time information:yearday of year andtime of day



Solar Conjunct Type 6 ASCII CharactersType n; where n = 1 or 2 depending on the geometry



4-69



Product will be generated on a weekly basis, on Wednesday of the week; it will include the next28 days of data. Data will be provided at a one minute step size.

A sample of the Solar Conjunction product is provided as a reference in Appendix B, Figure B.1-27Figure B.1-2623.4.1.2.19.4 Accuracy and CompletenessThe file start and stop times are accurate to 1 second.4.1.2.20 (FDF-25) Thruster Calibration Data4.1.2.20.1 Product DescriptionThis is a report that includes updated parameters for thruster calibration table.4.1.2.20.2 Support DurationThe FDF provides this Thruster Calibration data throughout all mission phases, from pre-launch(to support mission rehearsals and other project related tests) up through all mission phases.4.1.2.20.3 FormatThe file is an ASCII formatted file that provides the thruster calibration data file in which thefields are tab delimited. The report is a multi-line file that contains both meta-data and thrustercalibration data. The meta-data corresponds to when the report was generated, the start and stoptimes and other information related to the thruster calibration function.A sample file name for the first generation of this data file is given asFDF25_2009015_2009015_n01.txtA sample Thruster Calibration Data File is provided as a reference in .4.1.2.20.4 Accuracy and CompletenessTBR4.1.2.21 (FDF-26) LRO Momentum Management Unload Plan4.1.2.21.1 Product DescriptionThis is a report that identifies when the LRO spacecraft will perform a momentum managementmaneuver.4.1.2.21.2 Support DurationThe FSF provides this Momentum Management Unload Plan throughout all mission phases,from pre-launch (to support mission rehearsals and other project related tests) up through allmission phases.4.1.2.21.3 FormatThe file is an ASCII formatted file that provides the requested maneuver commands required tosupport the momentum management function file in which the fields are tab delimited. Thereport is a multi-line file that contains both meta-data and momentum management thrustermaneuver information. The meta-data corresponds to when the report was generated, the startand stop times and other information related to the momentum management function.


4-70




A sample LRO Momentum Management Unload Plan is provided as a reference in Appendix B,Figure B.1-26Figure B.1-25.4.1.2.21.4 Accuracy and CompletenessTBR4.1.3 FDF MOC/ADS ProductsThe following sections provide the details regarding the products that are generated by theattitude determination system that is contained within the LRO MOC facility. The MOC-ADS isdeveloped by the FDF facility and then hosted into the MOC facility, where the LRO operationsteam uses this system to create another set of products used by project and operations personnel.

4.1.3.1(FDF-1) Attitude Determination Verification Report4.1.3.1.1Product DescriptionThis file provides a comparison of the on-board computer (OBC) calculated attitude quaternionversus the ground based calculated attitude quaternion resulting from the MOC-ADS processingof the attitude telemetry. The report is used to verify the performance on the on-board attitudesystem.4.1.3.1.2Support DurationThe MOC-ADS provides this report for all mission phases4.1.3.1.3FormatThe file is an ASCII formatted multi-line report that provides the information related to the OBCcalculated attitude as compared with a ground-based solution from the MOC-ADS element. Thereport contains meta-data related to when the report was generated, the start and stop times of theattitude information, and what inputs were used in the calculations. The report also contains theattitude comparison for the time period referenced in the metadata.A sample file name for the first generation of this data file is given as FDF01_2009015_n01.txt

A sample Attitude Determination Verification Report file is provided as a reference in FigureB.1-24.4.1.3.1.4Accuracy and CompletenessThe report is accurate to TBR4.1.3.2(FDF-2) Attitude Slew Plans4.1.3.2.1Product DescriptionThis file contains the attitude quaternions for the various orbiter attitude slews requiredthroughout the mission. This file can consist of either one instance of an attitude slew (and thusone quaternion set) or a series of attitude slews (and therefore multiple sets of quaternions).4.1.3.2.2Support Duration


4-71



The MOC-ADS provides this report for all mission phases4.1.3.2.3FormatThe file is an ASCII formatted file that provides the attitude quaternions corresponding to arequested attitude slew maneuver. The file can be one line representing a single attitude slew, orit can consist of multiple lines representing a set of attitude slews. For each line, the dataconsists of a start time, the corresponding off-nadir angle slew and the corresponding attitudequaternion for that slew. The fields are ASCCI text separated by blanks. The following tableprovides a brief description of each field:

Table 4-20 FDF – Attitude Slew Plan Data Description Information

Field name Field CharacteristicsSlew Type ST => 1 ASCII Character that identifies the type of slew

= T; Table Offset =P; off-nadir pointing

time information:yearday of year andtime of day

YYYY DDD HHMMSS.sss, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day

Off-Nadir Slew Angle RRR.rrr => 6 ASCII characters including the period between the first 3 and last 3 first 2 are the whole degrees of requested slew (0- 99) last 3 are the degree decimal of Longitude (000- 999)

Attitude Quaternions Q1 Q2 Q3 Q4

4 quaternions that represent the attitude of the requested slew; each quaternion hasone of the following two representation: (-.rrrrrr or .rrrrrr))1 ASCII Signed Character (Blank represents a positive Q or – for a negative Q)an ASCII character for the decimal point6 ASCII characters representing the decimal portion of the attitude Q

A sample file name for the first generation of this data file is given as FDF02_2009015_n01.txtA sample Attitude Slew Plan file is provided as a reference in Figure B.1-25.4.1.3.2.4Accuracy and CompletenessThe report is accurate to TBR

4.1.3.3(FDF-11) Gyro Calibration Data4.1.3.3.1Product DescriptionThis is a report that includes updated parameters for gyroscope calibration table. This reportprovides an analysis of the gyro, which is also referenced as the inertial reference unit (IRU).4.1.3.3.2Support Duration


4-72



The MOC-ADS provides this Gyro Calibration data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission phases.4.1.3.3.3FormatThe file is an ASCII formatted file that provides the gyro calibration data. The report is a multi-line file that contains both meta-data and calibration data. The meta-data corresponds to whenthe report was generated, the start and stop times of the gyro data used in this calibrationfunction. The report also contains the gyro calibration information such as 3x3 drift rate matrix,a 1x3 IRU scale factor matrix, a 3x3 IRU misalignment matrix.

A sample file name for the first generation of this data file is given as FDF11_2009015_n01.txtA sample Gyro Calibration Data File is provided as a reference in Figure B.1-26.4.1.3.3.4Accuracy and CompletenessTBR4.1.3.4(FDF-12) HGA Calibration Data4.1.3.4.1Product DescriptionThis is a report that includes updated parameters for HGA calibration table.4.1.3.4.2Support DurationThe MOC-ADS provides this HGA Calibration data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through all missionphases.4.1.3.4.3FormatThe file is an ASCII formatted file in which the fields are tab delimited. The file provides theHGA calibration data. The report is a multi-line file that contains both meta-data and HGAcalibration data. The meta-data corresponds to when the report was generated, the start and stoptimes and other information related to the HGA calibration function. The file is generated usingthe White Sands antenna signal strength over a known time period.A sample file name for the first generation of this data file is given as FDF12_2009015_n01.txt

A sample HGA Calibration Data File is provided as a reference in Figure B.1-27.4.1.3.4.4Accuracy and CompletenessTBR

4.1.3.5(FDF-24) Star Tracker Calibration Data4.1.3.5.1Product DescriptionThis is a report that includes updated parameters for Star Tracker calibration table.4.1.3.5.2Support Duration


4-73



The MOC-ADS provides this Star Tracker Calibration data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through all missionphases.4.1.3.5.3FormatThe file is an ASCII formatted file that provides the Star Tracker calibration data file in whichthe fields are tab delimited. The report is a multi-line file that contains both meta-data and StarTracker calibration data. The meta-data corresponds to when the report was generated, the startand stop times and other information related to the Star Tracker calibration function.A sample file name for the first generation of this data file is given as FDF24_2009015_n01.txt

A sample Star Tracker Calibration Data File is provided as a reference in Figure B.1-29.4.1.3.5.4Accuracy and CompletenessTBR

4.1.3.1 (FDF-25) Thruster Calibration Data4.1.3.1.1Product DescriptionThis is a report that includes updated parameters for thruster calibration table.4.1.3.1.2Support DurationThe MOC-ADS provides this Thruster Calibration data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through all missionphases.4.1.3.1.3FormatThe file is an ASCII formatted file that provides the thruster calibration data file in which thefields are tab delimited. The report is a multi-line file that contains both meta-data and thrustercalibration data. The meta-data corresponds to when the report was generated, the start and stoptimes and other information related to the thruster calibration function.A sample file name for the first generation of this data file is given as FDF25_2009015_n01.txt

A sample Thruster Calibration Data File is provided as a reference in Figure B.1-30.4.1.3.1.4Accuracy and CompletenessTBR

4.1.3.1(FDF-26) LRO Momentum Management Unload Plan4.1.3.1.1Product DescriptionThis is a report that identifies when the LRO spacecraft will perform a momentum managementmaneuver.4.1.3.1.2Support DurationThe MOC-ADS provides this Momentum Management Unload Plan throughout all missionphases, from pre-launch (to support mission rehearsals and other project related tests) up throughall mission phases.


4-74



4.1.3.1.3FormatThe file is an ASCII formatted file that provides the requested maneuver commands required tosupport the momentum management function file in which the fields are tab delimited. Thereport is a multi-line file that contains both meta-data and momentum management thrustermaneuver information. The meta-data corresponds to when the report was generated, the startand stop times and other information related to the momentum management function.A sample file name for the first generation of this data file is given as FDF26_2009015_n01.txt

A sample LRO Momentum Management Unload Plan is provided as a reference in Figure B.1-31.4.1.3.1.4Accuracy and CompletenessTBR4.1.3.2 (FDF-27) Star Tracker Occultation Report4.1.3.2.1Product DescriptionThis is a report that includes identified when the star tracker field of view is occulted by themoon.4.1.3.2.2Support DurationFDF provides this Star Tracker Occultation Report throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through all missionphases.4.1.3.2.3FormatThe file is an ASCII formatted file that provides the Star Tracker occultation data file in whichthe fields are tab delimited. The report is a multi-line file that contains each instance of when theStar Tracker’s field of view is occulted. The file contains the occultation start time, theoccultation stop time, the occultation duration, and a flag indicator that identifies what caused thestar tracker occultation. The following table provides a description of the fields:

Table 4-21 FDF – Tracker Occultation Report Data Description Information

Field name Field CharacteristicsOccultation Start Time:yearday of year andtime of day



4-75



Field name Field CharacteristicsOccultation Stop Time:yearday of year andtime of day


Occultation Duration MMM.mm => 6 ASCII digits with a period between the first 3 and last 2 first 3 are the whole minutes of occultation (0 -999) last 2 are the decimal portion of the occultation (0 – 99)

Occultation Flag O => 1 ASCII Character that identifies the cause of the star tracker occultation = M; moon has occulted star tracker =E; earth has occulted star tracker =S, sun has occulted star tracker

A sample file name for the first generation of this data file is given as FDF27_2009015_n01.txtA sample Star Tracker Occultation Report is provided as a reference in .4.1.3.2.4Accuracy and CompletenessTBR4.1.3.3(FDF-34) SPICE Predicted CK (Predicted S/C Orientation)4.1.3.3.1Product DescriptionThe SPICE Predicted CK file contains the predicted LRO spacecraft orientation with respect toits orbit.4.1.3.3.2Support DurationThe SPICE Predicted CK File is generated for after the post-LOI mission phases.4.1.3.3.3FormatThe SPICE Predicted CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF34_2009015_2009042_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.The SPICE ID for LRO is -85, as assigned by JPL.

The product will be generated daily. Product will include 28 days worth of data. SPK file will betype 13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in the Appendix.4.1.3.3.4Accuracy and CompletenessTBR

4.1.2.22(FDF-35) SPICE Definitive CK (Definitive S/C, HGA, SA Orientation)4.1.2.22.1Product Description


4-76



The SPICE Definitive CK file contains the definitive LRO spacecraft orientation of the High-Gain Antenna and the Solar Arrays with respect to the LRO spacecraft..4.1.2.22.2Support DurationThe SPICE Definitive CK File is generated for after the post-LOI mission phases.4.1.2.22.3FormatThe SPICE Definitive CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF35_2009014_2009015_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.The SPICE ID for LRO is -85, as assigned by JPL.


4.1.3.11(FDF-31) HGA/SA Fixed Ooffset SPK4.1.3.11.1Product DescriptionThe HGA/SA Fixed Offset SPK CK file contains the as-measured HGA and SA orientation inreferenced to the LRO spacecraft.4.1.3.11.2Support DurationThe HGA/SA Fixed Offset SPK CK file is generated for after the post-LOI mission phases.4.1.3.11.3FormatThe HGA/SA Fixed Offset SPK CK file is an binary ASCII formatted file generated by theSPICE ToolsetLRO Project and support personnel. A sample file name for the first generation ofthis data file is given as FDF31_2009015_n01.bsp txt for a binary text file (little Endian format)or .xsp for a SPICE SPK Transfer Format. {Sample sent in .xsp format}.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated daily. Product will include 28 days worth of dataat most twiceduring the mission; once during the pre-launch mission phase and then once post-luanch. TheHGA/SA Fixed Offset CK fileSPK file will be type 13 and interpolation order 11; since this is abinary formatted file, no is provided as a sample product will be shown in the Appendix B,Figure B.1-33.

A sample file name for the first generation of this data file is given as FDF31_2009015_n01.bsptxtfor a binary file (little Endian format) or .xsp for a SPICE SPK Transfer Format. {Samplesent in .xsp format}.The SPICE ID for LRO is -85, as assigned by JPL.


4-77




4.1.3.12(FDF-32) SPICE Generic PCK (Planetary Constants)4.1.3.12.1Product DescriptionThe SPICE Generic PCK file provides the planetary or lunar ephemeredes based upon a DE405reference frame.4.1.3.12.2Support DurationThe SPICE Generic PCK file is generated for after the post-LOI mission phases.4.1.3.12.3FormatThe SPICE Generic PCK file is a binary formatted file generated by the SPICE Toolset. TheSPICE ID for LRO is -85, as assigned by JPL.

A sample file name for the first generation of this data file is given as FDF32_2009015_n01.bspfor a binary file (little Endian format) or .xsp for a SPICE SPK Transfer Format. {Sample sentin .xsp format}.The product will be generated daily. Product will include 28 days worth of data. SPK file will betype 13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in the Appendix.4.1.3.12.4Accuracy and CompletenessTBR4.2 STATION PRODUCTS AND DESCRIPTIONSThe following sections provide the details on the interface products generated by the variousground stations used to support the LRO mission. The following several products are derived byor created by various groups that fall under the general category of the Space CommunicationsNetwork. They provide specific information required by the LRO mission and are used either insupport of the Mission Operations Center or by various entities within the LRO missionThe following sections identify the interfaces sent by the LRO MOC to the various groundstations supporting the LRO mission. Nominally, these interfaces are used to transmit commandfrom the LRO MOC to the corresponding station. The command structure that the LRO MOCuses is dependant upon the station that is scheduled to be the interface for sending commands tothe LRO spacecraft. The following conventions are used by the LRO MOC to support theinterface with each of the corresponding stations:

• SMEX/LEOT Header for transferring telemetry from either WS1 or USN stations to theLRO MOC


4-78



• Cortex Header for transferring high-speed VC2 and VC 3 telemetry frames from the WS1station to the LRO-supplied mission unique equipment (MUE) located at the station

• Space Link Extension (SLE) telemetry structure for interfacing with DSN stations• SMEX/LEOT Telemetry Structure for interfacing with the Space NetworkThe SMEX/LEOT Telemetry header is 20 bytes long and has the following data structure asidentified in Figure 4-1Figure 4-1; Table 4-22Table 4-20 provides a reference definition for thefields contained within the SMEX/LEOT Telemetry Header.

The ground station will decommutate the Channel Access Data Units (CADU) received from thespacecraft and perform Reed Solomon decoding for eventual delivery of the Virtual ChannelData Unit (VCDU) to the MOC. The SMEX/LEO-T Telemetry header is a 20 byte headerattached to every VCDU that is forwarded in real-time to the MOC’s T&C system. The detailsfor the CADU & VCDU definition are documented in the T&C Formats Handbook. In thefigure below, the fields are represented in bits, not bytes.

Figure 4-1 SMEX/LEOT Telemetry Header

Table 4-2220 SMEX/LEOT Field Definitions and Expected Values

Field Name Size(bits)

LROValue

Nominal Values

Version 2 ‘01’ Value = 01, frame data

Message Length 14 1798decimal

for LRO = 1798 bytes (includes frame synch)

Reed-Solomon EnableFlag

1 ‘1’ Value = 0, RS not enabled;1, RS enabled

Will be 1 for LRO

Reed-Solomon ErrorFlag

1 variable Value = 0, no RS errors1, RS errors

CRC Enable Flag 1 ‘1’ Value = 0, CRC not enabled;1, CRC enabled

CRC Pass/Fail 1 variable Value = 0, pass;1, fail

Master channel sequence(MCS) checking enabledflag

1 ‘0’ Value = 0, MCS not enabled;1, MCS enabled

Not applicable for LRO


4-79



Field Name Size(bits)

LROValue

Nominal Values

MCS number error 1 ‘0’ Value = 0, number increased monotonically;1, number increased by 2 or more;

Not applicable for LRO

Data inversion flags 2 variable Value = 00, data true;01, data inverted;02, data inverted and corrected

Frame sync mode flags 2 variable Value = 00, search frame;01, check frame;02, lock frame;03, flywheel frame

Data forward/reverseflag

1 variable Value = 0, data forward;1, data reversed

Data Class 5 ‘01’ or’02’

Value = 01, spacecraft telemetry02, spacecraft command (will be used to identify the station status packet)03, tracking data (N/A for LRO)

Earth received time ofdata (PB-5 format): flagbit

1 ‘0’ 1 PB5 flag bit; value = 0

Earth received time ofdata (PB-5 format):truncated Julian day

14 variable 2-15 Truncated Julian day; 14 bits; truncate the mostsignificant decimal digits, retaining only the four leastsignificant decimal digits ranging from 0000 to 9999. Thecurrent Julian day epoch begins on is Jan 01, 2001

Earth received time ofdata (PB-5 format):seconds of day

1 variable 16 Seconds of day; 17 bits; most significant bit

Earth received time ofdata (PB-5 format):seconds of day

16 variable 1-16 Seconds of day; 17 bits total; remaining 16 bits fromword 3, bit 16, above. Value is variable; range is 0 to86,399; binary unsigned integer

Earth received time ofdata (PB-5 format):milliseconds of a second

10 variable 1-10 Milliseconds of a second; value is variable; range is 0to 999; binary unsigned integer

Fill / spare 6 0 16 Fill/spare

The DSN formats the received telemetry data within a Space Link Extension (SLE) telemetryframe. Figure 4-2 provides a representation of the SLE telemetry header; Table 4-21 providesthe field definitions used for the SLE telemetry header fields.

Figure 4-2 is TBS


4-80



Figure 4-2 SLE Telemetry Header StructureThe fields, represented within this figure are defined with the following table:Table 4-33 is TBS

Table 4-21 SLE Telemetry Header Structure Definitions

The Space Network formats the telemetry packets within a SMEX/LEOT structure asrepresented in Figure 4-1Figure 4-1; Table 4-22Table 4-20 provides the field definitions used forthe header fields.

4.2.1 Space Communication Network (WS1) Product Descriptions4.2.1.1 (GNSO-1) SCN Support Schedules4.2.1.1.1 Product DescriptionThis is a schedule file that contains 1 week of station contacts that support LRO; this supportschedule includes WS1, USN, and DSN and SN contacts when required. This support scheduleis the version that the Mission planning System ingests as part of its timeline generation function.The Station support schedule is three separate files that are created to cover various Monday –Sunday weekly activity schedules. The details and specifics related to how the schedules aredefine, created, reviewed, and modified are covered under the ICD between the LRO Project andthe NASA Ground Network (NGN). The basic concepts for the mission schedule identifies threeworking versions that are used to identify the over all station support schedules for future weeksas noted here:

• Strawman Schedule – generated and delivered to the LRO MOC approximately 3 week28days prior to the start of that week’s operational supports and planned scheduled stationcontacts

• Forecast Schedule – generated and delivered to the LRO MOC approximately 2 weeksprior to the start of that week’s operational supports and planned scheduled stationcontacts

• Operational Schedule – generated and delivered to the LRO MOC on the Thursday priorto the start of the operational scheduled events; this schedule is conflict free.

4.2.1.1.2 Support DurationWOTIS will provide the Station Support Schedules throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.1.3 FormatThe Station Support Schedule file is an ASCII-formatted file and consists of the station name,start time, stop time, duration, and configuration identified for the requested station support; thefollowing table provides a brief description of each field: The support activity codes, as initiallydefined within Table 4-25Table 4-22Table 4-23, are only used to identify a preliminary set of TR


4-81



codes. The LRO operations team and WOTIS scheduling personnel will coordinate the actualcodes and how the codes reference Ka-band and S-band Station contacts.

Table 4-242122 SCN Station Support Schedule Field Definitions

Field name Field CharacteristicsStation Name 4 ASCII Characters that uniquely identify the station

Start time:yearday of year andtime of day

YYYY DDD HHMMSS.mmm, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3


Stop time:yearday of year andtime of day



Support Activity Code 4 ASCII Character that identifies the station configuration used to support the LROstation contact; allowable values are: TR1 – TR99;The actual TR codes are listed in the Table 4-25Table 4-22Table 4-23

Orbit Number 10 ASCII Characters representing a monotonically increasing orbit counter

Band 2 ASCII Characters representing the support contact type; whereS1 = S-band SupportK1= Ka-Band Support

Antenna Used 1 ASCII characters that identify the LRO antenna used for this supportH => High Gain Antenna scheduledO => Omni antenna scheduled

Table 4-252223 LRO TR Code Assignments

Telemetry RateTR CodeS-Band Ka-Band

Command Rate Ranging

TR1 NA 100 Mbps NA NA

TR2 256 Kbps NA 4 kbps Yes

TR3 256 Kbps NA 4 kbps No





4-82



Telemetry RateTR CodeS-Band Ka-Band

Command Rate Ranging


TR8 125 bps NA 4 kbps Yes

TR9 125 bps NA 4 kbps No







TR16 1.093 Mbps NA 4 kbps Yes

TR17 1.093 Mbps NA 4 kbps No



A sample Station Support Schedule file is identified with the following naming conventions:<S><Mission ID><Schedule Type><Year/Date Information><Schedule Duration>.ext; where

S => 1 Character= S to indicate this is a schedule file from WOTIS

Mission ID => 3 characters to identify the mission= LRO

Year/Date Information => 7 characters in the form of YYYYDDD, whereYYYY – start year designator (2008 – 2013)DDD – start day of year (Monday) for the first

station contact in the schedule file

Schedule Duration => 3 characters d07, d14, wherelast 2 characters represent the number of days

(duration) of the file; nominally set for 7 daysSchedule Type => 1 character to identify the specific schedule

O = operationalF = ForecastW = Strawman

extension => 6 charactersxxxxxx; nominally represent the HHMMSS of the

creation time; this is used to uniquely identify the file


4-83



creation time; this is used to uniquely identify the file

A sample file name for the Support Schedule is defined as follows:

SLROOYYYYDOYd07O.xxxxxx – sample file name for the Ooperational scheduleSLROFYYYYDOYd07F.xxxxxx – sample file name for the Fforecast scheduleSLROWYYYYDOYd14S.xxxxxx - sample file name for the Sstrawman scheduleA file name for the Station Support Schedule is defined as per the NGN ICD.

A sample Station Support Schedule file is provided as a reference in Appendix B, Figure B.2-1Figure B.2-1.4.2.1.1.4 Accuracy and CompletenessThe file will contain all requested support contacts that the LRO project requires to meet the datadownlink requirements and to support the health and safety commanding for the orbiter and theinstrument suite.4.2.1.2 (GNSO-2) SCN Support Schedule Report4.2.1.2.1 Product DescriptionThis schedule report is a human-readable version of the station support schedules that arediscussed in the previous section. This schedule report file includes all station contactssupporting the LRO mission. This version is based upon the email version that was originallygenerated during the SMEX mission and is used more for internal MOT use. The GNSO alsoemails this schedule report to FDF and to the CDDIS interface for Laser Ranging supportfunctions.

As noted in the previous section, this schedule report file is generated in 3 separate versions thatrepresent information on a sliding window to indicate activities 3 weeks in the future (theStrawman Schedule), 2 weeks in the future (Forecast Schedule) and the next week’s operationalschedule (Operational Schedule).4.2.1.2.2 Support DurationThe SCN will provide the Station Support Schedules throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.2.3 FormatThe Station Support Schedule file is an ASCII-formatted file and is consistent with the standardsapplied by Section 9 of the ICD between the LRO Project and the NASA Ground Network(NGN). The file consists of the station name, start time, stop time, duration, and configurationidentified for the requested station support; the following table provides a brief description ofeach field:

Table 4-262324 SCN Station Support Schedule Report Field Definitions


4-84



Field name Field CharacteristicsStation Name 4 ASCII Characters that uniquely identify the station

Start time:yearday of year andtime of day



Stop time:yearday of year andtime of day



Support Activity Code 4 ASCII Character that identifies the station configuration used to support the LROstation contact; allowable values are: TR1 – TR99; these TR codes are defined inTable 4-25Table 4-22Table 4-23

Orbit Number 10 ASCII Characters representing a monotonically increasing orbit counter

Band 2 ASCII Characters representing the support contact type; whereS1 = S-band SupportK1 = Ka-Band Support

Antenna Used 1 ASCII characters that identify the LRO antenna used for this supportH => High Gain Antenna scheduledO => Omni antenna scheduled

A sample Station Support Schedule Report is identified with the following naming conventions:

<Mission ID><Year Designator><Schedule Type><Week Number>.<Version Number>; whereMission ID => 3 characters to identify the mission

= LROYear Designator => 4 characters in the form of YYYY, where

YYYY – start year designator (2008 – 2013)Schedule Type => 1 character to identify the specific schedule

O = operational; this is the active operationalschedule for the upcoming week or current week if file is inresponse to an update request or change due to otherconflicts.

F = ForecastW = Strawman


4-85



Week Number => 3-character field to identify the schedule weekWnn; where 01 = first week in the year with the first

MondayVersion Number => Up to 2-digit field identifying the version for this schedule

file. This field will update to reflect each update to anoperational schedule. This number will agree with thefilename identified in the

A sample file name for the Station Support Schedule Report for the first (0th iteration) of theOperational Schedule Report is defined as per the NGN ICDfollows:.

LRO2009O.w01.0A sample Station Support Schedule file is provided as a reference in Appendix B, Figure B.2-2Figure B.2-2.4.2.1.2.4 Accuracy and CompletenessThe file will contain all requested support contacts that the LRO project requires to meet the datadownlink requirements and to support the health and safety commanding for the orbiter and theinstrument suite.

4.2.1.3 (WS1-5) WS1 Raw Tracking Data4.2.1.3.1 Product DescriptionThe Station Tracking Data File provides the LRO Flight Dynamics Facility with the datarequired to support tracking of the orbiter and generation of orbit and mission products. ThisThese data is are also transferred to the LRO MOC for eventual distribution to the LOLA SOC.

Each SCN supported station contact will create the data in a format identified as the UniversalTracking Data Format (UTDF) as defined in the STDN Tracking and Acquisition Handbook(STDN-724, 1990).The WS1 facility has the ability to provide the tracking data in real-time to support missioncritical activities that occur during the WS1 station contact period. These mission criticalactivities are normally associated with early mission activities, such as the spacecraft separation,trans-lunar injection, or lunar insertion. In this event, the data will be one instance of theinformation that would normally be contained with the UTDF formatted file. As long as data aretransmitted in near real time, the file product would not be limited to five-minute durations. Inthe event of real-time UTDF support, the corresponding data files could be created at hourlyintervals. In the event that the station is not able to create a real time connection with FDF, thenthe station would revert to creating files that are based on capturing five minutes of tracking data.4.2.1.3.2 Support DurationThe SCN will provide the Station tracking Data File throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.


4-86



4.2.1.3.3 FormatThis data will be consistent with STDN-724; WS1 can provide the tracking data either as a real-time data source to FDF or as a post-pass file to both FDF and to the LRO MOC.

The tracking data are in a binary form; one datum contains seventy-five (75) bytes ofinformation as identified in the Tracking and Acquisition Handbook. The data records arecreated at a 60 second interval. The following table provides the fields and field definitions forthe station tracking data. FDF does not reference the data contained within byte 45 or byte 47.Since FDF does not use these two fields, the WS1 stations should default these two bytes so thatthe data product is not corrupt; the stations should set these two values to represent the closestantenna size used to support the LRO missions.

Table 4-272425 WS1 Raw Tracking Data File Field Definitions

Byte Format Description1 0D(16) Fixed

2 0A(16) Fixed

3 01(16) Fixed

4-5 ASCII Tracking Data Router4141=AA=GSFC4444=DD=GSFC

6 Binary Last two digits of current year

7-8 Binary Satellite Identification Code (SIC)

9-10 Binary Vehicle Identification (VID)

11-14 Binary Seconds of year

15-18 Binary Microseconds of second

Note: For bytes 19-22/23-36, convert angle data to decimal form. Angle data is are given in fractions of a circle. Toexpress raw angle in degrees, multiply decimal angle by 8.381903173 x 10-8 (360 degrees divided by 232)

19-22 FOC Angle 1: X or az

23-26 FOC Angle 2; Y or el (angle 2 byte/bit format is the same as for bytes 19-22.)

27-32 Binary RTLT in 1/256 nsec (MSB = 524288 ns; LSB = 0.00390625 ns)

33-38 Binary Bias Doppler, counts of: 240 MHz +1000 fd1 LSB - 1 count

39-40 Binary AGC (an integer * (-150/8192) AGC-50=dBm)

41-44 Binary Transmit frequency information in 10's of Hz


4-87



Byte Format Description45 Discrete MSD = antenna size (xmit) as follows:

0(16) = less than 1 m1(16) = 3.9 m2(16) = 4.3 m3(16) = 9 m4(16) = 12 m5(16) = 26 m6(16) = TDRSS ground antenna7(16) = 6 m8(16) = 7.3 m9(16) through Feet = spares

LSD = antenna geometry (xmit) as follows:0(16) = az-el1(16) = X-Y (+X-south)2(16) = X-Y (+X-east)3(16) = RA-DEC4(16) = HR-DEC5(16) through F(16) = spares

46 Binary Pad ID (xmit)

47 Discrete Antenna size (rcv) – (see byte 45)

48 Binary Pad ID (rcv)

49-50 Discrete Mode-system unique(refer to Table 2)

51 Discrete Data ValidityBit 8 = (MSB) sidelobe (1-sidelobe)

7 = destruct R (1 = destruct)6 = refraction correction to R, R (1corrected)5 = refraction correction to angles (1 =corrected)4 = angle data correction (1 =corrected)3 = angle valid (1=valid)2 = Rº valid (1=valid)1 = (LSB) R valid (1=valid)

52 Discrete MSD = frequency band, as follows:1(16) = VHF2(16) = UHF3(16) = S-band4(16) = C-band5(16) = X-band6(16) = Ku-band7(16) = visible8(16) through F(16) = spares


4-88



Byte Format Description LSD = data transmission type, as follows:

0(16) = test1(16) = spare2(16) = simulated3(16) = resubmit4(16) = RT (real time)5(16) = PB (playback)6(16) through F(16) = spares

53-54 Discrete MSD - tracker type Byte 53, bits 8 thru 5:0(16) = C-band pulse track1(16) = SRE (S-band and VHF) or RER2(16) = X-Y angles only (data acquisition antenna)3(16) = spare4(16) = SGLS (AFSCN S-band trackers)5(16) = spare6(16) = TDRSS7(16) through F(16) = spares

Byte 54, bit 4:1 = last frame of data

Byte 53, bits 3 thru 1 and eight bits of byte 54:11 bits for transmission rate (positive indicates the binary

seconds between samples up to a maximum of 1023; negativeindicates the two's complement of the number of samples persecond).

55-72 Spare

73 04(16) Fixed

74 04(16) Fixed

75 04(16) Fixed

For a real-time interface, WS1 provides the data identified in Table 4-27Table 4-24Table 4-25 asa binary data product to the Flight Dynamics facility; the data are created at a 60-second intervaland immediately forwarded via a socket connection to the FDF. As a post-pass file, WS1 storesthese data into a file and forwards the file to both the FDF and LRO MOC facility.

A sample of the station tracking data file is provided as a reference in Appendix B, Figure B.2-3Figure B.2-34.2.1.3.4 Accuracy and CompletenessTBR


4-89



4.2.1.4 (WS1-10) Archived VC0 Telemetry Data4.2.1.4.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at a station uponreceipt of the real-time spacecraft housekeeping telemetry. These data are stored with the filldata (VC63) removed. These files are stored at the ground station using their local storagefunctionality. The files are stored for up to seventy-two (72) hours in the event of a possibleretransmission to the LRO MOC upon request by the LRO operations team; this would normallybe considered within a contingency support concept.4.2.1.4.2 Support DurationThe SCN will provide the Archived VC0 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.4.3 FormatThe Archived VC0 Telemetry Data is are stored with the VC63 (fill data) removed. The stationarchives the VC0 data stream (the downlinked VCDUs) using the station generatedSMEX/LEOT Header.A sample Archived VC0 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B.When, or if requested, by the LRO MOT, the archived VC0 Telemetry file would be transferredback to the LRO MOC facility using the secure copy mechanism. The archive files that WS1creates are based on a configurable time duration; this configurable duration is set for the LROmission at 60 minutes. However, the LRO Mission Operations Support Plan (MOSP) willfinalize the details of this file size duration and identify any instances when and how the MOTcould request a different file size limit.A sample Archived VC0 telemetry file name is identified with the following namingconventions:<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>_<File Number>.vc0; where

SID => 3 ASCII Characters for the station ID= WS1 for White Sands

SIC => 4 ASCII Digits to identify the spacecraft ID= 0059

Data Source => 4 ASCII characters the source of the data as provided by theMCS

= HDR1 or HDR2


4-90



Schedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,where

YYYY – start year designator (2008 – 2013)DDD – start day of year (0 – 366)HHMMSS – Hours, Minutes and seconds of AOS

File Number => 4 ASCII digit number to indicate the sequence of the file inthe segmented series of files for a particular pass

= (0001 - 9999)

extension => 3 ASCII characters, vcn; wheren = 0, 1, 2, or 3 (to represent the virtual Channel ID)

For example, for an LRO pass that began on DOY 223 at 12:15:07 in the year 2008, where thedata was received from High data-rate receiver #1, and the segment time is set to 3600 seconds(as is expected for LRO), the filename would be:

WS1_0059_HDR1_2008223121507_0001.vc0

If there were multiple files associated with one pass, the files would be named as follows:WS1_0059_HDR1_2008223121507_0001.vc0WS1_0059_HDR1_2008223121507_0002.vc0WS1_0059_HDR1_2008223121507_0003.vc0WS1_0059_HDR1_2008223121507_0004.vc0<Station Name><Scheduled AOS Time>.vc0; whereStation name => Unique 4 character designator for the WS1 station

Scheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact

4.2.1.4.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).4.2.1.5 (WS1-11) Archived VC1 Telemetry Data4.2.1.5.1 Product DescriptionThis interface consists of the downlinked VC1 data that are stored in a file format at a stationupon receipt of the spacecraft housekeeping telemetry. These data are stored with the fill data(VC63) removed. These files are stored at the ground station using their local storagefunctionality. The files are stored for up to seventy-two (72) hours in the event of a possible


4-91



retransmission to the LRO MOC upon request by the LRO operations team; this would normallybe considered within a contingency support concept.4.2.1.5.2 Support DurationThe SCN will provide the Archived VC1 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.5.3 FormatThe Archived VC1 Telemetry Data File is stored with the VC63 (fill data) removed. The stationarchives the VC1 data stream (the downlinked VCDUs) using the station generatedSMEX/LEOT Header. The archive files that WS1 creates are based on a configurable timeduration; this configurable duration is set for the LRO mission at 60 minutes. However, the LROMission Operations Support Plan (MOSP) will finalize the details of this file size duration andidentify any instances when and how the MOT could request a different file size limit.A sample Archived VC1 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B.A sample Archived VC1 telemetry file name is identified with the following namingconventions:<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>_<File Number>.vc1; where




= HDR1 or HDR2Schedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,

whereYYYY – start year designator (2008 – 2013)DDD – start day of year (0 – 366)HHMMSS – Hours, Minutes and seconds of AOS


= (0001 - 9999)extension => 3 ASCII characters, vcn; where

n = 0, 1, 2, or 3 (to represent the virtual Channel ID)


4-92




WS1_0059_HDR2_2008223121507_0001.vc1

If there were multiple files associated with one pass, the files would be named as follows:WS1_0059_HDR2_2008223121507_0001.vc1WS1_0059_HDR2_2008223121507_0002.vc1WS1_0059_HDR2_2008223121507_0003.vc1WS1_0059_HDR2_2008223121507_0004.vc1<Station Name><Scheduled AOS Time>.vc1; where

Station name => Unique 4 character designator for the WS1 stationScheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.1.5.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).4.2.1.6 (WS1-12) Archived VC2 Telemetry Data4.2.1.6.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at a station uponreceipt of the instrument housekeeping telemetry. These data are stored with the fill data (VC63)removed. These files are stored at the ground station using their local storage functionality; thisstorage takes place before the data are routed to the LRO MUE. The files are stored for up toseventy-two (72) hours in the event of a possible retransmission to the LRO MOC upon requestby the LRO operations team; this would normally be considered within a contingency supportconcept.4.2.1.6.2 Support DurationThe SCN will provide the Archived VC2 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.6.3 FormatThe Archived VC2 Telemetry Data File is stored with the VC63 (fill data) removed. The stationarchives the VC2 data stream (the downlinked VCDUs) within the station generated CortexHeader/Trailer message. The archive files that WS1 creates are based on a configurable timeduration; this configurable duration is set for the LRO mission at 60 minutes. However, the LROMission Operations Support Plan (MOSP) will finalize the details of this file size duration andidentify any instances when and how the MOT could request a different file size limit.


4-93



A sample Archived VC2 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B.

A sample Archived VC2 telemetry file name is identified with the following namingconventions:

<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>_<File Number>.vc0; whereSID => 3 ASCII Characters for the station ID

= WS1 for White SandsSIC => 4 ASCII Digits to identify the spacecraft ID

= 0059Data Source => 4 ASCII characters the source of the data as provided by the

MCS= HDR1 or HDR2

Schedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,where

YYYY – start year designator (2008 – 2013)DDD – start day of year (0 – 366)HHMMSS – Hours, Minutes and seconds of AOS


= (0001 - 9999)



WS1_0059_HDR1_2008223121507_0001.vc2

If there were multiple files associated with one pass, the files would be named as follows:WS1_0059_HDR1_2008223121507_0001.vc2WS1_0059_HDR1_2008223121507_0002.vc2WS1_0059_HDR1_2008223121507_0003.vc2WS1_0059_HDR1_2008223121507_0004.vc2<Station Name><Scheduled AOS Time>.vc2; whereStation name => Unique 4 character designator for the WS1 station


4-94



Scheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.1.6.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).

4.2.1.7 (WS1-13) Archived VC3 Telemetry Data4.2.1.7.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at a station uponreceipt of the instrument’s science measurement data. These data are stored with the fill data(VC63) removed. These files are stored at the ground station using their local storagefunctionality; this storage takes place before the data are routed to the LRO MUE. The files arestored for up to seventy-two (72) hours in the event of a possible retransmission to the LROMOC upon request by the LRO operations team; this would normally be considered within acontingency support concept.4.2.1.7.2 Support DurationThe SCN will provide the Archived VC3 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.7.3 FormatThe Archived VC3 Telemetry Data File is stored with the VC63 (fill data) removed. The stationarchives the VC3 data stream (the downlinked VCDUs) within the station generated CortexHeader/Trailer message. The archive files that WS1 creates are based on a configurable timeduration; this configurable duration is set for the LRO mission at 60 minutes. However, the LROMission Operations Support Plan (MOSP) will finalize the details of this file size duration andidentify any instances when and how the MOT could request a different file size limit.A sample Archived VC3 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B.A sample Archived VC3 telemetry file name is identified with the following namingconventions:<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>_<File Number>.vc0; where




4-95




= HDR1 or HDR2Schedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,



= (0001 - 9999)extension => 3 ASCII characters, vcn; where

n = 0, 1, 2, or 3 (to represent the virtual Channel ID)


WS1_0059_HDR2_2008223121507_0001.vc3

If there were multiple files associated with one pass, the files would be named as follows:WS1_0059_HDR2_2008223121507_0001.vc3WS1_0059_HDR2_2008223121507_0002.vc3WS1_0059_HDR2_2008223121507_0003.vc3WS1_0059_HDR2_2008223121507_0004.vc3<Station Name><Scheduled AOS Time>.vc3; where

Station name => Unique 4 character designator for the WS1 stationScheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.1.7.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).4.2.1.8 (WS1-6) Real-time VC0 Telemetry Data4.2.1.8.1 Product DescriptionThis is the real-time data stream that is sent from the stations to the LRO MOC during a real-time station contact; the data stream consists of Virtual Channel Data Units (VCDUs). The


4-96



station inserts these VCDUs into data packets that contain a SMEX/LEO-T Header format. Thereal-time data are Reed-Solomon decoded by the station prior to the transfer to the LRO MOC.The Real-time VC0 data are the Orbiter Housekeeping data downlinked during the White Sands-1 station contact.4.2.1.8.2 Support DurationThe SCN will provide the real-time VC0 data throughout all mission phases, from pre-launch (tosupport mission rehearsals and other project related tests) up through the actual mission andconcluding with end-of-mission support.4.2.1.8.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinkeddata within a virtual channel data unit (VCDU) formatted structure. The station inserts theVCDU into a structure that has a SMEX/LEO-T header.This interface is the real-time VC telemetry stream that contains the downlinked telemetry in theVCDUs; this is a stream of binary data and as such, will not be represented in the Appendix B.4.2.1.8.4 Accuracy and CompletenessThe Real-Time VC0 Data will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).4.2.1.9 (WS1-7) Real-time VC1 Telemetry Data4.2.1.9.1 Product DescriptionThis is the real-time data stream that is sent from the WS1 station to the LRO MOC during areal-time station contact; the data stream consists of Virtual Channel Data Units (VCDUs) thatare downlinked via the VC1 channel. The station removes any fill data (VC63) and inserts theseVCDUs into data packets that contain a SMEX/LEO-T Header format. The real-time data areReed-Solomon decoded by the station prior to the transfer to the LRO MOC. Real-time VC1data are the stored Orbiter housekeeping data that are downlinked during the White Sands-1station contact.4.2.1.9.2 Support DurationThe SCN will provide the real-time VC1 data throughout all mission phases, from pre-launch (tosupport mission rehearsals and other project related tests) up through the actual mission andconcluding with end-of-mission support.4.2.1.9.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinkeddata within a virtual channel data unit (VCDU) formatted structure. The station inserts theVCDU into a structure that has a SMEX/LEO-T header.

This interface is the real-time VC telemetry stream that contains the downlinked telemetry in theVCDUs; this is a stream of binary data and as such, will not be represented in the Appendix B.


4-97



4.2.1.9.4 Accuracy and CompletenessThe Real-Time VC1 Data will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).

4.2.1.10 (WS-1) WS1 Station Status Packets4.2.1.10.1 Product DescriptionThis interface consists of status packets, which contain the general station status information, thedownlink performance related to data quality, data statistics, RF status, and uplink time. Thisinformation is sent in a CCSDS fixed data packets; each station is assigned a unique APID toprovide this station status packet data.4.2.1.10.2 Support DurationThe WS1 station will provide the WS1 Station Status Packets throughout all mission phases,from pre-launch (to support mission rehearsals and other project related tests) up through theactual mission and concluding with end-of-mission support.4.2.1.10.3 FormatThe WS1 Station Status Packets contains the real-time quality and monitoring statistics for theWS1 telemetry and command functions. The data statistics are contained within a standardCCSDS packet and defined as a standard APID so that the LRO T&C system (ITOS) candecommutated the packet and display the monitor information.

These WS1 station status packets are formatted within the standard CCSDS primary packetheader (10 bytes) and secondary packet header (6 bytes). The T&C Formats Handbook willdefine the actual data representation and format for the status packets. These CCSDS primaryand secondary packet headers are defined within the CCSDS Blue Book; they will not be re-referenced here.

The data is are sent via a real time socket connection using the designated Application Identifieras noted in the LRO Telemetry and Command Formats Handbook (431-HDBK-000052).These data quality statistics are reset before the next station contact. The station status packetsare identified by APIDs in the T&C Handbook and will be documented in that document; nosample product is provided.4.2.1.10.4 Accuracy and CompletenessAll data fields are accurate to best available based on station resources.4.2.1.11 (WS1-2) WS1 Weather Data4.2.1.11.1 Product DescriptionThis file contains the weather information per pass, such as the temperature, pressure, andrelative humidity, and wind speed collect every 1 5 minutes during the WS1 station contact.


4-98



4.2.1.11.2 Support DurationThe WS1 station provides the WS1 Weather Data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.11.3 FormatThe WS1 Weather data is are an ASCII formatted, space-delimited, information sent in a fileformat. The data points are captured at 1 5 minute increments for the duration of the stationcontact. It consists of multiple lines in which the first line is the time and station identifierinformation and then there are 1:N repeating lines that provide the following information:Time reference, temperature, Pressure, Relative Humidity, Wind Speed

Station Identifier (consistent with the unique identifier that the station uses to provide other LROdata)

temperature (in Degrees Celsius)(- or +) DDD.dd => 5 digits of temperature (3 significant digits of temperature before the

decimal point and 2 significant digits after the decimal point; 0.0Pressure (in millibars pressure)Relative humidity (percentage to 1 decimal place)Winds (in Km/Hr)

The following table provides a brief description of each field:

Table 4-282526 WS1 Station Weather Data Field Definitions

Field name Field CharacteristicsFirst Line of File

Date/Day of Year/StationIdentifier

Xx 17 ASCII Characters with the following format:DATE: YYYYMMDD DDD: NNNN; where:

YYYYMMDD, defined asYYYY => 4 ASCII digits of year (2008 – 2013)MM => 2 ASCII digits for the month (01 – 12)DD => 2 ASCII digits for the day (01 – 31)

DDD => 3 ASCII digits for day of year (1 – 366)NNNN => 4 ASCII Characters for the Station Identifier (e.g., USPS = USNDongara)

Station Identifier 4 ASCII Characters that uniquely identify the station

Repeating Lines (1:N) of FileTime Reference (UTCFormatted)

=> 4 ASCII characters with the following format:HHMM; where

HH => 2 ASCII digits for hours (01- 23)MM => 2 ASCII digits for minutes (00- 59)


4-99



Field name Field Characteristicstemperature (in DegreesCelsius))

5 ASCII characters;First ASCII Character is the sign indicator of the temperature; where

BLANK = positive temperature- = Negative temperature

Next 2 ASCII Character represent the whole temperature value (0 -99)Next character is the decimal point separator (.)Last 1 Character is the tenths of a degree temperature (0 – 9)

Pressure (in millibars ofMercury)

6 ASCII characters;4 ASCII Character represent the whole value of pressure (0 -1200)Next character is the decimal point separator (.)Last 1 Character is the tenths of the pressure (0 – 9)

Relative humidity 5 ASCII characters, which represent the relative humidity (0.0 – 100.0)3 ASCII Character represent the whole value of relative humidity (0 -100)Next character is the decimal point separator (.)Last 1 Character is the tenths of the pressure (0 – 9))

Wind Speed (Km/Hr) 2 ASCII characters;2 ASCII Character represent the whole value of wind speed (0 - 99)

The file name for the weather product is defined as:

<Station ID><Station AOS Contact Time>.weaA sample SCN Weather Data file is provided as a reference in Appendix B, Figure B.2-5FigureB.2-4Figure B.2-5.4.2.1.11.4 Accuracy and CompletenessThe WS1 Weather data accuracy is predicated on the Capricorn installed Weather station SWand HW components. Temperature should be accurate to tenths of a degree Celsius, Pressureshould be accurate to tenths of a millibar of pressure; relative humidity should be accurate to thenearest whole percentage point; the wind speed should be accurate to the nearest whole value inKilometers per hour.

4.2.1.12 (WS1-3) Ka-Band VC3 Telemetry4.2.1.12.1 Product DescriptionThis interface is the real-time data stream consisting of the VC3 telemetry packets, which theWS1 high-rate data recorder (HDR) transfers to the LRO mission unique equipment (MUE)known as the White Sands1 – Data Processing System. This product consists of data packets;the HDR transfers the data packets via a socket connection.4.2.1.12.2 Support DurationThe SCN will provide the Ka-Band VC3 Telemetry throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.12.3 Format


4-100



The Ka-Band VC3 Telemetry Data are a composite of VCDUs received at the station andtransmitted to the WS1-DPS element. The VCDUs are composed of specific APIDs for eachscience instrument. The VCDU formats the underlying APIDs are defined in the T&CHandbook; these products are binary data packets and are not shown as a sample product inAppendix B.4.2.1.12.4 Accuracy and CompletenessThe VC3 Telemetry Data are accurate and complete to a best effort based on the downlinkquality and based upon the information provided by the T&C Formats handbook.4.2.1.13 (WS1-4) Ka-Band VC2 Telemetry4.2.1.13.1 Product DescriptionThis interface is the real-time data stream consisting of the VC2 telemetry packets, which theWS1 HDR transfers to the LRO WS1-DPS. This product consists of data packets; the HDRtransfers the data packets via a socket connection.4.2.1.13.2 Support DurationThe SCN will provide the Ka-Band VC2 Telemetry throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.1.13.3 FormatThe Ka-Band VC2 Telemetry Data are a composite of VCDUs received at the station andtransmitted to the WS1-DPS element. The VCDUs are composed of specific APIDs for eachscience instrument. The VCDU formats the underlying APIDs are defined in the T&CHandbook; these products are binary data packets and are not shown as a sample product inAppendix B.4.2.1.13.4 Accuracy and CompletenessThe VC2 Telemetry Data are accurate and complete to a best effort based on the downlinkquality and based upon the information provided by the T&C Formats handbook.4.2.1.14 (WS1-8) Ka-Band RF Receiver Data4.2.1.14.1 Product DescriptionThe Ka-Band RF Receiver Data is are a file that containsthe RF Strength data from Ka-Bandreceiver that will be used for HGA calibration.4.2.1.14.2 Support DurationThe WS1 station generates this file for all mission phases.4.2.1.14.3 FormatThe Ka-Band RF Receiver Data File is an ASCII formatted file in which the fields are separatedby blanks. The file contains the following data:Time-Tag RF Signal Strength; the fields are defined in the following table:


4-101



Table 4-292627 WS1 Ka-Band Receiver Data Field Definitions

Field name Field CharacteristicsTime-Tag 18 ASCII Characters with the following format:

YYYYDDD HHMMSS.mmm; where:YYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for the day of year (01 – 366)HH => 2 ASCII digits for the day (00 – 23)MM => 2 ASCII digits for the minutes (00 – 59)SS.mmm => 6 ASCII digits for the seconds and milliseconds where the

two are separated by the decimal character (.)

KA-Band Receiver Strength TBR

A sample Ka-Band RF Receiver Data file is provided as a reference in Appendix B, Figure B.2-6Figure B.2-5Figure B.2-6. The sample file naming format is identified as Follows:

<Station Name>_<Station AOS>_<KaRF>.txt, where:Station name => Unique 4 character designator for the WS1 station

Scheduled AOS Time => YYYYDOY.HHMM; whereYYYY is the 4 character year representation (2008 – 2013)DOY is the 3 character representation for day of year (1 – 366)HHMM is the scheduled AOS time for that specific station contact

4.2.1.14.4 Accuracy and CompletenessTBR4.2.1.15 (WS1-9) SDPS CFDP Status Packets4.2.1.15.1 Product DescriptionThis message contains information related to the connection of CFDP processor located at WS1ground station to the LRO MOC. Technically, this is not a Space Communications Networkgenerated data file. The data are created from the mission unique equipment, which the LROproject provided to the WS1 facility.4.2.1.15.2 Support DurationThe SCN will provide the CFDP Status Messages throughout all mission phases, from pre- -launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support. The CFDP Status Messages are deliveredto the LRO MOC on a routine basis or to support mission rehearsals and other project relatedtests up through the actual mission and concluding with end-of-mission support.4.2.1.15.3 FormatThe SDPS CFDP Status Packets contain the current status of the MUE located at the WS1facility.


4-102



The SDPS CFDP Status Packets are a standard CCSDS Packet; the data are defined by thestandard CCSDS packet concept with a primary and secondary CCSDS packet headers; thespecific packet structure is defined and documented in the LRO T&C Formats handbook. Sincethey are identified by a specific APID; as such, no sample product is provided.4.2.1.15.4 Accuracy and CompletenessTBR4.2.1.16 (WS1-14) VC2 Housekeeping Telemetry Files4.2.1.16.1 Product DescriptionThis interface consists of the data downlinked using the VC2 channel that are stored in a fileformat at a station upon receipt of the instrument housekeeping telemetry. These data are storedwith the fill data (VC63) removed. These files are the transmitted VC2 products between theLRO MUE, located at the WS1 station, and the LRO MOC4.2.1.16.2 Support DurationThe WS1 station will provide the VC2 Housekeeping Telemetry Files throughout all missionphases, from pre-launch (to support mission rehearsals and other project related tests) up throughthe actual mission and concluding with end-of-mission support.4.2.1.16.3 FormatThe VC2 Housekeeping Telemetry Files is formatted to contain a series of Virtual Channel DataUnits (VCDUs) for that specific VC. The VCDU format is defined in the LRO Telemetry andCommand Formats Handbook (LRO-HDBK-000052).

The file naming conventions for the VC3 data files are identified within the corresponding FSWInstrument Data ICD.

This file contains the selected APIDs downlinked via the VC2 channel. This file contains thedata in a binary format; as such, no sample product is provided as a reference in Appendix B.4.2.1.16.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).

4.2.1.17 (WS1-15) VC2 FSW Telemetry FilesPost-Pass Summary Report4.2.1.17.1 Product DescriptionThis interface consists of the downlinked FSW data that are commanded down by the operationsteam in the VC2 channel. These data are stored in a file format at a station upon receipt of theFlight Software Memory/Table downlinked telemetry. These data are stored with the fill data(VC63) removed. These files are the transmitted VC2 products between the LRO MUE, locatedat the WS1 station, and the LRO MOCThe Station provides this interface as a summary report ofthe activities that occurred during the recently completed White Sands station contact duringwhich the spacecraft downlinked spacecraft and instrument data files.4.2.1.17.2 Support Duration

pgf

Cross-Out

pgf

Replacement Text

VC2


4-103



The SCN will provide the VC2 FSW Telemetry Files throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.The Station DPS (WS1-DPS) elementprovides this specific interface product through-out all mission phases.4.2.1.17.3 FormatThe Post-Pass Summary Report is an ASCII formatted file in which the fields are separated byblanks. The file contains the following data types of dataStation Contact AOS and LOSTotal Number of Files Downlinked

For each set of files (sc Housekeeping, Instrument HK, and Instrument Raw Measurement):Name of FileFile Quality StatisticsNumber of recoverable errorsNumber of Unrecoverable errors

The fields are defined in the following table:

Table 4-3027 Post-Pass Summary Field Definitions

Field name Field CharacteristicsAOS Time-Tag 14 ASCII Characters with the following format:

YYYYDDD HHMMSS; where:YYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for the day of year (01 – 366)HH => 2 ASCII digits for the day (00 – 23)MM => 2 ASCII digits for the minutes (00 – 59)SS => 2 ASCII digits for the seconds

LOS Time-Tag 14 ASCII Characters with the following format:YYYYDDD HHMMSS; where:

YYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for the day of year (01 – 366)HH => 2 ASCII digits for the day (00 – 23)MM => 2 ASCII digits for the minutes (00 – 59)SS => 2 ASCII digits for the seconds

Total Number of File 4 ASCII Digits (0000 – 9999)

File name Up to 40 ASCII Characters that represent the on-board file name

File Quality Statistics Up to 10 Hexadecimal digits that provide the File Quality Statistics (such as aCRD code or file checksum)

recoverable error value Up to 4 ASCII digits that indicate the number of recoverable file errors

Unrecoverable error value Up to 4 ASCII digits that indicate the number of unrecoverable file errors


4-104



A sample Post-Pass Summary Report file is provided as a reference in Appendix B, Figure B.2-7Figure B.2-6. The sample file naming format is identified as follows:

<Station Name>_<Station AOS>_<PassSum>.txt, where:Station/Element Name => 4 Character

= SDPS to indicate that the Station DPS element generatedthis file

Scheduled AOS Time => YYYYDOY.HHMM; whereYYYY is the 4 character year representation (2008 – 2013)DOY is the 3 character representation for day of year (1 – 366)HHMM is the scheduled AOS time for that specific stationcontact

File Type => 7 characters followed by an underscore;PassSum to indicate that this file represents a WS1-DPS Pass

Summary File

extension => 3 ASCII characterstxt; used to represent this is a textual file

A sample file name for the Support Schedule is defined as follows:SDPS_2009015.0345_PassSum.txt

The VC2 FSW Telemetry Files is formatted to contain a series of Virtual Channel Data Units(VCDUs). The VCDU format is defined in the LRO Telemetry and Command FormatsHandbook (LRO-HDBK-000052).This file contains the selected APIDs downlinked via the VC2 channel. This file contains thedata in a binary format; as such, no sample product is provided as a reference in Appendix B.The VCDU format is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052).4.2.1.17.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).The Post Pass Summary Report is accurate andcomplete based upon the data files that the Orbiter downlinked during the last WS1 stationcontact.4.2.1.18 (WS1-16) VC3 Measurement Telemetry Files4.2.1.18.1 Product DescriptionThis VC3 Measurement Telemetry Files consists of the science measurement data filesdownlinked to the WS1 station during the current station contact using the VC3 channel. Thesedata are stored with the fill data (VC63) removed. These files are the transmitted VC3 productsbetween the LRO MUE, located at the WS1 station, and the LRO MOC4.2.1.18.2 Support Duration


4-105



The SCN will provide the VC3 Measurement Telemetry Files throughout all mission phases,from pre-launch (to support mission rehearsals and other project related tests) up through theactual mission and concluding with end-of-mission support.4.2.1.18.3 FormatOne VC3 Measurement Telemetry Files is created for each instrument and is formatted tocontain a series of Virtual Channel Data Units (VCDUs) for that specific instrument; the formatfor each of the instrument measurement data files is define within the corresponding FSW DataICD. The VCDU format is defined in the LRO Telemetry and Command Formats Handbook(LRO-HDBK-000052).

The file naming conventions for the VC3 data files are identified within the corresponding FSWInstrument Data ICD.

This file contains the data in a binary format; as such, no sample product is provided as areference in Appendix B.4.2.1.18.4 Accuracy and CompletenessThe VC3 Measurement Telemetry Files will be complete and accurate as listed in the LRODetailed Mission Requirements document (LRO-REQ-00048).

4.2.1.19 (WS1-17) SPDP Event Logs4.2.1.19.1 Product DescriptionThe Event Logs contain the status informational data of the MUE, which is located at WhiteSands (WS1). The MUE is a MOC-supplied processor that is responsible for the CFDPprocessing between the spacecraft in order to receive the downlinked data files.4.2.1.19.2 Support DurationThe SCN SDPS will provide the Event Logs throughout all mission phases, from pre-launch (tosupport mission rehearsals and other project related tests) up through the actual mission andconcluding with end-of-mission support.4.2.1.19.3 FormatThe Event Logs are an ASCII formatted file that provides the log of the MUE located at WS1

A sample Stored Data SDPS Event Log File is provided as a reference in AppendixB.2.3Appendix B, Figure B.2-8Figure B.2-7.4.2.1.19.4 Accuracy and CompletenessThe Event Logs contain all of the system status information since the time of the lasttransmission to the LRO MOC.

4.2.1.20 (WS1-18) SDPS System Logs4.2.1.20.1 Product DescriptionThe System Logs contain the status informational data of the MUE, which is located at WhiteSands (WS1). The MUE is a MOC-supplied processor that is responsible for the CFDP


4-106



processing between the spacecraft in order to receive the downlinked data files. Thisinformation is used by the LRO MOC to identify anomalous conditions within the MUE.4.2.1.20.2 Support DurationThe MUE, located at the WS1 facility, will provide the System Logs throughout all missionphases, from pre-launch (to support mission rehearsals and other project related tests) up throughthe actual mission and concluding with end-of-mission support.4.2.1.20.3 FormatThe System Logs are an ASCII formatted file that provides the hardware log of the MUE locatedat WS1A sample System Logs File is provided as a reference in Appendix B, Figure B.2-9Figure B.2-8.Appendix B.2.34.2.1.20.4 Accuracy and CompletenessThe data within the System Event Logs is accurate based on best available data captured withinth4e system logs.4.2.1.21 (WS1-19) SDPS CFDP PDU4.2.1.21.1 Product DescriptionThe SDPS CFDP PDU contains the current set of PDU data returned from the WS1-DPSelement and provides the indication of Acknowledgements, Negative Acknowledgements, andEnd-of-File receipt notifications.4.2.1.21.2 Support DurationThe WS1-DPS, located at the WS1 facility, will provide the data throughout all mission phases.4.2.1.21.3 FormatThe SDPS CFDP PDU contains data that is defined and documented in the LRO T&C Formatshandbook since they are identified by a specific APID; as such, no sample product is provided4.2.1.21.4 Accuracy and CompletenessThe SDPS CFDP PDU are identified by APIDs in the T&C Handbook and will be documentedin that document; no sample product is provided.

All data fields are accurate to best available based on station resources4.2.2 Universal Space Network Product Descriptions4.2.2.1 (USN-3) USN Raw Tracking Data4.2.2.1.1 Product DescriptionThe USN Raw Tracking Data File is sent to both the LRO MOC and the LRO FD Facility. Thisinterface product provides the LRO Flight Dynamics Facility with the data required to supporttracking of the orbiter and generation of orbit and mission products. This These data is are alsotransferred to the LRO MOC for eventual distribution to the LOLA SOC.


4-107



Each USN station, that has the capability to provide tracking data, will create the data in a formatidentified as the Universal Tracking Data Format (UTDF) as defined in the STDN Tracking andAcquisition Handbook (STDN-724, 1990).4.2.2.1.2 Support DurationThe USN station supporting the LRO mission will provide the USN Raw Tracking Data Filethroughout all mission phases, from pre-launch (to support mission rehearsals and other projectrelated tests) up through the actual mission and concluding with end-of-mission support.4.2.2.1.3 FormatThis data will be consistent with STDN-724. The data file contains the tracking data in a binaryform; one datum contains seventy-five (75) bytes of information as identified in the Trackingand Acquisition Handbook. The data records are created at a 60 second interval. The followingtable provides the fields and field definitions for the station tracking data. This format isconsistent with the format as identified in Section 4.2.1.3 for the WS1 tracking data format;specifically, referenced as Table 4-27Table 4-24Table 4-25.

A sample of the station tracking data file is provided as a reference in Appendix B, Figure B.2-3Figure B.2-34.2.2.1.4 Accuracy and CompletenessTBR4.2.2.2 (USN-1) USN Station Status Packets4.2.2.2.1 Product DescriptionThis interface consists of status packets, which contain the general station information, thedownlink performance related to data quality, data statistics, RF status, and uplink time. Thisinformation is sent in a CCSDS fixed data packets; each station is assigned a unique APID toprovide this station status packet data.4.2.2.2.2 Support DurationThe USN will provide the USN Station Status Packets throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.2.2.3 FormatThe USN Station Status Packets contains the real-time quality and monitoring statistics for thetelemetry and command functions for the corresponding USN station. The data statistics arecontained within a standard CCSDS packet and defined as a standard APID so that the LROT&C system (ITOS) can decommutated the packet and display the monitor information.These WS1 station status packets are formatted within the standard CCSDS primary packetheader (10 bytes) and secondary packet header (6 bytes). The T&C Formats Handbook willdefine the actual data representation and format for the status packets. These CCSDS primaryand secondary packet headers are defined within the CCSDS Blue Book; they will not be re-referenced here.


4-108



For each LRO station contact, the station will provide the data quality statistics every TBR (1)seconds.

The data is are sent via a real time socket connection using the designated Application Identifieras noted in the LRO Telemetry and Command Formats Handbook (431-HDBK-000052).

These data quality statistics are reset before the next station contact. The station status packetsare identified by APIDs in the T&C Handbook and will be documented in that document; nosample product is provided.4.2.2.2.4 Accuracy and CompletenessAll data fields are accurate to best available based on station resources.

4.2.2.3 (USN-2) USN Weather Data4.2.2.3.1 Product DescriptionThis file contains the weather information per pass, such as the temperature, pressure, andrelative humidity every 5 minutes during station contacts. This product is consistent with theproduct created by the WS1 station; refer to Section 4.2.1.11.4.2.2.3.2 Support DurationThe USN Stations will provide the USN Weather Data file throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.2.3.3 FormatThe USN Weather Data File is an ASCII formatted, space-delimited, file. The data points arecaptured at 5 minute increments for the duration of the station contact. It consists of multiplelines in which the first line is contains start date (YYYYMMDD), Day of Year (DDD), and thestation identifier and then there are 1:N repeating lines that provide the following information:Time reference, temperature, Pressure, Relative Humidity, and wind speed

Station Identifier (consistent with the unique identifier that the station uses to provide other LROdata)

NNNN = USPS for USN DongaraUSHS for USN HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, Germany

temperature (in Degrees Celsius)(- or +) DDD.dd => 5 digits of temperature (3 significant digits of temperature before

the decimal point and 2 significant digits after the decimal point; 0.0Pressure (in millibars pressure)Relative humidity (percentage to 1 decimal place)Winds (in Km/Hr)The following table provides a brief description of each field:


4-109



Table 4-312828 USN Station Weather Data Field Definitions

Field name Field CharacteristicsFirst Line of File

Date/Day of Year/StationIdentifier

Xx 17 ASCII Characters with the following format:DATE: YYYYMMDD DDD: NNNN; where:

YYYYMMDD, defined asYYYY => 4 ASCII digits of year (2008 – 2013)MM => 2 ASCII digits for the month (01 – 12)DD => 2 ASCII digits for the day (01 – 31)

DDD => 3 ASCII digits for day of year (1 – 366)NNNN => 4 ASCII Characters for the Station Identifier (e.g., USPS = USNDongara)

Station Identifier 4 ASCII Characters that uniquely identify the station

Repeating Lines (1:N) of FileTime Reference (UTCFormatted)

=> 4 ASCII characters with the following format:HHMM; where

HH => 2 ASCII digits for hours (01- 23)MM => 2 ASCII digits for minutes (00- 59)

temperature (in DegreesCelsius))

5 ASCII characters;First ASCII Character is the sign indicator of the temperature; where

BLANK = positive temperature- = Negative temperature

Next 2 ASCII Character represent the whole temperature value (0 -99)Next character is the decimal point separator (.)Last 1 Character is the tenths of a degree temperature (0 – 9)

Pressure (in millibars ofMercury)

6 ASCII characters;4 ASCII Character represent the whole value of pressure (0 -1200)Next character is the decimal point separator (.)Last 1 Character is the tenths of the pressure (0 – 9)

Relative humidity 5 ASCII characters, which represent the relative humidity (0.0 – 100.0)3 ASCII Character represent the whole value of relative humidity (0 -100)Next character is the decimal point separator (.)Last 1 Character is the tenths of the pressure (0 – 9)

Wind Speed (Km/Hr) 2 ASCII characters;2 ASCII Character represent the whole value of wind speed (0 - 99)

The file name for the weather product is defined as:

<Station ID><Station AOS Contact Time>.weaA sample USN Weather Data file is provided as a reference in Appendix B, Figure B.2-5FigureB.2-4Figure B.2-54.2.2.3.4 Accuracy and Completeness


4-110



The WS1 Weather data accuracy is predicated on the weather station SW and HW components.Temperature should be accurate to tenths of a degree Celsius, Pressure should be accurate totenths of a millibar of pressure; relative humidity should be accurate to the tenths of a percentagepoint; the wind speed should be accurate to the nearest whole value in Kilometers per hour.

4.2.2.4 (USN-4) Real-time VC0 Telemetry Data4.2.2.4.1 Product DescriptionThis is a near real-time data stream that is sent from the stations to the LRO MOC during a real-time station contact; the data stream consists of Virtual Channel Data Units (VCDUs). Thestation inserts these VCDUs into data packets that contain a SMEX/LEO-T Header format. Thedata are delivered electronically to the MOC via a real-time socket connection using theRestricted IONet.

The real-time data are Reed-Solomon decoded by the station prior to the transfer to LRO MOC.The R-S bits are stripped off prior to transmission; however, the R-S error flag in theSMEX/LEOT header is set appropriately. The station will transfer all frames regardless of anyR-S error.4.2.2.4.2 Support DurationThe USN stations will provide the real-time VC0 data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.2.4.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinkeddata within a virtual channel data unit (VCDU) formatted structure. The station inserts theVCDU into a structure that has a SMEX/LEO-T header.This data product consists of the selected VC0 downlinked data packets; the LRO T&C FormatsHandbook documents the VC0 contents and format. The data are binary and as such, no sampleproduct is provided in Appendix B.4.2.2.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.2.2.5 (USN-5) Real-time VC1 Telemetry Data4.2.2.5.1 Product DescriptionThis is the VC1 data stream that is sent from the USN stations to the LRO MOC during a real-time station contact; the data stream consists of Virtual Channel Data Units (VCDUs). Thestation inserts these VCDUs into data packets that contain a SMEX/LEO-T Header format. Thedata are delivered electronically to the MOC via a real-time socket connection using theRestricted IONet.The real-time data are Reed-Solomon decoded by the station prior to the transfer to the LROMOC. The R-S bits are stripped off prior to transmission; however, the R-S error flag in the


4-111



SMEX/LEOT header is set appropriately. The station will transfer all frames regardless of anyR-S error.4.2.2.5.2 Support DurationThe USN stations will provide the real-time VC1 data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.2.5.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinkeddata within a virtual channel data unit (VCDU) formatted structure. The station inserts theVCDU into a structure that has a SMEX/LEO-T header.This data product consists of the selected VC1 downlinked data packets; the LRO T&C FormatsHandbook documents the VC1 contents and format. The data are binary and as such, no sampleproduct is provided in Appendix B.4.2.2.5.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.2.2.6 (USN-6) Archived VC0 Telemetry Data4.2.2.6.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at a station uponreceipt of the real-time spacecraft housekeeping telemetry. These data are stored with the filldata (VC63) removed. These files are stored at the ground station using their local storagefunctionality. The files are stored for up to seventy-two (72) hours in the event of a possibleretransmission to the LRO MOC upon request by the LRO operations team; this would normallybe considered within a contingency support concept.4.2.2.6.2 Support DurationThe USN stations will provide the Archived VC0 Telemetry Data throughout all mission phases,from pre-launch (to support mission rehearsals and other project related tests) up through theactual mission and concluding with end-of-mission support.4.2.2.6.3 FormatThe Archived VC0 Telemetry Data File is stored with VC63 (fill data) removed. The ArchivedVC0 data file format contains SMEX/LEOT headers followed by the VC0 VCDU as is definedin the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052). The R-S bitsare stripped off prior to archiving the file; however, the R-S error flag in the SMEX/LEOTheader is set appropriately. The station will archive all frames regardless of any R-S error.




4-112



<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>.vc0; whereSID => 4 ASCII Characters for the station ID

USPS for USN Dongara, AustraliaUSHS for USN South Point, HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, Germany



= TBSSchedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,



An example of an LRO VC0 archived filename from a Dongara station contact would be:

USPS_0059_XXXX_2008223121507.vc0<Station Name><Scheduled AOS Time>.vc0; whereStation name => Unique 4 character designator for the USN stationScheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.2.6.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).

4.2.2.7 (USN-7) Archived VC1 Telemetry Data4.2.2.7.1 Product DescriptionThis interface consists of the downlinked VC1 data that are stored in a file format at a stationupon receipt of the spacecraft housekeeping telemetry. These data are stored with the fill data(VC63) removed. These files are stored at the ground station using their local storagefunctionality. The files are stored for up to seventy-two (72) hours in the event of a possibleretransmission to the LRO MOC upon request by the LRO operations team; this would normallybe considered within a contingency support concept.


4-113



4.2.2.7.2 Support DurationThe SCN will provide the Archived VC1 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.2.7.3 FormatThe Archived VC1 Telemetry Data File is stored with VC63 (fill data) removed. The ArchivedVC1 data file format contains SMEX/LEOT headers followed by the VC0 VCDU as is definedin the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052). The R-S bitsare stripped off prior to archiving the file; however, the R-S error flag in the SMEX/LEOTheader is set appropriately. The station will archive all frames regardless of any R-S error.



<SID>_<SIC>_<Data Source>_<Scheduled AOS Time>.vc1; whereSID => 4 ASCII Characters for the station ID

USPS for USN Dongara, AustraliaUSHS for USN South Point, HawaiiKU1S (or KU2S) for Kiruna, SwedenWU1S (or WU2S) for Wilheim, Germany



= TBSSchedule AOS time => 13 ASCII characters in the form of YYYYDOYHHMMSS,



An example of an LRO VC1 archived filename from the South Point station would be:

USHS_0059_XXXX_2008223121507.vc1<Station Name><Scheduled AOS Time>.vc1; where


4-114



Station name => Unique 4 character designator for the USN stationScheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.2.7.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-REQ-00048).4.2.3 Deep Space Network Product DescriptionsThe following sections provide the details on the interface products generated specifically by theDSN stations in support of the LRO mission. ASs noted earlier, DSN is used for early missionlaunch critical supports activities and for any mission maneuver; DSN provides regularlyscheduled proficiency supports.. Outside of these supports, DSN is used solely to provide anemergency, or contingency, supports in the event that the commercial S-band stations are down..DSN is also used on a regularly scheduled basis for proficiency supports.

The telemetry SLE interface between the DSN and the LRO MOC supports the return of all real-time VC0 and VC1 telemetry frames using the “Return All Frames (RAF)” SLE Service BindInstance. The MOC can issue a “Return Channel Frames (RCF)” to request a selective return ofeither VC0 or VC1; the MOC would issue 2 RCFs Service Binds to request DSN to return VC0and VC1 as two separate connections.The following paragraphs identify SLE header fields and definitions for the telemetry andcommands interfaces with the LRO MOC. provides a representation of the SLE telemetryheader; provides the field definitions used for the SLE telemetry header fields.

Figure 4-2 is TBS

Figure 4-32 SLE Telemetry Header StructureThe fields, represented within this figure are defined with the following table:Table 4-33 is TBS

Table 4-3229 SLE Telemetry Header Structure Definitions

4.2.3.1 (DSN-1) DSN Tracking Data4.2.3.1.1 Product DescriptionThe DSN Tracking Data File provides the LRO Flight Dynamics Facility with the data requiredto support tracking of the orbiter and generation of orbit and mission products. This These datais are also transferred to the LRO MOC for eventual distribution to the LOLA SOC.


4-115



DSN, which supports LRO through the 34 meter subnet, will provide this data such that it isconsistent with the TRK-2-34 format.4.2.3.1.2 Support DurationThe DSN will provide this tracking data file throughout all mission phases, from pre-launch (tosupport mission rehearsals and other project related tests) up through the actual mission andconcluding with end-of-mission support.4.2.3.1.3 FormatThis data will be consistent with DSN formatted tracking data as identified via the TRK-2-34format. A sample of the DSN Tracking Data file is provided as a reference in Appendix B,Figure B.2-10Figure B.2-9Figure B.2-94.2.3.1.4 Accuracy and CompletenessTBR4.2.3.2 (DSN-2) Real-time VC0 Telemetry Data4.2.3.2.1 Product DescriptionThe VC0 data consists of the orbiter housekeeping telemetry data packets that the spacecraftdownloads to the DSN station in real-time. This interface consists of the downlinked packet datathat are transferred with the fill data (VC63) removed. DSN returns the VC0 data selectivelywhen the MOC issues an RCF SLE Bind.4.2.3.2.2 Support DurationThe DSN will provide the Real-time VC0 Telemetry Data throughout all mission phases, frompre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.3.2.3 FormatThe Real-time VC0 Telemetry Data is are formatted to contain a series of Virtual Channel DataUnits (VCDUs) for VC0. The VCDU format is defined in the LRO Telemetry and CommandFormats Handbook (LRO-HDBK-000052).

Since this is a stream of real-time packets, which are sent in a binary format consistent with theLRO Telemetry and Command Formats Handbook (LRO-HDBK-000052), and via the CCSDSSLE interface. There are no sample products listed in Appendix B; the user may reference DSN820-013 0163-Telecomm interface document for additional details.4.2.3.2.4 Accuracy and CompletenessThe Real-time VC0 Telemetry Data will be complete and accurate as documented in the LROTelemetry and Command Formats Handbook (LRO-HDBK-000052).

4.2.3.3 (DSN-5) Archived VC0 Telemetry Data4.2.3.3.1 Product Description


4-116



Nominally, DSN delivers received VC0 data to the LRO MOC in near real-time. The DSNstation also stores the downlinked data for up to 72 hours in the event that the LRO MOTrequests a retransmission of the data.This interface consists of the downlinked data that are stored in a file format at the DSN uponreceipt of the real-time spacecraft housekeeping telemetry. These data are stored with the filldata (VC63) removed. These files are stored at the DSN using their local storage functionality.The files are stored for up to seventy-two (72) hours in the event of a possible retransmission tothe LRO MOC upon request by the LRO operations team; this would normally be consideredwithin a contingency support concept. The MOC would issue a RCF Service Bind option andwould request VC0 data for a specified time interval.4.2.3.3.2 Support DurationThe DSN stations will provide the Archived VC0 Telemetry Data throughout all mission phases,from pre-launch (to support mission rehearsals and other project related tests) up through theactual mission and concluding with end-of-mission support.4.2.3.3.3 FormatThe Archived VC0 Telemetry Data File is stored at JPL’s storage facility as it is received fromthe spacecraft station with VC63 (fill data) removed. The format of this downlinked datacontains VCDU formatted APIDs and is defined in the LRO Telemetry and Command FormatsHandbook (LRO-HDBK-000052).A sample Archived VC0 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B; the user may reference DSN 820-013 0163-Telecomm interface document for additional details.

DSN returns the Archived VC0 telemetry data via a socket connection to the LRO MOC andDSN transfers the data via a socket connection to the LRO MOC as an off-line data transfer; thistransfer is similar in nature to the real-time data delivery, except that it occurs post-pass and theLRO MOC’s initiating telemetry and command system might not be the prime telemetry andcommand element. DSN routes the archived VC0 Telemetry data back to the LRO MOC via theCCSDS SLE interface.

The archived VC0 Telemetry data would be routed back to the LRO MOC via the CCSDS SLEinterface.4.2.3.3.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-RQMT-00048).

4.2.3.4 (DSN-6) Archived VC1 Telemetry Data4.2.3.4.1 Product DescriptionNominally, DSN delivers received VC1 data to the LRO MOC in near real-time. The DSN alsostores the downlinked data for up to 72 hours in the event that the LRO MOT requests aretransmission of the data.


4-117



This interface consists of the downlinked VC1 data that are stored in a file format at the DSNupon receipt of the spacecraft housekeeping telemetry. These data are stored with the fill data(VC63) removed. These files are stored at the DSN. The files are stored for up to seventy-two(72) hours in the event of a possible retransmission to the LRO MOC upon request by the LROoperations team; this would normally be considered within a contingency support concept. TheMOC would issue a RCF Service Bind option and would request VC1 data for a specified timeinterval.4.2.3.4.2 Support DurationThe SCN DSN stations will provide the Archived VC1 Telemetry Data throughout all missionphases, from pre-launch (to support mission rehearsals and other project related tests) up throughthe actual mission and concluding with end-of-mission support.4.2.3.4.3 FormatThe Archived VC1 Telemetry Data File is stored at JPL’s storage facility as it is received fromthe spacecraft station with VC63 (fill data) removed. The format of this downlinked datacontains VCDU formatted APIDs and is defined in the LRO Telemetry and Command FormatsHandbook (LRO-HDBK-000052).

A sample Archived VC1 Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B; the user may reference DSN 820-013 0163-Telecomm interface document for additional details..DSN returns the Archived VC1 telemetry data via a socket connection to the LRO MOC andDSN transfers the data via a socket connection to the LRO MOC as an off-line data transfer; thistransfer is similar in nature to the real-time data delivery, except that it occurs post-pass and theLRO MOC’s initiating telemetry and command system might not be the prime telemetry andcommand element. DSN routes the archived VC1 Telemetry data back to the LRO MOC via theCCSDS SLE interface.A sample Archived VC1 telemetry file name is identified with the following namingconventions:<Station Name><Scheduled AOS Time>.vc1; where

Station name => Unique 4 character designator for the DSN stationScheduled AOS Time => YYYYDOY.HHMM; where YYYY is the 4 character year representation (2008 – 2013) DOY is the 3 character representation for day of year (1 – 366) HHMM is the scheduled AOS time for that specific station contact4.2.3.4.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-RQMT-00048).4.2.3.5 (DSN-3) Real-Time VC1 Telemetry Data4.2.3.5.1 Product Description


4-118



This is a real-time data stream that is sent from the LRO spacecraft in the VC1 data stream to theLRO MOC during a real-time station contact; the data stream consists of Virtual Channel DataUnits (VCDUs). The DSN inserts these VCDUs into data packets that contain a SLE Headerformat. The real-time data are Reed-Solomon decoded by the station prior to the transfer to theLRO MOC.4.2.3.5.2 Support DurationThe DSN will provide the real-time VC1 data throughout all mission phases, from pre-launch (tosupport mission rehearsals and other project related tests) up through the actual mission andconcluding with end-of-mission support.4.2.3.5.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The DSN insert the downlinked datawithin a virtual channel data unit (VCDU) formatted structure. The DSN inserts the VCDU intoa structure that has a SLE header. This interface consists of the downlinked packet data that aretransferred with the fill data (VC63) removed. Since this is a stream of real-time packets, whichare sent in a binary format consistent with the LRO Telemetry and Command Formats Handbook(LRO-HDBK-000052) and via the CCSDS SLE interface. There are no sample products listedin Appendix B; the user may reference DSN 820-013 0163-Telecomm interface document foradditional details.4.2.3.5.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-RQMT-00048).4.2.3.6 (DSN-4) DSN Station Monitor Packets4.2.3.6.1 Product DescriptionThis interface consists of the DSN status packets, which contain the general station information,the downlink performance related to data quality, data statistics, RF status, and uplink time.4.2.3.6.2 Support DurationThe DSN will provide the DSN Station Status Packets throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actualmission and concluding with end-of-mission support.4.2.3.6.3 FormatThe DSN Station Status Packets contain the data as specified by the DSN MON-0158 format.For each DSN station contact, the station provides the data quality statistics, as listed in DSN-MON-0158) every 5 seconds. The station status packets are encased within Standard FormattedData Units (SFDU) Block.These data quality statistics are reset before the next station contact. Since the data sent as abinary form, no sample product is reference in Appendix B.4.2.3.6.4 Accuracy and Completeness


4-119



The DSN MON-0158 document provides the TBRaccuracy and precision concepts for each datatype within the Monitor Block.

4.2.4Laser Ranging Product Description4.2.4.1Weekly Laser Ranging Schedule4.2.4.1.1Product DescriptionThis data contains information related to which sites are specifically scheduled to perform laserranging with the LRO spacecraft for the upcoming week and identifies the point of contactinformation of personnel in charge at the laser ranging site (name, phone contact information,email information) in case that the LRO operations team needs to request that laser ranging notbe performed because of a spacecraft problem.4.2.4.1.2Support DurationThis information is supplied for all mission phases. The LR site delivers this data file to theLRO MOC.4.2.4.1.3FormatThe Weekly Laser Ranging Schedule contains the following fields:

Station IdentifierScheduled start time for laser rangingScheduled stop time for laser rangingPoint of Contact (Name)POC Phone informationA sample Weekly Laser Ranging Schedule file is provided as a reference in Figure B.2-8.4.2.4.1.4Accuracy and CompletenessTBR4.2.54.2.4 Space Network (SN) Product DescriptionThe following sections provide the details on the interface products generated by the SpaceNetwork Tracking and Data Relay Satellites (TDRS) system in support of the LRO mission. TheSN support is limited for the several hours immediately after launch.4.2.5.14.2.4.1 (SN-1) Real-time VC0 Orbiter TelemetryThe Space Network provides a real-time telemetry data interface with the Orbiter during thelaunch ascent phase and for several hours after launch. This interface supports the transfer of theLRO telemetry, at low rates; the data stream consists of Virtual Channel Data Units (VCDUs).The SN inserts these VCDUs into data packets that contain a SMEX/LEO-T Header format. Thereal-time data are Reed-Solomon decoded by the station prior to the transfer to LRO MOC.4.2.5.1.14.2.4.1.1 Support DurationThe SN provides the real-time VC0 data throughout the first several hours after LRO launch.The SN will also be used during pre-launch mission phases to support mission readiness testactivities.


4-120



4.2.5.1.24.2.4.1.2 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetryand Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinkeddata within a virtual channel data unit (VCDU) formatted structure. The station inserts theVCDU into a structure that has a SMEX/LEO-T header.

This data product consists of the selected VC0 downlinked data packets; the LRO T&C FormatsHandbook documents the VC1 contents and format. The data are binary and as such, no sampleproduct is provided in Appendix B.4.2.5.1.34.2.4.1.3 Accuracy and CompletenessTBR

4.2.5.24.2.4.2 (SN-2) Archived VC0 Orbiter Telemetry4.2.5.2.14.2.4.2.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at the White SandsComplex (WSC) in support of the launch and early orbit support activities. When the WSCreceives the real-time spacecraft housekeeping telemetry, WSC will store the telemetry with thefill data (VC63) removed. These files are stored at the WSC using their local storagefunctionality. The files are stored for up to seventy-two (72) hours in the event of a possibleretransmission to the LRO MOC upon request by the LRO operations team; this would normallybe considered within a contingency support concept.4.2.5.2.24.2.4.2.2 Support DurationThe WSC provides the Archived VC0 Orbiter Telemetry throughout the first several hours afterLRO launch. WSC will also be used during pre-launch mission phases to support missionreadiness test activities.4.2.5.2.34.2.4.2.3 FormatThe Archived VC0 Orbiter Telemetry Data File is stored as it is received from the spacecraftwith VC63 (fill data) removed. The format of this downlinked data contains VCDU formattedAPIDs and is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052).The Archived VC0 Orbiter Telemetry Data File is a binary file of the downlinked telemetry data;as such, no sample product is listed in Appendix B.The Archived VC0 Orbiter Telemetry data would be routed back to the LRO MOC as a socketconnections consisting of the stored APIDs.4.2.5.2.44.2.4.2.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed MissionRequirements document (LRO-RQMT-00048).


4-121



4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONSThis section contains the interface products generated by the seven SOCs. These products are allsent to the LRO Mission Operations Center. The LOLA SOC transmits the LOLA ImprovedGravity Model to the Flight Dynamics Facility, and to the LRO MOC, to assist in the improvedorbit determination process. Each science center has its own unique subsection to define thespecific products that the SOCs generate and send to the MOC.

For products that the SOCs generate, they are normally identified as either command files orspecific instrument command sequences; these are command products that need to be sent to theMOC for uplink to the corresponding instrument.4.3.1 CRaTER SOC ProductsThis section provides the lower-level information regarding the files sent from the CRaTER SOCto the LRO MOC.

4.3.1.1 (CRaTER-1) CRaTER LRO Operations Activity RequestThis is the CRaTER Activity request that identifies the daily command load for the for theCRaTER instrument4.3.1.1.1 Product DescriptionThe CRaTER SOC generates the CRaTER Activity Request and forwards the inputs to the LROMOC. The MOC (MPS element) merge the individual SOC Activity Requests with commandinput for the spacecraft and orbiter health and safety commands and any specific maneuvercommands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.1.1.2 Support DurationThe CRaTER SOC will provide support through all mission phases.4.3.1.1.3 FormatThe Activity Request file will consists of a Systems Test and Operations Language (STOL) file,a file of absolute time sequence (ATS) of commands, or a file of relative time sequence (RTS) ofcommands.A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.

pgf

Note

RFG comments: I'm missing a product which tells me whether and when a command (activity request) has been put into the spacecraft load. We send in the activity request; there seems to be no confirmation.

pgf

Highlight

CRaTER to MOC deliverable


4-122



If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO Project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.

If the file is an RTS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in a relative time format (± ddd:hh:mm:ss).A single, line-feed character (ASCII 10) delimits lines within the file.

An RTS command or activity is scheduled relative to the start or stop time of an event.A sample CRaTER InstrumentLRO Operations Activity Request for CRaTER (ATS or , RTS,or STOL procedure) is provided in Appendix B, Figure B.3-1Figure B.3-1.The following file-naming convention is used for files transmitted between the various SOCfacilities and the LRO MOC. The filename consists of eight 25 characters; it also contains a three- or four-character file extension name. There is a hyphen (-)an underscore (_) between the firsttwo four fields and a period (.) between the last two fields. The form of the filename is asfollows:

<instrument id>_-<file content>_<YYYYDOY>_<version number>.<file extension>

where instrument id = [42 characters]CRAT for CRaTER

file content = Activity – used to denote this is the CRaTER Activity Request[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify the type of commandload.

Date = YYYYDOYDOY = start date of data in file and not the creation date

version number = [2 3 characters] V followed by a Ttwo-digit version number. Theinitial version is 00, next is 01 … up to 99.

file extension = [3–4 characters] Standard file extension for all input files receivedfrom SOC; it will be named for the input file type:

RTS for relative time sequenceATS for absolute time sequence

PROC for procedureA sample CRaTER Activity Request file name for an ATS request isCRaTER_Activity_YYYYDOY_Vnn.ATS

A sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-1.

pgf

Cross-Out

pgf

Replacement Text

CRAT


4-123



4.3.1.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.1.2 (CRaTER-2) CRaTER Instrument Reset Timeline4.3.1.2.1 Product DescriptionThis is a file that contains one (1) week of UTC times when the CRaTER science team wishes toperform the power reset on the CRaTER instrument.4.3.1.2.2 Support DurationThe CRaTER SOC will provide support through all mission phases.4.3.1.2.3 FormatThe CRaTER Instrument Reset Timeline consists of the times in the upcoming week, when theinstrument will perform a power rest; the fields in the file are incrementing time-ordered. Thefields contained within this file are defined as time with no spaces between the various portionsof the time tag; where the fields are defined in the following table

Field name Field CharacteristicsTimetag (in UTC format):yearday of year andtime of day

YYYY DDD HHMMSS.sss, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 6 ASCII digits with a period between the first 6 and last 3

first 6 are theto represent hours, minutes, and seconds of day last 3 are the milliseconds of day

A sample CRaTER Instrument Reset Timeline filename is:

CRaTER_Reset_YYYYDOY_Vnn.ATSA sample CRaTER Instrument Reset Timeline is provided in Appendix B, Figure B.3-2FigureB.3-24.3.1.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.2 DLRE SOC ProductsThis section provides the lower-level information regarding the files sent from the DLRE SOC tothe LRO MOC.4.3.2.1 (DLRE-1) LRO Operations DLRE Activity RequestThis is the Command/Procedure request for instrument4.3.2.1.1 Product DescriptionThe DLRE SOC generates the LRO Operations DLRE Activity Request and forwards this inputfile to the LRO MOC. The MOC (MPS element) merge the individual SOC Activity Requestswith command input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.

pgf

Cross-Out

pgf

Replacement Text

CRAT

pgf

Highlight



4-124



All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.2.1.2 Support DurationThe DLRE SOC will provide support through all mission phases.4.3.2.1.3 FormatThe LRO Operations Activity Request file will consists of a Systems Test and OperationsLanguage (STOL) file, a file of absolute time sequence (ATS) of commands, or a file of relativetime sequence (RTS) of commands.

A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO Project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.If the file is an RTS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in a relative time format (± ddd:hh:mm:ss).A single, line-feed character (ASCII 10) delimits lines within the file.

An RTS command or activity is scheduled relative to the start or stop time of an event.A sample LRO Operations DLRE Activity Request (ATS, or RTS, or STOL procedure) isprovided in Appendix B, Figure B.3-1Figure B.3-1.Figure B.3-3The following file-naming convention is used for files transmitted between the various SOCfacilities and the LRO MOC. The filename consists of eight 25 characters; it also contains a three- or four-character file extension name. There is a hyphen (-)are underscores (_) between the firsttwofile name fields and a period (.) between the file name and file extension last two fields. Theform of the filename is as follows:

<instrument id>-<file content><version number>.<file extension><instrument id>_<file content>_<YYYYDOY>_<version number>.<file extension>


4-125



where instrument id = [2 4 characters]DL for DLRE

file content = Activity – used to denote this is the DLRE Activity Request[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify the type of commandload.


version number = [2 3 characters] TwoV followed by a two-digit version number. Theinitial version is 00, next is 01 … up to 99.



PROC for procedureA sample LRO Operations Activity Request for DLRE file name for an ATS request isDLRE_Activity_YYYYDOY_Vnn.ATS

A sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-1.4.3.2.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.2.2 (DLRE-2) DLRE FSW Load4.3.2.2.1 Product DescriptionThis file contains the FSW image and tables for the specified instrument; it contains the testedand verified files that the SOC will send on an as needed basis, as required to correct/updateinstrument Flight Software table and/or files.The DLRE SOC facility generates its unique FSW load request and forwards the image file tothe LRO MOC. The MOC (MPS element) merge the individual SOC Instrument FSW Loadswith command input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.4.3.2.2.2 Support DurationThe DLRE SOC will provide support through all mission phases.4.3.2.2.3 FormatThe DLRE Instrument FSW Load consists of the complete file/table image to be re-loaded, or astarting address, number of bytes to load and then the new table/file image portion.


4-126



In a load file, comments begin with either semi-colon (;) or hash (#) and continue to the end ofthe line. Blank lines and lines containing only comments are ignored. The first non-blank, non-comment line is the abstract record; this is copied to the formatted image load file but otherwiseignored. It is intended as a comment to identify the load.

The second line is the mission information line, which consists of several comma-separatedfields, as identified in the following table:

Parameter Name Parameter valuemission name This field is ignored by the ITOS LOAD directive.image ID This field is ignored by the ITOS LOAD directive.Date Copied to the formatted image load file but otherwise ignored.Version This field is ignored by the ITOS LOAD directive.Source This field is ignored by the ITOS LOAD directive.packet size Maximum packet size. When the LOAD directive formats the raw image load

file into packets, this is the maximum number of data bytes in each packet.swap Indicates whether or not the LOAD directive should swap bytes when

generating the formatted image load file. Byte swapping is only performed ifthis field has one of the values SWAPBYTES or UI085.

The following file-naming convention is used for the files transmitted between the variousDLRE SOC facilities and the LRO MOC. The filename consists of eight 24 characters; it alsocontains a three- or four-character file extension name. There is a hyphen (-)are underscores (_)between the first twofile name fields and a period (.) between the last twofile name and extensionfields. The form of the filename is as follows:


where instrument id = [2 4 characters]DL for DLRE

file content = [4 7 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofc o m m a n d l o a d .

FSWLOAD; to indicate a FSW load

Date = YYYYDOYDOY = Identifies the file creation date since this is a load file anddoes not contain any date/time related commands

version number = [32 characters] TwoV followed by a two-digit version number. Theinitial version is 00, next is 01 … up to 99.

file extension = [3–4 characters] Standard file extension for all input files receivedfrom a SOC; it will be named for the input file type:

IFTU for Instrument FSW Table Updatebin; to represent a binary load file for the DLRE FSW load


4-127



A sample file name for a DLRE-generated FSW Load isDLRE_FSWLOAD_YYYYDOY_Vnn.bin A sample DLRE Instrument FSW Load is providedin Appendix B, Figure B.3-4Figure B.3-3Figure B.3-44.3.2.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.3 LAMP SOC ProductsThis section provides the lower-level information regarding the files sent from the LAMP SOCto the LRO MOC.4.3.3.1 (LAMP-1) LAMP LRO Operations Activity RequestThis is the Command Activity request for the LAMP instrument.4.3.3.1.1 Product DescriptionThe LAMP SOC generates the LAMP LRO Operations Activity Request and forwards thisinput file to the LRO MOC. The MOC (MPS element) merge the individual SOC ActivityRequests with command input for the spacecraft and orbiter health and safety commands and anyspecific maneuver commands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.3.1.2 Support DurationThe LAMP SOC will provide support through all mission phases.4.3.3.1.3 FormatThe Activity Request file will consists of a Systems Test and Operations Language (STOL) file,a file of absolute time sequence (ATS) of commands, or a file of relative time sequence (RTS) ofcommands.A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five eight commands can be specified to occur


4-128



at the exact same absolute time. This is a limit specified by the LRO Project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.


An RTS command or activity is scheduled relative to the start or stop time of an event. Thefollowing file-naming convention is used for files transmitted between the various LAMP SOCfacilities and the LRO MOC. The filename consists of eight 25 characters; it also contains athree- or four-character file extension name. There is a hyphen (-)are underscores (_) betweenthe first twofile name fields and a period (.) between the last two file name and file extensionfields. The form of the filename is as follows:


where instrument id = [42 characters]LA for LAMP

file content = Activity – used to denote this is the DLRE Activity Request[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify the type of commandload.


version number = [2 3 characters] TwoV, followed by a two-digit version number.The initial version is 00, next is 01 … up to 99.



PROC for procedureA sample LAMP Activity Request file name for an ATS request isLAMP_Activity_YYYYDOY_Vnn.ATSA sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-1.A sample LRO Activity LAMP Activity Request for LAMP (ATS, or RTS, or STOLprocedure) is provided in Figure B.3-5.4.3.3.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


4-129



4.3.3.2 LAMP HV Command Sequence4.3.3.2.1Product DescriptionThis file contains the command sequence(s) to either disable or enable the LAMP High Voltage.4.3.3.2.2Support DurationThe LAMP SOC will provide support through all mission phases.4.3.3.2.3FormatThe file format consists of the relative time value, command mnemonic and sun-mnemonic usedto enable or disable the LAMP High Voltage. The fields of this file are defined in the followingtable:

Field name Field CharacteristicsRelative Timetag:corresponding to a time atwhich the command should beexecuted

HHMMSS, whereHHMMSS. => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and last 3 are the milliseconds of day

Command Mnemonic LAMP HV

Command Sub-Mnemonic On/Off

A sample LAMP HV Command Sequence is provided in Figure B.3-6.4.3.3.2.4Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.3.34.3.3.2 (LAMP-3) LAMP Instrument FSW Load4.3.3.3.14.3.3.2.1 Product DescriptionThis file contains the FSW image and tables for the specified instrument; it contains the testedand verified files that the SOC will send on an as needed basis, as required to correct/updateinstrument Flight Software table and/or files.

The LAMP SOC facility generates its unique FSW load request and forwards the image file tothe LRO MOC. The MOC (MPS element) merge the individual SOC Instrument FSW Loadswith command input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.4.3.3.3.24.3.3.2.2 Support DurationThe LAMP SOC will provide support through all mission phases.4.3.3.3.34.3.3.2.3 FormatThe LAMP Instrument FSW Load consists of the complete file/table image to be re-loaded, or astarting address, number of bytes to load and then the new table/file image portion.In a load file, comments begin with either semi-colon (;) or hash (#) and continue to the end ofthe line. Blank lines and lines containing only comments are ignored. The first non-blank, non-


4-130



comment line is the abstract record; this is copied to the formatted image load file but otherwiseignored. It is intended as a comment to identify the load.





The following file-naming convention is used for files transmitted between the various LAMPSOC facilities and the LRO MOC. The filename consists of eight 24 characters; it also contains athree- or four-character file extension name. There are underscores (_)is a hyphen (-) betweenthe first twofile name fields and a period (.) between the last twofile name and file extensionfields. The form of the filename is as follows:


where instrument id = [2 4 characters]LA for LAMP

file content = [4 7 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofc o m m a n d l o a d .





IFTU for Instrument FSW Table Updatebin; to represent a binary load file for the LAMP FSW load

A sample file name for a LAMP-generated FSW Load is


4-131



LAMP_FSWLOAD_YYYYDOY_Vnn.bin. A sample LAMP Instrument FSW Load isprovided in Appendix B, Figure B.3-7Figure B.3-4Figure B.3-74.3.3.3.44.3.3.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.4 LEND SOC ProductsThis section provides the lower-level information regarding the files sent from the LEND SOC tothe LRO MOC.

4.3.4.1 (LEND-1) LEND LRO Operations Activity RequestThis is the Command/Procedure request for instrument.4.3.4.1.1 Product DescriptionThe LEND SOC generates the LEND LRO Operations Activity Request and forwards thisinput file to the LRO MOC, specifically the MPS element. The MPS element merges theindividual SOC Activity Requests with command input for the spacecraft and orbiter health andsafety commands and any specific maneuver commands based on mission profile support phases.

All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.4.1.2 Support DurationThe LEND SOC will provide support through all mission phases.4.3.4.1.3 FormatThe Activity Request file will consists of a Systems Test and Operations Language (STOL) file,a file of absolute time sequence (ATS) of commands, or a file of relative time sequence (RTS) ofcommands.

A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO PROJECT so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.


4-132




An RTS command or activity is scheduled relative to the start or stop time of an event. Thefollowing file-naming convention is used for files transmitted between the various LEND SOCfacilities and the LRO MOC. The filename consists of eight 25 characters; it also contains athree- or four-character file extension name. There are underscores (_)is a hyphen (-) betweenthe first twofile name fields and a period (.) between the file name and file extensionlast twofields. The form of the filename is as follows:


where instrument id = [2 4 characters]LE for LEND

file content = Activity – used to denote this is a LEND Activity Request[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify the type of commandload.





PROC for procedureA sample LEND Activity Request file name for an ATS request isLEND_Activity_YYYYDOY_Vnn.ATSA sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-1.A sample LRO Operations LEND Activity Request for LEND (ATS, or RTS, or STOLprocedure) is provided in Figure B.3-8.4.3.4.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


4-133



4.3.5 LOLA SOC ProductsThis section provides the lower-level information regarding the files sent from the LOLA SOC tothe LRO MOC.4.3.5.1 (LOLA-1) LOLA LRO Operations Activity RequestThis is the Command/Procedure request for instrument.4.3.5.1.1 Product DescriptionThe LOLA SOC generates the LOLA LRO Operations Activity Request and forwards thisinput file to the LRO MOC, specifically the MPS element. The MPS element merges theindividual SOC Activity Requests with command input for the spacecraft and orbiter health andsafety commands and any specific maneuver commands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.5.1.2 Support DurationThe LOLA SOC will provide support through all mission phases.4.3.5.1.3 FormatThe Activity Request file will consists of a Systems Test and Operations Language (STOL) file,a file of absolute time sequence (ATS) of commands, or a file of relative time sequence (RTS) ofcommands.A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO PROJECT so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.

If the file is an RTS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in a relative time format (± ddd:hh:mm:ss).A single, line-feed character (ASCII 10) delimits lines within the file.An RTS command or activity is scheduled relative to the start or stop time of an event.


4-134



The following file-naming convention is used for files transmitted between the various LOLASOC facilities and the LRO MOC. The filename consists of eight 25 characters; it also contains athree- or four-character file extension name. There are underscores (_)is a hyphen (-) betweenthe first two file name fields and a period (.) between the file name and file extension last twofields. The form of the filename is as follows:


where instrument id = [2 4 characters]LO for LOLA

file content = Activity – used to denote this is a LOLA Activity Request[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify the type of commandload.


version number = [2 3 characters] TV, followed by a two-digit version number. Theinitial version is 00, next is 01 … up to 99.



PROC for procedureA sample LOLA Activity Request file name for an ATS request isLOLA_Activity_YYYYDOY_Vnn.ATSA sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-1.A sample LRO Operations LOLA Activity Request for LOLA (ATS, or RTS, or STOLprocedure) is provided in Figure B.3-9.4.3.5.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.5.2 (LOLA-2) LOLA Improved Lunar Gravity Model4.3.5.2.1 Product DescriptionThe LOLA Gravity Model is a file that contains the updated Lunar Gravity Model that the LOLAscience team generates from its internal data processing. This file is sent to both the FlightDynamics Facility and to the LRO MOC.


4-135



This data contains an improved lunar gravity model based on the continual processing of thecorrelated laser ranginge one-way transmit times and using S-Band and other LOLA instrumentdata. The LOLA SOC provides this data to FDF every 6 months. FDF will use the improvedLunar Gravity Model to reprocess the orbit data and to create new definitive SPICE File andephemeris information.4.3.5.2.2 Support DurationThis information is supplied only post-launch. The LOLA SOC delivers this data file to theLRO MOC and to the Flight Dynamics Facility at GSFC.4.3.5.2.3 FormatThe LOLA Improved Gravity Model File is an ASCII-formatted file based on the LOLAprocessing; this file includes new lunar gravity model data including the standard deviationvalues for the updated parameters .

The following file-naming convention is used for files transmitted between the LROC SOC andthe LRO MOC. The filename consists of 26 characters; it also contains a three-character fileextension name. There are underscores (_) between the file name fields and a period (.) betweenthe file name and file extension fields. The form of the filename is as follows:

<instrument id>_<file content>_<YYYYDOY>_<version number>.<file extension>

where instrument id = [4 characters]LROC

file content = GRAVMODEL – used to denote this is the newly calculated LOLAGravity Model Information

Date = YYYYDOY based on UTC TimeframeDOY = is the creation date

version number = [3 characters] V followed by a two-digit version number. The initialversion is 00, next is 01 … up to 99.

file extension = [3 characters] Standard file extension for all input files receivedfrom SOC; it will be named for the input file type:

bsp; to represent a binary SPK fileA sample LROC Activity Request file name for an ATS request isLROC_GRAVMODEL_YYYYDOY_Vnn.txt

A sample Improved Lunar Gravity Model data file is provided as a reference in Appendix B,Figure B.3-10Figure B.3-5B.3-11.

4.3.5.2.4Accuracy and CompletenessTBR

4.3.5.3 (LOLA-3) LOLA Instrument FSW Load4.3.5.3.1 Product Description


4-136



This file contains the FSW image and tables for the specified instrument; it contains the testedand verified files that the SOC will send on an as needed basis, as required to correct/updateinstrument Flight Software table and/or files.The LOLA SOC facility generates its unique FSW load request and forwards the image file tothe LRO MOC. The MOC (MPS element) merges the individual SOC Instrument FSW Loadswith command input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.4.3.5.3.2 Support DurationThe LOLA SOC will provide support through all mission phases.4.3.5.3.3 FormatThe LOLA Instrument FSW Load consists of the complete file/table image to be re-loaded, or astarting address, number of bytes to load and then the new table/file image portion. The LOLAInstrument FSW Load consists of the complete file/table image to be re-loaded, or a startingaddress, number of bytes to load and then the new table/file image portion.






The following file-naming convention is used for files transmitted between the various LOLASOC facilities and the LRO MOC. The filename consists of eight 24 characters; it also contains athree- or four-character file extension name. There are underscores (_) is a hyphen (-) betweenthe first twofile name fields and a period (.) between the last two file name and file extensionfields. The form of the filename is as follows:



4-137




file content = [4 7 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofco m m a n d l o a d .





IFTU bin for to represent a binary LOLA Instrument FSW LoadTable Update

A sample file name for a LOLA-generated FSW Load isLAMP_FSWLOAD_YYYYDOY_Vnn.bin. A sample LOLA Instrument FSW Load isprovided inin Appendix B, Figure B.3-11Figure B.3-6Figure B.3-11.4.3.5.3.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.5.4 (LOLA-4) LOLA Processed OD Information4.3.5.4.1 Product DescriptionThis file contains the LOLA–calculated Orbit Determination from data processing based on thetelemetry that LOLA from the LRO MOC as past of the real-time and post-pass s/c andinstrument housekeeping and measurement telemetry.4.3.5.4.2 Support DurationThe LOLA SOC will provide support through all mission phases.4.3.5.4.3 FormatThe LOLA Processed OD Information is a set of SPK formatted files based on the LOLA OrbitDetermination calculations. The LOLA SOC creates these files on a weekly basis from the datagathered over the last seven days. This SPK is consistent with other OD-like SPK filespreviously discussed in the FDF section.The LOLA Processed OD Information consists of TBR information.

A sample LOLA Processed OD Information is provided in Appendix B, Figure B.3-13.


4-138



The filename consists of eight 20 characters; it also contains a three- or four-character fileextension name. There is a hyphen (-)are underscores (_) between the first twofile name fieldsand a period (.) between the file name and file extensionlast two fields. The form of the filenameis as follows:



file content = SPK – used to denote this is a LOLA Processed SPICE SPK File[4characters] Intent of the instrument loads. These characters will becreated by the corresponding SOC to identify file contents

Date = YYYYDOY based on UTC TimeframeDOY = start date corresponding to when new Processed OD Data isvalid and not the creation date



bsp; to represent a binary SPK filetxt => for textual fileinformation

A sample LOLA Processed OD Information file name is LOLA_SPK_YYYYDOY_Vnn.bsp

Since the LOLA Processed OD Information is a binary SPK file, no sample product is providedin Appendix B.4.3.5.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.5.5 (LOLA-5) LOLA Target Requests4.3.5.5.1 Product DescriptionThis is a file that contains target request for LOLA imaging. This information is used to developthe attitude slew plan for the spacecraft.4.3.5.5.2 Support DurationThe LOLA SOC will provide support through all mission phases.4.3.5.5.3 FormatThe LOLA Target Requests are consistent with the standard format used by the LROC Targetrequest file; the LOLA SOC generates this file in a consistent manner and this file is identical tothe LROC version. consists of TBR information; most likely time values and lunar lat/long


4-139



position (or maybe an attitude quaternion representing the specific lunar Lat/Long position). Thefields are defined in the following table:

Field name Field CharacteristicsTimetag: (UTC Time)yearday of year andtime of day

YYYY DDD HHMMSS.sss, whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS.mmm => 10 6 ASCII digits with a period between the first 6 and last 3to represent hours, minutes, and seconds of day first 6 are the hours, minutes,and seconds of day last 3 are the milliseconds of day

Off-nadir angleLunar Latitude(? – TBR)

6 7 ASCII Characters representing the targeted Lunar Latitudeoff-nadir angle;where

first character is a positive/negative sign indicator (blank or -)Next 2 characters represent the whole value of latitude (-90 to 90)Next character is the decimal separatorNext 2 3 characters represent the decimal portion for lunar latitude (0 –

999)

Off-nadir durationLunarLongitude (? – TBR))

5 ASCII Characters representing the duration (in seconds)for the off-nadir angle;where

5 characters represent the duration time (in seconds) (0 – 99999)6 ASCIICharacters representing the targeted Lunar Longitude; ; where first 3 character represent the whole decimal value of longitude (0 -360) Next character is the decimal separator Next 2 characters represent the decimal portion for lunar longitude (0 – 999)

A representative sample concept for the off nadir targets is provided:

yyyy_doy.hhmmss, +5.6, 20yyyy_doy.hhmmss, -10.3, 150yyyy_doy.hhmmss, +20.2, 140

The filename consists of eight 25 characters; it also contains a three- or four-character fileextension name. There is a hyphen (-) are underscores (_) between the first twofile name fieldsand a period (.) between the last twofile name and file extension fields. The form of the filenameis as follows:




4-140



file content = [4 7 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofcommand load.

TARGETS

YYYDOY = YYYYDOY whereYYYY => 4 ASCII digits of year (2008 – 2013)DOY => 3 ASCII digits for day of year (1 – 366) Note: DOYrepresents the start time of data within the file, not the file creationtime

version number = [2 3 characters] TV, followed by a two-digit version number. Theinitial version is 00, next is 01 … up to 99.


txt => for textual filesRTS for relative time sequence ATS for absolute time sequence PROC for procedure

A sample LOLA Target Request file is identified as LOLA_TARGETS_yyyydoy_V00.txt

A sample LOLA Target Requests File is provided in Appendix B, Figure B.3-13Figure B.3-7Figure B.3-13.4.3.5.5.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.6 LROC SOC ProductsThis section provides the lower-level information regarding the files sent from the LROC SOC tothe LRO MOC.

4.3.6.1 (LROC-1) LRO Operations Activity Request for LROCThis is the LROC Operations Activity request that identifies a set of commands or proceduresthat LROC generates on an as-needed basis to support instrument operations.4.3.6.1.1 Product DescriptionThe LROC SOC generates the LRO Operations Activity Request and forwards the inputs to theLRO MOC. The MOC (MPS element) merge the individual SOC Activity Requests withcommand input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.


4-141



If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.6.1.2 Support DurationThe LROC SOC will provide support through all mission phases.4.3.6.1.3 FormatThe Activity Request file will consists of a file of absolute time sequenced (ATS) commands, ora file of relative time sequenced (RTS) commands.

The ATS and RTS file will be an ASCII comma-delimited file. The end of an entry for an ATSor RTS file is marked by a semicolon (;). This identifies that anything following the semicolon istreated as a comment and not processed by the mission planning system. Comments can occuranywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only eight commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO Project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.

If the file is an RTS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in a relative time format (± hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file.

An RTS command or activity is scheduled relative to the start or stop time of an event.The following file-naming convention is used for files transmitted between the LROC SOC andthe LRO MOC. The filename consists of 25 characters; it also contains a three-character fileextension name. There are underscores (_) between the file name fields and a period (.) betweenthe file name and file extension fields. The form of the filename is as follows:



file content = Activity – used to denote this is the LROC Activity Request.

Date = YYYYDOY based on UTC TimeframeDOY = start date of data in file and not the creation date



4-142





A sample LROC Activity Request file name for an ATS request isLROC_Activity_YYYYDOY_Vnn.ATSA sample LRO Operations Activity Request File is provided in Appendix B, Figure B.3-1FigureB.3-14.3.6.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.6.14.3.6.2 (LROC-2) LROC Instrument Initialization Command Sequence4.3.6.1.14.3.6.2.1 Product DescriptionThis file is the command load that LROC SOC uses to initialize the LROC instrument. This fileis delivered electronically to the LRO MOC. The instrument initialization command sequence isused to identify which set of command to use whenever the LROC instrument isinitialized.Eventually, the MPS element merges this instrument initialization Activity Requestwith other command input for the spacecraft and orbiter health and safety commands and anyspecific maneuver commands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.6.1.24.3.6.2.2 Support DurationThe LROC SOC will provide support through all mission phases.4.3.6.1.34.3.6.2.3 FormatAn Instrument initialization command sequence provides the instrument FSW load that theLROC SOC wants to load at startup; this file is a binary content that the instrument uses duringthe initialization processThe operations team generates command that are used to load these files into the Orbiter’s solidstate recorder LROC directory structure. The following file-naming convention is used for filestransmitted between the LROC SOC and the LRO MOC. The filename consists of 31 characters;it also contains a three-character file extension name. There are underscores (_) between the filename fields and a period (.) between the file name and file extension fields. The form of thefilename is as follows:

<instrument id>_<file content>_<version number>.<file extension>


4-143



where instrument id = [4 characters]LROC, followed by the underscore character (_)

file content = [21 characters] Intent of the instrument loads.Init_Command_Seq_Filen; wheren = 1 thru 8 to identify the appropriate load file; followed by

the underscore character (_)

version number = [3 characters] V, followed by a two-digit version number. Theinitial version is 00, next is 01 … up to 99.


bin to indicate instrument command loadSample LROC File name

LROC_Init_Command_Seq_File1_V00.bin

LROC_Init_Command_Seq_File2_V00.binLROC_Init_Command_Seq_File3_V00.bin;

…LROC_Init_Command_Seq_File8_V00.bin;

The LROC Instrument Initialization Command Sequence is a binary formatted file and assuch, there is no sample product provided in Appendix B,A command or activity file can either contain a list of ATS or RTS entries or a STOL commandprocedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entryfor an ATS or RTS file is marked by a semicolon (;). This identifies that anything following thesemicolon is treated as a comment and not processed by the mission planning system. Commentscan occur anywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only five commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.



4-144



An RTS command or activity is scheduled relative to the start or stop time of an event. Thefilename consists of eight characters; it also contains a three- or four-character file extensionname. There is a hyphen (-) between the first two fields and a period (.) between the last twofields. The form of the filename is as follows:

<instrument id>-<file content><version number>.<file extension>

where instrument id = [2 characters] LR for LROC

file content = [4 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofcommand load.

version number = [2 characters] Two-digit version number. The initial version is 00,next is 01 … up to 99.

file extension = [3–4 characters] Standard file extension for all input files receivedfrom SOC; it will be named for the input file type: RTS for relative time sequence ATS for absolute time sequence PROC for procedure

A sample LROC Instrument Initialization Command Sequence (ATS, RTS, or STOLprocedure) is provided in Appendix B, Figure B.3-15Figure B.3-15.4.3.6.1.44.3.6.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.6.24.3.6.3 (LROC-3) LROC Daily Command Sequence4.3.6.2.14.3.6.3.1 Product DescriptionThis file is the text version of daily LROC sequence that identifies times of imaging and otherinstrument-related command parameters. This file is delivered electronically to the LRO MOC,specifically the MPS element. This file is used for visual verification of the commands that theLROC SOC transmitted within the binary command load file referenced in the previoussubsection.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.4.3.6.2.24.3.6.3.2 Support DurationThe LROC SOC will provide support through all mission phases.4.3.6.2.34.3.6.3.3 FormatThe LROC Daily Command Sequence is an ASCII file that consists of a set of absolute timesequenced (in UTC) time tag and corresponding command mnemonics and any required sub-mnemonics. All commands in the file must be defined in the LRO Telemetry and Command


4-145



Formats Handbook (431-HDBK-000052). If the command contains submnemonics, they mustbe specified with the command.

The fields are defined in the following table:

Field name Field CharacteristicsTimetag:yearday of year andtime of day



Command Mnemonic Valid LROC Command Mnemonics as defined within the T&C Formats Handbook

A sample daily command sequence product is represented asYYYYDOY HHMMSS, Command Mnemonic, <submnemonic value>= nnnn, <submnemonic value>= discretevalue, submnemonic value = Boolean, or <submnemonic state>2009015 093530 GSHKIOWHKCFGREG SPID=0XF2, LOGADDR=0X6F, METCLKA, DISABLE, PRI_A2009 093530 GSHKIOWLALSCFGREG LOGADDR=0X70, RXACTV, TXACTV, STOP1BIT, POLEVEN,PARDIS, USE8BIT, BAUDRATE=0X3254Note: these are not actual representations of LROC commands, but are referenced here toprovide a high-level concept of what format and concepts that the LRO MOC is requesting asinput from the SOC.

The following file-naming convention is used for files transmitted between the LROC SOC andthe LRO MOC. The filename consists of 20 characters; it also contains a three-character fileextension name. There are underscores (_) between the file name fields and a period (.) betweenthe file name and file extension fields. The form of the filename is as follows:



file content = [3 characters] Intent of the instrument loads. For LROC this isidentified asDCS = Daily Command Sequence

Date = YYYYDOY whereYYYY => 4 ASCII digits of year (2008 – 2013)DOY => 3 ASCII digits for day of year (1 – 366) Note: DOYrepresents the start time of data within the file, not the file creationtime



4-146




ATS for absolute time sequenceA sample file names is LROC_DCS_yyyydoy_V00.atsThe form of the filename is as follows:





file extension = [3–4 characters] Standard file extension for all input files receivedfrom SOC; it will be named for the input file type: RTS for relative time sequence ATS for absolute time sequence PROC for procedure

A sample LROC Daily Command Sequence (ATS,) is provided in Appendix B, Figure B.3-16Figure B.3-9Figure B.3-16.4.3.6.2.44.3.6.3.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.6.34.3.6.4 (LROC-4) LROC Target Request4.3.6.3.14.3.6.4.1 Product DescriptionThis is file that contains target request for LROC imaging; the MOC uses this information todevelop the attitude slew plan, which is eventually incorporated into the composite commandload.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.4.3.6.3.24.3.6.4.2 Support DurationThe LROC SOC will provide support through all mission phases.4.3.6.3.34.3.6.4.3 FormatThe file contains the time of the requested LROC target, a corresponding off-nadir angle, and atime duration for staying off-nadir; the fields are defined in the following table:


4-147




YYYY DDD HHMMSS.sss, (Time is UTC time representation), whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS => 6 ASCII digits used to represent the hours, minutes, and seconds ofdayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day

Off-nadir angle 7 ASCII Characters representing the targeted off-nadir angle; wherefirst character is a positive/negative sign indicator (blank or -)Next 2 characters represent the whole value of angle (-90 to 90)Next character is the decimal separatorNext 3 characters represent the decimal portion for the angle (0 – 999)

Off-nadir duration 5 ASCII Characters representing the duration (in seconds)for the off-nadir angle;where

5 characters represent the duration time (in seconds) (0 – 99999)

The following file-naming convention is used for files transmitted between the LROC SOC andthe LRO MOC. The filename consists of eight 25 characters; it also contains a three- or four-character file extension name. There is a hyphen (-)underscores (_) between the first twofilename fields and a period (.) between the last twofile name and file extension fields. The form ofthe filename is as follows:



file content = [7 characters] Intent of the command load.TARGETS




txt => for textual files



4-148






file extension = [3–4 characters] Standard file extension for all input files receivedfrom SOC; it will be named for the input file type: txt => for textual files

LROC_TARGETS_YYYYDOY_V00.txtA sample LROC Target Request is provided in Appendix B, Figure B.3-17Figure B.3-10FigureB.3-17.4.3.6.3.44.3.6.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.3.7 Mini-RF SOC ProductsThis section provides the lower-level information regarding the files sent from the Mini-RF SOCto the LRO MOC.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

4.3.7.1 (Mini-RF-1) LRO Operations Activity Request for Mini-RFThis is the Mini-RF Activity request that identifies the daily command load for the for the Mini-RF instrument4.3.7.1.1 Product DescriptionThe Mini-RF SOC generates the LRO Operations Activity Request for Mini-RF and forwardsthe inputs to the LRO MOC. The MOC (MPS element) merge the individual SOC ActivityRequests with command input for the spacecraft and orbiter health and safety commands and anyspecific maneuver commands based on mission profile support phases.All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start orstop time of an event. If a timetag is in universal time code (UTC) format, the command oractivity will occur at the absolute specified time.4.3.7.1.2 Support Duration


4-149



The Mini-RF SOC will provide support through all mission phases.4.3.7.1.3 FormatThe Activity Request file will consists of a file of absolute time sequenced (ATS) commands, ora file of relative time sequenced (RTS) commands.The ATS and RTS file will be an ASCII comma-delimited file. The end of an entry for an ATSor RTS file is marked by a semicolon (;). This identifies that anything following the semicolon istreated as a comment and not processed by the mission planning system. Comments can occuranywhere with the file.If the file is an ATS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activityis scheduled to occur at the identified time. Only eight commands can be specified to occur at theexact same absolute time. This is a limit specified by the LRO Project so that a closelytimetagged subsequent command is not skipped erroneously because of timing problems.If the file is an RTS file, it contains a header entry followed by any number of command oractivity entries. The commands or activities must be in a relative time format (± hh:mm:ss). Asingle, line-feed character (ASCII 10) delimits lines within the file.An RTS command or activity is scheduled relative to the start or stop time of an event.

A sample LRO Operations Activity Request (ATS or RTS) is provided in Appendix B, FigureB.3-1Figure B.3-1.

The following file-naming convention is used for files transmitted between the Mini-RF SOCand the LRO MOC. The filename consists of 25 characters; it also contains a three-character fileextension name. There underscores (_) between the file name fields and a period (.) between thefile name and file extension fields. The form of the filename is as follows:


where instrument id = [4 characters]MINI for Mini-RF

file content = Activity – used to denote this is the Mini-RF Activity Request.






4-150



Sample file name isMini_Activity_YYYYDOY_Vnn.ATS4.3.7.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.7.14.3.7.2 (Mini-RF-2) Mini-RF Load Files4.3.7.1.14.3.7.2.1 Product DescriptionThis file contains the FSW image and tables for the specified instrument; it contains the testedand verified files that the SOC will send on an as needed basis, as required to correct/updateinstrument Flight Software table and/or files.The Mini-RF SOC facility generates its FSW load request and forwards the image file to theLRO MOC. The MOC (MPS element) merges the individual SOC Instrument FSW Loads withcommand input for the spacecraft and orbiter health and safety commands and any specificmaneuver commands based on mission profile support phases.4.3.7.1.24.3.7.2.2 Support DurationThe MINI-RF SOC will provide support through all mission phases.4.3.7.1.34.3.7.2.3 FormatThe Instrument FSW Load consists of the complete file/table image to be re-loaded, or a startingaddress, number of bytes to load and then the new table/file image portion.






The following file-naming convention is used for files transmitted between the various Mini-RFSOC facilities and the LRO MOC. The filename consists of eight twenty-one (21) characters; italso contains a three- or four-character file extension name. There is a hyphen (-)are underscores


4-151



(_) between the first twofile name fields and a period (.) between the last twofile name and hefile extension fields. The form of the filename is as follows:



where instrument id = [2 4 characters]RF MINI for Mini-RF followed by the underscore (_) character

file content = [4 characters] Intent of the instrument loads.LOAD – used to denote this is the Mini-RF Load File.; followed bythe underscore (_) characterThese characters will be created by thecorresponding SOC to identify the type of command load.


version number = [2 3 characters] V, followed by a Ttwo-digit version number. Theinitial version is 00, next is 01 … up to 99.


IFTU bin to represent a binaryfor Instrument FSW TableUpdate

Sample file name is Mini_Load_YYYYDOY_Vnn.bin

A sample Mini-RF Load File is provided in Appendix B, Figure B.3-18Figure B.3-11FigureB.3-19.4.3.7.1.44.3.7.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.7.24.3.7.3 (Mini-RF-3) Mini-RF Command Timeline4.3.7.2.14.3.7.3.1 Product DescriptionThis file contains a set of command sequences that the MOC uses to create a daily load foruplink to the Mini-RF instrument.

All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.4.3.7.2.24.3.7.3.2 Support DurationSupport will be provided through all mission phases.4.3.7.2.34.3.7.3.3 FormatThe Mini-RF Command Timeline consists of the complete set of commands used on-board theLRO spacecraft to manage the Mini-RF instrument.


4-152



The following file-naming convention is used for files transmitted between the various Mini-RFSOC facilities and the LRO MOC. The filename consists of eight 22 characters; it also contains athree- or four-character file extension name. There is a hyphen (-)are underscores (_) betweenthe first twofile name fields and a period (.) between the last twofile name and file extensionfields. The form of the filename is as follows:<instrument id>_<file content>_<YYYYDOY>_<version number>.<file extension>


where instrument id = [2 4 characters]RF MINI for Mini-RF; followed by the underscore (_) character

file content = [4 characters] Intent of the instrument loads. These characters willbe created by the corresponding SOC to identify the type ofcommand load.CMDTL to represent a Command Timeline File


version number = [2 3 characters] V followed by a Ttwo-digit version number. Theinitial version is 00, next is 01 … up to 99.


RTS for relative time sequence ATS for absolute time sequence PROC for proceduretxt to represent textual file of commands

A sample file name is Mini_CMDTL_YYYYDOY_Vnn.txt

A sample Mini-RF Command Timeline is provided in Appendix B, Figure B.3-19Figure B.3-12Figure B.3-20.4.3.7.2.44.3.7.3.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.3.7.4 (Mini-RF-4) Mini-RF Target Request4.3.7.4.1 Product DescriptionThis is file that contains target request for Mini-RF off-nadir slews; the MOC uses thisinformation to develop the attitude slew plan.

All commands in the file must be defined in the LRO Telemetry and Command FormatsHandbook (431-HDBK-000052). If the command contains submnemonics, they must bespecified with the command.4.3.7.4.2 Support Duration


4-153



The Mini-RF SOC will provide support through all mission phases.4.3.7.4.3 FormatThe file contains the time of the requested Mini-RF targets, a corresponding off-nadir angle, anda time duration for staying off-nadir; the fields are defined in the following table:


YYYY DDD HHMMSS, (Time is UTC time representation), whereYYYY => 4 ASCII digits of year (2008 – 2013)DDD => 3 ASCII digits for day of year (1 – 366)HHMMSS => 6 ASCII digits used to represent the hours, minutes, and seconds ofday

Off-nadir angle 7 ASCII Characters representing the targeted off-nadir angle; wherefirst character is a positive/negative sign indicator (blank or -)Next 2 characters represent the whole value of angle (-90 to 90)Next character is the decimal separatorNext 3 characters represent the decimal portion for the angle (0 – 999)

Off-nadir duration 5 ASCII Characters representing the duration (in seconds)for the off-nadir angle;where

5 characters represent the duration time (in seconds) (0 – 99999)

The filename consists of eight characters; it also contains a three- or four-character file extensionname. There is a hyphen (-) between the first two fields and a period (.) between the last twofields. The form of the filename is as follows:


where instrument id = [6 characters]MINI

file content = [14 characters] Intent of the command load.TargetRequests




txt => for textual filesMINI_RF_TargetRequests_YYYYDOY_V00.txtA sample Mini-RF Target Request is provided in Appendix B, Figure B.3-20Figure B.3-1321.


4-154



4.3.7.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.4 LRO FSWM Facility to LRO MISSION MOC INTERFACE PRODUCTSThis section contains the interface between the Flight SW Maintenance (FSWM) Facility and theLRO MOC,; which the FSWM facility resides at GSFC within the FSW Branch, Code 582. andthe LRO MOC. This interface is used to transfer the on-board FSW updates for table andmemory loads to the Orbiter.4.4.1.1 (FSWM-1) Orbiter FSW Load Files4.4.1.1.1 Product DescriptionThis file contains the table or memory updates that are generated and verified by the FSWbranch. These files are used to modify the on-board memory of the LRO single board computer..4.4.1.1.2 Support DurationThe FSWM facility will provide support through all mission phases.4.4.1.1.3 FormatThe Orbiter FSW Load File contains the updated memory and is a binary formatted file. Sincethe file is a binary format, no sample product is shown in Appendix B.The file name for this memory/table load is defined in the FSW Data ICD.4.4.1.1.4 Accuracy and PrecisionRequired accuracy is 100-percent fidelity of received data, which is best available4.5 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONSThis section contains the interface products generated by the LRO MOC. In some cases, theseproducts were originally created by other facilities, such as the LRO Flight Dynamics Facility orthe stations and transferred to the LRO MOC. The LRO MOC then controls the delivery of thesefiles to the science centers and the Planetary Data System (PDS) facility.

4.5.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERSThis section provides the details related to the products that the LRO MOC transmits to eachindividual science center. These two tables, Table 3-1Table 3-1 and Table 4-1Table 4-1, providea cross reference between the logical products that the MOC transmits and the intendedrecipients and provide some details regarding the method and frequency of delivery. Furtherinformation is then provided within subsequent subsections.

All instruments, except for LROC, follow a base file name convention that includes thefollowing file name information: instrument ID, YYYY, DDD, serial counter; the file nameextension is identified as either .sci or .hk. The LROC-specific file naming conventions aredefined in 4.5.1.16.

The file name conventions and standards are defined in the following table”:


4-155



Table 4-29 SOC File Naming Conventions and Descriptions

File Name qualifiers Description

Instrument ID NNNN is a 4 ASCII characters used to represent the specificinstrument; where NNN = > = CRAT for CRaTER Instrument data files = DLRE for the DLRE instrument files = LAMP for the LAMP instrument files = LEND for the LEND instrument files = LOLA for LOLA instrument files = LROC for the LROC instrument files = MINI for the Mini-RF instrument files

YYYYDDD YYYYDDD is a 7 character year and Dao if year designations,such as YYYY => 4 character year designator (2008 – 2013) DDD => 3 character day of year designator (001 – 366)

serial counter NNNNNNNNN is a nine character sequentially incrementingnumber used to uniquely identify the files; (000000001 –9999999)

file name extension 2 or 3 character designation used to identify the file type = .hk for instrument housekeeping data files = ..sci for raw science data files

The following sections provide the information related to the general set of MOC-generatedproducts, which are used by all Science Centers. This information is initially listedhere, and then is cross-referenced in each section for the specified science centers.

4.5.1.1 (MOC-7) Daily Command Load Report4.5.1.1.1 Product DescriptionThis file contains the textual version of the daily uplinked command load, which the LRO MOCsent to the LRO spacecraft.4.5.1.1.2 Support DurationThe MOC will provide support through all mission phases.4.5.1.1.3 FormatThe Daily Command Load consists of the complete textual set of integrated commands sent tothe LRO spacecraft. This Daily Command Load Report consists of the integrated spacecrafthousekeeping commands to manage the LRO health and safety and the received set of instrumentcommands that a corresponding SOC had previously sent to the LRO MOC for uplink to thespacecraftfor any/all science centers. This command report defines the load for next day; based


4-156



on operations team approval and signature of the corresponding binary load). The LRO MOCuses the following file-naming convention is used for MOC-transmitted files transmitted fromthe LRO MOC. The filename consists of eight 18 characters; it also contains a three characterfile extension name. There are underscores (_) between the file name designators and Tthere is aperiod (.) between the last twofile name and file extension fields. The form of the filename is asfollows:

<File Designator>_<YYYYDOY>_<version number>.<file extension>

where File Name = 18 Characters; used to identify the MOC generated file name andstart date of data

File Designator = [6 characters] to identify file (followed by underscore (_)LROATS

Date = [7 characters], YYYYDOY represented in UTC format andfollowed by underscore(_);where

YYYY => 4 ASCII digits of year (2008 – 2013)DOY => 3 ASCII digits for day of year (1 – 366) and where

day of year indicates the first day for which data are represented


file extension = [3characters] Standard file extension for all input files receivedfrom a SOC; it will be named for the input file type:

txt for text filesA sample LRO Daily Command Load Report file name is LROATS_yyyydoy_V00.txt

<File name><version number>.<file extension>

where File Name = [6 Characters] LROCMD


file extension = [3characters] Standard file extension for all input files receivedfrom a SOC; it will be named for the input file type: txt for text files

A sample Daily Command Load is provided in Appendix B, Figure B.4-1Figure B.4-1.4.5.1.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


4-157



4.5.1.2 (MOC-2) SPICE SLCK Clock Correlation File4.5.1.2.1 Product DescriptionThis file contains the daily log of spacecraft to ground correlation times with amount ofadjustments.4.5.1.2.2 Support DurationThe MOC will provide support through all mission phases.4.5.1.2.3 FormatThe Clock Correlation File is an ASCII-formatted file that consists of the complete set of clockupdates sent to the LRO spacecraft to keep the on-board clock synchronized to UTC. Thefollowing file-naming convention is used for files transmitted from the LRO MOC. The filenameconsists of eight 22 characters; it also contains a three character file extension name. The MOCuses the following file-naming convention for files that it transmits. The filename consists of 25characters; it also contains a three-character file extension name. There are underscores (_)between the file name fields and a period (.) between the file name and file extension fields.There is a period (.) between the last two fields. The form of the filename is as follows:

<Mission Designator>_<File Type>_<YYYYDOY>_<version number>.<file extension>where File Name = [22 Characters]

MissionDesignator

= [3 characters] to identify file (followed by underscore (_)LRO

File Type = [6 Characters] followed by the underscore (_)CLKCOR_

Date = [7 characters], YYYYDOY; represented in UTC format andfollowed by underscore(_);where


day of year indicates when the file is generated


file extension = [3characters] Standard file extension for the SPICE ClockCorrelation File

tcsSample File name is LRO_CLKCOR_2009015_V00.tcs<File name><version number>.<file extension>

where File Name = [6 Characters] ClkCor


4-158





A sample Clock Correlation File is provided in Appendix B, Figure B.4-2Figure B.4-2.4.5.1.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.5.1.3 (MOC-33) SPICE Event Kernel4.5.1.3.1 Product DescriptionThe SPICE Event kernel identifies the various spacecraft, orbiter, or science events occurring ona nominal day or orbit boundary that are used to denote times of no science data capture events,such as the station keeping maneuvers.4.5.1.3.2 Support DurationThis file is generated in support of both pre-launch and post-launch activities; it is specificallyused for all post-LOI mission phases.4.5.1.3.3 FormatThe Events Kernel is an ASCII-formatted file that consists of the complete set of events (insequential time-order) when the instruments are not collecting science data, such as duringspacecraft station keeping maneuvers.

The LRO MOC uses the following file-naming convention for this file; the filename consists of22 characters; it also contains a three character file extension name. There are underscores (_)between the file name fields and a period (.) between the file name and file extension fields.A sample file name for the first generation of this data file is given as for a binary file (littleEndian format) or .xsp for a SPICE SPK Transfer Format. {Sample sent in .xsp format}.<File Designator>_<YYYYDOY>_<version number>.<file extension>

where File Name = [22 Characters]

File Designator = [3 characters] to identify file (followed by underscore (_)LRO

File Type = [6 Characters] followed by the underscore (_)EvtKer





4-159




file extension = [3characters] Standard file extension for an ASCII text filetxt

Sample File name is LRO_EvtKer_2009015_V00.txt

The product is generated on a daily basis; a sample file name is identified as TBR.

The SPICE Event Kernel is an binary ASCII file and is not shown in the Appendix B, FigureB.4-3Figure B.4-3.4.5.1.3.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.5.1.4 (MOC-39) SPICE FK – Frame Kernels4.5.1.4.1 Product DescriptionThe Frame kernel provides the definition and specification and the relationship betweenof thevarious referencereferences frames (coordinate systems) used on the Orbiter; this includesreference mounting angles and reference matrices for various spacecraft HW and actuators, aswell as the science instrument mounting alignments. Multiple LRO groups provide the inputs tocreate this file; these inputs are in the form of various project derived documentation.4.5.1.4.2 Support DurationThis file is generated in support of both pre-launch and post-launch activities.4.5.1.4.3 FormatThe Frames Kernel File is an ASCII-formatted file that provides the complete set of coordinatetransfer frames from the spacecraft body frame to instrument or other orbiter componentreference frames.The MOC uses the following file-naming convention for this file. The filename consists of 25characters; it also contains a three-character file extension name. There are underscores (_)between the file name fields and a period (.) between the file name and file extension fields.

A sample file name for the first generation of this data file is given as.<File Designator>_<YYYYDOY>_<version number>.<file extension>


File Designator = [3 characters] to identify file (followed by underscore (_)LRO

File Type = [6 Characters] followed by the underscore (_)FRAMES


4-160







file extension = [3characters] Standard file extension for an ASCII text filetxt

Sample File name is LRO_FRAMES_2009015_V00.txtThe SPICE Frames Kernel is an ASCII file and is shown in the Appendix B, A sample file namefor the first generation of this data file is given as for a binary file (little Endian format) or .xspfor a SPICE SPK Transfer Format. {Sample sent in .xsp format}. A sample file name isidentified as TBR.The product will be generated once pre-launch and possible once post –launch based on updatedreference matrices to indicate if any of the identified alignments were biased because of launchconditions.

A sample Frame Kernel is shown in the Appendix B Figure B.4-4Figure B.4-4.4.5.1.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.5.1.5 (MOC-41) SPICE Predicted CK (Predicted S/C Orientation)4.5.1.5.1 Product DescriptionThe SPICE Predicted CK file contains the predicted LRO spacecraft orientation with respect toits orbit.4.5.1.5.2 Support DurationThe SPICE Predicted CK File is generated for after the post-LOI mission phases.4.5.1.5.3 FormatThe SPICE Predicted CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF34_2009015_2009042_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated daily. Product will include 28 days worth of data. SPK file will betype 13 and interpolation order 11; since this is a binary formatted file, no sample product will beshown in Appendix B.4.5.1.5.4 Accuracy and Completeness


4-161



TBR4.5.1.6 (MOC-42) SPICE Definitive CK (Definitive S/C Orientation)4.5.1.6.1 Product DescriptionThe SPICE Definitive CK file contains the definitive LRO spacecraft orientation.4.5.1.6.2 Support DurationThe SPICE Definitive CK File is generated for all post-LOI mission phases.4.5.1.6.3 FormatThe SPICE Definitive CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF35_2009014_2009015_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated daily. The product includes the previous day of data. SPK file willbe type 13 and interpolation order 11; since this is a binary formatted file, no sample product willbe shown in Appendix B.4.5.1.6.4 Accuracy and CompletenessTBR4.5.1.7 (MOC-43) SPICE Definitive HGA Orientation CK4.5.1.7.1 Product DescriptionThis SPICE Definitive CK file contains the definitive orientation of the High-Gain Antenna withrespect to the LRO spacecraft..4.5.1.7.2 Support DurationThis SPICE Definitive CK File is generated for all post-LOI mission phases.4.5.1.7.3 FormatThe SPICE Definitive CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF35_2009014_2009015_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.The SPICE ID for LRO is -85, as assigned by JPL.

The product will be generated daily. The product includes the previous day of data. SPK file willbe type 13 and interpolation order 11; since this is a binary formatted file, no sample product willbe shown in Appendix B.4.5.1.7.4 Accuracy and CompletenessTBR


4-162



4.5.1.8 (MOC-44) SPICE Definitive SA Orientation CK4.5.1.8.1 Product DescriptionThis SPICE Definitive CK file contains the definitive orientation of the Solar Arrays with respectto the LRO spacecraft.4.5.1.8.2 Support DurationThe SPICE Definitive CK File is generated for all post-LOI mission phases.4.5.1.8.3 FormatThe SPICE Definitive CK File is a binary formatted file generated by the SPICE Toolset. Asample file name for the first generation of this data file is given asFDF35_2009014_2009015_n01.bsp for a binary file (little Endian format) or .xsp for a SPICESPK Transfer Format.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated daily. The product includes the previous day of data. SPK file willbe type 13 and interpolation order 11; since this is a binary formatted file, no sample product willbe shown in Appendix B.4.5.1.8.4 Accuracy and CompletenessTBR4.5.1.9 (MOC-45) HGA/SA Fixed Offset Frames Kernel4.5.1.9.1 Product DescriptionThe HGA/SA Fixed Offset CK file contains the as-measured HGA and SA orientation inreferenced to the LRO spacecraft.4.5.1.9.2 Support DurationThe HGA/SA Fixed Offset CK file is generated for after the post-LOI mission phases.4.5.1.9.3 FormatThe HGA/SA Fixed Offset CK file is an ASCII formatted file generated by the LRO Project andsupport personnel. A sample file name for the first generation of this data file is given asFDF31_2009015_n01.txt for a text file.

The SPICE ID for LRO is -85, as assigned by JPL.The product will be generated at most twice during the mission; once during the pre-launchmission phase and then once post-launch. The HGA/SA Fixed Offset CK file is provided as asample product Appendix B.

A sample file name for the first generation of this data file is given as FDF31_2009015_n01.txt.4.5.1.9.4 Accuracy and CompletenessTBR


4-163



4.5.1.10 Instrument – Spacecraft Housekeeping Data File4.5.1.10.1 Product DescriptionThis file contains the selected spacecraft telemetry parameters used by the instrument; it includesinformation such as attitude, spacecraft temperatures, etc. Once the SOC identifies the requestedtelemetry points, the corresponding APIDs will be extracted and archived in separate file for theinstruments.4.5.1.10.2 Support DurationThe MOC will provide this support through all mission phases.4.5.1.10.3 FormatThe Instrument – Spacecraft Housekeeping Data File consists of the complete set of LROspacecraft telemetry APIDs that the specific SOC has identified to support its internalprocessing.All instruments, except for LROC, follow a base file name convention that includes thefollowing file name information: instrument ID, YYYY, DDD, serial counter; the file nameextension is identified as either .sci or .hk. The LROC-specific file naming conventions aredefined in Section 4.5.1.12The file name conventions and standards are defined in the following table:

Table 4-3430 SOC File Naming Conventions and Descriptions

File Name qualifiers DescriptionInstrument ID NNNN is a 4 ASCII characters used to represent the specific instrument;

where NNN = >= CRAT for CRaTER Instrument data files= DLRE for the DLRE instrument files= LAMP for the LAMP instrument files= LEND for the LEND instrument files= LOLA for LOLA instrument files= LROC for the LROC instrument files= MINI for the Mini-RF instrument files

YYYYDDD YYYYDDD is a 7 character year and Day of year designations, such asYYYY => 4 character year designator (2008 – 2013)DDD => 3 character day of year designator (001 – 366)

serial counter NNNNNNN is a seven character sequentially incrementing number used touniquely identify the files; (0000001 – 9999999)

file name extension 2 or 3 character designation used to identify the file type= .hk for instrument housekeeping data files= .sci for raw science data files

The following sections provide the information related to the general set of MOC-generatedproducts, which are used by all Science Centers.

pgf

Highlight

CRaTER-specific S/C H/K


4-164



The first 64 bytes in the file are the file header, which contains basic meta-data that identifies thefile creation information for all data files. This meta-data is described in more detail in Section4.6.4 of T&C Handbook.The on-board LRO Flight SW creates all science data files based one of three methods: file size(1 MB); an identified time duration (e.g., hour or orbit) or using both file limit concepts.The following table identifies the MOC-generated products, the contents and a sample file nameconcept.

Product ID Contents File NameMOC-3 CRaTER – Spacecraft Housekeeping Data File CRAT_SCHK_YYYYDDD_NNNNNNN.hk

MOC-8 DLRE – Spacecraft Housekeeping Data File DLRE_SCHK_YYYYDDD_NNNNNNN.hk

MOC-12 LAMP – Spacecraft Housekeeping Data File LAMP_SCHK_YYYYDDD_NNNNNNN.hk

MOC-16 LEND – Spacecraft Housekeeping Data File LEND_SCHK_YYYYDDD_NNNNNNN.hk

MOC-20 LOLA – Spacecraft Housekeeping Data File LOLA_SCHK_YYYYDDD_NNNNNNN.hk

MOC-25 LROC – Spacecraft Housekeeping Data File LROC_SCHK_YYYYDDD_NNNNNNN.hk

MOC-28 Mini-RF – Spacecraft Housekeeping Data File MINI_SCHK_YYYYDDD_NNNNNNN.hk

These filenames are consistent with the standards defined by the LRO FSW User’s Guide(CCSDS File Data Protocol Task User's Guide).The Instrument – Spacecraft Housekeeping Data File is the collection of requested APIDs andcontains the associated telemetry mnemonics in binary form. The MOC creates these files basedon the SOC-requested APID; the MOC will document this information using the correspondingSOC Operations Agreement.Since these files are a binary representation of the data, there is no sample product provided inAppendix B.4.5.1.10.4 Accuracy and CompletenessSince the data within the files are a binary representation of telemetry or image data, the inherentaccuracy is identified by the associated telemetry mnemonics contained within the file. The usercan reference the T&C Formats Handbook for this information. The required completeness is100-percent fidelity of received data.4.5.1.11 Instrument Housekeeping Data Files4.5.1.11.1 Product DescriptionThis file contains the stored instrument telemetry data.4.5.1.11.2 Support DurationSupport will be provided through all mission phases.4.5.1.11.3 Format

pgf

Highlight

CRaTER instrument H/K


4-165



The Instrument Housekeeping Data File consists of the complete set of instrument telemetryvalues. The following file-naming convention is used for files transmitted from the LRO MOC.The filename is consistent with the standards defined by the LRO FSW User’s Guide (CCSDSFile Data Protocol Task User's Guide); the file name can be up to 40 characters in length,contains the complete directory path information, and includes the file extension.The following table identifies the MOC-generated products, the contents and a sample file nameconcept.

Product ID Contents File NameMOC-4 CRaTER Housekeeping Data File CRAT_YYYYDDD_NNNNNNN.hk

MOC-9 DLRE Housekeeping Data File DLRE_YYYYDDD_NNNNNNN.hk

MOC-13 LAMP Housekeeping Data File LAMP_YYYYDDD_NNNNNNN.hk

MOC-17 LEND Housekeeping Data File LEND_YYYYDDD_NNNNNNN.hk

MOC-21 LOLA Housekeeping Data File LOLA_YYYYDDD_NNNNNNN.hk

MOC-26 LROC Housekeeping Data File LROC_YYYYDDD_NNNNNNN.hk

MOC-29 Mini-RF Housekeeping Data File MINI_YYYYDDD_NNNNNNN.hk

The file name conventions for these instrument Housekeeping files are previously listed at thebeginning of the section in . These Housekeeping Data Files are a collection of requested APIDsand contains the associated telemetry mnemonics in binary form. The MOC creates these filesbased on the SOC-requested APID; the MOC will document this information using thecorresponding SOC Operations Agreement.

Since these files are a binary representation of the data, there is no sample product provided inAppendix B.4.5.1.11.4 Accuracy and CompletenessSince the data within the files are a binary representation of telemetry or image data, the inherentaccuracy is identified by the associated telemetry mnemonics contained within the file. The usercan reference the T&C Formats Handbook for this information. The required completeness is100-percent fidelity of received data.

4.5.1.12 Instrument Raw Measurement Data Files4.5.1.12.1 Product DescriptionThis file contains the raw measurement data files after CFDP processing. The Instrument RawMeasurement Data Files are a collection of image data files or collected science measurementtelemetry data in a binary form as noted in the Instrument ICD. The MOC will electronicallytransfer the Instrument Raw Measurement Data Files to the appropriate SOC at the completion ofthe Ka-Band pass from the WS1 station contact and receipt within the MOC.4.5.1.12.2 Support DurationThe MOC provides this support through all mission phases.

pgf

Highlight

CRaTER instrument science data


4-166



4.5.1.12.3 FormatThe Raw Measurement Data Files is a collection of requested APIDs and contains the associatedtelemetry mnemonics or an image file in a binary form. As such, there are no sample productsprovided in Appendix B.The filename is consistent with the standards defined by the LRO FSW User’s Guide (CCSDSFile Data Protocol Task User's Guide); the file name can be up to 40 characters in length,contains the complete directory path information, and includes the file extension. The generalfile name conventions for files are previous listed at the beginning of the section in .LROC controls their specific file naming convention since they provide the file name as part ofan input command load that the MOC receives and uplinks to the spacecraft. The file namingconvention still adheres to the 40 character file name limitations as previously referenced as partof the FSW Users’ Guide.For the Wide Angle Camera (WAC) and both Narrow Angle Cameras (NAC), the file nameconvention adheres to the following naming scheme, which is taken form the input commands:TTTTHHHHHHHH.ext; where

TTTT (3-4 characters) = NACL or NACR or WAC8 characters Image ID represented as a Hex ID

ext = 3 character extension; raw (sci) for raw image filesThe following table identifies the MOC-generated products, the contents and a sample file nameconcept.

ProductID

Contents File Name

MOC-5 CRaTER Raw Measurement Data File CRAT_YYYYDDD_NNNNNNN.sci

MOC-10 DLRE Raw Measurement Data File DLRE_YYYYDDD_NNNNNNN.sci

MOC-14 LAMP Raw Measurement Data File LAMP_YYYYDDD_NNNNNNN.sci

MOC-18 LEND Raw Measurement Data File LEND_YYYYDDD_NNNNNNN.sci

MOC-22 LOLA Raw Measurement Data File LOLA_YYYYDDD_NNNNNNN.sci

MOC-27

MOC-39

LROC Left Narrow Angle Camera Image Data FileLROC Right Narrow Angle Camera Image Data FileLROC Wide Angle Camera Image Data File

LROC_YYYYDDD_TTTTHHHHHHHH.sciLROC_YYYYDDD_TTTTHHHHHHHH.sciLROC_YYYYDDD_TTTTHHHHHHHH.sci

MOC-31 Mini-RF Raw Measurement Data File MINI_YYYYDDD_NNNNNNN.sci

4.5.1.12.4 Accuracy and CompletenessSince the data within the files are a binary representation of telemetry or image data, the inherentaccuracy is identified by the associated telemetry mnemonics contained within the file. The usercan reference the T&C Formats Handbook for this information. The required completeness is100-percent fidelity of received data.

pgf

Note

RFG comments: The second para ends premature...

pgf

Note

RFG comments: Although the filename is defined (by reference to the LRO FSW User's Guide) the contents are not defined. In particular, the file downlinked from the spacecraft includes an embedded 64 byte header /which is not/ part of the (binary contents of) the telemetry mnemonics.


4-167



4.5.1.13 Meta Summary Reports4.5.1.13.1 Product DescriptionThe Meta Summary Report contains a transaction id, filename (source and destination), file size,checksum, outcome (success/failure), and reason of failure if outcome was failure, filecompletion map, and start/end time. The DMS is sent this product for storage purposes only.All characters in the report are ASCII.4.5.1.13.2 Support DurationThe MOC provides the Meta Summary Report product to all the SOCs through out all missionphases.4.5.1.13.3 FormatTable 4-35Table 4-31 provides a content description of the Meta-Summary Report.

Table 4-3531 Meta-Summary Report Description

Field name Field CharacteristicsTransaction ID Identification number of the transaction.

Source Location Source of the file.

Destination Location Destination of the file.

File Size Size of file in bytes.

Checksum Checksum of data contained in file.

Outcome Success/Failure of file downlink.

Reason of failure Reason of failure if outcome was failure.

File Completion Map List of offsets in file.

Start/End Time Start/End time of file reception.

A sample file name for the first generation of this data file has the following convention:

<downlinked filename>.<file extension>

where downlinkedfilename

= Name of file that is downlinked from orbiter, name is same as theorbiter copy.

file extension = [4 characters] meta

The following table identifies the MOC-generated products, the contents and a sample file nameconcept.

Product ID Contents File NameMOC-46MOC-47

CRaTER Housekeeping Meta Summary FileCRaTER Raw Measurement Meta SummaryFile

CRAT_YYYYDDD_NNNNNNN_hk.metaCRAT_YYYYDDD_NNNNNNN_sci.meta

pgf

Highlight



4-168



MOC-47 CRaTER Raw Measurement Meta SummaryFile

CRAT_YYYYDDD_NNNNNNN_sci.meta

MOC-48MOC-49

DLRE Housekeeping Meta Summary FileDLRE Raw Measurement Meta SummaryFile

DLRE_YYYYDDD_NNNNNNN_hk. metaDLRE_YYYYDDD_NNNNNNN_sci. meta

MOC-50MOC-51

LAMP Housekeeping Meta Summary FileLAMP Raw Measurement Meta SummaryFile

LAMP_YYYYDDD_NNNNNNN_hk.metaLAMP_YYYYDDD_NNNNNNN_sci.meta

MOC-52MOC-53

LEND Housekeeping Meta Summary FileLEND Raw Measurement Meta SummaryFile

LEND_YYYYDDD_NNNNNNN_hk.metaLEND_YYYYDDD_NNNNNNN_sci.meta

MOC-54MOC-55

LOLA Housekeeping Meta Summary FileLOLA Raw Measurement Meta SummaryFile

LOLA_YYYYDDD_NNNNNNN_hk.metaLOLA_YYYYDDD_NNNNNNN_sci.meta

MOC-56MOC-57

MOC-58

LROC Housekeeping Meta Summary FileLROC Narrow Angle Camera Image MetaSummary FileLROC Wide Angle Camera Image MetaSummary File

LROC_YYYYDDD_NNNNNNN_hk.metaLROC_YYYYDDD_TTTTHHHHHHHH_sci.meta

LROC_YYYYDDD_TTTTHHHHHHHH_sci.meta

MOC-59MOC-60

Mini-RF Housekeeping Meta Summary FileMini-RF Raw Measurement Data File

MINI_YYYYDDD_NNNNNNN_hk.metaMINI_YYYYDDD_NNNNNNN_sci.meta

A sample Meta-summary Report product is listed in Appendix B, Figure B.4-31Figure B.4-6.4.5.1.13.4 Accuracy and CompletenessThe data contained in this file is There is no specific accuracy/completeness information for thisproduct.4.5.1.14 Real-time VC0 housekeeping data4.5.1.14.1 Product DescriptionThe LRO MOC forwards real-time data to each of the science centers. The LRO MOC’stelemetry and command system (e.g., ITOS) attempts to initiate a TCP/IP socket connection witheach of the SOCs at the start of a real-time pass. In the event of a socket connection failure,ITOS attempts to reconnect up to three times. If the connection request does not work, there isno real loss of data since the real-time data will always be transferred within a subsequent VC1data stream in a latter station contact. The real-time VC0 consists of the requested APIDs (or theentire VC0 data stream). ITOS uses a 12-byte ITOS annotation header to provide basic qualitystatistics. The following figure and table provides the data layout for this 12-byte header andprovides the field descriptor information.

pgf

Note

RFG comments: This, of course, is the problem with a TCP/IP connection. It's very reliable /if a connection is made/ with 4 strikes and you're out for that pass. And there is no provided mechanism for knowing that the MOC tried and failed to make a connection. Even e-mail would probably be an adequate notification system.

pgf

Note

RFG comments: Is this 12-byte ITOS header attached to /every/ binary CCSDS packet? Before or after the packet to which it applies? It certainly doesn't have a decent set of bits on which to synchronize the socket read process. And why are we doing this? The real-time data is only quick-look, not used for any subsequent processing. (And the quality data can't be that important; it's missing from the subsequent files transferred to the SOC containing the same data!) The cost is that you need a separate software pipeline since the format isn't the same as that given in the files.

pgf

Highlight

CRaTER instrument R/T H/K


4-169



vn2

scid8

vc6

rs3

?1

t_fmts4

flags8

fill16

gnd_time48

Word 0 Word 1 Word 2

enab err corr

pkthdrerr

dirpktseqerr

crcerr

crcena

incpkterr

vcseqerr

frmhdrerr

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4,Byte 5

Bytes 6 .. 11

Word 3

Word 4

Word 5

Figure 4-43 ITOS Annotation Header LayoutThe fields, represented within this figure are defined with the following table:

Table 4-3632 ITOS Annotation Header Field Definitions

Field Word Bit(s) Descriptionframe version 0 0-1 Version field from CCSDS transfer frame hdr.

frame s/c ID 0 2-9 Spacecraft ID from CCSDS transfer frame hdr.

frame VC ID 0 10-15 Virtual channel ID from CCSDS transfer frame hdr.

Reed-Solomon enabled 1 0 If set, Reed-Solomon error detection and correction enabled.

Reed-Solomon error 1 1 If set, uncorrectable Reed-Solomon error(s) encountered.

Reed-Solomon corrected 1 2 If set, the Reed-Solomon code corrected one or more errors.

reserved 1 3

time format 1 4-7 Defines time code format; list of values are:‘0’ = none‘1’ = PB1 code‘2 – 3’ = reserved‘4’ = PB4 code‘5 – 7’ = reserved‘8’ = relative TIME42, a time in CCSDS Unsegmented Code(CUC)‘9’ = absolute TIME42, a date in CUC, default for annotationheaders created by ITOS’10 – 15’ = reserved

packet header error 1 8 If set, packet header extracted from frame with uncorrectableerror.


4-170



Field Word Bit(s) Descriptiondata direction reversed 1 9 If set, data received in reverse bit order.

packet sequence error 1 10 If set, this packet's sequence count is not the successor or theprevious packet with the same application ID on the same VC.

frame error 1 11 If set, uncorrectable error detected in one or more frames fromwhich this packet was extracted.

frame error enabled 1 12 if set, frame error checking was enabled.

incomplete packet 1 13 If set, packet is incomplete, and filled to it's indicated lengthbeginning at `fill location'.

VC sequence error 1 14 If set, a transfer frame from which this packet was extracted wasnot the successor of the previous frame on the same virtualchannel.

frame header error 1 15 A frame from which this packet was extracted had an incorrectversion or spacecraft ID.

fill location 2 0-15 Byte offset from the end of the packet primary header of packetfill data, if `incomplete packet' is set.

ground received time 3-5 0-15 Ground received time extracted from frame wrappers in formatdefined by `time format' above.

The following table identifies the MOC-generated real-time data products, which the LRO MOCsends to the various SOCs. Since these are real-time socket connections, there are no associatedfile names.

Product ID ContentsMOC-6 CRaTER Real-time VC0 Housekeeping Data

MOC-11 DLRE Real-time VC0 Housekeeping Data

MOC-15 LAMP Real-time VC0 Housekeeping Data

MOC-19 LEND Real-time VC0 Housekeeping Data

MOC-23 LOLA Real-time VC0 Housekeeping Data

MOC-24 LROC Real-time VC0 Housekeeping Data

MOC-32 Mini-RF Real-time VC0 Housekeeping Data

4.5.1.14.2 Support DurationThe LRO MOC provides this real-time data connectivity support through all mission phases.4.5.1.14.3 FormatThe Real-time VC0 housekeeping data consists of the set of telemetry mnemonics from the SOCrequested list of APIDs; the SOC identifies which specific VC0 APIDS or the complete VC0data stream it wishes to receive in the real-time socket connection.

pgf

Note

We (CRaTER SOC) have formally requested that R/T VC0 housekeeping data be made available for transfer to the CRaTER SOC via SCP/push should the TCP contact from MOC to SOC fail at a time when CRaTER is experiencing an anomaly and VC0 data are critical.


4-171



The Real-time VC0 housekeeping data is a collection of APIDs and contains the associatedtelemetry mnemonics in a binary form. As such, there is no sample product provided inAppendix B.4.5.1.14.4 Accuracy and CompletenessSince this data interface consists of binary telemetry data, the inherent accuracy is identified bythe associated telemetry mnemonics. The user can reference the T&C Formats Handbook forthis information. The required completeness is 100-percent fidelity of received data.

4.5.1.15 (MOC-30) Mini-RF Operations Opportunity4.5.1.15.1 Product DescriptionThis file contains potential targets of operations opportunity (time periods) for which the Mini-RF instrument could be commanded on to take science measurements.4.5.1.15.2 Support DurationSupport will be provided through all mission phases.4.5.1.15.3 FormatThe Mini-RF Operations Opportunity is an ASCII formatted file that contains selected timeranges in which the Mini-RF instrument could be command on to take sits science data. The fileconsists of a set of times (start, stop) when Mini-RF can operate; the MOC will send this file on aweekly basis and it will contain information for the next week’s opportunity

The LRO MOC uses the following file-naming convention for this file. The filename consists of19 characters; it also contains a three character file extension name. There are underscores (_)between the file name fields and there is a period (.) between the file name and file extensionfields. The form of the filename is as follows:



File Designator = 7 Characters7MINITOO

YYYYDOY = [7 characters], YYYYDOY; represented in UTC format andfollowed by underscore(_);where


the day of year indicates the first day of week for which there mightbe an opportunity; (delivery is TBR of the week prior to thescheduled opportunity)



4-172




txt for text filesSample File name is MINITOO_2009015_V00.txtA sample product provided in Appendix B, Figure B.4-29Figure B.4-5.4.5.1.15.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.5.1.16 (MOC-61) PDS NAIF Dataset Archive4.5.1.16.1 Product DescriptionThis file contains the complete set of archived data products associated with each delivery thatthe MOC sends to the NAIF/PDS.4.5.1.16.2 Support DurationThe MOC will provide support through all mission phases.4.5.1.16.3 FormatThe file is a compressed file that contains a set of MOC products that correlate to a time span.For example, all files associated with a week, or a month duration.The LRO MOC uses the following file-naming convention for MOC-transmitted files. Thefilename consists of 18 characters; it also contains a three character file extension name. Thereare underscores (_) between the file name designators and there is a period (.) between the filename and file extension fields. The form of the filename is as follows



File Designator = [6 characters] to identify file (followed by underscore (_)LROPDS






arc to identify that this is an archive file


4-173



A sample LRO PDS NAIF Dataset Archive file name is LROPDS_yyyydoy_V00.txtSince this product is a compressed data product, there is no sample product provided inAppendix B.4.5.1.16.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available

4.5.1.17 (MOC-62) RTS Command Load Report4.5.1.17.1 Product DescriptionThis file contains the textual version of the relative time sequenced (RTS) uplinked commandload, which the LRO MOC sent to the LRO spacecraft.4.5.1.17.2 Support DurationThe MOC will provide support through all mission phases.4.5.1.17.3 FormatThe RTS Command Load Report consists of the complete textual set of integrated RTScommands associated with a specific RTS Sequence number. This command report defines theload; based on operations team approval and signature of the corresponding binary load. TheLRO MOC uses the following file-naming convention for MOC-transmitted files. The filenameconsists of 18 characters; it also contains a three character file extension name. There areunderscores (_) between the file name designators and there is a period (.) between the file nameand file extension fields. The form of the filename is as follows:



File Designator = [6 characters] to identify file (followed by underscore (_)LRORTS






txt for text filesA sample LRO RTS Command Load Report file name is LRORTS_yyyydoy_V00.txtA sample RTS Command Load is provided in Appendix B, Figure B.4-1Figure B.4-1.


4-174



4.5.1.17.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

(MOC-30



.

The Mini-RF Operations Opportunity is a collection of requested APIDs and contains theassociated telemetry mnemonics in binary form. As such, there is no sample product provided inAppendix B.4.5.1.11.10.4Accuracy and Completeness

Required accuracy is 100-percent fidelity of received data, which is best available.4.5.1.11.11Mini-RF Raw Measurement Data Files4.5.1.11.11.1Product Description

This file contains the raw measurement data files after CFDP processing.4.5.1.11.11.2Support Duration

Support will be provided through all mission phases.4.5.1.11.11.3Format

The Mini-RF Raw Measurement Data Files consists of the complete set of Mini-RF instrumentmeasurement telemetry as noted in the Mini-RF Instrument ICD. The MOC will electronicallytransfer the Mini-RF Raw Measurement Data Files to the Mini-RF SOC at the completion of theKa-Band pass from the WS1 S-Band station. The following file-naming convention is used forfiles transmitted from the LRO MOC. The filename is consistent with the standards defined bythe LRO FSW User’s Guide (CCSDS File Data Protocol Task User's Guide); the file name canbe up to 40 characters in length, contains the complete directory path information, and includesthe file extension. The general file name conventions for Mini-RF files are previous listed at thebeginning of the section in Table 4-29.The Mini-RF Raw Measurement Data Files is a collectionof requested APIDs and contains the associated telemetry mnemonics in binary form. As such,there is no sample product provided in Appendix B.4.5.1.11.11.4Accuracy and Completeness

Required accuracy is 100-percent fidelity of received data, which is best available.4.5.1.11.12Mini-RF Real-time VC0 HK Data4.5.1.11.12.1Product Description


4-175



This is the real-time data stream of data packets from the Mini-RF instrument and otherspacecraft housekeeping telemetry data received at the LRO MOC and forwarded in near real-time to the Mini-RF SOC for processing and monitoring.4.5.1.11.12.2Support Duration

Support will be provided through all mission phases.4.5.1.11.12.3Accuracy and Completeness

Required accuracy is 100-percent fidelity of received data, which is best available.4.5.1.11.13Mission Eclipse PredictsThe Mission Eclipse Predicts file is originally created by FDF. This file is transferred to theLRO MOC for storage archive and distribution to other LRO elements, as required. Section4.1.2.8 provides the information related to the product description, update frequency, and formatconcepts; Appendix B, Figure B.1-15 provides a representation of the sample product.4.5.1.11.14Predicted Lunar Ground Track FileThe Predicted Lunar Ground Track File is originally created by FDF. This file is transferred tothe LRO MOC for storage archive and distribution to other LRO elements, as required. Section4.1.2.15 provides the information related to the product description, update frequency, andformat concepts; Appendix B, Figure B.1-21 provides a representation of the sample product.4.5.1.11.15Definitive Lunar Ground Track FileThe Definitive Lunar Ground Track File is originally created by FDF. This file is transferred tothe LRO MOC for storage archive and distribution to other LRO elements, as required. Section4.1.2.16 provides the information related to the product description, update frequency, andformat concepts; Appendix B, Figure B.1-22 provides a representation of the sample product.4.5.1.11.16SPICE FK – Frame KernelsThe Frame kernel provides the definition of the various reference frames used on the Orbiter;this includes reference mounting angles and reference matrices for various spacecraft HW andactuators, as well as the science instrument mounting alignments. Section 4.5.1.4 provides theinformation related to the product description, update frequency, and format concepts. TheFrame Kernel is a binary file and is not shown in the Appendix B.4.5.2 PLANETARY DATA SYSTEM (PDS) Interface and ProductsThe following sections provide the summary information of the products that the LRO MOCdelivers to the Planetary Data System for storage and archival purposes. These products aredocumented in previous sections, so these sections will provide a reference back to the originalsection in which these products are discussed.

4.5.2.1 Products Delivered to PDS4.5.2.1.1 LRO Definitive SPICE SPK FileThe LRO Definitive SPICE SPK File is originally created by FDF. The LRO MOC archives thisfile and then on a regularly scheduled basis distributes the file to the PDS. Section 4.1.2.4


4-176



provides the information related to the product description, update frequency, and formatconcepts. Since this is a binary file, there is no referenced sample product in Appendix B.4.5.2.1.2 LRO Predictive SPICE SPK FileThe LRO Predictive SPICE SPK File is originally created by FDF. The LRO MOC archives thisfile and then on a regularly scheduled basis distributes the file to the PDS. Section 4.1.2.5provides the information related to the product description, update frequency, and formatconcepts. Since this is a binary file, there is no referenced sample product in Appendix B.4.5.2.1.3 SPICE Generic PCK (Planetary Constants)The SPICE Generic PCK is originally created by FDF. The LRO MOC archives this file andthen on a regularly scheduled basis distributes the file to the PDS. Section 4.1.2.17 provides theinformation related to the product description, update frequency, and format concepts. Since thisis a binary file, there is no referenced sample product in Appendix B.4.5.2.1.4 SPICE Binary PCK (High-Precision Lunar Orientation)The SPICE Binary PCK (High-Precision Lunar Orientation) is originally created by FDF. TheLRO MOC archives this file and then on a regularly scheduled basis distributes the file to thePDS. Section 4.1.2.17 provides the information related to the product description, updatefrequency, and format concepts. Since this is a binary file, there is no referenced sample productin Appendix B.4.5.2.1.5 SPICE Predicted CK (Predicted S/C Orientation)The SPICE Predicted CK (Predicted S/C Orientation) is originally created by FDF. The LROMOC archives this file and then on a regularly scheduled basis distributes the file to the PDS.Section 1.1.1.11.11.1 provides the information related to the product description, updatefrequency, and format concepts. Since this is a binary file, there is no referenced sample productin Appendix B.4.5.2.1.6 SPICE Definitive CK (Definitive S/C, HGA, SA Orientation)The SPICE Definitive CK (Definitive S/C, HGA, SA Orientation) is originally created by FDF.The LRO MOC archives this file and then on a regularly scheduled basis distributes the file tothe PDS. Section 1.1.1.11.11.1 provides the information related to the product description,update frequency, and format concepts. Since this is a binary file, there is no referenced sampleproduct in Appendix B.4.5.2.1.7 SPICE SCLK- Spacecraft Clock CorrelationThe SPICE SCLK- Spacecraft Clock Correlation is originally created by FDF. The LRO MOCarchives this file and then on a regularly scheduled basis distributes the file to the PDS. Section4.5.1.2 provides the information related to the product description, update frequency, and formatconcepts. A sample SPICE SLCK Spacecraft Clock Correlation File is provided in Appendix B,Figure B.4-2.4.5.2.1.8 SPICE FK – Frame KernelsThe SPICE FK – Frame Kernels is originally created by FDF. The LRO MOC archives this fileand then on a regularly scheduled basis distributes the file to the PDS. Section 4.5.1.4 provides


4-177



the information related to the product description, update frequency, and format concepts. Sincethis is a binary file, there is no referenced sample product in Appendix B.4.5.2.1.9 HGA/SA Fixed offset SPKThe HGA/SA Fixed offset SPK is originally created by FDF. The LRO MOC archives this fileand then on a regularly scheduled basis distributes the file to the PDS. Section 1.1.1.11.11.1provides the information related to the product description, update frequency, and formatconcepts. Since this is a binary file, there is no referenced sample product in Appendix B.4.5.2.1.10 Improved Lunar Gravity ModelThe Improved Lunar Gravity Model is originally created by the LOLA SOC. The LRO MOCarchives this file and then on a regularly scheduled basis distributes the file to the PDS. Section4.3.5.2 provides the information related to the product description, update frequency, and formatconcepts. Since this is a binary file, there is no referenced sample product in Appendix B.4.5.2.1.11 Processed LOLA Orbit Determination DataThe Processed LOLA Orbit Determination Data File is originally created by the LOLA SOC.The LRO MOC archives this file and then on a regularly scheduled basis distributes the file tothe PDS. Section 4.3.5.4 provides the information related to the product description, updatefrequency, and format concepts. Since this is a binary file, there is no referenced sample productin Appendix B.4.5.3 MOC PRODUCTS TO STATIONSThe following sections identify the interfaces sent by the LRO MOC to the various groundstations supporting the LRO mission. Nominally, these interfaces are used to transmit commandfrom the LRO MOC to the corresponding station. The command structure that the LRO MOCuses is dependant upon the station that is scheduled to be the interface for sending commands tothe LRO spacecraft. The following conventions are used by the LRO MOC to support theinterface with each of the corresponding stations:

• EOS Ground Message Header for commanding through either WS1 or USN stations• SLE Command structure for interfacing with DSN stations• TBS Command Structure for interfacing with the Space NetworkThe EOS Ground Message header is 24 bytes long and has the following data structure asidentified in Figure 4-5Figure 4-4; Table 4-37Table 4-33Table 4-32 provides a referencedefinition for the fields contained within the EOS Ground message Header. After the 24-byteheader, the commands are formatted into the variable length Command Length TransmissionUnits (CLTUs).

Ground Message Header

Message Type(1)

Fill/Spare

(1)

Destination Id(1)

Source Id(1)

Message GMT(7)

Seq. #(2)

Message Length

(2)

CLTU(variable )SC ID

(2)

SW Ver. #

(2)

Fill/Spare

(1)

Fill/Spare

(4)

Figure 4-54 EOS Ground Message Header


4-178



Table 4-373332 EOS Ground Message Header Definitions

Name Format Size(bytes)

Value Data Characteristics

MessageType orTest MessageType

Unsignedinteger

1 03 Range for message type = 0-127Range for test message type = 128-255(Test message type equals message type plus 128.) Thisfield uniquely identifies the message and indicates tothe receiver what message format to expect and process.

Fill/Spare(reserved forfuture use)

Unsignedinteger

1 0 Value = 0

SourceIdentification

Unsignedinteger

1 0 Range = 0-255; not used for LRO

DestinationIdentification

Unsignedinteger

1 0 Range = 0-255; not used for LRO


Unsignedinteger

1 0 Value = 0

MessageGenerationTime andDate

NASA PB5code format

7 variable Contains Greenwich mean time (GMT)

Spacecraft ID Unsignedinteger

2 0xA5 LRO will use the CCSDS uplink SCID value of A5

MessageSequenceNumber

Unsignedinteger

2 0 Range = 0-65,535; one-up counter that wraps around,on reaching the largest value, to smallest value. Thisnumber is one-up per source identification and isassigned by the originator. This field is not used forLRO.

SoftwareVersionNumber

Unsignedinteger

2 0 Range = 0-255 (first byte identifies major EDOSrelease; second byte represents version of major release,either initial version or an update) This field is not usedfor LRO.

MessageLength

Unsignedinteger

2 variable Range = 24-65,535 (number of bytes in message); ForLRO, this value includes the length of the LRO groundmessage header, as well as the attached CLTU


Unsignedinteger

4 0 Value = 0

For the DSN, the ground generated CLTUs are formatted into a Space Link Extension (SLE)Forward Command Link Transmission Unit (F-CLTU). Figure 4-6Figure 4-5 provides a


4-179



representation of the ground message header; Table 4-38Table 4-34Table 4-33 provides the fielddefinitions used for the F-CLTU SLE header fields.The SLE Command structure is used to interface with the 34-meter DSN subnet that is used tosupport the LRO mission.Figure 4-2 is TBS

Figure 4-65 SLE F-CLTU Command StructureThe fields, represented within this figure are defined with the following table:Table 4-33 is TBS

Table 4-383433 SLE Command Structure Definitions

For the Space Network, the ground generated CLTUs are formatted into a TBS structure asrepresented in Figure 4-7Figure 4-6; Table 4-38Table 4-34Table 4-33 provides the fielddefinitions used for the F-CLTU SLE header fields.The SLE Command structure is used to interface with the 34-meter DSN subnet that is used tosupport the LRO mission.Figure 4-2 is TBS

Figure 4-76 Space Network Command StructureThe fields, represented within this figure are defined with the following table:Table 4-39Table 4-35Table 4-34 is TBS.

Table 4-393534 Space Network Command Structure Definitions

4.5.3.1 (MOC-34) SCN Real-time Orbiter Commands (WS1 and USN)4.5.3.1.1 Product DescriptionThis product is the real-time Orbiter Commands via CLTUs (this covers both ATS/RTScommands as well as the Command File concepts to both the SCN station (WS1) and the fourcurrently allocated USN stations using the EOS Ground Message Header.4.5.3.1.2 Support DurationThis support will be provided through all mission phases.4.5.3.1.3 FormatThe SCN Real-time Orbiter Commands consists of the commands formatted into CLTUs andtransmitted to either the WS1 station or the appropriate USN station supporting the mission.

The SCN Real-time Orbiter Commands (for WS1 and USN interfaces) are sent in a binary formover a socket connection from the LRO MOC. Since this is a binary representation of the data,no sample product is listed in Appendix B.4.5.3.1.4 Accuracy and Completeness


4-180



The required accuracy is 100-percent fidelity of the MOC-delivered data. The Telemetry andCommand Formats Handbook defines each possible orbiter command mnemonic and theassociated format and identifies the possible limits; the command mnemonic accuracy is basedupon the mnemonic type.

4.5.3.2 (MOC-35) DSN Real-time Orbiter Commands4.5.3.2.1 Product DescriptionThis product is the real-time Orbiter Commands via CLTUs; this supports the ATS/RTCcommands transmitted to DSN stations using the Space Link Extension (SLE).4.5.3.2.2 Support DurationThis support will be provided through all mission phases.4.5.3.2.3 FormatThe DSN Real-time Orbiter Commands consists of the commands in CLTUs and formattedwithin the SLE wrappers. The SCN Real-time Orbiter Commands (for WS1 and USNinterfaces) are sent in a binary form over a socket connection from the LRO MOC. Since this is abinary representation of the data, no sample product is listed in Appendix B.4.5.3.2.4 Accuracy and CompletenessThe required accuracy is 100-percent fidelity of the MOC-delivered data. The Telemetry andCommand Formats Handbook defines each possible orbiter command mnemonic and theassociated format and identifies the possible limits; the command mnemonic accuracy is basedupon the mnemonic type.

4.5.3.3 (MOC-36) SN Real-time Orbiter Commands4.5.3.3.1 Product DescriptionThis product is the real-time Orbiter Commands via CLTUs that the LRO MOC would send tothe SN TDRSS assets during the Launch and early orbit mission phase.4.5.3.3.2 Support DurationThis support will be provided only during the first several hours of the L&EO mission phase.4.5.3.3.3 FormatThe SN Real-time Orbiter Commands consists of the commands in CLTUs and formatted withinthe SN wrappers. The SCN Real-time Orbiter Commands (for WS1 and USN interfaces) aresent in a binary form over a socket connection from the LRO MOC. Since this is a binaryrepresentation of the data, no sample product is listed in Appendix B.4.5.3.3.4 Accuracy and CompletenessThe required accuracy is 100-percent fidelity of the MOC-delivered data. The Telemetry andCommand Formats Handbook defines each possible orbiter command mnemonic and theassociated format and identifies the possible limits; the command mnemonic accuracy is basedupon the mnemonic type.


4-181



4.5.3.4 SCN Orbiter Commands – CFDP Structure4.5.3.4.1Product DescriptionThis product is the SCN Orbiter Commands via the CCSDS file delivery protocol, which areencapsulated in the CLTUs and sent to either the SCN station (WS1) and the four currentlyallocated USN stations using the EOS Ground Message Header.4.5.3.4.2Support DurationThis support will be provided through all mission phases.4.5.3.4.3FormatThe SCN Real-time Orbiter Commands consists of the commands formatted into CLTUs andtransmitted to either the WS1 station or the appropriate USN station supporting the mission.The SCN Real-time Orbiter Commands (for WS1 and USN interfaces) are sent in a binary formover a socket connection from the LRO MOC. Since this is a binary representation of the data,no sample product is listed in Appendix B.

4.5.3.5DSN Orbiter Commands – CFDP Structure4.5.3.5.1Product DescriptionThis product is the Orbiter Commands via the CCSDS file delivery protocol, which areencapsulated in the CLTUs and transmitted to the DSN station using the SLE wrappers.4.5.3.5.2Support DurationThis support will be provided through all mission phases.4.5.3.5.3FormatThe DSN Real-time Orbiter Commands – CFDP Structure commands in CLTUs and formattedwithin the SLE wrappers. These DSN commands are sent in a binary form over a socketconnection from the LRO MOC. Since this is a binary representation of the data, no sampleproduct is listed in Appendix B.

4.5.3.64.5.3.4 (MOC-1) SDPS CFDP Control4.5.3.6.14.5.3.4.1 Product DescriptionThis product is the CFDP Control Messages transmitted between the LRO MOC and the MUElocated at the WS1 station. Technically, this interface is really between two MOC developedcomponents (the Data Processing System). However, since the one system is physically locatedat the WS1 station, this document defines this interface as an external interface rather than justan internal interface.4.5.3.6.24.5.3.4.2 Support DurationThis support will be provided through all mission phases.4.5.3.6.34.5.3.4.3 FormatThe CFDP Control Messages consists of the regulating messages sent by the control system inthe MOC to the DPS system in the WS1 station. This message is an APID that the MOC sends


4-182



to the SDPS element; the contents of this APID are defined within the Telemetry and CommandsFormat Handbook. Since these data are referenced as APIDs (and as such, are binary data), nosample product is provided within Appendix B.4.5.3.4.4 A sample CFDP Control Messages is provided in Appendix B, Figure B.6-1.Accuracy

and CompletenessThe required accuracy is 100-percent fidelity of the MOC-delivered data. The Telemetry andCommand Formats Handbook defines the content and the associated format and identifies thepossible limits for these data; the SDPS CFDP Control accuracy is based upon the mnemonictype.

4.5.4MOC PRODUCTS to the CDDIS (for Laser Ranging Support)4.5.4.1SCN Support Schedules4.5.4.1.1Product DescriptionThis product is a copy of the SCN Station Schedules that the Ground Network Scheduling Office(GNGO) scheduled. These schedules correspond to the Strawman Schedule (generatedapproximately 3-4 weeks prior to the required week), the Forecast Schedule (generatedapproximately 2 weeks prior to the required week), and the Operational Schedule (generated bythe Thursday prior to the subsequent week.4.5.4.1.2Support DurationThis support will be provided through all mission phases.4.5.4.1.3FormatThe SCN Support Schedule follows the same format representation as identified in Section4.2.1.2. A sample SCN Station Schedule File is provided in Appendix B, Figure B.2-2.4.5.4.1.4Accuracy and PrecisionRequired accuracy is 100-percent fidelity of received data, which is best available.4.5.54.5.4 NAVIGATION AND ANCILLARY INFORMATION FACILITY (NAIF)

Interface and Products

The following sections provide the details related to the interfaces and products distributed byNASA's Navigation and Ancillary Information Facility (NAIF) for use by the LRO mission. TheNAIF is located at the Jet Propulsion Laboratory to lead the design and implementation of the"SPICE" ancillary information system. SPICE is used throughout the lifecycle of space sciencemissions to help scientists and engineers design missions, plan scientific observations, analyzescience data and conduct various engineering functions associated with flight projects. Theseproducts are generated by the NAIF and the LRO MOC will receive these files when notified andthen distribute the files to the necessary Science Operations Centers.

4.5.5.14.5.4.1 (NAIF-1) SPICE Planetary SPK4.5.5.1.14.5.4.1.1 Product Description

pgf

Note

Where are the NAIF file names defined? Will all file types be sent to all SOCs?

pgf

Highlight

NAIF data files


4-183



The SPICE Planetary SPK file provides the ephemeris information for planetary and lunar bodiesbased on a DE405 reference frame.4.5.5.1.24.5.4.1.2 Support DurationThe LRO MOC and NAIF will provide support through all mission phases.4.5.5.1.34.5.4.1.3 FormatThe SPICE Planetary SPK is a binary formatted file. As such, there is no sample productprovided in Appendix B.4.5.5.1.44.5.4.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.5.5.24.5.4.2 (NAIF-2) SPICE LSK – Leap Second4.5.5.2.14.5.4.2.1 Product DescriptionThe SPICE LSK – Leap Second File is a file that contains all of the leap second adjustments andwhen these adjustments should be used. This file supports the conversion between ephemeristime and UTC.4.5.5.2.24.5.4.2.2 Support DurationThe LRO MOC and NAIF will provide support through all mission phases.4.5.5.2.34.5.4.2.3 FormatThe SPICE LSK – Leap Second File is a binary formatted file. As such, there is no sampleproduct provided in Appendix B.4.5.5.2.44.5.4.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.5.4.3 (NAIF-3) SPICE Generic PCK (Planetary Constants)4.5.4.3.1 Product DescriptionThe SPICE Generic PCK file provides the planetary or lunar ephemeredes based upon a DE405reference frame.4.5.4.3.2 Support DurationNAIF provides the SPICE Generic PCK file is generated for any mission phases.4.5.4.3.3 FormatThe NAIF generates the SPICE Generic PCK file and it is a binary formatted file. Since this is abinary formatted file, no sample product will be shown in Appendix B.4.5.4.3.4 Accuracy and CompletenessTBR4.5.4.4 (NAIF-4) SPICE Binary (High Precision Lunar Orientation) PCK4.5.4.4.1 Product Description


4-184



The SPICE Binary PCK is the High Precision Lunar Orientation file that the NAIF generates onan as-needed frequency. This file contains the various lunar constants and other high-precisionlunar information required to support a mission orbiting the moon.4.5.4.4.2 Support DurationThe LRO MOC and NAIF will provide support through all mission phases.4.5.4.4.3 FormatThe SPICE Binary PCK File is a binary formatted file. As such, there is no sample productprovided in Appendix B.4.5.4.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.6 LAUNCH SITE (KSC) PRODUCT AND DESCRIPTIONSThis section contains the interface products generated by either the LRO MOC or the launch siteat Kennedy Space Center (KSC)This section provides the details on the interfaces between the Kennedy Space Center (the launchsite) or the launch vehicle and the LRO MOC.4.6.1 Launch Site Product Interface with the LRO MOCThis section describes the interface between KSC support facilities and the LRO MOC.4.6.1.1 (KSC-1) Real-time VC0 Orbiter Telemetry4.6.1.1.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for real-time. Thisinterface is used during pre-launch verification tests, when the orbiter and instrument suites areat KSC prior to the launch. This interface is between two ITOS systems. The one at KSC acts asthe initial interface with the orbiter and then sends the telemetry data to the ITOS located at theLRO MOC.4.6.1.1.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) andimmediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.4.6.1.1.3 FormatThe Real-time VC0 Orbiter Telemetry is a collection of APIDs and contains the associatedtelemetry mnemonics in binary form. As such, there is no sample product provided in AppendixB.4.6.1.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


4-185



4.6.1.2 (KSC-2) Real-time VC1 Orbiter Telemetry1.1.1.15.14.6.1.2.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for real-time. Thisinterface is used during pre-launch verification tests, when the orbiter and instrument suites areat KSC prior to the launch. This interface is between two ITOS systems. The one at KSC acts asthe initial interface with the orbiter and then sends the telemetry data to the ITOS located at theLRO MOC.1.1.1.15.24.6.1.2.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities to support missiontests and rehearsals.1.1.1.15.34.6.1.2.3 FormatThe Real-time VC1 Orbiter Telemetry is a collection of APIDs and contains the associatedtelemetry mnemonics in binary form. As such, there is no sample product provided in AppendixB.1.1.1.15.44.6.1.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.6.1.24.6.1.3 (KSC-3) Archived VC0 Orbiter Telemetry4.6.1.2.14.6.1.3.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for both real-time and FTPfiles. This interface is used during pre-launch verification tests, when the orbiter and instrumentsuites are at KSC prior to the launch. This interface is between two ITOS systems. The one atKSC acts as the initial interface with the orbiter and then sends the telemetry data to the ITOSlocated at the LRO MOC.4.6.1.2.24.6.1.3.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) andimmediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.4.6.1.2.34.6.1.3.3 FormatThe Archived VC0 Orbiter Telemetry is a collection of APIDs and contains the associatedtelemetry mnemonics in binary form. As such, there is no sample product provided in AppendixB.4.6.1.2.44.6.1.3.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.6.1.34.6.1.4 (KSC-4) Archived VC1 Telemetry Data4.6.1.3.14.6.1.4.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for both real-time and FTPfiles. This interface is used during pre-launch verification tests, when the orbiter and instrumentsuites are at KSC prior to the launch. This interface is between two ITOS systems. The one at


4-186



KSC acts as the initial interface with the orbiter and then sends the telemetry data to the ITOSlocated at the LRO MOC.4.6.1.3.24.6.1.4.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) andimmediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.4.6.1.3.34.6.1.4.3 FormatThe Archived VC1 Orbiter Telemetry is a collection of APIDs and contains the associatedtelemetry mnemonics in binary form. As such, there is no sample product provided in AppendixB.4.6.1.3.44.6.1.4.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.6.1.44.6.1.5 (KSC-5)Archived VC2 Telemetry Data4.6.1.4.14.6.1.5.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for both real-time and FTPfiles. This interface is used during pre-launch verification tests, when the orbiter and instrumentsuites are at KSC prior to the launch. This interface is between two ITOS systems. The one atKSC acts as the initial interface with the orbiter and then sends the telemetry data to the ITOSlocated at the LRO MOC.4.6.1.4.24.6.1.5.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) andimmediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.4.6.1.4.34.6.1.5.3 FormatThe Archived VC2 Telemetry Data File is a collection of APIDs and the associated telemetrymnemonics in binary form; as such, there is no sample product provided in Appendix B.4.6.1.4.44.6.1.5.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.6.1.54.6.1.6 (KSC-6) Archived VC3 telemetry Data4.6.1.5.14.6.1.6.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for both real-time and FTPfiles. This interface is used during pre-launch verification tests, when the orbiter and instrumentsuites are at KSC prior to the launch. This interface is between two ITOS systems. The one atKSC acts as the initial interface with the orbiter and then sends the telemetry data to the ITOSlocated at the LRO MOC.4.6.1.5.24.6.1.6.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) andimmediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.


4-187



4.6.1.5.34.6.1.6.3 FormatThe Archived VC3 Orbiter Telemetry is a collection of APIDs and the associated telemetrymnemonics in binary form; as such, there is no sample product provided in Appendix B.4.6.1.5.44.6.1.6.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.4.6.1.64.6.1.7 (LV-1) Launch Vehicle Post Separation Vector4.6.1.6.14.6.1.7.1 Product DescriptionThis information is the Post-separation vector from the launch vehicle provider. This vector isnominally transmitted via a fax to the GSFC flight dynamic’s facility. This interface is usedpost-launch and occurs several minutes after the actual separation of LRO from the launchvehicle.4.6.1.6.24.6.1.7.2 Support DurationThe Launch site Archived VC3 telemetry data File is valid only during pre-launch supportactivities (test, rehearsals).4.6.1.6.34.6.1.7.3 FormatThe post-separation vector is delivered via fax; this is a hard-copy format. A sample LaunchVehicle Post Separation Vector file is provided as a reference in Appendix B, Figure B.5-2FigureB.5-9Figure B.5-24.6.1.6.44.6.1.7.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.

4.6.2 LRO MOC Product Interface with the Launch SiteThis section describes the interface between the LRO MOC and KSC support facilities. Theseinterfaces are used in both a pre-launch and post-launch configuration.4.6.2.1 (MOC-38) Telemetry to KSC4.6.2.1.1 Product DescriptionThe interface is used for post launch data flows between the MOC and the launch site at theKennedy Space Center. This interface is between two ITOS systems. The ITOS located at theLRO MOC receives the post-launch telemetry data via the orbiter and transmits the post-launchtelemetry data to the ITOS system located at KSC.4.6.2.1.2 Support DurationThis KSC interface provides support through from approximately L-6 months to L+5days.4.6.2.1.3 FormatThis interface is a collection of requested APIDs and contains the associated telemetrymnemonics in binary form. As such, there is no sample product provided in Appendix B.4.6.2.1.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


4-188



4.6.2.2 (MOC-37) Commands to KSC4.6.2.2.1 Product DescriptionThis interface is used for testing and mission rehearsals and provides the conduit for sendingcommands to the LRO spacecraft prior to launch. This interface is between two ITOS systems.The ITOS located at the LRO MOC generates the commands and transmits the commands to theITOS system located at KSC.4.6.2.2.2 Support DurationThis interface is used during the pre-launch mission phase when the spacecraft and orbiter are atthe Kennedy Space Center prior to launch; this normally occurs from L-6 months up to L-2+5days.4.6.2.2.3 FormatThis interface is a collection of real-time command within a CLTU data structure and containsthe associated command mnemonics in binary form. As such, there is no sample productprovided in Appendix B.4.6.2.2.4 Accuracy and CompletenessRequired accuracy is 100-percent fidelity of received data, which is best available.


A-1



A Appendix – Abbreviations and AcronymsAbbreviation/

Acronym DEFINITIONAcq. AcquisitionACS Attitude Control SystemAGSD Attitude DeterminationGround SystemAETD Applied Engineering and Technology DirectorateAOS Advanced Orbiting Systems

Acquisition of SignalAPID Application Identification

application process identifierAPL Applied Physics LaboratoryASCII American Standard Code for Information InterchangeASE airborne support equipmentATS Absolute Time SequenceATS absolute time sequenceAUI attachment unit interfacebMOC backup Mission Operations CenterBps bytes per secondC&DH Command & Data HandlingCCB Configuration Control BoardCCL Closed-Circuit LoopCCR configuration change requestCCSDS Consultative Committee for Space Data SystemsCCTV Closed-Circuit TelevisionCFDP CCSDS File Delivery ProtocolCLCW Command Link Control WordCLTU command link transmission unitCM Configuration ManagementCMD CommandCMO Configuration Management OfficeCNE Center Network EnvironmentCOP Command Operating ProceduresCOTS commercial off the shelfCRaTER Cosmic Ray Telescope for Effects of RadiationCRC Cyclic Redundancy CheckDARPA Defense Advanced Research Projects AgencyDCN Document Change NoticeDDD DSN Data DeliveryDMR Detailed Mission Requirements


A-2



Abbreviation/Acronym DEFINITION

DPS Data Processing SystemDSN Deep Space NetworkDTAS Data Trending and Analysis SystemEIRP Effective Isotropic Radiated PowerEELV Evolved Expendable Launch VehicleEOM End of MissionFCS Front-End Communications SystemFD Flight DynamicsFDAB Flight Dynamics Analysis BranchFDF Flight Dynamics FacilityFDSS Flight Dynamics Support SystemFDSS Flight Dynamics Support SystemFEP front-end processorFMEA Failure Mode and Effect AnalysisFOP Flight Operations PlanFSW Flight SoftwareFSMF Flight Software Maintenance FacilityFSWM Flight Software MaintenanceFTP File Transfer ProtocolGMT Greenwich Mean TimeGN&C Guidance Navigation and ControlGOTS Government off the shelfGS Ground SystemGSE Ground Support EquipmentGSFC Goddard Space Flight CenterHGA High Gain AntennaI&T Integration and TestICD Interface Control DocumentID IdentificationIEEE Institute of Electrical and Electronics EngineersIGSE instrument ground support equipmentIIRV improved interrange vectorIONet IP Operational NetworkIP Internet ProtocolIPTX IP Transition NetworkIRIG Inter Range Instrumentation GroupISDN Integrated Services Digital NetworkISO International Organization for StandardizationISP FDF related term for thrusters


A-3




ITOS Integrated Test and Operations SystemJPL Jet Propulsion Laboratorykbps kilobits per secondkm kilometerKSC Kennedy Space CenterL&EO Launch and Early OrbitLAMP Lyman-Alpha Mapping ProjectLAN local area networkLEND Lunar Exploration Neutron DetectorLOI Lunar Orbit InsertionLOLA Lunar Orbiter Laser AltimeterLOS loss of signalLPRP Lunar Precursor and Robotic ProgramLRO Lunar Reconnaissance OrbiterLROC Lunar Reconnaissance Orbiter CameraLSB least significant bitMA multiple accessMb megabitsMB megabytesMC Mission CriticalMCC Mid Course CorrectionMCO Mission Concept of OperationsMCS master channel sequenceMMFD Multi-Mission Flight DynamicsMOC Mission Operations CenterMOT Mission Operations TeamMPS Mission Planning SystemMPS Mission Planning SystemMRD Mission Requirements DocumentMSB most significant bitNAC Narrow Angle CameraNAK negative acknowledgementNASA National Aeronautics and Space AdministrationNascom NASA CommunicationsNISN NASA Integrated Services NetworkNMC Network Management CenterNPD NASA Policy DirectiveOBC onboard computerOD Orbit Determination


A-4




OEM Orbital Ephemeris MessagePA principal axis – (a reference frame for a set of FDF generated products)PB playbackPDB project databasePDS Planetary Data SystemPDU packet data unitPI principal investigatorPOCC Payload Operations Control Centerpsk phase shift keyPTP programmable telemetry processorRF Radio FrequencyRGS Remote Ground StationsRS Reed-SolomonRTMC Real-Time Mission CriticalRTS Relative Time SequenceS/C SpacecraftSA Solar ArraySBC Single Board ComputerSCID spacecraft identifierSCN Space Communications NetworkSCP Stored Command Processorsecure copySCS Sequence and Compression SystemSDVF Software Development and Validation FacilitySIP Standard IP (replaces NI)SK Station-KeepingSOC Science Operations CenterSSR Solid State RecorderSTGT Second Tracking and Data Relay Satellite (TDRS) Ground TerminalSTOL Systems Test and Operations LanguageT&C Telemetry, & CommandTBD To Be DeterminedTBR To Be ResolvedTBS To Be SuppliedTC TelecommandTCP Transmission Control ProtocolTCW Test Conductor WorkstationTLM TelemetryTT&C Tracking, Telemetry, & CommandUDP User Datagram Protocol


A-5




URL Uniform Resource LocatorUSN Universal Space NetworkUTC universal time codeUTDF universal tracking data formatVC Virtual ChannelVCDU Virtual Channel Data UnitVCID virtual channel identifierVDS Voice Data SystemWAC Wide Angle CameraWAN wide area networkWS workstationWSC White Sands ComplexWSGT White Sands Ground Terminal


B-1



B Appendix B – Sample Product FormatsEach subsystem will have individual sections in which this document will document a sampleproduct, which can be used as a representative format for the specified product.B.1 Sample FDF ProductsB.1.1 (FDF-6) SCN INP-2 Acquisition Data Sample

Figure B.1-87 Sample SCN INP-2 Acquisition Data FileB.1.2 (FDF-6) SCN OEM Acquisition Data Sample

Figure B.1-98 Sample SCN OEM Acquisition Data File


B-2



B.1.2B.1.3 (FDF-7) LR Prediction Data Sample

Figure B.1-1098 Sample Laser Ranging Prediction Data File


B-3



B.1.3B.1.4 (FDF-8) Space Network Acquisition Data Sample

Figure B.1-11109 Sample Space Network Acquisition Data File


B-4



B.1.4B.1.5 (FDF-9) and (FDF-10) Ground Station View Period Predicts Data Sample

Figure B.1-121110 Sample Ground Station View Period Predicts Data File


B-5



B.1.5B.1.6 (FDF-3) LRO Beta Angle Predict File Sample17-05-2006 17:51:59

Beta Angle and Quadrant (1-4) for Satellite-0059.

YYYYDDD.HHMMSS Beta Angle (Deg) Quadrant============== ================ ========2009015.000000 56.30 22009015.060000 56.04 22009015.120000 55.80 22009015.180000 55.54 22009016.000000 55.29 22009016.060000 55.02 22009016.120000 54.73 22009016.180000 54.44 22009017.000000 54.15 22009017.060000 53.88 22009017.120000 53.62 22009017.180000 53.37 22009018.000000 53.13 22009018.060000 52.90 22009018.120000 52.69 22009018.180000 52.46 22009019.000000 52.22 22009019.060000 51.95 22009019.120000 51.67 22009019.180000 51.38 22009020.000000 51.07 22009020.060000 50.76 22009020.120000 50.44 22009020.180000 50.11 22009021.000000 49.79 22009021.060000 49.47 22009021.120000 49.17 22009021.180000 48.87 22009022.000000 48.59 22009022.060000 48.31 22009022.120000 48.04 22009022.180000 47.77 22009023.000000 47.51 2

Figure B.1-131211 Sample LRO Beta Angle Predict File


B-6



B.1.6B.1.7 (FDF-4) LRO Definitive Ephemeris File Sample

Figure B.1-141312 Sample LRO Definitive Ephemeris File


B-7



B.1.7B.1.8 (FDF-13) Lunar Orbit Ascending and Descending Node Predicts Sample

Figure B.1-151413 Sample Lunar Orbit Ascending and Descending Node PredictsFile


B-8



B.1.8B.1.9 (FDF-14) Lunar Orbit Terminator Crossing Predicts Sample

Figure B.1-161514 Sample Lunar Orbit Terminator Crossing Predicts Data File


B-9



B.1.9B.1.10 (FDF-15) Mission Eclipse Predicts Data Sample

Figure B.1-171615 Sample Mission Eclipse Predicts Data File


B-10



B.1.10B.1.11 (FDF-16) Lunar Ephemeris Data Sample

Figure B.1-181716 Sample Lunar Ephemeris Data File


B-11



B.1.11B.1.12 (FDF-17) Orbiter Thruster Maneuver Plans Data Sample

Figure B.1-191817 Sample Orbiter Thruster Maneuver Plans Data File


B-12



B.1.12B.1.13 (FDF-19) Orbiter Post Maneuver Report Data Sample

Figure B.1-201918 Sample Orbiter Post Maneuver Report Data File


B-13



B.1.13B.1.14 (FDF-18) Post Separation Report Data Sample

Figure B.1-212019 Sample Post Separation Report Data File


B-14



B.1.14B.1.15 (FDF-20) Predicted LRO Ephemeris File Sample

Figure B.1-222120 Sample Predicted LRO Ephemeris File


B-15



B.1.15B.1.16 (FDF-21) Predicted Lunar Ground Track File Sample

Figure B.1-232221 Sample Predicted Lunar Ground Track File


B-16



B.1.16B.1.17 (FDF-22) Definitive Lunar Ground Track File Sample

Figure B.1-242322 Sample Definitive Lunar Ground Track File


B-17



B.1.18 (FDF-23) LRO State Vector Table Sample

Figure B.1-2524 Sample LRO State Vector Table Data File


B-18



B.1.19 (FDF-26) LRO Momentum Management Unload Plan Sample

Figure B.1-2625 Sample LRO Momentum Management Unload Plan File


B-19



B.1.20 (FDF-37) Solar Conjunction File Sample

Figure B.1-272623 Sample Solar Conjunction File


B-20



B.1.17 Attitude Determination Verification Report Sample

Figure B.1-24 Sample Attitude Determination Verification Report File


B-21



B.1.18Attitude Slew Plan Sample

Figure B.1-25 Sample Attitude Slew Plan File


B-22



B.1.19Gyro Calibration Data Sample

Figure B.1-26 Sample Gyro Calibration Data File


B-23



B.1.20HGA Calibration Data Sample

Figure B.1-27 Sample HGA Calibration Data File


B-24



B.1.19 LRO State Vector Table Sample

Figure B.1-28 Sample LRO State Vector Table Data File


B-25



B.1.22Star Tracker Calibration Data Sample

Figure B.1-29 Sample Star Tracker Calibration Data File


B-26



B.1.23Thruster Calibration Data Sample

Figure B.1-30 Sample Thruster Calibration Data File


B-27



B.1.20LRO Momentum Management Unload Plan Sample

Figure B.1-31 Sample LRO Momentum Management Unload Plan File


B-28



Star Tracker Occultation Report Sample

Figure B.1-32 Sample LRO Star Tracker Occultation Report File


B-29



HGA/SA Fixed Offset CK Sample

Figure B.1-33 Sample HGA/SA Fixed offset CK File


B-30



B.1.25Star Tracker Occultation Report Sample

Figure B.1-3130 Sample LRO Star Tracker Occultation Report File


B-31



B.2 Space Communications Data ProductsB.2.1 (GNSO-1) Station Support Schedules Sample

Figure B.2-1 Sample Station Support Schedules File


B-32



B.2.2 (GNSO-2) Station Support Schedules Report Sample

Figure B.2-2 Sample Station Support Schedule Report File


B-33



B.2.3 (WS1-5) Station Tracking Data Sample

Figure B.2-33 Sample Station Tracking Data File


B-34



B.2.4 SCN Station Status Packets Sample

Figure B.2-4 Sample SCN Station Status Packets


B-35



B.2.5B.2.4 (WS1-2) and (USN-2) WS1/USN Weather Data SampleThe following sample is valid for both the WS1 station and any of the USN stations. Thefollowing example is for the USN Dongara, Australia station.

20061026 299 USPS11:23 22.7 1023.4 074 4.211:28 22.7 1023.4 074 4.211:33 22.7 1023.4 074 4.211:38 22.7 1023.4 074 4.211:43 22.7 1023.4 074 4.211:48 22.7 1023.4 074 4.211:53 22.7 1023.4 074 4.211:58 22.7 1023.4 074 4.2

Figure B.2-545 Sample WS1/USN Weather Data File


B-36



B.2.6B.2.5 (WS1- 8) Ka-Band RF Receiver Data File Sample

Figure B.2-656 Sample Ka-Band RF Receiver Data File


B-37



B.2.6 (WS1-15) Post-Pass Summary Report Sample

Figure B.2-76 Sample Post-Pass Summary Report File


B-38




B-39



B.2.7 (WS1-17) CFDP Status MessagesSDPS Event Log Sample

Figure B.2-87 Sample CFDP StatusSDPS Event Log MessagesFile


B-40



B.2.8 (WS1-18) SDPS System LogWeekly Laser Ranging Schedule Sample

Figure B.2-98 Sample Weekly Laser Ranging ScheduleSDPS System Log File


B-41



B.2.9 (DSN-1) DSN Tracking Data File Sample

Figure B.2-1099 Sample DSN Tracking Data File


B-42



B.3 Science Operations Center ProductsB.3.1 CRaTER LRO Operations Activity Request SampleThe LRO Operations Activity Request is valid for the SOC-generated activity requests that anySOC can deliver to the LRO MOC. The following figure is representative of any of the ActivityRequests.

Figure B.3-1 Sample CRaTER LRO Operations Activity Request File

pgf

Highlight



B-43



B.3.2 (CRaTER-2) CRaTER Instrument Reset Timeline Sample

Figure B.3-2 CRaTER Instrument Reset Timeline

pgf

Highlight



B-44



B.3.3 DLRE Activity Request Sample

Figure B.3-3 Sample DLRE Activity Request File


B-45



B.3.4B.3.3 (DLRE-2) DLRE FSW Load SampleTable LoadDLRE,TB145,98-133:05:40:05,001,I&T,00C8,NOSWAP/SMTBLSELECT TABLEID=145, SRCZERO, DESTRAM/SMTBLLOAD OFFSET=H’0’/SMTBLCOMMIT CKENABLE, CHECKSUM=H’E0C3’;;X385F12B5 ; Timestamp;X 00 04 00 02 99 C9 42 6F 11 F6 3F EE 87 0F 74 30;X E3 A8 3F D5 14 7B 47 AE 7A E1 3F 84 A9 FC D2 F1;X 62 4D 3F 60 7E FA BC 6A 93 74 3F 58 00 00 00 00;$Date: 2006/03/21 16:07:24 $Chapter 9: Image Loads 15...X 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 9A;X 99 99 99 99 3F F1 33 32 38 3F 6B 10 3F 09 33 32;X 38 3F 6B 10 3F 09 00 0A 00 00;

Figure B.3-434 Sample DLRE FSW Load File


B-46



B.3.5 LAMP Activity Request Sample

Figure B.3-5 Sample LAMP Activity Request File


B-47



B.3.6 LAMP HV Command Sequence Sample

Figure B.3-6 Sample LAMP HV Command Sequence


B-48



B.3.7B.3.4 (LAMP-3) LAMP Instrument FSW Load SampleTable LoadLAMP,TB145,98-133:05:40:05,001,I&T,00C8,NOSWAP/SMTBLSELECT TABLEID=145, SRCZERO, DESTRAM/SMTBLLOAD OFFSET=H’0’/SMTBLCOMMIT CKENABLE, CHECKSUM=H’E0C3’;;X385F12B5 ; Timestamp;X 00 04 00 02 99 C9 42 6F 11 F6 3F EE 87 0F 74 30;X E3 A8 3F D5 14 7B 47 AE 7A E1 3F 84 A9 FC D2 F1;X 62 4D 3F 60 7E FA BC 6A 93 74 3F 58 00 00 00 00;$Date: 2006/03/21 16:07:24 $Chapter 9: Image Loads 15...X 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 9A;X 99 99 99 99 3F F1 33 32 38 3F 6B 10 3F 09 33 32;X 38 3F 6B 10 3F 09 00 0A 00 00;

Figure B.3-747 Sample LAMP Instrument FSW Load File


B-49



B.3.8LEND Activity Request Sample

Figure B.3-8 Sample LEND Activity Request File


B-50



B.3.9 LOLA Activity Request Sample

Figure B.3-9 Sample LOLA Activity Request File


B-51



B.3.10B.3.5 (LOLA-2) LOLA Improved Lunar Gravity Model Sample

Figure B.3-10510 Sample LOLA Improved Lunar Gravity Model


B-52



B.3.11B.3.6 (LOLA-3) LOLA Instrument FSW Load SampleTable LoadLOLA,TB145,98-133:05:40:05,001,I&T,00C8,NOSWAP/SMTBLSELECT TABLEID=145, SRCZERO, DESTRAM/SMTBLLOAD OFFSET=H’0’/SMTBLCOMMIT CKENABLE, CHECKSUM=H’E0C3’;;X385F12B5 ; Timestamp;X 00 04 00 02 99 C9 42 6F 11 F6 3F EE 87 0F 74 30;X E3 A8 3F D5 14 7B 47 AE 7A E1 3F 84 A9 FC D2 F1;X 62 4D 3F 60 7E FA BC 6A 93 74 3F 58 00 00 00 00;$Date: 2006/03/21 16:07:24 $Chapter 9: Image Loads 15...X 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 9A;X 99 99 99 99 3F F1 33 32 38 3F 6B 10 3F 09 33 32;X 38 3F 6B 10 3F 09 00 0A 00 00;

Figure B.3-11611 Sample LOLA Instrument FSW Load File


B-53



B.3.12 LOLA Processed OD Information Sample

Figure B.3-12 Sample LOLA Processed OD Information


B-54



B.3.13B.3.7 (LOLA-5) LOLA Target Requests Sample

Figure B.3-13713 Sample LOLA Target Requests File


B-55



LROC Instrument Initialization Command Sequence Sample

Figure B.3-1514 Sample LROC Instrument Initialization Command Sequence File


B-56



B.3.15B.3.8 (LROC-2) LROC Instrument Initialization Command Sequence Sample

Figure B.3-15815 Sample LROC Instrument Initialization Command Sequence


B-57



B.3.16B.3.9 (LROC-3) LROC Daily Command Sequence Sample

Figure B.3-16916 LROC Daily Command Sequence File


B-58



B.3.17B.3.10 (LROC-4) LROC Target Requests2009_015.032530, +5.6, 202009_015.133350, -10.3, 1502009_015.192245, +20.2, 140

Figure B.3-171017 Sample LROC Target Requests File


B-59



B.3.11 (Mini-RF-2) Mini-RF Load FilesTable LoadMini-RF,TB145,98-133:05:40:05,001,I&T,00C8,NOSWAP/SMTBLSELECT TABLEID=145, SRCZERO, DESTRAM/SMTBLLOAD OFFSET=H’0’/SMTBLCOMMIT CKENABLE, CHECKSUM=H’E0C3’;;X385F12B5 ; Timestamp;X 00 04 00 02 99 C9 42 6F 11 F6 3F EE 87 0F 74 30;X E3 A8 3F D5 14 7B 47 AE 7A E1 3F 84 A9 FC D2 F1;X 62 4D 3F 60 7E FA BC 6A 93 74 3F 58 00 00 00 00;$Date: 2006/03/21 16:07:24 $Chapter 9: Image Loads 15...X 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 9A;X 99 99 99 99 3F F1 33 32 38 3F 6B 10 3F 09 33 32;X 38 3F 6B 10 3F 09 00 0A 00 00;;

Figure B.3-181119 Sample Mini-RF Load File


B-60



B.3.19B.3.12 (Mini-RF-3) Mini-RF Command Timeline Files

Figure B.3-191220 Sample Mini-RF Command Timeline File


B-61



B.3.13 (Mini-RF-4) Mini-RF Target Requests2009_015.032530, +5.6, 202009_015.133350, -10.3, 150

2009_015.192245, +20.2, 140

Figure B.3-201321 Sample Mini-RF Target Requests File


B-62




B-63



B.4 Mission Operations Center ProductsB.4.1 (MOC-7) Daily Command Load Report Sample

Figure B.4-1 Sample Daily Command Load Report File


B-64



B.4.2 (MOC-62) RTS Command Load Report Sample

Figure B.4-1 Sample RTS Command Load Report File


B-65



B.4.2B.4.3 MOC-2) SCLK SPICE Clock Correlation File Sample


B-66




B-67



Figure B.4-2 Sample SCLK SPICE Clock Correlation File


B-68



B.4.3B.4.4 (MOC-33) SPICE Event Kernel Sample

Figure B.4-33 Sample SPICE Event Kernel


B-69



B.4.4B.4.5 (MOC-39) SPICE FK – Frame Kernel Sample

Figure B.4-44 Sample SPICE FK – Frame Kernel


B-70



B.4.5CRaTER – Spacecraft Housekeeping Data File Sample

Figure B.4-5 Sample CRaTER – Spacecraft Housekeeping Data File


B-71



B.4.6CRaTER Housekeeping Data File Sample

Figure B.4-6 Sample CRaTER Housekeeping Data File


B-72



B.4.7CRaTER Raw Measurement Data Files Sample

Figure B.4-7 CRaTER Raw Measurement Data Files


B-73



B.4.8CRaTER Realtime VC0 Housekeeping Data Sample

Figure B.4-8 Sample CRaTER Realtime VC0 Housekeeping Data


B-74



B.4.9 DLRE – Spacecraft Housekeeping Data File Sample

Figure B.4-9 Sample DLRE – Spacecraft Housekeeping Data File


B-75



B.4.10DLRE Housekeeping Data Files Sample

Figure B.4-10 Sample DLRE Housekeeping Data Files


B-76



B.4.11DLRE Raw Measurement Data File Sample

Figure B.4-11 Sample DLRE Raw Measurement Data File


B-77



B.4.12DLRE Real-time VC0 Housekeeping Data Sample

Figure B.4-12 Sample DLRE Real-time VC0 Housekeeping Data


B-78



B.4.13LAMP – Spacecraft Housekeeping Data File Sample

Figure B.4-13 Sample LAMP – Spacecraft Housekeeping Data File


B-79



B.4.14LAMP Housekeeping Data Files Sample

Figure B.4-14 Sample LAMP Housekeeping Data Files


B-80



B.4.15LAMP Raw Measurement Data Files Sample

Figure B.4-15 Sample LAMP Raw Measurement Data Files


B-81



B.4.16LAMP Real-time VC0 Housekeeping Data Sample

Figure B.4-16 Sample LAMP Real-time VC0 Housekeeping Data


B-82



B.4.17LEND – Spacecraft Housekeeping Data Files Sample

Figure B.4-17 Sample LEND – Spacecraft Housekeeping Data Files


B-83



B.4.18LEND Housekeeping Data Files Sample

Figure B.4-18 Sample LEND Housekeeping Data Files


B-84



B.4.19LEND Raw Measurement Data Files Sample

Figure B.4-19 Sample LEND Raw Measurement Data Files


B-85



B.4.20LEND Real-time VC0 Housekeeping Data Sample

Figure B.4-20 Sample LEND Real-time VC0 Housekeeping Data


B-86



B.4.21LOLA – Spacecraft Housekeeping Data Files Sample

Figure B.4-21 Sample LOLA – Spacecraft Housekeeping Data Files


B-87



B.4.22LOLA Housekeeping Data Files Sample

Figure B.4-22 Sample LOLA Housekeeping Data Files


B-88



B.4.23LOLA Raw Measurement Data Files Sample

Figure B.4-23 Sample LOLA Raw Measurement Data Files


B-89



B.4.24LROC – Spacecraft Housekeeping Data Files Sample

Figure B.4-24 Sample LROC – Spacecraft Housekeeping Data Files


B-90



B.4.25LROC Housekeeping Data Files Sample

Figure B.4-25 Sample LROC Housekeeping Data Files


B-91



B.4.26LROC Raw Measurement Data Files Sample

Figure B.4-26 Sample LROC Raw Measurement Data Files


B-92



B.4.27Mini-RF – Spacecraft Housekeeping Data Files Sample

Figure B.4-27 Sample Mini-RF – Spacecraft Housekeeping Data Files


B-93



B.4.28Mini-RF Housekeeping Data Files Sample

Figure B.4-28 Sample Mini-RF Housekeeping Data Files


B-94



B.4.29B.4.6 (MOC-30) Mini-RF Operations Opportunity Sample

Figure B.4-29529 Sample Mini- Operations Opportunity File


B-95



B.4.30Mini-RF Raw Measurement Data Files Sample

Figure B.4-30 Sample Mini-RF Raw Measurement Data Files


B-96



B.4.31B.4.7 (MOC-nn) Meta-Summary Report Post Maneuver Spacecraft Mass SampleThe Meta-Summary Report is valid for the set of science instrument housekeeping andmeasurement data products that the WS1-SDPS element delivers to the MOC and that the MOCthen distributes to the various science centers. The following figure is representative of any ofthe Meta Summary Reports.

Figure B.4-31631 Post Maneuver Spacecraft MassSample Meta-summary ReportFile


B-97



B.4.32B.4.8 (MOC-34) SCN Realtime Orbiter Commands Sample

Figure B.4-32732 Sample SCN Realtime Orbiter Commands


B-98



B.4.33 SCN Realtime Orbiter Commands – CFDP Sample

Figure B.4-33 Sample SCN Realtime Orbiter Commands – CFDP


B-99



B.4.34B.4.9 (MOC-35) DSN Realtime Orbiter Commands Sample

Figure B.4-34834 Sample DSN Realtime Orbiter Commands


B-100



B.4.35 DSN Realtime Orbiter Commands – CFDP Sample

Figure B.4-35 Sample DSN Realtime Orbiter Commands – CFDP


B-101



B.5 Sample Launch Site ProductsB.5.1Realtime Telemetry to KSC Sample

Figure B.5-1 Sample SCN Acquisition Data File


B-102



B.5.2B.5.1 (LV-1) Launch Vehicle Post Separation Vector Sample

Figure B.5-292 Sample Launch Vehicle Post Separation Vector File


B-103



B.6Sample Products to Other FacilitiesB.6.1CFDP Control Messages

Figure B.6-1 Sample CFDP Control Messages


B-104



B.6.2Weekly LRO Schedule Sample

Figure B.6-2 Sample Weekly LRO Schedule File


B-105



B.6.3Processed OD File Sample

Figure B.6-3 Sample Processed OD File


B-106



B.6.4Improved Lunar Gravity Model Sample

Figure B.6-4 Sample Improved Lunar Gravity Model File


B-107



Documents

snebulos.mit.edu...431-ICD-000049 Revision -– A Effective Date: TBD Expiration Date: TBD CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRI