Interface Control Document (ICD) for the LRO Ground System

Interface Control Document (ICD) for the LRO Ground System 431-ICD-000049 Revision – Dv 3.0 Effective Date: To be added upon Release Expiration Date: To be added upon Release DRAFT Robotic Lunar Exploration ProgramLunar Reconnaissance Orbiter ProjectInterface Control Document for the Lunar Reconnaissance Ground System April 07, 2006 Goddard Space Flight Center Greenbelt, Maryland National Aeronautics andCHECK WITH RLEP DATABASE AT:Space Administration TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - 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 Office Mail Stop 431 Goddard Space Flight Center Greenbelt, Maryland 20771 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Signature Page Prepared by:Reviewed by: _________ ________Ralph Casasanta DateJim Clapsadle. DateLRO Ground System EngineerLRO Ground System EngineerCode 444Code 444 Reviewed by: ________ ________Richard S Saylor, Jr. DateMark Beckman. DateLRO Ground System LeadLRO Flight Dynamics LeadCode 444Code 595 ________ ________Stefan Waldherr. DateSteve Currier DateJPL, Telecommunications and Mission Space Communication NetworkServices Manager, Office 911GSFC/NASA, Code 453 ________ ________Mark Flanegan DateCRaTER SOC POC DateLR System EngineerCRaTER SOC GSFC/NASA, Code 556 _________ ________DLRE SOC POC DateLAMP SOC POC DateDLRE SOCLAMP SOC _________ ________LEND SOC POC DateLOLA SOC POC DateLEND SOCLOLA SOC ________ ________LROC SOC POC DateMini-RF SOC POC DateLROC SOCMini-RF SOC Reviewed by:Approved by: _________ ________Dave Everett DateCraig Tooley DateLRO Mission System EngineerLRO Project ManagerGSFC/NASA, Code 430GSFC/NASA, Code 431 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT LUNAR RECONNAISSANCE ORBITER PROJECT DOCUMENT CHANGE RECORDSheet: 1 of 1REVAPPROVEDDATEDESCRIPTION OF CHANGELEVELBYAPPROVED 01Initial Release, Released per 431-CCR-0000xxC. Tooley CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT List of TBDs/TBRsItem LocationSummaryInd./Org.Due DateNo. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFTItem LocationSummaryInd./Org.Due Date No. 25. 26. 27. 28. 29. 30. CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT TABLE OF CONTENTS Page 1.0 INTRODUCTION............................................................................................................................... 1 1.1 PURPOSE AND SCOPE............................................................................................................................... . 1 1.2 DOCUMENT ORGANIZATION....................................................................................................................... 1 1.3 REQUIREMENTS TRACEABILITY METHODOLOGY............................................................................................ 1 1.4 APPLICABLE DOCUMENTS.......................................................................................................................... 2 1.5 REFERENCED DOCUMENTS......................................................................................................................... 2 1.6 OTHER DOCUMENTED REFERENCES ............................................................................................................ 2 2.0 GROUND SYSTEM OVERVIEW..................................................................................................... 1 2.1 GROUND SYSTEM ARCHITECTURE ............................................................................................................... 2 2.1.1 The LRO Space Communications Network................................................................................ 4 2.1.2 LRO Mission Operations Center................................................................................................ 4 2.1.3 The Science Operations Centers................................................................................................ 5 2.1.4 Flight Dynamics Facility........................................................................................................... 5 2.1.5 Ground System Communications............................................................................................... 52.2 LRO O PERATIONAL GROUND SYSTEM....................................................................................................... 6 2.2.1 ITOS-Supported Real-time Telemetry and Commanding........................................................... 7 2.2.2 Data Processing System............................................................................................................. 7 2.2.3 Data Management System.......................................................................................................... 8 2.2.4 Mission Planning System........................................................................................................... 8 2.2.5 Mission Operations Center – Attitude Determination System.................................................... 8 2.2.6 Trending and Analysis System................................................................................................... 8 2.2.7 Monitoring, Notification and Reporting System......................................................................... 82.3 F LIGHT DYNAMICS FACILITY..................................................................................................................... 9 2.4 FLIGHT OPERATIONS TEAM........................................................................................................................ 92.5 F LIGHT SOFTWARE MAINTENANCE FACILITY................................................................................................ 9 2.6 LRO SPACE COMMUNICATIONS NETWORK.................................................................................................. 9 3.0 LRO GS EXTERNAL INTERFACE PRODUCT SYNOPSIS......................................................... 1 4.0 LRO GROUND SYSTEM EXTERNAL INTERFACES AND PRODUCT.................................... 1 4.1 FLIGHT DYNAMICS FACILITY PRODUCTS.................................................................................................... 21 4.1.1 FDF Products for Network Support......................................................................................... 22 4.1.2 FDF Products to support MOC Functions............................................................................... 25 4.1.3 FDF MOC/ADS Products........................................................................................................ 46 4.2 STATION PRODUCTS AND DESCRIPTIONS............................................................................................ 52 4.2.1 Space Communication Network Product Descriptions............................................................ 52 4.2.2 Deep Space Network Product Descriptions............................................................................. 66 4.3 SCIENCE OPERATION CENTER PRODUCTS AND DESCRIPTIONS...................................... 70 4.3.1 CRaTER SOC Products........................................................................................................... 70 4.3.2 DLRE SOC Products................................................................................................................ 73 4.3.3 LAMP SOC Products............................................................................................................... 76 4.3.4 LEND SOC Products............................................................................................................... 79 iii CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.5 LOLA SOC Products................................................................................................................ 82 4.3.6 LROC SOC Products............................................................................................................... 88 4.3.7 Mini-RF SOC Products............................................................................................................ 93 4.4 LRO MISSION OPERATIONS CENTER PRODUCTS AND DESCRIPTIONS........................... 96 4.4.1 MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS................................................. 96 4.4.2 MOC PRODUCTS DISTRIBUTED TO PLANETARY DATA SYSTEM.................................. 154 4.4.3 MOC PRODUCTS TO STATIONS......................................................................................... 154 4.5 LAUNCH SITE (KSC) PRODUCT AND DESCRIPTIONS....................................................................................... 157 4.5.1 Launch Site Product Interface with the LRO MOC................................................................ 157 4.5.2 LRO MOC Product Interface with the Launch Site................................................................ 158 5.0 LRO MOC INTERNAL INTERFACES............................................................................................ 1 5.1.1 Integrated Test and Operations System Interfaces..................................................................... 1 5.1.2 Mission Planning System Interfaces.......................................................................................... 1 5.1.3 MOC-FD Interfaces................................................................................................................... 2 5.1.4 Trending Interfaces.................................................................................................................... 3 5.1.5 Data Processing and Distribution Interfaces............................................................................. 3 5.1.6 Monitoring and Anomaly System Interfaces............................................................................... 4 1.A APPENDIX – ABBREVIATIONS AND ACRONYMS................................................................... 1 1.B APPENDIX B – SAMPLE PRODUCT FORMATS......................................................................... 1 1.B.1 SAMPLE FDF PRODUCTS....................................................................................................................... 1 1.B.1.1 SCN Acquisition Data Sample................................................................................................ 1 1.B.1.2 DSN Acquisition Data Sample................................................................................................ 2 1.B.1.3 LR Prediction Data Sample.................................................................................................... 3 1.B.1.4 Ground Station View Period Predicts Data Sample............................................................... 7 1.B.1.5 LRO Beta Angle Predict File Sample..................................................................................... 8 1.B.1.6 LRO Definitive Ephemeris File Sample.................................................................................. 9 1.B.1.7 LRO Definitive SPICE File Sample...................................................................................... 10 1.B.1.8 LRO Predictive SPICE File Sample..................................................................................... 11 1.B.1.9 Lunar Orbit Ascending and Descending Node Predicts Sample........................................... 12 1.B.1.10 Lunar Orbit Terminator Crossing Predicts Sample............................................................ 13 1.B.1.11 Mission Eclipse Predicts Data Sample............................................................................... 14 1.B.1.12 Lunar Ephemeris Data Sample........................................................................................... 15 1.B.1.13 Orbiter Thruster Maneuver Plans Data Sample................................................................. 16 1.B.1.14 Orbiter to Earth Range Predict Data Sample..................................................................... 17 1.B.1.15 Post Orbiter Maneuver Report Data Sample...................................................................... 18 1.B.1.16 Post Separation Report Data Sample................................................................................. 19 1.B.1.17 Predicted LRO Ephemeris File Sample.............................................................................. 20 1.B.1.18 Predicted Lunar Ground Track File Sample....................................................................... 21 1.B.1.19 Definitive Lunar Ground Track File Sample...................................................................... 22 1.B.1.20 Attitude Determination Verification Report Sample........................................................... 23 1.B.1.21 Attitude Slew Plan Sample.................................................................................................. 24 1.B.1.22 Gyro Calibration Data Sample........................................................................................... 25 1.B.1.23 HGA Calibration Data Sample........................................................................................... 26 1.B.1.24 LRO State Vector Table Sample........................................................................................ 27 1.B.1.25 Star Tracker Calibration Data Sample............................................................................... 28 iv CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1.B.1.26 Thruster Calibration Data Sample..................................................................................... 29 1.B.1.27 LRO Momentum Management Unload Plan Sample.......................................................... 30 1.B.1.28 Star Tracker Occultation Report Sample............................................................................ 31 1.B.2 SPACE COMMUNICATIONS DATA PRODUCTS........................................................................................... 32 1.B.2.1 Station Support Schedules Sample........................................................................................ 32 1.B.2.2 Station Tracking Data Sample.............................................................................................. 33 1.B.2.3 Stored Data Files (VC0 – VC3) Sample................................................................................ 37 1.B.2.4 Real-time VC0 – VC3Telemetry Data Sample...................................................................... 38 1.B.2.5 SCN Station Status Packets Sample...................................................................................... 39 1.B.2.6 SCN Weather Data Sample................................................................................................... 40 1.B.2.7 Ka-Band Measurement Data Files (VC3) Sample................................................................ 41 1.B.2.8 Ka-Band RF Receiver Data File Sample.............................................................................. 42 1.B.2.9 CFDP Status Messages Sample............................................................................................ 43 1.B.2.10 Weekly Laser Ranging Schedule Sample............................................................................ 44 1.B.2.11 DSN Tracking Data File Sample........................................................................................ 45 1.B.2.12 DSN Stored Data File Sample............................................................................................ 46 1.B.2.13 DSN Realtime VC Data Stream Sample.............................................................................. 47 1.B.2.14 DSN Station Status Packets Sample.................................................................................... 48 1.B.3 SCIENCE OPERATIONS CENTER PRODUCTS.............................................................................................. 49 1.B.3.1 CRaTER Command Request Sample.................................................................................... 49 1.B.3.2 CRaTER Instrument Reset Timeline Sample......................................................................... 50 1.B.3.3 DLRE Command Request Sample......................................................................................... 51 1.B.3.4 DLRE FSW Load Sample...................................................................................................... 52 1.B.3.5 LAMP Command Request Sample........................................................................................ 53 1.B.3.6 LAMP HV Command Sequence Sample................................................................................ 54 1.B.3.7 LAMP Instrument FSW Load Sample................................................................................... 55 1.B.3.8 LEND Command Request Sample........................................................................................ 56 1.B.3.9 LEND Instrument FSW Load Sample................................................................................... 57 1.B.3.10 LOLA Command Request Sample....................................................................................... 58 1.B.3.11 LOLA Gravity Model Sample............................................................................................. 59 1.B.3.12 LOLA Instrument FSW Load Sample .................................................................................. 60 1.B.3.13 LOLA Processed OD Information Sample.......................................................................... 61 1.B.3.14 LOLA Target Requests Sample........................................................................................... 62 1.B.3.15 LROC Instrument Initialization Command Sequence Sample............................................. 63 1.B.3.16 LROC Daily Command Sequence Sample.......................................................................... 64 1.B.3.17 LROC Instrument FSW Load Sample................................................................................. 65 1.B.3.18 LROC Target Requests ..................................................................................................... 66 1.B.3.19 Mini-RF Load Files............................................................................................................ 67 1.B.3.20 Mini-RF Command Timeline Files..................................................................................... 681.B.4 M ISSION OPERATIONS CENTER PRODUCTS.............................................................................................. 69 1.B.4.1 Clock Correlation File Sample............................................................................................. 69 1.B.4.2 CRaTER – Spacecraft Housekeeping Data File Sample....................................................... 70 1.B.4.3 CRaTER Housekeeping Data File Sample............................................................................ 71 1.B.4.4 CRaTER Raw Measurement Data Files Sample................................................................... 72 1.B.4.5 CRaTER Realtime VC0 Housekeeping Data Sample............................................................ 73 1.B.4.6 Daily Command Load Sample.............................................................................................. 74 1.B.4.7 DLRE – Spacecraft Housekeeping Data File Sample........................................................... 75 v CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1.B.4.8 DLRE Housekeeping Data Files Sample.............................................................................. 76 1.B.4.9 DLRE Raw Measurement Data File Sample......................................................................... 77 1.B.4.10 DLRE Real-time VC0 Housekeeping Data Sample............................................................. 78 1.B.4.11 LAMP – Spacecraft Housekeeping Data File Sample......................................................... 79 1.B.4.12 LAMP Housekeeping Data Files Sample............................................................................ 80 1.B.4.13 LAMP Raw Measurement Data Files Sample..................................................................... 81 1.B.4.14 LAMP Real-time VC0 Housekeeping Data Sample............................................................ 82 1.B.4.15 LEND – Spacecraft Housekeeping Data Files Sample....................................................... 83 1.B.4.16 LEND Housekeeping Data Files Sample............................................................................ 84 1.B.4.17 LEND Raw Measurement Data Files Sample..................................................................... 85 1.B.4.18 LEND Real-time VC0 Housekeeping Data Sample............................................................. 86 1.B.4.19 LOLA – Spacecraft Housekeeping Data Files Sample........................................................ 87 1.B.4.20 LOLA Housekeeping Data Files Sample............................................................................. 88 1.B.4.21 LOLA Raw Measurement Data Files Sample..................................................................... 89 1.B.4.22 LROC – Spacecraft Housekeeping Data Files Sample....................................................... 90 1.B.4.23 LROC Housekeeping Data Files Sample............................................................................ 91 1.B.4.24 LROC Raw Measurement Data Files Sample..................................................................... 92 1.B.4.25 Mini-RF – Spacecraft Housekeeping Data Files Sample.................................................... 93 1.B.4.26 Mini-RF Housekeeping Data Files Sample......................................................................... 94 1.B.4.27 Mini-RF Operations Opportunity Sample........................................................................... 95 1.B.4.28 Mini-RF Raw Measurement Data Files Sample.................................................................. 96 1.B.4.29 Post Maneuver Spacecraft Mass Sample............................................................................ 97 1.B.4.30 Raw Attitude Data File Sample.......................................................................................... 98 1.B.4.31 SCN Realtime Orbiter Commands Sample......................................................................... 99 1.B.4.32 SCN Realtime Orbiter Commands – CFDP Sample......................................................... 100 1.B.4.33 DSN Realtime Orbiter Commands Sample....................................................................... 101 1.B.4.34 DSN Realtime Orbiter Commands – CFDP Sample......................................................... 102 1.B.5 SAMPLE LAUNCH SITE PRODUCTS....................................................................................................... 103 1.B.5.1 Realtime Telemetry to KSC Sample.................................................................................... 103 1.B.5.2 Launch Vehicle Post Separation Vector Sample................................................................. 104 vi CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFTLIST OF FIGURES FigurePage FIGURE 2-1. LRO GROUND SYSTEM OVERVIEW DIAGRAM..................................................... 3 FIGURE 2-2 LRO COMMUNICATIONS ARCHITECTURE............................................................. 5 FIGURE B.1-1 SAMPLE SCN ACQUISITION DATA FILE............................................................... 1 FIGURE B.1-2 SAMPLE DSN ACQUISITION DATA FILE............................................................... 2 FIGURE B.1-3 SAMPLE LASER RANGING PREDICTION DATA FILE........................................ 6 FIGURE B.1-4 SAMPLE GROUND STATION VIEW PERIOD PREDICTS DATA FILE.............. 7 FIGURE B.1-5 SAMPLE LRO BETA ANGLE PREDICT FILE......................................................... 8 FIGURE B.1-6 SAMPLE LRO DEFINITIVE EPHEMERIS FILE...................................................... 9 FIGURE B.1-7 SAMPLE LRO DEFINITIVE SPICE FILE................................................................ 10 FIGURE B.1-8 SAMPLE LRO PREDICTIVE SPICE FILE.............................................................. 11FIGURE B.1-9 SAMPLE LUNAR ORBIT ASCENDING AND DESCENDING NODE PREDICTS FILE............................................................................................................................... ........................... 12FIGURE B.1-10 SAMPLE LUNAR ORBIT TERMINATOR CROSSING PREDICTS DATA FILE ............................................................................................................................... .................................... 13 FIGURE B.1-11 SAMPLE MISSION ECLIPSE PREDICTS DATA FILE....................................... 14 FIGURE B.1-12 SAMPLE LUNAR EPHEMERIS DATA FILE......................................................... 15 FIGURE B.1-13 SAMPLE ORBITER THRUSTER MANEUVER PLANS DATA FILE................ 16 FIGURE B.1-14 SAMPLE ORBITER TO EARTH RANGE PREDICT DATA FILE...................... 17 FIGURE B.1-15 SAMPLE POST ORBITER MANEUVER REPORT DATA FILE........................ 18 FIGURE B.1-16 SAMPLE POST SEPARATION REPORT DATA FILE ......................................... 19 FIGURE B.1-17 SAMPLE PREDICTED LRO EPHEMERIS FILE.................................................. 20 FIGURE B.1-18 SAMPLE PREDICTED LUNAR GROUND TRACK FILE................................... 21 FIGURE B.1-19 SAMPLE DEFINITIVE LUNAR GROUND TRACK FILE................................... 22 FIGURE B.1-20 SAMPLE ATTITUDE DETERMINATION VERIFICATION REPORT FILE... 23 FIGURE B.1-21 SAMPLE ATTITUDE SLEW PLAN FILE............................................................... 24 FIGURE B.1-22 SAMPLE GYRO CALIBRATION DATA FILE...................................................... 25 FIGURE B.1-23 SAMPLE HGA CALIBRATION DATA FILE......................................................... 26 FIGURE B.1-24 SAMPLE LRO STATE VECTOR TABLE DATA FILE......................................... 27 FIGURE B.1-25 SAMPLE STAR TRACKER CALIBRATION DATA FILE................................... 28 FIGURE B.1-26 SAMPLE THRUSTER CALIBRATION DATA FILE............................................ 29 vii CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT FIGURE B.1-27 SAMPLE LRO MOMENTUM MANAGEMENT UNLOAD PLAN FILE............ 30 FIGURE B.1-28 SAMPLE LRO STAR TRACKER OCCULTATION REPORT FILE................... 31 FIGURE B.2-1 SAMPLE STATION SUPPORT SCHEDULES FILE............................................... 32 FIGURE B.2-2 SAMPLE STATION TRACKING DATA FILE......................................................... 36 FIGURE B.2-3 SAMPLE STORED DATA FILES (VC0 – VC3)........................................................ 37 FIGURE B.2-4 SAMPLE REAL-TIME VC0 – VC3 TELEMETRY DATA FILE............................ 38 FIGURE B.2-5 SAMPLE SCN STATION STATUS PACKETS......................................................... 39 FIGURE B.2-6 SAMPLE SCN WEATHER DATA FILE.................................................................... 40 FIGURE B.2-7 SAMPLE KA-BAND MEASUREMENT DATA FILES (VC3)................................. 41 FIGURE B.2-8 SAMPLE KA-BAND RF RECEIVER DATA FILE................................................... 42 FIGURE B.2-9 SAMPLE CFDP STATUS MESSAGES...................................................................... 43 FIGURE B.2-10 SAMPLE WEEKLY LASER RANGING SCHEDULE FILE................................. 44 FIGURE B.2-11 SAMPLE DSN TRACKING DATA FILE ................................................................. 45 FIGURE B.2-12 SAMPLE DSN STORED DATA FILE...................................................................... 46 FIGURE B.2-13 SAMPLE DSN REALTIME VC DATA STREAM................................................... 47 FIGURE B.2-14 SAMPLE DSN STATION STATUS PACKETS....................................................... 48 FIGURE B.3-1 SAMPLE CRATER COMMAND REQUEST FILE.................................................. 49 FIGURE B.3-2 CRATER INSTRUMENT RESET TIMELINE.......................................................... 50 FIGURE B.3-3 SAMPLE DLRE COMMAND REQUEST FILE........................................................ 51 FIGURE B.3-4 SAMPLE DLRE FSW LOAD FILE............................................................................ 52 FIGURE B.3-5 SAMPLE LAMP COMMAND REQUEST FILE....................................................... 53 FIGURE B.3-6 SAMPLE LAMP HV COMMAND SEQUENCE....................................................... 54 FIGURE B.3-7 SAMPLE LAMP INSTRUMENT FSW LOAD FILE ............................................... 55 FIGURE B.3-8 SAMPLE LEND COMMAND REQUEST FILE........................................................ 56 FIGURE B.3-9 SAMPLE LEND INSTRUMENT FSW LOAD........................................................... 57 FIGURE B.3-10 SAMPLE LOLA COMMAND REQUEST FILE..................................................... 58 FIGURE B.3-11 SAMPLE LOLA GRAVITY MODEL....................................................................... 59 FIGURE B.3-12 SAMPLE LOLA INSTRUMENT FSW LOAD FILE............................................... 60 FIGURE B.3-13 SAMPLE LOLA PROCESSED OD INFORMATION............................................. 61 FIGURE B.3-14 SAMPLE LOLA TARGET REQUESTS FILE ......................................................... 62FIGURE B.3-15 SAMPLE LROC INSTRUMENT INITIALIZATION COMMAND SEQUENCE FILE............................................................................................................................... ........................... 63 FIGURE B.3-16 LROC DAILY COMMAND SEQUENCE FILE...................................................... 64 viii CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT FIGURE B.3-17 SAMPLE LROC INSTRUMENT FSW LOAD FILE.............................................. 65 FIGURE B.3-18 SAMPLE LROC TARGET REQUESTS FILE........................................................ 66 FIGURE B.3-19 SAMPLE MINI-RF LOAD FILE............................................................................... 67 FIGURE B.3-20 SAMPLE MINI-RF COMMAND TIMELINE FILE............................................... 68 FIGURE B.4-1 SAMPLE CLOCK CORRELATION FILE................................................................ 69 FIGURE B.4-2 SAMPLE CRATER – SPACECRAFT HOUSEKEEPING DATA FILE................. 70 FIGURE B.4-3 SAMPLE CRATER HOUSEKEEPING DATA FILE................................................ 71 FIGURE B.4-4 CRATER RAW MEASUREMENT DATA FILES..................................................... 72 FIGURE B.4-5 SAMPLE CRATER REALTIME VC0 HOUSEKEEPING DATA........................... 73 FIGURE B.4-6 SAMPLE DAILY COMMAND LOAD FILE............................................................. 74 FIGURE B.4-7 SAMPLE DLRE – SPACECRAFT HOUSEKEEPING DATA FILE....................... 75 FIGURE B.4-8 SAMPLE DLRE HOUSEKEEPING DATA FILES................................................... 76 FIGURE B.4-9 SAMPLE DLRE RAW MEASUREMENT DATA FILE ........................................... 77 FIGURE B.4-10 SAMPLE DLRE REAL-TIME VC0 HOUSEKEEPING DATA............................. 78 FIGURE B.4-11 SAMPLE LAMP – SPACECRAFT HOUSEKEEPING DATA FILE.................... 79 FIGURE B.4-12 SAMPLE LAMP HOUSEKEEPING DATA FILES................................................ 80 FIGURE B.4-13 SAMPLE LAMP RAW MEASUREMENT DATA FILES...................................... 81 FIGURE B.4-14 SAMPLE LAMP REAL-TIME VC0 HOUSEKEEPING DATA............................. 82 FIGURE B.4-15 SAMPLE LEND – SPACECRAFT HOUSEKEEPING DATA FILES................... 83 FIGURE B.4-16 SAMPLE LEND HOUSEKEEPING DATA FILES................................................. 84 FIGURE B.4-17 SAMPLE LEND RAW MEASUREMENT DATA FILES....................................... 85 FIGURE B.4-18 SAMPLE LEND REAL-TIME VC0 HOUSEKEEPING DATA............................. 86 FIGURE B.4-19 SAMPLE LOLA – SPACECRAFT HOUSEKEEPING DATA FILES................... 87 FIGURE B.4-20 SAMPLE LOLA HOUSEKEEPING DATA FILES................................................. 88 FIGURE B.4-21 SAMPLE LOLA RAW MEASUREMENT DATA FILES....................................... 89 FIGURE B.4-22 SAMPLE LROC – SPACECRAFT HOUSEKEEPING DATA FILES.................. 90 FIGURE B.4-23 SAMPLE LROC HOUSEKEEPING DATA FILES................................................. 91 FIGURE B.4-24 SAMPLE LROC RAW MEASUREMENT DATA FILES....................................... 92 FIGURE B.4-25 SAMPLE MINI-RF – SPACECRAFT HOUSEKEEPING DATA FILES.............. 93 FIGURE B.4-26 SAMPLE MINI-RF HOUSEKEEPING DATA FILES ............................................ 94 FIGURE B.4-27 SAMPLE MINI- OPERATIONS OPPORTUNITY FILE....................................... 95 FIGURE B.4-28 SAMPLE MINI-RF RAW MEASUREMENT DATA FILES.................................. 96 ix CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT FIGURE B.4-29 POST MANEUVER SPACECRAFT MASS FILE................................................... 97 FIGURE B.4-30 SAMPLE RAW ATTITUDE DATA FILE................................................................ 98 FIGURE B.4-31 SAMPLE SCN REALTIME ORBITER COMMANDS........................................... 99 FIGURE B.4-32 SAMPLE SCN REALTIME ORBITER COMMANDS – CFDP........................... 100 FIGURE B.4-33 SAMPLE DSN REALTIME ORBITER COMMANDS......................................... 101 FIGURE B.4-33 SAMPLE DSN REALTIME ORBITER COMMANDS – CFDP........................... 102 FIGURE B.5-1 SAMPLE SCN ACQUISITION DATA FILE........................................................... 103 FIGURE B.5-2 SAMPLE LAUNCH VEHICLE POST SEPARATION VECTOR FILE .............. 104 LIST OF TABLES TablePage TABLE 2-1 MOC FUNCTIONAL COMPONENT INFORMATION.................................................. 6 TABLE 3-1 LRO EXTERNAL INTERFACE PRODUCTS CROSS REFERENCE........................... 1 TABLE 4-1 LRO PRODUCT SUMMARY INFORMATION............................................................... 2 TABLE 4-2. MOC PRODUCTS TRANSMITTED TO VARIOUS LRO SOC FACILITIES........... 96 TABLE 4-3 LAUNCH SITE – MOC INTERFACE OVERVIEW.................................................... 157 x CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1.0INTRODUCTION 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.1PURPOSE 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.2DOCUMENT 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 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 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.3REQUIREMENTS TRACEABILITY METHODOLOGY The ground system interfaces specified in this document are derived from the LunarReconnaissance Orbiter Detailed Mission Requirements Document (431-RQMT-0000049), which identified the specific instance associated with the interface description. 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1.4APPLICABLE DOCUMENTS The following LRO project documents apply only to the extent they are cited in this document. 431-RQMT-000174Lunar Reconnaissance Orbiter Mission Assurance Requirements 431-RQMT-000049Lunar Reconnaissance Orbiter Detailed Mission Requirements Document 431-HDBK-000052Lunar Reconnaissance Orbiter Telemetry and Command Formats Handbook 431-HDBK-000053Lunar Reconnaissance Orbiter Telemetry and Command Database Handbook 431-SPEC-000078Lunar Reconnaissance Orbiter CCSDS File Delivery Protocol Specification 431-ICD-0000NNICD between the LRO Project and the NASA Ground Network (NGN) (Scheduling and Monitoring Interface) 431-HDBK-000486Lunar Reconnaissance Orbiter Mission Design Handbook431-RQMT-000113LRO Pointing and Alignment Requirements 1.5REFERENCED DOCUMENTS The following NASA and GFSC documents are used as supporting and reference documents only. NASA NPR 2810.1NASA Security of Information Technology; Revalidated 12 August 2004 1.6OTHER DOCUMENTED REFERENCES Format data concepts specifically needed to support the laser ranging sites 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 2.0GROUND 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.1GROUND SYSTEM ARCHITECTURE The LRO GS is comprised of several main elements as shown in Figure 2-1. LRO GroundSystem 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Each LRO Ground System element, as listed in Figure 2-1, is briefly described in the following subsections. 2.1.1The 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.2LRO 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 2.1.3The 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.4Flight 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.5Ground 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. Figure 2-2 LRO Communications Architecture Communication 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2LRO 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 ElementComponentProviderSection Reference Telemetry and CommandITOSGOTS – GSFC 584Section 2.2.1 Mission PlanningFlexPlanCOTS – GMVSection 2.2.4 Trending and AnalysisITPSGOTS – GSFC 580Section 2.2.6 Data Processing SystemITOS/DPSGOTS – GSFC 584Section 2.2.2 Data Management SystemITOS/DMSGOTS – GSFC 584Section 2.2.3 Monitoring and Anomaly AttentionCOTS Section 2.2.7 6 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Functional ElementComponentProviderSection Reference Attitude DeterminationMOC-ADSGOTS – Code 595Section 2.2.5 2.2.1ITOS-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.2Data 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 2.2.3Data 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.4Mission 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.5Mission 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.6Trending 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.7Monitoring, 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.3FLIGHT 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.4FLIGHT 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 mission 2.5FLIGHT 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.6LRO SPACE COMMUNICATIONS NETWORK The LRO mission requires support from a variety of networks identified as the Space Communications Network (SCN): 9 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1.The Ka and S-Band antennas located at WS1 will provide the prime station support for the LRO mission. 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 3.0LRO 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 Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO CRaTER Activity DMR-51, DMR-218, 1CRaTER-1CRaTERSection 4.3.1.1?RequestDMR-77, DMR-573 DMR-51, CRaTER Instrument DMR-218,2CRaTER-2CRaTERFSW LoadsDMR-77 DMR-573 CRaTER Instrument DMR-51, DMR-218, 3CRaTER-3Section 4.3.1.2?CRaTERReset TimelineDMR-77, DMR-573 DLRE Command 4DLRE-1DLRESection 4.3.2.1?Request 5DLRE-2DLRE FSW LoadsDLRESection 4.3.2.2? 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO6DSN-1DSN Tracking DataDSNSection 4.2.2.1? Archived Station Data 7DSN-2for any Stored Virtual DSNSection 4.2.2.2? Channel Real-Time Telemetry 8DSN-3for any commanded DSNSection 4.2.2.3? VC downlinked 9DSN-4DSN Status DataDSNSection 4.2.2.4? DMR-591Attitude Determination 10FDF-1MOC-ADSSection 4.1.3.1?Verification Report DMR-592 11FDF-2Attitude Slew PlansMOC-ADSSection 4.1.3.2? DMR-59412FDF-3Beta Angle PredictsFDFSection 4.1.2.2? DMR-595Definitive LRO 13FDF-4FDFSection 4.1.2.3?Ephemeris File 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO DMR-59614FDF-5DSN Acquisition DataFDFSection 4.1.1.2? DMR-57115FDF-6SCN Acquisition DataFDFSection 4.1.1.1? DMR-598Ground Station View 16FDF-7FDFSection 4.1.2.1??Period Predicts DMR-60917FDF-8Gyro Calibration DataFDFSection 4.1.3.3? DMR-56418FDF-9HGA Calibration DataFDFSection 4.1.3.4? DMR-597 Laser Ranging Site 19FDF-10FDFSection 4.1.1.3?Prediction Data LRO Definitive SPICE 20FDF-11FDFSection 4.1.2.4?File LRO Predictive SPICE 21FDF-12FDFSection 4.1.2.5?File 3 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO DMR-599Lunar Orbit Ascending 22FDF-13and Descending Node FDFSection 4.1.2.6? Predicts DMR-600Lunar Terminator 23FDF-14FDFSection 4.1.2.7?Crossing Predicts DMR-601Mission Eclipse 24FDF-15FDFSection 4.1.2.8?Predicts DMR-60225FDF-16Lunar EphemerisFDFSection 4.1.2.9? DMR-603Orbiter thruster 26FDF-17FDFSection 4.1.2.10?maneuver plans DMR-604Orbiter to Earth Range 27FDF-18FDFSection 4.1.2.11?Predicts DMR-605Orbiter Post Maneuver 28FDF-19FDFSection 4.1.2.12?Report DMR-60629FDF-20Post-Separation ReportFDFSection 4.1.2.13? 4 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO DMR-607Predicted LRO 30FDF-21FDFSection 4.1.2.14?Ephemeris File DMR-608Predicted Lunar 31FDF-22FDFSection 4.1.2.15?Ground Track File DELETED32FDF-23SA Calibration DataFDFSection DMR-613LRO State Vector 33FDF-24FDFSection 4.1.3.5?Table DMR-611Star Tracker 34FDF-25FDFSection 4.1.3.6 ?Calibration data DMR-610Thruster Calibration 35FDF-26FDFSection 4.1.3.7?Data DMR-593Momentum FDF-27 36Management Unload MOC - ADSSection 4.1.3.8?(New)Plan DMR-612FDF-28 Star Tracker 37FDFSection 4.1.2.17?(New)Occultation Report 5 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSOFDF-29 38Attitude Slew ReportMOC - ADSSection 4.1.3.2?(New) FDF-30 Definitive Lunar 39FDFSection 4.1.2.16?(New)Ground Track File FDF-31 HGA/SA Fixed offset 40FDFSection TBD?(New)SPK FDF-32 41SPK – PlanetNAIFN/AN/A??(New) FDF-33 42Generic PCKFDF/NAIFSection TBD?(New) FDF-34 43Binary PCKFDF/NAIFSection TBD?(New) FDF-35 44Predicted CKTBD ??Section TBD?(New) FDF-36 45Definitive CKTBD ??Section TBD?(New) FDF-37 SCLK – Spacecraft 46 Section TBD????????(New)clock correlation file 6 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO NAIF, FDF-38 LSK – Leap second announceme47NA?(New)tabulationnt is sent out. FDF-39 Multiple 48FK – Frame KernelsSection TBD?(New)LRO Groups Section 4.2.1.5SCN Station Status SCN49SCN-1and?PacketsUSNSection 4.2.1.6 SCN Support 50SCN-2SCNSection 4.2.1.1?Schedules SCN51SCN-3SCN Weather DataSection 4.2.1.7?USN Ka-Band Measurement 52SCN-4SCNSection 4.2.1.8??Data Files (VC3) Laser Range Transmit Only to LOLA and 53SCN-5LR SiteSection TBDInformationshould be removed Raw Tracking Data 54SCN-6SCNSection 4.2.1.2??Files 7 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSOReal-time VC0 orbiter 55SCN-7SCNSection 4.2.1.4 ?telemetry Real-time VC1, VC2, 56SCN-8SCNSection 4.2.1.4?VC3 data Ka-Band RF Receiver 57SCN-9SCNSection 4.2.1.9?Data CFDP Status Messages 58SCN-10from SCN/DPS to SCNSection 4.2.1.10? MOC/DPS Stored HK Data Files 59SCN-11SCNSection 4.2.1.3?(VC0–VC3) Telemetry from launch 60KSC-1Site (Real-time and KSCSection 4.5.1.1? FTP files) LAMP Command 61LAMP-1LAMPSection 4.3.3.1?Request LAMP HV command 62LAMP-2LAMPSection 4.3.3.2?sequence 8 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO LAMP Instrument 63LAMP-3LAMPSection 4.3.3.3?FSW Loads LV, via Launch Launch Vehicle Post-KSC Launch 64Section 4.5.1.2?Vehicle-1Sep VectorSupport Team LEND Command 65LEND-1LENDSection 4.3.4.1?Request LEND Instrument 66LEND-2LENDSection 4.3.4.2?FSW Loads LOLA Command 67LOLA-1LOLASection 4.3.5.1?Request 68LOLA-2LOLA Gravity ModelLOLASection 4.3.5.2? LOLA Instrument 69LOLA-3LOLASection 4.3.5.3?FSW Loads LOLA Processed OD 70LOLA-4LOLASection 4.3.5.4?information 9 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO71LOLA-5LOLA Target RequestLOLASection 4.3.5.5? LROC Instrument 72LROC-1Initialization LROCSection 4.3.6.1? Command Sequence LROC Daily 73LROC-2LROCSection 4.3.6.2?Command Sequence - LROC File Delivery 74LROC-5LROCSection ?Verification LROC Instrument 75LROC-3LROCSection 4.3.6.3?FSW Loads 76LROC-4LROC Target RequestLROCSection 4.3.6.4 ? 77Mini-RF-1Mini-RF Load FilesMini-RFSection 4.3.7.1? Mini-RF Command 78Mini-RF-2Mini-RFSection 4.3.7.2?Timeline 10 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO79MOC-1Beta Angle PredictsFDFSection 4.1.2.2??????? 80MOC-2CFDP ControlMOCSection 4.4.3.4?? 81MOC-3Clock Correlation FileMOCSection 4.4.1.1.2??????? 82MOC-48Commands to KSCMOCSection 4.5.2.2? CRaTER - Spacecraft 83MOC-4s/cSection 4.4.1.1.3?HK Data File CRaTER HK Data 84MOC-5s/cSection 4.4.1.1.4?Files CRaTER Raw 85MOC-6Measurement Data s/cSection 4.4.1.1.5? Files CRaTER Real-time 86MOC-7s/cSection 4.4.1.1.6?VC0 HK data 11 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO87MOC-8Daily Command LoadMOCSection 4.4.1.1.7??????? LRO Definitive 88MOC-9FDFSection 4.1.2.3??????Ephemeris File DLRE - Spacecraft HK 89MOC-10s/cSection 4.4.1.2.5?Data File 90MOC-11DLRE HK Data Filess/cSection 4.4.1.2.6? DLRE Raw 91MOC-12Measurement Data s/cSection 4.4.1.2.7? Files DLRE Real-time VC0 92MOC-13s/cSection 4.4.1.2.8?HK data 93MOC-14SCN Weather DataSCNSection 4.2.1.7? Ground Station View 94MOC-20FDFSection 4.1.2.1?Period Predicts 12 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO LAMP - Spacecraft 95MOC-15s/cSection 4.4.1.3.5?HK Data File 96MOC-16LAMP HK Data Filess/cSection 4.4.1.3.6? LAMP Raw 97MOC-17Measurement Data s/cSection 4.4.1.3.7? Files LAMP Real-time VC0 98MOC-18s/cSection 4.4.1.3.8?HK data Laser Range Transmit 99MOC-19LR SiteSection Information LEND - Spacecraft HK 100MOC-21s/cSection 4.4.1.4.5?Data File 101MOC-22LEND HK Data Filess/cSection 4.4.1.4.6? LEND Raw 102MOC-23Measurement Data s/cSection 4.4.1.4.7? Files 13 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO LEND Real-time VC0 103MOC-24s/cSection 4.4.1.4.8?HK data LOLA - Spacecraft HK 104MOC-25s/cSection 4.4.1.5.5?Data File 105MOC-26LOLA HK Data Filess/cSection 4.4.1.5.6? LOLA Raw 106MOC-27Measurement Data s/cSection 4.4.1.5.7? Files LRO SPICE Files 107MOC-47FDFSection ???????Definitive LRO SPICE Files 108MOC-28FDFSection ???????Predicts LROC - Spacecraft HK 109MOC-29s/cSection 4.4.1.6.7?Data File 110MOC-30LROC HK Data Filess/cSection 4.4.1.6.8? 14 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO LROC Raw 111MOC-31Measurement Data s/cSection 4.4.1.6.9? Files Lunar Orbit Ascending 112MOC-32and Descending Node FDFSection 4.1.2.6??????? Predicts Lunar Orbit 113MOC-33Terminator Crossing FDFSection 4.1.2.7?????? Predicts Mini-RF - Spacecraft 114MOC-34s/cSection 4.4.1.7.9?HK Data File Mini-RF HK Data Section 115MOC-35s/c?Files4.4.1.7.10 Mini-RF Operations Section 116MOC-36MOC?Opportunity4.4.1.7.11 Mini-RF Raw Section 117MOC-37Measurement Data s/c?4.4.1.7.12Files Mission Eclipse 118MOC-38FDFSection 4.1.2.8??????Predicts 15 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO Post-Maneuver 119MOC-39FDFSection 4.1.2.12?Spacecraft Mass Predicted LRO 120MOC-40FDFSection 4.1.2.14???????Ephemeris File Predicted Lunar 121MOC-41FDFSection 4.1.2.15???????Ground Track File 122MOC-42Raw Attitude Data Files/cSection 4.1.3.1???????? Section 4.2.1.2 Raw Tracking Data 123MOC-43SCNand?FilesSection 4.2.2.1 Real-Time orbiter 124MOC-44MOCSection 4.4.3.1??commands Real-Time orbiter 125MOC-45MOCSection 4.4.3.1?commands - DSN 126MOC-49Telemetry to KSCMOCSection 4.5.2.1? 16 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Destination(s) MNSMMMSCLOACiOOCRDLLLLRCINSection nKCCFDSNUNo.IDProduct NameSourceDMR ReferenceaLAEOR--F/ReferenceiS--DSC/STRMNLOSI-G-CDDFNNDNEEPDACLTPNRPMPRRODSFSSSSSO Definitive Lunar 127MOC-50FDFSection 4.1.2.16?Ground Track File This is a LR Site SCN Support 128MOC-51SCNSection 4.2.1.1interface product onlySchedules 17 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.0LRO 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Table 4-1 LRO Product Summary Information Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference The file is electronically delivered to the MOC Valid until the next load is CRaTER Section Variable size based on types 1CRaTER-1user via a TBR mechanism. Delivery Date and uplinked to the spacecraft.Activity Request4.3.1.1of commandstime are TBR 2CRaTER-2Product DeletedProduct DeletedProduct Deleted CRaTER Section The file is electronically delivered to the MOC Valid until the next load that is Variable size based on types 3CRaTER-3Instrument Reset 4.3.1.2via a TBR mechanism. Delivery Date and time uplinked to the spacecraft.of commandsTimelineare TBR Valid until the next command Section DLRE The file is electronically delivered to the MOC Variable size based on types request is uplinked to the 4.3.2.14DLRE-1Command via a TBR mechanism. Delivery Date and time of commandsspacecraft.Requestare TBR. The DLRE Instrument FSW Section The file is electronically delivered to the MOC DLRE FSW TBR – based on FSW Load is active until the next load 4.3.2.25DLRE-2via a TBR mechanism. Delivery Date and time LoadsImage being uploadedis uplinked to the spacecraft.are TBR Section The file is electronically delivered to the MOC 4.2.2.1via a TBR mechanism. Delivery Date and time Five minutes intervals during a DSN Tracking 6DSN-1TBRare TBR. The DSN Tracking Data File is station contactDatadelivered at the completion of the five minute duration for each tracking file Section The FOT requests this file for playback; the file Archived Station Contains all spacecraft data 4.2.2.2is electronically delivered to the MOC via a TBR Data for any TBR – Variable based on downlinked during the last real-7DSN-2mechanism. Stored Virtual station contacttime station contact. The Stored Data files are kept on site at the Channelstation for up to 72 hours 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section The file is electronically delivered to the MOC 4.2.2.3via a TBR real-time socket connection Real-Time Near real-time support TBR – based on VCs being Delivery time is near real-time as the data are Telemetry for 8DSN-3(approximately 30 seconds transmitted, data rate, and received at the DSN station any commanded latency). station contactAs noted previously, the stations will perform the VC downlinkedReed-Solomon decoding of the data prior to delivery to the LRO MOC (VC0 – VC3)Section The DSN Station Status The station status packets are electronically Packet sent every sixty (60) 4.2.2.4Packets is TBS bytes of 9DSN-4DSN Status Datadelivered to the MOC via a real-time socket seconds during station contactinformation for every connection. packet sent. Attitude Section The MOC-ADS element creates The report is transferred electronically to the Determination 4.1.3.1this file on a weekly basis using TBR10FDF-1MOC’s Data Management System via TBR Verification all received data from that time delivery mechanismReportspan. Section Attitude Slew TBR – based on number The file is electronically delivered via a TBR Valid for the upcoming slews11FDF-24.1.3.2Plansand types of slews.mechanism Delivery Date and time are TBR Section The file is posted to the FDF Product Center on a The time span for this product is 4.1.2.2monthly basis (first day of the month), no later for the next five (5) years. It Beta Angle 12FDF-3TBRthan 4:00 pm, local time (based on the Eastern starts at 0000 UTC of the next PredictsTime zone). The MOC uses a TBR mechanism day and contains predicted beta to “get” the file.angles for the next 5 years. Section The time span for this product is The file is posted to the FDF Product Center on a 4.1.2.3for the previous seven (7) days weekly basis (Wednesday of the week), no later Definitive LRO 13FDF-4from 0000 UTC seven days TBRthan 4:00 pm, local time (based on the Eastern Ephemeris Fileprior to 0000 UTC of the current Time zone). The MOC uses a TBR mechanism day.to “get” the file. 3 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference The FDF-generated file is electronically Section DSN The time span for this product is delivered to the DSN via a TBR mechanism. 4.1.1.214FDF-5TBRAcquisition Data28 daysDelivery Date and time are TBR. FDF generates the file on a daily basis Section The FDF-generated file is electronically 4.1.1.1delivered to the SCN user via a TBR mechanism. 10 days of station contactsSCN The file is generated on a weekly schedule, 15FDF-6starts at 0000Z for the TBRAcquisition Datanominally on the Wednesday of the week, unless subsequent Mondayagreed upon by FDF. It will be ready for delivery by 1400 Hours local time, EST. Section The file is generated on a daily basis and posted Ground Station 4.1.2.130 days from 0000 Hours of the to the FDF Product Center, no later than noon 16FDF-7View Period first day within the file to 0000 TBRlocal time (based on the Eastern Time zone). The PredictsHours thirty days laterusers electronically pull (TBR mechanism) to receive the file Section The file is generated on an as-needed basis and Gyro Calibration 4.1.3.3Valid until the next gyro cal delivered to the DMS System via a TBR delivery 17FDF-8TBRDatafunctionmechanism Delivery date and time are TBR The file is generated on an as-needed basis Section whenever the LRO High Gain Antennae is Valid until the next HGA cal 4.1.3.4HGA 18FDF-9TBRcalibrated and delivered to the DMS System via a functionCalibration DataTBR delivery mechanism Delivery date and time are TBR Section The FDF-generated file is electronically The time span for this product is Laser Ranging 4.1.1.3delivered to the LR Site via a TBR mechanism. 28 days from 0000 Hours of the 19FDF-10Site Prediction TBRFDF delivers this file on a weekly basis first day within the file to 0000 Data(Thursday of the week prior to the week in Hours twenty-eight days later.question) 4 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section The file is posted to the FDF Product Center on a The time span for this product is 4.1.2.4daily basis, no later than 4:00 pm, local time LRO Definitive for the previous day period from 20FDF-11TBR(based on the Eastern Time zone). SPICE File0000 UTC of the previous day The MOC uses a TBR mechanism to “get” the to 0000 UTC of the current day.file. Section The file is posted to the FDF Product Center on a The time span for this product is 4.1.2.5daily basis, no later than 4:00 pm, local time LRO Predictive for the next 28 days from 0000 21FDF-12TBR(based on the Eastern Time zone). SPICE FileUTC of the current day to 0000 The MOC uses a TBR mechanism to “get” the UTC 28 days in the future.file. Section Contain seven (7) days of node The file is posted to the FDF Product Center on a Lunar Orbit 4.1.2.6crossing data for LRO daily basis, no later than 4:00 pm, local time Ascending and spacecraft scheduled beginning 22FDF-13TBR(based on the Eastern Time zone). Descending at 0000Z on the next subsequent The MOC uses a TBR mechanism to “get” the Node Predictsday and stopping at 0000Z file.seven days later. Contain seven (7) days of Section The file is posted to the FDF Product Center on a terminator crossing data for 4.1.2.7Lunar daily basis, no later than 4:00 pm, local time LRO spacecraft scheduled Terminator 23FDF-14TBR(based on the Eastern Time zone). beginning at 0000Z on the next Crossing The MOC uses a TBR mechanism to “get” the subsequent day and stopping at Predictsfile.0000Z seven days later. Contain ninety (90) days of Section The file is posted to the FDF Product Center on a eclipse prediction data for LRO 4.1.2.8daily basis, no later than 4:00 pm, local time spacecraft scheduled beginning Mission Eclipse TBR – 90 days of mission 24FDF-15(based on the Eastern Time zone). at 0000Z on the next subsequent Predictseclipse predictsThe MOC uses a TBR mechanism to “get” the day and stopping at 0000Z file.ninety (90) days later. 5 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section Contain seven (7) days of lunar The file is posted to the FDF Product Center on a 4.1.2.9position and velocity daily basis, no later than 4:00 pm, local time Lunar information scheduled TBR – 7 days lunar 25FDF-16(based on the Eastern Time zone). Ephemerisbeginning at 0000Z on the next ephemeris predictsThe MOC uses a TBR mechanism to “get” the subsequent day and stopping at file.0000Z seven days later. Section The file is posted to the FDF Product Center TBR 4.1.2.10days before the planned maneuver, no later than Thruster Maneuver Plan only Orbiter thruster 4:00 pm, local time (based on the Eastern Time 26FDF-17valid for the stated period within TBRmaneuver planszone). the planThe MOC uses a TBR mechanism to “get” the file. Section Contain seven (7) days of 4.1.2.11orbiter to earth range predict The file is posted to the FDF Product Center on a data (centered at 1 minute daily basis, no later than 4:00 pm, local time Orbiter to Earth TBR – 7 days of LRO range 27FDF-18intervals) beginning at 0000Z on (based on the Eastern Time zone). Range Predictspredictsthe next day and stopping at The MOC uses a TBR mechanism to “get” the 0000Z seven days later for each file. station contact. Section The file is posted to the FDF Product Center no Orbiter Post 4.1.2.12later than 12 hours after the completion of the Report valid until the next LRO TBR – 7 days of LRO range 28FDF-19Maneuver current thruster maneuver. thruster maneuver.predictsReportThe MOC uses a TBR mechanism to “get” the file. Section The file is posted to the FDF Product Center no 4.1.2.13This report is generated within 2 later than 2 hours after the LRO separation from Post-Separation TBR – 1 page of ASCII text 29FDF-20hours after the LRO separation the EELV. Reportinformationfrom the launch vehicle.The MOC uses a TBR mechanism to “get” the file. 6 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section The file is posted to the FDF Product Center on a Contains the next thirty (30) 4.1.2.14weekly basis (Wednesday of the week), no later days of predictive ephemeris Predicted LRO than 4:00 pm, local time (based on the Eastern 30FDF-21data from 0000Z of the next TBREphemeris FileTime zone). subsequent day out through an The MOC uses a TBR mechanism to “get” the additional 30 days.file. Section The file is posted to the FDF Product Center on a Contains the next thirty (30) 4.1.2.15weekly basis (Wednesday of the week), no later Predicted Lunar days of lunar ground track data than 4:00 pm, local time (based on the Eastern 31FDF-22Ground Track from 0000Z of the next TBRTime zone). Filesubsequent day out through an The MOC uses a TBR mechanism to “get” the additional 30 days.file. Section SA Calibration 32FDF-23Product DeletedProduct DeletedProduct DeletedData Section The file is posted to the FDF Product Center on a 4.1.3.5Contains the next (TBR) days of daily basis, no later than 4:00 pm, local time LRO State 33FDF-24LRO State Vectors (centered at TBR(based on the Eastern Time zone). Vector TableTBR minute increments) The MOC uses a TBR mechanism to “get” the file. Section The MOC-ADS-generated file is electronically Star Tracker 4.1.3.6 Valid until the next Star Tracker delivered to the DMS element via a TBR 34FDF-25TBRCalibration datacal functionmechanism. Delivery Date and time are TBR.Section The MOC-ADS-generated file is electronically Thruster 4.1.3.7Valid until the next Thruster cal delivered to the DMS element via a TBR 35FDF-26TBRCalibration Datafunctionmechanism. Delivery Date and time are TBR. 7 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section The MOC-ADS-generated file is electronically Momentum LRO momentum management FDF-27 4.1.3.8delivered to the DMS element via a TBR 36Management Unload Plan only valid for the TBR(New)mechanism. Unload Planidentified time periodDelivery Date and time are TBR.Section The file is posted to the FDF Product Center on a Contains the next (TBR) days of Star Tracker 4.1.2.17daily basis, no later than 4:00 pm, local time FDF-28 data that identifies when the star 37Occultation TBR(based on the Eastern Time zone). (New)tracker is occulted by either the ReportThe MOC uses a TBR mechanism to “get” the moon, earth or sunfile. Section FDF-29 Attitude Slew TBR – based on number The file is electronically delivered via a TBR Valid for the upcoming slews384.1.3.2(New)Reportand types of slews.mechanism Delivery Date and time are TBR Section The file is posted to the FDF Product Center on a The time span for this product is Definitive Lunar 4.1.2.16daily basis, no later than 4:00 pm, local time FDF-30 for the previous 24 hours from 39Ground Track TBR(based on the Eastern Time zone). (New)0000Z of the previous day to FileThe MOC uses a TBR mechanism to “get” the 0000Z of the current day. file. Section TBDThe FDF-generated file is electronically FDF-31 HGA/SA Fixed 40delivered to the user via a TBR mechanism. (New)offset SPKDelivery Date and time are TBR.N/AThe FDF-generated file is electronically FDF-32 41SPK – Planetdelivered to the user via a TBR mechanism. (New)Delivery Date and time are TBR.Section TBDThe FDF-generated file is electronically FDF-33 42Generic PCKdelivered to the user via a TBR mechanism. (New)Delivery Date and time are TBR.Section TBDThe FDF-generated file is electronically FDF-34 43Binary PCKdelivered to the user via a TBR mechanism. (New)Delivery Date and time are TBR. 8 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section TBDThe FDF-generated file is electronically FDF-35 44Predicted CKdelivered to the user via a TBR mechanism. (New)Delivery Date and time are TBR. Section TBDThe FDF-generated file is electronically FDF-36 45Definitive CKdelivered to the user via a TBR mechanism. (New)Delivery Date and time are TBR. SCLK – Section TBDThe FDF-generated file is electronically FDF-37 46Spacecraft clock delivered to the user via a TBR mechanism. (New)correlation fileDelivery Date and time are TBR. LSK – Leap NAThe FDF-generated file is electronically FDF-38 47second delivered to the user via a TBR mechanism. (New)tabulationDelivery Date and time are TBR. Section TBDThe FDF-generated file is electronically FDF-39 FK – Frame 48delivered to the user via a TBR mechanism. (New)KernelsDelivery Date and time are TBR. Section Contains a running summation 4.2.1.5Station Status Packets are delivered to the MOC of requested status data for the SCN Station 49SCN-1andTBRevery 60 seconds in real-time via a TBR last 60 second during the station Status PacketsSection mechanism. contact4.2.1.6 Covers the weekly station Section contacts from Monday, 00:00:00 4.2.1.1GNSO electronically delivers schedule files is to Z for the specified start date up the MOC on a weekly basis via a TBR through 23:59:59Z of the next mechanism. SCN Support subsequent Sunday date. 50SCN-2TBRDelivery Date and time are TBR.SchedulesThe file may actually contain one week plus one day to ensure Operational schedule delivered on the Thursday consistency from one scheduling before the start of the week in question period to the next. 9 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Contains the weather Section information that corresponds to 4.2.1.7The file is electronically delivered to the MOC the time period of the station SCN Weather via a TBR mechanism. 51SCN-3TBRcontact DataDelivery is scheduled to occur within 30 minutes the data are sampled and of the conclusion of the station contact.provided at 30 minute intervals. Section TBR – Based on individual Contains stored science Ka-Band 4.2.1.8science instrument and measurement data files as The file is electronically delivered to the MOC Measurement science Housekeeping filesdefined within the 52SCN-4via a TBR mechanism, within 30 minutes of the Data Files Files can be bounded based corresponding Data Instrument completion of the WS1 station contact(VC3)on time limits, size limits, ICD.or command Laser Range Section TBD 53SCN-5Transmit Only to LOLA and should be removedInformation Section Data delivered either 4.2.1.21) Real-time to FDF. (backup also has files Tracking data correspond to TBR – max time limit for a created at hourly intervals) Realtime support is received UTDF data from the file is 5 minutes (nominal for mission critical activities.last 5 minutes (nominal case) or Raw Tracking 54SCN-6case) or Hourly files as over the last hour (when data is Data Files2) Files to both FDF and MOC every 5 minutes.backup when data is forwarded via real-time The files are electronically delivered to the FDF transmitted in R/T to FDF.connection))and the MOC via a TBR mechanism, 10 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section The data are delivered electronically to the MOC 4.2.1.4 via a real-time socket connection; data are delivered with near real-time of receipt at the The data is delivered in near Real-time VC0 TBR – based on downlink station (within TBD seconds)55SCN-7real-time to the LRO MOC as it orbiter telemetrydata rateStations perform the Reed-Solomon decoding of is received by the station. the data prior to delivery to the LRO MOC (VC0 – VC3) or to the WS1 mission unique equipment (VC2 and VC3). Section The data are delivered electronically to the MOC The data is delivered in near Real-time VC1, 4.2.1.4TBR – based on downlink via a real-time socket connection, data are 56SCN-8real-time to the LRO MOC as it VC2, VC3 datadata ratedelivered with near real-time of receipt at the is received by the station. station (within TBD seconds) Section The file is electronically delivered to the MOC Corresponds to the last WS1 Ka-Band RF 4.2.1.9and FDF via a TBR mechanism; , within 30 57SCN-9TBRstation contact (AOS to LOS)Receiver Dataminutes of the completion of the WS1 station contact Section The data consists of the status The file is electronically delivered to the MOC CFDP Status 4.2.1.10information that is valid from via a real-time socket connection, data packets Messages from 58SCN-10the last time interval since from TBRare delivered with near real-time of receipt at the SCN/DPS to when the MUE generated the station (within TBD seconds) of the MOC/DPSlast status message.corresponding CFDP Control Message Section TBR - dependant upon the Stored HK Data 4.2.1.3The Stored Data files are kept virtual channel and the time The files are electronically delivered to the MOC 59SCN-11Files (VC0–on site at the station for up to 72 duration of the real-time via a TBR mechanism, based on an FOT VC3)hours. pass, as well as the generated request to play back a specified file downlink rate 11 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section Realtime and File simulated Telemetry from 4.5.1.1telemetry is valid only during Real-time - The real-time data are electronically TBR – based on realtime launch Site test phasedelivered to the MOC via a socket connection. 60KSC-1rates or file sizes to support (Real-time and Relatime operational telemetry FTP Files - The file is electronically delivered to mission rehearsalsFTP files)is valid during post-launch the MOC via a TBR mechanism. support activities Command Request active until Section LAMP The file is electronically delivered to the MOC the next load is uplinked to the 4.3.3.1TBR – based on number of 61LAMP-1Command via a TBR mechanism, spacecraft; nominally daily or commandsRequestdelivery date and time are TBRweekly instrument loads. HV Command Sequence active Section LAMP HV The file is electronically delivered to the MOC until the next load is uplinked to 4.3.3.2TBR – based on number of 62LAMP-2command via a TBR mechanism., delivery date and time the spacecraft; nominally daily commandssequenceare TBRor weekly instrument loads. The LAMP Instrument FSW Section LAMP The file is electronically delivered to the MOC TBR – based on FSW Load is active until the next load 4.3.3.363LAMP-3Instrument FSW via a TBR mechanism., Image being uploadedis uplinked to the spacecraft.Loadsdelivery date and time are TBRSection via fax to FDF, at GSFC in Building 28, room 4.5.1.2File is delivered approximately TBD. Launch Launch Vehicle 6430 minutes after spacecraft 1 page text informationThe fax telephone number is 301-286-xxxx). Vehicle-1Post-Sep Vectorseparationbackup mechanism is to directly phone the flight dynamic’s facility at 301-286-yyyy). Command Request active until Section LEND The file is electronically delivered to the MOC the next load is uplinked to the 4.3.4.1TBR – based on number of 65LEND-1Command via a TBR mechanism, spacecraft; nominally daily or commandsRequestdelivery date and time are TBRweekly instrument loads. 12 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference LEND Section The LEND Instrument FSW The file is electronically delivered to the MOC TBR – based on FSW 66LEND-2Instrument FSW 4.3.4.2Load is active until the next load via a TBR mechanism, delivery date and time are Image being uploadedLoadsis uplinked to the spacecraft.TBR Command Request active until Section LOLA The file is electronically delivered to the MOC the next load is uplinked to the 4.3.5.1TBR – based on number of 67LOLA-1Command via a TBR mechanism, spacecraft; nominally daily or commandsRequestdelivery date and time are TBRweekly instrument loads. Section The updated gravity model 4.3.5.2generated approximately every TBR – based on size and The file is electronically delivered to the FDF and LOLA Gravity six months (TBR) and is based 68LOLA-2parameters for the new MOC via a TBR mechanism; Modelon the previous six months of Gravity Modeldelivery date and time are TBR. Laser Ranging transmit data and other tracking data. LOLA Section The LOLA Instrument FSW The file is electronically delivered to the MOC TBR – based on FSW 69LOLA-3Instrument FSW 4.3.5.3Load is active until the next load via a TBR mechanism; delivery date and time are Image being uploadedLoadsis uplinked to the spacecraft.TBR. Section TBR – based on size and TBSLOLA The file is electronically delivered to the FDF and 4.3.5.4parameters for the sampling 70LOLA-4Processed OD MOC via a TBR mechanism, delivery date and rate for the LOLA Process informationtime are TBR. OD data Section LOLA Target Requests active The file is electronically delivered to the MOC LOLA Target 4.3.5.5and valid only for the associated TBR – based on number of 71LOLA-5via a TBR mechanism; delivery date and time are Requesttime period identified in the commandsTBR. commands LROC Section Command Request active until Instrument 4.3.6.1The file is electronically delivered to the MOC the next load is uplinked to the TBR – based on number of 72LROC-1Initialization via a TBR mechanism, spacecraft; nominally daily or commandsCommand delivery date and time are TBRweekly instrument loads.Sequence 13 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Section Daily Command Sequence LROC Daily The file is electronically delivered to the MOC 4.3.6.2active for 24 hours until the next TBR – based on number of 73LROC-2Command via a TBR mechanism; delivery date and time are load is uplinked to the commandsSequence - TBR. spacecraft. Section 74LROC-5 TBR – based on FSW LROC Section The LROC Instrument FSW The file is electronically delivered to the MOC Image being uploaded75LROC-3Instrument FSW 4.3.6.3Load is active until the next load via a TBR mechanism; delivery date and time are Loadsis uplinked to the spacecraft.TBR. TBR – based on number of Section LROC Target Requests active The file is electronically delivered to the MOC LROC Target commands76LROC-44.3.6.4 and valid only for the time via a TBR mechanism; delivery date and time are Requestassociated in the command loadTBR. TBR – based on number of Section The Mini-RF Load File is active The file is electronically delivered to the MOC Mini-RF Load commands77Mini-RF-14.3.7.1until the next load is uplinked to via a TBR mechanism; delivery date and time are Filesthe spacecraft.TBR. Mini-RF Section Command Timeline active until The file is electronically delivered to the MOC TBR – based on number of 78Mini-RF-2Command 4.3.7.2the next load is uplinked to the via a TBR mechanism; delivery date and time are commandsTimelinespacecraft.TBR. Section Beta Angle The file is electronically delivered via a TBR 79MOC-14.1.2.2Predictsmechanism; delivery date and time are TBR. Section The CFDP Control delivered via a realtime 4.4.3.4socket connection to the MUE located at WS1 80MOC-2CFDP Controlstation CFDP Controls issued every TBR seconds 14 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Valid for previous day’s clock Section The Clock Correlation file is electronically updates from 0000Z of the 4.4.1.1.2Clock 81MOC-3TBRdelivered on a daily basis via a TBR mechanismprevious day to 0000Z of the Correlation Filedelivery time are TBR. current day. . Section The commands are sent electronically via a real-Commands to 82MOC-484.5.2.2time socket connectionKSCdelivery date and time are TBR. CRaTER - Section Data corresponds to that which The file is electronically delivered to the TBR – based on time since 83MOC-4Spacecraft HK 4.4.1.1.3was downlinked during the last CRaTER SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR CRaTER HK 84MOC-54.4.1.1.4mechanismData Filesdelivery date and time are TBR. CRaTER Raw Section The file is electronically delivered via a TBR 85MOC-6Measurement 4.4.1.1.5mechanism Data Filesdelivery date and time are TBR. CRaTER Real-Section The data are delivered electronically to the 86MOC-7time VC0 HK 4.4.1.1.6CRaTER SOC via a real-time socket connectiondata Section The file is electronically delivered via a TBR Daily Command 87MOC-84.4.1.1.7mechanismLoaddelivery date and time are TBR. Section The file is electronically delivered via a TBR LRO Definitive 88MOC-94.1.2.3mechanismEphemeris Filedelivery date and time are TBR. 15 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference DLRE - Section Data corresponds to that which The file is electronically delivered to the DLRE TBR – based on time since 89MOC-10Spacecraft HK 4.4.1.2.5was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR DLRE HK Data 90MOC-114.4.1.2.6mechanismFilesdelivery date and time are TBR. DLRE Raw Section The file is electronically delivered via a TBR 91MOC-12Measurement 4.4.1.2.7mechanism Data Filesdelivery date and time are TBR. Section The file is electronically delivered via a TBR DLRE Real-time 92MOC-134.4.1.2.8mechanismVC0 HK data Section SCN Weather The file is electronically delivered via a TBR 93MOC-144.2.1.7Datamechanism Ground Station Section The file is electronically delivered via a TBR 94MOC-20View Period 4.1.2.1mechanismPredicts LAMP - Section Data corresponds to that which The file is electronically delivered to the LAMP TBR – based on time since 95MOC-15Spacecraft HK 4.4.1.3.5was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR LAMP HK Data 96MOC-164.4.1.3.6mechanismFilesdelivery date and time are TBR. LAMP Raw Section The file is electronically delivered via a TBR 97MOC-17Measurement 4.4.1.3.7mechanism Data Filesdelivery date and time are TBR. 16 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference LAMP Real-Section The data are delivered electronically to the 98MOC-18time VC0 HK 4.4.1.3.8LAMP SOC via a real-time socket connectiondata Laser Range Section 99MOC-19Transmit Information LEND - Section Data corresponds to that which The file is electronically delivered to the LAMP TBR – based on time since 100MOC-21Spacecraft HK 4.4.1.4.5was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section LEND HK Data The file is electronically delivered via a TBR 101MOC-224.4.1.4.6Filesmechanism LEND Raw Section The file is electronically delivered via a TBR 102MOC-23Measurement 4.4.1.4.7mechanismData Files Section LEND Real-time The data are delivered electronically to the 103MOC-244.4.1.4.8VC0 HK dataLEND SOC via a real-time socket connectionLOLA - Section Data corresponds to that which The file is electronically delivered to the LAMP TBR – based on time since 104MOC-25Spacecraft HK 4.4.1.5.5was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR LOLA HK Data 105MOC-264.4.1.5.6mechanismFilesdelivery date and time are TBR. LOLA Raw Section The file is electronically delivered via a TBR 106MOC-27Measurement 4.4.1.5.7mechanism Data Filesdelivery date and time are TBR. 17 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference LRO SPICE 107MOC-47Files Definitive LRO SPICE 108MOC-28Files Predicts LROC - Section Data corresponds to that which The file is electronically delivered to the LAMP TBR – based on time since 109MOC-29Spacecraft HK 4.4.1.6.7was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR LROC HK Data 110MOC-304.4.1.6.8mechanismFilesdelivery date and time are TBRLROC Raw Section The file is electronically delivered via a TBR 111MOC-31Measurement 4.4.1.6.9mechanism Data Filesdelivery date and time are TBRLunar Orbit Section The file is electronically delivered via a TBR Ascending and 4.1.2.6112MOC-32mechanismDescending delivery date and time are TBRNode Predicts Lunar Orbit Section The file is electronically delivered via a TBR Terminator 4.1.2.7113MOC-33mechanismCrossing delivery date and time are TBRPredicts Mini-RF - Section Data corresponds to that which The file is electronically delivered to the LAMP TBR – based on time since 114MOC-34Spacecraft HK 4.4.1.7.9was downlinked during the last SOC via a TBR mechanismlast station contactData Filereal-time station contactdelivery time is TBR. Section The file is electronically delivered via a TBR Mini-RF HK 115MOC-354.4.1.7.10mechanismData Filesdelivery date and time are TBR. 18 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Mini-RF Section The file is electronically delivered via a TBR 116MOC-36Operations 4.4.1.7.11mechanism Opportunitydelivery date and time are TBR. Mini-RF Raw Section The file is electronically delivered via a TBR 117MOC-37Measurement 4.4.1.7.12mechanism Data Filesdelivery date and time are TBR. Section Mission Eclipse The file is electronically delivered via a TBR 118MOC-384.1.2.8Predictsmechanism Section Post-Maneuver The file is electronically delivered via a TBR 119MOC-394.1.2.12Spacecraft Massmechanism Section Predicted LRO The file is electronically delivered via a TBR 120MOC-404.1.2.14Ephemeris Filemechanism Predicted Lunar Section The file is electronically delivered via a TBR 121MOC-41Ground Track 4.1.2.15mechanismFile Section Raw Attitude The file is electronically delivered via a TBR 122MOC-424.1.3.1Data Filemechanism Section Raw Tracking 4.2.1.2 andThe file is electronically delivered via a TBR 123MOC-43Data FilesSection mechanism 4.2.2.1 Real-Time Section The commands are sent via real-time socket 124MOC-44orbiter 4.4.3.1connects to the USN/WS1 stationcommands 19 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Section No.IDProduct NameTimespanVolumeDelivery Mechanism and File ConventionsReference Real-Time Section orbiter 4.4.3.1The commands are sent via real-time socket 125MOC-45commands - connects to the DSN stationDSN Section Telemetry to The telemetry data are electronically delivered to 126MOC-494.5.2.1KSCthe KSC launch site via a socket connection Definitive Lunar Section The file is electronically delivered via a TBR 127MOC-50Ground Track 4.1.2.16mechanismFile SCN Support Section The file is electronically delivered via a TBR 128MOC-51Schedules4.2.1.1mechanism 20 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.1FLIGHT 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 (.):.; where , FDFnn_YYYYDOY.HHMMSS_vn; where FDFnn => 5 ASCII characters in which the nn refers to the identifier listed as the LRO Ground System Product Matrix; for example FDF01 = Attitude Determination Report FDF02 = Attitude Slew Plan FDF06 = Ground Network Acquisition Data File YYYYDOY => 7 ASCII characters YYYY => 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 time HH => 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 , 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 designation 21 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT tls, for leap second files 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.1FDF 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.1SCN Station Acquisition Data 4.1.1.1.1Product Description This 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 mission4.1.1.1.2Support Duration The FDF will provide the Station Acquisition Data throughout all mission phases, from pre-launch (to support mission rehearsals and other project related tests) up through the actual mission and concluding with end-of-mission support. 4.1.1.1.3Format The 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 nameField Characteristics station name4 ASCII text characters representing the unique station identifies timetag information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 22 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics rangeRRRRRRR.ddddd RRRRRR => 6 ASCII digits for whole range (0 – 999999) ddddd => 5 ASCII digits for decimal portion of range (00 – 99999)Range rateRR.dddddd RR => 2 ASCII digits for whole range rate (0 – 99) dddddd => 6 ASCII digits for decimal portion of range (00 – 999999)azimuth angleAAA.ddd AAA => 3 ASCII digits for whole angle measurement (0 – 360) ddd => 3 ASCII digits for decimal portion of range (00 – 999)elevation angleEE.ddd EE => 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: _. whereFile 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 Characters 4 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 Characters 15 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.1.1.1.4Accuracy and Completeness The 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.2DSN Site Acquisition Data 4.1.1.2.1Product Description The 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.2Support Duration 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.2.3Format The format is the predicted SPICE SPK formatted file; this format is consistent with the information listed at the following URL: A sample file name for the first generation of this data file is given as FDF05_10152006_01.bspThis file format and content are defined in Appendix B.1-2. 4.1.1.2.4Accuracy and Completeness The 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.3Laser Ranging Site Prediction Data 4.1.1.3.1Product Description The 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.2Support Duration 24 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.3Format The 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: ;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.txtA sample Laser Ranging Site Prediction Data file is provided as a reference in Appendix B.1-3.4.1.1.3.4Accuracy and Completeness 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.2FDF 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.1Ground Station View Period Predicts Data 4.1.2.1.1Product Description The 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.2Support Duration FDF 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.3Format This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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: Field nameField Characteristics station name4 ASCII text characters representing the unique station identifiesStart time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Stop time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Antennae Flag1 ASCII Character flag to indicate whether this is a HGA or OMNI view period H => LRO HGA is viewable from the ground station O => LRO omni is viewable from the ground station elevation angleEE.dd EE => 2 ASCII digits for whole angle measurement (0 – 90) dd => 3 ASCII digits for decimal portion of range (00 – 99) A sample file name for the first generation of this data file is given as FDF07_10152006_01.txt A sample Ground Station View Period Predict Data file is provided as a reference in Appendix B.1-4. 4.1.2.1.4Accuracy and Completeness 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.2LRO Beta Angle Predict File 4.1.2.2.1Product Description 26 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration FDF will generate this file for all mission phases. 4.1.2.2.3Format The 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 nameField Characteristics time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Beta Angle SBB.bb => 6 ASCII characters including the period between the first 3 and last 2 the 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 angle last 2 are the decimal portion of the Beta angle QuadrantN => 1 ASCII character that identifies the quadrant information related to the Beta Angle definition. Allowable values are: 1 – 4 inclusive A sample file name for the first generation of this data file is given as FDF03_10152006_01.txtA sample LRO Beta Angle File data file is provided as a reference in Appendix B.1-5.4.1.2.2.4Accuracy and Completeness 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.3LRO Definitive Ephemeris File 4.1.2.3.1Product Description 27 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration FDF will generate this file for all mission phases. 4.1.2.3.3Format The 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: Field nameField Characteristics time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 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 position last 3 are the decimal portion of the X-component positionY-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 position last 3 are the decimal portion of the Y-component positionZ-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 position last 3 are the decimal portion of the Z-component positionX-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the X-component velocityY-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Y-component velocity 28 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Z-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component velocity A sample file name for the first generation of this data file is given as FDF04_10152006_01.txtA sample LRO Definitive Ephemeris File data file is provided as a reference in Appendix B.1-6.4.1.2.3.4Accuracy and Completeness 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.4LRO Definitive SPICE File 4.1.2.4.1Product Description This 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.2Support Duration FDF will generate this file for all mission phases. 4.1.2.4.3Format The 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: A sample file name for the first generation of this data file is given as FDF11_10152006_01.bspA sample LRO Definitive SPICE File is provided as a reference in Appendix B.1-7.4.1.2.4.4Accuracy and Completeness 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.5LRO Predictive SPICE File 4.1.2.5.1Product Description This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration FDF will generate this file for all mission phases. 4.1.2.5.3Format The 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: A sample file name for the first generation of this data file is given as FDF12_10152006_01.bspA sample LRO Predictive SPICE File data file is provided as a reference in Appendix B.1-8.4.1.2.5.4Accuracy and Completeness 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.6Lunar Orbit Ascending and Descending Node Predicts 4.1.2.6.1Product Description This 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.2Support Duration FDF will generate this file during all mission phases and immediately after a maneuver.4.1.2.6.3Format This 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 nameField Characteristics timetag information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 30 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Node Crossing Type1 Character ASCII flag to indicate if the type of nodal crossing A => Ascending Node Crossing Type D => Descending Node Crossing Type Lunar LongitudeAAA.ddd AAA => 3 ASCII digits for whole angle measurement (0 – 360) dd => 2 ASCII digits for decimal portion of range (00 – 99) The lunar longitude is consistent with the DE400 coordinate system A sample file name for the first generation of this data file is given as FDF13_10152006_01.txtA sample LRO Ascending Descending Node data product is provided as a reference in Appendix B.1-9. 4.1.2.6.4Accuracy and Completeness The 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.7Lunar Orbit Terminator Crossing Predicts 4.1.2.7.1Product Description This is a file that contains lunar terminator crossing predicts associated when the LRO spacecraft crosses the lunar terminator line. 4.1.2.7.2Support Duration FDF will generate this file during all mission phases and immediately after a maneuver.4.1.2.7.3Format This 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: Field nameField Characteristics time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 31 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Lunar Terminator Type1 Character ASCII flag to indicate if the type of terminator crossing N => Into Lunar Night (going from Lunar Day into night) D => Out from Lunar Night (going from Lunar Night into day ) A sample file name for the first generation of this data file is given as FDF14_10152006_01.txtA sample LRO Ascending Descending Node data product is provided as a reference in Appendix B.1-10. 4.1.2.7.4Accuracy and Completeness The 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.8Mission Eclipse Predicts 4.1.2.8.1Product Description This 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.2Support Duration FDF will generate this file during all mission phases and immediately after a maneuver.4.1.2.8.3Format FDF 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 nameField Characteristics Start time information:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 32 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Stop time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Shadow Flag1 ASCII Character flag to indicate if the type of eclipse P => LRO is in penumbra eclipse U => LRO is in umbra eclipse DurationMMM..ddd MMM => 3 ASCII digits for whole portion of minutes (0 – 160) ddd => 3 ASCII digits for decimal portion of minutes (000 – 999) Occultation Flag1 ASCII Character flag to identify the eclipse cause M => Moon is cause of eclipse E => Earth is cause of eclipse This file contains 90-days worth of mission eclipse information for either lunar or earth eclipses.A sample file name for the first generation of this data file is given as FDF15_10152006_01.txtA sample LRO Mission Eclipse data product is provided as a reference in Appendix B.1-11.4.1.2.8.4Accuracy and Completeness The 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.9Lunar Ephemeris 4.1.2.9.1Product Description This 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.2Support Duration FDF will generate this file during all mission phases. 4.1.2.9.3Format The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Timetag:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 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 the moon’s position last 3 are the decimal portion of the X-component positionY-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 moon’s position last 3 are the decimal portion of the Y-component positionZ-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 moon’s position last 3 are the decimal portion of the Z-component positionX-VelocityRRRRRR.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 moon’s velocity last 3 are the decimal portion of the X-component positionY-VelocityRRRRRR.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 moon’s velocity last 3 are the decimal portion of the Y-component positionZ-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component positionThis file contains seven days of moon ephemeris information.A sample file name for the first generation of this data file is given as FDF16_10152006_01.txt A sample of the Moon Ephemeris data product is provided as a reference in Appendix B.1-12. 4.1.2.9.4Accuracy and Completeness The 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.10Orbiter Thruster Maneuver Plans 4.1.2.10.1Product Description 34 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration FDF will generate this file during all mission phases in preparation for the next scheduled maneuver. 4.1.2.10.3Format This 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 file name for the first generation of this data file is given as FDF17_10152006_01.txtA sample of the Orbiter Thruster Maneuver Plan product is provided as a reference in Appendix B.1-13. 4.1.2.10.4Accuracy and Completeness The data file will contain all thruster information related to this upcoming LRO maneuver; it will be accurate to TBD criteria. 4.1.2.11Orbiter to Earth Range Predicts 4.1.2.11.1Product Description This 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.2Support Duration FDF will generate this file during all mission phases in preparation for the next scheduled maneuver. 4.1.2.11.3Format The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT is followed by 1:N lines of station acquisition information. The standard fields and field description are listed in the following table. Field nameField Characteristics station name4 ASCII text characters representing the unique station identifies timetag information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day rangeRRRRRRR.ddd RRRRRR => 6 ASCII digits for whole range (0 – 999999) ddd => 3 ASCII digits for decimal portion of range (00 – 999) Range rateRRRRRRR.ddd RRRRRR => 6 ASCII digits for whole range (0 – 999999) ddd => 3 ASCII digits for decimal portion of range (00 – 999) A sample file name for the first generation of this data file is given as FDF18_10152006_01.txtA sample Orbiter to Earth Range Predict data product is provided as a reference in Appendix B.1-14. 4.1.2.11.4Accuracy and Completeness The 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.12Orbiter Post Maneuver Report 4.1.2.12.1Product Description This 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.2Support Duration This 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.3Format 36 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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 nameField Characteristics Thruster Used2 ASCII Characters that identified the LRO thruster used in the maneuver 01 – 08 Maneuver Start Time:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Maneuver Stop Time:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Expected Fuel Used RRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3 first 4 are the whole portions of the fuel used last 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 3 first 4 are the whole portions of the remaining fuel last 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 3 first 4 are the whole portions of the fuel used last 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 3 first 4 are the whole portions of the remaining fuel last 3 are the decimal portion of the remaining fuel Propellant Tank PressureRRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3 first 4 are the whole portions of the current tank pressure last 3 are the decimal portion of the current tank pressure Propellant Tank TemperatureRRRR.rrr => 8 ASCII characters including the period between the first 4 and last 3 first 4 are the whole portions of the current tank temperature last 3 are the decimal portion of the current tank temperature 37 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Expected 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 mass last 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 3 first 4 are the whole portions of the actual orbiter mass last 3 are the decimal portion of the actual orbiter mass Targeted ManeuverVVV.vvv => 7 ASCII characters including the period between the first 3 and last 3 first 3 are the whole portions of the targeted maneuver velocity last 3 are the decimal portion of the targeted maneuver velocity Targeted ManeuverVVV.vvv => 7 ASCII characters including the period between the first 3 and last 3 first 3 are the whole portions of the actual maneuver velocity last 3 are the decimal portion of the actual maneuver velocity A sample file name for the first generation of this data file is given as FDF19_10152006_01.txtA sample of the Post Orbiter Maneuver Report product is provided as a reference in Appendix B.1-15. 4.1.2.12.4Accuracy and Completeness TBR 4.1.2.13Post Separation Report 4.1.2.13.1Product Description This 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.2Support Duration FDF 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.3Format The 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 nameField Characteristics Line 1 – from EELV Launch Support Team 38 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics LV SeparationTime:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day X-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value X-component of the LV separation position last 3 are the decimal portion of the X-component positionY-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Y-component of the LV separation position last 3 are the decimal portion of the X-component positionZ-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Z-component of the LV separation position last 3 are the decimal portion of the Z-component positionX-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value X-component of the LV separation velocity last 3 are the decimal portion of the X-component velocityY-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Y-component of the LV separation velocity last 3 are the decimal portion of the Y-component velocityZ-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Z-component of the LV separation velocity last 3 are the decimal portion of the Z-component velocityLV Position Vector RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Magnitude last 3 first 6 are the whole portions of the Magnitude of the position vector last 3 are the decimal portion of the Magnitude of the position vectorLV Velocity Vector RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Magnitudelast 3 first 6 are the whole portions of the Magnitude of the velocity vector last 3 are the decimal portion of the Magnitude of the velocity vector Line 2 – FDF Calculated Data 39 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics FDF Calculated YYYY DOY HHMMSS.MMM, where SeparationTime:YYYY => 4 ASCII digits of year (2008 – 2013) yearDOY => 3 ASCII digits for day of year (1 – 366) day of year and HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3time of dayfirst 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day X-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value X-component of the FDF separation position last 3 are the decimal portion of the X-component positionY-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Y-component of the FDF separation position last 3 are the decimal portion of the X-component positionZ-Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Z-component of the FDF separation position last 3 are the decimal portion of the Z-component positionX-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value X-component of the FDF separation velocity last 3 are the decimal portion of the X-component velocityY-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Y-component of the FDF separation velocity last 3 are the decimal portion of the Y-component velocityZ-VelocityRRRRRR.rrr => 10 ASCII characters including the period between the first 6 and last 3 first 6 are the whole value Z-component of the FDF separation velocity last 3 are the decimal portion of the Z-component velocityFDF Position Vector RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Magnitude last 3 first 6 are the whole portions of the Magnitude of the position vector last 3 are the decimal portion of the Magnitude of the position vectorFDF Velocity Vector RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Magnitudelast 3 first 6 are the whole portions of the Magnitude of the velocity vector last 3 are the decimal portion of the Magnitude of the velocity vector Line 3 – Launch Vehicle Separation Comparison Magnitude of the Position RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Differencelast 3 first 6 are the whole portions of the position Delta Magnitude last 3 are the decimal portion of the position Delta Magnitude 40 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Magnitude of the Velocity RRRRRR.rrr => 10 ASCII characters including the period between the first 6 and Differencelast 3 first 6 are the whole portions of velocity Delta Magnitude last 3 are the decimal portion of the Delta Magnitude A sample file name for the first generation of this data file is given as FDF20_10152006_01.txtA sample of the Post Separation Report product is provided as a reference in Appendix B.1-16.4.1.2.13.4Accuracy and Completeness TBD 4.1.2.14Predicted LRO Ephemeris File 4.1.2.14.1Product Description This 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.2Support Duration FDF will generate this file for all mission phases. 4.1.2.14.3Format The 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: Field nameField Characteristics time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day 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 position last 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 position last 3 are the decimal portion of the Y-component position 41 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 position last 3 are the decimal portion of the Z-component position X-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the X-component velocity Y-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Y-component velocity Z-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component velocity A sample file name for the first generation of this data file is given as FDF21_10152006_01.txtA sample Predictive LRO Ephemeris File data file is provided as a reference in Appendix B-1.17. 4.1.2.14.4Accuracy and Completeness 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.15Predicted Lunar Ground Track File 4.1.2.15.1Product Description This file contains the predictive LRO ground track against the lunar surface. 4.1.2.15.2Support Duration FDF will generate this file for all mission phases. 4.1.2.15.3Format The 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 nameField Characteristics 42 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Lunar Longitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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 3 first character is the sign (blank = Northern Lats; - = Southern Lats) next 2 are the whole degrees of Latitude (0- 90) last 3 are the degree decimal of Latitude (000- 999) LRO Altitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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) X-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the X-component velocityY-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Y-component velocityZ-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component velocityA sample file name for the first generation of this data file is given as FDF22_10152006_01.txt A sample LRO Predictive Lunar Ground Track File is provided as a reference in Appendix B-1.18. 4.1.2.15.4Accuracy and Completeness 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.16Definitive Lunar Ground Track File 4.1.2.16.1Product Description This file contains the definitive LRO ground track against the lunar surface based on the most recent definitive ephemeris. 43 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.1.2.16.2Support Duration FDF will generate this file for all mission phases. 4.1.2.16.3Format The 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: Field nameField Characteristics time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Lunar Longitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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 3 first character is the sign (blank = Northern Lats; - = Southern Lats) next 2 are the whole degrees of Latitude (0- 90) last 3 are the degree decimal of Latitude (000- 999) LRO Altitude RRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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) X-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the X-component velocity Y-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Y-component velocity Z-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component velocity A sample file name for the first generation of this data file is given as FDF30_10152006_01.txt 44 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample Definitive Lunar Ground Track File is provided as a reference in Appendix B-1.19.4.1.2.16.4Accuracy and Completeness 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.17Star Tracker Occultation Report 4.1.2.17.1Product Description This is a report that includes identified when the star tracker field of view is occulted by the moon. 4.1.2.17.2Support Duration The 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.3Format The 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 nameField Characteristics Occultation Start Time:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Occultation Stop Time:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Occultation DurationMMM.mm => 6 ASCII digits with a period between the first 3 and last 2 first 3 are the whole minutes of occultation (0 -999) last 2 are the decimal portion of the occultation (0 – 99) Occultation FlagO => 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample file name for the first generation of this data file is given as FDF28_10152006_01.txtA sample Star Tracker Occultation Report is provided as a reference in Appendix B-1.284.1.2.17.4Accuracy and Completeness 4.1.3FDF 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.1Attitude Determination Verification Report 4.1.3.1.1Product Description This 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.2Support Duration The MOC-ADS provides this report for all mission phases 4.1.3.1.3Format The 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 file name for the first generation of this data file is given as FDF01_10152006_01.txtA sample Attitude Determination Verification Report file is provided as a reference in Appendix B-1.20. 4.1.3.1.4Accuracy and Completeness The report is accurate to TBR 4.1.3.2Attitude Slew Plans 4.1.3.2.1Product Description This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.1.3.2.2Support Duration The MOC-ADS provides this report for all mission phases 4.1.3.2.3Format The 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 nameField Characteristics Slew TypeST => 1 ASCII Character that identifies the type of slew = T; Table Offset =P; off-nadir pointing time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Off-Nadir Slew Angle RRR.rrr => 6 ASCII characters including the period between the first 3 and last 3 first 2 are the whole degrees of requested slew (0- 99) last 3 are the degree decimal of Longitude (000- 999) Attitude Quaternions4 quaternions that represent the attitude of the requested slew; each quaternion has Q1one of the following two representation: (-.rrrrrr or .rrrrrr)) Q21 ASCII Signed Character (Blank represents a positive Q or – for a negative Q) Q3an ASCII character for the decimal point Q4 6 ASCII characters representing the decimal portion of the attitude Q A sample file name for the first generation of this data file is given as FDF02_10152006_01.txtA sample Attitude Slew Plan file is provided as a reference in Appendix B-1.21.4.1.3.2.4Accuracy and Completeness The report is accurate to TBR 4.1.3.3Gyro Calibration Data 4.1.3.3.1Product Description This 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).4.1.3.3.2Support Duration 47 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.3Format The 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 file name for the first generation of this data file is given as FDF08_10152006_01.txtA sample Gyro Calibration Data File is provided as a reference in Appendix B-1.22.4.1.3.3.4Accuracy and Completeness 4.1.3.4HGA Calibration Data 4.1.3.4.1Product Description This is a report that includes updated parameters for HGA calibration table. 4.1.3.4.2Support Duration The 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.3Format The 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 file name for the first generation of this data file is given as FDF09_10152006_01.txtA sample Gyro Calibration Data File is provided as a reference in Appendix B-1.23.. 4.1.3.4.4Accuracy and Completeness 48 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.1.3.5LRO State Vector Table 4.1.3.5.1Product Description The 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.2Support Duration The 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.3Format The 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: Field nameField Characteristics time information:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day X-PositionRRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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-PositionRRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 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-PositionRRR.rrr => 7 ASCII characters including the period between the first 3 and last 3 first 3 are the whole degrees of Z-position vector information (0- 999) last 3 are the degree decimal of the Z-Position (000- 999) X-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the X-component velocity 49 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Y-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Y-component velocity Z-VelocityRRRRRR.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 velocity last 3 are the decimal portion of the Z-component velocity A sample file name for the first generation of this data file is given as FDF24_10152006_01.txtA sample LRO State Vector Table is provided as a reference in Appendix B-1.24.. 4.1.3.5.4Accuracy and Completeness 4.1.3.6Star Tracker Calibration Data 4.1.3.6.1Product Description This is a report that includes updated parameters for Star Tracker calibration table.4.1.3.6.2Support Duration The 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.3Format The 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 file name for the first generation of this data file is given as FDF25_10152006_01.txtA sample Star Tracker Calibration Data File is provided as a reference in Appendix B-1.25.4.1.3.6.4Accuracy and Completeness 4.1.3.7Thruster Calibration Data 4.1.3.7.1Product Description 50 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT This is a report that includes updated parameters for thruster calibration table.4.1.3.7.2Support Duration The 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.3Format The 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 file name for the first generation of this data file is given as FDF26_10152006_01.txtA sample Star Tracker Calibration Data File is provided as a reference in Appendix B-1.26.4.1.3.7.4Accuracy and Completeness 4.1.3.8LRO Momentum Management Unload Plan 4.1.3.8.1Product Description This is a report that identifies when the LRO spacecraft will perform a momentum management maneuver. 4.1.3.8.2Support Duration The 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.3Format The 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 file name for the first generation of this data file is given as FDF27_10152006_01.txtA sample LRO Momentum Management Unload Plan File is provided as a reference in Appendix B-1.27. 4.1.3.8.4Accuracy and Completeness 51 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.2STATION PRODUCTS AND DESCRIPTIONS 4.2.1Space 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.1Station Support Schedules 4.2.1.1.1Product Description This 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.2Support Duration The 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.3Format The 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 nameField Characteristics Station Name4 ASCII Characters that uniquely identify the station 52 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Start time:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Stop time:YYYY DOY HHMMSS.mmm, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Support Activity Code 4 ASCII Character that identifies the station configuration used to support the LRO station contact; allowable values are: TR1 – TR99 Orbit Number10 ASCII Characters representing a monotonically increasing orbit counterBand2 ASCII Characters representing the support contact type; where S1 = S-band Support xx = Ka-Band Support Antenna Used1 ASCII characters that identify the LRO antenna used for this support H => High Gain Antenna scheduled O => 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.14.2.1.1.4Accuracy and Completeness The 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.2Station Tracking Data 4.2.1.2.1Product Description The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration The 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.3Format This 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. ByteFormatDescription 10D(16)Fixed 20A(16)Fixed 301(16)Fixed 4-5ASCIITracking Data Router 4141=AA=GSFC 4444=DD=GSFC 54 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT ByteFormatDescription 6BinaryLast two digits of current year 7-8BinarySatellite Identification Code (SIC) 9-10BinaryVehicle Identification (VID) 11-14BinarySeconds of year 15-18BinaryMicroseconds 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 -8raw angle in degrees, multiply decimal angle by 8.381903173 x 10 (360 degrees divided by 232)19-22FOCAngle 1: X or az 23-26FOCAngle 2; Y or el (angle 2 byte/bit format is the same as for bytes 19- 22.) 27-32BinaryRTLT in 1/256 nsec (MSB = 524288 ns; LSB = 0.00390625 ns)33-38BinaryBias Doppler, counts of: 240 MHz +1000 fd1 LSB - 1 count39-40BinaryAGC (an integer * (-150/8192) AGC-50=dBm)41-44BinaryTransmit frequency information in 10's of Hz45DiscreteMSD = 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) = spares46BinaryPad ID (xmit) 47DiscreteAntenna size (rcv) – (see byte 45) 55 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFTByteFormatDescription 48BinaryPad ID (rcv) 49-50DiscreteMode-system unique (refer to Table 2) 51DiscreteData 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)52DiscreteMSD = 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 1(16) = spare 2(16) = simulated 3(16) = resubmit 4(16) = RT (real time) 5(16) = PB (playback) 6(16) through F(16) = spares53-54DiscreteMSD - 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 56 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT ByteFormatDescription 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-72Spare 7304(16)Fixed 7404(16)Fixed 7504(16)Fixed A sample of the station tracking data file is provided as a reference in Appendix B.2.2The TDRSS Tracking Data Format 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.4Accuracy and Completeness 4.2.1.3Stored Data Files (VC0 – VC3) 4.2.1.3.1Product Description 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 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). 4.2.1.3.2Support Duration 57 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.3Format One 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.4Accuracy and Completeness The Stored Data files will be complete and accurate as listed in the LRO Detailed Mission Requirements document (LRO-REQ-00048). 4.2.1.4Real-time VC0 – VC3 Telemetry Data 4.2.1.4.1Product Description This 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.2Support Duration The 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.3Format The 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.4.4Accuracy and Completeness 4.2.1.5SCN Station Status Packets 4.2.1.5.1Product Description 58 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration The 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.3Format The 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 quality Monitor uplink status and uplink lock (AGC data) Receiver strength Number of VCs Number of CADUs Number of Reed-Solomon errors decoded For the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field: Field nameField Characteristics Station Identifier4 ASCII Characters that uniquely identify the station Ka-Band RF Receiver Status TBD Data Command Time LatchYYYY DOY HHMMSS.MMM, where only applicable for stations YYYY => 4 ASCII digits of year (2008 – 2013) doing command uplinks to DOY => 3 ASCII digits for day of year (1 – 366) LRO; would be blank-filled if HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3no commanding; or default first 6 are the hours, minutes, and seconds of day timelast 3 are the milliseconds of day Downlink data qualityTBD AGC dataTBD Receiver strengthTBD 59 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Number of VCs1 ASCII Character, representing the number of downlinked virtual channels during this station contact; allowable values are 1, 2, 3, 4 Number of CADUs9 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 9 ASCII Characters, representing the total number of correctable R-S errors (this errors decodedfield 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 ratioTBR 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.5.4Accuracy and Completeness 4.2.1.6USN Station Status Packets 4.2.1.6.1Product Description 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.6.2Support Duration The 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.3Format The 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 quality Monitor uplink status and uplink lock (AGC data) 60 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Receiver strength Number of VCs Number of CADUs Number of Reed-Solomon errors decoded For the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field: Field nameField Characteristics Station Identifier4 ASCII Characters that uniquely identify the station Command Time LatchYYYY DOY HHMMSS.MMM, where only applicable for stations YYYY => 4 ASCII digits of year (2008 – 2013) doing command uplinks to DOY => 3 ASCII digits for day of year (1 – 366) LRO; would be blank-filled if HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3no commanding; or default first 6 are the hours, minutes, and seconds of day timelast 3 are the milliseconds of day Downlink data qualityTBD AGC dataTBD Receiver strengthTBD Number of VCs1 ASCII Character, representing the number of downlinked virtual channels during this station contact; allowable values are 1, 2, 3, 4 Number of CADUs9 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 9 ASCII Characters, representing the total number of correctable R-S errors (this errors decodedfield 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 ratioTBR 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.4Accuracy and Completeness 4.2.1.7SCN Weather Data 4.2.1.7.1Product Description 61 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration The 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.3Format The 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 nameField Characteristics First Line of File Date/Day of YearXx ASCII Characters with the following format: DATE: YYMMDD DOY: NNN; where: YYYYMMDD, defined as YYYY => 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 Identifier4 ASCII Characters that uniquely identify the station Repeating Lines (1:N) of File Time Reference (UTC => 4 ASCII characters with the following format: Formatted)HHMM; where HH => 2 ASCII digits for hours (01- 23) MM => 2 ASCII digits for minutes (00- 59) 62 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics temperature (in Degrees 5 ASCII characters; Celsius))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 6 ASCII characters; Mercury)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 humidity3 ASCII characters, which represent the relative humidity (0 – 100)The file name for the weather product is defined as: .wea A sample SCN Weather Data file is provided as a reference in Appendix B.2.6.4.2.1.7.4Accuracy and Completeness 4.2.1.8Ka-Band Measurement Data Files (VC3) 4.2.1.8.1Product Description This 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.2Support Duration The 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.3Format A sample Ka-Band Measurement data file is provided as a reference in Appendix B.2.7.4.2.1.8.4Accuracy and Completeness 4.2.1.9Ka-Band RF Receiver Data 4.2.1.9.1Product Description 63 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration The WS1 station generates this file for all mission phases. 4.2.1.9.3Format The 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 nameField Characteristics Time-Tag18 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 StrengthTBR A sample Ka-Band RF Receiver Data file is provided as a reference in Appendix B.2.8.4.2.1.9.4Accuracy and Completeness 4.2.1.10CFDP Status Messages 4.2.1.10.1Product Description This 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.2Support Duration The 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.3Format 64 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT The CFDP Status Messages contain the current status of the MUE located at the WS1 facility Possible CFDP status: Class 1 or 2 Total number of VCDUs received Breakout by each VC Packets sent by APID Total files sent/received successfully Total file transmission/reception failures Active files being transmitted/received Total number of NAKs sent For a limited number (last 5 or 10 or ?) files: file name (including path name) start time stop time progress (% complete) faults encountered (counts of each type) file size Error counts: file transfers suspended file transfers canceled file transfers abandoned file 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.10.4Accuracy and Completeness 4.2.1.11Weekly Laser Ranging Schedule 4.2.1.11.1Product Description This 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.2Support Duration This information is supplied for all mission phases. The LR site delivers this data file to the LRO MOC. 4.2.1.11.3Format 65 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT The Weekly Laser Ranging Schedule contains the following fields: Station Identifier Scheduled start time for laser ranging Scheduled stop time for laser ranging Point 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.4Accuracy and Completeness 4.2.1.11.5Timespan The 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.6Volume Estimate 4.2.1.11.7Delivery Schedule The 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.8Medium The 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.2Deep 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.1DSN Tracking Data 4.2.2.1.1Product Description The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration The 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.3Format This 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.114.2.2.1.4Accuracy and Completeness 4.2.2.1.5Timespan The DSN Tracking Data file will consist of the tracking data created over the last five minutes during a station contact. 4.2.2.1.6Volume Estimate TBR 4.2.2.1.7Delivery Schedule The DSN Tracking Data File is delivered at the completion of the five minute duration for each tracking file. 4.2.2.1.8Medium DSN will electronically deliver the DSN Tracking Data File via a TBR mechanism.4.2.2.2DSN Stored Data Files (VC0 – VC3) 4.2.2.2.1Product Description Nominally, 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.2Support Duration The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.2.2.2.3Format One 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.124.2.2.2.4Accuracy and Completeness The Stored Data files will be complete and accurate as listed in the LRO Detailed Mission Requirements document (LRO-RQMT-00048). 4.2.2.3Real-time VC0 – VC3 Telemetry Data 4.2.2.3.1Product Description This 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.2Support Duration The 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.3Format The 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.3.4Accuracy and Completeness 4.2.2.4DSN Station Status Packets 4.2.2.4.1Product Description This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.2.2.4.2Support Duration The 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.3Format The 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 quality Monitor uplink status and uplink lock (AGC data) Receiver strength Number of VCs Number of CADUs Number of Reed-Solomon errors decoded For the total station contact, the status information provides the symbol to noise ratio. The following table provides a brief description of each field: Field nameField Characteristics Station Identifier4 ASCII Characters that uniquely identify the station Command Time LatchYYYY DOY HHMMSS.MMM, where only applicable for stations YYYY => 4 ASCII digits of year (2008 – 2013) doing command uplinks to DOY => 3 ASCII digits for day of year (1 – 366) LRO; would be blank-filled if HHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3no commanding; or default first 6 are the hours, minutes, and seconds of day timelast 3 are the milliseconds of day Downlink data qualityTBD AGC dataTBD Receiver strengthTBD Number of VCs1 ASCII Character, representing the number of downlinked virtual channels during this station contact; allowable values are 1, 2, 3, 4 Number of CADUs9 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 69 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Field nameField Characteristics Number of Reed-Solomon 9 ASCII Characters, representing the total number of correctable R-S errors (this errors decodedfield 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 ratioTBR 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 DSN Station Status Packets is provided as a reference in Appendix B.2.14. 4.2.2.4.4Accuracy and Completeness TBR 4.3SCIENCE 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.1CRaTER SOC Products This section provides the lower-level information regarding the files sent from the CRaTER SOC to the LRO MOC. 4.3.1.1CRaTER Activity Request This is the Command/Procedure request for instrument 4.3.1.1.1Product Description The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration Support will be provided through all mission phases. 4.3.1.1.3Format The 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: -. 71 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT whereinstrument 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 sequence ATS for absolute time sequence PROC for procedure 4.3.1.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.1.2CRaTER Instrument Reset Timeline 4.3.1.2.1Product Description This 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.2Support Duration 4.3.1.2.3Format The 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 Field nameField Characteristics Timetag:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day A sample CRaTER Instrument Reset Timeline is provided in Appendix B, Figure B.3-2 72 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.1.2.4Accuracy and Completeness 4.3.2DLRE SOC Products This section provides the lower-level information regarding the files sent from the DLRE SOC to the LRO MOC. 4.3.2.1DLRE Command Request This is the Command/Procedure request for instrument 4.3.2.1.1Product Description The 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. 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.2.1.2Support Duration Support will be provided through all mission phases. 4.3.2.1.3Format The 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. 73 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 DLRE Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-3 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: -. whereinstrument id=[2 characters] DL for DLRE 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 sequence ATS for absolute time sequence PROC for procedure 4.3.2.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.2.2DLRE FSW Load 4.3.2.2.1Product Description This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.2.2.2Support Duration Support will be provided through all mission phases. 4.3.2.2.3Format The 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 NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: -. whereinstrument id=[2 characters] DL for DLRE 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update 75 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample DLRE Instrument FSW Load is provided in Appendix B, Figure B.3-4 4.3.2.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.3LAMP SOC Products This section provides the lower-level information regarding the files sent from the LAMP SOC to the LRO MOC. 4.3.3.1LAMP Command Request This is the Command/Procedure request for instrument. 4.3.3.1.1Product Description The 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. 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.3.1.2Support Duration Support will be provided through all mission phases. 4.3.3.1.3Format The 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 76 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.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. 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: -. whereinstrument id=[2 characters] LA for LAMP 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 sequence ATS for absolute time sequence PROC for procedure A sample LAMP Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-5. 4.3.3.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.3.2LAMP HV Command Sequence 4.3.3.2.1Product Description This file contains the command sequence(s) to either disable or enable the LAMP High Voltage.4.3.3.2.2Support Duration 4.3.3.2.3Format 77 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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: Field nameField Characteristics Timetag:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Command MnemonicLAMP HV Command Sub-MnemonicOn/Off A sample LAMP HV Command Sequence is provided in Appendix B, Figure B.3-6 4.3.3.2.4Accuracy and Completeness 4.3.3.3LAMP Instrument FSW Load 4.3.3.3.1Product Description This 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 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.2Support Duration Support will be provided through all mission phases. 4.3.3.3.3Format The 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.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: 78 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Parameter NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: -. whereinstrument id=[2 characters] LA for LAMP 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update A sample LAMP Instrument FSW Load is provided in Appendix B, Figure B.3-7 4.3.3.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.4LEND SOC Products This section provides the lower-level information regarding the files sent from the LEND SOC to the LRO MOC. 4.3.4.1LEND Command Request This is the Command/Procedure request for instrument. 4.3.4.1.1Product Description 79 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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. 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.4.1.2Support Duration Support will be provided through all mission phases. 4.3.4.1.3Format The 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. 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT whereinstrument id=[2 characters] LE for LEND 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 sequence ATS for absolute time sequence PROC for procedure A sample LEND Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-8. 4.3.4.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.4.2LEND Instrument FSW Load 4.3.4.2.1Product Description This 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 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.2Support Duration Support will be provided through all mission phases. 4.3.4.2.3Format The 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.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. 81 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT The second line is the mission information line, which consists of several comma-separated fields, as identified in the following table: Parameter NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: -. whereinstrument id=[2 characters] LE for LEND 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update A sample LEND Instrument FSW Load is provided in Appendix B, Figure B.3-9. 4.3.4.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.5LOLA SOC Products This section provides the lower-level information regarding the files sent from the LOLA SOC to the LRO MOC. 4.3.5.1LOLA Command Request This is the Command/Procedure request for instrument. 82 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.5.1.1Product Description The 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. 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.5.1.2Support Duration Support will be provided through all mission phases. 4.3.5.1.3Format The 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. 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: 83 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT -. whereinstrument id=[2 characters] LO for LOLA 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 sequence ATS for absolute time sequence PROC for procedure A sample LOLA Command Request (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-10. 4.3.5.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.5.2LOLA Gravity Model or Improved Lunar Gravity Model 4.3.5.2.1Product Description The 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.2Support Duration This 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.3Format A sample Improved Lunar Gravity Model data file is provided as a reference in Appendix B.3-11. 4.3.5.2.4Accuracy and Completeness 84 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.5.3LOLA Instrument FSW Load 4.3.5.3.1Product Description This 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 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.2Support Duration Support will be provided through all mission phases. 4.3.5.3.3Format 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. 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. 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 NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: -. 85 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT whereinstrument id=[2 characters] LO for LOLA 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update A sample LOLA Instrument FSW Load is provided in Appendix B, Figure B.3-12. 4.3.5.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.5.4LOLA Processed OD Information 4.3.5.4.1Product Description This 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.2Support Duration 4.3.5.4.3Format The 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: -. whereinstrument id=[2 characters] LO for LOLA file content=[4 characters] Intent of the instrument loads. These characters will be created by the corresponding SOC to identify file contents 86 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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: txt => for textual file information 4.3.5.4.4Accuracy and Completeness TBR 4.3.5.5LOLA Target Requests 4.3.5.5.1Product Description This 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.2Support Duration TBR 4.3.5.5.3Format The 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: Field nameField Characteristics Timetag:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Lunar Latitude (? – TBR)6 ASCII Characters representing the targeted Lunar Latitude; where first character is a positive/negative sign indicator (blank or -) Next 2 characters represent the whole value of latitude (-90 to 90) Next character is the decimal separator Next 2 characters represent the decimal portion for lunar latitude (0 – 999)Lunar Longitude (? – TBR))6 ASCII Characters representing the targeted Lunar Longitude; ; where first 3 character represent the whole decimal value of longitude (0 -360) Next character is the decimal separator Next 2 characters represent the decimal portion for lunar longitude (0 – 999) 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: 87 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT -. whereinstrument id=[2 characters] LO for LOLA 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 sequence ATS for absolute time sequence PROC for procedure A sample LOLA Target Requests File is provided in Appendix B, Figure B.3-14.4.3.5.5.4Accuracy and Completeness TBR 4.3.6LROC SOC Products This section provides the lower-level information regarding the files sent from the LROC SOC to the LRO MOC. 4.3.6.1LROC Instrument Initialization Command Sequence 4.3.6.1.1Product Description This 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. 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.6.1.2Support Duration Support will be provided through all mission phases. 88 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.6.1.3Format 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. 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: -. whereinstrument id=[2 characters] LR for LROC 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 sequence ATS for absolute time sequence PROC for procedure A sample LROC Instrument Initialization Command Sequence (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-15. 4.3.6.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available. 89 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.3.6.2LROC Daily Command Sequence 4.3.6.2.1Product Description This 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. 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. 4.3.6.2.2Support Duration Support will be provided through all mission phases. 4.3.6.2.3Format 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. 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: -. whereinstrument id=[2 characters] LR for LROC 90 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 sequence ATS for absolute time sequence PROC for procedure A sample LROC Daily Command Sequence (ATS, RTS, or STOL procedure) is provided in Appendix B, Figure B.3-16. 4.3.6.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.6.3LROC Instrument FSW Load 4.3.6.3.1Product Description This 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 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.2Support Duration Support will be provided through all mission phases. 4.3.6.3.3Format The 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.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: 91 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Parameter NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: -. whereinstrument id=[2 characters] LO for LOLA 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update A sample LROC Instrument FSW Load is provided in Appendix B, Figure B.3-17. 4.3.6.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.6.4LROC Target Request 4.3.6.4.1Product Description This is file that contains target request for LROC imaging; the MOC uses this information to develop the attitude slew plan. 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. 4.3.6.4.2Support Duration 92 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Support will be provided through all mission phases. 4.3.6.4.3Format The 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: Field nameField Characteristics Timetag:YYYY DOY HHMMSS.MMM, where yearYYYY => 4 ASCII digits of year (2008 – 2013) day of year and DOY => 3 ASCII digits for day of year (1 – 366) time of dayHHMMSS.mmm => 10 ASCII digits with a period between the first 6 and last 3 first 6 are the hours, minutes, and seconds of day last 3 are the milliseconds of day Off-nadir angle7 ASCII Characters representing the targeted off-nadir angle; where first 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 separator Next 3 characters represent the decimal portion for the angle (0 – 999)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: -. whereinstrument id=[2 characters] LR for LROC 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: txt => for textual files A sample LROC Target Request is provided in Appendix B, Figure B.3-18. 4.3.6.4.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.7Mini-RF SOC Products This section provides the lower-level information regarding the files sent from the Mini-RF SOC to the LRO MOC. 93 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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. 4.3.7.1Mini-RF Load Files 4.3.7.1.1Product Description This 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 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.2Support Duration Support will be provided through all mission phases. 4.3.7.1.3Format The 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 NameParameter value mission name This field is ignored by the ITOS LOAD directive. image IDThis field is ignored by the ITOS LOAD directive. DateCopied to the formatted image load file but otherwise ignored. VersionThis field is ignored by the ITOS LOAD directive. SourceThis field is ignored by the ITOS LOAD directive. packet sizeMaximum 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. 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: 94 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT -. whereinstrument id=[2 characters] RF for Mini-RF 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 a SOC; it will be named for the input file type: IFTU for Instrument FSW Table Update A sample Mini-RF Load File is provided in Appendix B, Figure B.3-19. 4.3.7.1.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.3.7.2Mini-RF Command Timeline 4.3.7.2.1Product Description This file contains a set of command sequences that the MOC uses to create a daily load for uplink to the Mini-RF instrument. 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. 4.3.7.2.2Support Duration Support will be provided through all mission phases. 4.3.7.2.3Format The Mini-RF Command Timeline consists of the complete set of commands used on-board the LRO spacecraft to manage the Mini-RF instrument. 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: -. whereinstrument id=[2 characters] RF for Mini-RF 95 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 a SOC; it will be named for the input file type: RTS for relative time sequence ATS for absolute time sequence PROC for procedure A sample Mini-RF Command Timeline is provided in Appendix B, Figure B.3-20. 4.3.7.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4LRO 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. Mini-RF4.4.1MOC PRODUCTS DISTRIBUTED TO SCIENCE CENTERS LROC This section provides the details related to the products that the LRO MOC transmits to each LOLAindividual 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 LENDwhich products a specific SOC receives. Further information is then provided within subsequent subsections.LAMP DivinerTable 4-2. MOC Products Transmitted to Various LRO SOC Facilities CRaTEROriginal Product Product Source Product DescriptionIDNameSection Reference MOC-1Beta Angle File containing the beta-angle FDF??????? Predictspredicts for the next 5 years. Data is Section 4.1.2.2 consistent with predicted ephemeris information, one predict every 2 hrs. MOC-3Clock File containing a daily log of MOC??????? Correlation spacecraft to ground correlation times 5.1.6.1.1 Filewith amount of adjustments 96 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Mini-RF LROC LOLA LENDInterface Control Document (ICD) for the LRO Ground System431-ICD-000049LAMPRevision - Dv 3.0 DRAFTDiviner CRaTEROriginal Product Product Source Product DescriptionIDNameSection ReferenceMOC-4CRaTER - File containing selected spacecraft s/c? Spacecraft telemetry parameters used by the 4.4.1.1.3 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-5CRaTER HK File containing stored housekeeping s/c? Data Filesdata from instrument4.4.1.1.4MOC-6CRaTER Raw measurement data files after s/c ? Raw CFDP processing4.4.1.1.5 Measurement Data Files MOC-7CRaTER Either selected APIDs or entire full s/c ? Real-time VC0 data stream4.4.1.1.6 VC0 HK data MOC-8Daily Text version of the daily command s/c ??????? Command loadB.4.6 Load MOC-9Definitive File containing 1 week of definitive FDF???? ?? LRO vectors with an interval of 60 4.1.2.3 Ephemeris seconds. Format is selenographic or FileMoon-Centered Mean J2000 MOC-10DLRE - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.2.5 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-11DLRE HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.2.6MOC-12DLRE Raw Raw measurement data files after s/c ? Measurement CFDP processing4.4.1.2.7 Data Files MOC-13DLRE Real-Either selected APIDs or entire full s/c ? time VC0 VC0 data stream4.4.1.2.8 HK data MOC-14Ground File for each pass that contains GN Station ? Network weather information (Temperature, 4.2.1.7 Weather DataPressure, and Rel. Hum) every 10 minutes during station contacts. 97 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Mini-RF LROC LOLA LENDInterface Control Document (ICD) for the LRO Ground System431-ICD-000049LAMPRevision - Dv 3.0 DRAFTDiviner CRaTEROriginal Product Product Source Product DescriptionIDNameSection ReferenceMOC-15LAMP - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.3.5 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-16LAMP HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.3.6MOC-17LAMP Raw Raw measurement data files after s/c ? Measurement CFDP processing4.4.1.3.7 Data Files MOC-18LAMP Real-Either selected APIDs or entire full s/c ? time VC0 VC0 data stream4.4.1.3.8 HK data MOC-19Laser Range File containing laser pulse transmit Ground ? Transmit times along with associated weather Network Informationinformation MOC-21LEND - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.4.5 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-22LEND HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.4.6MOC-23LEND Raw Raw measurement data files after s/c ? Measurement CFDP processing4.4.1.4.7 Data Files MOC-24LEND Real-Either selected APIDs or entire full s/c ? time VC0 VC0 data stream4.4.1.4.8 HK data MOC-25LOLA - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.5.5 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-26LOLA HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.5.6MOC-27LOLA Raw Raw measurement data files after s/c ? Measurement CFDP processing4.4.1.5.7 Data Files 98 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Mini-RF LROC LOLA LENDInterface Control Document (ICD) for the LRO Ground System431-ICD-000049LAMPRevision - Dv 3.0 DRAFTDiviner CRaTEROriginal Product Product Source Product DescriptionIDNameSection ReferenceMOC-28LRO SPICE SPICE files containing predict FDF??????? Files Predictsephemeris information for LROMOC-29LROC - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.6.7 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-30LROC HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.6.8MOC-31LROC Raw Raw measurement data files after s/c ? Measurement CFDP processing4.4.1.6.9 Data Files MOC-32Lunar Orbit File containing 1-week worth of FDF??????? Ascending & nodal crossing predicts.4.1.2.6 Descending Node Predicts MOC-33Lunar File containing 1-week worth of FDF???? ?? Terminator terminator predicts. Crossing Predicts MOC-34Mini-RF - File containing selected spacecraft s/c ? Spacecraft telemetry parameters used by the 4.4.1.7.9 HK Data Fileinstrument. Includes information such as attitude, spacecraft temperatures, etc MOC-35Mini-RF HK File containing stored housekeeping s/c ? Data Filesdata from instrument4.4.1.7.10MOC-36Mini-RF File containing potential operations s/c ? Operations opportunity for Mini-RF4.4.1.7.11 Opportunity MOC-37Mini-RF Raw measurement data files after s/c ? Raw CFDP processing4.4.1.7.12 Measurement Data Files MOC-38Mission File contains 90-days worth of FDF???? ?? Eclipse mission eclipse predicts; information 4.1.2.8 Predictsincludes entry/exit times for each period. File will also include lunar eclipse times 99 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Mini-RF LROC LOLA LENDInterface Control Document (ICD) for the LRO Ground System431-ICD-000049LAMPRevision - Dv 3.0 DRAFTDiviner CRaTEROriginal Product Product Source Product DescriptionIDNameSection Reference MOC-39Post-File will contain current estimate of FDF ? Maneuver spacecraft mass. Estimate will be 4.1.2.12 Spacecraft updated to reflect fuel usage after Masseach maneuver MOC-40Predicted File containing 30 days worth of FDF???? ?? LRO ephemeris predicts every 5 minutes. 4.1.2.14 Ephemeris Format of ephemeris is Moon- FileCentered Mean J2000 MOC-41Predicted File containing the Lat/Long position, FDF??????? Lunar altitude, ground track velocity every 4.1.2.15 Ground 60 seconds Track File MOC-42Raw Attitude File containing spacecraft telemetry s/c??????? Data Filepoints from gyro, star tracker, ACS B.4.30 processing regarding spacecraft attitude MOC-43Raw File containing the UTDF tracking Stations ? Tracking information from each GN support4.2.1.2 and Data Files4.2.2.1 MOC-47LRO SPICE SPICE files containing definitive FDF??????? Files ephemeris information for LRO Definitive MOC-Predicted File containing the Lat/Long position, FDF?xx50Definitive altitude, ground track velocity every 4.1.2.16 Lunar 60 seconds Ground Track File 4.4.1.1MOC PRODUCTS FOR CRaTER 4.4.1.1.1LRO Beta Angle Predicts The 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.2Clock Correlation File 4.4.1.1.2.1Product Description 100 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.1.2.2Support Duration Support will be provided through all mission phases. 4.4.1.1.2.3Format 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files A sample Clock Correlation File is provided in Appendix B, Figure B.4-1.4.4.1.1.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.3CRaTER - Spacecraft Housekeeping Data File 4.4.1.1.3.1Product 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.2Support Duration Support will be provided through all mission phases. 4.4.1.1.3.3Format 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample CRaTER - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-2. 4.4.1.1.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.3.5Timespan 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.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.1.3.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.1.3.8Medium 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: . whereFile Name=[9 Characters] CR_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.1.4CRaTER Housekeeping Data Files 4.4.1.1.4.1Product Description This file contains the stored CRaTER instrument telemetry data. 102 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.1.4.2Support Duration Support will be provided through all mission phases. 4.4.1.1.4.3Format 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.4.4.1.1.4.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.4.5Timespan 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.4.6Volume Estimate Each file size and volumes are TBR. 4.4.1.1.4.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.1.4.8Medium 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: . whereFile Name=[6 Characters] CR_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 103 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.1.5CRaTER Raw Measurement Data Files 4.4.1.1.5.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.1.5.2Support Duration Support will be provided through all mission phases. 4.4.1.1.5.3Format 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.4.4.1.1.5.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.5.5Timespan 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.5.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.1.5.7Delivery Schedule The LRO MOC will transfer this file to the corresponding CRaTER SOC at the completion of a downlinked pass. 4.4.1.1.5.8Medium 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: . whereFile Name=[6 Characters] CR_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 104 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 files 4.4.1.1.6CRaTER Real-time VC0 housekeeping data 4.4.1.1.6.1Product 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.2Support Duration Support will be provided through all mission phases. 4.4.1.1.6.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.6.5Timespan 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.6.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.1.6.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.1.6.8Medium 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.7Daily Command Load 4.4.1.1.7.1Product Description 105 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration Support will be provided through all mission phases. 4.4.1.1.7.3Format 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. 4.4.1.1.7.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.1.7.5Timespan 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. .4.4.1.1.7.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.1.7.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.1.7.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 106 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 files 4.4.1.1.8Definitive LRO Ephemeris File 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.1.9LRO SPICE Files Definitive The 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.10LRO SPICE Files Predicts The 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.11Lunar Orbit Ascending/Descending Node Predicts The 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.12Lunar Terminator Crossing Predicts The 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.13Mission Eclipse Predicts The 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.14Predicted LRO Ephemeris File 107 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.15Predicted Lunar Ground Track File The 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.16Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.2MOC PRODUCTS FOR DLRE 4.4.1.2.1Beta Angle Predicts The 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.2Clock Correlation File 4.4.1.2.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.2.2.2Support Duration Support will be provided through all mission phases. 4.4.1.2.2.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.2.5Timespan 108 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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. .4.4.1.2.2.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.2.2.7Delivery Schedule 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.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.2.3Daily Command Load 4.4.1.2.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.2.3.2Support Duration Support will be provided through all mission phases. 4.4.1.2.3.3Format 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.A sample Daily Command Load is provided in Appendix B, Figure B.4-6. 4.4.1.2.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.3.5Timespan 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. .4.4.1.2.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.2.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.2.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.2.4Definitive LRO Ephemeris File 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. 110 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.2.5DRLE - Spacecraft Housekeeping Data File 4.4.1.2.5.1Product 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.2.5.2Support Duration Support will be provided through all mission phases. 4.4.1.2.5.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.5.5Timespan 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.2.5.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.2.5.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.2.5.8Medium 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT whereFile Name=[9 Characters] DL_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.2.6DRLE Housekeeping Data Files 4.4.1.2.6.1Product Description This file contains the stored DRLE instrument telemetry data. 4.4.1.2.6.2Support Duration Support will be provided through all mission phases. 4.4.1.2.6.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.6.5Timespan 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.2.6.6Volume Estimate Each file size and volumes are TBR. 4.4.1.2.6.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.2.6.8Medium 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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: . whereFile Name=[6 Characters] DL_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.2.7DRLE Raw Measurement Data Files 4.4.1.2.7.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.2.7.2Support Duration Support will be provided through all mission phases. 4.4.1.2.7.3Format 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.4.4.1.2.7.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.7.5Timespan 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.2.7.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.2.7.7Delivery Schedule 113 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.8Medium 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: . whereFile Name=[6 Characters] DL_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.2.8DRLE Real-time VC0 housekeeping data 4.4.1.2.8.1Product 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.2Support Duration Support will be provided through all mission phases. 4.4.1.2.8.3Format 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.4.4.1.2.8.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.2.8.5Timespan 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. . 114 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.2.8.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.2.8.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.2.8.8Medium 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. 4.4.1.2.9LRO SPICE Files Definitive The 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.2.10LRO SPICE Files Predicts The 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.2.11Lunar Orbit Ascending/Descending Node Predicts The 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.2.12Lunar Terminator Crossing Predicts The 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.2.13Mission Eclipse Predicts The 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. 115 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.2.14Predicted LRO Ephemeris File 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.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.2.15Predicted Lunar Ground Track File The 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.2.16Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.3MOC PRODUCTS FOR LAMP 4.4.1.3.1Beta Angle Predicts The 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.3.2Clock Correlation File 4.4.1.3.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.3.2.2Support Duration Support will be provided through all mission phases. 4.4.1.3.2.3Format 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.3.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available. 116 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.3.2.5Timespan 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. .4.4.1.3.2.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.3.2.7Delivery Schedule 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.3.2.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.3.3Daily Command Load 4.4.1.3.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.3.3.2Support Duration Support will be provided through all mission phases. 4.4.1.3.3.3Format 117 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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. 4.4.1.3.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.3.3.5Timespan 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. .4.4.1.3.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.3.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.3.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.3.4Definitive LRO Ephemeris File 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 118 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.5LAMP - Spacecraft Housekeeping Data File 4.4.1.3.5.1Product 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.3.5.2Support Duration Support will be provided through all mission phases. 4.4.1.3.5.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.3.5.5Timespan 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.3.5.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.3.5.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.3.5.8Medium 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT character file extension name. There is a period (.) between the last two fields. The form of the filename is as follows: . whereFile Name=[9 Characters] LA_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.3.6LAMP Housekeeping Data Files 4.4.1.3.6.1Product Description This file contains the stored LAMP instrument telemetry data. 4.4.1.3.6.2Support Duration Support will be provided through all mission phases. 4.4.1.3.6.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.3.6.5Timespan 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.3.6.6Volume Estimate Each file size and volumes are TBR. 4.4.1.3.6.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.3.6.8Medium 120 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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: . whereFile Name=[6 Characters] LA_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.3.7LAMP Raw Measurement Data Files 4.4.1.3.7.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.3.7.2Support Duration Support will be provided through all mission phases. 4.4.1.3.7.3Format 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.4.4.1.3.7.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.3.7.5Timespan 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.3.7.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 121 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.3.7.7Delivery Schedule The LRO MOC will transfer this file to the corresponding LAMP SOC at the completion of a downlinked pass. 4.4.1.3.7.8Medium 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: . whereFile Name=[6 Characters] LA_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.3.8LAMP Real-time VC0 housekeeping data 4.4.1.3.8.1Product 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.2Support Duration Support will be provided through all mission phases. 4.4.1.3.8.3Format 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.4.4.1.3.8.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.3.8.5Timespan 122 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.3.8.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.3.8.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.3.8.8Medium 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.9LRO SPICE Files Definitive The 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.3.10LRO SPICE Files Predicts The 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.3.11Lunar Orbit Ascending/Descending Node Predicts The 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.3.12Lunar Terminator Crossing Predicts The 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.3.13Mission Eclipse Predicts The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.3.14Predicted LRO Ephemeris File 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.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.15Predicted Lunar Ground Track File The 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.3.16Definitive Lunar Ground Track File The 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.3.17Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.4MOC PRODUCTS FOR LEND 4.4.1.4.1Beta Angle Predicts The 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.4.2Clock Correlation File 4.4.1.4.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.4.2.2Support Duration Support will be provided through all mission phases. 124 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.4.2.3Format 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.4.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.2.5Timespan 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. .4.4.1.4.2.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.4.2.7Delivery Schedule 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.4.2.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.4.3Daily Command Load 125 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.4.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.4.3.2Support Duration Support will be provided through all mission phases. 4.4.1.4.3.3Format 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. 4.4.1.4.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.3.5Timespan 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. .4.4.1.4.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.4.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.4.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 126 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 files 4.4.1.4.4Definitive LRO Ephemeris File 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.4.5LEND - Spacecraft Housekeeping Data File 4.4.1.4.5.1Product 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.4.5.2Support Duration Support will be provided through all mission phases. 4.4.1.4.5.3Format 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.4.4.1.4.5.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.5.5Timespan 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.4.5.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.4.5.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 127 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.4.5.8Medium 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: . whereFile Name=[6 Characters] LE_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.4.6LEND Housekeeping Data Files 4.4.1.4.6.1Product Description This file contains the stored LEND instrument telemetry data. 4.4.1.4.6.2Support Duration Support will be provided through all mission phases. 4.4.1.4.6.3Format 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.4.4.1.4.6.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.6.5Timespan 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.4.6.6Volume Estimate Each file size and volumes are TBR. 128 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.4.6.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.4.6.8Medium 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: . whereFile Name=[6 Characters] LE_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.4.7LEND Raw Measurement Data Files 4.4.1.4.7.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.4.7.2Support Duration Support will be provided through all mission phases. 4.4.1.4.7.3Format 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.4.4.1.4.7.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.7.5Timespan 129 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.4.7.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.4.7.7Delivery Schedule The LRO MOC will transfer this file to the corresponding LEND SOC at the completion of a downlinked pass. 4.4.1.4.7.8Medium 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: . whereFile Name=[6 Characters] LE_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.4.8LEND Real-time VC0 housekeeping data 4.4.1.4.8.1Product 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.2Support Duration Support will be provided through all mission phases. 4.4.1.4.8.3Format 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample LEND Real-time VC0 housekeeping data is provided in Appendix B, Figure B.4-18.4.4.1.4.8.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.4.8.5Timespan 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.4.8.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.4.8.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.4.8.8Medium 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.9LRO SPICE Files Definitive The 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.4.10LRO SPICE Files Predicts The 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.4.11Lunar Orbit Ascending/Descending Node Predicts The 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.4.12Lunar Terminator Crossing Predicts The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.4.13Mission Eclipse Predicts The 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.4.14Predicted LRO Ephemeris File 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.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.4.15Predicted Lunar Ground Track File The 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.4.16Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.5MOC PRODUCTS FOR LOLA 4.4.1.5.1Beta Angle Predicts The 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.5.2Clock Correlation File 4.4.1.5.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.5.2.2Support Duration Support will be provided through all mission phases. 132 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.5.2.3Format 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.5.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.5.2.5Timespan 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. .4.4.1.5.2.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.5.2.7Delivery Schedule 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.5.2.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.5.3Daily Command Load 133 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.5.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.5.3.2Support Duration Support will be provided through all mission phases. 4.4.1.5.3.3Format 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. 4.4.1.5.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.5.3.5Timespan 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. .4.4.1.5.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.5.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.5.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 134 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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 files 4.4.1.5.4SCN Weather Data The 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.5LOLA - Spacecraft Housekeeping Data File 4.4.1.5.5.1Product 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.5.5.2Support Duration Support will be provided through all mission phases. 4.4.1.5.5.3Format 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.4.4.1.5.5.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.5.5.5Timespan 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.5.5.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.5.5.7Delivery Schedule 135 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.5.5.8Medium 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: . whereFile Name=[9 Characters] LO_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.5.6LOLA Housekeeping Data Files 4.4.1.5.6.1Product Description This file contains the stored LOLA instrument telemetry data. 4.4.1.5.6.2Support Duration Support will be provided through all mission phases. 4.4.1.5.6.3Format 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.4.4.1.5.6.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.5.6.5Timespan 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. . 136 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.5.6.6Volume Estimate Each file size and volumes are TBR. 4.4.1.5.6.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.5.6.8Medium 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: . whereFile Name=[6 Characters] LO_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.5.7LOLA Raw Measurement Data Files 4.4.1.5.7.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.5.7.2Support Duration Support will be provided through all mission phases. 4.4.1.5.7.3Format 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.4.4.1.5.7.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available. 137 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.5.7.5Timespan 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.5.7.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.5.7.7Delivery Schedule The LRO MOC will transfer this file to the corresponding LOLA SOC at the completion of a downlinked pass. 4.4.1.5.7.8Medium 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: . whereFile Name=[6 Characters] LO_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.5.8LRO SPICE Files Definitive The 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.5.9LRO SPICE Files Predicts The 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. 138 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.5.10Lunar Orbit Ascending/Descending Node Predicts The 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.5.11Predicted Lunar Ground Track File The 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.5.12Lunar Terminator Crossing Predicts The 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.5.13Mission Eclipse Predicts The 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.5.14Post-Maneuver Spacecraft Mass The 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.15Predicted LRO Ephemeris File 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.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.16Predicted Lunar Ground Track File The 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.17Raw Attitude Data File 139 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.5.18Raw Tracking Data Files The 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.6MOC PRODUCTS FOR LROC 4.4.1.6.1Beta Angle Predicts The 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.6.2Clock Correlation File 4.4.1.6.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.6.2.2Support Duration Support will be provided through all mission phases. 4.4.1.6.2.3Format 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.6.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.6.2.5Timespan 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. .4.4.1.6.2.6Volume Estimate 140 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.6.2.7Delivery Schedule 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.6.2.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.6.3Daily Command Load 4.4.1.6.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.6.3.2Support Duration Support will be provided through all mission phases. 4.4.1.6.3.3Format 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. 141 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.6.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.6.3.5Timespan 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. .4.4.1.6.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.6.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.6.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.6.4Definitive LRO Ephemeris File 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.6.5LRO SPICE Files Definitive The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.6.6LRO SPICE Files Predicts The 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.6.7LROC - Spacecraft Housekeeping Data File 4.4.1.6.7.1Product 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.6.7.2Support Duration Support will be provided through all mission phases. 4.4.1.6.7.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.6.7.5Timespan 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.6.7.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.6.7.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.6.7.8Medium 143 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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: . whereFile Name=[9 Characters] LR_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.6.8LROC Housekeeping Data Files 4.4.1.6.8.1Product Description This file contains the stored LROC instrument telemetry data. 4.4.1.6.8.2Support Duration Support will be provided through all mission phases. 4.4.1.6.8.3Format 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.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.6.8.5Timespan 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.6.8.6Volume Estimate Each file size and volumes are TBR. 4.4.1.6.8.7Delivery Schedule 144 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.6.8.8Medium 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: . whereFile Name=[6 Characters] LR_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.6.9LROC Raw Measurement Data Files 4.4.1.6.9.1Product Description This file contains the raw measurement data files after CFDP processing.4.4.1.6.9.2Support Duration Support will be provided through all mission phases. 4.4.1.6.9.3Format 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.4.4.1.6.9.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.6.9.5Timespan 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. . 145 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.6.9.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.6.9.7Delivery Schedule The LRO MOC will transfer this file to the corresponding LROC SOC at the completion of a downlinked pass. 4.4.1.6.9.8Medium 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: . whereFile Name=[6 Characters] LR_INS version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.6.10Lunar Orbit Ascending/Descending Node Predicts The 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.6.11Lunar Terminator Crossing Predicts The 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.6.12Mission Eclipse Predicts The 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 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.6.13Predicted LRO Ephemeris File 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.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.6.14Predicted Lunar Ground Track File The 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.6.15Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.1.7MOC PRODUCTS FOR Mini-RF 4.4.1.7.1Beta Angle Predicts The 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.7.2Clock Correlation File 4.4.1.7.2.1Product Description This file contains the daily log of spacecraft to ground correlation times with amount of adjustments. 4.4.1.7.2.2Support Duration Support will be provided through all mission phases. 4.4.1.7.2.3Format 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. 147 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.7.2.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.7.2.5Timespan 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. .4.4.1.7.2.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.7.2.7Delivery Schedule 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.7.2.8Medium 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: . whereFile Name=[6 Characters] ClkCor version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.7.3Daily Command Load 4.4.1.7.3.1Product Description This file contains the textual version of the daily uplinked command load, which the LRO MOC sent to the LRO spacecraft. 4.4.1.7.3.2Support Duration Support will be provided through all mission phases. 148 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.7.3.3Format 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. 4.4.1.7.3.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.7.3.5Timespan 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. .4.4.1.7.3.6Volume Estimate Each file is variable based upon the kinds and types of instrument command requests that the individual SOC create. 4.4.1.7.3.7Delivery Schedule The LRO MOC delivers this Daily Command Load to each LRO SOC on a daily basis.4.4.1.7.3.8Medium 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: . whereFile Name=[6 Characters] LROCMD version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.7.4Definitive LRO Ephemeris File 149 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.5LRO SPICE Files Definitive The 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.7.6LRO SPICE Files Predicts The 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.7.7Lunar Orbit Ascending/Descending Node Predicts The 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.7.8Lunar Terminator Crossing Predicts The 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.7.9Mini-RF - Spacecraft Housekeeping Data File 4.4.1.7.9.1Product 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.7.9.2Support Duration Support will be provided through all mission phases. 4.4.1.7.9.3Format 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample Mini-RF - Spacecraft Housekeeping Data File is provided in Appendix B, Figure B.4-25. 4.4.1.7.9.4Accuracy and Completeness Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.7.9.5Timespan 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.7.9.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 4.4.1.7.9.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 4.4.1.7.9.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 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: . whereFile Name=[9 Characters] RF_LROTLM version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.7.10Mini-RF Housekeeping Data Files 4.4.1.7.10.1Product Description This file contains the stored Mini-RF instrument telemetry data. 151 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.7.10.2Support Duration Support will be provided through all mission phases. 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 Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.7.10.5Timespan 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.7.10.6Volume Estimate Each file size and volumes are TBR. 4.4.1.7.10.7Delivery Schedule The LRO MOC will transfer this file to the corresponding SOC at the completion of a downlinked pass. 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: . whereFile Name=[6 Characters] RF_HKP version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 152 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.1.7.11Mini-RF Operations Opportunity 4.4.1.7.12Mini-RF Raw Measurement Data Files 4.4.1.7.12.1Product Description This file contains the raw measurement data files after CFDP processing. 4.4.1.7.12.2Support Duration Support will be provided through all mission phases. 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 Required accuracy is 100-percent fidelity of received data, which is best available.4.4.1.7.12.5Timespan 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.7.12.6Volume Estimate Each file is variable based upon the kinds and types of Spacecraft telemetry that the individual SOC requested. 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: . whereFile Name=[6 Characters] RF_INS 153 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT version number=[2 characters] Two-digit version number. The initial version is 00, next is 01 … up to 99. 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 files 4.4.1.7.13Mission Eclipse Predicts The 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.7.14Predicted LRO Ephemeris File 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.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.7.15Predicted Lunar Ground Track File The 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.7.16Raw Attitude Data File 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 5.1.6.1.1 provides a representation of the sample product. 4.4.2MOC PRODUCTS DISTRIBUTED TO PLANETARY DATA SYSTEM SPICE Files and Ephemeris Data and maybe improved Lunar Gravity Model 4.4.3MOC PRODUCTS TO STATIONS 4.4.3.1SCN Realtime Orbiter Commands (SCN and USN) 4.4.3.1.1Product Description This 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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.4.3.1.2Support Duration This support will be provided through all mission phases. 4.4.3.1.3Format The 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.2SCN Orbiter Commands – CFDP Structure 4.4.3.2.1Product Description This 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.2Support Duration This support will be provided through all mission phases. 4.4.3.2.3Format The 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.3DSN Realtime Orbiter Commands 4.4.3.3.1Product Description This 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.2Support Duration This support will be provided through all mission phases. 4.4.3.3.3Format The 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.4DSN Orbiter Commands – CFDP Structure 4.4.3.4.1Product Description 155 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 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.2Support Duration This support will be provided through all mission phases. 4.4.3.4.3Format The 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.5CFDP Control Messages (WS1 Interface Only) 4.4.3.5.1Product Description This 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.2Support Duration This support will be provided through all mission phases. 4.4.3.5.3Format The 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.6SCN Support Schedules (Laser Ranging Interface Only) 4.4.3.6.1Product Description This 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.2Support Duration This support will be provided through all mission phases. 4.4.3.6.3Format The SCN Support Schedule follows the same format representation as identified in Section 4.2.1.1.3. 156 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT A sample SCN Station Schedule File is provided in Appendix B, Figure B.2.1. 4.5LAUNCH 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 ICD Section Product Matrix Comments DescriptionReferenceCross Reference Telemetry from Launch Section 4.5.1.1KSC-1Pre-launch testing support Site Telemetry to KSCSection 4.5.2.1MOC-49Post-launch support Commands to KSCSection 4.5.2.2MOC-48Pre-launch testing support Launch Vehicle Post Section 4.5.1.2LV-1Post-launch support Separation Vector 4.5.1Launch Site Product Interface with the LRO MOC This section describes the interface between KSC support facilities and the LRO MOC.4.5.1.1Telemetry from Launch Site 4.5.1.1.1Product Description This 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.2Support Duration The 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.3Format A sample telemetry file is provided as a reference in Appendix B.5-1. 4.5.1.1.4Accuracy and Completeness 157 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.5.1.1.5Timespan 4.5.1.2Launch Vehicle Post Separation Vector 4.5.1.2.1Product Description This 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.2Support Duration 4.5.1.2.3Format The 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.1.2.4Accuracy and Completeness 4.5.2LRO 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.1Telemetry to KSC 4.5.2.1.1Product Description The 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.2Support Duration 4.5.2.1.3Format A sample of telemetry data is provided as a reference in Appendix B.5-3. 4.5.2.1.4Accuracy and Completeness 158 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 4.5.2.2Commands to KSC 4.5.2.2.1Product Description This 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.2Support Duration This 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.3Format A sample command load file is provided as a reference in Appendix B.5-4. 4.5.2.2.4Accuracy and Completeness 4.5.2.2.5Timespan 4.5.2.2.6Delivery Schedule The 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.7Medium The commands are delivered electronically using the specified IONet. 159 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT5.0LRO MOC INTERNAL INTERFACES This section provides the specific information for the interfaces that exist for the various MOC system components. . 5.1.1Integrated Test and Operations System Interfaces 5.1.1.1ITOS to MPS Products 5.1.1.1.1Product Description Postpass Operations Summary 5.1.1.2ITOS to Anomaly Notification Response and Reporting Products 5.1.1.2.1Product Description Realtime or Postpass Logs Spacecraft and System Event Messages 5.1.1.3ITOS to Data Processing and Distribution Products5.1.1.3.1Product Description Archived Telemetry Files Command Load Files 5.1.1.4ITOS to FlatSat Products 5.1.1.4.1Product Description Simulated Telemetry Simulated Commands Simulated CFDP Commands 5.1.2Mission Planning System Interfaces 5.1.2.1MPS to ITOS Products 5.1.2.1.1Product Description Pass Scripts 5.1.2.2MPS to DP&DS Products 5.1.2.2.1Product Description Command Loads 5.1.2.3MPS to Anomaly Notification Response and Reporting Interface 5.1.2.3.1Product Description 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT Logs and System Event Messages 5.1.2.4MPS to Flight Operations Team Interface 5.1.2.4.1Product Description Viewable Activity Maps Model Analysis Reports 5.1.3MOC-FD Interfaces 5.1.3.1MOC-FD to MPS Products 5.1.3.1.1Product Description Gyro Calibration Data – Report that includes updated parameters for gyro calibration tableSA Calibration Data – Report that includes updated parameters for SA calibration tableStar 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.2MOC-FD to FOT Products 5.1.3.2.1Product Description Gyro Calibration Data – Report that includes updated parameters for gyro calibration tableSA Calibration Data – Report that includes updated parameters for SA calibration tableStar 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.3MOC-FD to DP&DS Products 5.1.3.3.1Product Description 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" 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFTSensor Calibration Report Files 5.1.3.4MOC-FD to Anomaly Products 5.1.3.4.1Product Description MOC FD System Events – Data File that identifies anomalous system events within the FD- MOC element 5.1.4Trending Interfaces 5.1.4.1Trending to Data Processing and Distribution Products5.1.4.1.1Product Description Trended Products – various types of graphs, plots based on telemetry points, time and other user- defined criteria 5.1.4.2MPS to Anomaly Notification Response and Reporting Products 5.1.4.2.1Product Description Logs and System Event Messages 5.1.4.3MPS to FOT Products 5.1.4.3.1Product Description Activity Report Request Viewable Activity Map 5.1.5Data Processing and Distribution Interfaces 5.1.5.1DP&DS to MOC-FD Products 5.1.5.1.1Product Description Selected attitude telemetry mnemonics Selected ancillary telemetry Mnemonics 5.1.5.2DP&DS to Trending Products 5.1.5.2.1Product Description Telemetry data (Raw and File versions) 3 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT5.1.5.3DP&DS to ITOS Products 5.1.5.3.1Product Description Command Loads (CFDP Commands, s/c command files)5.1.5.4Data Processing and Distribution to Notification Response and Reporting Interface Products 5.1.5.4.1Product Description Logs and System Event Messages 5.1.6Monitoring and Anomaly System Interfaces 5.1.6.1Monitoring and Anomaly System to FOT Products5.1.6.1.1Product Description System Error Page Notifications User Notification/Response Report Request and Generated Report 4 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 3.0 DRAFT 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.AAppendix – Abbreviations and AcronymsAbbreviation/ AcronymDEFINITION Acq.Acquisition ACSAttitude Control System ADAttitude Determination AETDApplied Engineering and Technology DirectorateAOSAdvanced Orbiting Systems Acquisition of Signal APIDApplication Identification application process identifierAPLApplied Physics Laboratory ASCIIAmerican Standard Code for Information InterchangeASEairborne support equipment ATSAbsolute Time Sequence ATSabsolute time sequence AUIattachment unit interface Bpsbytes per second C&DHCommand & Data Handling CCBConfiguration Control Board CCLClosed-Circuit Loop CCRconfiguration change request CCSDSConsultative Committee for Space Data SystemsCCTVClosed-Circuit Television CFDPCCSDS File Delivery Protocol CLCWCommand Link Control Word CLTUcommand link transmission unit CMConfiguration Management CMDCommand CMOConfiguration Management Office CNECenter Network Environment COPCommand Operating Procedures COTScommercial off the shelf CRaTERCosmic Ray Telescope for Effects of RadiationCRCCyclic Redundancy Check DARPADefense Advanced Research Projects AgencyDCNDocument Change Notice DDDDSN Data Delivery DMRDetailed Mission Requirements DPSData Processing System 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTAbbreviation/ AcronymDEFINITION DSNDeep Space Network DTASData Trending and Analysis SystemEIRPEffective Isotropic Radiated PowerEELVEvolved Expendable Launch VehicleEOMEnd of Mission FCSFront-End Communications SystemFDFlight Dynamics FDABFlight Dynamics Analysis BranchFDFFlight Dynamics Facility FDSSFlight Dynamics Support SystemFDSSFlight Dynamics Support SystemFEPfront-end processor FMEAFailure Mode and Effect AnalysisFOPFlight Operations Plan FOTFlight Operations Team FSWFlight Software FSMFFlight Software Maintenance FacilityFSWM Flight Software Maintenance FTPFile Transfer Protocol GMTGreenwich Mean Time GN&CGuidance Navigation and ControlGOTSGovernment off the shelf GSGround System GSEGround Support Equipment GSFCGoddard Space Flight Center HGAHigh Gain Antenna I&TIntegration and Test ICDInterface Control Document IDIdentification IEEEInstitute of Electrical and Electronics Engineers IGSEinstrument ground support equipmentIIRVimproved interrange vector IONetIP Operational Network IPInternet Protocol IPTXIP Transition Network IRIGInter Range Instrumentation GroupISDNIntegrated Services Digital NetworkISOInternational Organization for Standardization ITOSIntegrated Test and Operations System 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTAbbreviation/ AcronymDEFINITION JPLJet Propulsion Laboratory kbpskilobits per second kmkilometer KSCKennedy Space Center L&EOLaunch and Early Orbit LAMPLyman-Alpha Mapping ProjectLANlocal area network LENDLunar Exploration Neutron DetectorLOILunar Orbit Insertion LOLALunar Orbiter Laser AltimeterLOSloss of signal LROLunar Reconnaissance OrbiterLROCLunar Reconnaissance Orbiter CameraLSBleast significant bit MAmultiple access Mbmegabits MBmegabytes MCMission Critical MCCMid Course Correction MCOMission Concept of OperationsMCSmaster channel sequence MMFDMulti-Mission Flight DynamicsMO&DSDMission Operations and Data Systems Directorate MOCMission Operations Center MPSMission Planning System MPSMission Planning System MRDMission Requirements DocumentMSBmost significant bit NACNarrow Angle Camera NAKnegative acknowledgement NASANational Aeronautics and Space Administration NascomNASA Communications NISNNASA Integrated Services NetworkNMCNetwork Management Center NPDNASA Policy Directive OBConboard computer ODOrbit Determination OSPFOpen Shortest Path First PBplayback 3 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTAbbreviation/ AcronymDEFINITION PDBproject database PDSPlanetary Data System PDUpacket data unit PIprincipal investigator POCCPayload Operations Control Centerpskphase shift key PTPprogrammable telemetry processorRFRadio Frequency RGSRemote Ground Stations RLEPRobotic Lunar Exploration ProgramRSReed-Solomon RTMCReal-Time Mission Critical RTSRelative Time Sequence S/CSpacecraft SASolar Array SBCSingle Board Computer SCIDspacecraft identifier SCNSpace Communications Network SCPStored Command Processor SCSSequence and Compression SystemSDVFSoftware Development and Validation FacilitySERSSpacecraft Emergency Response SystemSIPStandard IP (replaces NI) SKStation-Keeping SOCScience Operations Center SSRSolid State Recorder STGTSecond Tracking and Data Relay Satellite (TDRS) Ground Terminal STOLSystems Test and Operations LanguageT&CTelemetry, & Command TBDTo Be Determined TBRTo Be Resolved TBSTo Be Supplied TCTelecommand TCPTransmission Control ProtocolTCWTest Conductor Workstation TLMTelemetry TT&CTracking, Telemetry, & CommandUDPUser Datagram Protocol URLUniform Resource Locator 4 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTAbbreviation/ AcronymDEFINITION USNUniversal Space Network UTCuniversal time code UTDFuniversal tracking data format VCVirtual Channel VCDUVirtual Channel Data Unit VCIDvirtual channel identifier VDSVoice Data System VMOCVirtual Mission Operations CenterWACWide Angle Camera WANwide area network WSworkstation WSCWhite Sands Complex WSGTWhite Sands Ground Terminal 5 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.BAppendix B – Sample Product Formats Each 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. 1.B.1Sample FDF Products 1.B.1.1SCN Acquisition Data Sample Figure B.1-1 Sample SCN Acquisition Data File 1 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.2DSN Acquisition Data Sample Figure B.1-2 Sample DSN Acquisition Data File 2 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.1.3LR Prediction Data Sample BytesDescriptionExample 1-7ILRS Satellite Identification Number - 7 digit number based on COSPAR ID, See Explanation'7603901'8-9Year of Century - 2 digits with leading zero fill'09'10-12Day of Year - 3 digits with leading blank fill' 34'13-24Time of Day - from midnight GMT with a .1 microsecond granularity and' leading blank fill36005000000'25-28Crustal Dynamics Project Pad ID- a 4-digit monument identification'7105'29-30Crustal Dynamics Project 2-digit system number'07'31-32Crustal Dynamics Project 2-digit occupancy sequence number'24'33-39Azimuth - the geometric or true azimuth angle with a .1 millidegree' 987500' granularity and leading blank fill 40-45Elevation - the geometric or true elevation angle with a .1 millidegree'292500' granularity and leading blank fill 46-57Laser Range - in units of two way time with a 1 picosecond' granularity and leading blank fill 52035998000'58-64Pass RMS from the mean of raw range values minus the trend function, for accepted ranges (two-way ' 66' value in picoseconds). 65-68Wavelength of the laser with leading blank fill'5321' The user of the data should interpret the value given as follows: 3000 - 9999: units are 0.1 nanometer 1000 - 2999: units are 1.0 nanometer For the station generating the data, the rule is: Wavelength in rate 0.3000 - 0.9999 microns: unit 0.1 nanometer Wavelength in rate 1.000 - 2.999 microns: unit 1.0 nanometer69-73Surface Pressure - .1 millibar granularity with leading blank fill '10135'74-77Surface Temperature - .1 degree Kelvin granularity with leading'2905' blank fill 78-80Relative Humidity at Surface - percentage with leading blank fill ' 55'81-85Tropospheric refraction correction - a round trip refraction'33956' correction with a 1 picosecond granularity and leading blank fill 86-91Center of Mass Correction - a round trip correction with a' 1601' 1 picosecond granularity and leading blank fill 92-96Receive Amplitude - a positive linear scale value with leading blank fill ' 700' 97-104Applied System Delay - the two way system delay applied in the' 95942' current record with a 1 picosecond granularity and leading blank fill 105-Calibration Delay Shift - a measure of two way calibration stability' 33'110with a 1 picosecond granularity and leading blank fill. 3 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT111-Root Mean Square (RMS) of raw system delay values from the mean. Two-way value in ' 40'114picoseconds. If pre- and post- pass calibrations are made, use the mean of the two RMS values, or the RMS of the combined data set. 115Normal Point Window Indicator - indicates whether or not the'0' record represents a normal point and the time span of the normal point 0: not a normal point 1: 5-second normal point (GFZ-1) 2: LLR normal point 3: 15-second normal point (TOPEX) 4: 20-second normal point 5: 30-second normal point 6: 1-minute normal point 7: 2-minute normal point (LAGEOS) 8: 3-minute normal point 9: 5-minute normal point (ETALON) 116-Number of raw ranges compressed into normal point leading blank fill ' ' 119 120Epoch Event - indicates the time event reference.'1' Currently, only 1 and 2 are used for laser ranging data. 0 = Ground receive time 1 = Satellite transmit time (standard for LAGEOS) 2 = Ground transmit time 3 = Satellite receive time 121Epoch Time Scale - indicates the time scale reference.'3' Other flags may appear for historical data. 3 = UTC (USNO) 4 = UTC (GPS) 7 = UTC (BIH) 122Angle Origin Indicator - source of angle values.'3' 0 = Unknown (converted from MERIT I) 1 = Computed (from range) 2 = Command (predicts and operator inputs) 3 = Measured (calibrated instrument readings) 123Tropospheric Refraction Correction Indicator'0' 0 = Data has been corrected using the Marini-Murray formula 1 = Data has not been corrected 124Center of Mass Correction Application Indicator'0' 0 = Applied 1 = Not applied 125Receive Amplitude Correction Indicator'1' 0 = Data has been receive amplitude corrected 1 = Data has not been receive amplitude corrected 4 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 126System calibration method and delay shift indicator. Indicates the type of calibration and the type of '0' calibration shift given in columns 105-110 Pre- to Post-PassMinimum to Maximum Calibration ShiftCalibration Shift External cal05 Internal cal16 Burst cal27 Some other cal38 Not used49 127System Change indicator (SCH). A flag to increment for every major change to the system (hardware '0' 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. 128System Configuration Indicator (SCI). A flag used to indicate alternative modes of operation for a '1' 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). 129Format Revision Number Indicator - indicates the version'3' of the MERIT II format for the current record. Data prior to MERIT II that is converted into the MERIT II format will have a revision number of '0'. 130Release Flag Indicator - indicates when this record first'A' appeared on a release tape. Cooperating stations which send release tapes to the CDDIS will use a numbering scheme beginning with '1'. Release tapes from the CDDIS will 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 will have a release flag of '0'. 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. 5 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 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) 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 seconds b) divide the result in a) by 2 c) multiply the result in b) by the speed of light, (299792458 m/s) Figure B.1-3 Sample Laser Ranging Prediction Data File 6 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.4Ground Station View Period Predicts Data Sample Figure B.1-4 Sample Ground Station View Period Predicts Data File 7 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.5LRO Beta Angle Predict File Sample Figure B.1-5 Sample LRO Beta Angle Predict File 8 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.6LRO Definitive Ephemeris File Sample Figure B.1-6 Sample LRO Definitive Ephemeris File 9 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.7LRO Definitive SPICE File Sample Figure B.1-7 Sample LRO Definitive SPICE File 10 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.8LRO Predictive SPICE File Sample Figure B.1-8 Sample LRO Predictive SPICE File 11 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.9Lunar Orbit Ascending and Descending Node Predicts SampleFigure B.1-9 Sample Lunar Orbit Ascending and Descending Node Predicts File 12 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.10Lunar Orbit Terminator Crossing Predicts Sample Figure B.1-10 Sample Lunar Orbit Terminator Crossing Predicts Data File 13 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.11Mission Eclipse Predicts Data Sample Figure B.1-11 Sample Mission Eclipse Predicts Data File 14 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.12Lunar Ephemeris Data Sample Figure B.1-12 Sample Lunar Ephemeris Data File 15 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.13Orbiter Thruster Maneuver Plans Data Sample Figure B.1-13 Sample Orbiter Thruster Maneuver Plans Data File 16 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.14Orbiter to Earth Range Predict Data Sample Figure B.1-14 Sample Orbiter to Earth Range Predict Data File 17 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.15Post Orbiter Maneuver Report Data Sample Figure B.1-15 Sample Post Orbiter Maneuver Report Data File 18 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.16Post Separation Report Data Sample Figure B.1-16 Sample Post Separation Report Data File 19 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.17Predicted LRO Ephemeris File Sample Figure B.1-17 Sample Predicted LRO Ephemeris File 20 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.18Predicted Lunar Ground Track File Sample Figure B.1-18 Sample Predicted Lunar Ground Track File 21 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.19Definitive Lunar Ground Track File Sample Figure B.1-19 Sample Definitive Lunar Ground Track File 22 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.20Attitude Determination Verification Report Sample Figure B.1-20 Sample Attitude Determination Verification Report File 23 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.21Attitude Slew Plan Sample Figure B.1-21 Sample Attitude Slew Plan File 24 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.22Gyro Calibration Data Sample Figure B.1-22 Sample Gyro Calibration Data File 25 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.23HGA Calibration Data Sample Figure B.1-23 Sample HGA Calibration Data File 26 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.24 LRO State Vector Table Sample Figure B.1-24 Sample LRO State Vector Table Data File 27 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.25Star Tracker Calibration Data Sample Figure B.1-25 Sample Star Tracker Calibration Data File 28 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.26Thruster Calibration Data Sample Figure B.1-26 Sample Thruster Calibration Data File 29 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.27LRO Momentum Management Unload Plan Sample Figure B.1-27 Sample LRO Momentum Management Unload Plan File 30 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.1.28Star Tracker Occultation Report Sample Figure B.1-28 Sample LRO Star Tracker Occultation Report File 31 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2Space Communications Data Products 1.B.2.1Station Support Schedules Sample Figure B.2-1 Sample Station Support Schedules File 32 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.2Station Tracking Data Sample ByteFormatDescription 10D(16)Fixed 20A(16)Fixed 301(16)Fixed 4-5ASCIITracking Data Router 4141=AA=GSFC 4444=DD=GSFC 6BinaryLast two digits of current year 7-8BinarySatellite Identification Code (SIC)9-10BinaryVehicle Identification (VID) 11-14BinarySeconds of year 15-18BinaryMicroseconds of second Note: For bytes 19-22/23-36, convert angle data to decimal form. Angle data is given in fractions of a -8circle. To express raw angle in degrees, multiply decimal angle by 8.381903173 x 10 (360 degrees divided by 232) 19-22FOCAngle 1: X or az 23-26FOCAngle 2; Y or el (angle 2 byte/bit format is the same as for bytes 19-22.) 27-32BinaryRTLT in 1/256 nsec (MSB = 524288 ns; LSB = 0.00390625 ns) 33-38BinaryBias Doppler, counts of: 240 MHz +1000 fd1 LSB - 1 count 39-40BinaryAGC (an integer * (-150/8192) AGC-50=dBm)41-44BinaryTransmit frequency information in 10's of Hz 33 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTByteFormatDescription 45DiscreteMSD = 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) = spares46BinaryPad ID (xmit) 47DiscreteAntenna size (rcv) (see byte 45) 48BinaryPad ID (rcv) 34 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT ByteFormatDescription 49-50DiscreteMode-system unique (refer to Table 2) 51DiscreteData 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)52DiscreteMSD = 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 1(16) = spare 35 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFTByteFormatDescription 2(16) = simulated 3(16) = resubmit 4(16) = RT (real time) 5(16) = PB (playback) 6(16) through F(16) = spares 53-54DiscreteMSD - 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-72Spare 7304(16)Fixed 7404(16)Fixed 7504(16)Fixed Figure B.2-2 Sample Station Tracking Data File 36 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.3Stored Data Files (VC0 – VC3) Sample Figure B.2-3 Sample Stored Data Files (VC0 – VC3) 37 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.4Real-time VC0 – VC3Telemetry Data Sample Figure B.2-4 Sample Real-time VC0 – VC3 Telemetry Data File 38 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.5SCN Station Status Packets Sample Figure B.2-5 Sample SCN Station Status Packets 39 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.2.6SCN Weather Data Sample Figure B.2-6 Sample SCN Weather Data File 40 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.7Ka-Band Measurement Data Files (VC3) Sample Figure B.2-7 Sample Ka-Band Measurement Data Files (VC3) 41 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.8Ka-Band RF Receiver Data File Sample Figure B.2-8 Sample Ka-Band RF Receiver Data File 42 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.2.9CFDP Status Messages Sample Figure B.2-9 Sample CFDP Status Messages 43 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.10Weekly Laser Ranging Schedule Sample Figure B.2-10 Sample Weekly Laser Ranging Schedule File 44 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.11DSN Tracking Data File Sample Figure B.2-11 Sample DSN Tracking Data File 45 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.2.12DSN Stored Data File Sample Figure B.2-12 Sample DSN Stored Data File 46 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.13DSN Realtime VC Data Stream Sample Figure B.2-13 Sample DSN Realtime VC Data Stream 47 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.2.14DSN Station Status Packets Sample Figure B.2-14 Sample DSN Station Status Packets 48 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3Science Operations Center Products 1.B.3.1CRaTER Command Request Sample Figure B.3-1 Sample CRaTER Command Request File 49 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.2CRaTER Instrument Reset Timeline Sample Figure B.3-2 CRaTER Instrument Reset Timeline 50 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.3DLRE Command Request Sample Figure B.3-3 Sample DLRE Command Request File 51 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.4DLRE FSW Load Sample Table Load DLRE,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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.5LAMP Command Request Sample Figure B.3-5 Sample LAMP Command Request File 53 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.6LAMP HV Command Sequence Sample Figure B.3-6 Sample LAMP HV Command Sequence 54 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.7LAMP Instrument FSW Load Sample Table Load LAMP,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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.8LEND Command Request Sample Figure B.3-8 Sample LEND Command Request File 56 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.9LEND Instrument FSW Load Sample Table Load LEND,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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.10LOLA Command Request Sample Figure B.3-10 Sample LOLA Command Request File 58 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.11LOLA Gravity Model Sample Figure B.3-11 Sample LOLA Gravity Model 59 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.12LOLA Instrument FSW Load Sample Table Load LOLA,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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.13LOLA Processed OD Information Sample Figure B.3-13 Sample LOLA Processed OD Information 61 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.14LOLA Target Requests Sample Figure B.3-14 Sample LOLA Target Requests File 62 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.15LROC Instrument Initialization Command Sequence Sample Figure B.3-15 Sample LROC Instrument Initialization Command Sequence File 63 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.16LROC Daily Command Sequence Sample Figure B.3-16 LROC Daily Command Sequence File 64 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.17LROC Instrument FSW Load Sample Table Load LROC,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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.18 LROC Target Requests Figure B.3-18 Sample LROC Target Requests File 66 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT1.B.3.19Mini-RF Load Files Table Load Mini-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 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.3.20Mini-RF Command Timeline Files Figure B.3-20 Sample Mini-RF Command Timeline File 68 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4Mission Operations Center Products 1.B.4.1Clock Correlation File Sample Figure B.4-1 Sample Clock Correlation File 69 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.2CRaTER – Spacecraft Housekeeping Data File Sample Figure B.4-2 Sample CRaTER – Spacecraft Housekeeping Data File 70 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.3CRaTER Housekeeping Data File Sample Figure B.4-3 Sample CRaTER Housekeeping Data File 71 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.4CRaTER Raw Measurement Data Files Sample Figure B.4-4 CRaTER Raw Measurement Data Files 72 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.5CRaTER Realtime VC0 Housekeeping Data Sample Figure B.4-5 Sample CRaTER Realtime VC0 Housekeeping Data 73 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.6Daily Command Load Sample Figure B.4-6 Sample Daily Command Load File 74 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.7DLRE – Spacecraft Housekeeping Data File Sample Figure B.4-7 Sample DLRE – Spacecraft Housekeeping Data File 75 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.8DLRE Housekeeping Data Files Sample Figure B.4-8 Sample DLRE Housekeeping Data Files 76 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.9DLRE Raw Measurement Data File Sample Figure B.4-9 Sample DLRE Raw Measurement Data File 77 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.10DLRE Real-time VC0 Housekeeping Data Sample Figure B.4-10 Sample DLRE Real-time VC0 Housekeeping Data 78 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.11LAMP – Spacecraft Housekeeping Data File Sample Figure B.4-11 Sample LAMP – Spacecraft Housekeeping Data File 79 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.12LAMP Housekeeping Data Files Sample Figure B.4-12 Sample LAMP Housekeeping Data Files 80 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.13LAMP Raw Measurement Data Files Sample Figure B.4-13 Sample LAMP Raw Measurement Data Files 81 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.14LAMP Real-time VC0 Housekeeping Data Sample Figure B.4-14 Sample LAMP Real-time VC0 Housekeeping Data 82 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.15LEND – Spacecraft Housekeeping Data Files Sample Figure B.4-15 Sample LEND – Spacecraft Housekeeping Data Files 83 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.16LEND Housekeeping Data Files Sample Figure B.4-16 Sample LEND Housekeeping Data Files 84 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.17LEND Raw Measurement Data Files Sample Figure B.4-17 Sample LEND Raw Measurement Data Files 85 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.18LEND Real-time VC0 Housekeeping Data Sample Figure B.4-18 Sample LEND Real-time VC0 Housekeeping Data 86 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.19LOLA – Spacecraft Housekeeping Data Files Sample Figure B.4-19 Sample LOLA – Spacecraft Housekeeping Data Files 87 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.20LOLA Housekeeping Data Files Sample Figure B.4-20 Sample LOLA Housekeeping Data Files 88 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.21LOLA Raw Measurement Data Files Sample Figure B.4-21 Sample LOLA Raw Measurement Data Files 89 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.22LROC – Spacecraft Housekeeping Data Files Sample Figure B.4-22 Sample LROC – Spacecraft Housekeeping Data Files 90 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.23LROC Housekeeping Data Files Sample Figure B.4-23 Sample LROC Housekeeping Data Files 91 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.24LROC Raw Measurement Data Files Sample Figure B.4-24 Sample LROC Raw Measurement Data Files 92 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.25Mini-RF – Spacecraft Housekeeping Data Files Sample Figure B.4-25 Sample Mini-RF – Spacecraft Housekeeping Data Files 93 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.26Mini-RF Housekeeping Data Files Sample Figure B.4-26 Sample Mini-RF Housekeeping Data Files 94 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.27Mini-RF Operations Opportunity Sample Figure B.4-27 Sample Mini- Operations Opportunity File 95 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.28Mini-RF Raw Measurement Data Files Sample Figure B.4-28 Sample Mini-RF Raw Measurement Data Files 96 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.29Post Maneuver Spacecraft Mass Sample Figure B.4-29 Post Maneuver Spacecraft Mass File 97 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.30Raw Attitude Data File Sample Figure B.4-30 Sample Raw Attitude Data File 98 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.31SCN Realtime Orbiter Commands Sample Figure B.4-31 Sample SCN Realtime Orbiter Commands 99 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.32SCN Realtime Orbiter Commands – CFDP Sample Figure B.4-32 Sample SCN Realtime Orbiter Commands – CFDP 100 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.33DSN Realtime Orbiter Commands Sample Figure B.4-33 Sample DSN Realtime Orbiter Commands 101 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.4.34DSN Realtime Orbiter Commands – CFDP Sample Figure B.4-33 Sample DSN Realtime Orbiter Commands – CFDP 102 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.5Sample Launch Site Products 1.B.5.1Realtime Telemetry to KSC Sample Figure B.5-1 Sample SCN Acquisition Data File 103 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. Interface Control Document (ICD) for the LRO Ground System431-ICD-000049 Revision - Dv 2.5 DRAFT 1.B.5.2Launch Vehicle Post Separation Vector Sample Figure B.5-2 Sample Launch Vehicle Post Separation Vector File 104 CHECK WITH RLEP DATABASE AT: TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.