Developing a cross-project support system during mission operations: Deep Space 1 extended mission flight control
Explore the source record for details and available documents.
SEARCH · Engineering Papers
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Explore the source record for details and available documents.
For many years the diverse scientific community that supports JPL's wide variety ofinterplanetary space missions has needed a tool in order to plan and develop their experiments. The tool needs to be easily adapted to various mission types and portable to the user community. The Science Opportunity Analyzer, SOA, now in its third year of development, is intended to meet this need. SOA is a java-based application that is designed to enable scientists to identify and analyze opportunities for science observations from spacecraft. It differs from other planning tools in that it does not require an in-depth knowledge of the spacecraft command system or operation modes to begin high level planning. Users can, however, develop increasingly detailed levels of design. SOA consists of six major functions: Opportunity Search, Visualization, Observation Design, Constraint Checking, Data Output and Communications. Opportunity Search is a GUI driven interface to existing search engines that can be used to identify times when a spacecraft is in a specific geometrical relationship with other bodies in the solar system. This function can be used for advanced mission planning as well as for making last minute adjustments to mission sequences in response to trajectory modifications. Visualization is a key aspect of SOA. The user can view observation opportunities in either a 3D representation or as a 2D map projection. The user is given extensive flexibility to customize what is displayed in the view. Observation Design allows the user to orient the spacecraft and visualize the projection of the instrument field of view for that orientation using the same views as Opportunity Search. Constraint Checking is provided to validate various geometrical and physical aspects of an observation design. The user has the ability to easily create custom rules or to use official project-generated flight rules. This capability may also allow scientists to easily impact the cost to science if flight rule changes occur. Data Output generates information based on the spacecraft's trajectory, opportunity search results or based on a created observation. The data can be viewed either in tabular format or as a graph. Finally, SOA is unique in that it is designed to be able to communicate with a variety of existing planning and sequencing tools. From the very beginning SOA was designed with the user in mind. Extensive surveys of the potential user community were conducted in order to develop the software requirements. Throughout the development period, close ties have been maintained with the science community to insure that the tool maintains its user focus. Although development is still in its early stages, SOA is already developing a user community on the Cassini project, which is depending on this tool for their science planning. There are other tools at JPL that do various pieces of what SOA can do; however, there is no other tool which combines all these functions and presents them to the user in such a convenient, cohesive, and easy to use fashion.
Explore the source record for details and available documents.
The daily preparation of uplink products (commands and files) for Deep Impact was as problematic as the final encounter images were spectacular. The operations team was faced with many challenges during the six-month mission to comet Tempel One of the biggest difficulties was that the Deep Impact Flyby and Impactor vehicles necessitated a high volume of uplink products while also utilizing a new uplink file transfer capability. The Jet Propulsion Laboratory (JPL) Multi-Mission Ground Systems and Services (MGSS) Mission Planning and Sequence Team (MPST) had the responsibility of preparing the uplink products for use on the two spacecraft. These responsibilities included processing nearly 15,000 flight products, modeling the states of the spacecraft during all activities for subsystem review, and ensuring that the proper commands and files were uplinked to the spacecraft. To guarantee this transpired and the health and safety of the two spacecraft were not jeopardized several new ground scripts and procedures were developed while the Deep Impact Flyby and Impactor spacecraft were en route to their encounter with Tempel-1. These scripts underwent several adaptations throughout the entire mission up until three days before the separation of the Flyby and Impactor vehicles. The problems presented by Deep Impact's daily operations and the development of scripts and procedures to ease those challenges resulted in several valuable lessons learned. These lessons are now being integrated into the design of current and future MGSS missions at JPL.
Safe human exploration in space missions requires careful management of limited resources such as breathable air and stored electrical energy. Daily activities for astronauts must be carefully planned with respect to such resources, and usage must be monitored as activities proceed to ensure that they can be completed while maintaining safe resource margins. Such planning and monitoring can be complex because they depend on models of resource usage, the activities being planned, and uncertainties. This paper describes a system - and the technology behind it - for energy management of the NASA-Johnson Space Center's Multi-Mission Space Exploration Vehicles (SEV), that provides, in an onboard advisory mode, situational awareness to astronauts and real-time guidance to mission operators. This new capability was evaluated during this year's Desert RATS (Research and Technology Studies) planetary exploration analog test in Arizona. This software aided ground operators and crew members in modifying the day s activities based on the real-time execution of the plan and on energy data received from the rovers.
The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.
HEFT was a NASA-wide team that performed analyses of architectures for human exploration beyond LEO, evaluating technical, programmatic, and budgetary issues to support decisions at the highest level of the agency in HSF planning. HEFT Phase I (April - September, 2010) and Phase II (September - December, 2010) examined a broad set of Human Exploration of Near Earth Objects (NEOs) Design Reference Missions (DRMs), evaluating such factors as elements, performance, technologies, schedule, and cost. At end of HEFT Phase 1, an architecture concept known as DRM 4a represented the best available option for a full capability NEO mission. Within DRM4a, the habitation system was provided by Deep Space Habitat (DSH), Multi-Mission Space Exploration Vehicle (MMSEV), and Crew Transfer Vehicle (CTV) pressurized elements. HEFT Phase 2 extended DRM4a, resulting in DRM4b. Scrubbed element-level functionality assumptions and mission Concepts of Operations. Habitation Team developed more detailed concepts of the DSH and the DSH/MMSEV/CTV Conops, including functionality and accommodations, mass & volume estimates, technology requirements, and DDT&E costs. DRM 5 represented an effort to reduce cost by scaling back on technologies and eliminating the need for the development of an MMSEV.
Multi-Mission Power Analysis Tool (MMPAT) Version 2 simulates spacecraft power generation, use, and storage in order to support spacecraft design, mission planning, and spacecraft operations. It can simulate all major aspects of a spacecraft power subsystem. It is parametrically driven to reduce or eliminate the need for a programmer. A user-friendly GUI (graphical user interface) makes it easy to use. Multiple deployments allow use on the desktop, in batch mode, or as a callable library. It includes detailed models of solar arrays, radioisotope thermoelectric generators, nickel-hydrogen and lithium-ion batteries, and various load types. There is built-in flexibility through user-designed state models and table-driven parameters.
This white paper documents a roadmap for development of Environmental Control and Life Support (ECLS) Systems (ECLSS) capabilities required to enable beyond-Low Earth Orbit (LEO) Exploration missions. In many cases, the execution of this Exploration-based roadmap will directly benefit International Space Station (ISS) operational capability by resolving known issues and/or improving overall system reliability. In addition, many of the resulting products will be applicable across multiple Exploration elements such as Multi-Purpose Crew Vehicle (MPCV), Multi-Mission Space Exploration Vehicle (MMSEV), Deep Space Habitat (DSH), and Landers. Within the ECLS community, this white paper will be a unifying tool that will improve coordination of resources, common hardware, and technologies. It will help to align efforts to focus on the highest priority needs that will produce life support systems for future human exploration missions that will simply run in the background, requiring minimal crew interaction.
The Multi-Mission Power Analysis Tool (MMPAT) simulates a spacecraft power subsystem including the power source (solar array and/or radioisotope thermoelectric generator), bus-voltage control, secondary battery (lithium-ion or nickel-hydrogen), thermostatic heaters, and power-consuming equipment. It handles multiple mission types including heliocentric orbiters, planetary orbiters, and surface operations. Being parametrically driven along with its user-programmable features can reduce or even eliminate any need for software modifications when configuring it for a particular spacecraft. It provides multiple levels of fidelity, thereby fulfilling the vast majority of a project s power simulation needs throughout the lifecycle. It can operate in a stand-alone mode with a graphical user interface, in batch mode, or as a library linked with other tools. This software can simulate all major aspects of a spacecraft power subsystem. It is parametrically driven to reduce or eliminate the need for a programmer. Added flexibility is provided through user-designed state models and table-driven parameters. MMPAT is designed to be used by a variety of users, such as power subsystem engineers for sizing power subsystem components; mission planners for adjusting mission scenarios using power profiles generated by the model; system engineers for performing system- level trade studies using the results of the model during the early design phases of a spacecraft; and operations personnel for high-fidelity modeling of the essential power aspect of the planning picture.
Scalable Integrated Multi-Mission Support System (SIMSS) Simulator Release 2.0 software is designed to perform a variety of test activities related to spacecraft simulations and ground segment checks. This innovation uses the existing SIMSS framework, which interfaces with the GMSEC (Goddard Mission Services Evolution Center) Application Programming Interface (API) Version 3.0 message middleware, and allows SIMSS to accept GMSEC standard messages via the GMSEC message bus service. SIMSS is a distributed, component-based, plug-and-play client-server system that is useful for performing real-time monitoring and communications testing. SIMSS runs on one or more workstations, and is designed to be user-configurable, or to use predefined configurations for routine operations. SIMSS consists of more than 100 modules that can be configured to create, receive, process, and/or transmit data. The SIMSS/GMSEC innovation is intended to provide missions with a low-cost solution for implementing their ground systems, as well as to significantly reduce a mission s integration time and risk.
Militarized versions of commercial platforms are growing in popularity due to many logistical benefits in the form of commercial off-the-shelf (COTS) parts, established production methods, and commonality for different certifications. Commercial data and best practices are often leveraged to reduce procurement and engineering development costs. While the developmental and cost reduction benefits are clear, these militarized aircraft are routinely operated in flight at significantly different conditions and in significantly different manners than for routine commercial flight. Therefore they are at a higher risk of flight envelope exceedance. This risk may lead to departure from controlled flight and/or aircraft loss1. Historically, the risk of departure from controlled flight for military aircraft has been mitigated by piloted simulation training and engineering analysis of typical aircraft response. High-agility military aircraft simulation databases are typically developed to include high angles of attack (AoA) and sideslip due to the dynamic nature of their missions and have been developed for many tactical configurations over the previous decades. These aircraft simulations allow for a more thorough understanding of the vehicle flight dynamics characteristics at high AoA and sideslip. In recent years, government sponsored research on transport airplane aerodynamic characteristics at high angles of attack has produced a growing understanding of stall/post-stall behavior. This research along with recent commercial airline training initiatives has resulted in improved understanding of simulator-based training requirements and simulator model fidelity.2-5 In addition, inflight training research over the past decade has produced a database of pilot performance and recurrency metrics6. Innovative solutions to aerodynamically model large commercial aircraft for upset conditions such as high AoA, high sideslip, and ballistic damage, as well as capability to accurately account for scaling factors, is necessary to develop realistic engineering and training simulations. Such simulations should significantly reduce the risk of departure from controlled flight, loss of aircraft, and ease the airworthiness certification process. The characteristics of commercial derivative aircraft are exemplified by the P-8A Multi-mission Maritime Aircraft (MMA) aircraft, and the largest benefits of initial investigation are likely to be yielded from this platform. The database produced would also be utilized by flight dynamics engineers as a means to further develop and investigate vehicle flight characteristics as mission tactics evolve through the years ahead. This paper will describe ongoing efforts by the U.S. Navy to develop a methodology for simulation and training for large commercial-derived transport aircraft at unusual attitudes, typically experienced during an aircraft upset. This methodology will be applied to a representative Navy aircraft (P-8A) and utilized to develop a robust simulation that should accurately represent aircraft response in these extremes. Simulation capabilities would then extend to flight dynamics analysis and simulation, as well as potential training applications. Recent evaluations of integrated academic, ground-based simulation, and in-flight upset training will be described along with important lessons learned, specific to military requirements.
In May 1983 the European Space Agency launched EXOSAT, its first X-ray astronomy observatory. Even though it lasted only 3 short years, this mission brought not only new capabilities that resulted in unexpected discoveries, but also a pioneering approach to operations and archiving that changed X-ray astronomy from observations led by small instrument teams, to an observatory approach open to the entire community through a guest observer program. The community use of the observatory was supported by a small dedicated team of scientists, the precursor to the data center activities created to support e.g. Chandra and XMM-Newton. The new science capabilities of EX OS AT included a 90 hr highly eccentric high earth orbit that allow unprecedented continuous coverage of sources as well as direct communication with the satellite that allowed real time decisions to respond to unexpected events through targets of opportunity. The advantages of this orbit demonstrated by EXOSAT resulted in Chandra and XMM-Newton selecting similar orbits. The three instruments on board the EXOSAT observatory were complementary, designed to give complete coverage over a wide energy band pass of 0.05-50 keY. An onboard processor could be programmed to give multiple data modes that could be optimized in response to science discoveries: These new capabilities resulted in many new discoveries including the first comprehensive study of AGN variability, new orbital periods in X-ray binaries and cataclysmic variables, new black holes, quasi-periodic oscillations from neutron stars and black holes and broad band X-ray spectroscopy. The EXOSAT team generated a well-organized database accessible worldwide over the nascent internet, allowing remote selection of data products, making samples and undertaking surveys from the data. The HEASARC was established by NASA at Goddard Space Flight Center in 1990 as the repository of NASA X-ray and Gamma-ray data. The proven EXOSAT database system became the core of the HEASARC infrastructure. The HEASARC pioneered many concepts now taken for granted including standardized formats using FITS files, restoring data from earlier missions, multi-mission analysis tools and a searchable archive over the world wide web.
The Mars Science Laboratory (MSL) spacecraft carrying the Curiosity rover launched from Cape Canaveral Air Force Station (CCAFS) on November 26, 2011. Following an 8.5-month cruise and after a successful Entry, Descent and Landing (EDL) phase, the Curiosity rover arrived at the surface of Mars on August 6, 2012 UTC. At the core of the Curiosity rover power subsystem is the F1 Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) supplied by the Department of Energy. Integration of the F1 MMRTG into the MSL spacecraft has provided the first opportunity to architect a power subsystem that also included a Solar Array (during the cruise phase of the mission and up to the initial stage of the EDL phase) and secondary Li-ion batteries for operation during the planned one Martian year surface phase of the mission. This paper describes the F1 MMRTG functional features as an enabler of the MSL mission and as a novel component of the MSL power subsystem architecture.
The Mission data Processing and Control Subsystem (MPCS) is being developed as a multi-mission Ground Data System with the Mars Science Laboratory (MSL) as the first fully supported mission. MPCS is a fully featured, Java-based Ground Data System (GDS) for telecommand and telemetry processing based on Configuration-Driven Development (CDD). The eXtensible Markup Language (XML) is the ideal language for CDD because it is easily readable and editable by all levels of users and is also backed by a World Wide Web Consortium (W3C) standard and numerous powerful processing tools that make it uniquely flexible. The CDD approach adopted by MPCS minimizes changes to compiled code by using XML to create a series of configuration files that provide both coarse and fine grained control over all aspects of GDS operation.
The MSL Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) was fueled on October 28, 2008 by the Department Of Energy (DOE) in preparation for a late 2009 launch. Shortly after, the MSL launch was delayed approximately 2 years until 2011. The fueled MMRTG was placed in storage to await the new date for liftoff. Occasional measurements of the MMRTG's power output were taken and compared with power predictions that pre-dated fueling. An error in the predictive models was quickly recognized and remedied. The resultant predictions, while improved, carried significant uncertainty. This uncertainty did not deter the launch of MSL, but did alter the planned mission on the surface of Mars. Once launched, the MSL spacecraft provided a hi-fidelity telemetry stream measuring the generator's electrical and thermal performance. These data were used to update the predictive models and a new prediction of the performance of the MMRTG on the surface of Mars was run just before Entry, Descent, and Landing (EDL) at Mars. The MSL MMRTG is working extremely well, providing power above predictions and operating within its flight allowable temperature limits. The generator was producing approximately 114 W at the beginning of the surface mission. This paper will elaborate on power modeling for the MSL MMRTG along with a review of some of the data recorded from the MSL cruise to Mars, EDL, and the early days of the surface mission.
The Cassini Spacecraft and its ground system have been operational for over 16 years. Modernization presents several challenges due to the personnel, processes, and tools already invested and embedded into the current ground system structure. Every mission's ground system has its own unique complexities and challenges, involving various organizational units. As any mission from its inception to its execution, schedules are always tight. This forces GDS engineers to implement a working ground system that is not necessarily fully optimized. Ground system challenges increase as technology evolves and cyber threats become more sophisticated. Cassini's main challenges were due to its ground system existing before many security requirements were levied on the multi-mission tools and networks. This caused a domino effect on Cassini GDS tools that relied on outdated technological features. In the aerospace industry reliable and established technology is preferred over innovative yet less proven technology. Loss of data for a spacecraft mission can be catastrophic; therefore, there is a reluctance to make changes and updates to the ground system. Nevertheless, all missions and associated teams face the need to modernize their processes and tools. Systems development methods from well-known system analysis and design principles can be applied to many missions' ground systems. Modernization should always be considered, but should be done in such a way that it does not affect flexibility nor interfere with established practices. Cassini has accomplished a secure and efficient ground data system through periodic updates. The obstacles faced while performing the modernization of the Cassini ground system will be outlined, as well as the advantages and challenges that were encountered.
The majority of today's CubeSat fleet consists of Earth-orbiting missions that mostly use existing ground systems developed by universities because of availability, simplicity, and low-cost. The Interplanetary NanoSpacecraft Pathfinder In Relevant Environment (INSPIRE) mission is a revolutionary CubeSat mission that will launch a pair of CubeSats into deep space to study the feasibility of CubeSats beyond low-Earth orbit. This uncovers a new set of systems and software engineering challenges to the development of a robust and reliable ground system in a low-cost environment. In this paper, we discuss the approach to these challenges by using the Jet Propulsion Laboratory's (JPL) Advanced Multimission Operation System (AMMOS) Ground Data System (GDS) as well as the methodologies used to engineer the flight system to work with an existing ground system developed for large-scale missions. Specifically we will focus on the command and telemetry subsystem of AMMOS, the Multimission Data Processing and Control System. We conclude with a retrospective on the challenges encountered and a brief discussion on our efforts to provide AMMOS to support future deep space CubeSat missions.