SEARCH · Search NASA
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.
The Microrover Flight Experiment (MFEX) is a NSAS OACT (Office of Advanced Concepts and Technology) flight experiment which, integrated with the Mars Pathfinder (MPF) lander and spacecraft system, landed on Mars on July 4, 1997.
The military spacecraft power subsystem design requirements, developments goals, and planned technology efforts are summarized. The mission drivers of performance (weight and volume), hardening (survivability), autonomy, reliability, and miniaturization influence space mission effectiveness are outlined. The anticipated performance versus power level trends for reactor static conversion systems are illustrated. A conceptual design for a space based radar system is also given.
The spacecraft design and operations and mission results of the Voyager Project are reviewed with particular emphasis on the results of the Saturn encounters. The mission was undertaken by two spacecraft: Voyager 2, launched first on August 20, 1977 on a lower energy trajectory to Jupiter, Saturn, Uranus and Neptune; and Voyager 1, launched on September 5, 1977 on a higher energy trajectory to closer flybys of Jupiter and Saturn. The Voyager spacecraft make use of earlier Mariner and Viking Orbiter design concepts, with additional capabilities for solar independent power, long-range communications and autonomy as well as equipment for the 11 science investigations. The Voyager operations system consists of a ground data system, missions operations system, and support by the Mission Control and Computer Center and Deep Space Network. Among the results of the Jupiter encounter are data concerning the magnetospheric structure and atmospheric dynamics of the planet and the surface features of the Galilean satellites. The encounters with Saturn produced scientific data concerning wind speeds, auroral emissions, and radio emissions from the planet, the fine structure of the previously known and newly discovered rings, the surface features of the satellites and the atmospheric composition and conditions of Titan. Voyager 1 is presently making field and particle measurements on its flight into interstellar space, while Voyager 2 is headed for an encounter with Uranus in January 1986 and Neptune in August 1989.
Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the past mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the more autonomous operations to which we transferred as part of the Autonomous Sciencecraft Experiment (ASE).
Propellant-optimal trajectories, relative sensors and navigation, and docking/capture mechanisms are rendezvous disciplines that receive much attention in the technical literature. However, other areas must be considered. These include absolute navigation, maneuver targeting, attitude control, power generation, software development and verification, redundancy management, thermal control, avionics integration, robotics, communications, lighting, human factors, crew timeline, procedure development, orbital debris risk mitigation, structures, plume impingement, logistics, and in some cases extravehicular activity. While current and future spaceflight programs will introduce new technologies and operations concepts, the complexity of integrating multiple systems on multiple spacecraft will remain. The systems integration task may become more difficult as increasingly complex software is used to meet current and future automation, autonomy, and robotic operation requirements.
Develop and maintain a world class, leading edge capability in Advanced Avionic Systems and Advanced Microelectronics Technologies for future highly integrated, miniaturized, autonomous spacecraft systems for deep-space and Earth orbiting missions.
The verification and validation of autonomy software is widely believed to be a challenging unsolved problem. To a certain extent this is true, but in this paper I argue that the problem is not nearly as severe as seems to be widely perceived. many of the perceived hard problems in autonomy software V&V also exist for traditional software, and can be solved using many of the same methods and techniques used for traditional spacecraft software. In particular, the problem of intractably large state spaces exists for any non-trivial software system.
The NASA Artemis program will return humans to the moon. This time, with the help of commercial and international partners, the program’s objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, more onboard systems autonomy and functionality will be needed to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with-audio, video, lighting, and crew controls. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program-especially crew controls which is the focus of this paper. How does NASA ensure crew controls are reliable to control complex systems and prevent a catastrophic event due to human error-especially when the astronauts could be physiologically and/or psychologically impaired? NASA’s approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls is through a holistic system engineering and Human System Integration methodology that embraces NASA’s Human-Rating Requirements-ensuring human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering, and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.
NASA’s Deep Space Network (DSN) consists of thirteen large (34- and 70-meter) antennas that are used to communicate with approximately 40 NASA and partner spacecraft, all at great distance from the earth (generally at Lunar distances and beyond). The DSN has a long history — over 50 years — and has evolved with cutting edge, often custom, telecommunications equipment and associated software systems. In recent years, and in preparation for an increasing future demand, there has been an effort to invest in initiatives that will result in significant cost savings in the future. These efforts are building on, or augmenting, the recent deployment of “Follow-the-Sun” operations (day shift remote operational control of the entire network from each of the three antenna complexes in turn) — which is being deployed in 2017. This paper focuses on Adaptive Demand Access: in a paradigm shift from completely pre-planned operations, this concept calls for spacecraft to signal their intent (or not) for near-future contacts, in case they have science results of interest, or have experienced an anomaly. This would take advantage of a beacon tone transmission, which can be detected using smaller antennas. When a connection request is received, the DSN ground systems would adaptively accommodate the request, inserting the contact into the plan as soon as possible, subject to constraints and priorities. The demand access concept incorporates onboard data analysis and science data processing, so that beacon tones can be generated with maximum information. This area is representative of several where infusing AI technologies can lead to improved effectiveness of the DSN as the network readies for support of expanded Mars exploration efforts in the 2020’s and beyond.
The Huygens probe arrived at Saturn's moon Titan on January 14, 2005, unveiling a world that is radically different from any other in the Solar system. The data obtained, complemented by continuing observations from the Cassini spacecraft, show methane lakes, river channels and drainage basins, sand dunes, cryovolcanos and sierras. This has lead to an enormous scientific interest in a follow-up mission to Titan, using a robotic lighter-than-air vehicle (or aerobot). Aerobots have modest power requirements, can fly missions with extended durations, and have very long distance traverse capabilities. They can execute regional surveys, transport and deploy scientific instruments and in-situ laboratory facilities over vast distances, and also provide surface sampling at strategic science sites. This paper describes our progress in the development of the autonomy technologies that will be required for exploration of Titan. We provide an overview of the autonomy architecture and some of its key components. We also show results obtained from autonomous flight tests conducted in the Mojave desert.
A spacecraft guidance, navigation, and control (GN&C) system is needed to enable a spacecraft to descend to a surface, take a sample using a touch-and-go (TAG) sampling approach, and then safely ascend. At the time of this reporting, a flyable GN&C system that can accomplish these goals is beyond state of the art. This article describes AutoGNC, which is a GN&C system capable of addressing these goals, which has recently been developed and demonstrated to a maturity TRL-5-plus. The AutoGNC solution matures and integrates two previously existing JPL capabilities into a single unified GN&C system. The two capabilities are AutoNAV and GREX. AutoNAV is JPL s current flight navigation system, and is fairly mature with respect to flybys and rendezvous with small bodies, but is lacking capability for close surface proximity operations, sampling, and contact. G-REX is a suite of low-TRL algorithms and capabilities that enables spacecraft operations in close surface proximity and for performing sampling/contact. The development and integration of AutoNAV and G-REX components into AutoGNC provides a single, unified GN&C capability for addressing the autonomy, close-proximity, and sampling/contact aspects of small-body sample return missions. AutoGNC is an integrated capability comprising elements that were developed separately. The main algorithms and component capabilities that have been matured and integrated are autonomy for near-surface operations, terrain-relative navigation (TRN), real-time image-based feedback guidance and control, and six degrees of freedom (6DOF) control of the TAG sampling event. Autonomy is achieved based on an AutoGNC Executive written in Virtual Machine Language (VML) incorporating high-level control, data management, and fault protection. In descending to the surface, the AutoGNC system uses camera images to determine its position and velocity relative to the terrain. This capability for TRN leverages native capabilities of the original AutoNAV system, but required advancements that integrate the separate capabilities for shape modeling, state estimation, image rendering, defining a database of onboard maps, and performing real-time landmark recognition against the stored maps. The ability to use images to guide the spacecraft requires the capability for image-based feedback control. In Auto- GNC, navigation estimates are fed into an onboard guidance and control system that keeps the spacecraft guided along a desired path, as it descends towards its targeted landing or sampling site. Once near the site, AutoGNC achieves a prescribed guidance condition for TAG sampling (position/orientation, velocity), and a prescribed force profile on the sampling end-effector. A dedicated 6DOF TAG control then implements the ascent burn while recovering from sampling disturbances and induced attitude rates. The control also minimizes structural interactions with flexible solar panels and disallows any part of the spacecraft from making contact with the ground (other than the intended end-effector).
The Space Station Module Power Management And Distribution (SSM/PMAD) automation test bed project was begun at NASA/Marshall Space Flight Center (MSFC) in the mid-1980s to develop an autonomous, user-supportive power management and distribution test bed simulating the Space Station Freedom Hab/Lab modules. As the test bed has matured, many new technologies and projects have been added. The author focuses on three primary areas. The first area is the overall accomplishments of the test bed itself. These include a much-improved user interface, a more efficient expert system scheduler, improved communication among the three expert systems, and initial work on adding intermediate levels of autonomy. The second area is the addition of a more realistic power source to the SSM/PMAD test bed; this project is called the Large Autonomous Spacecraft Electrical Power System (LASEPS). The third area is the completion of a virtual link between the SSM/PMAD test bed at MSFC and the Autonomous Power Expert at Lewis Research Center.
Discrepancy Reporting Management System (DRMS) is a computer program designed for use in the stations of NASA's Deep Space Network (DSN) to help establish the operational history of equipment items; acquire data on the quality of service provided to DSN customers; enable measurement of service performance; provide early insight into the need to improve processes, procedures, and interfaces; and enable the tracing of a data outage to a change in software or hardware. DRMS is a Web-based software system designed to include a distributed database and replication feature to achieve location-specific autonomy while maintaining a consistent high quality of data. DRMS incorporates commercial Web and database software. DRMS collects, processes, replicates, communicates, and manages information on spacecraft data discrepancies, equipment resets, and physical equipment status, and maintains an internal station log. All discrepancy reports (DRs), Master discrepancy reports (MDRs), and Reset data are replicated to a master server at NASA's Jet Propulsion Laboratory; Master DR data are replicated to all the DSN sites; and Station Logs are internal to each of the DSN sites and are not replicated. Data are validated according to several logical mathematical criteria. Queries can be performed on any combination of data.
The Gateway Vehicle Systems Manager (VSM), the top-level software control system in a distributed, hierarchical Autonomous System Management Architecture is, like most modern spacecraft software control systems, heavily data-driven. For example, schedules (timelines) will be developed on the ground and, due to the high degree of autonomy, contain complex procedures involving conditional branching, variable timing, and resource contention resolution. In order to verify that an uploaded timeline will function correctly, it is necessary to explore the feasible set of possible executions. While it is possible to test a timeline using a mission simulation, the complexity of the system and duration of a timeline limits the number of trials and therefore the test coverage. To address this problem, the VSM team is using a discrete event system model that can rapidly generate from a timeline sets of event sequences using Monte Carlo techniques. To achieve rapid and trustworthy checking of the event sequences, we use an offline version of the runtime model checking tool R2U2. This presentation describes the approach the VSM team is using to implement the discrete event simulation and evaluate event sequences using R2U2. The presentation will discuss: 1. Description of the timelines by VSM in the context of VSM operations 2. Expansion of a timeline into a sequence of atomic events 3. Adjustment, in the Monte Carlo environment, of an event sequence to account for uncertainty, external events, and failures 4. Definition of R2U2 input and mission-time linear temporal logic files 5. Generation and use of R2U2 verdict sequences 6. Lessons learned and future work
A methodology is given by which an improvement to spacecraft navigation accuracy may be achieved by including accelerometer measurements as observations.
As NASA moves into the last part on the twentieth century, the desire to do 'business as usual' has been replaced with the mantra 'faster, cheaper, better'. Recently, new work has been done to show how the implementation of advanced technologies, such as intelligent systems, will impact the cost of a system design or in the operational cost for a spacecraft mission. The impact of the degree of autonomous or intelligent systems and human participation on a given program is manifested most significantly during the program operational phases, while the decision of who performs what tasks, and how much automation is incorporated into the system are all made during the design and development phases. Employing intelligent systems and automation is not an either/or question, but one of degree. The question is what level of automation and autonomy will provide the optimal trade-off between performance and cost. Conventional costing methodologies, however, are unable to show the significance of technologies like these in terms of traceable cost benefits and reductions in the various phases of the spacecraft's lifecycle. The proposed comprehensive life-cycle methodology can address intelligent system technologies as well as others that impact human-machine operational modes.
Artificial Intelligence (AI) is a growing field of computa- tional science techniques designed to mimic functions per- formed by people. Advancements in autonomy will depend on a portfolio of AI technologies. Automated planning and scheduling is a venerable field of study in AI, and is needed for a variety of mission planning functions. Plan execution technology is less well studied, but important for auton- omy and robotics. Specialized forms of automated reason- ing and machine learning are key technologies to enable fault management. Over the past decade, the NASA Au- tonomous Systems and Operations (ASO) project has devel- oped and demonstrated numerous autonomy enabling tech- nologies employing AI techniques. Our work has employed AI in three distinct ways to enable autonomous mission op- erations capabilities. Crew Autonomy gives astronauts tools to assist in the performance of each of these mission oper-ations functions. Vehicle System Management uses AI tech- niques to turn the astronaut's spacecraft into a robot, allow- ing it to operate when astronauts are not present, or to reduce astronaut workload. AI technology also enables Autonomous Robots as crew assistants or proxies when the crew are not present. When these capabilities are used to enable astro- nauts to operate autonomously, they must be integrated with user interfaces, introducing numerous human factors con- siderations; when these capabilities are used to enable vehi- cle system management, they must be integrated with flight software, and run on embedded processors under the control of real-time operating systems.We first describe human spaceflight mission operations capabilities. The remainder of the paper will describe the ASO project, and the development and demonstration per- formed by ASO since 2011. We will describe the AI tech- niques behind each of these demonstrations, which include a variety of symbolic automated reasoning and machine learn- ing based approaches. Finally, we conclude with an assess- ment of future development needs for AI to enable NASA's future Exploration missions.
Supervisory or semiautonomous control has some compelling advantages over step-by-step human command and verification for the operation of roving vehicles on remote planetary surfaces. There are also disadvantages in relation to the complex system that must be mobilized and the chain of events that must be enacted to conduct a mission. Which of the two control methods is better on technical grounds may not be the deciding factor in its acceptance or rejection. Some of the issues that affect changes in spacecraft design and operation are summarized. To accelerate the movement toward more autonomous machines, it will be necessary to understand and to address the problems that such autonomy will create for other elements of the control system and for the control process.