Interface Control Document (ICD) for the LRO Ground … · Web viewInterface Control Document for...

431-ICD-000049Revision – Dv 3.0

Effective Date: To be added upon ReleaseExpiration Date: To be added upon Release

Robotic Lunar Exploration Program

Lunar Reconnaissance Orbiter Project

Interface Control Document for the Lunar Reconnaissance Ground System

April 07, 2006

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

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

DRAFT

Goddard Space Flight CenterGreenbelt, Maryland

National Aeronautics andSpace Administration

Interface Control Document (ICD) for the LRO Ground System 431-ICD-000049Revision - Dv 3.0

DRAFT

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 applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the LRO CM Office (CMO), along with supportive material justifying the proposed change. 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 431Goddard Space Flight CenterGreenbelt, Maryland 20771




DRAFT

Signature Page

Prepared by: Reviewed by:

_________Ralph Casasanta DateLRO Ground System EngineerCode 444

________Jim Clapsadle. DateLRO Ground System EngineerCode 444

Reviewed by:

________Richard S Saylor, Jr. DateLRO Ground System LeadCode 444

________Mark Beckman. DateLRO Flight Dynamics LeadCode 595

________Stefan Waldherr. DateJPL, Telecommunications and Mission Services Manager, Office 911

________Steve Currier DateSpace Communication NetworkGSFC/NASA, Code 453

________Mark Flanegan DateLR System EngineerGSFC/NASA, Code 556

________CRaTER SOC POC DateCRaTER SOC

_________DLRE SOC POC DateDLRE SOC

________LAMP SOC POC DateLAMP SOC

_________LEND SOC POC DateLEND SOC

________LOLA SOC POC DateLOLA SOC

________LROC SOC POC DateLROC SOC

________Mini-RF SOC POC DateMini-RF SOC

Reviewed by: Approved by:

_________Dave Everett DateLRO Mission System EngineerGSFC/NASA, Code 430

________Craig Tooley DateLRO Project ManagerGSFC/NASA, Code 431




DRAFT

LUNAR RECONNAISSANCE ORBITER PROJECT

DOCUMENT CHANGE RECORD Sheet: 1 of 1REV

LEVEL DESCRIPTION OF CHANGE APPROVEDBY

DATEAPPROVED

01 Initial Release, Released per 431-CCR-0000xx C. Tooley




DRAFT

List of TBDs/TBRs

Item No.

Location Summary Ind./Org. Due Date

1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.20.21.22.23.24.25.26.27.28.29.30.




DRAFT

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-21.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-42.1.2 LRO Mission Operations Center.........................................................................................................2-42.1.3 The Science Operations Centers..........................................................................................................2-52.1.4 Flight Dynamics Facility.....................................................................................................................2-52.1.5 Ground System Communications.........................................................................................................2-5

2.2 LRO OPERATIONAL GROUND SYSTEM.....................................................................................................2-62.2.1 ITOS-Supported Real-time Telemetry and Commanding....................................................................2-72.2.2 Data Processing System......................................................................................................................2-72.2.3 Data Management System...................................................................................................................2-82.2.4 Mission Planning System.....................................................................................................................2-82.2.5 Mission Operations Center – Attitude Determination System.............................................................2-82.2.6 Trending and Analysis System.............................................................................................................2-82.2.7 Monitoring, Notification and Reporting System..................................................................................2-8

2.3 FLIGHT DYNAMICS FACILITY...................................................................................................................2-92.4 FLIGHT OPERATIONS TEAM......................................................................................................................2-92.5 FLIGHT SOFTWARE MAINTENANCE FACILITY..........................................................................................2-92.6 LRO SPACE COMMUNICATIONS NETWORK..............................................................................................2-9

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-214.1.1 FDF Products for Network Support..................................................................................................4-22

4.1.1.1 SCN Station Acquisition Data..................................................................................................................4-224.1.1.2 DSN Site Acquisition Data.......................................................................................................................4-244.1.1.3 Laser Ranging Site Prediction Data..........................................................................................................4-24

4.1.2 FDF Products to support MOC Functions........................................................................................4-254.1.2.1 Ground Station View Period Predicts Data...............................................................................................4-254.1.2.2 LRO Beta Angle Predict File....................................................................................................................4-264.1.2.3 LRO Definitive Ephemeris File................................................................................................................4-274.1.2.4 LRO Definitive SPICE File......................................................................................................................4-294.1.2.5 LRO Predictive SPICE File......................................................................................................................4-294.1.2.6 Lunar Orbit Ascending and Descending Node Predicts...........................................................................4-304.1.2.7 Lunar Orbit Terminator Crossing Predicts................................................................................................4-314.1.2.8 Mission Eclipse Predicts...........................................................................................................................4-324.1.2.9 Lunar Ephemeris.......................................................................................................................................4-334.1.2.10 Orbiter Thruster Maneuver Plans..............................................................................................................4-344.1.2.11 Orbiter to Earth Range Predicts................................................................................................................4-35

ii




DRAFT

4.1.2.12 Orbiter Post Maneuver Report..................................................................................................................4-364.1.2.13 Post Separation Report..............................................................................................................................4-384.1.2.14 Predicted LRO Ephemeris File.................................................................................................................4-414.1.2.15 Predicted Lunar Ground Track File..........................................................................................................4-424.1.2.16 Definitive Lunar Ground Track File.........................................................................................................4-43

4.1.3 FDF MOC/ADS Products..................................................................................................................4-454.1.3.1 Attitude Determination Verification Report.............................................................................................4-464.1.3.2 Attitude Slew Plans...................................................................................................................................4-464.1.3.3 Gyro Calibration Data...............................................................................................................................4-474.1.3.4 HGA Calibration Data..............................................................................................................................4-484.1.3.5 LRO State Vector Table............................................................................................................................4-494.1.3.6 Star Tracker Calibration Data...................................................................................................................4-504.1.3.7 Thruster Calibration Data..........................................................................................................................4-504.1.3.8 LRO Momentum Management Unload Plan............................................................................................4-514.1.3.9 Star Tracker Occultation Report...............................................................................................................4-45

4.2 STATION PRODUCTS AND DESCRIPTIONS...........................................................................................4-524.2.1 Space Communication Network Product Descriptions.....................................................................4-52

4.2.1.1 Station Support Schedules........................................................................................................................4-524.2.1.2 Station Tracking Data...............................................................................................................................4-534.2.1.3 Stored Data Files (VC0 – VC3)................................................................................................................4-574.2.1.4 Real-time VC0 – VC3 Telemetry Data.....................................................................................................4-584.2.1.5 SCN Station Status Packets.......................................................................................................................4-584.2.1.6 USN Station Status Packets......................................................................................................................4-604.2.1.7 SCN Weather Data....................................................................................................................................4-614.2.1.8 Ka-Band Measurement Data Files (VC3).................................................................................................4-634.2.1.9 Ka-Band RF Receiver Data.......................................................................................................................4-634.2.1.10 CFDP Status Messages.............................................................................................................................4-644.2.1.11 Weekly Laser Ranging Schedule..............................................................................................................4-65

4.2.2 Deep Space Network Product Descriptions......................................................................................4-664.2.2.1 DSN Tracking Data...................................................................................................................................4-664.2.2.2 DSN Stored Data Files (VC0 – VC3).......................................................................................................4-674.2.2.3 Real-time VC0 – VC3 Telemetry Data.....................................................................................................4-684.2.2.4 DSN Station Status Packets......................................................................................................................4-68

4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONS..........................................4-704.3.1 CRaTER SOC Products.....................................................................................................................4-70

4.3.1.1 CRaTER Activity Request........................................................................................................................4-704.3.1.2 CRaTER Instrument Reset Timeline........................................................................................................4-72

4.3.2 DLRE SOC Products.........................................................................................................................4-734.3.2.1 DLRE Command Request.........................................................................................................................4-734.3.2.2 DLRE FSW Load......................................................................................................................................4-74

4.3.3 LAMP SOC Products.........................................................................................................................4-764.3.3.1 LAMP Command Request........................................................................................................................4-764.3.3.2 LAMP HV Command Sequence...............................................................................................................4-774.3.3.3 LAMP Instrument FSW Load...................................................................................................................4-78

4.3.4 LEND SOC Products.........................................................................................................................4-794.3.4.1 LEND Command Request........................................................................................................................4-794.3.4.2 LEND Instrument FSW Load...................................................................................................................4-81

4.3.5 LOLA SOC Products.........................................................................................................................4-824.3.5.1 LOLA Command Request........................................................................................................................4-824.3.5.2 LOLA Gravity Model or Improved Lunar Gravity Model.......................................................................4-844.3.5.3 LOLA Instrument FSW Load...................................................................................................................4-854.3.5.4 LOLA Processed OD Information............................................................................................................4-864.3.5.5 LOLA Target Requests.............................................................................................................................4-87

4.3.6 LROC SOC Products.........................................................................................................................4-884.3.6.1 LROC Instrument Initialization Command Sequence..............................................................................4-884.3.6.2 LROC Daily Command Sequence............................................................................................................4-904.3.6.3 LROC Instrument FSW Load...................................................................................................................4-91

iii




DRAFT

4.3.6.4 LROC Target Request...............................................................................................................................4-924.3.7 Mini-RF SOC Products.....................................................................................................................4-93

4.3.7.1 Mini-RF Load Files...................................................................................................................................4-944.3.7.2 Mini-RF Command Timeline....................................................................................................................4-95

4.4 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONS...............................4-964.4.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS.........................................................4-96

4.4.1.1 MOC PRODUCTS FOR CRaTER.........................................................................................................4-1004.4.1.2 MOC PRODUCTS FOR DLRE.............................................................................................................4-1084.4.1.3 MOC PRODUCTS FOR LAMP.............................................................................................................4-1164.4.1.4 MOC PRODUCTS FOR LEND.............................................................................................................4-1244.4.1.5 MOC PRODUCTS FOR LOLA.............................................................................................................4-1324.4.1.6 MOC PRODUCTS FOR LROC.............................................................................................................4-1404.4.1.7 MOC PRODUCTS FOR Mini-RF..........................................................................................................4-147

4.4.2 MOC PRODUCTS DISTRIBUTED TO PLANETARY DATA SYSTEM..........................................4-1544.4.3 MOC PRODUCTS TO STATIONS..................................................................................................4-154

4.4.3.1 SCN Realtime Orbiter Commands (SCN and USN)..............................................................................4-1544.4.3.2 SCN Orbiter Commands – CFDP Structure...........................................................................................4-1554.4.3.3 DSN Realtime Orbiter Commands.........................................................................................................4-1554.4.3.4 DSN Orbiter Commands – CFDP Structure...........................................................................................4-1554.4.3.5 CFDP Control Messages (WS1 Interface Only).....................................................................................4-1564.4.3.6 SCN Support Schedules (Laser Ranging Interface Only).......................................................................4-156

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

4.5.1.1 Telemetry from Launch Site...................................................................................................................4-1574.5.1.2 Launch Vehicle Post Separation Vector.................................................................................................4-158

4.5.2 LRO MOC Product Interface with the Launch Site.........................................................................4-1584.5.2.1 Telemetry to KSC...................................................................................................................................4-1584.5.2.2 Commands to KSC..................................................................................................................................4-159

5.0 LRO MOC INTERNAL INTERFACES..................................................................................................5-1

5.1.1 Integrated Test and Operations System Interfaces..............................................................................5-15.1.1.1 ITOS to MPS Products................................................................................................................................5-15.1.1.2 ITOS to Anomaly Notification Response and Reporting Products............................................................5-15.1.1.3 ITOS to Data Processing and Distribution Products...................................................................................5-15.1.1.4 ITOS to FlatSat Products............................................................................................................................5-1

5.1.2 Mission Planning System Interfaces....................................................................................................5-15.1.2.1 MPS to ITOS Products................................................................................................................................5-15.1.2.2 MPS to DP&DS Products...........................................................................................................................5-15.1.2.3 MPS to Anomaly Notification Response and Reporting Interface.............................................................5-15.1.2.4 MPS to Flight Operations Team Interface..................................................................................................5-2

5.1.3 MOC-FD Interfaces.............................................................................................................................5-25.1.3.1 MOC-FD to MPS Products.........................................................................................................................5-25.1.3.2 MOC-FD to FOT Products.........................................................................................................................5-25.1.3.3 MOC-FD to DP&DS Products....................................................................................................................5-25.1.3.4 MOC-FD to Anomaly Products..................................................................................................................5-3

5.1.4 Trending Interfaces..............................................................................................................................5-35.1.4.1 Trending to Data Processing and Distribution Products.............................................................................5-35.1.4.2 MPS to Anomaly Notification Response and Reporting Products.............................................................5-35.1.4.3 MPS to FOT Products.................................................................................................................................5-3

5.1.5 Data Processing and Distribution Interfaces......................................................................................5-35.1.5.1 DP&DS to MOC-FD Products....................................................................................................................5-35.1.5.2 DP&DS to Trending Products.....................................................................................................................5-35.1.5.3 DP&DS to ITOS Products..........................................................................................................................5-45.1.5.4 Data Processing and Distribution to Notification Response and Reporting Interface Products.................5-4

5.1.6 Monitoring and Anomaly System Interfaces........................................................................................5-45.1.6.1 Monitoring and Anomaly System to FOT Products...................................................................................5-4

iv




DRAFT

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 DSN Acquisition Data Sample............................................................................................................B-2B.1.3 LR Predicition Data Sample...............................................................................................................B-3B.1.4 Ground Station View Period Predicts Data Sample...........................................................................B-7B.1.5 LRO Beta Angle Predict File Sample..................................................................................................B-8B.1.6 LRO Definitive Ephemeris File Sample..............................................................................................B-9B.1.7 LRO Definitive SPICE File Sample..................................................................................................B-10B.1.8 LRO Predictive SPICE File Sample..................................................................................................B-11B.1.9 Lunar Orbit Ascending and Descending Node Predicts Sample......................................................B-12B.1.10 Lunar Orbit Terminator Crossing Predicts Sample.....................................................................B-13B.1.11 Mission Eclipse Predicts Data Sample........................................................................................B-14B.1.12 Lunar Ephemeris Data Sample....................................................................................................B-15B.1.13 Orbiter Thruster Maneuver Plans Data Sample..........................................................................B-16B.1.14 Orbiter to Earth Range Predict Data Sample..............................................................................B-17B.1.15 Post Orbiter Maneuver Report Data Sample...............................................................................B-18B.1.16 Post Separation Report Data Sample...........................................................................................B-19B.1.17 Predicted LRO Ephemeris File Sample.......................................................................................B-20B.1.18 Predicted Lunar Ground Track File Sample................................................................................B-21B.1.19 Definitive Lunar Ground Track File Sample...............................................................................B-22B.1.20 Attitude Determination Verification Report Sample....................................................................B-23B.1.21 Attitude Slew Plan Sample...........................................................................................................B-24B.1.22 Gyro Calibration Data Sample....................................................................................................B-25B.1.23 HGA Calibration Data Sample....................................................................................................B-26B.1.24 LRO State Vector Table Sample...................................................................................................B-27B.1.25 Star Tracker Calibration Data Sample........................................................................................B-28B.1.26 Thruster Calibration Data Sample...............................................................................................B-29B.1.27 LRO Momentum Management Unload Plan Sample...................................................................B-30B.1.28 Star Tracker Occultation Report Sample.....................................................................................B-31

B.2 SPACE COMMUNICATIONS DATA PRODUCTS.........................................................................................B-32B.2.1 Station Support Schedules Sample....................................................................................................B-32B.2.2 Station Tracking Data Sample..........................................................................................................B-33B.2.3 Stored Data Files (VC0 – VC3) Sample............................................................................................B-37B.2.4 Real-time VC0 – VC3Telemetry Data Sample..................................................................................B-38B.2.5 SCN Station Status Packets Sample..................................................................................................B-39B.2.6 SCN Weather Data Sample...............................................................................................................B-40B.2.7 Ka-Band Measurement Data Files (VC3) Sample............................................................................B-41B.2.8 Ka-Band RF Receiver Data File Sample..........................................................................................B-42B.2.9 CFDP Status Messages Sample........................................................................................................B-43B.2.10 Weekly Laser Ranging Schedule Sample.....................................................................................B-44B.2.11 DSN Tracking Data File Sample..................................................................................................B-45B.2.12 DSN Stored Data File Sample......................................................................................................B-46B.2.13 DSN Realtime VC Data Stream Sample.......................................................................................B-47B.2.14 DSN Station Status Packets Sample.............................................................................................B-48

B.3 SCIENCE OPERATIONS CENTER PRODUCTS............................................................................................B-49B.3.1 CRaTER Command Request Sample.................................................................................................B-49B.3.2 CRaTER Instrument Reset Timeline Sample.....................................................................................B-50B.3.3 DLRE Command Request Sample.....................................................................................................B-51B.3.4 DLRE FSW Load Sample..................................................................................................................B-52

v




DRAFT

B.3.5 LAMP Command Request Sample....................................................................................................B-53B.3.6 LAMP HV Command Sequence Sample............................................................................................B-54B.3.7 LAMP Instrument FSW Load Sample...............................................................................................B-55B.3.8 LEND Command Request Sample.....................................................................................................B-56B.3.9 LEND Instrument FSW Load Sample...............................................................................................B-57B.3.10 LOLA Command Request Sample................................................................................................B-58B.3.11 LOLA Gravity Model Sample.......................................................................................................B-59B.3.12 LOLA Instrument FSW Load Sample...........................................................................................B-60B.3.13 LOLA Processed OD Information Sample...................................................................................B-61B.3.14 LOLA Target Requests Sample....................................................................................................B-62B.3.15 LROC Instrument Initialization Command Sequence Sample.....................................................B-63B.3.16 LROC Daily Command Sequence Sample...................................................................................B-64B.3.17 LROC Target Requests.................................................................................................................B-66B.3.18 Mini-RF Load Files......................................................................................................................B-67B.3.19 Mini-RF Command Timeline Files...............................................................................................B-68

B.4 MISSION OPERATIONS CENTER PRODUCTS............................................................................................B-69B.4.1 Clock Correlation File Sample.........................................................................................................B-69B.4.2 CRaTER – Spacecraft Housekeeping Data File Sample...................................................................B-70B.4.3 CRaTER Housekeeping Data File Sample........................................................................................B-71B.4.4 CRaTER Raw Measurement Data Files Sample...............................................................................B-72B.4.5 CRaTER Realtime VC0 Housekeeping Data Sample........................................................................B-73B.4.6 Daily Command Load Sample..........................................................................................................B-74B.4.7 DLRE – Spacecraft Housekeeping Data File Sample.......................................................................B-75B.4.8 DLRE Housekeeping Data Files Sample..........................................................................................B-76B.4.9 DLRE Raw Measurement Data File Sample.....................................................................................B-77B.4.10 DLRE Real-time VC0 Housekeeping Data Sample......................................................................B-78B.4.11 LAMP – Spacecraft Housekeeping Data File Sample.................................................................B-79B.4.12 LAMP Housekeeping Data Files Sample.....................................................................................B-80B.4.13 LAMP Raw Measurement Data Files Sample..............................................................................B-81B.4.14 LAMP Real-time VC0 Housekeeping Data Sample.....................................................................B-82B.4.15 LEND – Spacecraft Housekeeping Data Files Sample................................................................B-83B.4.16 LEND Housekeeping Data Files Sample.....................................................................................B-84B.4.17 LEND Raw Measurement Data Files Sample..............................................................................B-85B.4.18 LEND Real-time VC0 Housekeeping Data Sample......................................................................B-86B.4.19 LOLA – Spacecraft Housekeeping Data Files Sample.................................................................B-87B.4.20 LOLA Housekeeping Data Files Sample......................................................................................B-88B.4.21 LOLA Raw Measurement Data Files Sample..............................................................................B-89B.4.22 LROC – Spacecraft Housekeeping Data Files Sample................................................................B-90B.4.23 LROC Housekeeping Data Files Sample.....................................................................................B-91B.4.24 LROC Raw Measurement Data Files Sample..............................................................................B-92B.4.25 Mini-RF – Spacecraft Housekeeping Data Files Sample.............................................................B-93B.4.26 Mini-RF Housekeeping Data Files Sample..................................................................................B-94B.4.27 Mini-RF Operations Opportunity Sample....................................................................................B-95B.4.28 Mini-RF Raw Measurement Data Files Sample..........................................................................B-96B.4.29 Post Maneuver Spacecraft Mass Sample.....................................................................................B-97B.4.30 Raw Attitude Data File Sample....................................................................................................B-98B.4.31 SCN Realtime Orbiter Commands Sample...................................................................................B-99B.4.32 SCN Realtime Orbiter Commands – CFDP Sample..................................................................B-100B.4.33 DSN Realtime Orbiter Commands Sample................................................................................B-101B.4.34 DSN Realtime Orbiter Commands – CFDP Sample..................................................................B-102

B.5 SAMPLE LAUNCH SITE PRODUCTS.......................................................................................................B-103B.5.1 Realtime Telemetry to KSC Sample................................................................................................B-103

vi




DRAFT

B.5.2 Launch Vehicle Post Separation Vector Sample............................................................................B-104

vii




DRAFT

LIST OF FIGURES

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

Figure 2-2 LRO Communications Architecture...........................................................................2-5

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

Figure B.1-2 Sample DSN Acquisition Data File.......................................................................B-2

Figure B.1-3 Sample Laser Ranging Prediction Data File..........................................................B-6

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

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

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

Figure B.1-7 Sample LRO Definitive SPICE File.....................................................................B-10

Figure B.1-8 Sample LRO Predictive SPICE File.....................................................................B-11

Figure B.1-9 Sample Lunar Orbit Ascending and Descending Node Predicts File..................B-12

Figure B.1-10 Sample Lunar Orbit Terminator Crossing Predicts Data File............................B-13

Figure B.1-11 Sample Mission Eclipse Predicts Data File........................................................B-14

Figure B.1-12 Sample Lunar Ephemeris Data File...................................................................B-15

Figure B.1-13 Sample Orbiter Thruster Maneuver Plans Data File..........................................B-16

Figure B.1-14 Sample Orbiter to Earth Range Predict Data File..............................................B-17

Figure B.1-15 Sample Post Orbiter Maneuver Report Data File...............................................B-18

Figure B.1-16 Sample Post Separation Report Data File..........................................................B-19

Figure B.1-17 Sample Predicted LRO Ephemeris File.............................................................B-20

Figure B.1-18 Sample Predicted Lunar Ground Track File......................................................B-21

Figure B.1-19 Sample Definitive Lunar Ground Track File.....................................................B-22

Figure B.1-20 Sample Attitude Determination Verification Report File..................................B-23

Figure B.1-21 Sample Attitude Slew Plan File.........................................................................B-24

viii




DRAFT

Figure B.1-22 Sample Gyro Calibration Data File....................................................................B-25

Figure B.1-23 Sample HGA Calibration Data File...................................................................B-26

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

Figure B.1-25 Sample Star Tracker Calibration Data File........................................................B-28

Figure B.1-26 Sample Thruster Calibration Data File...............................................................B-29

Figure B.1-27 Sample LRO Momentum Management Unload Plan File.................................B-30

Figure B.1-28 Sample LRO Star Tracker Occultation Report File...........................................B-31

Figure B.2-1 Sample Station Support Schedules File...............................................................B-32

Figure B.2-2 Sample Station Tracking Data File......................................................................B-36

Figure B.2-3 Sample Stored Data Files (VC0 – VC3)..............................................................B-37

Figure B.2-4 Sample Real-time VC0 – VC3 Telemetry Data File............................................B-38

Figure B.2-5 Sample SCN Station Status Packets.....................................................................B-39

Figure B.2-6 Sample SCN Weather Data File...........................................................................B-40

Figure B.2-7 Sample Ka-Band Measurement Data Files (VC3)...............................................B-41

Figure B.2-8 Sample Laser Ranging Transmit Information File...............................................B-42

Figure B.2-9 Sample CFDP Status Messages............................................................................B-43

Figure B.2-10 Sample Weekly Laser Ranging Schedule File...................................................B-44

Figure B.3-1 Sample CRaTER Command Request File...........................................................B-49

Figure B.3-2 CRaTER Instrument Reset Timeline....................................................................B-50

Figure B.3-3 Sample DLRE Command Request File................................................................B-51

Figure B.3-4 Sample DLRE FSW Load File.............................................................................B-52

Figure B.3-5 Sample LAMP Command Request File...............................................................B-53

Figure B.3-6 Sample LAMP HV Command Sequence.............................................................B-54

Figure B.3-7 Sample LAMP Instrument FSW Load File..........................................................B-55

Figure B.3-8 Sample LEND Command Request File...............................................................B-56

ix




DRAFT

Figure B.3-9 Sample LEND Instrument FSW Load.................................................................B-57

Figure B.3-10 Sample LOLA Command Request File.............................................................B-58

Figure B.3-11 Sample LOLA Gravity Model............................................................................B-59

Figure B.3-12 Sample LOLA Instrument FSW Load File........................................................B-60

Figure B.3-13 Sample LOLA Processed OD Information........................................................B-61

Figure B.3-14 Sample LOLA Target Requests File..................................................................B-62

Figure B.3-15 Sample LROC Instrument Initialization Command Sequence File...................B-63

Figure B.3-16 LROC Daily Command Sequence File..............................................................B-64

Figure B.3-17 Sample LROC Target Requests File..................................................................B-66

Figure B.3-18 Sample Mini-RF Load File................................................................................B-67

Figure B.3-19 Sample Mini-RF Command Timeline File.........................................................B-68

Figure B.4-1 Sample Clock Correlation File.............................................................................B-69

Figure B.4-2 Sample CRaTER – Spacecraft Housekeeping Data File......................................B-70

Figure B.4-3 Sample CRaTER Housekeeping Data File...........................................................B-71

Figure B.4-4 CRaTER Raw Measurement Data Files...............................................................B-72

Figure B.4-5 Sample CRaTER Realtime VC0 Housekeeping Data..........................................B-73

Figure B.4-6 Sample Daily Command Load File......................................................................B-74

Figure B.4-7 Sample DLRE – Spacecraft Housekeeping Data File..........................................B-75

Figure B.4-8 Sample LAMP DLRE Housekeeping Data Files.................................................B-76

Figure B.4-9 Sample DLRE Raw Measurement Data File........................................................B-77

Figure B.4-10 Sample DLRE Real-time VC0 Housekeeping Data...........................................B-78

Figure B.4-11 Sample LAMP – Spacecraft Housekeeping Data File.......................................B-79

Figure B.4-12 Sample LAMP Housekeeping Data Files...........................................................B-80

Figure B.4-13 Sample LAMP Raw Measurement Data Files...................................................B-81

Figure B.4-14 Sample LAMP Real-time VC0 Housekeeping Data..........................................B-82

x




DRAFT

Figure B.4-15 Sample LEND – Spacecraft Housekeeping Data Files......................................B-83

Figure B.4-16 Sample LEND Housekeeping Data Files...........................................................B-84

Figure B.4-17 Sample LEND Raw Measurement Data Files....................................................B-85

Figure B.4-18 Sample LEND Real-time VC0 Housekeeping Data..........................................B-86

Figure B.4-19 Sample LOLA – Spacecraft Housekeeping Data Files......................................B-87

Figure B.4-20 Sample LOLA Housekeeping Data Files...........................................................B-88

Figure B.4-21 Sample LOLA Raw Measurement Data Files....................................................B-89

Figure B.4-22 Sample LROC – Spacecraft Housekeeping Data Files......................................B-90

Figure B.4-23 Sample LROC Housekeeping Data Files...........................................................B-91

Figure B.4-24 Sample LROC Raw Measurement Data Files....................................................B-92

Figure B.4-25 Sample Mini-RF – Spacecraft Housekeeping Data Files...................................B-93

Figure B.4-26 Sample Mini-RF Housekeeping Data Files........................................................B-94

Figure B.4-27 Sample Mini- Operations Opportunity File.......................................................B-95

Figure B.4-28 Sample Mini-RF Raw Measurement Data Files................................................B-96

Figure B.4-29 Post Maneuver Spacecraft Mass File.................................................................B-97

Figure B.4-30 Sample Raw Attitude Data File..........................................................................B-98

Figure B.5-1 Sample SCN Acquisition Data File....................................................................B-103

Figure B.5-2 Sample Launch Vehicle Post Separation Vector File........................................B-104

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

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

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

Table 4-2. MOC Products Transmitted to Various LRO SOC Facilities...................................4-96

Table 4-3 Launch Site – MOC Interface Overview.................................................................4-157

xi




DRAFT

1.0 INTRODUCTION

The 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 the ground system for all mission phases. The other documents are the Lunar Reconnaissance Orbiter Detailed Mission Requirements Document (431-RQMT-000049) and the Lunar Reconnaissance 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 SCOPE

The ICD specifies the interface that the LRO ground system (GS) has both external with the Space Communications Network (SCN) and the various science centers, as well as the internal interfaces with other LRO mission operations center (MOC) elements.

1.2 DOCUMENT ORGANIZATION

The document organization provides details regarding the various ground system elements and the interfaces and products between the external LRO elements and the LRO ground system as well as the interfaces and products internal to0 the LRO ground system.

Section 2.0 contains a brief description of the mission and ground system architecture and identifies the 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 of Operations (MCO).

Section 3.0 provides the cross reference of the external products to/from the LRO MOC; it provides a mapping of DRM 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 are transferred between LRO external elements and the LRO ground system elements.

Section 5 provides the call out of the internal interfaces among the various LRO MOC elements and the associated products transferred between the various elements.

Outstanding open items within the ICD are identified as “To Be Determined” (TBD) and “To Be Resolved” (TBR). Open items are documented in the List of TBDs/TBRs section in the front of the document.

1.3 REQUIREMENTS TRACEABILITY METHODOLOGY

The ground system interfaces specified in this document are derived from the Lunar Reconnaissance Orbiter Detailed Mission Requirements Document (431-RQMT-0000049), which identified the specific instance associated with the interface description.

1



Ralph Casasanta, 03/21/06,

Add the other documents as necessary


DRAFT

1.4 APPLICABLE DOCUMENTS

The following LRO project documents apply only to the extent they are cited in this document.

431-RQMT-000174 Lunar Reconnaissance Orbiter Mission Assurance Requirements 431-RQMT-000049 Lunar Reconnaissance Orbiter Detailed Mission Requirements

Document431-HDBK-000052 Lunar Reconnaissance Orbiter Telemetry and Command Formats

Handbook431-HDBK-000053 Lunar Reconnaissance Orbiter Telemetry and Command Database

Handbook431-SPEC-000078 Lunar Reconnaissance Orbiter CCSDS File Delivery Protocol

Specification431-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 DOCUMENTS

The following NASA and GFSC documents are used as supporting and reference documents only.

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

1.6 OTHER DOCUMENTED REFERENCES

Format data concepts specifically needed to support the laser ranging sites

http://ilrs.gsfc.nasa.gov/products_formats_procedures/fullrate/fr_format_v3.html

2




Add the DSN referenced concept for the DSN Scheduling aspects.



DRAFT

2.0 GROUND SYSTEM OVERVIEW

The Lunar Reconnaissance Orbiter (LRO) is the first robotic mission of the Robotic Lunar Exploration Program (RLEP). The primary objective of the LRO mission is to conduct investigations that support future human exploration of the Moon. The launch readiness date for LRO 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 surface

The LRO instrument complement includes six instruments. Together, all six instruments allow LRO to meet the mission objectives. The following text provides an overview description of the six instruments:

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

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

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

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

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

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

1




DRAFT

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 planetary resource mapping. The mini-RF payload will operate on a non-interference basis throughout the mission.

The LRO spacecraft bus will be built at Goddard Space Flight Center (GSFC). Integration of the measurement instruments to the orbiter system as well orbiter environmental testing will be performed at GSFC.

LRO is scheduled to launch in October 2008. The orbiter will be launched aboard an evolved expendable 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 to perform a series of Lunar Orbit Insertion (LOI) maneuvers to enter into the orbiter commissioning orbit of 30x216 kilometers (km). After orbiter commissioning is complete, LRO will be maneuvered into a 50 km circular orbit.

Once LRO is in the final mission orbit, the six instruments will start to collect measurement data for the mission. Measurement data along with housekeeping (HK) data will be dumped to the LRO Ground System (GS). Once the data is on the ground, the GS is responsible for distribution of the data to the individual science operations centers (SOCs). The SOCs will receive and process the data to create level 1 data products. The LRO GS and SOCs also 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 with each phase are provided in the Lunar Reconnaissance Orbiter Mission Design Handbook (431-HDBK-000486)

2.1 GROUND SYSTEM ARCHITECTURE

The LRO GS is comprised of several main elements as shown in Figure 2-1. LRO Ground System Overview Diagram:

The LRO Space Communications Network, which consists of an S/Ka Band ground station at White Sands and various S-Band only ground stations located throughout the world. It includes the Deep Space Network for use as a contingency/emergency network and a laser ranging facility, which is used to provide improved orbit knowledge for the orbiter.

Mission Operations Center (MOC)

Flight Dynamics (FD), which supports maneuver planning, orbit determination, and attitude determination and sensor calibration processing

SOC for each instrument

2




DRAFT

Communications network which provides voice and data connectivity between each of these elements

Because of the high data volume that LRO will produce and the use of Ka-Band frequency, LRO elected to use a dedicated S/Ka ground station for primary measurement data downlink. The measurement data is collected at the ground station and rate buffered to the MOC post-pass for data processing/accountability. The MOC at GSFC will distribute the measurement files along with other mission products that are needed for processing to each of the instrument SOCs. The MOC is the focal point for all orbiter operations including health and safety monitoring. All commands to the orbiter are generated at the MOC. The SOCs support instrument operations including instrument command sequence inputs, measurement data processing, transferring measurement products to the PDS, and instrument housekeeping and performance trending.

Figure 2-1. LRO Ground System Overview Diagram

3




DRAFT

Each LRO Ground System element, as listed in Figure 2-1, is briefly described in the following subsections.

2.1.1 The LRO Space Communications Network

The LRO Space Communications Network (SCN) consists of a dedicated ground station at White Sands Complex, which is identified as White Sands One (WS1) and commercial S-Band ground stations; it uses the Jet Propulsion Laboratory (JPL)/DSN ground stations for backup/emergency support. The SCN supports the laser ranging site, which is located in Greenbelt, Maryland. The laser ranging site is used to provide definitive, improved orbit knowledge for LRO and an improved lunar gravity model.

The WS1 ground station is capable of receiving 100 megabits per second (Mbps) downlink on Ka-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 LRO requires near continuous tracking data for orbit determination, additional S-Band sites are needed. The S-Band only sites will provide real-time telemetry and commands capabilities along with tracking data. The S-Band stations could be used to dump low rate measurement files in a contingency 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 Center

The MOC will be located at GSFC. It is the main telemetry and command interface to the orbiter. 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 other required mission products. The MOC provides temporary measurement data storage until verification is received from the SOC on file delivery. The MOC will receive any required instrument command sequences from the SOCs and process them before uplink. The MOC will also distribute real-time telemetry to the SOCs.

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

Telemetry& Command System (includes functionality to support I&T GSE) Mission Planning System Trending System MOC – Attitude Determination System (MOC-ADS) Data Processing System Data Management System Monitoring and Anomaly System

4




DRAFT

2.1.3 The Science Operations Centers

The six SOCs and the Mini-RF technology demonstration operations center provide the hardware and software to support the following functions:

Instrument health and safety monitoring Instrument command sequence generation/request 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/tables

The SOCs themselves are not controlled and developed by the LRO ground system. The ground system responsibility ends with the interfaces to/from each of the SOCs

2.1.4 Flight Dynamics Facility

Flight Dynamics performs orbit determination, attitude processing and maneuver/ trajectory planning. For orbit determination, FD will receive the tracking data from the ground network and generate mission products. FD will also provide attitude verification and planning support for slews. Besides pre-mission trajectory and orbit planning, FD will also monitor and plan for trajectory maneuvers during the cruise, Lunar Orbit Insertion burns, and station-keeping maneuvers. The maneuver plans will be supplied to the MOC for execution.

2.1.5 Ground System Communications

The ground system communication network provides voice and data connectivity between each of the ground system elements. It will provide the necessary communication lines between the ground networks, MOC and SOCs.

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

<Insert Network Connectivity & Communications Architecture Diagram>

Figure 2-2 LRO Communications ArchitectureCommunication among the I&T GSE, GS elements, the various science centers, and dedicated ground station at the White Sands Complex (WSC), the JPL/DSN backup/emergency ground stations, and the commercial S-Band network is accomplished through the Nascom Division and the 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 hybrid Restricted IONet (RIONet).

5




DRAFT

The LRO MOC GS elements, including the ITOS, the Data Processing System (DPS), the Data Management System (DMS), the MOC ADS, and the Mission Planning System (MPS), are on the restricted IONet; the FDF component, located at GSFC in Building 28, resides on the closed IONet. The Trending and Analysis System (TAS), and the Monitoring and Anomaly System reside on the open IONet.

NISN supplies the IP access connection from the closed, restricted, and open IONets and to the CNE WAN; this connection is transparent to the user.

Real-time data access from the restricted IONet to the open IONet is through a socket connection using a secure applications gateway. Non real-time data access will be accomplished using FTP. The MOC elements or operations personnel will nominally use the “FTP-push” mechanism to transfer files to other GS elements and to other external SOC facilities. The elements on the open side will initiate the FTP-push of the data files and products that they create. In case of error conditions, the elements on the open side will allow the LRO operations personnel to access the data using the FTP “pull” protocol. The elements on the open side will provide an e-mail notification of a product’s availability whenever possible.

2.2 LRO OPERATIONAL GROUND SYSTEM

The LRO orbiter and spacecraft monitoring and control functions of the GS are performed within the LRO MOC by the Flight Operations Team (FOT). The ITOS GS element typically performs its functions 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 determination functions of the GS also are performed within the LRO MOC by the LRO FOT. These elements perform their functions using data from prior spacecraft passes and other sources. The products of these elements may be used during a LRO spacecraft ground contact and are located within the offline portion of the MOC. This set of GS elements that support both real-time and offline functionality are defined and identified 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 580 Section 2.2.6

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

Data Management System ITOS/DMS GOTS – GSFC 584 Section 2.2.3

Monitoring and Anomaly Attention COTS Section 2.2.7

6




DRAFT

Functional Element Component Provider Section Reference

Attitude Determination MOC-ADS 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) telemetry identified as VC0 and VC1. ITOS processes the engineering data and displays it to the FOT for monitoring the health and safety of the LRO spacecraft. ITOS processes the VC0 data and generates attitude data files for use by the MOC-ADS. ITOS archives engineering data files for later trending analysis by ITPS. ITOS performs the following real-time functions in support of the spacecraft health and safety: Receive command files from FlexPlan Performs real-time commanding using the received files from the FlexPlan Transmits real-time data packets to 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 MOC-ADS component or use in the onboard computer

(OBC) attitude verification determination and to generate new gyro calibration tables2.2.2 Data Processing System

ITOS provides the functionality of the Data Processing System (DPS); this is the primary interface to the station front end units for receiving and processing files transmitted using the CCSDS File Delivery Protocol (CFDP). The DPS is responsible for ensuring a reliable transfer of data and that the data received on the ground is in the same format in which it was stored on the spacecraft. There will be two active units, one at the station for high data rate capture and one at the MOC for low data rate capture and uplink of table and memory files. The station and MOC DPS are both setup and controlled by the ITOS system at the MOC and all commanding is coordinated and funneled through the ITOS for uplink to the spacecraft.

The station DPS will provide temporary data storage and deliver data products to the Data Management System after processing is complete for a file. The station DPS can receive the science data in any virtual channel (nominally it is commanded to be downlinked in either VC2 or VC3, but the spacecraft could be commanded to downlink the data in any VC), and performs data 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/DPS then distributes the data to the ITOS/DSM component for eventual transmission to the appropriate science team for further data analysis.

7




DRAFT

2.2.3 Data Management System

ITOS also provides the functionality for the Data Management System (DMS). This component provides the data file archiving, data file dissemination, and provides a mechanism that can be used to track the delivery of data file products, which the LRO MOC transfers to the other LRO ground segment elements, such as the Ground Networks, the SOCs and the PDS. ITOS/DMS receives 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 that the files are delivered to the correct recipient and delivered error free.

2.2.4 Mission Planning System

FlexPlan was chosen as the mission planning system; it provides the short term daily planning and the long term projected planning for mission operations. FlexPlan receives science planning information from the science centers, maneuver planning data from FDF, and spacecraft health and safety commands from the operations team. The LRO mission planner uses the FlexPlan to generate and maintain daily planning activities as well as spacecraft command files that are forwarded to the ITOS for uplink to the spacecraft.

2.2.5 Mission Operations Center – Attitude Determination System

The MOC-ADS provides the attitude determination validation and attitude sensor calibration; it is a COTS/GOTS system developed by the Flight Dynamics Branch at GSFC. It receives the on-board attitude quaternion data from the LRO spacecraft via ITOS/DMS, performs sensor calibration, applies biases and misalignment information to the data, and validates the on-board calculated attitude solutions from the spacecraft.

The MOC-ADS creates the command data for any orbiter off-nadir slews. One such example is to support the LROC instrument slews. LROC sends a file to the MOC. The MOC-ADS element receives the data file and generates a slew plan; this slew is eventually sent to MPS for ingestion and the creation of the daily command load. Also, it handles more than just LROC slews.

2.2.6 Trending and Analysis System

The Integrated Trending and Plotting System (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 mission housekeeping and engineering data to perform full data analysis and will also process the data to provide a reduced resolution data containing min/max/mean & standard deviation.

2.2.7 Monitoring, Notification and Reporting System

Attention was chosen as the Monitoring, Notification, and Reporting System. This system is resident in the LRO MOC and it provides a comprehensive solution for spacecraft and ground system monitoring. The system interfaces with all MOC ground components, monitoring system

8




DRAFT

events and software tasks. Upon recognizing anomalous events, notification and reporting procedures are in place to ensure that a proper response is received and data is accumulated to research and correct the anomalous behavior. For spacecraft supports the monitoring system creates pass summaries keep a record of all supports including commands sent; procedures executed, and specified event messages. The monitoring system compares entries in these pass log files against a predefined set of limits and checks. If an event or data value is flagged as a problem, the monitoring system issues a notification to one of a selected group of operations personnel of a spacecraft anomaly and providing an informative, textual message identifying the anomaly situation.

2.3 FLIGHT DYNAMICS FACILITY

The FDF provides the prime support for all orbit determination and generation of acquisition data. The FDF is located in Building 28 at GSFC.During all phases of the LRO mission, the FDF receives the station-tracking data, which includes two-way Doppler tracking, laser ranging data, and ranging data. FDF determines the spacecraft orbit and generates predicted and definitive spacecraft ephemeredes. The predicted ephemeris is used to provide acquisition data to all ground stations. FDF will supply the operations team with all mission planning aids.The FDF provides processing and control for all maneuvers and generates the trajectory maneuver commands for all mission phases.

2.4 FLIGHT OPERATIONS TEAM

The FOT personnel are responsible for managing the health and safety of the spacecraft following initial acquisition. They are the focal point of LRO GS operations during the life of the 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&T GSE system. It is responsible for maintaining the onboard flight software starting approximately 60 days after launch until the end of the mission. This interface is exclusively documented in LRO Program/SDVF Memorandum of Understanding (MOU) (Reference 2).2.6 LRO SPACE COMMUNICATIONS NETWORK

The LRO mission requires support from a variety of networks identified as the Space Communications Network (SCN):

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

9




Is the FOT responsible for anything H&S prior to s/c separation


DRAFT

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

3. The DSN, operated by the JPL located in Pasadena, California, maintains three stations at Goldstone, California; Madrid, Spain; and Canberra, Australia. DSN is designated for emergency/backup support for telemetry, tracking, and command interface during the initial acquisition, during any orbit maneuvers, or at any other times when a spacecraft emergency is identified.

4. Laser Ranging facility, which is located in Greenbelt, Maryland, provides one-way laser time of flight data and an improved lunar gravity model.

5. The Space Network (SN) will be used for launch support and for post separation coverage.

LRO information for the DSN-to-GS interface is provided in Reference 3. The interfaces between the USN and the LRO GS are documented in detail in References 4 and 5.

10




Need to work theses references, delete, or put in text.


DRAFT

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 comprehensive listing of all LRO external interfaces defined to date. This table reflects the product name, identifies who created the product and who uses the product, and provides a cross-reference to a DMR identifier to track where this interface product originates and who uses this interface product within 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

No. ID Product Name Source

Destination(s)

Section Reference DMR Reference

CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

1 CRaTER-1 CRaTER Activity Request CRaTER ● Section 4.3.1.1 DMR-51, DMR-218,

DMR-77, DMR-573

2 CRaTER-2 CRaTER Instrument FSW Loads CRaTER

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

3 CRaTER-3 CRaTER Instrument Reset Timeline CRaTER ● Section 4.3.1.2 DMR-51, DMR-218,

DMR-77, DMR-573

4 DLRE-1 DLRE Command Request DLRE ● Section 4.3.2.1

5 DLRE-2 DLRE FSW Loads DLRE ● Section 4.3.2.2

1




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

6 DSN-1 DSN Tracking Data DSN ● Section 4.2.2.1

7 DSN-2Archived Station Data for any Stored Virtual Channel

DSN ● Section 4.2.2.2

8 DSN-3Real-Time Telemetry for any commanded VC downlinked

DSN ● Section 4.2.2.3

9 DSN-4 DSN Status Data DSN ● Section 4.2.2.4

10 FDF-1 Attitude Determination Verification Report MOC-ADS ● Section 4.1.3.1

DMR-591

11 FDF-2 Attitude Slew Plans MOC-ADS ● Section 4.1.3.2DMR-592

12 FDF-3 Beta Angle Predicts FDF ● Section 4.1.2.2DMR-594

13 FDF-4 Definitive LRO Ephemeris File FDF ● Section 4.1.2.3

DMR-595

2




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

14 FDF-5 DSN Acquisition Data FDF ● Section 4.1.1.2DMR-596

15 FDF-6 SCN Acquisition Data FDF ● Section 4.1.1.1DMR-571

16 FDF-7 Ground Station View Period Predicts FDF ● ● Section 4.1.2.1

DMR-598

17 FDF-8 Gyro Calibration Data FDF ● Section 4.1.3.3DMR-609

18 FDF-9 HGA Calibration Data FDF ● Section 4.1.3.4DMR-564

19 FDF-10 Laser Ranging Site Prediction Data FDF ● Section 4.1.1.3

DMR-597

20 FDF-11 LRO Definitive SPICE File FDF ● Section 4.1.2.4

21 FDF-12 LRO Predictive SPICE File FDF ● Section 4.1.2.5

3




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

22 FDF-13Lunar Orbit Ascending and Descending Node Predicts

FDF ● Section 4.1.2.6DMR-599

23 FDF-14 Lunar Terminator Crossing Predicts FDF ● Section 4.1.2.7

DMR-600

24 FDF-15 Mission Eclipse Predicts FDF ● Section 4.1.2.8

DMR-601

25 FDF-16 Lunar Ephemeris FDF ● Section 4.1.2.9DMR-602

26 FDF-17 Orbiter thruster maneuver plans FDF ● Section 4.1.2.10

DMR-603

27 FDF-18 Orbiter to Earth Range Predicts FDF ● Section 4.1.2.11

DMR-604

28 FDF-19 Orbiter Post Maneuver Report FDF ● Section 4.1.2.12

DMR-605

29 FDF-20 Post-Separation Report FDF ● Section 4.1.2.13DMR-606

4




Can this be combined with some other FDF-generated products? Perhaps FDF-7, FDF-6?


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

30 FDF-21 Predicted LRO Ephemeris File FDF ● Section 4.1.2.14

DMR-607

31 FDF-22 Predicted Lunar Ground Track File FDF ● Section 4.1.2.15

DMR-608

32 FDF-23 SA Calibration Data FDF Section DELETED

33 FDF-24 LRO State Vector Table FDF ● Section 4.1.3.5

DMR-613

34 FDF-25 Star Tracker Calibration data FDF ● Section 4.1.3.6

DMR-611

35 FDF-26 Thruster Calibration Data FDF ● Section 4.1.3.7

DMR-610

36 FDF-27 (New)

Momentum Management Unload Plan

MOC - ADS ● Section 4.1.3.8DMR-593

37 FDF-28 (New)

Star Tracker Occultation Report FDF ● Section 4.1.2.17

DMR-612

5




This product is deleted based on FDF discussions with Rick Saylor


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

38 FDF-29 (New) Attitude Slew Report MOC - ADS ● Section 4.1.3.2

39 FDF-30 (New)

Definitive Lunar Ground Track File FDF ● Section 4.1.2.16

40 FDF-31 (New)

HGA/SA Fixed offset SPK FDF ● Section TBD

41 FDF-32 (New) SPK – Planet NAIF ● ● N/A N/A

42 FDF-33 (New) Generic PCK FDF/NAIF ● Section TBD

43 FDF-34 (New) Binary PCK FDF/NAIF ● Section TBD

44 FDF-35 (New) Predicted CK TBD ?? ● Section TBD

45 FDF-36 (New) Definitive CK TBD ?? ● Section TBD

46 FDF-37 (New)

SCLK – Spacecraft clock correlation file ● ● ● ● ● ● ● ● Section TBD

6




The following 9 FDF Products are not currently listed within the Section 4 set of FDF-ge3nerated products. This will be correct in the next release.


Is it possible to combine this with FDF-2? Or can they be based on a common format?


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

47 FDF-38 (New)

LSK – Leap second tabulation

NAIF, announcement is sent out.

● NA

48 FDF-39 (New) FK – Frame Kernels Multiple

LRO Groups ● Section TBD

49 SCN-1 SCN Station Status Packets

SCNUSN ●

Section 4.2.1.5andSection 4.2.1.6

50 SCN-2 SCN Support Schedules SCN ● Section 4.2.1.1

51 SCN-3 SCN Weather Data SCNUSN ● Section 4.2.1.7

52 SCN-4 Ka-Band Measurement Data Files (VC3) SCN ● ● Section 4.2.1.8

53 SCN-5 Laser Range Transmit Information LR Site Section TBD Only to LOLA and

should be removed

54 SCN-6 Raw Tracking Data Files SCN ● ● Section 4.2.1.2

7




Might be able to combine with SCN-11 because the details should be similar enough


Does this include LR Schedules, or do we still need SCN12 (which is not currently included in this table)


Note that these should be different packets and different Section 4 references.


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

55 SCN-7 Real-time VC0 orbiter telemetry SCN ● Section 4.2.1.4

56 SCN-8 Real-time VC1, VC2, VC3 data SCN ● Section 4.2.1.4

57 SCN-9 Ka-Band RF Receiver Data SCN ● Section 4.2.1.9

58 SCN-10CFDP Status Messages from SCN/DPS to MOC/DPS

SCN ● Section 4.2.1.10

59 SCN-11 Stored HK Data Files (VC0–VC3) SCN ● Section 4.2.1.3

60 KSC-1Telemetry from launch Site (Real-time and FTP files)

KSC ● Section 4.5.1.1

61 LAMP-1 LAMP Command Request LAMP ● Section 4.3.3.1

62 LAMP-2 LAMP HV command sequence LAMP ● Section 4.3.3.2

8




Might need to break this into 2 separate KSC-generated products; one for RT and one for files


Might merge with SCN 8 since these are both R/T telemetry interfaces to MOC


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

63 LAMP-3 LAMP Instrument FSW Loads LAMP ● Section 4.3.3.3

64 Launch Vehicle-1

Launch Vehicle Post-Sep Vector

LV, via KSC Launch Support Team

● Section 4.5.1.2

65 LEND-1 LEND Command Request LEND ● Section 4.3.4.1

66 LEND-2 LEND Instrument FSW Loads LEND ● Section 4.3.4.2

67 LOLA-1 LOLA Command Request LOLA ● Section 4.3.5.1

68 LOLA-2 LOLA Gravity Model LOLA ● Section 4.3.5.2

69 LOLA-3 LOLA Instrument FSW Loads LOLA ● Section 4.3.5.3

70 LOLA-4 LOLA Processed OD information LOLA ● Section 4.3.5.4

9




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

71 LOLA-5 LOLA Target Request LOLA ● Section 4.3.5.5

72 LROC-1LROC Instrument Initialization Command Sequence

LROC ● Section 4.3.6.1

73 LROC-2 LROC Daily Command Sequence - LROC ● Section 4.3.6.2

74 LROC-5 LROC File Delivery Verification LROC ● Section

75 LROC-3 LROC Instrument FSW Loads LROC ● Section 4.3.6.3

76 LROC-4 LROC Target Request LROC ● Section 4.3.6.4

77 Mini-RF-1 Mini-RF Load Files Mini-RF ● Section 4.3.7.1

78 Mini-RF-2 Mini-RF Command Timeline Mini-RF ● Section 4.3.7.2

10




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

79 MOC-1 Beta Angle Predicts FDF ● ● ● ● ● ● ● Section 4.1.2.2

80 MOC-2 CFDP Control MOC ● ● Section 4.4.3.4

81 MOC-3 Clock Correlation File MOC ● ● ● ● ● ● ● Section 4.4.1.1.2

82 MOC-48 Commands to KSC MOC ● Section 4.5.2.2

83 MOC-4 CRaTER - Spacecraft HK Data File s/c ● Section 4.4.1.1.3

84 MOC-5 CRaTER HK Data Files s/c ● Section 4.4.1.1.4

85 MOC-6CRaTER Raw Measurement Data Files

s/c ● Section 4.4.1.1.5

86 MOC-7 CRaTER Real-time VC0 HK data s/c ● Section 4.4.1.1.6

11




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

87 MOC-8 Daily Command Load MOC ● ● ● ● ● ● ● Section 4.4.1.1.7

88 MOC-9 LRO Definitive Ephemeris File FDF ● ● ● ● ● ● Section 4.1.2.3

89 MOC-10 DLRE - Spacecraft HK Data File s/c ● Section 4.4.1.2.5

90 MOC-11 DLRE HK Data Files s/c ● Section 4.4.1.2.6

91 MOC-12DLRE Raw Measurement Data Files

s/c ● Section 4.4.1.2.7

92 MOC-13 DLRE Real-time VC0 HK data s/c ● Section 4.4.1.2.8

93 MOC-14 SCN Weather Data SCN ● Section 4.2.1.7

94 MOC-20 Ground Station View Period Predicts FDF ● Section 4.1.2.1

12




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

95 MOC-15 LAMP - Spacecraft HK Data File s/c ● Section 4.4.1.3.5

96 MOC-16 LAMP HK Data Files s/c ● Section 4.4.1.3.6

97 MOC-17LAMP Raw Measurement Data Files

s/c ● Section 4.4.1.3.7

98 MOC-18 LAMP Real-time VC0 HK data s/c ● Section 4.4.1.3.8

99 MOC-19 Laser Range Transmit Information LR Site Section

100 MOC-21 LEND - Spacecraft HK Data File s/c ● Section 4.4.1.4.5

101 MOC-22 LEND HK Data Files s/c ● Section 4.4.1.4.6

102 MOC-23LEND Raw Measurement Data Files

s/c ● Section 4.4.1.4.7

13




Might not go to MOC but from LR to LOLA


DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

103 MOC-24 LEND Real-time VC0 HK data s/c ● Section 4.4.1.4.8

104 MOC-25 LOLA - Spacecraft HK Data File s/c ● Section 4.4.1.5.5

105 MOC-26 LOLA HK Data Files s/c ● Section 4.4.1.5.6

106 MOC-27LOLA Raw Measurement Data Files

s/c ● Section 4.4.1.5.7

107 MOC-47 LRO SPICE Files Definitive FDF ● ● ● ● ● ● ● Section

108 MOC-28 LRO SPICE Files Predicts FDF ● ● ● ● ● ● ● Section

109 MOC-29 LROC - Spacecraft HK Data File s/c ● Section 4.4.1.6.7

110 MOC-30 LROC HK Data Files s/c ● Section 4.4.1.6.8

14




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

111 MOC-31LROC Raw Measurement Data Files

s/c ● Section 4.4.1.6.9

112 MOC-32Lunar Orbit Ascending and Descending Node Predicts

FDF ● ● ● ● ● ● ● Section 4.1.2.6

113 MOC-33Lunar Orbit Terminator Crossing Predicts

FDF ● ● ● ● ● ● Section 4.1.2.7

114 MOC-34 Mini-RF - Spacecraft HK Data File s/c ● Section 4.4.1.7.9

115 MOC-35 Mini-RF HK Data Files s/c ● Section

4.4.1.7.10

116 MOC-36 Mini-RF Operations Opportunity MOC ● Section

4.4.1.7.11

117 MOC-37Mini-RF Raw Measurement Data Files

s/c ● Section 4.4.1.7.12

118 MOC-38 Mission Eclipse Predicts FDF ● ● ● ● ● ● Section 4.1.2.8

15




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

119 MOC-39 Post-Maneuver Spacecraft Mass FDF ● Section 4.1.2.12

120 MOC-40 Predicted LRO Ephemeris File FDF ● ● ● ● ● ● ● Section 4.1.2.14

121 MOC-41 Predicted Lunar Ground Track File FDF ● ● ● ● ● ● ● Section 4.1.2.15

122 MOC-42 Raw Attitude Data File s/c ● ● ● ● ● ● ● ● Section 4.1.3.1

123 MOC-43 Raw Tracking Data Files SCN ●

Section 4.2.1.2 andSection 4.2.2.1

124 MOC-44 Real-Time orbiter commands MOC ● ● Section 4.4.3.1

125 MOC-45 Real-Time orbiter commands - DSN MOC ● Section 4.4.3.1

126 MOC-49 Telemetry to KSC MOC ● Section 4.5.2.1

16




DRAFT


Destination(s)


CRaTER

DLRE

LAMP

LEND

LOLA

LROC

Mini-RF

KSC

LR-SLR

MOC-DPS

MOC-DMS

MOC-ITOS

NAIF-PDS

FDF

DSN

SCN

SCN/DPS

SCN/GNSO

USN

127 MOC-50 Definitive Lunar Ground Track File FDF ● Section 4.1.2.16

128 MOC-51 SCN Support Schedules SCN Section 4.2.1.1

This is a LR Site interface product only

17




DRAFT

4.0 LRO GROUND SYSTEM EXTERNAL INTERFACES AND PRODUCT

For the products defined within this section, Table 4-1 provides the high-level details regarding product information; specifically for the file duration or file time span, volume estimates of the data file and the file delivery protocols and mechanisms.

This table also provides the quick section reference so that users can easily reference the specific section to review for more informational details.

1




DRAFT

Table 4-1 LRO Product Summary Information

No. ID Product Name Section Reference Timespan Volume Delivery Mechanism and File

Conventions

1 CRaTER-1 CRaTER Activity Request

Section 4.3.1.1

Valid until the next load is uplinked to the spacecraft.

Variable size based on types of commands

The file is electronically delivered to the MOC user via a TBR mechanism. Delivery Date and time are TBR

2 CRaTER-2 Product Deleted Product Deleted Product Deleted

3 CRaTER-3CRaTER Instrument Reset Timeline

Section 4.3.1.2

Valid until the next load that is uplinked to the spacecraft.


The file is electronically delivered to the MOC via a TBR mechanism. Delivery Date and time are TBR

4 DLRE-1DLRE Command Request

Section 4.3.2.1

Valid until the next command request is uplinked to the spacecraft.


The file is electronically delivered to the MOC via a TBR mechanism. Delivery Date and time are TBR.

5 DLRE-2 DLRE FSW Loads

Section 4.3.2.2

The DLRE Instrument FSW Load is active until the next load is uplinked to the spacecraft.

TBR – based on FSW Image being uploaded

The file is electronically delivered to the MOC via a TBR mechanism. Delivery Date and time are TBR

6 DSN-1 DSN Tracking Data

Section 4.2.2.1 Five minutes intervals during a

station contact TBR

The file is electronically delivered to the MOC via a TBR mechanism. Delivery Date and time are TBR. The DSN Tracking Data File is delivered at the completion of the five minute duration for each tracking file

7 DSN-2

Archived Station Data for any Stored Virtual Channel

Section 4.2.2.2 Contains all spacecraft data

downlinked during the last real-time station contact.

TBR – Variable based on station contact

The FOT requests this file for playback; the file is electronically delivered to the MOC via a TBR mechanism. The Stored Data files are kept on site at the station for up to 72 hours

2




DRAFT


Conventions

8 DSN-3

Real-Time Telemetry for any commanded VC downlinked

Section 4.2.2.3

Near real-time support (approximately 30 seconds latency).

TBR – based on VCs being transmitted, data rate, and station contact

The file is electronically delivered to the MOC via a TBR real-time socket connection Delivery time is near real-time as the data are received at the DSN station As noted previously, the stations will perform the Reed-Solomon decoding of the data prior to delivery to the LRO MOC (VC0 – VC3)

9 DSN-4 DSN Status Data

Section 4.2.2.4 Packet sent every sixty (60)

seconds during station contact

The DSN Station Status Packets is TBS bytes of information for every packet sent.

The station status packets are electronically delivered to the MOC via a real-time socket connection.

10 FDF-1

Attitude Determination Verification Report

Section 4.1.3.1

The MOC-ADS element creates this file on a weekly basis using all received data from that time span.

TBRThe report is transferred electronically to the MOC’s Data Management System via TBR delivery mechanism

11 FDF-2 Attitude Slew Plans

Section 4.1.3.2

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

The file is electronically delivered via a TBR mechanism Delivery Date and time are TBR

12 FDF-3 Beta Angle Predicts

Section 4.1.2.2

The time span for this product is for the next five (5) years. It starts at 0000 UTC of the next day and contains predicted beta angles for the next 5 years.

TBR

The file is posted to the FDF Product Center on a monthly basis (first day of the month), no later than 4:00 pm, local time (based on the Eastern Time zone). The MOC uses a TBR mechanism to “get” the file.

13 FDF-4 Definitive LRO Ephemeris File

Section 4.1.2.3

The time span for this product is for the previous seven (7) days from 0000 UTC seven days prior to 0000 UTC of the current day.

TBR

The file is posted to the FDF Product Center on a weekly basis (Wednesday of the week), no later than 4:00 pm, local time (based on the Eastern Time zone). The MOC uses a TBR mechanism to “get” the file.

3




DRAFT


Conventions

14 FDF-5 DSN Acquisition Data

Section 4.1.1.2 The time span for this product is

28 days TBRThe FDF-generated file is electronically delivered to the DSN via a TBR mechanism. Delivery Date and time are TBR. FDF generates the file on a daily basis

15 FDF-6 SCN Acquisition Data

Section 4.1.1.1 10 days of station contacts

starts at 0000Z for the subsequent Monday

TBR

The FDF-generated file is electronically delivered to the SCN user via a TBR mechanism. The file is generated on a weekly schedule, nominally on the Wednesday of the week, unless agreed upon by FDF. It will be ready for delivery by 1400 Hours local time, EST.

16 FDF-7Ground Station View Period Predicts

Section 4.1.2.1 30 days from 0000 Hours of the

first day within the file to 0000 Hours thirty days later

TBR

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

17 FDF-8 Gyro Calibration Data

Section 4.1.3.3 Valid until the next gyro cal

function TBR

The file is generated on an as-needed basis and delivered to the DMS System via a TBR delivery mechanismDelivery date and time are TBR

18 FDF-9 HGA Calibration Data

Section 4.1.3.4 Valid until the next HGA cal

function TBR

The file is generated on an as-needed basis whenever the LRO High Gain Antennae is calibrated and delivered to the DMS System via a TBR delivery mechanismDelivery date and time are TBR

19 FDF-10Laser Ranging Site Prediction Data


28 days from 0000 Hours of the first day within the file to 0000 Hours twenty-eight days later.

TBR

The FDF-generated file is electronically delivered to the LR Site via a TBR mechanism. FDF delivers this file on a weekly basis (Thursday of the week prior to the week in question)

4




DRAFT


Conventions

20 FDF-11 LRO Definitive SPICE File


for the previous day period from 0000 UTC of the previous day to 0000 UTC of the current day.

TBR

The file is posted to the FDF Product Center on a daily basis, no later than 4:00 pm, local time (based on the Eastern Time zone). The MOC uses a TBR mechanism to “get” the file.

21 FDF-12 LRO Predictive SPICE File


for the next 28 days from 0000 UTC of the current day to 0000 UTC 28 days in the future.

TBR


22 FDF-13

Lunar Orbit Ascending and Descending Node Predicts

Section 4.1.2.6

Contain seven (7) days of node crossing data for LRO spacecraft scheduled beginning at 0000Z on the next subsequent day and stopping at 0000Z seven days later.

TBR


23 FDF-14

Lunar Terminator Crossing Predicts

Section 4.1.2.7

Contain seven (7) days of terminator crossing data for LRO spacecraft scheduled beginning at 0000Z on the next subsequent day and stopping at 0000Z seven days later.

TBR


24 FDF-15 Mission Eclipse Predicts

Section 4.1.2.8

Contain ninety (90) days of eclipse prediction data for LRO spacecraft scheduled beginning at 0000Z on the next subsequent day and stopping at 0000Z ninety (90) days later.

TBR – 90 days of mission eclipse predicts


5




DRAFT


Conventions

25 FDF-16 Lunar Ephemeris

Section 4.1.2.9

Contain seven (7) days of lunar position and velocity information scheduled beginning at 0000Z on the next subsequent day and stopping at 0000Z seven days later.

TBR – 7 days lunar ephemeris predicts


26 FDF-17 Orbiter thruster maneuver plans

Section 4.1.2.10 Thruster Maneuver Plan only

valid for the stated period within the plan

TBR

The file is posted to the FDF Product Center TBR days before the planned maneuver, no later than 4:00 pm, local time (based on the Eastern Time zone). The MOC uses a TBR mechanism to “get” the file.

27 FDF-18 Orbiter to Earth Range Predicts

Section 4.1.2.11

Contain seven (7) days of orbiter to earth range predict data (centered at 1 minute intervals) beginning at 0000Z on the next day and stopping at 0000Z seven days later for each station contact.

TBR – 7 days of LRO range predicts


28 FDF-19Orbiter Post Maneuver Report

Section 4.1.2.12 Report valid until the next LRO

thruster maneuver.TBR – 7 days of LRO range predicts

The file is posted to the FDF Product Center no later than 12 hours after the completion of the current thruster maneuver. The MOC uses a TBR mechanism to “get” the file.

29 FDF-20 Post-Separation Report

Section 4.1.2.13 This report is generated within 2

hours after the LRO separation from the launch vehicle.

TBR – 1 page of ASCII text information

The file is posted to the FDF Product Center no later than 2 hours after the LRO separation from the EELV. The MOC uses a TBR mechanism to “get” the file.

6




Is this time period too relaxed? Should FDF generate this within 30 minutes of receipt of the LV Separation data from the EELV Support Team.


Need to define this limit with FDF and FOT so that plan can be used to create & validate orbiter commands.


DRAFT


Conventions

30 FDF-21 Predicted LRO Ephemeris File

Section 4.1.2.14 Contains the next thirty (30)

days of predictive ephemeris data from 0000Z of the next subsequent day out through an additional 30 days.

TBR


31 FDF-22Predicted Lunar Ground Track File

Section 4.1.2.15 Contains the next thirty (30)

days of lunar ground track data from 0000Z of the next subsequent day out through an additional 30 days.

TBR


32 FDF-23 SA Calibration Data

Section Product Deleted Product Deleted Product Deleted

33 FDF-24 LRO State Vector Table

Section 4.1.3.5 Contains the next (TBR) days of

LRO State Vectors (centered at TBR minute increments)

TBR


34 FDF-25 Star Tracker Calibration data

Section 4.1.3.6 Valid until the next Star Tracker

cal function TBR

The MOC-ADS-generated file is electronically delivered to the DMS element via a TBR mechanism. Delivery Date and time are TBR.

35 FDF-26 Thruster Calibration Data

Section 4.1.3.7 Valid until the next Thruster cal

function TBR


7




DRAFT


Conventions

36 FDF-27 (New)

Momentum Management Unload Plan

Section 4.1.3.8 LRO momentum management

Unload Plan only valid for the identified time period

TBR


37 FDF-28 (New)

Star Tracker Occultation Report

Section 4.1.2.17 Contains the next (TBR) days of

data that identifies when the star tracker is occulted by either the moon, earth or sun

TBR


38 FDF-29 (New)

Attitude Slew Report

Section 4.1.3.2

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

The file is electronically delivered via a TBR mechanism Delivery Date and time are TBR

39 FDF-30 (New)

Definitive Lunar Ground Track File


for the previous 24 hours from 0000Z of the previous day to 0000Z of the current day.

TBR


40 FDF-31 (New)

HGA/SA Fixed offset SPK

Section TBD The FDF-generated file is electronically delivered to the user via a TBR mechanism. Delivery Date and time are TBR.

41 FDF-32 (New) SPK – Planet

N/A The FDF-generated file is electronically delivered to the user via a TBR mechanism. Delivery Date and time are TBR.

42 FDF-33 (New) Generic PCK


43 FDF-34 (New) Binary PCK


8




DRAFT


Conventions

44 FDF-35 (New) Predicted CK


45 FDF-36 (New) Definitive CK


46 FDF-37 (New)

SCLK – Spacecraft clock correlation file


47 FDF-38 (New)

LSK – Leap second tabulation

NA The FDF-generated file is electronically delivered to the user via a TBR mechanism. Delivery Date and time are TBR.

48 FDF-39 (New)

FK – Frame Kernels


49 SCN-1 SCN Station Status Packets

Section 4.2.1.5andSection 4.2.1.6

Contains a running summation of requested status data for the last 60 second during the station contact

TBRStation Status Packets are delivered to the MOC every 60 seconds in real-time via a TBR mechanism.

50 SCN-2 SCN Support Schedules

Section 4.2.1.1

Covers the weekly station contacts from Monday, 00:00:00 Z for the specified start date up through 23:59:59Z of the next subsequent Sunday date. The file may actually contain one week plus one day to ensure consistency from one scheduling period to the next.

TBR

GNSO electronically delivers schedule files is to the MOC on a weekly basis via a TBR mechanism. Delivery Date and time are TBR.

Operational schedule delivered on the Thursday before the start of the week in question

9




Does this include LR Schedules, or do we still need SCN12 (which is not currently included in this table)


Note that these should be different packets and different Section 4 references.


DRAFT


Conventions

51 SCN-3 SCN Weather Data

Section 4.2.1.7

Contains the weather information that corresponds to the time period of the station contact the data are sampled and provided at 30 minute intervals.

TBR

The file is electronically delivered to the MOC via a TBR mechanism. Delivery is scheduled to occur within 30 minutes of the conclusion of the station contact.

52 SCN-4

Ka-Band Measurement Data Files (VC3)

Section 4.2.1.8

Contains stored science measurement data files as defined within the corresponding Data Instrument ICD.

TBR – Based on individual science instrument and science Housekeeping filesFiles can be bounded based on time limits, size limits, or command

The file is electronically delivered to the MOC via a TBR mechanism, within 30 minutes of the completion of the WS1 station contact

53 SCN-5Laser Range Transmit Information

Section TBDOnly to LOLA and should be removed

54 SCN-6 Raw Tracking Data Files

Section 4.2.1.2 Tracking data correspond to

received UTDF data from the last 5 minutes (nominal case) or over the last hour (when data is forwarded via real-time connection))

TBR – max time limit for a file is 5 minutes (nominal case) or Hourly files as backup when data is transmitted in R/T to FDF.

Data delivered either 1) Real-time to FDF. (backup also has files created at hourly intervals) Realtime support is for mission critical activities.

2) Files to both FDF and MOC every 5 minutes.The files are electronically delivered to the FDF and the MOC via a TBR mechanism,

10




Need to define whether stations WILL support R/T UTDF transmission


MOC43 Data Product (Raw3 Tracking Data is also sent to the LOLA SOC; need to verify how/if R/T UTDF Data is captured into file format for transmission to LOLA SOC


Missing the CFDP I/F messages for Acks and NACKs and other File Control


DRAFT


Conventions

55 SCN-7 Real-time VC0 orbiter telemetry

Section 4.2.1.4

The data is delivered in near real-time to the LRO MOC as it is received by the station.

TBR – based on downlink data rate

The data are delivered electronically to the MOC via a real-time socket connection; data are delivered with near real-time of receipt at the station (within TBD seconds)Stations perform the Reed-Solomon decoding of the data prior to delivery to the LRO MOC (VC0 – VC3) or to the WS1 mission unique equipment (VC2 and VC3).

56 SCN-8 Real-time VC1, VC2, VC3 data

Section 4.2.1.4 The data is delivered in near

real-time to the LRO MOC as it is received by the station.

TBR – based on downlink data rate

The data are delivered electronically to the MOC via a real-time socket connection, data are delivered with near real-time of receipt at the station (within TBD seconds)

57 SCN-9 Ka-Band RF Receiver Data

Section 4.2.1.9 Corresponds to the last WS1

station contact (AOS to LOS) TBR

The file is electronically delivered to the MOC and FDF via a TBR mechanism; , within 30 minutes of the completion of the WS1 station contact

58 SCN-10

CFDP Status Messages from SCN/DPS to MOC/DPS

Section 4.2.1.10

The data consists of the status information that is valid from the last time interval since from when the MUE generated the last status message.

TBR

The file is electronically delivered to the MOC via a real-time socket connection, data packets are delivered with near real-time of receipt at the station (within TBD seconds) of the corresponding CFDP Control Message

59 SCN-11Stored HK Data Files (VC0–VC3)

Section 4.2.1.3 The Stored Data files are kept

on site at the station for up to 72 hours.

TBR - dependant upon the virtual channel and the time duration of the real-time pass, as well as the downlink rate

The files are electronically delivered to the MOC via a TBR mechanism, based on an FOT generated request to play back a specified file

11




Define limit for delivery; will define pipeline.for transmission; define limit for all 3 stations ; approx 30 seconds good for all elements.


DRAFT


Conventions

60 KSC-1

Telemetry from launch Site (Real-time and FTP files)

Section 4.5.1.1

Realtime and File simulated telemetry is valid only during test phaseRelatime operational telemetry is valid during post-launch support activities

TBR – based on realtime rates or file sizes to support mission rehearsals

Real-time - The real-time data are electronically delivered to the MOC via a socket connection. FTP Files - The file is electronically delivered to the MOC via a TBR mechanism.

61 LAMP-1LAMP Command Request

Section 4.3.3.1

Command Request active until the next load is uplinked to the spacecraft; nominally daily or weekly instrument loads.

TBR – based on number of commands

The file is electronically delivered to the MOC via a TBR mechanism, delivery date and time are TBR

62 LAMP-2LAMP HV command sequence

Section 4.3.3.2

HV Command Sequence active until the next load is uplinked to the spacecraft; nominally daily or weekly instrument loads.


The file is electronically delivered to the MOC via a TBR mechanism., delivery date and time are TBR

63 LAMP-3LAMP Instrument FSW Loads

Section 4.3.3.3

The LAMP Instrument FSW Load is active until the next load is uplinked to the spacecraft.


The file is electronically delivered to the MOC via a TBR mechanism., delivery date and time are TBR

64 Launch Vehicle-1

Launch Vehicle Post-Sep Vector

Section 4.5.1.2 File is delivered approximately

30 minutes after spacecraft separation

1 page text information

via fax to FDF, at GSFC in Building 28, room TBD. The fax telephone number is 301-286-xxxx). backup mechanism is to directly phone the flight dynamic’s facility at 301-286-yyyy).

65 LEND-1LEND Command Request

Section 4.3.4.1




12




Actually delivery mechanism for LV Post Sep Vector is dependent upon which EELV provider is chosen (Atlas or Delta)


DRAFT


Conventions

66 LEND-2LEND Instrument FSW Loads

Section 4.3.4.2

The LEND Instrument FSW Load is active until the next load is uplinked to the spacecraft.



67 LOLA-1LOLA Command Request

Section 4.3.5.1




68 LOLA-2 LOLA Gravity Model

Section 4.3.5.2

The updated gravity model generated approximately every six months (TBR) and is based on the previous six months of Laser Ranging transmit data and other tracking data.

TBR – based on size and parameters for the new Gravity Model

The file is electronically delivered to the FDF and MOC via a TBR mechanism; delivery date and time are TBR.

69 LOLA-3LOLA Instrument FSW Loads

Section 4.3.5.3

The LOLA Instrument FSW Load is active until the next load is uplinked to the spacecraft.


The file is electronically delivered to the MOC via a TBR mechanism; delivery date and time are TBR.

70 LOLA-4LOLA Processed OD information

Section 4.3.5.4

TBS TBR – based on size and parameters for the sampling rate for the LOLA Process OD data

The file is electronically delivered to the FDF and MOC via a TBR mechanism, delivery date and time are TBR.

71 LOLA-5 LOLA Target Request

Section 4.3.5.5

LOLA Target Requests active and valid only for the associated time period identified in the commands



13




DRAFT


Conventions

72 LROC-1

LROC Instrument Initialization Command Sequence

Section 4.3.6.1




73 LROC-2LROC Daily Command Sequence -

Section 4.3.6.2

Daily Command Sequence active for 24 hours until the next load is uplinked to the spacecraft.



74 LROC-5Section

75 LROC-3LROC Instrument FSW Loads

Section 4.3.6.3

The LROC Instrument FSW Load is active until the next load is uplinked to the spacecraft.



76 LROC-4 LROC Target Request

Section 4.3.6.4

LROC Target Requests active and valid only for the time associated in the command load



77 Mini-RF-1 Mini-RF Load Files

Section 4.3.7.1

The Mini-RF Load File is active until the next load is uplinked to the spacecraft.



78 Mini-RF-2Mini-RF Command Timeline

Section 4.3.7.2

Command Timeline active until the next load is uplinked to the spacecraft.



79 MOC-1 Beta Angle Predicts

Section 4.1.2.2

The file is electronically delivered via a TBR mechanism; delivery date and time are TBR.

14




DRAFT


Conventions

80 MOC-2 CFDP Control

Section 4.4.3.4

The CFDP Control delivered via a realtime socket connection to the MUE located at WS1 stationCFDP Controls issued every TBR seconds

81 MOC-3 Clock Correlation File

Section 4.4.1.1.2

Valid for previous day’s clock updates from 0000Z of the previous day to 0000Z of the current day. .

TBRThe Clock Correlation file is electronically delivered on a daily basis via a TBR mechanismdelivery time are TBR.

82 MOC-48 Commands to KSC

Section 4.5.2.2

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

83 MOC-4CRaTER - Spacecraft HK Data File

Section 4.4.1.1.3

Data corresponds to that which was downlinked during the last real-time station contact

TBR – based on time since last station contact

The file is electronically delivered to the CRaTER SOC via a TBR mechanismdelivery time is TBR.

84 MOC-5 CRaTER HK Data Files

Section 4.4.1.1.4

The file is electronically delivered via a TBR mechanismdelivery date and time are TBR.

85 MOC-6CRaTER Raw Measurement Data Files

Section 4.4.1.1.5


86 MOC-7CRaTER Real-time VC0 HK data

Section 4.4.1.1.6 The data are delivered electronically to the

CRaTER SOC via a real-time socket connection

87 MOC-8 Daily Command Load

Section 4.4.1.1.7


15




DRAFT


Conventions

88 MOC-9 LRO Definitive Ephemeris File

Section 4.1.2.3


89 MOC-10DLRE - Spacecraft HK Data File

Section 4.4.1.2.5



The file is electronically delivered to the DLRE SOC via a TBR mechanismdelivery time is TBR.

90 MOC-11 DLRE HK Data Files

Section 4.4.1.2.6


91 MOC-12DLRE Raw Measurement Data Files

Section 4.4.1.2.7


92 MOC-13 DLRE Real-time VC0 HK data

Section 4.4.1.2.8

The file is electronically delivered via a TBR mechanism

93 MOC-14 SCN Weather Data

Section 4.2.1.7


94 MOC-20Ground Station View Period Predicts

Section 4.1.2.1 The file is electronically delivered via a TBR

mechanism

95 MOC-15LAMP - Spacecraft HK Data File

Section 4.4.1.3.5



The file is electronically delivered to the LAMP SOC via a TBR mechanismdelivery time is TBR.

96 MOC-16 LAMP HK Data Files

Section 4.4.1.3.6


16




DRAFT


Conventions

97 MOC-17LAMP Raw Measurement Data Files

Section 4.4.1.3.7


98 MOC-18LAMP Real-time VC0 HK data

Section 4.4.1.3.8 The data are delivered electronically to the

LAMP SOC via a real-time socket connection

99 MOC-19Laser Range Transmit Information

Section

100 MOC-21LEND - Spacecraft HK Data File

Section 4.4.1.4.5




101 MOC-22 LEND HK Data Files

Section 4.4.1.4.6


102 MOC-23LEND Raw Measurement Data Files

Section 4.4.1.4.7 The file is electronically delivered via a TBR

mechanism

103 MOC-24 LEND Real-time VC0 HK data

Section 4.4.1.4.8

The data are delivered electronically to the LEND SOC via a real-time socket connection

104 MOC-25LOLA - Spacecraft HK Data File

Section 4.4.1.5.5




105 MOC-26 LOLA HK Data Files

Section 4.4.1.5.6


17




DRAFT


Conventions

106 MOC-27LOLA Raw Measurement Data Files

Section 4.4.1.5.7


107 MOC-47 LRO SPICE Files Definitive

108 MOC-28 LRO SPICE Files Predicts

109 MOC-29LROC - Spacecraft HK Data File

Section 4.4.1.6.7




110 MOC-30 LROC HK Data Files

Section 4.4.1.6.8

The file is electronically delivered via a TBR mechanismdelivery date and time are TBR

111 MOC-31LROC Raw Measurement Data Files

Section 4.4.1.6.9

The file is electronically delivered via a TBR mechanismdelivery date and time are TBR

112 MOC-32

Lunar Orbit Ascending and Descending Node Predicts


mechanismdelivery date and time are TBR

113 MOC-33

Lunar Orbit Terminator Crossing Predicts


mechanismdelivery date and time are TBR

114 MOC-34Mini-RF - Spacecraft HK Data File

Section 4.4.1.7.9




18




DRAFT


Conventions

115 MOC-35 Mini-RF HK Data Files

Section 4.4.1.7.10


116 MOC-36Mini-RF Operations Opportunity

Section 4.4.1.7.11


117 MOC-37Mini-RF Raw Measurement Data Files

Section 4.4.1.7.12


118 MOC-38 Mission Eclipse Predicts

Section 4.1.2.8


119 MOC-39 Post-Maneuver Spacecraft Mass

Section 4.1.2.12


120 MOC-40 Predicted LRO Ephemeris File

Section 4.1.2.14


121 MOC-41Predicted Lunar Ground Track File


mechanism

122 MOC-42 Raw Attitude Data File

Section 4.1.3.1


123 MOC-43 Raw Tracking Data Files

Section 4.2.1.2 andSection 4.2.2.1


19




DRAFT


Conventions

124 MOC-44Real-Time orbiter commands

Section 4.4.3.1 The commands are sent via real-time socket

connects to the USN/WS1 station

125 MOC-45

Real-Time orbiter commands - DSN

Section 4.4.3.1 The commands are sent via real-time socket

connects to the DSN station

126 MOC-49 Telemetry to KSC

Section 4.5.2.1

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

127 MOC-50Definitive Lunar Ground Track File


mechanism

128 MOC-51 SCN Support Schedules

Section 4.2.1.1


20




DRAFT

4.1 FLIGHT DYNAMICS FACILITY PRODUCTS

This section provides the details to the products that the Flight Dynamics Facility creates to support of the LRO mission. FDF creates these products are on a regular basis in support of station acquisition data, science operations centers, maneuver planning and general reports to the Flight Operations Team.

FDF generates these products using a standard naming convention as defined by the following concepts of a file name and a file extension separated by the standard period (.):

<file name>.<file extension>; where

<file name> FDFnn_YYYYDOY.HHMMSS_vn; whereFDFnn => 5 ASCII characters in which the nn refers to the identifier listed as the LRO

Ground System Product Matrix; for exampleFDF01 = Attitude Determination ReportFDF02 = Attitude Slew PlanFDF06 = Ground Network Acquisition Data File

YYYYDOY => 7 ASCII charactersYYYY => 4 ASCII characters for the year (2008 – 2013)DOY => 3 ASCII characters for day of year designator (01 – 366)

HHMMSS => 6 ASCII characters representing the station AOS timeHH => 2 ASCII characters for the AOS hour (00 – 23)MM => 2 ASCII characters for the AOS minutes (01 – 59)SS => 2 ASCII characters for the AOS seconds (01 – 59)

vnn => 3 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 is 02, 03, etc. The MMDDDOY designation identifies the first time period covered by the data within the file, while the HHMMSS represents the first AOS time contained within the file.

For example, the SCN Station Acquisition Data file would be names with these concepts assuming that the first data point represents October 15, 2008 at HYHMMSS and it was the first generation of the file, this portion of the file name is identified as FDF06_2006_DOY_HHMMSS_01.inp2

<file extension> 3 ASCII characters representing the type of file; e.g., txt, for a text file inp2 for the FDF generated SCN acquisition data product (version 2 of INP)bsp, for a binary spice (SPK) file, which provides the position and velocity information for the referenced object; the position information is x, y, z referenced information given as Km and the velocity information (xdot, ydot, zdot) referenced as Km/sec.tf, for a text reference frame designationtls, for leap second files

21



Jim Clapsadle, 04/09/06,

Prefer DOY


DRAFT

tpc, for PCK constants file

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

4.1.1 FDF Products for Network Support

This section provides the details on the acquisitions data products that FDF generates; these products are used by the various networks that provide tracking, telemetry and command interfaces to support the LRO mission.

4.1.1.1 SCN Station Acquisition Data

4.1.1.1.1 Product DescriptionThis product file contains acquisition information for each Space Communications Network ground station supporting the LRO telemetry and measurement data downlink or command uplink. FDF creates a separate file for each station supporting the LRO mission

4.1.1.1.2 Support DurationThe 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 actual mission 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 ASCII textual data fields that are space delimited. This product is generated such that the time tag information is centered at 1 minute increments.

The file contains the acquisition data for each contact for the station; FDF generates a separate file for each station. Each file will have 1:N lines of header information that identifies the file name and file creation information. This is followed by 1:N lines of station acquisition information. The standard fields and field description (for the 1:N lines of acquisition data) are listed in the following table.

Field name Field Characteristicsstation name 4 ASCII text characters representing the unique station identifies

timetag information:yearday of year and time of day

YYYY DOY HHMMSS.mmm, whereYYYY => 4 ASCII digits of year (2008 – 2013)DOY => 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

22




Are SPICE Files provided only in Binary File format or will they be textual? Also, do we need to provide a SPICE File Viewer tool? And is that on the NAIF web site?


DRAFT

Field name Field Characteristicsrange RRRRRRR.ddddd

RRRRRR => 6 ASCII digits for whole range (0 – 999999)ddddd => 5 ASCII digits for decimal portion of range (00 – 99999)

Range rate RR.ddddddRR => 2 ASCII digits for whole range rate (0 – 99)dddddd => 6 ASCII digits for decimal portion of range (00 – 999999)

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

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

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

<File name>_<version number>.<file extension>

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

Station Identifier =>5 total ASCII Characters4 ASCII Characters used to represent the stations supporting

the LRO mission; followed by a 1 character underscore Project Identifier => 5 total ASCII Characters

4 ASCII Characters used to represent the LRO mission (0059), followed by an underscore

Start Date/Time => 16 total ASCII Characters15 ASCII Characters used to represent the start time of the

first station acquisition; YYYY_DOY.HHMMSS; followed by a 1 character underscore

version number = [3 characters] Three ASCII character version number. The initial version is 001, next is 002 … up to 999.

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

For example, a sample file name for the acquisition data corresponding to the WS1 station (for the 10 day period of Monday, October 27 2008 through Thursday, November 6, 2008) would have the following file name convention:LRWS_0059_2008_301.020000_001.inp2

A sample station acquisition data product is provided as a reference in Appendix B.1-1.

23




DRAFT

4.1.1.1.4 Accuracy and CompletenessThe data file will consist of all station contacts for the upcoming three days and will contain the acquisition information centered at one minute increments. The accuracy of this station acquisition data is consistent with the predicted ephemeris data based upon the most recent tracking information. The file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.1.2 DSN Site Acquisition Data

4.1.1.2.1 Product DescriptionThe DSN site acquisition data describes the FDF-generated information, which provides times, angles, and other necessary information to allow the DSN 34-m site to acquire the LRO spacecraft.

4.1.1.2.2 Support DurationFDF provides the laser ranging site acquisition data for all mission phases. FDF will provide this data during pre-launch for use in testing interfaces and to support any pre-launch mission rehearsals and tests. FDF continues to provide this data for all post-launch mission phases.

4.1.1.2.3 FormatThe format is the predicted SPICE SPK formatted file; this format is consistent with the information listed at the following URL:

<PROVIDE NAIF WEB SITE URL REFERENCE>

A sample file name for the first generation of this data file is given as FDF05_10152006_01.bsp

This file format and content are defined in Appendix B.1-2.

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 the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations))

4.1.1.3 Laser Ranging Site Prediction Data

4.1.1.3.1 Product DescriptionThe laser ranging site prediction data describes the FDF-generated information used by the laser ranging site; it provides the detailed laser pointing information required to accurately point the laser to the spacecraft. This information provides times, angles, and other necessary information to allow the laser ranging site to locate the LRO spacecraft and begin the laser ranging functions.

4.1.1.3.2 Support Duration

24




Add new tracking precision concepts


Provide the correct NAIF reference for SPICE related formats


DRAFT

FDF provides the laser ranging site acquisition data for all mission phases. FDF will provide this data during pre-launch for use in testing interfaces and to support any pre-launch mission rehearsals and tests. FDF continues to provide this data for all post-launch mission phases.

4.1.1.3.3 FormatThe laser ranging site acquisition data format is consistent with International Laser Ranging

Service (ILRS) format, as defined by the Consolidated Laser Ranging Prediction Format; Version 1.00 or otherwise known as the ILRS Fullrate Format (Version 3). This format is consistent with the information listed at the following URL:

http://ilrs.gsfc.nasa.gov/products_formats_procedures/fullrate/fr_format_v3.html<PROVIDE CORRECT ILRS WEB SITE URL REFERENCE>

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

A sample Laser Ranging Site Prediction Data file is provided as a reference in Appendix B.1-3.

4.1.1.3.4 Accuracy and CompletenessThe file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations))

4.1.2 FDF Products to support MOC Functions

FDF generates this following set of products for use by the MOC to perform most of its daily functions. Some of these data products are electronically transferred to the various Science Operations Centers while other are used internally within the MOC by the LRO operations team to support command generation or as reports that are generated on a daily or as-needed basis.

4.1.2.1 Ground Station View Period Predicts Data

4.1.2.1.1 Product DescriptionThe Ground Station View Period Predicts file contains the information related to when an LRO-affiliated ground station is in view of the LRO spacecraft. It identifies the time period and whether the High-Gain and/or Omni antennas can be viewed from the ground station.

4.1.2.1.2 Support DurationFDF provides the Ground Station View Period Predicts file for all mission phases. FDF will provide this data during pre-launch for use in testing interfaces and to support any pre-launch mission rehearsals and tests. FDF continues to provide this data for all post-launch mission phases.

4.1.2.1.3 FormatThis file contains the data associated with view periods for all supporting ground stations used to provide LRO with TT&C support during the various mission phases. It consists of the station identifier and the view period information for that station based on the known antennae masking

25




Need to provide the correct ILRS URL reference that identifies the acq data needed by Laser Ranging.



DRAFT

parameters. There are two lines for each station if the HGA and omni antennas are both viewable from the ground station. In this event, the HGA view period is a subset of the omni view period.

The general format of this file consists of the following information:

Station Name Start Time Stop Time Antenna Flag Maximum Elevation Angle; where these fields are defined in the following table:


Start time information:yearday of year and time of day



Stop time information:yearday of year and time of day



Antennae Flag 1 ASCII Character flag to indicate whether this is a HGA or OMNI view periodH => LRO HGA is viewable from the ground stationO => LRO omni is viewable from the ground station

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


A sample Ground Station View Period Predict Data file is provided as a reference in Appendix B.1-4.


4.1.2.2 LRO Beta Angle Predict File

4.1.2.2.1 Product Description

26




DRAFT

The LRO Beta Angle Predict File provides the angle information between the LRO lunar orbit plane and the sun with the following definition. When the sun is in the orbit plane, this results in a zero degree (0°) angle. If the sun and orbit plane are perpendicular to each other; then this results in a beta angle of ninety degrees (90°). In this specific instance, the LRO spacecraft is in continuous full sun.

4.1.2.2.2 Support DurationFDF will generate this file for all mission phases.

4.1.2.2.3 FormatThe LRO Beta Angle Predict file is an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The file contains the time of the sample, the Beta angle information (given in degrees and hundredths of degree) and the sun quadrant information that provides information as to whether the angle is increasing or decreasing. The file entries are generated at six hour increments. The file contains the time, beta angle, and quadrant information; the following table provides a brief description of each field:

Field name Field Characteristicstime information:yearday of year and time of day



Beta Angle SBB.bb => 6 ASCII characters including the period between the first 3 and last 2the first character is a sign value (positive or negative angles)

a Blank = Positive angle reference - = Negative angle 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 Beta Angle definition. Allowable values are: 1 – 4 inclusive


A sample LRO Beta Angle File data file is provided as a reference in Appendix B.1-5.


4.1.2.3 LRO Definitive Ephemeris File


27




Is this suppose to be at 2 hour increments?


DRAFT

The LRO Definitive Ephemeris file contains the LRO spacecraft’s position and velocity information in a moon-centered inertial, mean J2000 coordinate reference frame. The data is centered at one minute increments


4.1.2.3.3 FormatThe Definitive Ephemeris file is an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The file contains the time of the sample, the X,Y, Z position information (given in Kilometers, or Km) and the X, Y, and Z velocity components (given in Kilometers per second, or Km/sec). The file entries are generated at one minute increments. The following table provides a brief description of each field:




X-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3

first 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 RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 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 RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 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 RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3

first 6 are the whole portions of the X-component of the LRO’s velocitylast 3 are the decimal portion of the X-component velocity

Y-Velocity RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3

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

28




DRAFT

Field name Field CharacteristicsZ-Velocity RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and

last 3first 6 are the whole portions of the Z-component of the LRO’s velocitylast 3 are the decimal portion of the Z-component velocity


A sample LRO Definitive Ephemeris File data file is provided as a reference in Appendix B.1-6.

4.1.2.3.4 Accuracy and CompletenessThe file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.2.4 LRO Definitive SPICE File

4.1.2.4.1 Product DescriptionThis file contains the SPICE “kernel” information for the definitive LRO spacecraft ephemeris data. This kernel file contains the previous day’s definitive LRO spacecraft position and velocity information based upon the recently processed day’s tracking data.


4.1.2.4.3 FormatThe Definitive Spice file is a UNIX-based binary SPICE file and will require the use of the SPICE 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 LRO Definitive SPICE File is provided as a reference in Appendix B.1-7.


4.1.2.5 LRO Predictive SPICE File

4.1.2.5.1 Product DescriptionThis file contains the SPICE “kernel” information for the predictive LRO spacecraft ephemeris data. This kernel file contains the next twenty-eight (28) day’s worth of LRO spacecraft positions and velocity information based upon the just processed day’s tracking data. This file

29



http://naif.jpl.nasa.gov/naif/index.html


DRAFT

will contain the LRO Predictive data information related to the LRO station keeping maneuvers that are to occur in within this 28 day time period.


4.1.2.5.3 FormatThe Predictive Spice file is a UNIX-based binary SPICE file and will require the use of the SPICE 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 LRO Predictive SPICE File data file is provided as a reference in Appendix B.1-8.


4.1.2.6 Lunar Orbit Ascending and Descending Node Predicts

4.1.2.6.1 Product DescriptionThis file contains the lunar-nodal crossing predicts associated when the LRO orbit either crosses the ascending node or the descending node.

4.1.2.6.2 Support DurationFDF will generate this file during all mission phases and immediately after a 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 text file in which the fields are separated by a variable length set of blanks. The file contains the nodal crossing time, the nodal crossing type, and the corresponding lunar longitude; these fields are separated by blanks. The following table provides a brief description of each field:

Field name Field Characteristicstimetag information:yearday of year and time of day



30




Does it make sense to have add LRO lunar orbit number?

http://naif.jpl.nasa.gov/naif/index.html


DRAFT

Field name Field CharacteristicsNode Crossing Type 1 Character ASCII flag to indicate if the type of nodal crossing

A => Ascending Node Crossing TypeD => Descending Node Crossing Type

Lunar Longitude AAA.dddAAA => 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 DE400 coordinate system


A sample LRO Ascending Descending Node data product is provided as a reference in Appendix B.1-9.

4.1.2.6.4 Accuracy and CompletenessThe data file will consist of every ascending and descending node crossing predictions for the upcoming seven days and will contain the data centered at one minute increments. The accuracy of this node crossing data is consistent with the predicted ephemeris data based upon the most recent tracking information. The file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.2.7 Lunar Orbit Terminator Crossing Predicts

4.1.2.7.1 Product DescriptionThis is a file that contains lunar terminator crossing predicts associated when the LRO spacecraft crosses the lunar terminator line.


4.1.2.7.3 FormatThis is a file that contains 1-week’s worth of lunar terminator crossing predicts. The file is an ASCII text file in which the fields are separated by a variable length set of blanks. The file contains the terminator crossing time and the corresponding terminator type; the following table provides a brief description of each data field:




31




Similar to the last file, is there such a thing as a Lunar orbit number that should be included here?


DRAFT

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 => Out from Lunar Night (going from Lunar Night into day )


A sample LRO Ascending Descending Node data product is provided as a reference in Appendix B.1-10.

4.1.2.7.4 Accuracy and CompletenessThe data file will consist of every lunar terminator crossing predictions for the upcoming seven days and will contain the data centered at one minute increments. The accuracy of this node crossing data is consistent with the predicted ephemeris data based upon the most recent tracking information. The file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.2.8 Mission Eclipse Predicts

4.1.2.8.1 Product DescriptionThis file contains the predictive information associated when the LRO spacecraft is put into a shadow resulting from either a lunar or earth caused eclipse.


4.1.2.8.3 FormatFDF generates this file as an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The format for this file can consist of 2 lines that identify the mission eclipses that result in both a partial eclipse (LRO is flying in the penumbra shadow) and a full eclipse (LRO is flying in the umbra shadow). The umbra is always a subset of the penumbra phase and as such the start/stop times and durations will be contained within the penumbra. If there are 2 lines, the first line is the penumbra information and the second line contains the umbra information. The file has the following field information: Start Time, Stop Time, Shadow Flag, Duration, and Occultation Flag; these fields are defined in the following table:

Field name Field CharacteristicsStart time information:yearday of year and time of day



32




One minute increments might be too coarse - Check w/ Mark Beckman


DRAFT

Field name Field CharacteristicsStop time information:yearday of year and time of day

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


Shadow Flag 1 ASCII Character flag to indicate if the type of eclipseP => LRO is in penumbra eclipseU => LRO is in umbra eclipse

Duration MMM..dddMMM => 3 ASCII digits for whole portion of minutes (0 – 160)ddd => 3 ASCII digits for decimal portion of minutes (000 – 999)

Occultation Flag 1 ASCII Character flag to identify the eclipse causeM => Moon is cause of eclipseE => Earth is cause of eclipse

This file contains 90-days worth of mission eclipse information for either lunar or earth eclipses.


A sample LRO Mission Eclipse data product is provided as a reference in Appendix B.1-11.

4.1.2.8.4 Accuracy and CompletenessThe data file will consist of every LRO eclipse predictions for the upcoming ninety (90) days and will contain the data centered at one minute increments. The accuracy of this eclipse data is consistent with the predicted ephemeris data based upon the most recent tracking information. The file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.2.9 Lunar Ephemeris

4.1.2.9.1 Product DescriptionThis file contains the Lunar Ephemeris, which is used to update the on-board attitude/orbit flight software 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 separated by a variable length set of blanks. The file contains multiple lines that provide the ephemeris information for the moon’s position and velocity, 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 are defined in the following table

33




DRAFT

Field name Field CharacteristicsTimetag:yearday of year and time of day




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


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


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


first 6 are the whole portions of the X-component of the moon’s velocitylast 3 are the decimal portion of the X-component position


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

Z-Velocity RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3

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

This file contains seven days of moon ephemeris information.


A sample of the Moon Ephemeris data product is provided as a reference in Appendix B.1-12.

4.1.2.9.4 Accuracy and CompletenessThe data file will consist of the lunar position and velocity predictions for the upcoming seven days and will contain the data centered at one minute increments.

4.1.2.10 Orbiter Thruster Maneuver Plans


34




DRAFT

This file contains the data information for the upcoming LRO maneuver related to the required start thruster firing time, the thruster sequence, initial attitude, stop thruster firing time.

4.1.2.10.2 Support DurationFDF will generate this file during all mission phases in preparation for the next scheduled maneuver.

4.1.2.10.3 FormatThis product consists of one file detailing the parameters required to characterize an LRO thruster 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 maneuver data, which can include the thruster to use; the pre-burn attitude; the maneuver start time, the maneuver stop time and duration of the burn; the post-burn lunar orbital elements; the post-burn predicted attitude; the predicted fuel used; the predicted delta-V; the fuel used to date; the remaining LRO fuel; the predicted tank pressure and pressure at the completion of the thruster burn.


A sample of the Orbiter Thruster Maneuver Plan product is provided as a reference in Appendix B.1-13.

4.1.2.10.4 Accuracy and CompletenessThe data file will contain all thruster information related to this upcoming LRO maneuver; it will be accurate to TBD criteria.

4.1.2.11 Orbiter to Earth Range Predicts

4.1.2.11.1 Product DescriptionThis file contains the range and range rate data for the orbiter to the appropriate LRO ground station supporting the LRO mission.

4.1.2.11.2 Support DurationFDF will generate this file during all mission phases in preparation for the next scheduled maneuver.

4.1.2.11.3 FormatThe Orbiter to Earth Range Predict data is formatted as an ASCII file in which the textual data fields that are space delimited. This product is generated such that the time tag information is centered at 1 minute increments.

The file contains a repeating group for each station within the file. Currently there are 5 repeating groups; one for the White Sands station and the other four for the USN stations supporting LRO. The first line of the repeating group is a 4 ASCII character station name. This

35




Need to ID this concept with FDF ; specifically Mark Beckman


Is there such as thing as the lunar orbital elements?


SDO referenced this model; Will LRO use an identical model or another STK FreeFlyer concept


DRAFT

is followed by 1:N lines of station acquisition information. The standard fields and field description are listed in the following table.


timetag information:yearday of year and time of day



range RRRRRRR.dddRRRRRR => 6 ASCII digits for whole range (0 – 999999)ddd => 3 ASCII digits for decimal portion of range (00 – 999)

Range rate RRRRRRR.dddRRRRRR => 6 ASCII digits for whole range (0 – 999999)ddd => 3 ASCII digits for decimal portion of range (00 – 999)


A sample Orbiter to Earth Range Predict data product is provided as a reference in Appendix B.1-14.

4.1.2.11.4 Accuracy and CompletenessThe data file will consist of all station contacts for the upcoming three days and will contain the range information centered at one minute increments. The accuracy of this range data is consistent with the predicted ephemeris data based upon the most recent tracking information. The file data contents will be accurate to the best predictions from the tracking data, which themselves should be accurate to a 1-sigma value (1 mm/sec Doppler (WS1), 3 mm/sec (USN/DSN), 10 m range (All stations)).

4.1.2.12 Orbiter Post Maneuver Report

4.1.2.12.1 Product DescriptionThis file contains the data generated to show a comparison of the predicted and actual performance and provides a calculation of the fuel used and an estimate of the remaining fuel available. 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 which FDF profiles the results of a thruster maneuver.

4.1.2.12.3 Format

36




DRAFT

The report is an ASCII formatted file in which the fields are separated by a variable length set of blanks. The report provides the thruster profile and compares the planned versus actual thruster information, the fuel used and the remaining on-board fuel, and the estimated and actual spacecraft mass following the thruster maneuver.

Thruster Used, Maneuver Start Time, Maneuver Stop Time, Expected Fuel Used, Expected Remaining Fuel, Actual Fuel Used, Actual Remaining Fuel, Propellant Tank Pressure and Temperature; Estimated Spacecraft Mass, and Actual Spacecraft Mass, Projected maneuver and actual maneuver (e.g., expected 50m meters/sec and achieved 49.5 meters/sec) as defined in the following table

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 and time of day



Maneuver Stop Time:yearday of year and time 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

Expected 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

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

37




DRAFT

Field name Field CharacteristicsExpected Spacecraft Mass RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3

first 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 of the Post Orbiter Maneuver Report product is provided as a reference in Appendix B.1-15.

4.1.2.12.4 Accuracy and CompletenessTBR

4.1.2.13 Post Separation Report

4.1.2.13.1 Product DescriptionThis report provides a comparison of the launch separation vector that the launch vehicle support team reports against the launch separation vector that FDF calculates based on the updated launch information.

4.1.2.13.2 Support DurationFDF generates this report only once during the launch and early orbit mission phase, nominally within the first hour of the mission. FDF will also generate this report in support of pre-mission rehearsals that are configured to provide test and training of the launch day support for the LRO mission team.

4.1.2.13.3 FormatThe report is an ASCII formatted file in which the fields are separated by a variable length set of blanks. The report fields provide the comparison between the reported launch vehicle separation vector and the FDF-calculated launch vehicle separation vector (updated to reflect the actual launch epoch). The report is a multi-line file, which contains the two original vectors (and their magnitudes) and then the position and velocity magnitudes of the differences. This information is identified in the following table

Field name Field CharacteristicsLine 1 – from EELV Launch Support Team

38




DRAFT

Field name Field CharacteristicsLV SeparationTime:yearday of year and time of day




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


first 6 are the whole value X-component of the LV separation velocitylast 3 are the decimal portion of the X-component velocity


first 6 are the whole value Y-component of the LV separation velocitylast 3 are the decimal portion of the Y-component velocity


first 6 are the whole value Z-component of the LV separation velocitylast 3 are the decimal portion of the Z-component velocity

LV Position Vector Magnitude

RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 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 Vector Magnitude


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

39




DRAFT

Field name Field CharacteristicsFDF Calculated SeparationTime:yearday of year and time of day




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


first 6 are the whole value X-component of the FDF separation velocitylast 3 are the decimal portion of the X-component velocity


first 6 are the whole value Y-component of the FDF separation velocitylast 3 are the decimal portion of the Y-component velocity


first 6 are the whole value Z-component of the FDF separation velocitylast 3 are the decimal portion of the Z-component velocity

FDF Position Vector Magnitude


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 Vector Magnitude


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 Position Difference


first 6 are the whole portions of the position Delta Magnitudelast 3 are the decimal portion of the position Delta Magnitude

40




DRAFT

Field name Field CharacteristicsMagnitude of the Velocity Difference


first 6 are the whole portions of velocity Delta Magnitudelast 3 are the decimal portion of the Delta Magnitude


A sample of the Post Separation Report product is provided as a reference in Appendix B.1-16.

4.1.2.13.4 Accuracy and CompletenessTBD

4.1.2.14 Predicted LRO Ephemeris File

4.1.2.14.1 Product DescriptionThis file contains predictive LRO ephemeris data for the spacecraft position and velocity information centered at five minute increments. The file is generated in a moon-centered inertial, mean J2000 coordinate reference frame.


4.1.2.14.3 FormatThe Predictive LRO Ephemeris file is an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The file contains the time of the sample, the X,Y, Z position information (given in Kilometers, or Km) and the X, Y, and Z velocity components (given in Kilometers per second, or Km/sec). The file entries are generated at five minute increments. The following table provides a brief description of each field:





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


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

41




DRAFT


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






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


A sample Predictive LRO Ephemeris File data file is provided as a reference in Appendix B-1.17.


4.1.2.15 Predicted Lunar Ground Track File

4.1.2.15.1 Product DescriptionThis file contains the predictive LRO ground track against the lunar surface.


4.1.2.15.3 FormatThe Predictive Lunar Ground Track file is an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The file contains the time of the sample, the lunar Latitude and Longitude position, the LRO altitude, and ground track velocity every 60 seconds. The latitude and longitude information is based on the DE400 reference frame. The LRO altitude is given in Kilometers (or Km), the LRO ground track velocity components given in Kilometers per second, or Km/sec). The file entries are generated at one minute increments. The following table provides a brief description of each field:

Field name Field Characteristics

42




Is this velocity components in the x, y, z directions or the velocity magnitude ?


DRAFT

time information:yearday of year and time of day



Lunar Longitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole degrees of Longitude (0- 360)last 3 are the degree decimal of Longitude (000- 999)

Lunar Latitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 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 => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole portions of the LRO’s altitude (in Km, 000 – 999)last 3 are the decimal portion of the LRO’s altitude (in hundredths of Km, 000 – 999)








A sample LRO Predictive Lunar Ground Track File is provided as a reference in Appendix B-1.18.


4.1.2.16 Definitive Lunar Ground Track File

4.1.2.16.1 Product DescriptionThis file contains the definitive LRO ground track against the lunar surface based on the most recent definitive ephemeris.

43




DRAFT


4.1.2.16.3 FormatThe Definitive Lunar Ground Track file is an ASCII-formatted file in which the fields are separated by a variable length set of blanks. The file contains the time of the sample, the lunar Latitude and Longitude position, the LRO altitude, and ground track velocity every 60 seconds. The latitude and longitude information is based on the DE400 reference frame. The LRO altitude is given in Kilometers (or Km), the LRO ground track velocity components given in Kilometers per second, or Km/sec). The file entries are generated at one minute increments. The following table provides a brief description of each field:




Lunar Longitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole degrees of Longitude (0- 360)last 3 are the degree decimal of Longitude (000- 999)

Lunar Latitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 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 => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole portions of the LRO’s altitude (in Km, 000 – 999)last 3 are the decimal portion of the LRO’s altitude (in hundredths of Km, 000 – 999)








44




Is this velocity components in the x, y, z directions or the velocity magnitude ?


DRAFT

A sample Definitive Lunar Ground Track File is provided as a reference in Appendix B-1.19.


4.1.2.17 Star Tracker Occultation Report

4.1.2.17.1 Product DescriptionThis is a report that includes identified when the star tracker field of view is occulted by the moon.

4.1.2.17.2 Support DurationThe MOC-ADS 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 mission phases.

4.1.2.17.3 FormatThe file is an ASCII formatted file that provides the Star Tracker occultation data file in which the fields are separated by a variable length set of blanks. The report is a multi-line file that contains each instance of when the Star Tracker’s field of view is occulted by the moon. The file contains the occultation start time, the occultation stop time, the occultation duration. The following table provides a description of the fields:

Field name Field CharacteristicsOccultation Start Time:yearday of year and time of day



Occultation Stop Time:yearday of year and time of day



Occultation Duration MMM.mm => 6 ASCII digits with a period between the first 3 and last 2first 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

45




DRAFT


A sample Star Tracker Occultation Report is provided as a reference in Appendix B-1.28

4.1.2.17.4 Accuracy and Completeness

4.1.3 FDF MOC/ADS Products

The following sections provide the details regarding the products that are generated by the attitude determination system that is contained within the LRO MOC facility. The MOC-ADS is developed by the FDF facility and then hosted into the MOC facility, where the LRO operations team uses this system to create another set of products used by project and operations personnel.

4.1.3.1 Attitude Determination Verification Report

4.1.3.1.1 Product DescriptionThis file provides a comparison of the on-board computer (OBC) calculated attitude quaternion versus the ground based calculated attitude quaternion resulting from the MOC-ADS processing of the attitude telemetry. The report is used to verify the performance on the on-board attitude system.

4.1.3.1.2 Support DurationThe MOC-ADS provides this report for all mission phases

4.1.3.1.3 FormatThe file is an ASCII formatted multi-line report that provides the information related to the OBC calculated attitude as compared with a ground-based solution from the MOC-ADS element. The report contains meta-data related to when the report was generated, the start and stop times of the attitude information, and what inputs were used in the calculations. The report also contains the attitude comparison for the time period referenced in the metadata.


A sample Attitude Determination Verification Report file is provided as a reference in Appendix B-1.20.

4.1.3.1.4 Accuracy and CompletenessThe report is accurate to TBR

4.1.3.2 Attitude Slew Plans

4.1.3.2.1 Product DescriptionThis file contains the attitude quaternions for the various orbiter attitude slews required throughout the mission. This file can consist of either one instance of an attitude slew (and thus one quaternion set) or a series of attitude slews (and therefore multiple sets of quaternions).

46




DRAFT

4.1.3.2.2 Support DurationThe MOC-ADS provides this report for all mission phases

4.1.3.2.3 FormatThe file is an ASCII formatted file that provides the attitude quaternions corresponding to a requested attitude slew maneuver. The file can be one line representing a single attitude slew, or it can consist of multiple lines representing a set of attitude slews. For each line, the data consists of a start time, the corresponding off-nadir angle slew and the corresponding attitude quaternion for that slew. The fields are ASCCI text separated by blanks. The following table provides a brief description of each field:

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 and time of day



Off-Nadir Slew Angle RRR.rrr => 6 ASCII characters including the period between the first 3 and last 3first 2 are the whole degrees of requested slew (0- 99)last 3 are the degree decimal of Longitude (000- 999)

Attitude QuaternionsQ1Q2Q3Q4

4 quaternions that represent the attitude of the requested slew; each quaternion has one 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 Attitude Slew Plan file is provided as a reference in Appendix B-1.21.

4.1.3.2.4 Accuracy and CompletenessThe report is accurate to TBR

4.1.3.3 Gyro Calibration Data

4.1.3.3.1 Product DescriptionThis is a report that includes updated parameters for gyroscope calibration table. This report provides an analysis of the gyro, which is also referenced as the inertial reference unit (IRU).


47




DRAFT

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 actual mission phases.

4.1.3.3.3 FormatThe 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 meat-data corresponds to when the report was generated, the start and stop times of the gyro data used in this calibration function. 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 Gyro Calibration Data File is provided as a reference in Appendix B-1.22.


4.1.3.4 HGA Calibration Data

4.1.3.4.1 Product DescriptionThis is a report that includes updated parameters for HGA calibration table.

4.1.3.4.2 Support 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 mission phases.

4.1.3.4.3 FormatThe file is an ASCII formatted file in which the fields are separated by a variable length set of blanks. The file provides the HGA calibration data. The report is a multi-line file that contains both meta-data and HGA calibration data. The meta-data corresponds to when the report was generated, the start and stop times and other information related to the HGA calibration function. The file is generated using the White Sands antenna signal strength over a known time period.


A sample Gyro Calibration Data File is provided as a reference in Appendix B-1.23.

.


48




DRAFT

4.1.3.5 LRO State Vector Table

4.1.3.5.1 Product DescriptionThe LRO State Vector Table provides the predicted set of OD state information for the LRO spacecraft for the upcoming referenced time period, nominally 1-weeks of predicted OD state information. This data is used by the on-board computer to update its attitude flight SW system.

4.1.3.5.2 Support DurationThe MOC-ADS provides this State Vector Table throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.1.3.5.3 FormatThe file is an ASCII formatted file that provides the State Vector data file in which the fields are separated by a variable length set of blanks. 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 other information 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 position information is given in Kilometers (or Km), the LRO velocity components given in Kilometers per second, or Km/sec). The file entries are time centered every TBD minutes. The following table provides a brief description of each field:




X-Position RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole degrees of X-position vector information (0- 999)last 3 are the degree decimal of the X-position (000- 999)

Y-Position RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole degrees of Y-position vector information (0- 999)last 3 are the degree decimal of the Y-position (000- 999)

Z-Position RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3first 3 are the whole degrees of Z-position vector information (0- 999)last 3 are the degree decimal of the Z-Position (000- 999)



49




The Triana sample was generated on 4 hour time centers


Is this file generated by the MOC-ADS element or by the main FDF element (B28 systems)


DRAFT






A sample LRO State Vector Table is provided as a reference in Appendix B-1.24.

.


4.1.3.6 Star Tracker Calibration Data

4.1.3.6.1 Product DescriptionThis is a report that includes updated parameters for Star Tracker calibration table.

4.1.3.6.2 Support DurationThe MOC-ADS provides this Star Tracker 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.3.6.3 FormatThe file is an ASCII formatted file that provides the Star Tracker calibration data file in which the fields are separated by a variable length set of blanks. The report is a multi-line file that contains both meta-data and HGA calibration data. The meta-data corresponds to when the report was generated, the start and stop times and other information related to the Star Tracker calibration function.


A sample Star Tracker Calibration Data File is provided as a reference in Appendix B-1.25.


4.1.3.7 Thruster Calibration Data


50




DRAFT

This is a report that includes updated parameters for thruster calibration table.

4.1.3.7.2 Support 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 mission phases.

4.1.3.7.3 FormatThe file is an ASCII formatted file that provides the Star Tracker calibration data file in which the fields are separated by a variable length set of blanks. The report is a multi-line file that contains both meta-data and HGA calibration data. The meta-data corresponds to when the report was generated, the start and stop times and other information related to the Star Tracker calibration function.


A sample Star Tracker Calibration Data File is provided as a reference in Appendix B-1.26.


4.1.3.8 LRO Momentum Management Unload Plan

4.1.3.8.1 Product DescriptionThis is a report that identifies when the LRO spacecraft will perform a momentum management maneuver.

4.1.3.8.2 Support DurationThe MOC-ADS provides this Momentum Management Unload data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through all mission phases.

4.1.3.8.3 FormatThe file is an ASCII formatted file that provides the requested maneuver commands required to support the momentum management function file in which the fields are separated by a variable length set of blanks. The report is a multi-line file that contains both meta-data and momentum management thruster maneuver information. The meta-data corresponds to when the report was generated, the start and stop times and other information related to the momentum management function.


A sample LRO Momentum Management Unload Plan File is provided as a reference in Appendix B-1.27.

4.1.3.8.4 Accuracy and Completeness51




DRAFT

4.2 STATION PRODUCTS AND DESCRIPTIONS

4.2.1 Space Communication Network Product Descriptions

The following sections provide the details on the interface products generated by the various ground stations that comprise the Space Communications Network used to support the LRO mission.

Question

4.2.1.1 Station Support Schedules

4.2.1.1.1 Product DescriptionThis file is a schedule that contains 1 week of station contacts that support LRO, includes both WS1 and USN contacts. 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 are define, created, reviewed, and modified are covered under the ICD between the LRO Project and the NASA Ground Network (NGN). The basic concepts for the mission schedule identifies three working versions that are used to identify the over all station support schedules for future weeks as noted here:

Strawman Schedule – generated approximately 2.5 week out for that next subsequent Monday week of activities

Update Schedule – generated approximately 1-2 weeks prior to the start of that week’s planned events

Confirmed Schedule – generated to cover the same time period as identified in the previous version of the Update Schedule.

4.2.1.1.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 actual mission and concluding with end-of-mission support.

4.2.1.1.3 FormatThe Station Support Schedule file is an ASCII-formatted file and is consistent with the standards applied 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 configuration identified for the requested station support; the following table provides a brief description of each field:

Field name Field CharacteristicsStation Name 4 ASCII Characters that uniquely identify the station

52




Coordinate w/ SCN Reps to validate field information and correct as requiredn used to support the LRO station contact; where Identified for the requested station s


AS per the NGN ICD Template; or should this be references as GNSO?


(What about DSN schedules for early ops and proficiency ops – Need to determine if part of this ICD or part of an OA/MOU


Add section for DSN Support Schedule and I/F Products


Are the SCN support stations going to generate a NGN Downlink Report as noted in Sect 1.3.2 of NGN ICD?


DRAFT

Field name Field CharacteristicsStart time:yearday of year and time of day



Stop time:yearday of year and time of day



Support Activity Code 4 ASCII Character that identifies the station configuration used to support the LRO station contact; allowable values are: TR1 – TR99

Orbit Number 10 ASCII Characters representing a monotonically increasing orbit counter

Band 2 ASCII Characters representing the support contact type; whereS1 = S-band Supportxx = 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 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.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 data downlink requirements and to support the health and safety commanding for the orbiter and the instrument suite.

4.2.1.2 Station Tracking Data

4.2.1.2.1 Product DescriptionThe Station Tracking Data File provides the LRO Flight Dynamics Facility with the data required to support tracking of the orbiter and generation of orbit and mission products. This data is 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 Universal Tracking Data Format (UTDF) as defined in the STDN Tracking and Acquisition Handbook (STDN-724, 1990).

53




Break this out into 2 separate section; one for WS1/UDN and a separate one for DSN


Need to identify what GNSO uses for Ka-Band Support


DRAFT

The WS1 facility has the ability to provide the tracking data in real-time to support mission critical activities that occur during the WS1 station contact period. These mission critical activities 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 the information that would normally be contained with the UTDF formatted file. As long as data are transmitted in near real time, the file product would not be limited to five-minute durations. In the event of real-time UTDF support, the corresponding data files could be created at hourly intervals. In the event that the station is not able to create a real time connection with FDF, then the station would revert to creating files that are based on capturing five minutes of tracking data.

DSN, which supports LRO through the 34 meter subnet, will provide this data such that it is consistent with the TRK-2-34 format.

The Space Network (SN) supports the LRO mission only during the L&EO mission phase. It provides the data that is captured by TDRSS. The TDRSS tracking data format, a subset of the NASA Universal Tracking Data Format (UTDF), consists of 75 bytes of contiguous information comprising one sample of data. Tracking data messages (TDMs) consist of one or more standard NASA/TDRSS 4800 bit data blocks with each block containing from 1 to 7 tracking samples. The number of samples is a function of simultaneous TDRSS service support.

4.2.1.2.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 actual mission and concluding with end-of-mission support.

4.2.1.2.3 FormatThis data will be consistent with STDN-724. DSN, which supports LRO through the 34 meter subnet, will provide this data such that it is consistent with the TRK-2-34 format. The data file contains the tracking data in a binary form; one datum contains seventy-five (75) bytes of information as identified in the Tracking and Acquisition Handbook. The data records are created at a 60 second interval. The following table provides the fields and field definitions for the station tracking data.

Byte Format Description

1 0D(16) Fixed

2 0A(16) Fixed

3 01(16) Fixed

4-5 ASCII Tracking Data Router 4141=AA=GSFC4444=DD=GSFC

54




DRAFT


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 given in fractions of a circle. To express 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

45 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)

55




DRAFT


48 Binary Pad ID (rcv)

49-50 Discrete Mode-system unique (refer to Table 2)

51 Discrete Data Validity Bit 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

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

56




DRAFT


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; negative indicates the two's complement of the number of samples per second).

55-72 Spare

73 04(16) Fixed

74 04(16) Fixed

75 04(16) Fixed

A sample of the station tracking data file is provided as a reference in Appendix B.2.2

The TDRSS Tracking Data FormatThe TDRSS tracking data format, a subset of the NASA Universal Tracking Data Format (UTDF), consists of 75 bytes of contiguous information comprising one sample of data. Tracking data messages (TDMs) consist of one or more standard NASA/TDRSS 4800 bit data blocks with each block containing from 1 to 7 tracking samples. The number of samples is a function of simultaneous TDRSS service support.


4.2.1.3 Stored Data Files (VC0 – VC3)

4.2.1.3.1 Product DescriptionThis interface consists of the downlinked data that are stored in a file format at a station upon receipt of the spacecraft and instrument housekeeping telemetry and the science measurement data. These data are stored with the fill data (VC63) removed. These files are stored at the ground station using their local storage functionality; this storage takes place before the data are routed to the LRO mission unique equipment (MUE). 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 LRO operations team; this would normally be considered within a contingency support concept.

Additionally, the data can be downlinked as files from the spacecraft and the files would contain the data, as archived onboard the spacecraft, since the last real-time station contact. For LRO, the spacecraft will downlink the VC1 and VC2 data using S-band stations; the VC2 and VC3 data are downlinked using the LRO Ka-Band station at White Sands (WS1).


57




DRAFT

The SCN will provide the Stored Data File throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.1.3.3 FormatOne Stored Data File is created for each virtual channel (VC) and is formatted to contain a series of Virtual Channel Data Units (VCDUs) for that specific VC. For example, one file is created that contains all of the downlinked data for VC0, another file for VC1 data, another for VC2, and a final file for VC3 data. The VCDU format is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052).

A sample Stored Data File is provided as a reference in Appendix B.2.3

4.2.1.3.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed Mission Requirements document (LRO-REQ-00048).

4.2.1.4 Real-time VC0 – VC3 Telemetry Data

4.2.1.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). The station inserts these VCDUs into data packets that contain a SMEX/LEO-T Header format. The realtime data are Reed-Solomon decoded by the station prior to the transfer to the MUE or LRO MOC. Real-time S-Band data are downlinked in either VC0 – VC3 data channels; Ka-Band data are downlinked in either VC2 or VC3 data streams.

4.2.1.4.2 Support DurationThe SCN will provide the real-time VC0 – VC3 data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.1.4.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinked data within a virtual channel data unit (VCDU) formatted structure. The station inserts the VCDU into a structure that has a SMEX/LEO-T header.

A sample real-time VC telemetry stream is provided as a reference in Appendix B.2.4.


4.2.1.5 SCN Station Status Packets

4.2.1.5.1 Product Description58




DSN I/F with SLE Header formats


DRAFT

This interface consists of status packets, which contain the general station information, the downlink performance related to data quality, data statistics, RF status, and uplink time. This information is sent in a CCSDS fixed data packets; each station is assigned a unique APID to provide this station status packet data.

4.2.1.5.2 Support DurationThe SCN will provide the SCN Station Status Packets throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.1.5.3 FormatThe SCN Station Status Packets contain the following information. For each LRO station contact, the station will provide the following data quality statistics every 60 seconds.

Station Identifier

Ka-Band RF Receiver Status Data (only applicable for WS1)Command Time latch for first command byte radiated to LRO (only applicable for stations doing command uplinks to LRO) Performance on the downlink related to data qualityMonitor uplink status and uplink lock (AGC data)Receiver strengthNumber of VCsNumber of CADUsNumber of Reed-Solomon errors decodedFor the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field:

Field name Field CharacteristicsStation Identifier 4 ASCII Characters that uniquely identify the station

Ka-Band RF Receiver Status Data

TBD

Command Time Latchonly applicable for stations doing command uplinks to LRO; would be blank-filled if no commanding; or default time



Downlink data quality TBD

AGC data TBD

Receiver strength TBD

59




Ditto for defining contents






If no commanding, is this not in the status packet? Or blank-filled? Or set to default?


Ned to define this data record and contents


Need to define what their data are Are these data blank for S-Band contacts? Or not there entirely?


DRAFT

Field name Field CharacteristicsNumber of VCs 1 ASCII Character, representing the number of downlinked virtual channels during

this station contact; allowable values are1, 2, 3, 4

Number of CADUs 9 ASCII Characters, representing the total number of downlinked CADUs (this field represents a number and will be formatted to include the comma delimiters between the thousands and millions place hollers; the range is:0 – 9,999,999

Number of Reed-Solomon errors decoded

9 ASCII Characters, representing the total number of correctable R-S errors (this field represents a number and will be formatted to include the comma delimiters between the thousands and millions place hollers; the range is:0 – 9,999,999

symbol to noise ratio TBR

The data is sent via a real time socket connection using the designated Application Identifier as noted in the LRO Telemetry and Command Formats Handbook (431-HDBK-000052).

These data quality statistics are reset before the next station contact. A sample SCN Station Status Packets is provided as a reference in Appendix B.2-5.


4.2.1.6 USN Station Status Packets

4.2.1.6.1 Product DescriptionThis interface consists of status packets, which contain the general station information, the downlink performance related to data quality, data statistics, RF status, and uplink time. This information is sent in a CCSDS fixed data packets; each station is assigned a unique APID to provide this station status packet data.

4.2.1.6.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 actual mission and concluding with end-of-mission support.

4.2.1.6.3 FormatThe USN Station Status Packets contain the following information. For each LRO station contact, the station will provide the following data quality statistics every 60 seconds.

Station Identifier

Command Time latch for first command byte radiated to LRO (only applicable for stations doing command uplinks to LRO) Performance on the downlink related to data qualityMonitor uplink status and uplink lock (AGC data)

60




Ditto for defining content


DRAFT

Receiver strengthNumber of VCsNumber of CADUsNumber of Reed-Solomon errors decodedFor the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field:






AGC data TBD


Number of VCs 1 ASCII Character, representing the number of downlinked virtual channels during this station contact; allowable values are1, 2, 3, 4


Number of Reed-Solomon errors decoded




These data quality statistics are reset before the next station contact. A sample SCN Station Status Packets is provided as a reference in Appendix B.2.5.


4.2.1.7 SCN Weather Data


61




DSN does not provide weather data in a packaged form;












DRAFT

This file contains the weather information per pass, such as the temperature, pressure, and relative humidity every 10 minutes during station contacts.

4.2.1.7.2 Support DurationThe SCN will provide the SCN Weather Data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.1.7.3 FormatThe SCN Weather data is an ASCII formatted, space-delimited, file. The data points are captured at 30 minute increments for the duration of the station contact. It consists of multiple lines in which the first line is the station identifier and then there are 1:N repeating lines that provide the following information:Time reference, temperature, Pressure, Relative Humidity

Station Identifier (consistent with the unique identifier that the station uses to provide other LRO data)

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.0 Pressure (in millibars pressure)Relative humidity (percentage to TDB decimal places)

The following table provides a brief description of each field:

Field name Field CharacteristicsFirst Line of File

Date/Day of Year Xx ASCII Characters with the following format:DATE: YYMMDD DOY: NNN; 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)

DOY => 3 ASCII digits for day of year (1 – 366)

Station Identifier 4 ASCII Characters that uniquely identify the station

Repeating Lines (1:N) of FileTime Reference (UTC Formatted)

=> 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)

62




DRAFT

Field name Field Characteristicstemperature (in Degrees Celsius))

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 of Mercury)

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 3 ASCII characters, which represent the relative humidity (0 – 100)

The file name for the weather product is defined as:

<Station ID><Station AOS Contact Time>.wea

A sample SCN Weather Data file is provided as a reference in Appendix B.2.6.


4.2.1.8 Ka-Band Measurement Data Files (VC3)

4.2.1.8.1 Product DescriptionThis file contains the measurement data files (Raw files after CFDP processing), which are sent from the WS1 station to the LRO MOC. The transfers are handled by the CFDP processing units at the station and at the MOC; these files are transferred post-pass.

4.2.1.8.2 Support DurationThe SCN will provide the Ka-Band Measurement Data Files throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.1.8.3 FormatA sample Ka-Band Measurement data file is provided as a reference in Appendix B.2.7.


4.2.1.9 Ka-Band RF Receiver Data


63




Removed Laser Ranging Transmit Information since this data is not required by either MOC or FDF; the File goes directly to LOLA SOC from LR Station Replaced Transmit File with Ka-Band RF Receiver Data


DRAFT

The Ka-Band RF Receiver Data is a file that contains RF Strength data from Ka-Band receiver that will be used for HGA calibration.

4.2.1.9.2 Support DurationThe WS1 station generates this file for all mission phases.

4.2.1.9.3 FormatThe Ka-Band RF Receiver Data is an ASCII formatted file in which the fields are separated by blanks. The file contains the following data:

Time-Tag RF Signal Strength; the fields are defined in the following table:

Field name Field CharacteristicsTime-Tag 18 ASCII Characters with the following format:

YYYYDOY HHMMSS.mmm; where:YYYY => 4 ASCII digits of year (2008 – 2013)DOY => 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.2.8.


4.2.1.10 CFDP Status Messages

4.2.1.10.1 Product DescriptionThis message contains information related to the connection of CFDP processor located at WS1 ground station to the LRO MOC. Technically, this is not a Space Communications Network generated data file. The data are created from the mission unique equipment, which the LRO project provided to the WS1 facility.

4.2.1.10.2 Support DurationThe SCN will provide the CFDP Status Messages throughout all mission phases, from pre- The CFDP Status Messages are delivered to the LRO MOC on a routine basis or to support mission rehearsals and other project related tests up through the actual mission and concluding with end-of-mission support.

4.2.1.10.3 Format

64




Ned to define content for this file


DRAFT

The CFDP Status Messages contain the current status of the MUE located at the WS1 facility Possible CFDP status: Class 1 or 2Total number of VCDUs received

Breakout by each VCPackets sent by APIDTotal files sent/received successfullyTotal file transmission/reception failuresActive files being transmitted/receivedTotal number of NAKs sent

For a limited number (last 5 or 10 or ?) files:file name (including path name)start timestop timeprogress (% complete)faults encountered (counts of each type)file size

Error counts:file transfers suspendedfile transfers canceledfile transfers abandonedfile transfers ignored

Socket status (connected/not connected)

A sample CFDP Status Message Packet is provided as a reference in Appendix B.2-9.


4.2.1.11 Weekly Laser Ranging Schedule

4.2.1.11.1 Product DescriptionThis data contains information related to which sites are specifically scheduled to perform laser ranging with the LRO spacecraft for the upcoming week and identifies the point of contact information 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 not be performed because of a spacecraft problem.

4.2.1.11.2 Support DurationThis information is supplied for all mission phases. The LR site delivers this data file to the LRO MOC.

4.2.1.11.3 Format

65




DRAFT

The 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 information

A sample Weekly Laser Ranging Schedule file is provided as a reference in Appendix B.2.10.


4.2.1.11.5 TimespanThe Weekly Laser Ranging Schedule contains the data corresponding for the upcoming next several days, or up to a week’s worth of potential laser ranging activities.

4.2.1.11.6 Volume Estimate

4.2.1.11.7 Delivery ScheduleThe laser ranging site provides the Weekly Laser Ranging Schedule on a daily basis approximately 1-2 days before the start of the scheduled laser ranging activities.

4.2.1.11.8 MediumThe laser ranging site provides the Weekly Laser Ranging Schedule via secure FTP to the agreed upon MOC-controlled directory structure approximately 1-2 days before the start of the scheduled laser ranging activities.

4.2.2 Deep Space Network Product Descriptions

The following sections provide the details on the interface products generated specifically by the DSN stations in support of the LRO mission. AS noted earlier, DSN is used for early mission launch critical supports activities and for any mission maneuver. Outside of these supports, DSN is used solely to provide an emergency, 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.

4.2.2.1 DSN Tracking Data

4.2.2.1.1 Product DescriptionThe DSN Tracking Data File provides the LRO Flight Dynamics Facility with the data required to support tracking of the orbiter and generation of orbit and mission products. This data is also transferred to the LRO MOC for eventual distribution to the LOLA SOC.

66




DRAFT

DSN, which supports LRO through the 34 meter subnet, will provide this data such that it is consistent with the TRK-2-34 format.

4.2.2.1.2 Support DurationThe DSN will provide this tracking data file throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.2.1.3 FormatThis data will be consistent with DSN formatted tracking data as identified via the TRK-2-34 format. A sample of the DSN Tracking Data file is provided as a reference in Appendix B.2.11


4.2.2.1.5 TimespanThe DSN Tracking Data file will consist of the tracking data created over the last five minutes during a station contact.

4.2.2.1.6 Volume EstimateTBR

4.2.2.1.7 Delivery ScheduleThe DSN Tracking Data File is delivered at the completion of the five minute duration for each tracking file.

4.2.2.1.8 MediumDSN will electronically deliver the DSN Tracking Data File via a TBR mechanism.

4.2.2.2 DSN Stored Data Files (VC0 – VC3)

4.2.2.2.1 Product DescriptionNominally, DSN delivers received VC data to the LRO MOC in near real-time. The DSN station also stores the downlinked data for up to 72 hours in the event that the LRO FOT requests a retransmission of the data.

This interface consists of the downlinked data that are stored in a file format at a station upon receipt of the spacecraft and instrument housekeeping telemetry and the science measurement data. These data files are stored with the fill data (VC63) removed.

4.2.2.2.2 Support DurationThe DSN will provide the DSN Stored Data File throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

67




DRAFT

4.2.2.2.3 FormatOne DSN Stored Data File is created for each virtual channel (VC) and is formatted to contain a series of Virtual Channel Data Units (VCDUs) for that specific VC. For example, one file is created that contains all of the downlinked data for VC0, another file for VC1 data, another for VC2, and a final file for VC3 data. The VCDU format is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052).

A sample of the DSN Stored Data File is provided as a reference in Appendix B.2.12

4.2.2.2.4 Accuracy and CompletenessThe Stored Data files will be complete and accurate as listed in the LRO Detailed Mission Requirements document (LRO-RQMT-00048).

4.2.2.3 Real-time VC0 – VC3 Telemetry Data

4.2.2.3.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). The station inserts these VCDUs into data packets that contain a SLE Header format. The realtime data are Reed-Solomon decoded by the station prior to the transfer to the LRO MOC. Real-time data are downlinked from any of the VC0 – VC3 data channels.

4.2.2.3.2 Support DurationThe DSN will provide the real-time VC0 – VC3 data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support.

4.2.2.3.3 FormatThe real-time data product for the virtual channel (VC) format is defined in the LRO Telemetry and Command Formats Handbook (LRO-HDBK-000052). The stations insert the downlinked data within a virtual channel data unit (VCDU) formatted structure. The station inserts the VCDU into a structure that has a SLE header.

A sample real-time VC telemetry stream is provided as a reference in Appendix B.2.13.


4.2.2.4 DSN Station Status Packets

4.2.2.4.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. This information is sent in a CCSDS fixed data packets; each station is assigned a unique APID to provide this station status packet data.

68




DRAFT

4.2.2.4.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 actual mission and concluding with end-of-mission support.

4.2.2.4.3 FormatThe DSN Station Status Packets contain the data as specified by the DSN Mon-0158 format. For each LRO station contact, the station will provide the following data quality statistics every 60 seconds.

Station Identifier

Command Time latch for first command byte radiated to LRO (only applicable for stations doing command uplinks to LRO) Performance on the downlink related to data qualityMonitor uplink status and uplink lock (AGC data)Receiver strengthNumber of VCsNumber of CADUsNumber of Reed-Solomon errors decodedFor the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field:






AGC data TBD


Number of VCs 1 ASCII Character, representing the number of downlinked virtual channels during this station contact; allowable values are1, 2, 3, 4


69












DRAFT

Field name Field CharacteristicsNumber of Reed-Solomon errors decoded




These data quality statistics are reset before the next station contact. A sample DSN Station Status Packets is provided as a reference in Appendix B.2.14.


4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONS

This section contains the interface products generated by the seven SOCs. These products are all sent to the LRO Mission Operations Center. The LOLA SOC transmits the LOLA Improved Gravity Model to the Flight Dynamics Facility, and to the LRO MOC, to assist in the improved orbit determination process. Each science center has its own unique subsection to define the specific products that the SOCs generate and send to the MOC.

For products that the SOCs generate, they are normally identified as either command files or specific instrument command sequences; these are command products that need to be sent to the MOC for uplink to the corresponding instrument.

4.3.1 CRaTER SOC Products

This section provides the lower-level information regarding the files sent from the CRaTER SOC to the LRO MOC.

4.3.1.1 CRaTER Activity Request

This is the Command/Procedure request for instrument

4.3.1.1.1 Product DescriptionThe CRaTER SOC generates the CRaTER Activity Request and forwards the inputs to the LRO MOC. The MOC (MPS element) merge the individual SOC Command Requests with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.

70






DRAFT

All commands in the file must be defined in the LRO Telemetry and Command Formats Handbook (431-HDBK-000052). If the command contains submnemonics, they must be specified with the command.

If a timetag is in relative time format, the command or activity is scheduled relative to the start or stop time of an event. If a timetag is in universal time code (UTC) format, the command or activity will occur at the absolute specified time.

4.3.1.1.2 Support DurationSupport will be provided through all mission phases.

4.3.1.1.3 FormatThe command 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) of commands.

A command or activity file can either contain a list of ATS or RTS entries or a STOL command procedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entry for an ATS or RTS file is marked by a semicolon (;). This identifies that anything following the semicolon is treated as a comment and not processed by the mission planning system. Comments can occur anywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command or activity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). A single, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activity is scheduled to occur at the identified time. Only five commands can be specified to occur at the exact same absolute time. This is a limit specified by the LRO Project so that a closely timetagged 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 or activity 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 Instrument Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-1.

The following file-naming convention is used for files transmitted between the various SOC facilities and the LRO MOC. The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:

<instrument id>-<file content><version number>.<file extension>

71




DRAFT

where instrument id = [2 characters]CR for CRaTER

file content = [4 characters] Intent of the instrument loads. These characters will be created by the corresponding SOC to identify the type of command 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 received from SOC; it will be named for the input file type:

RTS for relative time sequenceATS for absolute time sequencePROC for procedure

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 Instrument Reset Timeline

4.3.1.2.1 Product DescriptionThis is a file that contains one (1) week of UTC times when the CRaTER science team wishes to perform the power reset on the CRaTER instrument.


4.3.1.2.3 FormatThe CRaTER Instrument Reset Timeline consists of the times in the upcoming week, when the instrument will perform a power rest; the fields in the file are incrementing time-ordered. The fields contained within this file are defined as time; where the fields are defined in the following table




A sample CRaTER Instrument Reset Timeline is provided in Appendix B, Figure B.3-2

72




DRAFT


4.3.2 DLRE SOC Products

This section provides the lower-level information regarding the files sent from the DLRE SOC to the LRO MOC.

4.3.2.1 DLRE Command Request

This is the Command/Procedure request for instrument

4.3.2.1.1 Product DescriptionThe DLRE SOC generates the DLRE Command Request and forwards this input file to the LRO MOC. The MOC (MPS element) merge the individual SOC Command Requests with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.







73




DRAFT



A sample DLRE Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-3



where instrument id = [2 characters]DL for DLRE






4.3.2.2 DLRE FSW Load

4.3.2.2.1 Product DescriptionThis file contains the FSW image and tables for the specified instrument; it contains the tested and verified files that the SOC will send on an as needed basis, as required to correct/update instrument Flight Software table and/or files.

The DLRE SOC facility generates its unique FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merge the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.

74




DRAFT


4.3.2.2.3 FormatThe DLRE Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting 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 of the 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 otherwise ignored. It is intended as a comment to identify the load.

The second line is the mission information line, which consists of several comma-separated fields, 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 if this field has one of the values SWAPBYTES or UI085.



where instrument id = [2 characters]DL for DLRE



file extension = [3–4 characters] Standard file extension for all input files received from a SOC; it will be named for the input file type:

IFTU for Instrument FSW Table Update

75




DRAFT

A sample DLRE Instrument FSW Load is provided in Appendix B, Figure B.3-4


4.3.3 LAMP SOC Products

This section provides the lower-level information regarding the files sent from the LAMP SOC to the LRO MOC.

4.3.3.1 LAMP Command Request

This is the Command/Procedure request for instrument.

4.3.3.1.1 Product DescriptionThe LAMP SOC generates the LAMP Command Request and forwards this input file to the LRO MOC. The MOC (MPS element) merge the individual SOC Command Requests with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.






If the file is an ATS file, it contains a header entry followed by any number of command or activity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). A single, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activity is scheduled to occur at the identified time. Only five commands can be specified to occur at the

76




DRAFT

exact same absolute time. This is a limit specified by the LRO PROJECT so that a closely timetagged 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. The following file-naming convention is used for files transmitted between the various SOC facilities and the LRO MOC. The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:


where instrument id = [2 characters]LA for LAMP





A sample LAMP Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-5.


4.3.3.2 LAMP HV Command Sequence

4.3.3.2.1 Product DescriptionThis file contains the command sequence(s) to either disable or enable the LAMP High Voltage.


4.3.3.2.3 Format

77




DRAFT

The file format consists of the time value, command mnemonic and sun-mnemonic used to enable or disable the LAMP High Voltage. The fields of this file are defined in the following table:




Command Mnemonic LAMP HV

Command Sub-Mnemonic On/Off

A sample LAMP HV Command Sequence is provided in Appendix B, Figure B.3-6


4.3.3.3 LAMP Instrument FSW Load


The LAMP SOC facility generates its unique FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merge the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.


4.3.3.3.3 FormatThe LAMP Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion.



78




DRAFT






where instrument id = [2 characters]LA for LAMP




IFTU for Instrument FSW Table UpdateA sample LAMP Instrument FSW Load is provided in Appendix B, Figure B.3-7


4.3.4 LEND SOC Products

This section provides the lower-level information regarding the files sent from the LEND SOC to the LRO MOC.

4.3.4.1 LEND Command Request



79




DRAFT

The LAMP SOC generates the LEND Command Request and forwards this input file to the LRO MOC, specifically the MPS element. The MPS element merges the individual SOC Command Requests with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.






If the file is an ATS file, it contains a header entry followed by any number of command or activity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). A single, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activity is scheduled to occur at the identified time. Only five commands can be specified to occur at the exact same absolute time. This is a limit specified by the LRO PROJECT so that a closely timetagged 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. The following file-naming convention is used for files transmitted between the various SOC facilities and the LRO MOC. The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:


80




DRAFT

where instrument id = [2 characters]LE for LEND





A sample LEND Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-8.


4.3.4.2 LEND Instrument FSW Load


The LEND SOC facility generates its unique FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merge the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.


4.3.4.2.3 FormatThe LEND Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion.


81




DRAFT







where instrument id = [2 characters]LE for LEND




IFTU for Instrument FSW Table UpdateA sample LEND Instrument FSW Load is provided in Appendix B, Figure B.3-9.


4.3.5 LOLA SOC Products

This section provides the lower-level information regarding the files sent from the LOLA SOC to the LRO MOC.

4.3.5.1 LOLA Command Request


82




DRAFT

4.3.5.1.1 Product DescriptionThe LOLA SOC generates the LOLA Command Request and forwards this input file to the LRO MOC, specifically the MPS element. The MPS element merges the individual SOC Command Requests with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.






If the file is an ATS file, it contains a header entry followed by any number of command or activity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). A single, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activity is scheduled to occur at the identified time. Only five commands can be specified to occur at the exact same absolute time. This is a limit specified by the LRO PROJECT so that a closely timetagged subsequent command is not skipped erroneously because of timing problems.




83




DRAFT


where instrument id = [2 characters]LO for LOLA





A sample LOLA Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-10.


4.3.5.2 LOLA Gravity Model or Improved Lunar Gravity Model

4.3.5.2.1 Product DescriptionThe LOLA Gravity Model is a file that contains the updated Lunar Gravity Model that the LOLA science team generates from its internal data processing. This file is sent to both the Flight Dynamics Facility and to the LRO MOC.

This data contains an improved lunar gravity model based on the continual processing of the correlated laser range one-way transmit times. The LOLA SOC provides this data to FDF approximately every 3 months. FDF will use the improved Lunar Gravity Model to reprocess the orbit data and to create new definitive SPICE File and ephemeris information.

4.3.5.2.2 Support DurationThis information is supplied only post-launch. The LOLA SOC delivers this data file to the LRO MOC and to the LRO’s FD facility.

4.3.5.2.3 FormatA sample Improved Lunar Gravity Model data file is provided as a reference in Appendix B.3-11.


84




DRAFT

4.3.5.3 LOLA Instrument FSW Load


The LOLA SOC facility generates its unique FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merges the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.


4.3.5.3.3 FormatThe LOLA Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion. The LOLA Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion.







<instrument id>-<file content><version number>.<file extension>85




DRAFT





IFTU for Instrument FSW Table UpdateA sample LOLA Instrument FSW Load is provided in Appendix B, Figure B.3-12.


4.3.5.4 LOLA Processed OD Information

4.3.5.4.1 Product DescriptionThis file contains the LOLA–calculated Orbit Determination from data processing based on the telemetry that LOLA from the LRO MOC as past of the real-time and post-pass s/c and instrument housekeeping and measurement telemetry.


4.3.5.4.3 FormatThe LOLA Processed OD Information consists of TBR information.

A sample LOLA Processed OD Information is provided in Appendix B, Figure B.3-13.

The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:



file content = [4 characters] Intent of the instrument loads. These characters will be created by the corresponding SOC to identify file contents

86




Coordinate w/ LOLA SOC (Greg) to define what the parameters are for this product.


DRAFT



txt => for textual file information


4.3.5.5 LOLA Target Requests

4.3.5.5.1 Product DescriptionThis is a file that contains target request for LOLA imaging. This information is used to develop the attitude slew plan for the spacecraft.

4.3.5.5.2 Support DurationTBR

4.3.5.5.3 FormatThe LOLA Target Requests consists of TBR information; most likely time values and lunar lat/long position (or maybe an attitude quaternion representing the specific lunar Lat/Long position). The fields are defined in the following table:




Lunar Latitude (? – TBR) 6 ASCII Characters representing the targeted Lunar Latitude; wherefirst 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 characters represent the decimal portion for lunar latitude (0 – 999)

Lunar Longitude (? – TBR)) 6 ASCII Characters representing the targeted Lunar Longitude; ; wherefirst 3 character represent the whole decimal value of longitude (0 -360)Next character is the decimal separatorNext 2 characters represent the decimal portion for lunar longitude (0 – 999)


87




Coordinate w/ LOLA SOC (Greg) to define what the parameters are for this product.


DRAFT







A sample LOLA Target Requests File is provided in Appendix B, Figure B.3-14.


4.3.6 LROC SOC Products

This section provides the lower-level information regarding the files sent from the LROC SOC to the LRO MOC.

4.3.6.1 LROC Instrument Initialization Command Sequence

4.3.6.1.1 Product DescriptionThis file is the command load that LROC SOC uses to initialize the LROC instrument. This file is delivered electronically to the LRO MOC. Eventually, the MPS element merges this instrument initialization command request with other command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.




88




DRAFT

4.3.6.1.3 FormatA command or activity file can either contain a list of ATS or RTS entries or a STOL command procedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entry for an ATS or RTS file is marked by a semicolon (;). This identifies that anything following the semicolon is treated as a comment and not processed by the mission planning system. Comments can occur anywhere with the file.

If the file is an ATS file, it contains a header entry followed by any number of command or activity entries. The commands or activities must be in UTC format (yyyy:ddd:hh:mm:ss). A single, line-feed character (ASCII 10) delimits lines within the file. An ATS command or activity is scheduled to occur at the identified time. Only five commands can be specified to occur at the exact same absolute time. This is a limit specified by the LRO project so that a closely timetagged 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. The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:


where instrument id = [2 characters]LR for LROC





A sample LROC Instrument Initialization Command Sequence (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-15.


89




DRAFT

4.3.6.2 LROC Daily Command Sequence

4.3.6.2.1 Product DescriptionThis file is the text version of daily LROC sequence that identifies times of imaging and other instrument-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 the LROC SOC transmitted within the binary command load file referenced in the previous subsection.



4.3.6.2.3 FormatA command or activity file can either contain a list of ATS or RTS entries or a STOL command procedure. The ATS and RTS file will be an ASCII comma-delimited file. The end of an entry for an ATS or RTS file is marked by a semicolon (;). This identifies that anything following the semicolon is treated as a comment and not processed by the mission planning system. Comments can occur anywhere with the file.



An RTS command or activity is scheduled relative to the start or stop time of an event. The filename consists of eight characters; it also contains a three- or four-character file extension name. There is a hyphen (-) between the first two fields and a period (.) between the last two fields. The form of the filename is as follows:



90




DRAFT





A sample LROC Daily Command Sequence (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-16.


4.3.6.3 LROC Instrument FSW Load


The LROC SOC facility generates its unique FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merges the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.


4.3.6.3.3 FormatThe LROC Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion. The LOLA Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion.



91




DRAFT










IFTU for Instrument FSW Table UpdateA sample LROC Instrument FSW Load is provided in Appendix B, Figure B.3-17.


4.3.6.4 LROC Target Request

4.3.6.4.1 Product DescriptionThis is file that contains target request for LROC imaging; the MOC uses this information to develop the attitude slew plan.


4.3.6.4.2 Support Duration92




DRAFT

Support will be provided through all mission phases.

4.3.6.4.3 FormatThe file contains the time of the requested LROC target and a corresponding lunar latitude and lunar longitude; the fields are defined in the following table:




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)







txt => for textual filesA sample LROC Target Request is provided in Appendix B, Figure B.3-18.


4.3.7 Mini-RF SOC Products

This section provides the lower-level information regarding the files sent from the Mini-RF SOC to the LRO MOC.

93




DRAFT


4.3.7.1 Mini-RF Load Files


The Mini-RF SOC facility generates its FSW load request and forwards the image file to the LRO MOC. The MOC (MPS element) merges the individual SOC Instrument FSW Loads with command input for the spacecraft and orbiter health and safety commands and any specific maneuver commands based on mission profile support phases.


4.3.7.1.3 FormatThe Instrument FSW Load consists of the complete file/table image to be re-loaded, or a starting address, number of bytes to load and then the new table/file image portion.







94




DRAFT


where instrument id = [2 characters]RF for Mini-RF




IFTU for Instrument FSW Table UpdateA sample Mini-RF Load File is provided in Appendix B, Figure B.3-19.


4.3.7.2 Mini-RF Command Timeline

4.3.7.2.1 Product DescriptionThis file contains a set of command sequences that the MOC uses to create a daily load for uplink to the Mini-RF instrument.



4.3.7.2.3 FormatThe Mini-RF Command Timeline consists of the complete set of commands used on-board the LRO spacecraft to manage the Mini-RF instrument.



where instrument id = [2 characters]RF for Mini-RF

95




DRAFT





A sample Mini-RF Command Timeline is provided in Appendix B, Figure B.3-20.


4.4 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONS

This section contains the interface products generated by the LRO MOC. In some cases, these products were originally created by the LRO Flight Dynamics Facility and initially transferred to the LRO MOC. The LRO MOC then controls the delivery of these files to the science centers and the Planetary Data System (PDS) facility.

4.4.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS

This section provides the details related to the products that the LRO MOC transmits to each individual science center. Table 4-2 provides a cross reference between the logical products that the MOC transmits and the intended recipients; the table can be used by the readers to determine which products a specific SOC receives. Further information is then provided within subsequent subsections.

Table 4-2. MOC Products Transmitted to Various LRO SOC Facilities

Product ID

Product Name Product Description

Original Source Section

Reference

CR

aTER

Diviner

LAM

P

LEND

LOLA

LRO

C

Mini-R

F

MOC-1 Beta Angle Predicts

File containing the beta-angle predicts for the next 5 years. Data is consistent with predicted ephemeris information, one predict every 2 hrs.

FDFSection 4.1.2.2

● ● ● ● ● ● ●

MOC-3 Clock Correlation File

File containing a daily log of spacecraft to ground correlation times with amount of adjustments

MOCB.4.1

● ● ● ● ● ● ●

96




DRAFT

Product ID



Reference

CR

aTER

Diviner

LAM

P

LEND

LOLA

LRO

C

Mini-R

F

MOC-4 CRaTER - Spacecraft HK Data File

File containing selected spacecraft telemetry parameters used by the instrument. Includes information such as attitude, spacecraft temperatures, etc

s/c4.4.1.1.3

●

MOC-5 CRaTER HK Data Files

File containing stored housekeeping data from instrument

s/c4.4.1.1.4

●

MOC-6 CRaTER Raw Measurement Data Files

Raw measurement data files after CFDP processing

s/c 4.4.1.1.5

●

MOC-7 CRaTER Real-time VC0 HK data

Either selected APIDs or entire full VC0 data stream

s/c 4.4.1.1.6

●

MOC-8 Daily Command Load

Text version of the daily command load

s/c B.4.6

● ● ● ● ● ● ●

MOC-9 Definitive LRO Ephemeris File

File containing 1 week of definitive vectors with an interval of 60 seconds. Format is selenographic or Moon-Centered Mean J2000

FDF4.1.2.3

● ● ● ● ● ●

MOC-10 DLRE - Spacecraft HK Data File


s/c 4.4.1.2.5

●

MOC-11 DLRE HK Data Files


s/c 4.4.1.2.6

●

MOC-12 DLRE Raw Measurement Data Files


s/c 4.4.1.2.7

●

MOC-13 DLRE Real-time VC0 HK data


s/c 4.4.1.2.8

●

MOC-14 Ground Network Weather Data

File for each pass that contains weather information (Temperature, Pressure, and Rel. Hum) every 10 minutes during station contacts.

GN Station4.2.1.7

●

97




DRAFT

Product ID



Reference

CR

aTER

Diviner

LAM

P

LEND

LOLA

LRO

C

Mini-R

F

MOC-15 LAMP - Spacecraft HK Data File


s/c 4.4.1.3.5

●

MOC-16 LAMP HK Data Files


s/c 4.4.1.3.6

●

MOC-17 LAMP Raw Measurement Data Files


s/c 4.4.1.3.7

●

MOC-18 LAMP Real-time VC0 HK data


s/c 4.4.1.3.8

●

MOC-19 Laser Range Transmit Information

File containing laser pulse transmit times along with associated weather information

Ground Network

●

MOC-21 LEND - Spacecraft HK Data File


s/c 4.4.1.4.5

●

MOC-22 LEND HK Data Files


s/c 4.4.1.4.6

●

MOC-23 LEND Raw Measurement Data Files


s/c 4.4.1.4.7

●

MOC-24 LEND Real-time VC0 HK data


s/c 4.4.1.4.8

●

MOC-25 LOLA - Spacecraft HK Data File


s/c 4.4.1.5.5

●

MOC-26 LOLA HK Data Files


s/c 4.4.1.5.6

●

MOC-27 LOLA Raw Measurement Data Files


s/c 4.4.1.5.7

●

98




Product MOC-19 does go into or out of the MOC, but goes directly from LR site to LOLA


DRAFT

Product ID



Reference

CR

aTER

Diviner

LAM

P

LEND

LOLA

LRO

C

Mini-R

F

MOC-28 LRO SPICE Files Predicts

SPICE files containing predict ephemeris information for LRO

FDF ● ● ● ● ● ● ●

MOC-29 LROC - Spacecraft HK Data File


s/c 4.4.1.6.7

●

MOC-30 LROC HK Data Files


s/c 4.4.1.6.8

●

MOC-31 LROC Raw Measurement Data Files


s/c 4.4.1.6.9

●

MOC-32 Lunar Orbit Ascending & Descending Node Predicts

File containing 1-week worth of nodal crossing predicts.

FDF4.1.2.6

● ● ● ● ● ● ●

MOC-33 Lunar Terminator Crossing Predicts

File containing 1-week worth of terminator predicts.

FDF ● ● ● ● ● ●

MOC-34 Mini-RF - Spacecraft HK Data File


s/c 4.4.1.7.9

●

MOC-35 Mini-RF HK Data Files


s/c 4.4.1.7.10

●

MOC-36 Mini-RF Operations Opportunity

File containing potential operations opportunity for Mini-RF

s/c 4.4.1.7.11

●

MOC-37 Mini-RF Raw Measurement Data Files


s/c 4.4.1.7.12

●

MOC-38 Mission Eclipse Predicts

File contains 90-days worth of mission eclipse predicts; information includes entry/exit times for each period. File will also include lunar eclipse times

FDF4.1.2.8

● ● ● ● ● ●

99




DRAFT

Product ID



Reference

CR

aTER

Diviner

LAM

P

LEND

LOLA

LRO

C

Mini-R

F

MOC-39 Post-Maneuver Spacecraft Mass

File will contain current estimate of spacecraft mass. Estimate will be updated to reflect fuel usage after each maneuver

FDF4.1.2.12

●

MOC-40 Predicted LRO Ephemeris File

File containing 30 days worth of ephemeris predicts every 5 minutes. Format of ephemeris is Moon-Centered Mean J2000

FDF4.1.2.14

● ● ● ● ● ●

MOC-41 Predicted Lunar Ground Track File

File containing the Lat/Long position, altitude, ground track velocity every 60 seconds

FDF4.1.2.15

● ● ● ● ● ● ●

MOC-42 Raw Attitude Data File

File containing spacecraft telemetry points from gyro, star tracker, ACS processing regarding spacecraft attitude

s/cB.4.30

● ● ● ● ● ● ●

MOC-43 Raw Tracking Data Files

File containing the UTDF tracking information from each GN support

Stations4.2.1.2 and4.2.2.1

●

MOC-47 LRO SPICE Files Definitive

SPICE files containing definitive ephemeris information for LRO

FDF ● ● ● ● ● ● ●

MOC-xx50

Predicted Definitive Lunar Ground Track File

File containing the Lat/Long position, altitude, ground track velocity every 60 seconds

FDF4.1.2.16

●

4.4.1.1 MOC PRODUCTS FOR CRaTER

4.4.1.1.1 LRO Beta Angle PredictsThe Beta Angle Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.2 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.5 provides the representation of a sample product.

4.4.1.1.2 Clock Correlation File4.4.1.1.2.1 Product Description

100




DRAFT

This file contains the daily log of spacecraft to ground correlation times with amount of adjustments.

4.4.1.1.2.2 Support Duration


4.4.1.1.2.3 Format

The Clock Correlation File consists of the complete set of clock updates sent to the LRO spacecraft to keep the on-board clock synchronized to UTC. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:

<File name><version number>.<file extension>

where File Name = [6 Characters]ClkCor


file extension = [3characters] Standard file extension for all input files received from a SOC; it will be named for the input file type:

txt for text filesA sample Clock Correlation File is provided in Appendix B, Figure B.4-1.

4.4.1.1.2.4 Accuracy and Completeness

Required accuracy is 100-percent fidelity of received data, which is best available.

4.4.1.1.3 CRaTER - Spacecraft Housekeeping Data File4.4.1.1.3.1 Product Description

This file contains the selected spacecraft telemetry parameters used by the instrument; it includes information such as attitude, spacecraft temperatures, etc. Once the SOC identifies the requested telemetry points, the corresponding APIDs will be extracted and archived in separate file for the instruments.



4.4.1.1.3.3 Format

The CRaTER - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the CRaTER SOC has identified as being required to support its internal SOC processing.

101




DRAFT

A sample CRaTER - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-2.



4.4.1.1.3.5 Timespan

The LRO MOC creates this file on a pass-by-pass basis; the contents of this file correspond to the spacecraft telemetry downlinked from the previous pass. .

4.4.1.1.3.6 Volume Estimate

Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested.

4.4.1.1.3.7 Delivery Schedule

The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass.

4.4.1.1.3.8 Medium

The MOC will electronically transfer the CRaTER - Spacecraft Housekeeping Data File to the CRaTER SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [9 Characters]CR_LROTLM



txt for text files

4.4.1.1.4 CRaTER Housekeeping Data Files4.4.1.1.4.1 Product Description

This file contains the stored CRaTER instrument telemetry data.

102




DRAFT



4.4.1.1.4.3 Format

The CRaTER Housekeeping Data File consists of the complete set of CRaTER instrument telemetry values.

A sample CRaTER Housekeeping Data File is provided in Appendix B, Figure B.4-3.






Each file size and volumes are TBR.



4.4.1.1.4.8 Medium

The MOC will electronically transfer the CRaTER - Spacecraft Housekeeping Data File to the CRaTER SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]CR_HKP



txt for text files

103




Coordinate w/ SOC to determine the volume estimate for their on-board recorded file sizes


DRAFT

4.4.1.1.5 CRaTER Raw Measurement Data Files4.4.1.1.5.1 Product Description

This file contains the raw measurement data files after CFDP processing.



4.4.1.1.5.3 Format

The CRaTER Raw Measurement Data Files consists of the complete set of CRaTER instrument measurement telemetry as noted in the CRaTER Instrument ICD.

A sample CRaTER Raw Measurement Data Files is provided in Appendix B, Figure B.4-4.




The LRO MOC creates this file on a pass-by-pass basis; the contents of this file correspond to the spacecraft telemetry downlinked from the previous pass.




The LRO MOC will transfer this file to the corresponding CRaTER SOC at the completion of a downlinked pass.

4.4.1.1.5.8 Medium

The MOC will electronically transfer the CRaTER Raw Measurement Data Files to the CRaTER SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]CR_INS


104




DRAFT


txt for text files

4.4.1.1.6 CRaTER Real-time VC0 housekeeping data4.4.1.1.6.1 Product Description

The CRaTER Real-time VC0 housekeeping data consists of either selected APIDs or the entire full VC0 data stream.



4.4.1.1.6.3 Format

The CRaTER Real-time VC0 housekeeping data consists of the complete set of telemetry mnemonics from either selected APIDs or all APIDs from the VC0 data stream.

A sample CRaTER Real-time VC0 housekeeping data is provided in Appendix B, Figure B.4-5.









4.4.1.1.6.8 Medium

The MOC will electronically transfer the CRaTER Real-time VC0 housekeeping data to the CRaTER SOC during the real-time station contact. The telemetry and command component in the LRO MOC (e.g., ITOS) initiates the transfer via a socket connection.

4.4.1.1.7 Daily Command Load4.4.1.1.7.1 Product Description

105




DRAFT

This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft.



4.4.1.1.7.3 Format

The Daily Command Load consists of the complete textual set of integrated commands sent to the LRO spacecraft. This integrated command load consists of spacecraft housekeeping commands to manage the LRO health and safety and the set of instrument commands that a corresponding SOC had previously sent to the LRO MOC for uplink to the spacecraft.

A sample Daily Command Load is provided in Appendix B, Figure B.4-6.




The LRO MOC creates this file on a daily basis; the contents of this file correspond to the previous day’s command load from 0000Z of the previous day to 0000Z of the current day. .


Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create.


The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.

4.4.1.1.7.8 Medium

The MOC will electronically transfer the Daily Command Load to the various SOCs on a daily basis. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LROCMD


106




DRAFT


txt for text files

4.4.1.1.8 Definitive LRO Ephemeris FileThe Definitive LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.3 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.6 provides a representation of the sample product.

4.4.1.1.9 LRO SPICE Files DefinitiveThe LRO SPICE Files Definitive is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.4 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.7 provides a representation of the sample product.

4.4.1.1.10 LRO SPICE Files PredictsThe LRO SPICE Files Predicts is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.5 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.8 provides a representation of the sample product.

4.4.1.1.11 Lunar Orbit Ascending/Descending Node PredictsThe Lunar Orbit Ascending/Descending Node Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.6 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.9 provides a representation of the sample product.

4.4.1.1.12 Lunar Terminator Crossing PredictsThe Lunar Terminator Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.7 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.10 provides a representation of the sample product.

4.4.1.1.13 Mission Eclipse PredictsThe Mission Eclipse Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.8 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.11 provides a representation of the sample product.

4.4.1.1.14 Predicted LRO Ephemeris File

107




DRAFT

The Predicted LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.14 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.17 provides a representation of the sample product.

4.4.1.1.15 Predicted Lunar Ground Track FileThe Predicted Lunar Ground Track File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.15 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.18 provides a representation of the sample product.

4.4.1.1.16 Raw Attitude Data FileThe Raw Attitude Data File is originally created by the MOC Telemetry and command system on a daily basis; it contains spacecraft telemetry points from gyro, star tracker, ACS processing regarding spacecraft attitude. Section 5 provides the information related to the product description, update frequency, and format concepts; Appendix B.4.30 provides a representation of the sample product.

4.4.1.2 MOC PRODUCTS FOR DLRE

4.4.1.2.1 Beta Angle PredictsThe Beta Angle Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.2 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.5 provides the representation of a sample product.





4.4.1.2.2.3 Format

The Clock Correlation File consists of the complete set of clock updates sent to the LRO spacecraft to keep the on-board clock synchronized to UTC.

A sample Clock Correlation File is provided in Appendix B, Figure B.4-1.



4.4.1.2.2.5 Timespan108




Need to define this from the MOC Internal Section; currently TBS


DRAFT

The LRO MOC creates this file on a daily basis; the contents of this file correspond to the previous day’s clock updates from 0000Z of the previous day to 0000Z of the current day. .




The SOCs will send a new set of spacecraft instrument commands whenever necessary. When the SOC is ready to send a new instrument command request, the SOCs will send an e-mail notification to the operations team (TBR – or will the SOC simply FTP (or sFTP or sCPY) the file to an agreed-upon file directory structure.

4.4.1.2.2.8 Medium

The MOC will electronically transfer the Clock Correlation file to the various SOCs on a daily basis. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:





txt for text files





4.4.1.2.3.3 Format

The Daily Command Load consists of the complete textual set of integrated commands sent to the LRO spacecraft. This integrated command load consists of spacecraft housekeeping

109




DRAFT

commands to manage the LRO health and safety and the set of instrument commands that a corresponding SOC had previously sent to the LRO MOC for uplink to the spacecraft.










4.4.1.2.3.8 Medium






txt for text files


110




DRAFT

4.4.1.2.5 DRLE - Spacecraft Housekeeping Data File4.4.1.2.5.1 Product Description




4.4.1.2.5.3 Format

The DRLE - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

A sample DRLE - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-7.









4.4.1.2.5.8 Medium

The MOC will electronically transfer the DRLE - Spacecraft Housekeeping Data File to the DRLE SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


111




DRAFT

where File Name = [9 Characters]DL_LROTLM



txt for text files

4.4.1.2.6 DRLE Housekeeping Data Files4.4.1.2.6.1 Product Description

This file contains the stored DRLE instrument telemetry data.



4.4.1.2.6.3 Format

The DRLE Housekeeping Data File consists of the complete set of DRLE instrument telemetry values.

A sample DRLE Housekeeping Data File is provided in Appendix B, Figure B.4-8.









4.4.1.2.6.8 Medium

The MOC will electronically transfer the DRLE - Spacecraft Housekeeping Data File to the DRLE SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted

112






DRAFT

from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]DL_HKP



txt for text files

4.4.1.2.7 DRLE Raw Measurement Data Files4.4.1.2.7.1 Product Description




4.4.1.2.7.3 Format

The DRLE Raw Measurement Data Files consists of the complete set of DRLE instrument measurement telemetry as noted in the DRLE Instrument ICD.

A sample DRLE Raw Measurement Data Files is provided in Appendix B, Figure B.4-9.








113




DRAFT

The LRO MOC will transfer this file to the corresponding DRLE SOC at the completion of a downlinked pass.

4.4.1.2.7.8 Medium

The MOC will electronically transfer the DRLE Raw Measurement Data Files to the DRLE SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]DL_INS



txt for text files

4.4.1.2.8 DRLE Real-time VC0 housekeeping data4.4.1.2.8.1 Product Description

The DRLE Real-time VC0 housekeeping data consists of either selected APIDs or the entire full VC0 data stream.



4.4.1.2.8.3 Format

The DRLE Real-time VC0 housekeeping data consists of the complete set of telemetry mnemonics from either selected APIDs or all APIDs from the VC0 data stream.

A sample DRLE Real-time VC0 housekeeping data is provided in Appendix B, Figure B.4-10.





114




DRAFT





4.4.1.2.8.8 Medium

The MOC will electronically transfer the DRLE Real-time VC0 housekeeping data to the DRLE SOC during the real-time station contact. The telemetry and command component in the LRO MOC (e.g., ITOS) initiates the transfer via a socket connection.






115




DRAFT

4.4.1.2.14 Predicted LRO Ephemeris FileThe Predicted LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.14provides the information related to the product description, update frequency, and format concepts; Appendix B.1.16 provides a representation of the sample product.



4.4.1.3 MOC PRODUCTS FOR LAMP






4.4.1.3.2.3 Format





116






DRAFT







4.4.1.3.2.8 Medium






txt for text files





4.4.1.3.3.3 Format

117




DRAFT











4.4.1.3.3.8 Medium






txt for text files

4.4.1.3.4 Definitive LRO Ephemeris FileThe Definitive LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section

118




DRAFT

4.1.2.3 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.6 provides a representation of the sample product.

4.4.1.3.5 LAMP - Spacecraft Housekeeping Data File4.4.1.3.5.1 Product Description




4.4.1.3.5.3 Format

The LAMP - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

A sample LAMP - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-11.









4.4.1.3.5.8 Medium

The MOC will electronically transfer the LAMP - Spacecraft Housekeeping Data File to the LAMP SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three

119




DRAFT

character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [9 Characters]LA_LROTLM



txt for text files

4.4.1.3.6 LAMP Housekeeping Data Files4.4.1.3.6.1 Product Description

This file contains the stored LAMP instrument telemetry data.



4.4.1.3.6.3 Format

The LAMP Housekeeping Data File consists of the complete set of LAMP instrument telemetry values.

A sample LAMP Housekeeping Data File is provided in Appendix B, Figure B.4-12.









4.4.1.3.6.8 Medium120






DRAFT

The MOC will electronically transfer the LAMP - Spacecraft Housekeeping Data File to the LAMP SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LA_HKP



txt for text files

4.4.1.3.7 LAMP Raw Measurement Data Files4.4.1.3.7.1 Product Description




4.4.1.3.7.3 Format

The LAMP Raw Measurement Data Files consists of the complete set of LAMP instrument measurement telemetry as noted in the LAMP Instrument ICD.

A sample LAMP Raw Measurement Data Files is provided in Appendix B, Figure B.4-13.







121




DRAFT


The LRO MOC will transfer this file to the corresponding LAMP SOC at the completion of a downlinked pass.

4.4.1.3.7.8 Medium

The MOC will electronically transfer the LAMP Raw Measurement Data Files to the LAMP SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LA_INS



txt for text files

4.4.1.3.8 LAMP Real-time VC0 housekeeping data4.4.1.3.8.1 Product Description

The LAMP Real-time VC0 housekeeping data consists of either selected APIDs or the entire full VC0 data stream.



4.4.1.3.8.3 Format

The LAMP Real-time VC0 housekeeping data consists of the complete set of telemetry mnemonics from either selected APIDs or all APIDs from the VC0 data stream.

A sample LAMP Real-time VC0 housekeeping data is provided in Appendix B, Figure B.4-14.




122




DRAFT






4.4.1.3.8.8 Medium

The MOC will electronically transfer the LAMP Real-time VC0 housekeeping data to the LAMP SOC during the real-time station contact. The telemetry and command component in the LRO MOC (e.g., ITOS) initiates the transfer via a socket connection.





4.4.1.3.13 Mission Eclipse PredictsThe Mission Eclipse Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section

123




DRAFT




4.4.1.3.16 Definitive Lunar Ground Track FileThe Definitive Lunar Ground Track File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.16provides the information related to the product description, update frequency, and format concepts; Appendix B.1.19 provides a representation of the sample product.


4.4.1.4 MOC PRODUCTS FOR LEND






124






DRAFT

4.4.1.4.2.3 Format











4.4.1.4.2.8 Medium






txt for text files

4.4.1.4.3 Daily Command Load

125




DRAFT

4.4.1.4.3.1 Product Description




4.4.1.4.3.3 Format











4.4.1.4.3.8 Medium





126




DRAFT


txt for text files


4.4.1.4.5 LEND - Spacecraft Housekeeping Data File4.4.1.4.5.1 Product Description




4.4.1.4.5.3 Format

The LEND - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

A sample LEND - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-15.









127




DRAFT

4.4.1.4.5.8 Medium

The MOC will electronically transfer the LEND - Spacecraft Housekeeping Data File to the LEND SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LE_LROTLM



txt for text files

4.4.1.4.6 LEND Housekeeping Data Files4.4.1.4.6.1 Product Description

This file contains the stored LEND instrument telemetry data.



4.4.1.4.6.3 Format

The LEND Housekeeping Data File consists of the complete set of LEND instrument telemetry values.

A sample LEND Housekeeping Data File is provided in Appendix B, Figure B.4-16.







128






DRAFT



4.4.1.4.6.8 Medium

The MOC will electronically transfer the LEND - Spacecraft Housekeeping Data File to the LEND SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LE_HKP



txt for text files

4.4.1.4.7 LEND Raw Measurement Data Files4.4.1.4.7.1 Product Description




4.4.1.4.7.3 Format

The LEND Raw Measurement Data Files consists of the complete set of LEND instrument measurement telemetry as noted in the LEND Instrument ICD.

A sample LEND Raw Measurement Data Files is provided in Appendix B, Figure B.4-17.




129




DRAFT





The LRO MOC will transfer this file to the corresponding LEND SOC at the completion of a downlinked pass.

4.4.1.4.7.8 Medium

The MOC will electronically transfer the LEND Raw Measurement Data Files to the LEND SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LE_INS



txt for text files

4.4.1.4.8 LEND Real-time VC0 housekeeping data4.4.1.4.8.1 Product Description

The LEND Real-time VC0 housekeeping data consists of either selected APIDs or the entire full VC0 data stream.



4.4.1.4.8.3 Format

The LEND Real-time VC0 housekeeping data consists of the complete set of telemetry mnemonics from either selected APIDs or all APIDs from the VC0 data stream.

130




DRAFT

A sample LEND Real-time VC0 housekeeping data is provided in Appendix B, Figure B.4-18.









4.4.1.4.8.8 Medium

The MOC will electronically transfer the LEND Real-time VC0 housekeeping data to the LEND SOC during the real-time station contact. The telemetry and command component in the LRO MOC (e.g., ITOS) initiates the transfer via a socket connection.




4.4.1.4.12 Lunar Terminator Crossing PredictsThe Lunar Terminator Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section

131




DRAFT






4.4.1.5 MOC PRODUCTS FOR LOLA






132






DRAFT

4.4.1.5.2.3 Format











4.4.1.5.2.8 Medium






txt for text files

4.4.1.5.3 Daily Command Load

133




DRAFT

4.4.1.5.3.1 Product Description




4.4.1.5.3.3 Format











4.4.1.5.3.8 Medium





134




DRAFT


txt for text files

4.4.1.5.4 SCN Weather DataThe Ground Network Weather Data file is originally generated by all stations supporting the LRO mission. This file is transferred to the LRO MOC for storage archive and for distribution to the LOLA SOC. Section 4.2.1.7 provides the information related to the product description, update frequency, and format concepts; Appendix B.2.6 provides the representation of a sample product.

4.4.1.5.5 LOLA - Spacecraft Housekeeping Data File4.4.1.5.5.1 Product Description




4.4.1.5.5.3 Format

The LOLA - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

A sample LOLA - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-19.








135




DRAFT


4.4.1.5.5.8 Medium

The MOC will electronically transfer the LOLA - Spacecraft Housekeeping Data File to the LOLA SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [9 Characters]LO_LROTLM



txt for text files

4.4.1.5.6 LOLA Housekeeping Data Files4.4.1.5.6.1 Product Description

This file contains the stored LOLA instrument telemetry data.



4.4.1.5.6.3 Format

The LOLA Housekeeping Data File consists of the complete set of LOLA instrument telemetry values.

A sample LOLA Housekeeping Data File is provided in Appendix B, Figure B.4-20.





136




DRAFT





4.4.1.5.6.8 Medium

The MOC will electronically transfer the LOLA - Spacecraft Housekeeping Data File to the LOLA SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LO_HKP



txt for text files

4.4.1.5.7 LOLA Raw Measurement Data Files4.4.1.5.7.1 Product Description




4.4.1.5.7.3 Format

The LOLA Raw Measurement Data Files consists of the complete set of LOLA instrument measurement telemetry as noted in the LOLA Instrument ICD.

A sample LOLA Raw Measurement Data Files is provided in Appendix B, Figure B.4-21.



137






DRAFT






The LRO MOC will transfer this file to the corresponding LOLA SOC at the completion of a downlinked pass.

4.4.1.5.7.8 Medium

The MOC will electronically transfer the LOLA Raw Measurement Data Files to the LOLA SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LO_INS



txt for text files



138




DRAFT





4.4.1.5.14 Post-Maneuver Spacecraft MassThe Post-Maneuver Spacecraft Mass file is originally created by FDF after each spacecraft maneuver involving thrusters. This file is transferred to the LRO MOC for storage archive and distribution to the LOLA SOC, as required. Section TBD provides the information related to the product description, update frequency, and format concepts; Appendix B.1.29 provides a representation of the sample product.

4.4.1.5.15 Predicted LRO Ephemeris FileThe Predicted LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.2 provides the information related to the product description, update frequency, and format concepts; Appendix B.1-1 provides a sample product view and representation.

4.4.1.5.16 Predicted Lunar Ground Track FileThe Predicted Lunar Ground Track File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.2 provides the information related to the product description, update frequency, and format concepts; Appendix B.1-1 provides a sample product view and representation.

4.4.1.5.17 Raw Attitude Data File139






Should LOLA receive this file V2.8 of matrix does not have this product going to LOLA


Need to define this product with the FDF section and then x-ref that FDF section here. OR Could this be defined within the Post-Maneuver Orbiter Post-Maneuver Report? (Section 4.1.2.11)


Should LOLA get this product


Should LOLA get this file?


DRAFT

The Raw Attitude Data File is originally created by the MOC Telemetry and command system on a daily basis; it contains spacecraft telemetry points from gyro, star tracker, ACS processing regarding spacecraft attitude. Section 5 provides the information related to the product description, update frequency, and format concepts; Appendix B.4.30 provides a representation of the sample product.

4.4.1.5.18 Raw Tracking Data FilesThe Raw Tracking Data file is originally generated by each of the stations doing S-Band tracking. This file is transferred to the LRO MOC for storage archive and for distribution to the LOLA SOC. Section 4.2.1.2 provides the information related to the product description, update frequency, and format concepts; Appendix B.2.2 provides the representation of a sample product.

4.4.1.6 MOC PRODUCTS FOR LROC






4.4.1.6.2.3 Format








140




DRAFT




4.4.1.6.2.8 Medium






txt for text files





4.4.1.6.3.3 Format



141




DRAFT









4.4.1.6.3.8 Medium






txt for text files


4.4.1.6.5 LRO SPICE Files DefinitiveThe LRO SPICE Files Definitive is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section

142




DRAFT



4.4.1.6.7 LROC - Spacecraft Housekeeping Data File4.4.1.6.7.1 Product Description




4.4.1.6.7.3 Format

The LROC - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

A sample LROC - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-22.









4.4.1.6.7.8 Medium

143




DRAFT

The MOC will electronically transfer the LROC - Spacecraft Housekeeping Data File to the LROC SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [9 Characters]LR_LROTLM



txt for text files

4.4.1.6.8 LROC Housekeeping Data Files4.4.1.6.8.1 Product Description

This file contains the stored LROC instrument telemetry data.



4.4.1.6.8.3 Format

The LROC Housekeeping Data File consists of the complete set of LROC instrument telemetry values.

A sample LROC Housekeeping Data File is provided in Appendix B, Figure B.4-23.







4.4.1.6.8.7 Delivery Schedule144






DRAFT


4.4.1.6.8.8 Medium

The MOC will electronically transfer the LROC - Spacecraft Housekeeping Data File to the LROC SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LR_HKP



txt for text files

4.4.1.6.9 LROC Raw Measurement Data Files4.4.1.6.9.1 Product Description




4.4.1.6.9.3 Format

The LROC Raw Measurement Data Files consists of the complete set of LROC instrument measurement telemetry as noted in the LROC Instrument ICD.

A sample LROC Raw Measurement Data Files is provided in Appendix B, Figure B.4-24.





145




DRAFT




The LRO MOC will transfer this file to the corresponding LROC SOC at the completion of a downlinked pass.

4.4.1.6.9.8 Medium

The MOC will electronically transfer the LROC Raw Measurement Data Files to the LROC SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]LR_INS



txt for text files



4.4.1.6.12 Mission Eclipse PredictsThe Mission Eclipse Predicts file is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section

146




DRAFT





4.4.1.7 MOC PRODUCTS FOR Mini-RF






4.4.1.7.2.3 Format



147






DRAFT









4.4.1.7.2.8 Medium






txt for text files




Support will be provided through all mission phases.148




DRAFT

4.4.1.7.3.3 Format











4.4.1.7.3.8 Medium






txt for text files

4.4.1.7.4 Definitive LRO Ephemeris File

149




DRAFT

The Definitive LRO Ephemeris File is originally created by FDF. This file is transferred to the LRO MOC for storage archive and distribution to other LRO elements, as required. Section 4.1.2.3 provides the information related to the product description, update frequency, and format concepts; Appendix B.1.6 provides a representation of the sample product.





4.4.1.7.9 Mini-RF - Spacecraft Housekeeping Data File4.4.1.7.9.1 Product Description




4.4.1.7.9.3 Format

The Mini-RF - Spacecraft Housekeeping Data File consists of the complete set of LRO spacecraft telemetry points that the SOC has identified as being required to support its internal SOC processing.

150




DRAFT

A sample Mini-RF - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-25.









4.4.1.7.9.8 Medium

The MOC will electronically transfer the Mini-RF - Spacecraft Housekeeping Data File to the Mini-RF SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eleven characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [9 Characters]RF_LROTLM



txt for text files

4.4.1.7.10 Mini-RF Housekeeping Data Files4.4.1.7.10.1Product Description

This file contains the stored Mini-RF instrument telemetry data.

151




DRAFT

4.4.1.7.10.2Support Duration


4.4.1.7.10.3Format

The Mini-RF Housekeeping Data File consists of the complete set of Mini-RF instrument telemetry values.

A sample Mini-RF Housekeeping Data File is provided in Appendix B, Figure B.4-26.

4.4.1.7.10.4Accuracy and Completeness


4.4.1.7.10.5Timespan


4.4.1.7.10.6Volume Estimate


4.4.1.7.10.7Delivery Schedule


4.4.1.7.10.8Medium

The MOC will electronically transfer the Mini-RF - Spacecraft Housekeeping Data File to the Mini-RF SOC at the completion of an S-Band telemetry pass from either a USN S-Band station or from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]RF_HKP



txt for text files

152






DRAFT

4.4.1.7.11 Mini-RF Operations Opportunity

4.4.1.7.12 Mini-RF Raw Measurement Data Files4.4.1.7.12.1Product Description


4.4.1.7.12.2Support Duration


4.4.1.7.12.3Format

The Mini-RF Raw Measurement Data Files consists of the complete set of Mini-RF instrument measurement telemetry as noted in the Mini-RF Instrument ICD.

A sample Mini-RF Raw Measurement Data Files is provided in Appendix B, Figure B.4-28.

4.4.1.7.12.4Accuracy and Completeness


4.4.1.7.12.5Timespan


4.4.1.7.12.6Volume Estimate


4.4.1.7.12.7Delivery Schedule

The LRO MOC will transfer this file to the corresponding Mini-RF SOC at the completion of a downlinked pass.

4.4.1.7.12.8Medium

The MOC will electronically transfer the Mini-RF Raw Measurement Data Files to the Mini-RF SOC at the completion of the Ka-Band pass from the WS1 S-Band station. The following file-naming convention is used for files transmitted from the LRO MOC. The filename consists of eight characters; it also contains a three character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows:


where File Name = [6 Characters]RF_INS

153




DRAFT



txt for text files





4.4.2 MOC PRODUCTS DISTRIBUTED TO PLANETARY DATA SYSTEM

SPICE Files and Ephemeris Data and maybe improved Lunar Gravity Model

4.4.3 MOC PRODUCTS TO STATIONS

4.4.3.1 SCN Realtime Orbiter Commands (SCN and USN)

4.4.3.1.1 Product DescriptionThis product is the realtime Orbiter Commands via CLTUs (this covers both ATS/RTS commands as well as the Command File concepts to both the SCN station (WS1) and the four currently allocated USN stations using the EOS Ground Message Header.

154






DRAFT

4.4.3.1.2 Support DurationThis support will be provided through all mission phases.

4.4.3.1.3 FormatThe SCN Realtime Orbiter Commands consists of the commands formatted into CLTUs and transmitted to either the WS1 station or the appropriate USN station supporting the mission.

A sample SCN Realtime Orbiter Command (for WS1 and USN interfaces) is provided in Appendix B.4.31.

4.4.3.2 SCN Orbiter Commands – CFDP Structure

4.4.3.2.1 Product DescriptionThis product is the Orbiter Commands via the CCSDS file delivery protocol, which are encapsulated in the CLTUs and sent to either the SCN station (WS1) and the four currently allocated USN stations using the EOS Ground Message Header.


4.4.3.2.3 FormatThe SCN Realtime Orbiter Commands consists of the commands formatted into CLTUs and transmitted to either the WS1 station or the appropriate USN station supporting the mission.

A sample SCN Realtime Orbiter Command (for WS1 and USN interfaces) is provided in Appendix B.4.32.

4.4.3.3 DSN Realtime Orbiter Commands

4.4.3.3.1 Product DescriptionThis product is the realtime Orbiter Commands via CLTUs; this supports the ATS/RTC commands transmitted to DSN stations using the Space Link Extension (SLE).


4.4.3.3.3 FormatThe DSN Realtime Orbiter Commands consists of the commands in CLTUs and formatted within the SLE wrappers.

A sample Realtime Orbiter Command (for the DSN interfaces) is provided in Appendix B.4.33.

4.4.3.4 DSN Orbiter Commands – CFDP Structure


155




DRAFT

This product is the Orbiter Commands via the CCSDS file delivery protocol, which are encapsulated in the CLTUs and transmitted to the DSN station using the SLE wrappers..


4.4.3.4.3 FormatThe DSN Realtime Orbiter Commands consists of the commands in CLTUs and formatted within the SLE wrappers.

A sample Realtime Orbiter Command (for the DSN interfaces) is provided in Appendix B.4.34.

4.4.3.5 CFDP Control Messages (WS1 Interface Only)

4.4.3.5.1 Product DescriptionThis product is the CFDP Control Messages transmitted between the LRO MOC and the mission unique equipment (MUE) located at the WS1 station. Technically, this interface is really between two MOC developed components (the Data Processing System). However, since the one system is physically located at the WS1 station, this document defines this interface as an external interface rather than just an internal interface.


4.4.3.5.3 FormatThe CFDP Control Messages consists of the regulating messages sent by the DPS system in the MOC to the DPS system in the WS1 station.

A sample CFDP Control Messages is provided in Appendix B.4.35.

4.4.3.6 SCN Support Schedules (Laser Ranging Interface Only)

4.4.3.6.1 Product 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 (generated approximately 3-4 weeks prior to the required week), the Forecast Schedule (generated approximately 2 weeks prior to the required week), and the Operational Schedule (generated by the Thursday prior to the subsequent week.


4.4.3.6.3 FormatThe SCN Support Schedule follows the same format representation as identified in Section 4.2.1.1.3.

156




DRAFT

A sample SCN Station Schedule File is provided in Appendix B, Figure B.2.1.

4.5 LAUNCH SITE (KSC) PRODUCT AND DESCRIPTIONS

This section contains the interface products generated by either the LRO MOC or the launch site at Kennedy Space Center (KSC)

This section provides the details on the interfaces between the Kennedy Space Center (the launch site) or the launch vehicle and the LRO MOC.

Table 4-3 Launch Site – MOC Interface Overview

Product Description

ICD Section Reference

Product Matrix Cross Reference

Comments

Telemetry from Launch Site

Section 4.5.1.1 KSC-1 Pre-launch testing support

Telemetry to KSC Section 4.5.2.1 MOC-49 Post-launch support

Commands to KSC Section 4.5.2.2 MOC-48 Pre-launch testing support

Launch Vehicle Post Separation Vector

Section 4.5.1.2 LV-1 Post-launch support

4.5.1 Launch Site Product Interface with the LRO MOC

This section describes the interface between KSC support facilities and the LRO MOC.

4.5.1.1 Telemetry from Launch Site

4.5.1.1.1 Product DescriptionThis interface allows provides a telemetry flow path from launch Site for both real-time and FTP files. This interface is used during pre-launch verification tests, when the orbiter and instrument suites are at KSC prior to the launch. This interface is between two ITOS systems. The one at KSC acts as the initial interface with the orbiter and then sends the telemetry data to the ITOS located at the LRO MOC.

4.5.1.1.2 Support DurationThe Launch site telemetry is valid only during pre-launch support activities (test, rehearsals) and immediately post-launch as KSC receives minimal LRO telemetry downlinked via the orbiter.

4.5.1.1.3 FormatA sample telemetry file is provided as a reference in Appendix B.5-1.


157




DRAFT

4.5.1.1.5 Timespan

4.5.1.2 Launch Vehicle Post Separation Vector

4.5.1.2.1 Product DescriptionThis information is the Post-separation vector from the launch vehicle provider. This vector is nominally transmitted via a fax to the GSFC flight dynamic’s facility. This interface is used post-launch and occurs several minutes after the actual separation of LRO from the launch vehicle.


4.5.1.2.3 FormatThe post-separation vector is delivered via fax; this is a hard-copy format. A sample station acquisition data file is provided as a reference in Appendix B.5-2.


4.5.2 LRO MOC Product Interface with the Launch Site

This section describes the interface between the LRO MOC and KSC support facilities. These interfaces are used in both a pre-launch and post-launch configuration.

4.5.2.1 Telemetry to KSC

4.5.2.1.1 Product DescriptionThe interface is used for post launch data flows between the MOC and the launch site at the Kennedy Space Center. This interface is between two ITOS systems. The ITOS located at the LRO MOC receives the post-launch telemetry data via the orbiter and transmits the post-launch telemetry data to the ITOS system located at KSC.


4.5.2.1.3 FormatA sample of telemetry data is provided as a reference in Appendix B.5-3.


158




DRAFT

4.5.2.2 Commands to KSC

4.5.2.2.1 Product DescriptionThis interface is used for testing and mission rehearsals and provides the conduit for sending commands 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 the ITOS system located at KSC.

4.5.2.2.2 Support DurationThis interface is used during the pre-launch mission phase when the spacecraft and orbiter are at the Kennedy Space Center prior to launch; this normally occurs from L-6 months up to Launch.

4.5.2.2.3 FormatA sample command load file is provided as a reference in Appendix B.5-4.


4.5.2.2.5 Timespan

4.5.2.2.6 Delivery ScheduleThe commands are sent whenever the LRO project schedules a mission rehearsal and allows the LRO GS to send commands to the orbiter/spacecraft.

4.5.2.2.7 MediumThe commands are delivered electronically using the specified IONet.

159




Coordinate w/ Chris S. to verify that this is the Restricted IONet


DRAFT

5.0 LRO MOC INTERNAL INTERFACES

This section provides the specific information for the interfaces that exist for the various MOC system components. .

5.1.1 Integrated Test and Operations System Interfaces

5.1.1.1 ITOS to MPS Products

5.1.1.1.1 Product DescriptionPostpass Operations Summary

5.1.1.2 ITOS to Anomaly Notification Response and Reporting Products

5.1.1.2.1 Product DescriptionRealtime or Postpass Logs

Spacecraft and System Event Messages

5.1.1.3 ITOS to Data Processing and Distribution Products

5.1.1.3.1 Product DescriptionArchived Telemetry Files

Command Load Files

5.1.1.4 ITOS to FlatSat Products

5.1.1.4.1 Product DescriptionSimulated Telemetry

Simulated Commands

Simulated CFDP Commands

5.1.2 Mission Planning System Interfaces

5.1.2.1 MPS to ITOS Products

5.1.2.1.1 Product DescriptionPass Scripts

5.1.2.2 MPS to DP&DS Products

5.1.2.2.1 Product DescriptionCommand Loads

5.1.2.3 MPS to Anomaly Notification Response and Reporting Interface


1




DRAFT

Logs and System Event Messages

5.1.2.4 MPS to Flight Operations Team Interface

5.1.2.4.1 Product DescriptionViewable Activity Maps

Model Analysis Reports

5.1.3 MOC-FD Interfaces

5.1.3.1 MOC-FD to MPS Products

5.1.3.1.1 Product DescriptionGyro Calibration Data – Report that includes updated parameters for gyro calibration table

SA Calibration Data – Report that includes updated parameters for SA calibration table

Star Tracker Calibration data – Report that includes updated parameters for star tracker calibration table

Attitude Determination Report – A report that provides the calculated definitive attitude based on the raw attitude telemetry mnemonics. In a format such as:"Time (UTCJ)","First Attitude Q","Second Attitude Q","Third Attitude Q","Fourth Attitude Q"

5.1.3.2 MOC-FD to FOT Products

5.1.3.2.1 Product DescriptionGyro Calibration Data – Report that includes updated parameters for gyro calibration table

SA Calibration Data – Report that includes updated parameters for SA calibration table

Star Tracker Calibration data – Report that includes updated parameters for star tracker calibration table

Attitude Determination Report – A report that provides the calculated definitive attitude based on the raw attitude telemetry mnemonics. In a format such as:"Time (UTCJ)","First Attitude Q","Second Attitude Q","Third Attitude Q","Fourth Attitude Q"

5.1.3.3 MOC-FD to DP&DS Products

5.1.3.3.1 Product DescriptionAttitude Determination Report – A report that provides the calculated definitive attitude based on the raw attitude telemetry mnemonics. In a format such as:"Time (UTCJ)","First Attitude Q","Second Attitude Q","Third Attitude Q","Fourth Attitude Q"

2




DRAFT

Sensor Calibration Report Files

5.1.3.4 MOC-FD to Anomaly Products

5.1.3.4.1 Product DescriptionMOC FD System Events – Data File that identifies anomalous system events within the FD-MOC element

5.1.4 Trending Interfaces

5.1.4.1 Trending to Data Processing and Distribution Products

5.1.4.1.1 Product DescriptionTrended Products – various types of graphs, plots based on telemetry points, time and other user-defined criteria

5.1.4.2 MPS to Anomaly Notification Response and Reporting Products

5.1.4.2.1 Product DescriptionLogs and System Event Messages

5.1.4.3 MPS to FOT Products

5.1.4.3.1 Product DescriptionActivity Report Request

Viewable Activity Map

5.1.5 Data Processing and Distribution Interfaces

5.1.5.1 DP&DS to MOC-FD Products

5.1.5.1.1 Product DescriptionSelected attitude telemetry mnemonics

Selected ancillary telemetry Mnemonics

5.1.5.2 DP&DS to Trending Products

5.1.5.2.1 Product DescriptionTelemetry data (Raw and File versions)

3




DRAFT

5.1.5.3 DP&DS to ITOS Products

5.1.5.3.1 Product DescriptionCommand Loads (CFDP Commands, s/c command files)

5.1.5.4 Data Processing and Distribution to Notification Response and Reporting Interface Products

5.1.5.4.1 Product DescriptionLogs and System Event Messages

5.1.6 Monitoring and Anomaly System Interfaces

5.1.6.1 Monitoring and Anomaly System to FOT Products

5.1.6.1.1 Product DescriptionSystem Error Page Notifications

User Notification/Response

Report Request and Generated Report

4




DRAFT

1




DRAFT

A Appendix – Abbreviations and AcronymsAbbreviation/

Acronym DEFINITIONAcq. AcquisitionACS Attitude Control SystemAD Attitude DeterminationAETD 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 interfaceBps bytes per secondC&DH Command & Data HandlingCCB Configuration Control BoardCCL Closed-Circuit LoopCCR configuration change requestCCSDS Consultative Committee for Space Data SystemsCCTV Closed-Circuit Television CFDP 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 RequirementsDPS Data Processing System

1




DRAFT

Abbreviation/ Acronym DEFINITION

DSN 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 PlanFOT Flight Operations TeamFSW 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 StandardizationITOS Integrated Test and Operations System

2




DRAFT


JPL 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 signalLRO 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 DynamicsMO&DSD Mission Operations and Data Systems DirectorateMOC Mission Operations CenterMPS 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 DeterminationOSPF Open Shortest Path FirstPB playback

3




DRAFT


PDB project databasePDS Planetary Data SystemPDU packet data unitPI principal investigatorPOCC Payload Operations Control Centerpsk phase shift keyPTP programmable telemetry processorRF Radio FrequencyRGS Remote Ground StationsRLEP Robotic Lunar Exploration ProgramRS Reed-SolomonRTMC Real-Time Mission CriticalRTS Relative Time SequenceS/C SpacecraftSA Solar ArraySBC Single Board ComputerSCID spacecraft identifierSCN Space Communications NetworkSCP Stored Command ProcessorSCS Sequence and Compression SystemSDVF Software Development and Validation FacilitySERS Spacecraft Emergency Response SystemSIP Standard IP (replaces NI)SK Station-Keeping SOC Science Operations CenterSSR Solid State RecorderSTGT Second Tracking and Data Relay Satellite (TDRS) Ground Terminal STOL 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 ProtocolURL Uniform Resource Locator

4




DRAFT


USN Universal Space NetworkUTC universal time codeUTDF universal tracking data formatVC Virtual ChannelVCDU Virtual Channel Data UnitVCID virtual channel identifierVDS Voice Data SystemVMOC Virtual Mission Operations CenterWAC Wide Angle CameraWAN wide area networkWS workstationWSC White Sands ComplexWSGT White Sands Ground Terminal

5




DRAFT

B Appendix B – Sample Product FormatsEach subsystem will have individual sections in which this document will document a sample product, which can be used as a representative format for the specified product.

B.1 Sample FDF ProductsB.1.1 SCN Acquisition Data Sample

Figure B.1-1 Sample SCN Acquisition Data File

1




DRAFT

B.1.2 DSN Acquisition Data Sample

Figure B.1-2 Sample DSN Acquisition Data File

2




DRAFT

B.1.3 LR Prediction Data SampleBytes Description Example1-7 ILRS Satellite Identification Number - 7 digit number based on COSPAR ID, See Explanation '7603901'

8-9 Year of Century - 2 digits with leading zero fill '09'

10-12 Day of Year - 3 digits with leading blank fill ' 34'

13-24 Time of Day - from midnight GMT with a .1 microsecond granularity andleading blank fill

' 36005000000'

25-28 Crustal Dynamics Project Pad ID- a 4-digit monument identification '7105'

29-30 Crustal Dynamics Project 2-digit system number '07'

31-32 Crustal Dynamics Project 2-digit occupancy sequence number '24'

33-39 Azimuth - the geometric or true azimuth angle with a .1 millidegreegranularity and leading blank fill

' 987500'

40-45 Elevation - the geometric or true elevation angle with a .1 millidegreegranularity and leading blank fill

'292500'

46-57 Laser Range - in units of two way time with a 1 picosecondgranularity and leading blank fill

' 52035998000'

58-64 Pass RMS from the mean of raw range values minus the trend function, for accepted ranges (two-way value in picoseconds).

' 66'

65-68 Wavelength of the laser with leading blank fillThe user of the data should interpret the value given as follows:3000 - 9999: units are 0.1 nanometer1000 - 2999: units are 1.0 nanometerFor the station generating the data, the rule is:Wavelength in rate 0.3000 - 0.9999 microns: unit 0.1 nanometerWavelength in rate 1.000 - 2.999 microns: unit 1.0 nanometer

'5321'

69-73 Surface Pressure - .1 millibar granularity with leading blank fill '10135'

74-77 Surface Temperature - .1 degree Kelvin granularity with leadingblank fill

'2905'

78-80 Relative Humidity at Surface - percentage with leading blank fill ' 55'

81-85 Tropospheric refraction correction - a round trip refractioncorrection with a 1 picosecond granularity and leading blank fill

'33956'

86-91 Center of Mass Correction - a round trip correction with a1 picosecond granularity and leading blank fill

' 1601'

92-96 Receive Amplitude - a positive linear scale value with leading blank fill ' 700'

97-104 Applied System Delay - the two way system delay applied in thecurrent record with a 1 picosecond granularity and leading blank fill

' 95942'

105-110

Calibration Delay Shift - a measure of two way calibration stabilitywith a 1 picosecond granularity and leading blank fill.

' 33'

3



http://ilrs.gsfc.nasa.gov/stations/site_procedures/sod/index.html

http://ilrs.gsfc.nasa.gov/products_formats_procedures/normal_point/np_format.html#Note:%20COSPAR%20ID


DRAFT

111-114

Root Mean Square (RMS) of raw system delay values from the mean. Two-way value in picoseconds. If pre- and post- pass calibrations are made, use the mean of the two RMS values, or the RMS of the combined data set.

' 40'

115 Normal Point Window Indicator - indicates whether or not therecord represents a normal point and the time span of the normal point0: not a normal point1: 5-second normal point (GFZ-1)2: LLR normal point3: 15-second normal point (TOPEX)4: 20-second normal point5: 30-second normal point6: 1-minute normal point7: 2-minute normal point (LAGEOS)8: 3-minute normal point9: 5-minute normal point (ETALON)

'0'

116-119

Number of raw ranges compressed into normal point leading blank fill ' '

120 Epoch Event - indicates the time event reference.Currently, only 1 and 2 are used for laser ranging data.0 = Ground receive time1 = Satellite transmit time (standard for LAGEOS)2 = Ground transmit time3 = Satellite receive time

'1'

121 Epoch Time Scale - indicates the time scale reference.Other flags may appear for historical data.3 = UTC (USNO)4 = UTC (GPS)7 = UTC (BIH)

'3'

122 Angle Origin Indicator - source of angle values.0 = Unknown (converted from MERIT I)1 = Computed (from range)2 = Command (predicts and operator inputs)3 = Measured (calibrated instrument readings)

'3'

123 Tropospheric Refraction Correction Indicator0 = Data has been corrected using the Marini-Murray formula1 = Data has not been corrected

'0'

124 Center of Mass Correction Application Indicator0 = Applied1 = Not applied

'0'

125 Receive Amplitude Correction Indicator0 = Data has been receive amplitude corrected1 = Data has not been receive amplitude corrected

'1'

126 System calibration method and delay shift indicator. Indicates the type of calibration and the type of calibration shift given in columns 105-110

'0'

4




DRAFT

Pre- to Post-PassCalibration Shift

Minimum to MaximumCalibration Shift

External cal 0 5

Internal cal 1 6

Burst cal 2 7

Some other cal 3 8

Not used 4 9

127 System Change indicator (SCH). A flag to increment for every major change to the system (hardware or software). After the value '9' return to '0', and then continue incrementing. The station and data centers should keep a log in a standard format of the value used, the date of the change, and a description of the change.

'0'

128 System Configuration Indicator (SCI). A flag used to indicate alternative modes of operation for a system (e.g., choice of alternative timers or detectors, or use of a different mode of operation for high satellites). Each value of the flag indicates a particular configuration, which is described in a log file held at the station and at the data centers. If only a single configuration is used then use a fixed value. If a new configuration is introduced then use the next higher flag value. If value exceeds '9' then return to '0', overwriting a previous configuration flag (it is not likely that a station will have 10 current possible configurations).

'1'

129 Format Revision Number Indicator - indicates the versionof the MERIT II format for the current record. Data priorto MERIT II that is converted into the MERIT II formatwill have a revision number of '0'.

'3'

130 Release Flag Indicator - indicates when this record firstappeared on a release tape. Cooperating stations whichsend release tapes to the CDDIS will use a numberingscheme beginning with '1'. Release tapes from the CDDISwill have a labeling scheme beginning with 'A'.Non-operational engineering data will have a release flag of'Z'. Data released prior to the MERIT II implementation willhave a release flag of '0'.

'A'

Specifications on the Fullrate format:

1) A field should be blank if a value does not apply or if the value is unknown.2) All fields should have trailing '0' fill when the accuracy of the field value is less than the accuracy of the format.3) The range and all correction fields are in two way time units of picoseconds for both accuracy and consistency.4) All correction field values, except the center of mass, are represented such that they would be subtracted from the laser range when applied. The center of mass value is represented such that it would be added to the laser range when applied.

5




DRAFT

5) To convert the laser range field from two way time in picoseconds to one way distance in meters:

a) convert the range in units of picoseconds to secondsb) divide the result in a) by 2c) multiply the result in b) by the speed of light, (299792458 m/s)

Figure B.1-3 Sample Laser Ranging Prediction Data File

6




DRAFT

B.1.4 Ground Station View Period Predicts Data Sample

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

7




DRAFT

B.1.5 LRO Beta Angle Predict File Sample

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

8




DRAFT

B.1.6 LRO Definitive Ephemeris File Sample

Figure B.1-6 Sample LRO Definitive Ephemeris File

9




DRAFT

B.1.7 LRO Definitive SPICE File Sample

Figure B.1-7 Sample LRO Definitive SPICE File

10




DRAFT

B.1.8 LRO Predictive SPICE File Sample

Figure B.1-8 Sample LRO Predictive SPICE File

11




DRAFT

B.1.9 Lunar Orbit Ascending and Descending Node Predicts Sample

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

12




DRAFT

B.1.10 Lunar Orbit Terminator Crossing Predicts Sample

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

13




DRAFT

B.1.11 Mission Eclipse Predicts Data Sample

Figure B.1-11 Sample Mission Eclipse Predicts Data File

14




DRAFT

B.1.12 Lunar Ephemeris Data Sample

Figure B.1-12 Sample Lunar Ephemeris Data File

15




DRAFT

B.1.13 Orbiter Thruster Maneuver Plans Data Sample

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

16




DRAFT

B.1.14 Orbiter to Earth Range Predict Data Sample

Figure B.1-14 Sample Orbiter to Earth Range Predict Data File

17




DRAFT

B.1.15 Post Orbiter Maneuver Report Data Sample

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

18




DRAFT

B.1.16 Post Separation Report Data Sample

Figure B.1-16 Sample Post Separation Report Data File

19




DRAFT

B.1.17 Predicted LRO Ephemeris File Sample

Figure B.1-17 Sample Predicted LRO Ephemeris File

20




DRAFT

B.1.18 Predicted Lunar Ground Track File Sample

Figure B.1-18 Sample Predicted Lunar Ground Track File

21




DRAFT

B.1.19 Definitive Lunar Ground Track File Sample

Figure B.1-19 Sample Definitive Lunar Ground Track File

22




DRAFT

B.1.20 Attitude Determination Verification Report Sample

Figure B.1-20 Sample Attitude Determination Verification Report File

23




DRAFT

B.1.21 Attitude Slew Plan Sample

Figure B.1-21 Sample Attitude Slew Plan File

24




DRAFT

B.1.22 Gyro Calibration Data Sample

Figure B.1-22 Sample Gyro Calibration Data File

25




DRAFT

B.1.23 HGA Calibration Data Sample

Figure B.1-23 Sample HGA Calibration Data File

26




DRAFT

B.1.24 LRO State Vector Table Sample

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

27




DRAFT

B.1.25 Star Tracker Calibration Data Sample

Figure B.1-25 Sample Star Tracker Calibration Data File

28




DRAFT

B.1.26 Thruster Calibration Data Sample

Figure B.1-26 Sample Thruster Calibration Data File

29




DRAFT

B.1.27 LRO Momentum Management Unload Plan Sample

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

30




DRAFT

B.1.28 Star Tracker Occultation Report Sample

Figure B.1-28 Sample LRO Star Tracker Occultation Report File

31




DRAFT

B.2 Space Communications Data ProductsB.2.1 Station Support Schedules Sample

Figure B.2-1 Sample Station Support Schedules File

32




DRAFT

B.2.2 Station Tracking Data Sample

Byte Format Description1 0D(16) Fixed2 0A(16) Fixed3 01(16) Fixed4-5 ASCII Tracking Data Router

4141=AA=GSFC

4444=DD=GSFC6 Binary Last two digits of current year7-8 Binary Satellite Identification Code (SIC)9-10 Binary Vehicle Identification (VID)11-14 Binary Seconds of year15-18 Binary Microseconds of secondNote: For bytes 19-22/23-36, convert angle data to decimal form. Angle data is given in fractions of a circle. To express 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 az23-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

count39-40 Binary AGC (an integer * (-150/8192) AGC-50=dBm)41-44 Binary Transmit frequency information in 10's of Hz

33




DRAFT

Byte Format Description45 Discrete MSD = antenna size (xmit) as follows:

0(16) = less than 1 m

1(16) = 3.9 m

2(16) = 4.3 m

3(16) = 9 m

4(16) = 12 m

5(16) = 26 m

6(16) = TDRSS ground antenna

7(16) = 6 m

8(16) = 7.3 m

9(16) through Feet = spares

LSD = antenna geometry (xmit) as follows:

0(16) = az-el

1(16) = X-Y (+X-south)

2(16) = X-Y (+X-east)

3(16) = RA-DEC

4(16) = HR-DEC

5(16) through F(16) = spares46 Binary Pad ID (xmit)47 Discrete Antenna size (rcv)

(see byte 45)48 Binary Pad ID (rcv)

34




DRAFT

Byte Format Description49-50 Discrete Mode-system unique

(refer to Table 2)51 Discrete Data Validity

Bit 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) = VHF 2(16) = UHF 3(16) = S-band 4(16) = C-band 5(16) = X-band 6(16) = Ku-band 7(16) = visible 8(16) through F(16) = spares LSD = data transmission type, as follows: 0(16) = test

35




DRAFT

Byte Format Description 1(16) = spare 2(16) = simulated 3(16) = resubmit 4(16) = RT (real time) 5(16) = PB (playback) 6(16) through F(16) = spares53-54 Discrete MSD - tracker type Byte 53, bits 8 thru 5: 0(16) = C-band pulse track 1(16) = SRE (S-band and VHF) or RER 2(16) = X-Y angles only (data acquisition antenna) 3(16) = spare 4(16) = SGLS (AFSCN S-band trackers) 5(16) = spare 6(16) = TDRSS 7(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; negative indicates the two's complement of the number of samples per second).55-72 Spare 73 04(16) Fixed74 04(16) Fixed75 04(16) Fixed

Figure B.2-2 Sample Station Tracking Data File

36




DRAFT

B.2.3 Stored Data Files (VC0 – VC3) Sample

Figure B.2-3 Sample Stored Data Files (VC0 – VC3)

37




DRAFT

B.2.4 Real-time VC0 – VC3Telemetry Data Sample

Figure B.2-4 Sample Real-time VC0 – VC3 Telemetry Data File

38




DRAFT

B.2.5 SCN Station Status Packets Sample

Figure B.2-5 Sample SCN Station Status Packets

39




DRAFT

B.2.6 SCN Weather Data Sample

Figure B.2-6 Sample SCN Weather Data File

40




DRAFT

B.2.7 Ka-Band Measurement Data Files (VC3) Sample

Figure B.2-7 Sample Ka-Band Measurement Data Files (VC3)

41




DRAFT

B.2.8 Ka-Band RF Receiver Data File Sample

Figure B.2-8 Sample Ka-Band RF Receiver Data File

42




DRAFT

B.2.9 CFDP Status Messages Sample

Figure B.2-9 Sample CFDP Status Messages

43




DRAFT

B.2.10 Weekly Laser Ranging Schedule Sample

Figure B.2-10 Sample Weekly Laser Ranging Schedule File

44




DRAFT

B.2.11 DSN Tracking Data File Sample

Figure B.2-11 Sample DSN Tracking Data File

45




DRAFT

B.2.12 DSN Stored Data File Sample

Figure B.2-12 Sample DSN Stored Data File

46




DRAFT

B.2.13 DSN Realtime VC Data Stream Sample

Figure B.2-13 Sample DSN Realtime VC Data Stream

47




DRAFT

B.2.14 DSN Station Status Packets Sample

Figure B.2-14 Sample DSN Station Status Packets

48




DRAFT

B.3 Science Operations Center ProductsB.3.1 CRaTER Command Request Sample

Figure B.3-1 Sample CRaTER Command Request File

49




DRAFT

B.3.2 CRaTER Instrument Reset Timeline Sample

Figure B.3-2 CRaTER Instrument Reset Timeline

50




DRAFT

B.3.3 DLRE Command Request Sample

Figure B.3-3 Sample DLRE Command Request File

51




DRAFT

B.3.4 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-4 Sample DLRE FSW Load File

52




DRAFT

B.3.5 LAMP Command Request Sample

Figure B.3-5 Sample LAMP Command Request File

53




DRAFT

B.3.6 LAMP HV Command Sequence Sample

Figure B.3-6 Sample LAMP HV Command Sequence

54




DRAFT

B.3.7 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-7 Sample LAMP Instrument FSW Load File

55




DRAFT

B.3.8 LEND Command Request Sample

Figure B.3-8 Sample LEND Command Request File

56




DRAFT

B.3.9 LEND Instrument FSW Load SampleTable LoadLEND,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-9 Sample LEND Instrument FSW Load

57




DRAFT

B.3.10 LOLA Command Request Sample

Figure B.3-10 Sample LOLA Command Request File

58




DRAFT

B.3.11 LOLA Gravity Model Sample

Figure B.3-11 Sample LOLA Gravity Model

59




DRAFT

B.3.12 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-12 Sample LOLA Instrument FSW Load File

60




DRAFT

B.3.13 LOLA Processed OD Information Sample

Figure B.3-13 Sample LOLA Processed OD Information

61




DRAFT

B.3.14 LOLA Target Requests Sample

Figure B.3-14 Sample LOLA Target Requests File

62




DRAFT

B.3.15 LROC Instrument Initialization Command Sequence Sample

Figure B.3-15 Sample LROC Instrument Initialization Command Sequence File

63




DRAFT

B.3.16 LROC Daily Command Sequence Sample

Figure B.3-16 LROC Daily Command Sequence File

64




DRAFT

B.3.17 LROC Instrument FSW Load SampleTable LoadLROC,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-17 Sample LROC Instrument FSW Load File

65




DRAFT

B.3.18 LROC Target Requests

Figure B.3-18 Sample LROC Target Requests File

66




DRAFT

B.3.19 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-19 Sample Mini-RF Load File

67




DRAFT

B.3.20 Mini-RF Command Timeline Files

Figure B.3-20 Sample Mini-RF Command Timeline File

68




DRAFT

B.4 Mission Operations Center ProductsB.4.1 Clock Correlation File Sample

Figure B.4-1 Sample Clock Correlation File

69




DRAFT

B.4.2 CRaTER – Spacecraft Housekeeping Data File Sample

Figure B.4-2 Sample CRaTER – Spacecraft Housekeeping Data File

70




DRAFT

B.4.3 CRaTER Housekeeping Data File Sample

Figure B.4-3 Sample CRaTER Housekeeping Data File

71




DRAFT

B.4.4 CRaTER Raw Measurement Data Files Sample

Figure B.4-4 CRaTER Raw Measurement Data Files

72




DRAFT

B.4.5 CRaTER Realtime VC0 Housekeeping Data Sample

Figure B.4-5 Sample CRaTER Realtime VC0 Housekeeping Data

73




DRAFT

B.4.6 Daily Command Load Sample

Figure B.4-6 Sample Daily Command Load File

74




DRAFT

B.4.7 DLRE – Spacecraft Housekeeping Data File Sample

Figure B.4-7 Sample DLRE – Spacecraft Housekeeping Data File

75




DRAFT

B.4.8 DLRE Housekeeping Data Files Sample

Figure B.4-8 Sample DLRE Housekeeping Data Files

76




DRAFT

B.4.9 DLRE Raw Measurement Data File Sample

Figure B.4-9 Sample DLRE Raw Measurement Data File

77




DRAFT

B.4.10 DLRE Real-time VC0 Housekeeping Data Sample

Figure B.4-10 Sample DLRE Real-time VC0 Housekeeping Data

78




DRAFT

B.4.11 LAMP – Spacecraft Housekeeping Data File Sample

Figure B.4-11 Sample LAMP – Spacecraft Housekeeping Data File

79




DRAFT

B.4.12 LAMP Housekeeping Data Files Sample

Figure B.4-12 Sample LAMP Housekeeping Data Files

80




DRAFT

B.4.13 LAMP Raw Measurement Data Files Sample

Figure B.4-13 Sample LAMP Raw Measurement Data Files

81




DRAFT

B.4.14 LAMP Real-time VC0 Housekeeping Data Sample

Figure B.4-14 Sample LAMP Real-time VC0 Housekeeping Data

82




DRAFT

B.4.15 LEND – Spacecraft Housekeeping Data Files Sample

Figure B.4-15 Sample LEND – Spacecraft Housekeeping Data Files

83




DRAFT

B.4.16 LEND Housekeeping Data Files Sample

Figure B.4-16 Sample LEND Housekeeping Data Files

84




DRAFT

B.4.17 LEND Raw Measurement Data Files Sample

Figure B.4-17 Sample LEND Raw Measurement Data Files

85




DRAFT

B.4.18 LEND Real-time VC0 Housekeeping Data Sample

Figure B.4-18 Sample LEND Real-time VC0 Housekeeping Data

86




DRAFT

B.4.19 LOLA – Spacecraft Housekeeping Data Files Sample

Figure B.4-19 Sample LOLA – Spacecraft Housekeeping Data Files

87




DRAFT

B.4.20 LOLA Housekeeping Data Files Sample

Figure B.4-20 Sample LOLA Housekeeping Data Files

88




DRAFT

B.4.21 LOLA Raw Measurement Data Files Sample

Figure B.4-21 Sample LOLA Raw Measurement Data Files

89




DRAFT

B.4.22 LROC – Spacecraft Housekeeping Data Files Sample

Figure B.4-22 Sample LROC – Spacecraft Housekeeping Data Files

90




DRAFT

B.4.23 LROC Housekeeping Data Files Sample

Figure B.4-23 Sample LROC Housekeeping Data Files

91




DRAFT

B.4.24 LROC Raw Measurement Data Files Sample

Figure B.4-24 Sample LROC Raw Measurement Data Files

92




DRAFT

B.4.25 Mini-RF – Spacecraft Housekeeping Data Files Sample

Figure B.4-25 Sample Mini-RF – Spacecraft Housekeeping Data Files

93




DRAFT

B.4.26 Mini-RF Housekeeping Data Files Sample

Figure B.4-26 Sample Mini-RF Housekeeping Data Files

94




DRAFT

B.4.27 Mini-RF Operations Opportunity Sample

Figure B.4-27 Sample Mini- Operations Opportunity File

95




DRAFT

B.4.28 Mini-RF Raw Measurement Data Files Sample

Figure B.4-28 Sample Mini-RF Raw Measurement Data Files

96




DRAFT

B.4.29 Post Maneuver Spacecraft Mass Sample

Figure B.4-29 Post Maneuver Spacecraft Mass File

97




DRAFT

B.4.30 Raw Attitude Data File Sample

Figure B.4-30 Sample Raw Attitude Data File

98




DRAFT

B.4.31 SCN Realtime Orbiter Commands Sample

Figure B.4-31 Sample SCN Realtime Orbiter Commands

99




DRAFT

B.4.32 SCN Realtime Orbiter Commands – CFDP Sample

Figure B.4-32 Sample SCN Realtime Orbiter Commands – CFDP

100




DRAFT

B.4.33 DSN Realtime Orbiter Commands Sample

Figure B.4-33 Sample DSN Realtime Orbiter Commands

101




DRAFT

B.4.34 DSN Realtime Orbiter Commands – CFDP Sample

Figure B.4-33 Sample DSN Realtime Orbiter Commands – CFDP

102




DRAFT

B.5 Sample Launch Site ProductsB.5.1 Realtime Telemetry to KSC Sample

Figure B.5-1 Sample SCN Acquisition Data File

103




DRAFT

B.5.2 Launch Vehicle Post Separation Vector Sample

Figure B.5-2 Sample Launch Vehicle Post Separation Vector File

104



Interface Control Document (ICD) for the LRO Ground … · Web viewInterface Control Document for...

Documents

Transcript of Interface Control Document (ICD) for the LRO Ground … · Web viewInterface Control Document for...