Elements of Mission Control Software for a Commercial Lunar Landing and Surface Exploration Mission
- Paper number
IAC-18,B6,1,3,x42636
- Author
Ms. Chakshu Gupta, India, Team Indus, Axiom Research Labs Pvt. Ltd.
- Coauthor
Mr. Kritesh Semwal, India, Team Indus, Axiom Research Labs Pvt. Ltd.
- Coauthor
Mrs. Mohini Parameswaran, India, Team Indus, Axiom Research Labs Pvt. Ltd.
- Coauthor
Mr. Vijay Vujjini, India, Team Indus, Axiom Research Labs Pvt. Ltd.
- Coauthor
Mr. Mathew DeNeen, United States, Laboratory for Atmospheric and Space Physics (LASP) at University of Colorado
- Year
2018
- Abstract
Mission Control Software (MCS) for a mission consists of real-time heath monitoring through telemetry (TM), controlling the spacecraft through telecommands (TC), payload data reception and dissemination, and archival and retrieval of all data. Laboratory for Atmospheric and Space Physics (LASP) is providing TeamIndus with OASIS-CC, a CCSDS-compliant real-time health monitoring and commanding software and the interface for communicating with deep space network stations (DSN) over the Space Link Extension (SLE). The software modules involving archival and retrieval of telemetry, time correlation and processing of payload data are all developed by TeamIndus. The MCS described above, with elements built by LASP and TeamIndus, is being used for mission simulations, instrument and ground checkout and real-time mission operations. To achieve the objectives of the MCS, the telemetry and telecommand definitions form the basis of communication between on-board software and ground processing of spacecraft data. This has been achieved by automation of TM and TC schematics across sub systems, viz. on-board software, MCS and payload processing software. This paper describes in detail the following aspects of TeamIndus’s MCS: \begin{itemize} \item Handling of TM/TC definitions as stipulated by OASIS-CC tables. \item Integration of near real time processing with OASIS-CC. \item Real-time displays of telemetry parameters (Alphanumeric and graphical) as per spacecraft subsystems’ requirements. \item Time correlation for time-stamping of telemetry data and time tagged commands. \item Payload data processing and dissemination as per payload users’ requirement. \end{itemize}
- Abstract document
- Manuscript document
(absent)